vnsolutions (vnsolutions) wrote,

10 Consulting Notes for CO-PA Analysts

Profile picture of Solutions VN solutions said 59 minutes ago:

  • Note (1) Free of Charge Deliveries – Costs in CO-PA
    One of the most common business requirements is of handling free of charge delivery
    costs in CO-PA. If no Billing Document is generated for free-of-charge deliveries, costs
    are not transferred to Costing-based PA. However, you would like to see costs for such
    free of charge deliveries in CO-PA.
    10 Consulting notes for CO-PA analysts Page 2
    You have two options to transfer costs to PA.
    1. Sales Order -> Delivery -> ‘Zero dollar’ Invoice
    2. Sales Order -> Delivery -> Invoice with 100% discounts
    Consulting note 36129 (Release: 21A – 46D), describes first scenario where costs are
    transferred to CO-PA with Statistical condition type in Invoice Document.
    For Option 2, Consulting note 33258, explains how to configure relevant settings in SAP.
    Note 33382 describes free-of-charge items for Inter-company billing.

    Note (2) Characteristics from SD transaction Tables to CO-PA
    Another very common business requirements is to transfer SD characteristics from
    transaction tables (VBKD, VBAK or VBAP), rather than master tables (KNVV).
    For example, in Standard SAP system, Customer Group (KDGRP) has a reference to
    master table KNVV. Therefore, if you change the customer group in the Sales Order, this
    changed value is not transferred to CO-PA.
    Consulting note 33968 (release: 300 – 46D) explains how to transfer SD transaction
    characteristics to CO-PA.

    Note (3) SD Partner functions in CO-PA
    Certain standard SD partner functions (Sold-to, Ship-to, Bill-to, Payer, Sales Employee
    etc.) are available in CO-PA as pre-defined characteristics.
    However, in Sales and Distribution (SD) module you can create your own additional
    partner functions. To transfer these ‘customer defined partner functions’ to CO-PA, refer
    to consulting note 36557 (release: 300 – 46C).

    Note (4) Product Hierarchies in CO-PA Reports
    Product Hierarchy field is typically made up of 3 Parts. If you have only one
    characteristic in PA to store Product Hierarchy, you will not be able to drill-down
    through all the levels in CO-PA Reports. If you want to drill-down through all the levels
    of the Product Hierarchies, you will need to have three separate Characteristics in COPA.
    Note 62690(release: 30A – 40B, as of release 4.5, there is an integrated option available.)
    helps you define your own characteristics to represent 3 levels of Product Hierarchy.

    Note (5) + / – Signs in CO-PA and Conditions with plus/minus signs
    Revenues in different applications within SAP are stored with different +/- signs. For
    example, in FI module, Debits have +ve sign and Credits have –ve Sign. However, direct
    credit revenue postings from FI to CO-PA have +ve signs.
    To avoid this confusion, typically, in CO-PA all amounts1 are stored as positive.
    Notes: 52849 and 33178 explain the sign logic of value fields and how ‘transfer with +/-‘
    indicator in transaction code (KE4I) can cause unexpected results in CO-PA.
    Consulting note 33178 gives information on sign logic with an example. Consulting note
    52489 explains in detail the control indicator ‘Transfer +/-‘ in transaction code KE4I.

    Note (6) SD Condition Types to CO-PA Value Fields
    Condition Types is the link between SD module and CO-PA. Condition Types from SD
    are mapped to Value fields from CO-PA. Sometimes it is confusing and you don’t know
    which SD condition Types are transferred to CO-PA. General thumb rule is ‘SD
    condition types assigned to CO-PA value fields via transaction code KE4I’. However,
    irrespective of this thumb-rule, Consulting note 20254 (release 040 – 620) lists certain
    • SD conditions with Revenues and sales deductions whose G/L account is created
    in CO with cost element type 11 = ”revenue” or 12 = ”sales deduction”,
    • Statistical Condition Types
    • Tax Conditions are NOT transferred to CO-PA
    Note that Statistical Condition Types are always available in CO-PA. This special feature
    can be utilized to ‘fine-tune’ CO-PA ledger, by populating Statistical conditions and
    posting additional information in CO-PA.
    Note that for Make-To-Order production, condition types from Sales Order can be
    transferred to CO-PA using Order Settlement.
    Note (7) Valuation with Condition Technique in CO-PA
    Valuation in CO-PA is used for calculating additional values in PA ledger. Basically
    there are three valuation techniques: Product Costing Info, Costing Sheets and User Exit.
    Consulting Note 62536 (release 040 – 620) explains in detail the features of Condition
    Technique using Costing Sheets in CO-PA.
    Note (8) Characteristics from Variant Configuration
    In the standard SAP system, you cannot transfer characteristics from variant
    configuration to CO-PA. Refer to consulting note 93652(release: 30A – 46C) for a
    proposed solution. Please note the pros and cons of using this note.
    Note (9) Costs for Third-party Processing
    Typically, costs from Invoice Receipts are transferred to CO-PA (Costing-based) via
    VPRS of the Billing Document. However, if the invoice receipts takes place after the
    customer billing documents. Actual costs are not transferred to VPRS. Refer to
    workaround solution note 35367 (release: 300-45B).

    Note (10) More than 120 value fields
    In release 4.x, you can have maximum of 50 characteristics and 120 value fields allowed
    in an Operating Concern. Typically, for most of the installations, this is more than
    enough. However, I have met one customer who had already utilized 117 value fields and
    wanted to analyze if they could create more than 120 value fields. If you want to have
    more than 120 value fields, refer to note 160892.


  • Post a new comment


    Anonymous comments are disabled in this journal

    default userpic

    Your IP address will be recorded