Regarding COPA extraction

Hi All,
We have created a datasource for COPA(Account Based), used generic InfoCube, replicated DataSources and created TR and UR.
The data is available in R/3. But when we are checking the data in RSA3. Obviously, we are unable to extract the data to BW. Can anybody provide us with a solution for this situation.
Regards
YJ

Hi PRK,
First of all thank you for your interest.
Let me explain you clearly:
When I am extracting the data using Extractor Checker, first I am receiving the following error:
'Make an entry into all the required fields'
Next I entered the values for 'Controlling Area', 'Company Code' and 'Period/year'(I had entered the correct date format).
Next I am receiving the following error:
'Errors occured during extraction'
I will be thankful for your help.
Regards
YJ

Similar Messages

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 issues - Incorrect field name for selection

Dear gurus,
I've issues with my COPA extraction, hope you guys could give me some clue here, point will be rewarded if I could fine the solution.
Requirement:-
To add additional field.
Step:-
As usual 1) Delete
2) Create back with select the new field. (KEB0)
3) Do not have issues when check RSA3 from DEV, but when transport to QAS I hit this issues.
Issues:
At RSA3 , when do check hit the error, "Errors occurred during the extraction"
When check from RSA3 log here I get..
** Did try to find any solution in SCN forum, with no luck. Hope get some help here.
thank you
rgds
Edi.

Yes I did get this feedback ..
Hi Edi,
As per the standard SAP, once you have assigned characteristics and values fields to your operating concern (KEA0), you can't de-assign them. When characteristics or values fields are in assigned status, you can't delete them.
But I hope there won't be much problem of having that characteristic also. If you look at performance wise, then instead of deleting, make "not used" under profitability segment characteristics, remove from the characteristic groups etc. While doing so, please check any derivation rules written based on these, or any assessment cycles defined with these also..
Regards...
Jose
forward to my FICO ..

Difference between LO and COPA Extraction and Steps

Hello All,
Can you please share the COPA extraction steps and also advise why COPA is differnt from other extraction (e.g.LIS/LO etc.) mechanisms?
And also advise what should be my aproach for any COPA extraction related reporting projects.
Thanks,
Mainak

