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.

Similar Messages

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

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

Maintenance view: how to read EXTRACT and TOTAL table

Hi, All,
I created a maintenance view, as stated in the documentation, there are 2 internal tables EXTRACT and TOTAL available in running environment. Now I want to read a record from the internal table by using "READ TABLE...."
In my example: the table strucutre has A, B, C 3 fields.
So I tried to use "READ TABLE EXTRACT with key A=' xyz' assigning <fs>", in this case, the syntax check shows error saying that the specified type has no structure and no component can be called.
So how can I search a row in the table EXTRACT and TOTAL by giving a field value? Is there any other way to get data from the table?
Thank you!

Hi Yongying,
I know this is an old post, but, may be this is still helpful for you or for others with the same problem.
Just add the option "CASTING" at the end of your READ statement:
"READ TABLE EXTRACT with key A=' xyz' assigning must be full typed or at least, be of the same type of the Z table from which is generated the itab EXTRACT.
Regards,
José Gabriel.

What are the delta mechanisms and tables used for Lo Extraction & COPA

Hi all
what are the delta mechanisms and tables used for Lo Extraction & COPA.
please explain clealry.
Thanks & Regards,
James

James,
Please go through Roberto's weblog :
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
Anyways,
As you know LO cockpit consists of different modules(MM, PP, SD, etc)
They are called appl components. Each of them have a number (eg.MM=02) and for each appl comp they might be different Data sources and for each DS they might be different tables. So, unless you be specific we cant tell a specific table for a DS.
coming to the delta mechanisms, there are " direct delta, queqed delta and serialized delta".
Copa is based on the oepration concern. it can be created on " accouting based" or "costing based".
Assign points if helpful
Kalyan

When we go for Business content extraction and when we go for LO/COPA etc.e

Hi Dear Friends
When we go for Business content extraction and when we go for LO/COPA etc.extractions
Thanks
Learner

Hi,
It depends on the KPI you are extracting for,if Business Content Extractor provides you with those then there is no need for generic extractors.
In CO-PA the KPI for profitability differs from client to client.You have Business Content for CO-PA also...
Cheers

Why we have setup tables in LO extraction and why not in CO-PA,Generic

Hi Friends
Why we have setup tables in LO extraction and why not in CO-PA,Generic
Please give me reply
****************Points are assured********************
Thanks&Regards
Revathi

