4 Answers

• 00

  BETA

  ChatBot4/13/25

  Automated answer

  This reply was automagically generated by our Espressi A.I. Think of it as a one-off attempt to instantly solve your problem. It will not respond to further replies.

  Hello Ulrich, when switching to SAP S/4HANA and implementing margin analysis with COGS split, there are indeed some challenges regarding the data basis for the COGS calculation. In your specific case, where you want to use the production order cost estimate (FAUF) as the basis for the valuation, you encounter the problem that the standard functionalities primarily support standard cost estimates and sales order cost estimates ### Standard approaches and options: 1. ** Standard cost estimate and sales order cost estimate in margin analysis:** - As you have correctly stated, the COGS split in SAP S/4HANA is mainly based on standard cost estimates or sales order cost estimates. Standard costing (usually stored via the material master data) is often used for standardized products, while sales order costing (or unit costing) is used for more specific or customer-specific products. 2 Customization through BAdIs: - The use of Business Add-Ins (BAdIs) is a common method to map special requirements in the COGS splitting mechanism. The BAdIs, such as COPC_COGS_SPLIT and COPC_COGS_SPLIT_ITEM, allow you to implement your own logics to define and split the COGS. These would allow you to integrate the cost information derived from the production orders. ### Potential procedure: #### Step 1: Analysis of existing costing data - Check whether and how the data from COSP/COSS is currently used for the production orders and to what extent this information can be transferred to a standard structure. #### Step 2: BAdIs for integrating production order costing - Use the existing enhancement points using BAdIs to map the transfer of costing data from the production orders to the COGS split logic. Here you could possibly develop a mapping logic that pulls the relevant cost information from COSP/COSS and flows into the COGS split accordingly. #### Step 3: Test and validate - Implement the customizations in a test environment first and validate the results thoroughly to ensure that the costs are mapped and mapped correctly ### Final note: It sounds like you have a very specific requirement that may not be fully covered by standard functionalities. Often in such cases the use of customizing and BAdIs is unavoidable. I would also recommend discussing this with SAP support or an experienced SAP consultant to ensure that all aspects of the conversion and new functionalities are implemented correctly.

  report

  Need more help from our chatbot? Click here and visit our AI SAP Helper on the SAP learning platform et.training.¹

  1. log in with your Espresso Tutorials account. Digital subscription or trial access required.

• 00

  

  User #17919 (Author)4/13/25, 3:59 PM

  Where do the BAdIs COPC_COGS_SPLIT and COPC_COGS_SPLIT_ITEM come from?

  report
• 00

  

  exberliner 5/14/25, 1:26 PM

  These are the BADIs for COGS Split and COGS Split Basis. We use them to split the COGS according to primary costs.

  Good question - I don't know how the COGS split based on unit costing can be posted without a BADI. But maybe the standard should be able to handle it, if I read this description

  FCO_COGS_SPLIT_BASIS

  With the SAP standard logic for splitting the cost of goods sold, the split must be based on either the unit cost estimate for the sales order item or the standard cost estimate for the material/plant combination. This BAdI enables you to use a different basis for the split. For example, you could use a past or future standard cost estimate or the actual cost estimate of the previous year.

  report
• 00

  

  User #17919 (Author)5/14/25, 1:56 PM

  Hello exberliner,

  I don't want to be petty, but the AI confused me with the wrong names. I already know the two COGS split BAdIs quite well.

  One of them can juggle the costs. For my customer, the standard COGS split is to be used in more detail in that the target accounts (with the total costs per cost element) are split into accounts for fixed and variable portions. This can be mapped, but only for costs that originate either from a sales order cost estimate (whether unit costing or product costing, as my contact at SAP has since confirmed) or a material/plan cost estimate.

  If the pilgrimage to Walldorf does not bring anything in the short term, you would have to determine the plan values for FAUF from the known tables in the same BAdI for the requirement to crunch the costs from a production order cost estimate, apart from the aforementioned fixed/variable split - after you have indicated to the system in the BAdI FCO_COGS_SPLIT_RELEVANCE with a switch that you want to do without the limited standard logic.

  Best regards

  Ulrich

  report