2Content Business Drivers FI Extraction CO-OM Extraction FI line-item extractionTimestamp mechanismCustomer extensionsGlobal SettingsAvailability and further informationCO-OM ExtractionCO-OM line-item extractionDelta mechanism (Revised 06/05/03)Customer extensions (Revised 06/05/03)
3Business drivers In other words: Detailed data and delta capability Flexibility:Need for project specific choice of fields.Check on status fields, like open / cleared items.Drill-down and drill-through (analysis):Drill down capability from summarized data to line-item details.Full through capability, e.g. from Accounts Payable to G/L accounts information.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.In other words: Detailed data and delta capabilityCheck on status fields, like open / cleared items. Example: Accounts Payable report with purchase order information – order quantity and value grouped by status
4FI line-item extraction: Data Sources and Data Targets BWG/L accountsAccts. receivableAccts. payableInfoCubes -> summarized dataanalytical queries on cube data0FIAR_C03FIAR: Line item0FIAP_C03FIAP: Line itemDrilldownODS -> document detailsoperational queries on line-item data0FI_GL_O02FIGL: Line item0FI_AR_O03FIAR: Line item0FI_AP_O03FIAP: Line itemInfoSources0FI_GL_4FIGL: Line item0FI_AR_4FIAR: Line item0FI_AP_4FIAP: Line itemDataSourcesR/3Coupled extractionCoupled extractionBKPFHeaderBSADCleared ItemsBSAKCleared ItemsR/3 TablesBSEGSegmentBSIDOpen ItemsBSIKOpen Items
5FI line-item extraction: Features 0FI_GL_4 (G/L Accounts: line items)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.0FI_AP_4 (AP: line items) and 0FI_AR_4 (AR: line items)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 , see OSS noteActuality of extracted dataThe most recent FI documents, which are extracted to BW, are posted in R/3 the day before.See OSS note if you need to circumvent this restriction.0FI_GL_4 provides the General Ledger Accounting line items from tables BKPF and BSEG in the R/3 source system. Only fields that are relevant for the general ledger are transferred from the Financial Accounting document (BKPF and BSEG tables) to the BW. In particular, the InfoSource contains no InfoObjects from Accounts Receivable and Accounts Payable Accounting. This information is extracted separately (InfoSources 0FI_AR_4 and 0FI_AP_4).If the initialization selection the source system is deleted for InfoSource 0FI_GL_4 in the BW system Administrator Workbench, the time stamp entries for InfoSources 0FI_GL_4, 0FI_AP_4 and 0FI_AR_4 from table BWOM2_TIMEST are also removed.
6FI line-item extraction: Delta mechanism 0FI_GL_4, 0FI_AP_4, 0FI_AR_4 use an After Image DeltaDelta type “Extractor“:Delta records are directly selected from the R/3 tables using a timestamp mechanism.Delta records are directly transferred to BW. No record is written to the BW delta queue.After Image Delta:FI line items are transferred from the source system in their final state (= “After Image“).This delta method is not suitable for direct InfoCube update.ODS object is obligatory to determine the delta for InfoCube update.Where BW Delta Queue is used: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.Selection criteria of Delta-Init upload are used to “couple” the datasources logically.
7Timestamp Mechanism: New documents New FI documentsPosted in R/3 since the last line-item extraction.Selection based on the field BKPF-CPUDT.Table BKPF(FI document header)MANDTBUKRSBELNRGJAHR:CPUDTCPUTMAEDATTable BWOM2_TIMEST(Timestamp table)FI document keyUpper limit:previous dayBWOM2_TIMESTnew documentsLower limit:upper limit of thelast G/L line-itemextractionchanged documents
8Timestamp Mechanism: Entries in BWOM2_TIMEST Table BWOM2_TIMEST (Timestamp table)Timestamps are stored as Seconds since ”.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.
9Timestamp Mechanism: Changed documents Changed FI documentsChanged in R/3 since the last line-item extractionCannot be selected based on field BKPF-AEDAT:BKPF-AEDAT is not updated by all BW relevant changes of FIExample: Clearing of an open invoice (by incoming payment) changes the document state, but does not update BKPF-AEDAT.SolutionRecording of all changed FI documents (FI document key, date of last change) in table BWFI_AEDAT.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.
10Timestamp mechanism: Recording of changed docs Simplified flow chartR/3 transactions that recordchanged FI documents intable BWFI_AEDAT:Change documentIncoming/outgoing paymentsDunning...function FI_DOCUMENT_CHANGE...update BSEG.call function OPEN_FI_PERFORM_ _Pendfunction.Business Transaction Events (Tab. TPS31)Process FunctionBWFIP_WRITE_AEDAT_POINTERfunction BWFIP_WRITE_AEDAT_POINTERmove-corresponding BKPF to I_T_BKPF.call function BWFIP_INSERT_BWFI_AEDATtables I_T_BPKF.This entry in table TPS31 starts the recording of changed FI documents.It should be inserted before the delta-init upload.See OSS noteIf the initialization selection the source system is deleted for InfoSource 0FI_GL_4 in the BW system Administrator Workbench, the entry from table TPS31 is also removed. This stops recording of changed line items in table BWFI_AEDAT. Before a new data request can be made in the update mode initialization of the delta method, the entry must be added again to table TPS31.
11Customer ExtensionsExtension of extract structures using customer includesData source R/3 table Extract struct. Customer include0FI_GL_4 BSEG DTFIGL_4 CI_BSIS0FI_AP_4 BSIK/BSAK DTFIAP_3 CI_BSIK0FI_AR_4 BSID/BSAD DTFIAR_3 CI_BSIDCase 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 EventBuild a function module that fills the fields of the customer include. Use the following template: SAMPLE_PROCESS_No modification of SAP standard extractors required.For more information: See OSS noteClean separation of SAP standard and customer extraction
12Global Settings (BWOM_SETTINGS) BWFILOWLIMHere, you can set the lower time limit of the time stamp selection for data requests in update mode initialization of the delta method. Together with the selection criteria, this parameter is a decisive factor for the data volume with data requests in update mode initialization of the delta method.BWFISAFETYHere, 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.ORGSYSONLYIf 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.DELTIMESTWith 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.For the transferal of line items from Financial Accounting, important global settings can be made in the SAP R/3 system in table BWOM_SETTINGS. For this purpose, change the table using transaction SE16 (table maintenance).
13Further information and availability System requirementsR/3 source system:Release 4.0B++PlugInBW:Release 3.0A++(Release 2.0b / 2.1c: See OSS note )SAPNet (OSS) notesImplementation of new DataSources:Extension of extract structures: /Extraction of recent updates:Migration from 0FI_AP_3 / 0FI_AR_3: /“Coupled” extraction:“Uncoupled” extraction:Online documentationCheck documentation on business content, BW 3.0b.
15CO-OM Delta mechanism Where BW Delta Queue is used: 0CO_OM_CCA_9, 0CO_OM_OPA_6, etc. use an Additive DeltaDelta type “Extractor“:Delta records are directly selected from the R/3 tables using a timestamp mechanism (Timestamp table BWOM2_TIMEST).Field *COEP-TIMESTMP is used as a reliable timestamp for selecting new CO-OM line-items.* Reference Field name revised 06/05/03Delta 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).Where BW Delta Queue is used: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.0CO_OM_CCA_9: Use this InfoSource contains information on the actual costs that were posted to cost centers. These costs could have been posted to the cost centers as primary cost postings or internal allocations. In records the system identifies the costs in object currency of a cost center with 0CURTYPE = 10 (company code currency). Unlike the 0CO_OM_CCA_1 InfoSource, you can use the 0CO_OM_CCA_9 InfoSource to select delta datasets also. So that you can enter delta datasets, OLTP system DataSources are created. These DataSources select data from the COEP line item table. This enables additional fields (not contained in the COSP and COSS totals tables) to be transferred to the BIW.
16CO-OM Customer extensions Extension of extract structures* If there is a requirement to extract new fields into BW, use transaction 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 R/3 tables Extract struct. Customer include0CO_OM_CCA_9 COBK/COEP ICCTRCSTA1 CI_COBL0CO_OM_OPA_6 COBK/COEP ICORDCSTA1 CI_COBL0CO_OM_WBS_6 COBK/COEP ICWBSCSTA1 CI_COBL0CO_OM_ABC_7 COBK/COEP ICBPRCSTA1 CI_COBL* Please review OSS Note – Handling Errors from DataSource Append Structures (released 05/14/03) for further details*Revised for content correction 06/05/03
17CO-OM Further information and availability System requirementsR/3 source system:Release 4.0B or higherBW:Release 2.0B or higherSAPNet (OSS) notesTechnical background info:Performance optimization: ,Online documentationCheck documentation on business content, BW 3.0b.