DGP and Interest on Arrears: Procedure for Line Item Extraction 
The consistent data extraction in the delta procedure for IOA/IoA related information is based on extraction methods used in Finance for line items from General Ledger Accounting (FI-GL), selected subledgers (Accounts Receivable (FI-AR) and Accounts Payable (FI-AP)) and tax reporting with effect from SAP BW 3.1 Content. IOA/IoA extraction process enhances the possibilities of line item analysis already provided in SAP standard Financial Accounting.
To enter a consistent delta dataset, you can reuse any of the following BI standard InfoSources (with the corresponding DataSources and extractors in ECC):
Application |
InfoSource |
Name |
|---|---|---|
FI-GL |
0FI_GL_4 |
General ledger: Line Items |
FI-AP |
0FI_AP_4 |
Accounts payable: Line Items |
FI-AR |
0FI_AR_4 |
Accounts receivable: Line Items |
FI-TX |
0FI_TAX_4 |
General ledger: Data for taxes on sales and purchases |
The DGP//IoA related data can be transferred to BI using the following DataSources:
Application |
DataSource |
System |
Name |
|---|---|---|---|
FPS_IOA_IO |
0PPS_FPIA_DGDOCN_ATTR |
ECC |
IOA Document number |
FPS_IOA |
0PPS_FPIA_IOAIOA_PROTIME_OC |
ECC |
IOA Processing time open/cleared docs |
FPS_IOA |
/FPIA_IOAIOA_LITEM_OC |
ECC |
IOA Line items open/cleared docs |
FPS_IOA |
0PPS_BBP_TD_CONTR_2 |
SRM |
Purchase contracts with IoA data |
FPS_IOA |
0PPS_SRM_TD_PO |
SRM |
SRM Purchase Order Transactional Data with IoA |
For the General Ledger, selection is made from the tables BKPF and BSEG, while selection for the subledgers is made from tables BSID/BSAD (Accounts Receivable) and BSIK/BSAK (Accounts Payable). IOA/IoA extraction is devided into category line items oriented extraction for open/cleared FI documents and preliminary documents such as MM invoices without an accounting (FI) document and preliminary FI documents and category IOA processing time document related extraction of open/cleared FI documents and preliminary FI / MM documents without related FI , (tables BSEG, VBKPF, BKPF , VBSEGK, VBSEGS, RBKP, RBCO, FPIA_INTEREST, FPIA_FI_IDX, FMIFIIT, INTITIT).
The consistent recording of data from General Ledger Accounting and IOA/IoA related information is provided by means of coupled delta extraction in the time stamp procedure. General ledger accounting is the main process in delta mode and provides IOA/IoA extraction (as well as subsidiary ledger extraction) with time stamp information. That is, time intervals of previously selected general ledger line items.
The ECC extractors of all DataSources concerning IOA line items, IOA processing times and IOA document number are primarily oriented on availability of documents in table FPIA_INTEREST and FPIA_FI_IDX. In contrast to General Ledger extractors as mentioned above, the extractors for IOA don’t deliver any other document and line items if the document number is neither contained in FPIA_INTEREST nor FPIA_FI_IDX as being leading tables during IOA extraction process.
IOA/IoA information in SRM contracts and purchase orders are delivered by DataSources 0PPS_BBP_TD_CONTR_2 and 0PPS_SRM_TD_PO. Both DataSources are copies of DataSources 0BBP_TD_CONTR_2 and 0SRM_TD_PO but include the additional interest key field.
Delta extraction enables you to load into BW only the data that has been added or has changed since the last extraction event. Data that has already been loaded and has not changed is not extracted and does not need to be deleted before a new load. This improves performance compared with periodic extraction of the entire dataset.
IOA line items (datasource 0PPS_FPIA_IOAIOA_LITEM_OC) consist of Financial Accounting line items that are read directly from the tables in ECC (mainly BSEG) but without IOA processing time data. A time stamp on the FPIA_INTEREST line items (field CHANGED_AT) serves to identify the status of the delta data. Time stamp intervals of open and cleared FI documents that have already been read are stored in a time stamp table (FPIA_INTEREST-CHANGED_AT). The delta dataset is transferred to BW directly, without records being transferred to the SAP standard delta queue in ECC (extractor delta method).
The IOA processing time open/cleared documents are extracted from ECC in their most recent status (after-image delta method). Like IOA line items, the delta procedure is not suitable for filling InfoCubes in BW directly. Therefore, firstly, the line items must be loaded in the BW system in a DataStore object that identifies the changes made to individual characteristics and Key Figures within a delta data record. Other data destinations (InfoCubes, DataSource objects) can be provided with data from this DataStore object.
If the DataStore object permits BEx Reporting, queries can be defined directly there.
The IOA document number master data is extracted from ECC in their most recent status (after-image delta method and to be loaded directly into characteristic 0PPS_DGDOCN, followed by an attribute change run.
With Financial Accounting line items that have been posted in ECC since the last data request, the extractors identify the following delta dataset using the time stamp in the document header (BKPF-CPUDT in case of G/L extractors, FPIA_INTEREST-CHANGED_AT in case of IOA extractors).
When a delta dataset has been selected successfully, ECC logs two time stamps that delimit a selection interval for a DataSource in table BWOM2_TIMEST:
Field Name |
Key |
Description |
|---|---|---|
MANDT |
X |
Client |
OLTPSOURCE |
X |
DataSource |
AEDAT |
X |
SYSTEM: Date |
AETIM |
X |
SYSTEM: Time |
UPDMODE |
Data update mode (full, delta, delta init) |
|
TS_LOW |
Lower limit of the time selection (time stamp in seconds since 1.1.1990) |
|
TS_HIGH |
Upper limit of the time selection (time stamp in seconds since 1.1.1990) |
|
LAST_TS |
Flag: X = Last time stamp interval of the delta extraction |
|
TZONE |
Time zone |
|
DAYST |
Daylight saving time active? |
The time stamps are determined from the system date and time and converted to the format seconds since 1.1.1990, taking into account the time zone and daylight saving time. To ensure correct and unique reconversion to date and time, the time zone and daylight saving time must be stored in table BWOM2_TIMEST.
Table BWOM2_TIMEST therefore serves to document the loading history of Financial Accounting line items. It also provides defined restart points following incorrect data requests.
Note
To provide a better overview, the time stamps in the following example table are entered in the date format. The columns TZONE and DAYST are omitted.
OLTPSOURCE |
AEDAT/AETIM |
UPD |
DATE_LOW |
DATE_HIGH |
LAST_TS |
|---|---|---|---|---|---|
0FI_GL_4 |
16.05.2004/20:15 |
Init |
01.01.1990 |
15.05.2004 |
|
24.05.2004/16:59 |
Delta |
16.05.2004 |
23.05.2004 |
||
02.06.2004/21:45 |
Delta |
24.06.2004 |
01.06.2004 |
||
15.06.2004/12:34 |
Delta |
02.06.2004 |
14.06.2004 |
||
21.06.2004/18:12 |
Delta |
15.06.2004 |
20.06.2004 |
X |
|
0FI_AP_4 |
18.05.2004/21:23 |
Init |
01.01.1990 |
15.05.2004 |
|
30.05.2004/12:48 |
Delta |
16.05.2004 |
23.05.2004 |
||
10.06.2004/13:19 |
Delta |
24.06.2004 |
01.06.2004 |
X |
|
0FI_AR_4 |
17.05.2004/18:45 |
Init |
01.01.1990 |
15.05.2004 |
|
04.06.2004/13:32 |
Delta |
16.05.2004 |
01.06.2004 |
||
16.06.2004/15:41 |
Delta |
02.06.2004 |
14.06.2004 |
X |
|
0FI_TX_4 |
17.05.2004/18:45 |
Init |
01.01.1990 |
15.05.2004 |
|
04.06.2004/13:32 |
Delta |
16.05.2004 |
01.06.2004 |
||
16.06.2004/15:41 |
Delta |
02.06.2004 |
14.06.2004 |
X |
|
0PPS_FPIA_IOAIOA_LITEM_OC |
17.05.2004/18:45 |
Init |
01.01.1990 |
15.05.2004 |
|
04.06.2004/13:32 |
Delta |
16.05.2004 |
01.06.2004 |
||
16.06.2004/15:41 |
Delta |
02.06.2004 |
14.06.2004 |
X |
Per day, no more than one delta dataset can be transferred with DataSources 0PPS_FPIA_IOAIOA_LITEM_OC, 0PPS_FPIA_IOAIOA_PROTIME_OC and 0PPS_FPIA_DGDOCN_ATTR. The extracted data therefore has the status of the previous day. For further data requests on the same day, the DataSource does not provide any data. However, you can change this standard delivery. For more information, see SAP Note 485958 which describes the situation for FI standard extractors but is also valid for IOA/IoA.
To be able to record changed line items, various update programs in ECC need to be changed. Therefore, the following support packages must be implemented:
Release |
Support Package |
|---|---|
4.0B |
64 |
4.5B |
42 |
4.6B |
30 |
4.6C |
22 |
If these support packages are not implemented in your system, see SAP Note 401646.
Recording of the changed line items must be started a reasonable amount of time (see SAP Notes 401646 and 663539) 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):
Process |
Lnd |
Applic. |
Function module |
|---|---|---|---|
00005011 |
BWFIP_WRITE_AEDAT_POINTER |
Note
If you delete the last initialization selection in the source system for the InfoSources 0FI_*_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. Existing data in table BWFI_AEDAT is also deleted. 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.
As of Plug-In 2002.2, it is no longer necessary to have DataSources linked. This means that you can load 0FI_GL_4, 0FI_AR_4, 0FI_AP_4, 0FI_TX_4, 0PPS_FPIA_IOAIOA_LITEM_OC, 0PPS_FPIA_IOAIOA_PROTIME_OC, and 0PPS_FPIA_DGDOCN_ATTR in any order. You also have the option of using DataSources 0PPS_FPIA_IOAIOA_LITEM_OC, 0PPS_FPIA_IOAIOA_PROTIME_OC and 0PPS_FPIA_DGDOCN_ATTR separately without 0FI_GL_4. The DataSources can then be used independently of one another (see SAP Note 551044).
Note
As soon as DataSource 0FI_GL_4 is loaded, it is the leading DataSource with regard to the time limits – such as maximum time (CPU date in case of 0FI_GL_4 and CHANGED_AT in case of IOA datasources) – up to which data extraction is allowed. Therefore, when the transition is made from having data requirements in Delta Init mode to having them in pure Delta operation, the data requirement in delta mode of leading DataSource (OFI_GL_4) must be processed first.
Linking of DataSources in the delta helps to ensure consistent extraction of FI and IOA/IoA data with regard to time limits. Consistency with regard to the data extracted has to be ensured by means of the init selection criteria (see below).
You can enhance the extraction structure for DataSources 0PPS_FPIA_IOAIOA_LITEM_OC and 0PPS_FPIA_IOAIOA_LITEM_P in the ECC system by creating user-defined include structure or using transaction RSA6. The following customer includes are supported:
Application |
DataSource |
ECC Table |
Include Structure |
|---|---|---|---|
FPS_IOA |
0PPS_FPIA_IOAIOA_LITEM_OC |
FPIA_S_IOAIOA |
CI_FPIA |
FPS_IOA |
0PPS_FPIA_IOAIOA_LITEM_P |
FPIA_S_IOAIOA |
CI_FPIA |
Include CI_FPIA may be used for additional fields available in source tables using the following order:
Open/cleared documents: BSEG
Preliminary FI documents: VBSEGS, VBKPF, VBSEGK
MM documents: RBCO and RBKP.
The extractor automatically determines the corresponding source table; no additional coding is necessary.
If there are fields in the customer include structure that are not contained in the above mentioned ECC table (FPIA_S_IOAIOA), these fields cannot be filled using a function module created by the user. For more information see SAP Note 410799.
Alternatively, you can use the BW standard exits for extractor enhancements. Programs from the SAP standard are not modified by this customer interface.
For the transfer of line items from Financial Accounting, important global settings can be made in ECC in table BWOM_SETTINGS. To do this, change the table using transaction SE16 (table maintenance):
OLTPSOURCE |
PARAM_NAME |
PARAM_VALUE |
Default Value |
|---|---|---|---|
<space> |
BWFILOWLIM |
YYYYMMDD |
19910101 |
<space> |
BWFISAFETY |
<Days> |
1 |
<space> |
ORGSYSONLY |
<space> or X |
<space> |
<space> |
DELTIMEST |
<Days> |
60 |
<space> |
BWFIOVERLA |
<space> or X |
<space> |
<space> |
BWFITIMBOR |
<Time> |
020000 |
BWFILOWLIM
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
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
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 ECC 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 ECC system. This prevents line items being transferred several times to BW from various ECC systems.
DELTIMEST
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.