Technical name: 0FI_AR_4
Technical Data
Type of DataSource |
Transaction data (movement data) |
Application Component |
Financial Accounting: Accounts Receivable Accounting (FI-AR) |
Available from OLTP Release |
4.0B |
Available from Plug-In Release |
2001.1 |
RemoteCube-Compatible |
|
Use
This DataSource extracts Accounts Receivable Accounting line items from tables BSID (open items) and BSAD (cleared items) in the R/3 source system.
This DataSource replaces DataSource 0FI_AR_3 (Accounts Receivable: Line Items) and uses the same extraction structure. The migration of DataSource 0FI_AR_3 to new DataSource 0FI_AR_4 is described in OSS note 410797.
· Source structure: BSID, BSAD
· Extractor: BWFID_GET_FIAR_ITEM
· Extract structure OLTP: DTFIAR_3
Delta Update
This DataSource is delta-compatible.
Origin Fields in the Extract Structure
Field in Extract Structure |
Description of Field in Extract Structure |
Table of Origin |
Field in Table of Origin |
BUKRS |
Company code |
BSID, BSAD |
BSID-BUKRS |
FISCPER |
Fiscal year/period |
BSID, BSAD |
BSID-GJAHR, BSID-MONAT |
BELNR |
Accounting document number |
BSID, BSAD |
BSID-BELNR |
BUZEI |
Account document posting line |
BSID, BSAD |
BSID-BUZEI |
UPOSZ |
Subitem number |
|
= 0001 |
STATUSPS |
Status of the FI item (O = open, C = cleared) |
BSID, BSAD |
BSID-BSTAT, BSID- AUGDT |
KUNNR |
Customer number |
BSID, BSAD |
BSID-KUNNR |
KKBER |
Credit control area |
BSID, BSAD, T001 |
BSID-KKBER or T001-KKBER |
MABER |
Dunning area |
BSID, BSAD |
BSID-MABER |
KOART |
Account type |
|
= D |
UMSKZ |
Special G/L indicator |
BSID, BSAD |
BSID-UMSKZ |
BLART |
Document type |
BSID, BSAD |
BSID-BLART |
BSCHL |
Posting key |
BSID, BSAD |
BSID-BSCHL |
FISCVAR |
Fiscal year variant |
T001 |
T001-PERIV |
BLDAT |
Document date in document |
BSID, BSAD |
BSID-BLDAT |
BUDAT |
Posting date in the document |
BSID, BSAD |
BSID-BUDAT |
CPUDT |
Day on which accounting document was created |
BSID, BSAD |
BSID-CPUDT |
AUGDT |
Clearing date |
BSID, BSAD |
BSID- AUGDT |
MADAT |
Last dunning date |
BSID, BSAD |
BSID-MADAT |
NETDT |
Due date for net payment |
BSID, BSAD |
See below 1) |
SK1DT |
Due date according to cash discount terms 1 |
BSID, BSAD |
See below 1) |
SK2DT |
Due date according to cash discount terms 2 |
BSID, BSAD |
See below 1) |
ZFBDT |
Baseline date for due date calculation |
BSID, BSAD |
BSID-ZFBDT |
ZBD1T |
Cash discount days 1 |
BSID, BSAD |
BSID-ZBD1T |
ZBD2T |
Cash discount days 2 |
BSID, BSAD |
BSID-ZBD2T |
ZBD3T |
Net payment terms period |
BSID, BSAD |
BSID-ZBD3T |
ZBD1P |
Cash discount percentage 1 |
BSID, BSAD |
BSID-ZBD1P |
ZBD2P |
Cash discount percentage 2 |
BSID, BSAD |
BSID-ZBD2P |
LAND1 |
Country key |
T001 |
T001-LAND1 |
ZLSCH |
Payment method |
BSID, BSAD |
BSID-ZLSCH |
ZTERM |
Terms of payment key |
BSID, BSAD |
BSID-ZTERM |
ZLSPR |
Payment block key |
BSID, BSAD |
BSID-ZLSPR |
RSTGR |
Reason code for payments |
BSID, BSAD |
BSID-RSTGR |
MANSP |
Dunning block |
BSID, BSAD |
BSID-MANSP |
MSCHL |
Dunning key |
BSID, BSAD |
BSID-MSCHL |
MANST |
Dunning level |
BSID, BSAD |
BSID-MANST |
LCURR |
Currency key of the local currency |
T001 |
T001-WAERS |
DMSOL |
Debit amount in local currency |
BSID, BSAD |
BSID-SHKZG, BSID-DMBTR |
DMHAB |
Credit amount in local currency |
BSID, BSAD |
BSID-SHKZG, BSID-DMBTR |
DMSHB |
Local currency amount (+/-) |
BSID, BSAD |
BSID-SHKZG, BSID-DMBTR |
SKNTO |
Cash discount amount in local currency |
BSID, BSAD |
BSID- SKNTO |
WAERS |
Currency key |
BSID, BSAD |
BSID-WAERS |
WRSOL |
Debit amount in foreign currency |
BSID, BSAD |
BSID-SHKZG, BSID-WRBTR |
WRHAB |
Credit amount in foreign currency |
BSID, BSAD |
BSID-SHKZG, BSID-WRBTR |
WRSHB |
Foreign currency amount (+/-) |
BSID, BSAD |
BSID-SHKZG, BSID-WRBTR |
SKFBT |
Amount eligible for cash discount in document currency |
BSID, BSAD |
BSID- SKFBT |
WSKTO |
Cash discount amount in document currency |
BSID, BSAD |
BSID- WSKTO |
KTOPL |
Chart of accounts |
T001 |
T001-KTOPL |
HKONT |
General ledger account in G/L accounting. |
BSID, BSAD |
BSID-HKONT |
SAKNR |
G/L account number |
BSID, BSAD |
BSID-SAKNR |
FILKD |
Branch account number |
BSID, BSAD |
BSID-FILKD |
AUGBL |
Clearing document number |
BSID, BSAD |
BSID-AUGBL |
XBLNR |
Reference document number |
BSID, BSAD |
BSID-XBLNR |
REBZG |
Invoice document number |
BSID, BSAD |
BSID-REBZG |
REBZJ |
Fiscal year of the relevant invoice |
BSID, BSAD |
BSID-REBZJ |
REBZZ |
Posting item in the relevant invoice |
BSID, BSAD |
BSID-REBZZ |
VBELN |
Sales document number |
BSID, BSAD |
BSID-VBELN |
XREF1 |
Reference key of the business partner |
BSID, BSAD |
BSID-XREF1 |
XREF2 |
Reference key of the business partner |
BSID, BSAD |
BSID-XREF2 |
XREF3 |
Reference key for the document items |
BSID, BSAD |
BSID-XREF3 |
SGTXT |
Item text |
BSID, BSAD |
BSID-SGTXT |
XNGEP |
Flag: Negative Posting |
BSID, BSAD |
BSID- XNGEP |
XARCH |
Indicator: amount already in archive |
BSID, BSAD |
BSID-XARCH |
UMSKS |
Transaction class Special Ledger |
BSID, BSAD |
BSID-UMSKS |
UPDMOD |
BW delta process: Update mode |
|
|
ZUONR |
Assignment number |
|
|
.INCLUDE CI_BSID |
Customer exits for extract structure DTFIAR_3 |
|
See below 2) |
Notes on the calculated fields:
1) The extract structure fields on the due date for net payment (NETDT, SK1DT, SK2DT) are derived in the R/3 source system from fields ZFBDT, ZBD1T, ZBD2T, ZBD3T, BLDAT, KOART, REBZG, REBZT, SHKZG in tables BSID and BSAD using the function module DETERMINE_DUE_DATE
2) The procedure for customer exits is described in OSS note 410799.
Features of the Extractor
As the
strict connectoin of DataSources has been abolished as of PlugIn2002.2, you
can now load 0FI_GL_4, 0FI_AR_4, 0FI_AP_4 and 0FI_TX_4 in any order you
like. You can also use 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 has been loaded, it is the leading DataSource with regard to
accruals, such as the time and date (CPU date) by which extraction should be
carried out.
From the transition of the data requirements in Delta-Init-Modus to Delta
operation therefore, the data requirement in Delta mode 0FI_GL_4 should take
place first.
Connecting the DataSources in delta operation helps to ensure consistent extraction of FI data. Consistency must be ensured using the Init selection criteria.