Hi Mainak,
COPA Extraction -steps
R/3 System
1. KEB0
2. Select Datasource 1_CO_PA_CCA
3. Select Field Name for Partitioning (Eg, Ccode)
4. Initialise
5. Select characteristics & Value Fields & Key Figures
6. Select Development Class/Local Object
7. Workbench Request
8. Edit your Data Source to Select/Hide Fields
9. Extract Checker at RSA3 & Extract
BW
1. Replicate Data Source
2. Assign Info Source
3. Transfer all Data Source elements to Info Source
4. Activate Info Source
5. Create Cube on Infoprovider (Copy str from Infosource)
6. Go to Dimensions and create dimensions, Define & Assign
7. Check & Activate
8. Create Update Rules
9. Insert/Modify KF and write routines (const, formula, abap)
10. Activate
11. Create InfoPackage for Initialization
12. Maintain Infopackage
13. Under Update Tab Select Initialize delta on Infopackage
14. Schedule/Monitor
15. Create Another InfoPackage for Delta
16. Check on DELTA OptionPls r
17. Ready for Delta Load
LIS, CO/PA, and FI/SL are Customer Generated Generic Extractors, and LO is BW Content Extractors.
LIS is a cross application component LIS of SAP R/3 , which includes, Sales Information System, Purchasing Information System, Inventory Controlling....
Similarly CO/PA and FI/SL are used for specific Application Component of SAP R/3.
CO/PA collects all the OLTP data for calculating contribution margins (sales, cost of sales, overhead costs).
FI/SL collects all the OLTP data for financial accounting, special ledger
Difference: CO-PA / LIS / LO / FI-SL
1)Method for Delta: Time Stamp / LIS InfoStructure / Change Log / PseudoDelta
2) Application Specific: All are
3) Extractors: Customer Generated (CG) / SAP BW Content / CG / CG
4) Tables Used: Line item tables / 1 structure (s5nn). 2 tables (BWl1 and 2) and control change log (TMCBIW) / V3 update(asynchronous) and two tables: VBDATA and ARCFC (change log from SAP R-3 / Three types of tables - Line Item Tables- ZZP(plan) & ZZA(actual), - Total Table ZZT, - Objects Tables ZZO & ZZC
Pls refer:
http://help.sap.com/saphelp_nw04/helpdata/en/ee/cd143c5db89b00e10000000a114084/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sapportals.km.docs/documents/a1-8-4/how%20to%20set%20up%20connection%20co-pa%20-%20extraction
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sapportals.km.docs/documents/a1-8-4/how%20to%20set%20up%20connection%20co-pa%20-%20retraction
Differences between LIS,LO,CO/PA and FI-SL extractors
*Pls Assign points if info is useful*
Regards
CSM Reddy

Step by step procedure for copa extraction

hi experts,
            what are the steps involved in copa extraction, please give me step by step procedure for copa extraction.
Thanks,
Rk

Hi Rama Krishna
     COPA STEPS
     SERVER R/3 SERVER  CONTOLLING & PROBALITY ANALYSIS  ENTER COPA WITH T-CODE 9TRANSACTION CODE KEBO)  CREATE (OPERATING CONCERN ; IDEAS (CLICK ON EXCUTE)  ENTER (SHORT TEXT,MEDIUM TEXT,LONG TEXT)  FIELD NAME FROM PERITION ; BURKS  DESLECT SOME VALUE FIELDS  LICK ON CHECK BUTTON  CLICK ON SUMMATIATION LEVEL CLICK ON INFO CATALOG  IT GOES TO ATA SOURE [CUSTOMER VERSION EDIT.  SELECT IN SELECTION , HIDE FIELD  CLICK ON SVE BUTTON  NEXT CLICK ON GENERATE  GO BACK  TO CHECK THE DATA IN COPA DATA SOURCE  T- CODE RSA3 IMP  DATA SOURCE  1-CO PA800 STISH  CLICK ON EXTRACTION.
     SERVER BW SYSTEM  GO TO INFO SOURCE YSTEM  SELECT YOUR SOURCE SYSTEM  DOUBLE CLICK ON SOURCE SYSTEM  SELECT BW DATA SOURCE  SAP APPLICATION COMPONENTS  CONTROLLING  PROFITABILITY ANALYSIS  RIGHT CLICK  REPLICATE DATA SOURCES  ELECT COPA DATA SOURCE (R.C)  SELECT REPLICATE DATA SOURCE  DOUBLE CLICK ON DATA SOURES  APPLICATION PROPOSAL  1-CO-PA800 SATISH  CLICK ON TRANSFER BUTTON  YES  PROPOSE TRANSFER RULES  IF WARNING OCCURS SAY CONTINUE  ACTIVATE  GO BACK  CREATE INFO AREA  INFO PROVIDER  CREATE INFO CUBE  INFO SOURCE  1-CO PA8000SATISH  CREATE UPDATE RULES  GO BACK TO INFO SOURCES  REFERESH  FIND THE 1-CO-PA800  PC ON SOURCE SYSTEM AND CREATE INFO PACKAGE  SCHEDULER  MONITOR.
Regards
Ashwin

Regarding Generic Extraction

Hi Experts,
I m new to SAP BW, I need a information regarding Generic Extraction as the senario is follows.
I created a table with fields,
Customer Id (PK), name, age ***, address
and i maintained five records in it.
i created a generic master data attributes data source using above table
i replicated the data source in bw and run the full update and it is succussful.
Now my requirement is to add 5 more records in the above table and i hav to get those records in bw using delta update.
So, can any one can explain how to maintain delta for that generic datasource and how to run delta update in step-by-step process
regards,
Ramakrishna

Check the PDF doc..on how to create generic delta..
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
Check this doc for more
http://www.ko-india.com/content/weblogs/generic_delta_explained.pdf
Regards,
R.Ravi
Assigning Points is the way of saying Thanks in SDN!

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

Regarding CRM extraction.....

Hi Gurus,
I have few questions regarding CRM extraction.
Q1: If we enhance a CRM transactional Datasource, do we have to write the ABAP logic in SE19 or CMOD or both?
Q2: If we enhance a CRM MasterData Datasource, do we have to write the ABAP logic in SE19 or CMOD or both?
Q3: What is the significance of the T-CODES BWA1, BWA5, BWA7 ?
Q4: When do you implement the BADI CRM_BWA_MFLOW and when do we implement the BADI CRM_BWA_SFLOW and when do we implement both of them?
Q5: What is the significance of the function module CRM_BADI_GET_BDOC? Is there any other function module which is used in CRM extraction that has to be implemented in coding?
Please throw some light on my questions.
Thanks
Nice day
Regards
Sam

HI,
For Delta Extraction of CRM to BI pelase follwo the below steps
Go to transaction GNRWB
Select BUS_TRANS_MSG
Select (on the right, the services): BWA_DELTA3, BWA_FILL, BWA_queue
Press Generate.
Also check for the following:
1. The delta should have been initialized successfully.
2. Confirm that all Bdocs of type BUS_TRANS_MSG
are processed with success in SMW01.
3. If there are queues in SMQ1 with erroneous status then activate
these queues.
In Transaction SMQ1 if there are Queues existing with
names beginning with CRM_BWAn (n is number) then
activate these queues in the same transaction.
4.a)If required activate the datasource
Go to transaction BWA5 > select the required datasource and
activate.
4 b) The Delta may not be active ,activate the delta in BWA7 by
selecting the name of the datsource and pressing the candle icon for
'activate delta'.
5. In BW system
Go to transaction RSA1 > modeling > infosources > select the
info source > right mouse click on the selected
infosource > choose option replicate datasource
Activate the infosource.
6. Go to the scheduler for the infosource > select delta in the
update >choose the option PSA only (in the Processing tab)
start immediately
Check the entry in the RSA7 in the OLTP(CRM system)
Hope It helps You.
Regards,
Nagaraju.V

