Reconcile Accounts Based COPA with FI

Dear Experts,
My client needs material wise, customer wise, Sales Area-wise, region wise etc profitability report. The only way to achieve this is through COPA.I have confusion whether to go for Costing based COPA (CBC) or Accounts based COPA (ABC).
I am afraid of CBC because reports from CBC do not automatically reconcile with FI and I will have a life long task of explaining the difference to management. I have seen clients scarpping CBC because at the end CBC works on calculated values which cannot inherently tally with FI and soon management stops trusting CBC. Moreover Gross Profit level figures for each characteristics can be obtained straight from LIS instead of going for CBC.
I am sure that ABC will reconcile with FI. I presume that this will happen ONLY if field status group of all cost and revenue accounts have been configured to mandate posting to PSG. Else even ABC will not reconicle with FI. My question is If I mandate PSG for all cost/revenue posting then I fear that automatic postings coming from MM/HR will go into error.  How do we handle this and achieve ABC = FI.
If anyone has come across ABC to FI reconcilation error/issues I would like take their guidance before I move forward.
Regards
Deepak Saxena

Hi..!
You can use either activate Costing Based CO PA nor  Accounting Based CO PA.
1.Costing based CO-PA - it will be difficult to reconcile FI with CO PA as lot of time it will take to reconcile.
For this you need to do assessment - settlements and direct postings from FI-MM-SD to CO PA thru PA transfer structure.
You can find the Differences of FI -CO PA in KEAT t-code and based on the you can understand why it is showing difference (If any). This T-code will help you to reconcile.
2.Accounting Based CO-PA  it is easy to reconcile and here the reconciliation happens between GL Account and Cost element level. So you wont get many issues while reconciling.
In Costing based CO-PA you can draw a report at COGS Level where as you wont get it in Account Based CO-PA.
Thanks,
Anil

