分级基金的募集方式:Financial Accounting: Line Item Extraction Procedure

General Information About the Line Item Extraction Procedure
BW Release 3.1 makes consistent data extraction in the delta method possible for line items in General Ledger Accounting (FI-GL), and selected subsidiary ledgers (Accounts Receivable FI-AR and Accounts Payable FI-AP) and tax reporting. The extraction procedure delivered with BW Release 2.0B, based on DataSources 0FI_AR_3 and 0FI_AP_3 , can be replaced. This is described in note 0410797.
The decisive advantage of choosing R/3 line item tables as the data source is that extra fields can be transferred to the BW. These were not available with transaction figures from table GLTO, the previous R/3 data source in General Ledger Accounting FI-GL. This provides more extensive and flexible analysis in BW.
To enable you to assure consistent Delta data, four new InfoSources are provided in the OLTP system (with the corresponding DataSources and extractors in the SAP R/3 system):
Application
InfoSource
Description
FI-GL
0FI_GL_4
General Ledger: Line Items
FI-AP
0FI_AP_4
Accounts Payable: Line Items (Extraction Linked to 0FI_GL_4)
FI-AR
0FI_AR_4
Accounts Receivable: Line Items (Extraction Linked to 0FI_GL_4)
FI-TX
0FI_TAX_4
General Ledger: Data for Tax on Sales/Purchases
For the General Ledger, selection is made from tables BKPF and BSEG, while selection for the subsidiary accounts is made from tables BSID/BSAD (Accounts Receivable) and BSIK/BSAK (Accounts Payable). InfoSource 0FI_GL_4 transfers only those fields that are relevant for General Ledger Accounting from the Financial Accounting document (tables BKPF and BSEG) to the BW system.
The consisten recording of data from General Ledger Accounting and Subledger Accounting 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 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.
Delta Method
Delta extraction enables you to load into the BW system only that data that has been added or has changed since the last extraction event. Data that is already loaded and is not changed is retained. This data does not need to be deleted before a new upload. This procedure enables you to improve performance unlike the periodic extraction of the overall dataset.
Financial Accounting line items are read by extractors directly from the tables in the SAP R/3 system. A time stamp on the line items serves to identify the status of the delta data. Time stamp intervals that have already been read are then stored in a time stamp table. The delta dataset is transferred to the BW system directly, without records being transferred to the delta queue in the SAP R/3 system (extraktor delta method).
The Financial Accounting line items are extracted from the SAP R/3 system in their most recent status (after-image delta method). This data method is not suitable for filling InfoCubes directly in the BW system. To start with therefore, the line items must be loaded in the BW system in an ODS object that identifies the changes made to individual characteristics and key figures within a delta data record. Other data destinations (InfoCubes) can be provided with data from this ODS object.
Time Stamp Method
With Financial Accounting line items that have been posted in the SAP R/3 system since the last data request, the extractors identify the following delta dataset using the time stamp in the document header (BKPF-CPUDT).
When a delta dataset has been selected successfully, the SAP R/3 system 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, deltainit)
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.

To provide a better overview, the time stamps in the example table are entered in the date format. The columns TZONE and DAYST were left out.
OLTPSOURCE
AEDAT/AETIM
UPD
DATE_LOW
DATE_HIGH
LAST_TS
0FI_GL_4
16 May 2000/20:15
Init
01 Jan. 1990
15 May 2000
0FI_GL_4
24 May 2000/16:59
Delta
16 May 2000
23 May 2000
0FI_GL_4
02 June 2000/21:45
Delta
24 June 2000
01 June 2000
0FI_GL_4
15 June 2000/12:34
Delta
02 June 2000
14 June 2000
0FI_GL_4
21 June 2000/18:12
Delta
15 June 2000
20 June 2000
X
0FI_AP_4
18 May 2000/21:23
Init
01 Jan. 1990
15 May 2000
0FI_AP_4
30 May 2000/12:48
Delta
16 May 2000
23 May 2000
0FI_AP_4
10 June 2000/13:19
Delta
24 June 2000
01 June 2000
X
0FI_AR_4
17 May 2000/18:45
Init
01 Jan. 1990
15 May 2000
0FI_AR_4
04 June 2000/13:32
Delta
16 May 2000
01 June 2000
0FI_AR_4
16 June 2000/15:41
Delta
02 June 2000
14 June 2000
X
0FI_TX_4
17 May 2000/18:45
Init
01 Jan. 1990
15 May 2000
0FI_TX_4
04 June 2000/13:32
Delta
16 May 2000
01 June 2000
0FI_TX_4
16 June 2000/15:41
Delta
02 June 2000
14 June 2000
X
Constraints
Per day, no more than one delta dataset can be transferred for InforSource 0FI_GL_4. The extracted data therefore has the status of the previous day. For further data requests on the same day, the InfoSource does not provide any data.

