FI Extraction

- Vinay Kumar

FI Extraction
FI Module deals with accounting and financial needs of an organization. Financial Accounting is broken down into the following sub-modules: General Ledger Account Receivables Account Payables Asset Accounting Special Purpose Ledger We can extract the financial data at totals level / line item level. In general, we will use R/3 line item tables as the data source for extracting the data to allow drill down capability from summarized data to line-item details. Financial Accounting data can be extracted directly from the tables.

FI-GL, FI-AR and FI-AP:

General Ledger:
The main task of G/L accounting is the overall presentation of Financial Accounting. The general ledger is the complete record of all business transactions

All accounting postings will be recorded in General Ledger.

These postings are real time to provide up-to-date visibility of the financial accounts.

Account Receivable:
Accounts Receivables record all account postings generated as a result of Customer sales activity. These postings are automatically updated in the General Ledger.

Accounts Payable:
Accounts Payables record all account postings generated as a result of Vendor purchasing activity.

Automatic postings are generated in the General Ledger as well.

Sample Flow:

Standard FI Datasources (Old):

0FI_GL_4 (G/L Accounts: Line Items)
This Datasource 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. This datasource is delta-compatible. However, due to the Delta procedure used (AIE - After images Via Extractor (FI-GL/AP/AR)) it is not suitable for loading InfoCubes directly.

An ODS object can be used as data target in order to identify the changes made to individual InfoObjects when loading Delta data.

0FI_AR_4 (AR- line items)

This Datasource provides Accounts Receivable Accounting line items from tables BSID (open items) and BSAD (cleared items) in the R/3 source system. This datasource is delta-compatible. However, due to the Delta procedure used (AIE - After images Via Extractor (FI-GL/AP/AR)) it is not suitable for loading InfoCubes directly.

0FI_AP_4 (AP- line items)

This Datasource provides Accounts Payable Accounting line items from tables BSIK (open items) and BSAK (cleared items) in the R/3 source system. This datasource is delta-compatible. However, due to the Delta procedure used (AIE - After images Via Extractor (FI-GL/AP/AR)) it is not suitable for loading InfoCubes directly. With old G/L in R/3, the tables GLT0 (Totals) - G/L account master record transaction figures BSEG - Accounting Document Segment BKPF (Line Item) - Accounting Document Header get filled in SAP BI side we should have to use data model. GLT0 0FI_GL_1 0FIGL_C01 (for Totals)

BSEG & BKPF 0FI_GL_4 0FIGL_O02 (for Line Items)

GL (New):
With New G/L in SAP ECC 6.0 onwards, the tables FAGLFLEXT (totals), FAGLFLEXA, BSEG, BKPF (Line Item) get filled in BI side: FAGLFLEXT General Ledger: Totals FAGLFLEXA General Ledger: Actual Line Items BSEG Accounting Document Segment BKPF (Line Item) Accounting Document Header Data Model: FAGLFLEXT --> 0FI_GL_10 --> 0FIGL_O10 --> 0FIGL_C10 (New GL Totals) (FAGLFLEXA & BSEG & BKPF) --> 0FI_GL_14 --> 0FIGL_O14 (New GL Line Items)

FI Data Extraction: Time Stamp Method

How the data extraction happens?
In FI extraction 0FI_AR_4 and 0FI_AP_4 are linked with 0FI_GL_4 in order to maintain consistent data transfer from OLTP system (it is called coupled data extraction) General ledger accounting is the main process in delta mode and provides subsidiary ledger extraction with time stamp information (time intervals of previously selected general ledger line items).

This time stamp information can also be used for a loading history: this shows which line items have previously been extracted from the SAP R/3 system.
0FI_GL_4 writes the entries into the time stamp table BWOM2_TIMEST in the SAP R/3 System with a new upper limit for the time stamp selection. And now, 0FI_AP_4 and 0FI_AR_4 will copy this new upper limit for the time stamp selection during the next data extraction in the SAP R/3 System. This ensures the proper synchronization of accounts payable and accounts receivable accounting with respect to G/L accounting. Full Load: Not a valid choice because of large volumes of detailed R/3 transaction data.

