In the standard transaction the user can only choose ONE plant or all plants in the entire CO Area Implementing this note will provide more flexible possibilities for selecting the scope of orders included in collective processing:Įxample with settlement transaction CO88: Hence SAP offers a solution – described in OSS note In a global group company with different time zones and even possibly different closing schedules this is not refined enough. In all of these collective transactions, the SAP standard system (valid for S/4 HANA On-Premise, Extended cloud as well as ECC) offers 2 selection options: Either you can run for one single plant or for the entire controlling area. KKS1/KKS5 Variance Calculation (Separate calculation for Cost collectors and Orders).For this purpose the following transaction codes exists – the below list covers process orders, production orders and product cost collectors. As part of the month end close you want to perform the mass/collective transactions for a complete plant, possibly even for a multiple different number of plants within the same legal entity. In this Blog I’m focusing on the collective run transaction. If you have been working with closing steps in cost object controlling you are probably familiar with the different standard possibilities to run the various closing steps:įor each of these steps there’s an individual and a collective run transaction.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |