Skip to Content
author's profile photo Former Member
Former Member

COPA alternatives for posting kits at header(real)&subitem(statistic) level

Dear Experts,

In the company where I am working, there is a product category called u201Cpacksu201D that is composed by different finished products but are sold together in one single reference. This means that the composed product has a BOM that includes the finished products as components. The header has a specific business line for packs, and the subitems/finished products that are part of the header belong to different business lines.

We have a business requirement in terms of CO reporting where the margin needs to be analyzed from two different perspectives: either at header level (i.e. business line packs) or at subitem level (i.e. by the business line of the finished products that composes the pack).

The billing from SD will occur at header level, and revenues, COGS, discounts will be transferred to COPA (and FI) for the header, but based on the business requirement, we need to statistically post the subitems in order to be able to analyze the margin at business unit level of the subitems.

We have already disregarded the option of creating positions in the SD billing for the subitems, as this leads to an array of inconveniences for example if goods issues needs to be cancelled, etc.

So, we have considered replicating a logic so that if the material sold is a pack, the system should distribute revenues, COGS, discounts, etc at item level proportionally based on the COGS of the subitems. The doubt we have is whether create this logic in BI or in COPA.

Does any of you experts have experience of a similar case? What do you think is more viable, to do this in BI or COPA? How could a solution in COPA be set-up? What would be the advantages/disadvantages of setting it up in COPA vs. BI?

I thank you in advance for your valuable feedback.

Kind Regards,

Eric

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Posted on Jan 11, 2011 at 12:22 PM

    Hi Eric

    The std solution, i guess, is IS-Retail... I have not used it though...

    W/o IS-R, you need to do a development....My answer would be as below

    Assume you have Products A, B, C & D which are packed together into E

    1. I would prefer billing for Sub items and not for header item...Because, in COPA if you want to analyse A to D, then billing has to happen for A to D and not E

    2. Have 2 set of Item Categories i.e. one for Header Material E and the other for A to D.. The item category for E will not be relevant for billing

    3. When you create sale order for E, use Exit MV45AFZB and populate the Order Items A to D in the sales order using the BOM of Material E (Tables MAST & STPO)

    4. Using the same exit, Split the revenue of E into A, B, C and D...

    5. In COPA Valuation strategy 001 in KE4U, specify that Valuation has to happen using a User Exit (COPA0002)

    KE4U - Select 001 - CLick on DETAILS - Specify Exit No in the Field "Exit" and Specify QTy Field ABSMG...

    You will create the Exit and give it a name as per the documentation available in the field "Exit" in KE4U... Press f1 in this field

    6. Code this exit in a way that the COGS of E is split into A to D depending on the Material Master price of A to D or based on any logic you want

    Regards

    Ajay M

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 11, 2011 at 12:55 PM

    Hi Eric,

    we basically had the same requirement.

    Our solution goes like this:

    We wrote an ABAP Program that reads data from COPA and then splits all the values that COPA has for pack x onto the components. We apply different splitting criteria here for revenue, COGS, etc (defined in a customizing Z-table for each value field). The quantity split is taken from the BOM. The program then writes the result in a Z (customer created) table. The Z table has a characteristic "component" in addition to the characteristic "article" (it also has all the other characteristics from COPA that we need for our reporting).

    This Z-table is then used to create a BW-cube for our reporting.

    In the reports, you are free to choose if you want to take the "article" (pack)-view ot the component-view.

    You may also want to check out this thread: http://forums.sdn.sap.com/thread.jspa?messageID=9791818#9791818

    If anything is unclear, please get back

    Regards

    Nikolas

    Edited by: Nikolas John on Jan 11, 2011 1:56 PM

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Feb 10, 2012 at 11:06 AM

    Does your company use BW? if you have BW you can load the individuel subitems from the sales order, and the BOM-structure as master data, and do the profitability analysis in the BW reports. The advantage of BW over CO-PA is that you have more flexibility to derive the cost structure, as you have all the individual components. You also don't need to do customisation in R/3 as all the business rules are applied in BW, eitehr on query level or in the datamodel where the infoCube is loaded with data.

    You may also extract CO-PA to BW, shere you can add missing data to the reports for example the BOM-structure with the subitems or costing info on subitem level from material master if this is not available in invoice conditions

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.