SAP Note 15307 - Performance

Symptom:

Poor performance when creating/editing production orders, networks, plant maintenance requests, projects ( CO01, CN21, ...)

Solution
Performance is affected by a large number of factors. In addition to
hardware installed by the customer, which of course cannot be considered in this note, there are a number of parameters that
the customer can check and influence. Only the most important ones are
listed in this note. Should you have further questions, the SAP 'Early Watch Service' is available for you to take advantage of.

The following aspects should be taken into account when judging performance:
1) Data volume and constellation (extensive BOMs/routings; complex conditions in pricing/calculating overhead rates)
2) Scope of the functions performed (operation checks when routing is copied, type of availability check)
3) Technical parameters (buffer situation, network architecture, number of dialog processes)

Re 1)
Whenever possible, avoid using complex access sequences when selecting BOMs and routings.
Also check the conditions for pricing (They are used to determine overhead rates). If you are not interested in the planned costs of production orders, you can switch off the calculation of planned costs by not entering a costing variant for determining planned costs (Order Type Dependent Parameters in the customizing menu of Production Activity Control).

Re 2)
To improve performance, you should deactivate the availability check during order creation (customizing menu of Production Activity Control: Operations -> Availability Check -> Control).
Checking of the routing data during order creation should be deactivated (Customizing: Order Type Dependent Parameters) as well as
checking of the component data from the BOM via detail screens.

Performance problems in lead time scheduling and calculation of capacity requirements can be traced back to calculation of the formula analysis. Here one must be careful that the formulas in Include
FCR05xxx ('xxx' stands for the respective command) are present in
generated form. The formulas can be generated explicitly via report
RCR05GEN.

Re 3)
A monitoring tool exists within the SAP System (Tools -> Administration -> Monitoring -> Performance -> Tune/setup buffers that can be used to judge the quality of the system buffers). The qualities of the DDIC-relevant buffers should always be > 95%. The size and quality of the program buffer are equally important. In PP, the program buffer should be at least 40 MB. The allocation of applications per application server is also important for good quality. The optimal configuration is one work area per application server. i.e. users from different work areas (PP, SD, CASE) do not work on one application server; instead, separate servers are configured for PP, SD, CASE, etc. You should select the number of dialog processes in such a way that at least one dialog process is always available. This and the possible size of the system buffer are dependent on the memory available on the application server. For sufficient performance, the memory capacity should be at least 256 MB.