Regarding copa

Hi All
Experts.. & PradipPatil
I am Having Doudts Regarding Copa
what Is Accout Based Copa and Costbased Copa ?
Wht the main diffrence between Them ?
In which Scenerion We will choose Accunntbased & costbased
Please Clarify Me
I had Studied some docs Related that Stil have some confuision.
cheers
Purushottam
Points will be Assigned

Hi ,
COPA Accounting based is for seeing at abstract level
COPA costing based is the detailed level,
90% we go for costing based only
COPA Accounting is based on Account numbers,
COPA Cost accounting is based on cost centers.
Renjith

OSS note regarding 0EC_PCA_3 extraction optimization

hello Frnds,
We are facing severe Data load issues with a load from 0EC_PCA_3 in production,
Could any one suggest OSS note regarding 0EC_PCA_3 extraction optimization
Thanks in Advance
raky

Rakesh
Also check this for General BW related Performance issues
Business Intelligence Performance Tuning [original link is broken]
Thnaks
Sat

Regarding LO Extraction

Hi All,
This is regarding LO Extraction.
The steps that I am following are first installation of Business Content InfoCube. Next identified the data sources in LBWG I deleted the data from setup tables for that particular application.
In a broad way how to extract the deltas from now on.
We will do the time setup in 0LI*BW. Next we set the time in Job Control and then again in BW side we can set the time in InfoPackage.
What is the best practice to follow to extract deltas?
I am having all the materials and Links regarding LO.
But I am not clear on this point. Someone please guide me regarding this issue.
Regards
YJ

