Based on R/3 Extraction

1.  Different kinds of extractors:

LO Cockpit Extractors are SAP standard / pre-defined extractors / Data Source for loading data to BW.

COPA- is customer generated application specific Data Source. When we create COPA Data Source we will be getting different field selections. There are no BI cubes for COPA.

Generic Extractor: We create generic extractors from table views, query and functional module / InfoSet Query.

2. What's the difference between extraction structure and table in datasource?

a) The extraction structure is just a technical definition, it does not hold any physical data on the database. The reason why you have it in addition to the table/view is that you can hide deselect fields here so that not the complete table needs to be transferred to BW.

b) In short - The extract structure define the fields that will be extracted and the table contains the records in that structure.

c) Table is having data but Extract structure doesn’t have data.
Extract structure is formed based on table and here we have the option to select the fields that are required for extraction. So extract structure will tell what are the fields that are using for extraction.

3. Define V3 Update (Serialised and Unserialised), Direct Delta and Queued Delta

a). Direct Delta: When number of document changes between two delta extractions is small, you go for direct delta. The recommended limit is 10000 i.e. if the No of doc changes (Creating, changing and deleting) between two successive delta runs is within 10000, direct delta is recommended.
Here the number of LUWs are more as they are not clubbed into one LUW.

b). Queued delta is used if number of document changes is high ( more than 10000). Here data is written into an extraction queue and from there it is moved to delta queue. Here up to 10000doc changes are cumulated to one LUW.

c). Unserialized V3 update method is used only when it is not important that data to be transferred to BW in the exactly same sequence as it was generated in R/3.

d). Serialized V3 Update: This is the conventional update method in which the document data is collected in the sequence of attachment and transferred to BW by batch job. The sequence of the transfer does not always match the sequence in which the data was created.

Basic difference is in the sequence of data transfer. In Queued delta it is same as the one in which documents are created whereas in serialized v3 update it is not always the same.

 4) Difference between Costing based and Account based CO-PA

Account based is tied to a GL account posting. Costing based is derived from value fields. Account based would be more exact to tie out to the GL. Costing based is not easy to balance to the GL and more analytical and expect differences. Costing based offers some added revaluation costing features

Implementing costing based is much more work but also gives much more reporting possibilities especially focused on margin analyses. Without paying attention to it while implementing costing based COPA, you get account based with it, with the advantage of reconciled data.

COPA accounting based is for seeing at abstract level whereas costing based is the detailed level, 90% we go for costing based only.

COPA Accounting is based on Account numbers; where as cost accounting is based on cost centers.

COPA Tables: Account base COPA tables are COEJ, COEP, COSS and COSP