Professional Documents
Culture Documents
BW HowTo - COPA - Extraction PDF
BW HowTo - COPA - Extraction PDF
CO-PA Extraction
BUSINESS INFORMATION WAREHOUSE
SAP (SAP America, Inc. and SAP AG) assumes no responsibility for errors or omissions in these materials.
These materials are provided “as is” without a warranty of any kind, either express or implied, including but not limited to, the implied
warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that
may result from the use of these materials.
SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these
materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and
does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages.
mySAP BI “How-To” papers are intended to simplify the product implementation. While specific product features and procedures
typically are explained in a practical business context, it is not implied that those features and procedures are the only approach in
solving a specific business problem using mySAP BI. Should you wish to receive additional information, clarification or support,
please refer to SAP Professional Services (Consulting/Remote Consulting).
HOW TO … CO-PA EXTRACTION
The following steps are not performed in the OLTP system, but instead in the SAP BW system (in the
Administrator Workbench, transaction RSA1).
For extractions from account-based CO-PA, only update mode Full Update from summarization levels is
supported for releases up to and including Release PI2001.1. From Release PI2001.2, the delta method can also
be used. The initialization must still be performed from a summarization level. The subsequent delta updates then
read the line items.
For data to be read from a summarization level, the level must also contain all the characteristics that are to be
extracted using the DataSource (entry * in maintenance transaction KEDV). Furthermore, the summarization
must have status ACTIVE.
In the case of DataSources for costing-based CO-PA, data can only be read from a summarization level if no
characteristics of the line item are selected apart from the Record Currency (REC_WAERS) field, which is always
selected.
An extraction from the segment level, that is, from the combination of the tables CE3XXXX / CE4XXXX (where
XXXX stands for the operating concern), is only performed for Full Updates if no line item characteristics are
selected (as with summarization levels).
For the initialization of the delta method and of the subsequent delta update, it is necessary to read the data up to
a defined point in time. There are two possible sources for the initialization of the delta method. Summarization
levels record the time when the data was last updated / built. If no line item characteristics were selected and a
suitable, active summarization level (see above) is available, the DataSource inherits the time information from
the summarization level. If it is not possible to read data from a summarization level, data is read from line items
instead.
In the case of delta updates, data is always read from line items.
There can only ever be one valid initial package for a DataSource. If, for the same DataSource, a separate
initialization is scheduled for different selections, for example, and data is posted to the operating concern
between the individual initializations, data inconsistencies could occur between SAP BW and OLTP. The reason
for this is that, with each initialization, the time stamp of the DataSource in the OLTP system is set to the current
value. Consequently, records from a previous selection are no longer selected with the next delta upload if they
were posted with a different selection prior to the last initial run.
The initialization can only occur from one system. If the same DataSource is used from several SAP BW systems
and is posted between the initial runs, data inconsistencies can also occur. This is also because, with each initial
or delta upload, the time stamp for the replication status of the DataSource is reset in the OLTP system. For this
reason, records could be missing in the system that was first updated if data was posted to the operating concern
before the initial run or the delta run. The records loaded into the first system are then missing with a delta upload
in the system that was updated second.
When data is extracted from CO-PA, a “safety delta” of half an hour is used with the initialization and the delta
upload. This always ensures that only records that are already half an hour old since the start of the upload are
loaded into SAP BW. Half an hour was chosen as the safety delta to overcome any time differences between the
clocks on the different application servers.