A/C based COPA extraction - Tables

BW COPA Gurus,
I have a situation and need your suggestion. Recently we generated a A? based COPA data source after the summarization levels were set (KEDU). I do a RSA3 extractor check and end up having 0 records. There are no errors. However, the FI guys sware that they have mor ethan 300 records!! I am not sure which tables to check to verify their claim.
Has anyone experinced this? Which tables should I be checking in R/3 to make sure the data records do exit and to investigate why my extractor fails.
Appreciate your feed back.
Thanks....Chu

Hi,
Can you ask you FI guys to rebuild the summarization levels? Please make sure that this runs during an off-peak time when no one is making any postings, otherwise it will fail.
Can't remember the exact table... look out for something like CEXXXX_. I remember it comes with an extension.
Hope this helps.
Cheers,
Gimmo

Similar Messages

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

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.

Copa extraction and tables read

We want to perform currency translation for a copa extraction. The requirement to determine if translation takes place is currency type, company code and plan/act indicator.
I understand copa dynamically picks which table to read during extraction (I've read the notes).
The problem we face is that CE3 has the plan/act indicator, but no company code. CE4 has company code, but no plan/act indicator.
The only table that has all this information is CE1. How can we be sure all the correct records are translated if it reads from CE3 and CE4?
Our COPA datasource has line item information coming over. So I know it will be reading CE1, but what if it reads CE3 and CE4, this will create inconsistencies??
Thanks,
Mark.

Totalling can be done in reporting.
This is what I think - Since you are extracting line item level data, summarized data can't be extracted at that level as it will be incorrect( a total getting repeated for each line). If you have chosen even a single line item characteristic, summary level values can't be included in the datasource.
When you run a query, you have all the option to see the totals in various ways based on the line item level values.

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

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

BW - COPA extraction requirements for account based and costing based

Our client has a requirements of having both account based and costing based BW extraction from ECC.
Is it recommended? if yes, how does it effect BW data model?

Hi Ali Khan,
Kindly have a look at below link,
http://sap.seo-gym.com/copa.pdf
yes it's possible and it will not affect BW.
Hope this helps.
Regards,
Mani

COPA Extraction-Characteristics value not appearing in RSA3

Hi All,
We have developed Costing based COPA DataSource in KEB0 based on our operating concern. Included all standard fields(Characteristics from the segment level, Characteristics from the segment table, Characteristics from the line items, Value fields) in data source.
When we do extract data in RSA3, All the key figure value fields are appearing correctly but I cannot see any Characteristics values. all the characteristic value appearing blank value.
I have checked everything is active and all (CE1 **** ,CE2 and CE4) tables have data with characteristics and value fields .
My questions are:
1)why COPA characteristics value are not coming in RSA3?
2)what do I need to get this work?
I hope it helps. let me know if you need more further details
Thanks,
L.Prathap

Hi,
Worked on CO-PA but never got such an issue..........
Do you have any of the chars selected from the line items section other than rec_waers?
Also check if you have any summarization levels...transaction KEDV. If no other char from the line items are selected, data could be read from the summarization levels.
There would be 2 tables for a summarization level...key table and the totals table. Check what chars are selected in the key table.
http://help.sap.com/saphelp_470/helpdata/en/7a/4c40794a0111d1894c0000e829fbbd/content.htm
Edited by: Murali Krishna K on Mar 8, 2011 3:32 PM

COPA Extraction

Hi Friends,
Im new2 BI7.
1)Plz provide detailed info on hw 2 go abt for COPA extraction.
2)I need 2 make Customer specific Datasources.So plz guide on this
3)Since my existing Copa reps r frm Report painter/Abap,they just drill down 2 multiple screen,,Is multiple drill down functionality possible in BI?If so plz provide details on hw to make sample drill report.
4)Wat are the crucial steps to take in Copa extraction.
Plz provide any links/ppts/pdf's.
It vll be highly appreciated.
Thanks & Regards.

CO-PA:
CO-PA collects all the OLTP data for calculating contribution margins (Sales, cost of sales, overhead costs)
CO-PA also has power reporting tools and planning functions however co-pa reporting facility is limited to
          Integrated cross-application reporting concept is not as differentiated as it is in BW.
     OLTP system is optimized for transaction processing and high reporting work load has negative impact on the overall performance of the system.