Delta load:
Note: Here the delta identification process works differently for new financial records and for changed financial records. New Financial accounting line items which are posted in SAP R/3 system will be identified by the extractor using the time stamp in the document header (Table BKPF-(field) CPUDT Day on which accounting data was entered). By scheduling an initialization IP all the historical data can be loaded into BW from the application tables and it also sets "X" indicator in field LAST_TS (Flag: 'X' = Last time stamp interval of the delta extraction).That means after the last delta, initialization was done.

 After this, daily delta loads can be carried out depending on timestamp by scheduling delta info packages. During the delta load , the SAP R/3 system logs two time stamps that delimit a selection interval for a Data Source in table BWOM2_TIMEST(fields TS_LOW and TS_HIGH).

Changed FI Documents:
In the case of Financial Accounting line items that have been changed since the last data request in SAP R/3, there is no reliable time stamp that can document the time of the last change. For this reason, all line items that are changed in a way relevant for BW must be logged in the system. Changed line items, together with the document key and the time of the last change are recorded in table BWFI_AEDAT:

 Selection of the changed FI documents, will be based on tables: BWFI_AEDAT and (timestamp table) BWOM2_TIMEST
Prerequisite: Recording of the changed line items must be started a reasonable amount of time before the first data request in update mode initialization of the data method. For this purpose, add the following entry in table TPS31 using transaction SM30 (view maintenance):

This function module basically updates the pointer of the field AEDAT and updates the changes done in FI Documents into the table BWFI_AEDAT. This FM must be there before you do a Init.

Customer Enhancements of the Extraction Structure: We can enhance the extraction structures for DataSources 0FI_GL_4, 0FI_AP_4, 0FI_AR_4, and OFI_TX_4 in the SAP R/3 system
by creating user-defined include structures or using transaction RSA6. The following customer includes are supported:

 Case 1: All fields of the customer include are part of the R/3 table. If all fields in the customer include structure are contained in the above-mentioned R/3 table, no further ABAP programming is required. In this case, the fields in the customer include structure are automatically supplied with data by the DataSource extractor.

Case 2: Some fields of the customer include are not part of the R/3 table. If there are fields in the customer include structure that are not contained in the above-mentioned R/3 able, these fields cant be filled using a function module created by the user. Alternatively we can use the BW standard exits for extractor enhancements. Programs from the SAP standard are not modified by this customer interface. Clean separation of SAP standard and customer extraction

Global Settings:
For the transferal of line items from Financial Accounting, important global settings can be made in SAP R/3 in table BWOM_SETTINGS. To do this, change the table using transaction SE16 (table maintenance):

BWFILOWLIM Here, 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 this update mode. BWFISAFETY Here, you can set the upper time limit of the time stamp selection for data requests in all update modes. If the parameter has a value 1, the upper time limit of the time stamp selection is the previous day. Where the parameter values are larger than 1, the upper time limit of the time stamp selection is the corresponding number of days in the past. Note that you cannot select a parameter value smaller than 1, since this would mean that the delta dataset would not be determined completely. ORGSYSONLY If your 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 to BW from various SAP R/3 systems.

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 setting 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 line items are deleted simultaneously from log table BWFI_AEDA2.

BWFIOVERLA
The logic of this parameter prevents records with the previous day as their CPU date from still being in the update at the time of extraction. If X is set for this parameter, selection is made up to the previous day if the time limit is not reached. If <space> is set for this parameter, selection is made up to the day before the previous day if the time limit is not reached.

BWFITIMBOR This parameter designates 02.00 (2 A.M.) as the time limit for extraction. If this limit is not reached, the system uses a security interval of one day to determine the To-value of the selection. If extraction is started before 02:00 therefore, the selection takes place only up to the day before the extraction run.