With Plugin 2002.2, this restriction no longer applies (note 485958). See Global Settings (below).
In delta mode, data requests with InfoSource 0FI_AR_4 and InfoSource 0FI_AP_4 do not provide any data if no new extraction has taken place with InfoSource 0FI_GL_4 since the last data transfer. This ensures that the data in the BW system for Accounts Receivable and Accounts Payable Accounting is exactly as up to date as the data for General Ledger Accounting.

If you delete the initialization selection in the source system for InfoSource 0FI_GL_4 in the BW system Administrator Workbench, the time stamp entries for InfoSources 0FI_GL_4, 0FI_AP_4, 0FI_AR_4 and OFI_TX_4 are also removed from table BWOM2_TIMEST.
Recording Changed Line Items
In the case of Financial Accounting line items that have been changed since the last data request in the SAP R/3 system, 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 SAP R/3 system. Changed line items, together with the document key and the time of the last change are recorded in table BWFI_AEDAT.
Field Name
Key
Description
MANDT
X
Client
BUKRS
X
Company Code
BELNR
X
Accounting document number
GJAHR
X
Fiscal year
AEDAT
Date of last document change
AETIM
Time of last document change

MANDT
BUKRS
BELNR
GJAHR
AEDAT
AETIM
600
1000
1900000010
2001
21 Feb. 2001
10:23:17
600
1000
1000000016
2001
21 Feb. 2001
10:28:34
Using the log table and the time stamp procedure described above, the extractors can find a delta dataset from changed Financial Accounting line items.
Prerequisite
To be able to record changed line items, various update programs in the SAP R/3 system need to be changed. These program changes are provided in the SAP standard via support packages or can be installed manually in the SAP R/3 system using a preliminary correction. For implementation details, see note 401646.
Recording of the changed line items must be started a reasonable amount of time (see note 401646) 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

If you delete the initialization selection in the source system 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. 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.
In the SAP standard system, recording of changed line items is implemented via support packages or by manual installation of the preliminary correction to note 401646 in the following transactions:
Manual changing of Financial Accounting line items Clearing line items Changing dunning data for a line item
Linking InfoSources
As of PlugIn2002.2, it is no longer necessary to have DataSources linked. This means that you can now load 0FI_GL_4, 0FI_AR_4, 0FI_AP_4 and 0FI_TX_4 in any order. You also have the option of using DataSources 0FI_AR_4, 0FI_AP_4 and 0FI_TX_4 separately without 0FI_GL_4. The DataSources can then be used independently of one another (see note 551044).

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) – 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 data with regard to time limits. Consistency with regard to the data extracted has to be ensured via the init selection criteria (see below).
Partioned Initial Data Requests
As of PlugIn 2002.2 / BW Content Release 3.10, selections by company code and fiscal year/period are possible for DataSources 0FI_AR_4, 0FI_AP_4 and 0FI_TX_4. Partioned data requests are therefore possible in Delta Init mode. Selections for data requests in Delta Init mode are then managed separately for each DataSource.

If you want extraction to be consistent, you have to choose the same Init selection criteria (company code and fiscal year/period) for all DataSources.
Customer Enhancements of the Extraction Structure
The extraction structures for DataSources 0FI_GL_4, 0FI_AP_4, 0FI_AR_4 and OFI_TX_4 can be enhanced in the SAP R/3 system by the creation of user-defined include structures.
Application
DataSource
R/3 Table
Include Structure
General Ledger
0FI_GL_4
BSEG/BKPF
CI_BSIS
Accounts Receivable
0FI_AR_4
BSIK / BSAK
CI_BSIK
Accounts Payable
0FI_AP_4
BSID / BSAD
CI_BSID
Taxes
0FI_TX_4
BSET
CI_BSET
If all fields in the user-defined include structure are contained in the above-mentioned R/3 table, no further ABAP programming is required. In this case, the fields in the user-specific structure are automatically supplied with data by the DataSource extractor. If there are fields in the user-specific 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. For details, see note 410799. Programs from the SAP standard are not changed by this user-specific interface.
Global Settings
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).
OLTPSOURCE
PARAM_NAME
PARAM_VALUE
Default Value

BWFILOWLIM
YYYYMMDD
19910101

BWFISAFETY

1

ORGSYSONLY
or X


DELTIMEST

60

BWFIOVERLA
or X


BWFITIMBOR

020000
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 update mode initialization of the delta method.
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 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 FI line items are deleted simultaneously from log table BWFI_AEDAT.
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 is selected 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 applies a safety time interval of one day for determination of the to-value. If extraction is started before 02:00 therefore, the selection takes place only up to the day before the extraction run.
Changing the default value is not recommended.
In some way, we can create abap report to collect delta data for 0FI_GL_04, not change the global settings.Refer theURL:http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/7444.