Professional Documents
Culture Documents
Data Extraction (Line Item Level) FI/CO (Financial Accounting and Controlling)
Data Extraction (Line Item Level) FI/CO (Financial Accounting and Controlling)
Paula Gist (CPA), BW RIG Lothar Schubert, BW RIG October 3rd, 2002
Content
Business Drivers FI Extraction
FI line-item extraction Timestamp mechanism Customer extensions Global Settings Availability and further information
CO-OM Extraction
CO-OM line-item extraction Delta mechanism (Revised 06/05/03) Customer extensions (Revised 06/05/03) Availability and further information
Business drivers
Flexibility:
Need for project specific choice of fields. Check on status fields, like open / cleared items.
Actuality:
Access to recent (or even real-time) data.
Scalability:
High number / wide variety of users. Large volumes of detailed R/3 transaction data are transferred to BW Daily full loads are inefficient.
BW
InfoCubes -> summarized data
analytical queries on cube data
G/L accounts
Accts. receivable
Accts. payable
Drilldown
InfoSources
R/3
0FI_GL_4 0FI_AR_4 0FI_AP_4 FIGL: Line item FIAR: Line item FIAP: Line item Coupled extraction Coupled extraction
No redundant fields are transferred into BW: Only fields from the FI document tables (BKPF/BSEG) that are relevant to general ledger accounting (compare table BSIS), No customer or vendor related fields. Vendor / Customer related information (e.g. payment/dunning data). Coupled extraction consistent snapshot of FI data in BW: G/L account extraction determines selection criteria (comp.code, fiscal period) and upper time limit of all extracted FI line-items. AP and AR extraction: no further selection criteria necessary / possible. Uncoupled extraction possible with PlugIn PI 2002.2, see OSS note 551044. The most recent FI documents, which are extracted to BW, are posted in R/3 the day before. See OSS note 485958 if you need to circumvent this restriction.
Table BKPF
(FI document header) MANDT BUKRS Table BWOM2_TIMEST BELNR FI document key (Timestamp table) GJAHR : Upper limit: : new documents previous day CPUDT CPUTM BWOM2_TIMEST AEDAT Lower limit: : changed documents upper limit of the last G/L line-item :
extraction
Timestamps are stored as Seconds since 01.01.1990. Other DataSources (e.g. CO line-item extraction) also use this table. Documentation of upload history: Recording of FI data that has already been extracted into BW. Well-defined sync-points, if the delta upload has failed.
Solution
Recording of all changed FI documents (FI document key, date of last change) in table BWFI_AEDAT.
MANDT 600 600 BUKRS 1000 1000 BELNR 1900000010 1000000016 GJAHR AEDAT 2001 21.02.2001 2001 21.02.2001 AETIM 10:23:17 10:28:34
FI update programs in R/3 had to be changed. Selection of the changed FI documents based on tables BWFI_AEDAT and (timestamp table) BWOM2_TIMEST.
It should be inserted before the delta-init upload. See OSS note 401646
function BWFIP_WRITE_AEDAT_POINTER ... move-corresponding BKPF to I_T_BKPF. call function BWFIP_INSERT_BWFI_AEDAT tables I_T_BPKF. endfunction.
SAP Labs America 2002, FI / CO Line Item Extraction 10
Customer Extensions
Extension of extract structures using customer includes
Data source R/3 table 0FI_GL_4 0FI_AP_4 0FI_AR_4 BSEG BSIK/BSAK BSID/BSAD DTFIGL_4 DTFIAP_3 DTFIAR_3 CI_BSIS CI_BSIK CI_BSID Extract struct. Customer include
Case 1: All fields of the customer include are part of the R/3 table. No additional ABAP-coding is required. The fields of the customer include is automatically filled by the extractor. Case 2: Some fields of the customer include are not part of the R/3 table. Use Business Transaction Event 00005021. Build a function module that fills the fields of the customer include. Use the following template: SAMPLE_PROCESS_00005021. No modification of SAP standard extractors required. For more information: See OSS note 410799
BWFISAFETY
Here, you can the upper time limit of the time stamp selection for data requests in all update modes. Value 1 in this parameter means that the upper time limit of the time stamp selection is the previous day. With larger parameter values, the upper limit of the time stamp selection is correspondingly further (in days) in the past. Note that you cannot choose a parameter value cannot be smaller than 1, as this would prevent the delta dataset being found completely.
ORGSYSONLY
If you SAP R/3 system is part of an ALE scenario, set this parameter to X. This ensures that only those line items that were originally posted to the BW system will be transferred there from the SAP R/3 system. This prevents line items being transferred several times from various SAP R/3 system.
DELTIMEST
With this parameter, you can set the retention period of entries that are no longer required in time stamp table BWOM2_TIMEST. The default settings for deletion of entries that are no longer required in the time stamp table is 60 days. The minimum retention period for entries in the time stamp table is 15 days. When entries are deleted from table BWOM2_TIMEST, the corresponding entries for the changed FI line items are deleted simultaneously from log table BWFI_AEDAT.
BW:
Release 3.0A++ (Release 2.0b / 2.1c: See OSS note 401646)
Online documentation
Check documentation on business content, BW 3.0b.
BW
InfoCubes ->
summarized data
analytical queries
InfoSources DataSources
0CO_OM_CCA_9 0CO_OM_OPA_6
0CO_OM_WBS_6
0CO_OM_ABC_7
R/3 Tables
COBK COEP
R/3
SAP Labs America 2002, FI / CO Line Item Extraction 14
CO documents
Delta records are directly transferred to BW. No record is written to the BW delta queue. Additive Delta : Only new CO-OM line-items are transferred from the source system (=Additive Delta). No changes on CO documents are relevant for BW. This delta method is suitable for direct InfoCube update. ODS object is optional to store document details (for operational queries on line-item data).
Delta queue and BW scheduler ensure correct serialization of the records (e.g. inserts must not pass changes) Distribution of delta records to multiple BW systems.
RSA6. The extract structure must be increased with the new fields required to be extracted. The new data will be written automatically with the extractor ,but please note, this will not automatically be sent to BW if the fields are not in the extract structure. * The includes CI_COBL e.g. for 0CO_OM_CCA_9 do not have anything to do with BW but it is normal CO include where the customer can fill in some new fields he needs in CO.
Data source 0CO_OM_CCA_9 0CO_OM_OPA_6 0CO_OM_WBS_6 0CO_OM_ABC_7 R/3 tables COBK/COEP COBK/COEP COBK/COEP COBK/COEP Extract struct. ICCTRCSTA1 ICORDCSTA1 ICWBSCSTA1 ICBPRCSTA1 Customer include CI_COBL CI_COBL CI_COBL CI_COBL
* Please review OSS Note 394491 Handling Errors from DataSource Append Structures (released 05/14/03) for further details
BW:
Release 2.0B or higher