cancel
Showing results for 
Search instead for 
Did you mean: 

Disable EK02 SD Condition - calculate cost - performance issue & impacts

FabioFontao
Discoverer
0 Kudos
147

I am experiencing performance issues with sales order creation in SAP via integration. I have identified that the issue occurs due to cost calculation, as outlined in note https://me.sap.com/notes/2569300/E. I have reviewed the configurations (controlling -> Product Cost Controlling -> Cost Object Controlling -> Control of Sales-Order-Related Production/Product Cost by Sales Order).

The note states: “In the customizing of the requirement class, please check field 'Costing ID'. The field should have value A (Automatic costing) or B (Automatic costing and marking). This means that the sales order item will be costed (marked) automatically during saving. Resolution: You should check if you really need the sales order cost estimate. If not, then you can change the requirement class, so that the system doesn't automatically calculate each item. If you decide that you need the cost estimates, you can still consider to not do that automatically during saving of the sales order but asynchronously via T-code CK55.”

The client indicated that they do not use this condition when saving the order but find it useful for subsequent price determination studies. Therefore, I removed the value “A” from the configuration and left it empty, and the condition was no longer calculated, as expected. I executed CK55 after creating the order, and the condition was calculated correctly. This resolves the issue as the interface will function, and the calculation will be done after the order creation process.

Now, I need your help to understand if there are any other impacts with this configuration in CO, cost, or anything else. I would like to confirm whether this configuration only disables this calculation without affecting other processes.

Accepted Solutions (0)

Answers (0)