Jayanth
Check this sequence. Hope this helps. Also check these weblogs.
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/u/21406 [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken]
Also refer this link:
http://www.sap-img.com/business/lo-cockpit-step-by-step.htm
Thnaks
Sat
LO EXTRACTION
- Go to Transaction LBWE (LO Customizing Cockpit)
1). Select Logistics Application
SD Sales BW
Extract Structures
2). Select the desired Extract Structure and deactivate it first.
3). Give the Transport Request number and continue
4). Click on `Maintenance' to maintain such Extract Structure
Select the fields of your choice and continue
Maintain DataSource if needed
5). Activate the extract structure
6). Give the Transport Request number and continue
- Next step is to Delete the setup tables
7). Go to T-Code SBIW
8). Select Business Information Warehouse
i. Setting for Application-Specific Datasources
ii. Logistics
iii. Managing Extract Structures
iv. Initialization
v. Delete the content of Setup tables (T-Code LBWG)
vi. Select the application (01 Sales & Distribution) and Execute
- Now, Fill the Setup tables
9). Select Business Information Warehouse
i. Setting for Application-Specific Datasources
ii. Logistics
iii. Managing Extract Structures
iv. Initialization
v. Filling the Setup tables
vi. Application-Specific Setup of statistical data
vii. SD Sales Orders Perform Setup (T-Code OLI7BW)
Specify a Run Name and time and Date (put future date)
Execute
- Check the data in Setup tables at RSA3
- Replicate the DataSource
Use of setup tables:
You should fill the setup table in the R/3 system and extract the data to BW - the setup tables is in SBIW - after that you can do delta extractions by initialize the extractor.
Full loads are always taken from the setup tables
The Lo-cockpit procedure is go with LBWE Transaction
so that you can get Applications 02,03,...etc
Under that you have
Extract structures
select your data source here Be sure that First you InActive that Then go with LBWG "Delete setup data"
here you can give the application No example 02(if your application is Purchages)
then once again LBWE go with Maintanace Tab select your Fields then your Datasource is Active position then You have to Fill the Data
go with OLI*BW for example if your application is Purchages then OLI3BW
then go with Extractor Checker RSA3

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.

Help Regarding Generic Extraction

Hi Experts,
I m new to SAP BW, I need a information regarding Generic Extraction as the senario is follows.
I created a table with fields,
Customer Id (PK), name, age ***, address
and i maintained five records in it.
i created a generic master data attributes data source using above table
i replicated the data source in bw and run the full update and it is succussful.
Now my requirement is to add 5 more records in the above table and i hav to get those records in bw using delta update.
So, can any one can explain how to maintain delta for that generic datasource and how to run delta update in step-by-step process
regards,
Ramakrishna

Hi Ramakrishna,
For doing a delta on a generic extractor you will have to set up any one of the following type of the field as delta attribute and on the basis of this delta records will be extracted.
- Time Stamp
- Calendar day
- Numerical Pointer (i.e. Document Number)
You can monitor your delta queue via RSA7 transaction.
Also For delta you will have to do Init load first.
Hope that helps.
Regards.

All About COPA extraction and business view

Hi All,
I have gone through lots of questions posted in this forum about the functionla side of COPA and also on extraction side. Is there any document( preferably a pdf) where I can find all the info in one document about COPA functional aspects .
Thanks in advance.
Regards
Srini

Hi Srinivas,
Give us ur mail ID, i can send u one doc.
Re: COPA R/3 vs BW(aCCOUNT BASED-PA)
One of the differences between account based CO-PA and costing-based CO-PA that there is no delta extraction. There is also 1 other rule. You can only select 1 fiscal-period. The set-up is similar to costing based CO-PA.
The big difference between Account Based CO-AP and Costing Based CO-PA is of course the data is stored in the CO Modules.
Account based CO-PA is part of the CO concept. This means when you post to a cost element the data is posted to a CO-module (CCA, OPA, PA, PS etc). The way the data is stored is also different from costing based PA.
The CO tables like COEP, COBK (for the individual item are used and the COSS and COSP are used for the totals.
The object where the posting are related to they are stored in the CE4... table. So if you want to analyse the data there is 1 keyfigure and the cost-element is a characteristic (account model).
COsting Based CO-PA data is statistical data. This means that the update of CO-PA is not always equal to what is stored in the CO modules or in finance. The cost element is also not always updated and there are also more key-figures used to store info about the type of costs or revenues. Tables as CE1, CE2 , CE3 and CE4 are used.
Extraction for Account Based CO-PA is only based on the total records (full loads are only possible). For costing based CO-PA there it is possible work with init and delta packages and also to select data from the individual postings databases (CE1, CE2).
The way you generate the extractor is similar.
Hopelfully this gives you a bit more background of the CO-PA module.
Assign points if it helps..
Regards,
ARK

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

Regarding COPA extraction

Similar Messages

Maybe you are looking for