CO-PA Account Based - Summarization built but no records!

Our CO-PA AB extractor has not been functional for a while in test. Production is fine. To remedy, the R/3 folks have rebuilt the summarization levels. Ran for 3 days but finished OK. The status is now "Active". In the details screen the K8XXXXX tables - Key and Totals - have records. The Build panel has a record count but the Update panel has 0 records. RSA3 to check the extractor brings back nothing - times out. Running an infopackage - first replicating the datasource and reactivating TRs - still no records. Has anyone run into this before? Is there another step? Or another setting after the summarization runs that we have missed? Do records need to built for the Update panel - is that done through KEDU? Any help would be much appreciated. Thanks. Don

Ravi - Thanks. The R/3 system (F) that feeds the dev BW enviroment is not modifiable so I would have to get it opened for this but it brings up an issue. Our company has R/3 D and Q systems but we are not connected to them for data. Extractor enhancement is done in D then moved quickly thru Q and then to F for testing. (Yes, the R/3 transport person is always complaining). There are some minor enhancements to this extractor that are waiting to move to F for testing - once we get data. I assume re-generating the datasource will have no impact on the transport moving through with those enhancements. Please let me know if that needs clarification. Thanks again.

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.

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.

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

COPA Account Based Problem

Dear All,
I had created two DataSource for COPA one is Cost Based and another is Account Based using T-code KEB0 in R/3 Dev. I can able to see the data in RSA3 for Cost Based but when come the Account Based it is giving "Error Occured during the extraction" (When i get into the Help -During the extraction phase an error occurred for the extractor. An exception, 'error_passed_to_mess_handler' was triggered.-).
Could any one please help me in creating of COPA Account Based, and please do help me in some notes.
Thanks in advance,
Prashanth

Hi all,
the solution is:
the extractor needs a summarization level in CO-PA --> see OSS 392635 (TC KEDV).
After Creation of this level you have to build new level (TC KEDU) --> fill with data.
After this you have to create the datasource CO-PA.
Notice: lucky time entry: e.g. 2005.001 in RSA3, RSA6
Questions remains: why does this information/hint (sum. level missing?) is not included in the error message.
Dieter

COPA Account based extraction error

We have an account based COPA Datasource modified to add another characteristic.
All the pre-reqs involving this re-generation( new characteristic in same operating concern) have been done by R/3 consultant. During Transport, it works fine in all instances but production. All the R/3 checks(KEDV,KEB0 ...) have been performed and summarization levels have been generated. In BW everything is in order, but when trying to load data(full load) it fails with zero records. The error message is
"No source could be found to answer the search query"
Any thoughts?
Thanks!

Thanks Sam for your answer.
The R/3 functional consultant confirms that the summarization levels are generated properly and nothing seems to be amiss there.
Is there a SAP note on this?
Thanks for your answers . Any more thoughts ?

Customizing CO-PA Account-Based Extractor

A requirement exists to customize our Account-Based CO-PA extractor. The Costing-Based extractor has been customized/appended but some team members have suggested that AB-PA extractor should not be. These would all be characteristics. Is there a problem with adding fields to this extractor - and if so, why? Any differences from adding to the Costing-Based? Thanks.

Don,
CE1 and CE2 tables are the ones to store actual line items and plan line items. I am pasting the relevant para from SAP help at the bottom of my msg.
Reg your other question, what level of summarization your users are talking about?
Ravi Thothadri
Physical Structure of the Data in CO-PA
The following sections describe the detailed physical structure of the data (physical insertion sequence) and the typical accesses of the dataset.
In the section Physical Distribution of the Data in CO-PA, we will propose a way to distribute the data effectively over larger areas (table spaces, hard drives, striping, and so on).
Documents
Actual line items are stored in table CE1xxxx (where xxxx = operating concern). The system inserts into this table on an ongoing basis (sorted according to time stamp of the insertion point).
In drilldown reporting, cost center assessment, etc., the system accesses the data by this time stamp. Thus the physical insertion sequence corresponds to the typical read access method.
Plan line items are stored similarly in table CE2xxxx and are accessed in the same way. Consequently, this table will not be referred to separately in the following.
Segment Level
The segment level -- CE3xxxx -- contains the data in its first summarized form. The profitability segment number and the period are key fields (along with additional technical fields: plan version, record type, plan/actual indicator, etc.). The data part consists of the value fields.
The data in the segment level is typically sorted by period when it is created (INSERT) and updated during the period. That is, the insertion sequence depends on the random order in which the business transactions occurred and is only sorted roughly according to period (or period block PERBL).
The typical queries search in the segment level with a few (approximately 100) fixed segment numbers (WHERE PAOBJNR IN <List> ...) and a condition of time (... AND PERBL IN ...). Thus the physical insertion sequence does not correspond to the typical read access sequence! The segment level is always accessed via the primary index CE3xxxx__0.
Segment Table
The segment table CE4xxxx contains a unique profitability segment number (the primary key) for each combination of characteristic values (data part) to which data has been posted.
The records are inserted in the order of the profitability segment numbers (albeit only approximately, due to buffering of the segment number assignment on the application servers) and are practically never changed.
Selections from the segment table can generally be divided into two groups:
Selections of large data volumes for drilldown reporting, planning or cost center assessment
Here the system finds all the profitability segment numbers whose combination of characteristic values meets a specified condition (e.g. in a drilldown report). If a suitable index exists, the system uses it to access table CE4xxxx. In that case the access does not correspond to the physical insertion sequence. If no suitable index exists, the system selects using the primary index. To read about how you can improve performance for this type of access, see Physical Distribution of the Data in CO-PA.
Determination of a profitability segment number based on the known combination of characteristics
In this case the system finds the profitability segment number when the values of all characteristics are known. To read about how you can improve performance for this type of access, see Index Support for Determination of Segment Numbers.

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

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

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 CO-PA Quantity Not updated in COEP-MEGBTR

Hello,
We use account based CO-PA. For certain Billing transactions, the quantity is not coming to the BW.
On analysis, we notice that the line item document created in COEP table is not updating the quantity field MEGBTR but only the field MBGBTR.
Not sure what is cuasing these transactions to post differently.
Thanks for your help. Murali

Could you please check note 105747, 911203, 353643 or 188724, This does not pertain to ECC6 but possibly earlier releases.

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.

CO-PA Account Based - Summarization built but no records!

Similar Messages

Maybe you are looking for