018: Manual FI/CO configuration in R/3

When implementing SAP R/3, you normally use at least 3 different systems: development, quality assurance and production. Normally system configuration can be transported from development to production via quality assurance systems. But some types of configuration has to be maintained manually in each single system. This becomes obvious when building the Foxy Cola prototype using a separate development and quality assurance environment.

This post shows the types of configuration I have encountered that requires a manual effort in each system.

Although considered master data, General Ledger accounts are vital. Else no end-to-end business process can be recorded by the system because the assignment of General Ledger account is part of system customising that can be transported between systems.
As Foxy Cola is prototyped based on the official SAP demo system, the model company code 1000 can be used as reference. So that avoids the need for data migration development.
Use the SAP transaction OB_GLACC01 to copy the General Ledger accounts using a reference company code.

Each system has various calendars, for example to define when the factory is open for business and to define public holidays.
It is important to verify whether these calendars have been maintained far enough into the future to avoid issues with planning related business transactions in the system. For example, you cannot execute Material Requirements Planning in a specific year when the calendars have not been maintained.

In order to analyse profitability in the Controlling module, you need to maintain a Profit Center Hierarchy and a Cost Center Hierarchy. These structures for profit centers and cost centers have to be maintained manually in each individual system. Be aware that General Ledger accounts may be linked to individual profit and cost centers. So it is important that the structure set-up in the development environment is mirrored in the other environments.

Also number ranges need to be maintained manually in each single system. Various types of number ranges are required in financial accounting and controlling. regarding controlling, it may be necessary to execute the correction program RKTKA04C when you experiences difficulties in maintaining the number ranges.

When you are serious in using the controlling module, you need also to have a Operating Concern. You can create one from scratch, but Foxy Cola uses the existing operating concern code 1000.
Use the transaction KECP to create an operating concern based on data from an existing one.

After creating the operating concern, check the derivation rules as they may cause inconveniences when processing a sales order flow when releasing billing document information to accounting.
Regarding the Foxy Cola prototype some changes were necessary to maintain the derivation rule regarding customer intercompany indicators.

Finally, take close attention to opening and closing posting periods as that is quite fundamental when using the system to record business transactions with a financial consequence.