Similar Messages

  • Account based copa does not tie with GL

    Hello All,
    I have created a report in acccount based copa that shows me the balance of a GL account (XYZ). However, the balance only pertains to postings that have associated profitability segments entered (table CE4XXXX). However, the purpose of account based COPA is to tie FI GL accounts to COPA. Postings that do not have associated profitability segments do not appear in the profitability report, hence the balance of account in FBL3N and the copa report do not match up..this defeats the purpose of employing account based copa that permanently reconciles FI with COPA.
    Ofcourse, there are instances where a profitability segment is not required or cannot be generated but it should show up on the report in order for a user to see FI and COPA balances matching (COEP table is getting updated with the currency value even if a profitability segment is not generated).
    I need to see the total balance of the GL account in COPA divided in the following way:
    Sales                                                                                YYYY
    Cost of Good Sold (Cost element XYZ-assigned to Psg)                   YYYY
    Cost of Good Sold (Cost element XYZ-not assigned to Psg)              YYYY

    You should change your field status in FI to require the proper COPA segment when posting an FI document. In account based no postings should be made to COPA without it.
    pls assign points to say thanks.

  • Reconciliation of  costing based COPA and account based COPA

    hi experts,
                 I want reconciliation statement of A/c based copa and costing based copa through SAP. we have not configured any account based copa reports. now we are manually doing the reconciliation. Please tell me the configuration.
    Thanks & regards
    jay

    HI
    Costing-based Profitability Analysis is the form of profitability analysis that groups costs and revenues according to value fields and costing-based valuation approaches, both of which you can define yourself. It guarantees you access at all times to a complete, short-term profitability report.
    Account-based Profitability Analysis is a form of profitability analysis organized in accounts and using an account-based valuation approach. The distinguishing characteristic of this form is its use of cost and revenue elements. It provides you with a profitability report that is permanently reconciled with financial accounting
    Regards,
    Vijayanand Sankaran

  • Account Based COPA problems

    Hi all,
    I activated the Account Based COPA, but why customer & product (which is the fixed characteristics from SAP) can not be taken during the report execution.
    Everytime I try to see a report with those characteristics it always come back as unassign field.
    Can anyone help me regarding this problems?
    Thanks.
    Lea

    Hi,
    Costing-based Profitability Analysis is the form of profitability analysis that groups costs and revenues according to value fields and costing-based valuation approaches, both of which you can define yourself. It guarantees you access at all times to a complete, short-term profitability report.
    Account-based Profitability Analysis is a form of profitability analysis organized in accounts and using an account-based valuation approach. The distinguishing characteristic of this form is its use of cost and revenue elements. It provides you with a profitability report that is permanently reconciled with financial accounting.
    You can also use both of these types of CO‑PA simultaneously.
    Hope this helps.
    Rgds
    Manish

  • Characterstics Assignment in Accounting Based COPA Config.

    HI,
    How to give Characterstics in Accounting Based COPA Config. and what is the TCode....
    regards
    JK

    Hi
    It is strongly recommended, however, that you do not activate both types of CO-PA. The
    major reason being is that you will have significant table size impacts. You must be careful
    with account based CO-PA as this creates additional line items in the existing CO tables of
    COEP (actual), COEJ (plan), COSP & COSS (summary records). Hence if you want to do any
    cost center reporting, say, from any of these existing tables you will run the risk that
    performance will be degraded by these additional and unnecessary records. 
    The only advantage of account based over costing based CO-PA is it's ability to
    automatically reconcile back to FI, in much the same manner as you would reconcile
    cost center accounting back to FI. However you don't have the flexibility in account
    based CO-PA to perform valuations using product cost estimates etc. as you do in
    costing based CO-PA. If the reason you were advised to turn on account based CO-PA
    as well as costing based was to facilitate reconciliation, it is suggested that you look
    at alternatives that won't have the same negative impacts that turning on account
    based would have. In addition to the serious table space issues, it is not that easy to
    turn on and off account based at will (especially in production).
    Instead what you should look at doing is creating a series of reports that enable you to
    reconcile costing based CO-PA back to CCA/PCA and FI, if this is required. The complexity
    of the costing based functionality you have used will determine the complexity of the
    reports that will be needed to reconcile back, but it can be done without turning on
    account based CO-PA.
    Regards

  • Accounting based COPA Activation

    Hi Guys,
    In present client Costing based COPA is in Production. As its not Reconciling with FI the management has decided to active Accounting based COPA.
    So what are the steps pre req conditions i need to take and what the steps to activate the Accounting based COPA
    Thanks,
    Santosh

    Hi,
    I want you to check this [link|Re: Accounting based COPA] first and then this [link|COPA  Account Based copa;. Please post back on what you feel.
    Hope this helps.

  • Accounting based COPA

    Hi co experts,
    In COPA divided two ways one is costing based copa and another one is accounting based copa
    I have worked in costing based copa.
    My query is in which situation we can use accounting based copa and what are the settings I have do in STD SAP,
    Kindly explain the total accounting based copa concept and required settings
    Regards
    venkataswamy

    Hi
    It is strongly recommended, however, that you do not activate both types of CO-PA. The
    major reason being is that you will have significant table size impacts. You must be careful
    with account based CO-PA as this creates additional line items in the existing CO tables of
    COEP (actual), COEJ (plan), COSP & COSS (summary records). Hence if you want to do any
    cost center reporting, say, from any of these existing tables you will run the risk that
    performance will be degraded by these additional and unnecessary records. 
    The only advantage of account based over costing based CO-PA is it's ability to
    automatically reconcile back to FI, in much the same manner as you would reconcile
    cost center accounting back to FI. However you don't have the flexibility in account
    based CO-PA to perform valuations using product cost estimates etc. as you do in
    costing based CO-PA. If the reason you were advised to turn on account based CO-PA
    as well as costing based was to facilitate reconciliation, it is suggested that you look
    at alternatives that won't have the same negative impacts that turning on account
    based would have. In addition to the serious table space issues, it is not that easy to
    turn on and off account based at will (especially in production).
    Instead what you should look at doing is creating a series of reports that enable you to
    reconcile costing based CO-PA back to CCA/PCA and FI, if this is required. The complexity
    of the costing based functionality you have used will determine the complexity of the
    reports that will be needed to reconcile back, but it can be done without turning on
    account based CO-PA.
    Regards

  • Differences between Costing based COPA and Account based COPA

    Hi,
    I wanted to know the main differences between Costing based COPA and Account based COPA?
    For which scenarios account based COPA used and for which scenarios costing based copa used.
    please guide me
    sateesh

    HI
    Costing-based Profitability Analysis is the form of profitability analysis that groups costs and revenues according to value fields and costing-based valuation approaches, both of which you can define yourself. It guarantees you access at all times to a complete, short-term profitability report.
    Account-based Profitability Analysis is a form of profitability analysis organized in accounts and using an account-based valuation approach. The distinguishing characteristic of this form is its use of cost and revenue elements. It provides you with a profitability report that is permanently reconciled with financial accounting
    Regards,
    Vijayanand Sankaran

  • Account-based COPA and having Cost Center as Real Object in Sales Order

    Hi,
    We have recently activated account-based COPA and in our SO, we realized the Profitability Segment being populated- that is not a problem in normal scenarios.
    However, in some cases, we would like to charge to a cost center instead of COPA. We have tried the 2 ways mentioned in the forum/on the web to include Cost Center in Sales Order:
    1. Go to OVF3 t-code and configure a default cost center for the order reason
    2. Change the SD Document Category under 'Define Sales Document Types' to 'I- Order w/o charge'.
    However both ways only open the Cost center field but still populates the COPA. At accounting entries, cost center will become a statistical object and COPA, the real object- which is not what we want.
    Is there a way to stop the auto-populating of Profitabiltiy Segment in SO when cost center is being entered?
    Thanks very much in advance for any suggestions.
    Regards,
    Huimin

    Solved by myself, with help of OSS Note: 44381 - Profitability Segment Not Required in SD Postings. Have a CO substitution rule to clear away the Profitability Segment number based on certain conditions. Thanks!

  • Account Based COPA Cost of goods sold and Revenue Split

    Dear Experts,
    We are using account based copa in a automobile company.
    As per the requirement when a car is sold, depending on the customer request the car  goes for a conversion. like adding Radio, Seat cover, etc
    As per our setup we have different profit centers for vehicle and Parts(radio, seat cover etc) and in this case radio, seat cover, etc are the classes of the material vehicle(not separate material).
    After the vehicle conversion there is a sales order raised which goes to profit center derived from vehicle material master.
    As per the reporting requirement I need to spit the Cost of good sold  and revenue by vehicle profit center and parts profit center for COPA reporting purpose
    Is there any way to do this in standard SAP? Or I need an exit?
    Appreciate your response and please let me know in case of any clarification.
    Many thanks
    Roy
    Edited by: roy001 on Aug 4, 2011 4:52 PM

    For those who may need an answer to this, our solution was the following: 
    1)       Created new types for SO, SO Item, Sched. Line, Delivery, Delivery Item, Billing type  
    2)       Created new Pricing procedure
    3)       Created new movement type Y61/Y62 modeled after 601/602
    4)       Mapped Y61/Y62 to account modifier ZAX.
    5)       Mapped GBB/ZAX to the new account.
    Benefits, they now have better view of the orders going inter-company.  It is flexible enough to adjusting prices for intercompany separate from standard orders, even though for now it is a straight copy of cost.  They are able to remove the sales/use tax, from the calculations. They are able to plan with these orders separated out.  Plus, this will standardize their process for inter-company. 
    Hope this helps someone. 
    Cheers!
    Rick

  • Account based COPA datsource taking long time to extract data

    Hi
    We have created a Account based COPA datasource but it is not extracting data in RSA3 even though the underlying tables have data in it.
    If the COPA datasource is created using fields only from CE4 (segment ) and not CE1 (line items ) table then it extracts data but tat too after very long time.
    If the COPA datasource is created using fields from CE4 (segment ) and  CE1 (line items ) table then it does not extarct any records and RSA3 gives a time out error..
    Also job scheduled from BW side for extracting data goes on for days but does not fetch any data and neither gives any error.
    The COPA tables have huge amount of data and so performance could be a issue. But we have also created the indexes on them. Still it is not helping.
    Please suggest a solution to this...
    Thanks
    Gaurav

    Hi Gaurav
    Check this note 392635 ,,might be usefull
    Regards
    Jagadish
    Symptom
    The process of selecting the data source (line item, totals table or summarization level) by the extractor is unclear.
    More Terms
    Extraction, CO-PA, CE3XXXX, CE1XXXX, CE2XXXX, costing-based, account-based,profitability analysis, reporting, BW reporting, extractor, plug-in, COEP,performance, upload, delta method, full update, CO-PAextractor, read, datasource, summarization level, init, DeltaInit, Delta Init Cause and Prerequisites
    At the time of the data request from BW, the extractor determines the data source that should be read. In this case, the data source to be used depends on the update mode (full initialization of the deltamethod or delta update), and on the definition of the DataSources (line item characteristics (except for REC_WAERS FIELD) or calculated key figures) and the existing summarization levels.
    Solution
    The extractor always tries to select the most favorable source, that is,the one with the lowest dataset. The following restrictions apply:
    o Only the 'Full' update mode from summarization levels is
    supported during extraction from the account-based profitability
    analysis up to and including Release PI2001.1. Therefore, you can
    only everload individual periods for a controlling area. You can
    also use the delta method as of Release PI2001.2. However, the
    delta process is only possible as of Release 4.0. The delta method
    must still be initialized from a summarization level. The following
    delta updates then read line items. In the InfoPackage, you must
    continue to select the controlling area as a mandatory field. You
    then no longer need to make a selection on individual periods.
    However, the period remains a mandatory field for the selection. If
    you do not want this, you can proceed as described in note 546238.
    o To enable reading from a summarization level, all characteristics
    that are to be extracted with the DataSource must also be contained
    in this level (entry * in the KEDV maintenance transaction). In
    addition, the summarization level must have status 'ACTIVE' (this
    also applies to the search function in the maintenance transaction
    for CO-PA data sources, KEB0).
    o For DataSources of the costing-based profitability analysis,
    30.03.2009 Page 2 of 3
    SAP Note 392635 - Information: Sources with BW extraction from the CO-PA
    data can only be read from a summarization level if no other
    characteristics of the line item were selected (the exception here
    is the 'record currency' (REC_WAERS) field, which is always
    selected).
    o An extraction from the object level, that is, from the combination
    of tables CE3XXXX/CE4XXXX ('XXXX' is the name of the result area),
    is only performed for full updates if (as with summarization
    levels) no line item characteristics were selected. During the
    initialization of the delta method this is very difficult to do
    because of the requirements for a consistent dataset (see below).
    o During initialization of the delta method and subsequent delta
    update, the data needs to be read up to a defined time. There are
    two possible sources for the initialization of the delta method:
    - Summarization levels manage the time of the last update/data
    reconstruction. If no line item characteristics were selected
    and if a suitable, active summarization level (see above)
    exists, the DataSource 'inherits' the time information of the
    summarization level. However, time information can only be
    'inherited' for the delta method of the old logic (time stamp
    administration in the profitability analysis). As of PlugIn
    Release PI2004.1 (Release 4.0 and higher), a new logic is
    available for the delta process (generic delta). For
    DataSources with the new logic (converted DataSources or
    DataSources recreated as of Plug-In Release PI2004.1), the line
    items that appear between the time stamp of the summarization
    level and the current time minus the security delta (usually 30
    minutes) are also read after the suitable summarization level
    is read. The current time minus the security delta is set as
    the time stamp.
    - The system reads line items If it cannot read from a
    summarization level. Since data can continue to be updated
    during the extraction, the object level is not a suitable
    source because other updates can be made on profitability
    segments that were already updated. The system would have to
    recalculate these values by reading of line items, which would
    result in a considerable extension of the extraction time.
    In the case of delta updates, the system always reads from line
    items.
    o During extraction from line items, the CE4XXXX object table is read
    as an additional table for the initialization of the delta method
    and full update so that possible realignments can be taken into
    account. In principle, the CE4XXXX object table is not read for
    delta updates. If a realignment is performed in the OLTP, no
    further delta updates are possible as they would make the data
    inconsistent between OLTP and BW. In this case, a new
    initialization of the delta method is required.
    o When the system reads data from the line items, make sure that the
    30.03.2009 Page 3 of 3
    SAP Note 392635 - Information: Sources with BW extraction from the CO-PA
    indexes from note 210219 for both the CE1XXXX (actual data) and
    CE2XXXX (planning data) line item tables have been created.
    Otherwise, you may encounter long-running selections. For
    archiving, appropriate indexes are delivered in the dictionary as
    of Release 4.5. These indexes are delivered with the SAP standard
    system but still have to be created on the database.

  • KE24 - no line items in account-based COPA

    Hello,
    I am trying to configure Account-based COPA. I did all the configuration and create a report with a form assigned. The account I have posted is a revenue cost element and has profitability segment as an optional field and is updated with segment data.
    Since account-based COPA updates only COEP and CE4XXXX tables I am able to see the record being updated in these tables. But when I run KE24 and COPA report both of them yield no results.
    Please see attached for the detailed configuration and copa report set up.
    Note: I replicated the exact same scenario in another system with same config and also using the same accounts I was able to generate the KE24 and also COPA report. The only difference between these two systems being the database. System where COPA is working is on SQL DB and where it is not is on HANA DB.

    Pablo,
    My issue was because of HANA Database. So I had run a report called RKE_HDB_EXTEND_COEX which extends the COEP/COEJ tables into HDB. After running this the issue was resolved.
    Not sure if you have the same cause. Let me know.
    Thanks,
    Raj

  • COS sales account in Account based COPA

    Hi,
    I am new to account based COPA and like to implement it in parallel to costing based COPA. I understand that COS or COGS account triggered during delivery has to be created as cost element.  What should be cost element category of  COS account ?
    Does it'll cause issue with existing costing based COPA ?
    Cheers,
    Anand

    Anand Agrawal,
    COS account should be of cost element category '1'.
    Cost-based COPA can be provide both cost-based reporting and account-based reporting. Since your existing is cost-based COPA, do not understand your question on any issue with existing cost-based COPA.

  • Quantity in Account Based COPA upon WBS Settlement

    Hi All
    I am facing an issue with the quantity flow into Account Based COPA.
    We have activated account based COPA and we use sales orders/billing and also Projects.
    When I am creating sales order (no reference to WBS), delivery against sales order and billing from delivery, I see that
    quantity posted in Delivery document and quantity from billing document are transferred to account based COPA along with GL postings.
    But when I am creating sales orders with account assignment of WBS, then all the delivered quantity and billed quantity
    are posted to WBS elements along with the FI postings. Receiver on my WBS is COPA segment.
    When I settle the WBS that carry both revenues and costs (COGS to be sepcific), I see that amounts are settled correctly with
    right GL accounts into account based COPA, but I do not see that quantities getting transferred.
    I know how we can transfer quantities using costing based COPA during settlement (using PA Transfer structure with Qty setting), but
    not sure how it works in account based COPA for settlements.
    Any thoughts on how to transfer quantities from WBS settlement to account based COPA.
    Your help is much appreciated
    Thanks
    Rama

    Hello Rama,
    First of all, I want to give you with note 352610 some general
    information about the update of quantities in CO. For further
    analyses I would recommand you report RKACSHOW where you can
    find the relevant tables you can take a look, f.e. table COKA,
    COSS(A) and COSS(A). Probabely in table COKA the field 'MEINH'
    is not filled.
    Furthermore I want to provide you note 27922 which explains in detail
    the system behaviour for settlements in this case.
    https://service.sap.com/sap/support/notes/352610
    https://service.sap.com/sap/support/notes/27922
    Thanks and best regards,
    Ronghua Fan

  • Account Based COPA extraction

    Hi,
    I created an Account based COPA datasource with the available Operating Concern. After doing this, when I am trying to check the Extraction in Rsa3, i get an error message saying Errors occured. No other information is displayed. Can anyone please help me out with this? Has anyone encountered such an error? This is critical. Please respond as soon as possible.
    Also note that while creating the Datasource in KEB0, the Summarization Level option is not enabled. would this be a possible reason of the error??
    Regards
    Forum

    Hi,
    iam also facing same problem if any body have solution let me know

Maybe you are looking for

  • Shutter sound that camera makes when taking a picture sound like it's dying.

    The shutter sound that my iphone 5s makes when I take a picture sounds like it's dying. Anyone else have this happen on their phone? This hasn't caused a problem with taking pictures but it sounds weird.

  • My Ipad2 is asking for me to update Carrier settings

    But won't let me either "update" or "not now" moreover I can't get past this screen and it won't allow me to power off and reset. Help please

  • A bug in message pattern's queue implementation?

    Here is how to reproduce the problem. Have 2 Java program ready. A is to create a queue and publish 3 messages to the queue. B is to subscribe to the same queue and try to get all messages from the queue (put the getMessage inside a while(true) loop)

  • OWM and Training

    Is there any OWM Oracle University training (couldn't find any)? I ask this because the only "official" training I have had is what is tacked onto the Oracle Spatial class, but I really need something more for both myself (lead db developer) and our

  • ISE 1.3 Policy Set

    We want to create a policy set that hits on a endpoint identity group. An endpoint identity group contains a bunge mac-address which we can't filter out with radius user-name match which work fine for a vendor hit. Does anybody got an idea of this is