Flow of Actual Values:
During Billing in SD Revenues and Payments are transferred to profitability segments in Profitability Analysis at the same time sales quantities are valuated using standard cost of goods manufactured.
In Overhead cost controlling primary postings is made to objects in overhead cost controlling and assigned to relevant cost object. Actual cost of goods manufactured also assigned to cost objects and at the same time performing cost centers are credited
The Production Variances calculated for the cost objects i.e. the difference between the actual cost of the goods manufactured and the standard costs are divided into variance categories and settled to profitability segments (example production orders).
What are the top products and customers in our different divisions. This is one of the typical questions that can be answered with CO-PA Module.
Characteristics are the fields in an operating Concern according to which data can be differentiated in Profitability Analysis.
Each characteristic in an operating concern has a series of valid characteristic values.
Profitability is a fixed combination of valid characteristic values.
Characteristics:
Some Characteristics are predefined in Operating concern like Material, Customer, and Company Code. In addition to these fixed characteristics we can define up to 50 characteristics of our own. In most cases we will be able to satisfy our profitability analysis requirements with between 10 to 20 Characteristics.
Value Fields:
Key Figures like revenue, cost of goods sold, overhead costs are stored in value fields.
Organizational Structure:
The Value fields and Characteristics that are required to conduct detailed analysis vary from industry to Industry and between Individual Customers.
In CO-PA we can configure structure of one or more operating concerns in each individual installation.
An operating concern is an Organizational Structure that groups controlling areas together in the same way controlling areas Groups Companys together
Data Base Structures in CO-PA:
Actual Line Item table:      CE1xxxx
Plan Line Items: CE2xxxx
Line Item Contain some information at document level that most cases is too detailed for analysis example CO-PA Document Number, Sales document Number, Posting date.
CO-PA Maintains summarization of data used by all CO-PA functions like reporting, planning, assessments, settlements and so on.
Actual Line Item table:      CE1xxxx
Plan Line Items: CE2xxxx
Line Item Contain some information at document level that most cases is too detailed for analysis example CO-PA Document Number, Sales document Number, Posting date.
CO-PA Maintains summarization of data used by all CO-PA functions like reporting, planning, assessments, settlements and so on.
Segment Table: CE4xxxx
The Characteristics that describes the market are first separated from the rest of the line Items.
Each combination of characteristic vales is stored in profitability segment number. The Link between the profitability segment number and characteristic values is maintained in Segment Table.
Segment Level: CE3xxxx
The Value fields are summarized at profitability segment and period levels and stored together with these fields in Table CE3xxxx.
This table contains total values of the period for each Profitability segment number.
Storage Procedure:
We can compare an operating Concern associated by segment table and segment level to an Info cube. Info cube comprises Dimension Table Segment Table) and the fact table (Segment Level).
Unlike Fact table the segment level key contains other keys like processing type in addition to the key field from the segment table.
Characteristics in Info Cube correspond to characteristics (Or Attributes) in Info Cube.
Value fields can be regarded as a Key Figures.
Summarization level in Operating Concern have the same function as aggregates for an Info Cube, the difference is that aggregates for Info Cube are managed together with the Info Cube Itself while summarization levels are updated at regular intervals usually daily.
Line Items in CO-PA is comparable with Operational Data Store
Data Staging Overview:
To Provide Data Source for BW all CO-PA Data Sources must be generated in the Source System.
Data Sources can be defined at Operating Concern and client level.
Data Source contains the following Information
Name of the Operating Concern
Client
Subset of the Characteristics
Subset of the Value fields
Time Stamp which data has already been loaded in to BW.
Creating Data Source:
Since Data Source is always defined at operating concern and Client levels a standard name is always generated which starts with 1_CO_PA_<%CL>_<%ERK . We can change this name if necessary however the prefix 1_CO_PA is Mandatory.
Data Source-Segment Table:
Characteristics from the segment table are the characteristics that are maintained in transaction KEQ3.
By Default all characteristics are selected.
Data Source-Accounting Base:
When we generate CO-PA Data Source select accounting based option.
Fields KOKRS, BUKRS, KSTAR are compulsory.
There are no Characteristics available for line Items because accounting based data sources do not contain characteristics.
There are no value fields or calculated key figures available
KOKRS and PERIO must be selected as selection fields.
Hope it will helps you........