Hi Revathi,
Please check the following Threads :
[why set up tables ?;
[Why LO only having Setup tables not Others.......?;
Regards
Hemant Khemani

Most buffer gets and disk reads on table "CRMD_BRELVONAI"

hello friends,
we have to much buffer gets and disk reads on this table. se11 says:
2 indexes on this table:
first:
OBJKEY_A -
Index CRMD_BRELVONAI~1 exist on DB ORACLE
second:
OBJKEY_B-
Index not exist on DB ORACLE
Has anbody created the second index and good experience? OSS has no information.
thanks,
christoph

Ho Christioph,
If you double click on secondary index OBJECT_B you will get to index screen. Note that secondary index OBJECT_B as been set to No database index.
For your information, here is a copy of the related documentation.
Create the index in the database (selection)
Whether an index improves or worsens performance often depends on the database system. You can therefore set whether an index defined in the ABAP Dictionary should be created in the database.
This makes it easier to install a platform-specific customer system.
You can set this option as follows:
Index in all database systems: The index is always created in the database.
In selected database systems: The index is created depending on the database system used. In this option, you must specify the databases in which the indexes are to be created. You can do this either on an inclusive (list of systems on which it should be created) or an exclusinve (list of systems on which it should not be created) basis. In either case, you can list up to four different database systems.
No database index: The index is not created in the database. If you set this option for an index that already exists in the database, it is deleted when you activate the table in the ABAP Dictionary.
Note: Unique indexes have an extra function, and must therefore always be created in the database. The database system prevents entries or index fields being duplicated. Since programs may rely on this database function, you cannot delete unique indexes from the database.
Hopping this answer your question.
Sincerely,
Alain Gauthier

Can you read Reports and Tables through RFCs and BAPIS?

Is there any way to read established reports and tables through RFC or BAPI function calls? We have a middleware that can execute various BAPIs and RFCs. I see a few promising ones: RFC_READ_REPORT, but no examples anywhere what the parameters needed are for the inputs.

Hello Scott,
Check below FMs for reading tables and programs.
Tables : RFC_READ_TABLE
Program : RFC_READ_DEVELOPMENT_OBJECT
Please note that for reading program using RFC_READ_DEVELOPMENT_OBJECT , lines in program should not exceed 72 chars else FM will throw dump(READ_REPORT_LINE_TOO_LONG).
Program code will appear in table QTAB which is 72 chars wide.

Why we have setup tables in LO extraction and why not in CO-PA,Generic,FI-S

HI Friends
Why we have setup tables in LO extraction and why not in CO-PA,Generic,FI-SL. Please clarify.
Thanks&Regards
Revathi
<removed by moderator>
Edited by: Siegfried Szameitat on Nov 13, 2008 12:07 PM

Hi revathi,
The R/3 database structure for accounting is much more easier than the Logistical structure.
Once you post in a ledger that is done. You can correct, but that give just another posting.
BI can get information direct out of this (relatively) simple database structure.
In LO, you can have an order with multiple deliveries to more than one delivery addresses. And the payer can also be different.
When 1 item (orderline) changes, this can have its reflection on order, supply, delivery, invoice, etc.
Therefore a special record structure is build for Logistical reports.and this structure now is used for BI.
In order to have this special structre filled with your starting position, you must run a set-up. from that moment on R/3 will keep filling this LO-database.
If you wouldn't run the setup. BI would start with data from the moment you start the filling of LO (with the logistica cocpit)
I hope I have been clear.
Udo

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

How to set Delta for COPA Extraction

Hi all,
I want to do generic data source using Function Module for COPA can any one tell how to set the delta what fields i have to fill.
thanks
kavitha

Hi kavitha,
The easiest way to work out with Function Module is to copy the standard one and modify according to your reqirement.
The standard one is RSAX_BIW_GET_DATA_SIMPLE .
Dont forget to copy the Function grp RSAX into a custom defined Grp and Modify the Ranges options as per ur req.
and in Function module, in Sourcecode and Tables, Do modify the E_T_data with ur Generic datasource ,make sure u also modify the select statements within the sourcecode. If you have an idea on ABAP its really easy to work out.
And regarding the creation of Datasource.
this blog may help for the same.
Generic Extraction via Function Module
Safety Interval Upper Limit of Delta Selection
This field is used by DataSources that determine their delta generically using a repetitively-increasing field in the extract structure.
The field contains the discrepancy between the current maximum when the delta or delta init extraction took place and the data that has actually been read.
Leaving the value blank increases the risk that the system could not extract records arising during extraction.
Example: A time stamp is used to determine the delta. The time stamp that was last read is 12:00:00. The next delta extraction begins at 12:30:00. In this case, the selection interval is 12:00:00 to 12:30:00. At the end of extraction, the pointer is set to 12:30:00.
A record - for example, a document- is created at 12:25 but not saved until 12:35. It is not contained in the extracted data but, because of its time stamp, is not extracted the next time either.
For this reason, the safety margin between read and transferred data must always be larger than the maximum length of time that it takes to create a record for this DataSource (with a time stamp delta), or it must display an interval that is sufficiently large (for determining delta using a serial number).
Safety Interval Lower Limit
This field contains the value taken from the highest value of the previous delta extraction to determine the lowest value of the time stamp for the next delta extraction.
For example: A time stamp is used to determine a delta. The extracted data is master data: The system only transfers after-images that overwrite the status in the BW. Therefore, a record can be extracted into the BW for such data without any problems.
Taking this into account, the current time stamp can always be used as the upper limit when extracting: The lower limit of the next extraction is not seamlessly joined to the upper limit of the last extraction. Instead, its value is the same as this upper limit minus a safety margin. This safety margin needs to be big enough to contain all values in the extraction which already had a time stamp when the last extraction was carried out but which were not read. Not surprisingly, records can be transferred twice. However, for the reasons above, this is unavoidable.
these are used to determining the delta in a datasource:
1. Time stamp - The field is a DEC15 field which always contains the time stamp of the last change to a record in the local time format.
2. Calendar day - The field is a DATS8 field which always contains the day of the last change.
3. Numerical pointer - The field contains another numerical pointer that appears with each new record .
Regards,
Anish

Keyfigures source field and table in R/3

Hi,
Can anyone suggest or send what are source field and table in R/3
Serv. Hrs     Serv.@BR     Serv.Disc.     Adjustments     NSR     Calc. Disc.     NSR/Hr     "Prior Yr
Serv. Hrs"     "Serv Hrs
Variance"     "Serv Hrs %
Variance"     "Prior Yr
NSR"     "NSR
Variance"     "NSR %
Variance"     "Prior Yr
Calc. Disc."     "Calc. Disc
Variance"     "Prior Yr
NSR/Hr"     "NSR/Hr
Variance"     "NSR/Hr
Variance %"     Net Services AP     Calc.Disc. AP     Std Rate AP     Rev/Hr AP     Expenses Incurred AP     Hours YTD     Gross Serv. YTD     Net Services YTD     Calc.Disc. YTD     Std Rate YTD     Rev/Hr YTD     Expenses Incurred YTD     Hours LTD     Gross Serv. LTD     Net Services LTD     Calc.Disc. LTD     Std Rate LTD     Rev/Hr LTD     Expenses Incurred LTD     "Equalization
Adjustment
AP"     "Unbilled
Adjustments
AP"     "Closeout
Adjustment
AP"     "Total
Adjustments
AP"     Unbilled Adjustment     Close-out Adjustment     Other Adjustments     "Net Rev
Actual"     "Net Rev
Plan"     "Net Rev
M(L) Plan"     "Net Rev
Prior"     "Net Rev
M/(L) Prior"     "Net Rev
Growth Rate"     "Net Rev
Period Plan"     "Net Rev
Remainder
to Achieve
Plan"     "Net Rev
% of Plan
Achieved"     "Prior Year
Period %
Net Rev"

Dear Sridhar,
Are you dealing with DataSource to extract data ?
If so...
gotoST05
Switch on the SQL Trace
Come to RSA3
Execute your DataSource
Goto ST05
Swicth off the Trace
Analyze Trace File...u will get the Table and Field names..
Regards,
Ram.

When we go for view ,fm,infosetquery,and tables

Hi Masters,
1)when we go for view ,fm,infosetquery,and tables ?
& how to create view ,fm,infosetquery,and tables ?
2)what is user of numeric pointer?
3)what is different between view ,fm,infosetquery,and tables ?
4) what is user of view ,fm,infosetquery,and tables ?
please help on this issue by give good understading answer

