CO-PA Account Based enhancement : BELNR-CO

Hi all,
I have successfully implemented a CO-PA ETL for both Costing and account based CO-PA in my system.
I enhanced the costing based Extraction with no major concern.
However I now wish to enhance the CO-PA Accoutn BAsed, and here I struggle , because I cannot get the controlling document number - part of COEP key - in my extract.
I need to use this controlling document number in order to conduct some logic in the extraction, but the creation of the account based datasoource in KEB0 does not provide the option to have this field as part of the extract structure ( as a sidenote, it will not be defined in KEQ3 either, as the granularity of the profitability segment would then be to fine)
... Any idea on how to collect the CO doc number in this scenario? I am missing something...
I would very much appreciate some insight from experienced CO-PA - BW community members !
Cheers
Patrick

Patrick,
The link between COSP / COSS and CE4xxxx is the objnr of the tables COSP / COSS. The first 2 positions = 'EO'. The following positions, the name of the results area and rest of the objnr relates to the PAOBJNR of table CE4xxx. In the table CE4xxxx the field KNT_FRM_KZ = '1'. This means account based CO-PA object.
For the standard extraction process you don't need to build things between these tables. The extractor knows the relationships already.
Regards,
Peter

Similar Messages

  • COPA account based extractor (Bill type field FKART) missing

    Hello Experts,
    I am new to COPA and currently working on account based COPA DataSource on ECC 6.0 & BI 7.0.
    I have created the DataSource in KEB0 for account based by selecting the appropriate operating concern. One of the field requirements for me is to have billing doc type but it is not available in KEB0 or in RSA6.
    When checked in KEA0 billing type (FKART) is available as display fixed fields.
    Main menu -> extras -> display fixed fields.
    Could you please let me know how to get this part of my DataSource?
    Does enhancing the DataSource is only the solution?
    Highly appreciate your help.
    Best Regards
    VJ

    Hi Vijay!
    If your current scenario does not present you with the standard extractor from the source system, perhaps you should try to create a generic datasource for your business requirements.

  • Post GL Accounts based on valauation class in EDI Postings

    Hi,
    We have a business requirement in intercompany billing postings.  At the time of posting the account receivable posting through intercompany billing, system also post account payable posing based on the EDI settings.  However standard EDI settings for determine GL Account is based on the vendor and company code not on the basis of valuation class.  Hence, we need to determine the account payable gl accounts based on valuation class instead of GL Accounts assigned in EDI.
    For that we through of using the Enhancement FEDI0001 and userexit EXIT_SAPLIEDI_001. However this exit is not trigerring while inbound idoc is processed.
    Kindly advice how we need to process and whether we are using the right userexit or not.
    Best Regards.,
    Goutham

    not answered

  • Please tell me a BAPI to get Closing balance of customer account based on Sales Organization?

    Hi Experts,
    A requirement has come up where I want to get Customer closing balance based on its sales organization as this particular customer is extented to 2 different sales organizations. I want to get the closing balance of individual sales organization vise.
    Please tell me a BAPI to get Closing balance of customer account based on Sales Organization?

    AFAIK there is no such BAPI, cause there is no database table with balance for customer per sales organisation. (No KNCx table for VKORG)
    First ask functionals (*) how to recover sales organisation from a FI document (I suppose for SD invoice it is easy if no merging between organisation) will be a little tricker for pure FI document like payment transactions (hope thet are quickly cleared...)  Then start from non cleared records of BSID (also BSAD if you use a past date of reference, in case you have to add the records of BSAD with clearing date greater than reference date) and cross it with SD information to break FI into sales organisation.
    Regards,
    Raymond
    (*) Ask for where do they store VKORG in FI documents

  • Posting to different GR/IR account based on purchase order type

    We are implementing cross company stock transport orders that require an AP invoice to be posted against the goods receipt.  Our AP department does not want the GR/IR postings to go to the account used for traded AP.  I cannot determine a method using OBYC to specify a different account based on purchase order type.  Is there a way to do this?

    Hi Jud
    You should make these posting to a cost center then..The only way you can control account postings via PO type is having a account assignement category. You can make this as mandatory filed for this PO type..
    Please let me know if your requirement is different..
    CHeers
    R K Bolla

  • 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!

  • Activating Account based Copa in the existing Cost-based COPA

    Hi Sap CO gurus!
    Please advise me for the following issue.
    Presently, My client using Cost-based COPA for segment wise reporting.( Already activated).
    Now they wanted the reports in Account Based. Is it possible to activate the Account based now? Will the system allow us to activate or not?
    If yes, What will be the implications? I want to know the pros and cons for that.
    If not, How Can I edit the COPA settings( Operating concern)? Or shall I delete the Operating concern and create one new one?
    Can you please explain the impact of each situation?
    Thanks a lot in advance
    Rama

    Hi Joe
    You can deactivate Account Based COPA, but you will have to do a thorough testing so that you are aware of the issues that can crop up
    The IMG Menu is SPRO > Controlling > Prof Analysis
    You will have to do a testing of how the open sales orders would behave... The open sales orders mean Sales Orders where PGI has been done, but billing is pending AS WELL AS Sales orders which are just created, but no Logistics movement (PGI) has taken place... You will have to do testing on both types of sales orders
      - When you do PGI after deactivating the account based COPA, you may face error. Because, COGS GL account is a cost element in Account based COPA, where as in Costing based COPA, it is usually not a Cost Element
      - Also do a billing from an open sales order and see if you get any error there...
    Similar issue can arise during variance settlement also, because the variance account is not a cost ele in Costing Based COPA.
    Test out the above scenarios and do share your experiences
    Regards
    Ajay M

  • CO -PA Account based extractor

    Hello
    We want to create a CO -PA Account based extractor delta. We have created the summarization levels (KEDV) and tried fill it with Data (KEDU). The problem is that this process takes too much. It spends too time and reach the time out for the machine. How may I optimized this time?  Is it true that  we must run this transaction before each load in BW not only for BW Full load but BW Delta load by CO -PA Account extractor?
    Thanks.

    Hello
    We want to create a CO -PA Account based extractor delta. We have created the summarization levels (KEDV) and tried fill it with Data (KEDU). The problem is that this process takes too much. It spends too time and reach the time out for the machine. How may I optimized this time?  Is it true that  we must run this transaction before each load in BW not only for BW Full load but BW Delta load by CO -PA Account extractor?
    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

  • GL account based on account assignment group

    Set the GL account based on the account assignment group of the customer. How is it done?

    hi Zarah,
    in enhacement SAPMF02D you can check if the right recon. account is selected, however you cannot change, but you can issue an error message.
    hope this helps
    ec

  • What is the purpose of account based COPA when we have FSVs

    Hi,
    I noted the information we can get from account based copa is exactly the same as the information we can get from financial statement version reports. As such why do we need account based copa for?
    What info i can get in account based copa that i cannot get from FSV reports?
    help.sap.com

    Hi,
       Information gets passed to account based COPA if the relevant G/L account is a cost element.
       However account based COPA uses PA segments. This information contained in the PA segment can be viewed via KE24
       To test this post a billing document using account based COPA. After that go to KE24 for account based COPA and check the report. You will see all the details which would not be available in any FI report. Basically the information available for reporting makes it worth using for account based COPA
    regards
    Waman

  • COST ELEMENTS IN ACCOUNT BASED COPA

    Hi all,
    1. I understand that all FI/GL accounts correspond to COST   ELEMENTS in COPA.
    2. I also understand that there are NO value fields in an Account Based Profitability Analysis.So there is no VALUE FIELD to KEY FIGURE mapping.
    3. My question is: how do we map each individual GL account into BI?
    4. If we dont map each individual GL account, how do we report these accounts in BI?
    This part of Account based has been very confusing. I have searched numerous posts, but they all have the same answers, none that explains how we handle the numeric fields of account based profitability analysis.
    Cheers
    TJ

    You will have a KF lets say amount
    In account based COPA your Cost and revenue elements will identify what does the value in this KF corresponds to.
    your report will look something like below:
    Ex:
    Cost and Revenue Element #     Amount
    800 - Revenues                     1,000,000
    808 - Sales deductions             100,000
    800 - 808 = Net Revenue            900,000
    893 - Cost of Sales               90,000
    231 - Price Difference              10,000
    Total                               1,000,000
    You may get amount from source system in 2-3 diff currencies like controlling area curr, transaction curr...
    Sometimes range of accounts correspond to a value. Ex: Accounts 800-900 resemble revenue.
    In such a case you may create Text node in hierarchy called revenue and use it in report (if no hierarchy available from the source system) or create selection in the report.,

  • How to stop the charges incurred to my account based on the action of itunes storing U2's newest album into my iPhone that I personally did not pay for?

    How to stop the charges incurred to my account based on the action of itunes storing U2's newest album into my iPhone that I personally did not pay for?

    There was no charge. The album was free.

  • 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

Maybe you are looking for