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

Similar Messages

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.

Extract account Based COPA from R/3 using Business Object data services

Hello,
We have a requirement to extract Account Based COPA from SAP R/3 to Teradata using Business Objects data services.
I have read couple of white papers which give information on Rapid Marts( which are built in packages) already available for some applications like inventory, GL, AP, AR etc. But I could not find anything for COPA.
Would anyone give me any information on how to use BO data services for COPA?
Also if there is no rapid mart available for COPA, does anyone know how to create custom data marts in BO Data services?
Is there any document available on this?
Please respond as soon as possible.
Thanks.

Hi,
this forum is for the SAP Integration Kit. Would suggest you post your question into the EIM area for Data Services.
Ingo

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

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

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.,

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

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.

Which table the characteristic values of accounting based COPA are stored?

Hi Guru,
we are using Accounting based COPA. we need to generate a report based on the characteristic values updated while posting to revenue accounts.
i searched the CE4XXXX and COSP tables but i am unable to get the results. COSP is not havinf the the revenue GL accounts PA characteristics.
CE4XXXX is not having the the PAOBJNR(profitability object no) updated in BSEG for the revenue accounts.
from which table can i capture the characteristic values for a line item posted in BSEG.
regards
Jaya

HI
refer CE4XXXX_ACCT for account based COPA
The function module to read chars from PSG is RKE_GET_CHARS_FOR_PAOBJNR
Regards
Ajay M

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

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

Qty from VA88 Settlement for Account based copa

Hi Gurus,
I have a question on VA88 in MTO-E scenario. In account based copa the qty will update in Delivery. In MTO-E Scenario there is no accounting entries in Delivery(PGI).
Is there any way to derive Billing qty in Settlement.(VA88)
Thanks
Vasanth K.

Hi Castles
It depends on your segment level chars in KEQ3.... Suppose you defined Customre and Product as Seg Levle CHar
Each time you enter a new Cust or Prod in sales order - The record will be written to CE4 and a new PSG no would be generated... Next tieme when you enter same Cust / Prod - Same PSG would be used
If you see carefully in KEQ3 - Sale order is not a segment level char by default.. hence, Sales order is not written in CE4
However, you can see it in table CE4xxxx_ACCT
Regarding jumping no.s you can refer table SNRO and check your buffer... your basis guys should help in this
In Account based COPA, PSG is determined at sale order itself.. refer note 1351257 for more details
Regards
Ajay M

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.

Account Based COPA extraction

Similar Messages

Maybe you are looking for