Hi Kumar,
1. Maintaining Generic DataSources.
http://help.sap.com/saphelp_nw04/helpdata/en/3f/548c9ec754ee4d90188a4f108e0121/frameset.htm
Create View:
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ecf9446011d189700000e8322d00/frameset.htm
Create FM:
http://help.sap.com/saphelp_nw04s/helpdata/en/9f/db98fc35c111d1829f0000e829fbfe/frameset.htm
Create Table:
http://help.sap.com/saphelp_nw04/helpdata/en/87/773a55f35a65409009e87261c84eb2/frameset.htm
Create Infoset query:
How to create infoset query
what is an infoset and infoset query?
Create Generic Delta:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
2. Numeric pointer:
Generic Delta with Numeric pointer.
Generic Delta Extraction
Delta specific fields
You can have the differences and the uses of View, FM, Infoset query and table from above links itself.
Hope these helps u...
Regards,
KK.

Required Field name and Table name

Hi All,
My customer is extracting DATA from SAP and send it to Oracle. In oracle we have 3 fields
1. Unapplied Amount: means for example, there is a invoice for $50.00 and customer sends the payment of $100.00, so customer paid $50.00 extra, this $50.00 will be called as a Unapplied amount.
2. DEPOSIT DATE : Now the day when the customer sends the payment will be called DEPOSIT DATE
3. GL_DATE: On the day when invoice gets cleared and updates the GL, will be called as GL_DATE
If any one has any idea regarding the above fields and tables please let me know.
Thanks & Best Regards
Shashi
Edited by: shashi mantripragada on Mar 17, 2011 2:55 PM

hello,
if i am right in understanding your question, then you wanted to know the technical details about the project number or should i say project id, from which wbs elements are created, on which we finally place the orders.
if this is what you want, then for getting the prject number for a particular order, at the table level, follow the below steps -
using the po number or order number as an input in ekkn table, along with the po line item, you will get the wbs element for the order number for that particular po line item.
and using this wbs element as an input in prps table, you can find the current project number.
finally using this current project number as an input in the table proj, you can find the project id or project number = proj-pspid
so you will require 3 tables to get the required details.
hope this helps you.
Regards,
Zafar.

Copa extraction and tables read

Similar Messages

Maybe you are looking for