COPA EXTRACTION---BASICS TO ADVANCE

HI GURUS,
I AM NEW AND PRACTISING COPA EXTRACTION.
SORRY I AM EDITING IT FOR MORE CLARITY.
I KNOW THAT THEIR R
CHARCTERSTICS
CHARCTERSTICS VALUES
VALUE FIELDS
SEGMENT LEVEL
SEGMENT TABLE
HOW THEY R LINKED TO EACH OTHER-- BECOZ WHEN I COMPLETE THE SELECTION -
THEY ALL APPEAR IN ONE GROUP --AND HOW TO MODEL A INFOCUBE (DO WE NEED TO GO BACK TO R/3 TO CHECK.)
ON R/3 SIDE-- WHEN WE DEFINE COPA DATASOURCE WE DO AT OPERATING CONCERN LEVEL...RIGHT??
I WANT TO KNOW WHEN DEFINING WE DO SOME SELECTION OF
CHARCTERSTICS FROM THE DATA SOURCE...WHAT IS THAT BASED
ON WE HAVE TO DO OUR OWN ANALYSIS R ELSE ....THE CLIENT
WILL BE GIVING THE REQUIRED SELECTION .CRITERIA.
SORRY ONCE AGAIN FOR POSTING CONFUSED MSSG I AM DESPARATE TO UNDERSTAND THIS....PLZ TRY TO UNDERSTAND AND HELP ME.
Message was edited by: neelkamal moganti
Message was edited by: neelkamal moganti

If i've understood now you have to link your datasource to the infosource and then create the infopakage; there you can find selection criteria.
Regards

Want to update data in a view based on multiple tables

Hi
I am facing a problem i want to update data in tables using a view. As that view is based on multiple tables so i am unable to update data. i came to know we can update table from view only if view is based on single table. so if anyone knows any alternative please let me know.
Thanx
Devinder

Devinder,
The table can be updated through a view based on multiple tables, if and only if the table is a "key preserved" table. Rather than explaining myself, i avoided the burden of typing by finding the material in Oracle Docs and pasting it for you :-)
If you want a join view to be updatable, all of the following conditions must be
true:
1. The DML statement must affect only one table underlying the join.
2. For an INSERT statement, the view must not be created WITH CHECK
OPTION, and all columns into which values are inserted must come from a
key-preserved table. A key-preserved table in one for which every primary
key or unique key value in the base table is also unique in the join view.
3. For an UPDATE statement, all columns updated must be extracted from a
key-preserved table. If the view was created WITH CHECK OPTION, join
columns and columns taken from tables that are referenced more than once
in the view must be shielded from UPDATE.
4. For a DELETE statement, the join can have one and only one key-preserved
table. That table can appear more than once in the join, unless the view was
created WITH CHECK OPTION.
HTH
Naveen

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.

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

Cost Based COPA

Hello Experts,
I am reviewing this document and there seems to be a daily feed from R3 into a BW Cost Based COPA.
When I read Cost Based, the first question in my mind was that there much be other options and cost based was selected.
If so what are the other options which could have been selected, and what are the implications of selecting cost based over the others.
I will appreciate if you could share your thoughts with real life examples to help me understand what may be going on in R3 and what may be coming to BW, and why?
Please mention any helpful transaction codes on the BW or R3 side related to this explanation.
Thanks

Which datasources are you interested in...?
Depending on what your users need, two datasources come to mind.
0CO_OM_OPA_6 and 0CO_OM_CCA_9.
OPA_6 is for internal order based cost collection.
CCA_9 is for cost center based cost collection.
Both extract transaction level information from COSP, COEP, etc..... it just depends on how your company uses internal orders or cost centers for cost collecting.
For collecting costs, these are really very key datasources for determining budget vs actuals information.
Hope this helps...
/smw

A/C based COPA extraction - Tables

Similar Messages

Maybe you are looking for