Accounts Payable Accounting

(1)

Accounts Payable A

ccounting

PDF download from SAP Help Portal: PDF download from SAP Help Portal: http://help.sap.com/saphelp_e

http://help.sap.com/saphelp_erp2005/helpdatrp2005/helpdata/en/29/e3383a/en/29/e3383ffcca4ffcca450ee10050ee10000000a00000a114084/con114084/content.htmtent.htm

Created on July 16, 2016 Created on July 16, 2016

The documenta

tion may have changed since you downloaded the PDF. Y

ou can always find

the latest inform

ation on SAP

Help

Portal.

Note Note

This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included. This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

© 2016 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose © 2016 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permiss

without the express permission of SAP ion of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SE. The information contained herein may be changed without prior notice. Some software products marketed by SAPSAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE

provided by SAP SE and its affiliand its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAPind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries. Pleas

(2)

(3)

Table of content

1 1 Accounts

Accounts Payable

Payable Accounting

Accounting

1.1 Roles

1.1.1 1.1.1 Accounts

Accounts Payable Accou

Payable Accountant

ntant

1.2 Workbooks

1.2.1 1.2.1 Accounts

Accounts Payable:

Payable: Overview

Overview

1.3 Queries

1.3.1 1.3.1 Accounts

Accounts Payable:

Payable: Overview

Overview

1.4 InfoCubes

1.4.1 1.4.1 Accounts Payable:

Accounts Payable: Line I

Line Items

tems

1.4.2 1.4.2 Accounts

Accounts Payable: Tr

Payable: Transaction

ansaction Data

Data

1.5 1.5 ODS

ODS Objects

Objects

1.5.1 1.5.1 Accounts Payable:

Accounts Payable: Line I

Line Items

tems

1.5.2 1.5.2 FI-AP:

FI-AP: Transaction

Transaction Figures

Figures

1.5.3 1.5.3 FI-AP Special Gene

FI-AP Special General Ledger

ral Ledger Transaction

Transaction Figures

Figures

1.6 InfoSources

1.6.1 1.6.1 Accounts Payable:

Accounts Payable: Line I

Line Items

tems

1.6.2 1.6.2 Accounts Payable:

Accounts Payable: Line I

Line Items

tems

1.6.3 1.6.3 Vendor:

Vendor: Transaction

Transaction Figures

Figures

1.6.4 1.6.4 Accounts Payable:

Accounts Payable: Transaction Figures

Transaction Figures Using Delta Procedure

Using Delta Procedure

1.6.5 1.6.5 Accounts Payable:

Accounts Payable: Special General Ledger

Special General Ledger Transaction Figure

Transaction Figures Usi

s Usi

1.6.6 1.6.6 Financial Accounting: Procedure f

Financial Accounting: Procedure for Line Ite

or Line Item Extract

m Extraction

ion

1.6.7 1.6.7 Financial Accounting: Procedure f

Financial Accounting: Procedure for Delta Extract

or Delta Extraction of Transact

ion of Transact

1.7 1.7 Key

Key Figures

Figures

1.7.1 1.7.1 Accumulated

Accumulated Balance

Balance

1.7.2 1.7.2 Total

Total Credit

Credit Postings

Postings

1.7.3 1.7.3 Credit Am

Credit Amount

ount in Foreign

in Foreign Currency

Currency

1.7.4 1.7.4 Credit Am

Credit Amount

ount in Local Cur

in Local Currency

rency

1.7.5 1.7.5 Total

Total Debit

Debit Postings

Postings

1.7.6 1.7.6 Debit Amoun

Debit Amount in

t in Foreign Cur

Foreign Currency

rency

1.7.7 1.7.7 Debit Amoun

Debit Amount in

t in Local Curr

Local Currency

ency

1.7.8 1.7.8 Foreign Currency

Foreign Currency Amount

Amount with Sign

with Sign (+/-)

(+/-)

1.7.9 1.7.9 Local Currency

Local Currency Amount

Amount with Sign (+/

with Sign (+/-)

-)

1.7.1

1.7.10 0 Cash

Cash Discount

Discount Base

Base

1.7.1

1.7.11 1 Cash Discount

Cash Discount Days

Days 1

1

1.7.1

1.7.12 2 Cash Discount

Cash Discount Days

Days 2

2

1.7.1

1.7.13 3 Cash Discount

Cash Discount Percentage

Percentage 1

1

1.7.1

1.7.14 4 Cash Discount

Cash Discount Percentage

Percentage 2

2

1.7.1

1.7.15 5 Cash Discount Amount

Cash Discount Amount in Document

in Document Currency

Currency

1.7.1

1.7.16 6 Cash Discount Am

Cash Discount Amount in

ount in Local Currency

Local Currency

1.7.17 1.7.17 Net

Net Payment

Payment Terms

Terms Period

Period

1.7.1

1.7.18 8 Sales of

Sales of the

the Period

Period

1.8 Characteristics

1.8.1 1.8.1 Postin

Posting

g Date

Date

1.8.2 1.8.2 Balance

Balance Sheet

Sheet Account

Account

1.8.3 1.8.3 Group

Group Chart

Chart of

of Accoun

Accounts

ts

1.8.4 1.8.4 Clearing

Clearing Date

Date

1.8.5 1.8.5 Terms

Terms of

of Payment Key

Payment Key

1.8.6 1.8.6 Chart

Chart of

of Accounts

Accounts

1.8.7 1.8.7 Business

Business Area

Area

1.8.8 Company

1.8.9 1.8.9 Dunning

Dunning Area

Area

1.8.10 1.8.10 G/L

G/L Account

Account

1.8.1

1.8.11 1 Account

Account Type

Type

1.8.12 1.8.12 Document

Document Type

Type

1.8.13 1.8.13 Document

Document Date

Date

1.8.1

1.8.14 4 Posting

Posting Key

Key

1.8.15 1.8.15 Country

Country Key

Key

1.8.16 1.8.16 Company ID

Company ID of

of Tradin

Trading

g Partner

Partner

1.8.1

1.8.17 7 Globally Unique

Globally Unique Business Ar

Business Area

ea

1.8.18

(4)

1.8.1

1.8.19 9 Due Date

Due Date for

for Cash Discount

Cash Discount 1

1

1.8.2

1.8.20 0 Due Date

Due Date for

for Cash Discount

Cash Discount 2

2

1.8.2

1.8.21 1 Dunning

Dunning Block

Block

1.8.2

1.8.22 2 Dunning

Dunning Key

Key

1.8.2

1.8.23 3 Dunning

Dunning Level

Level

1.8.2

1.8.24 4 Date of

Date of Last

Last Dunning Notice

Dunning Notice

1.8.25 1.8.25 Net

Net Due

Due Date

Date

1.8.2

1.8.26 6 Payment

Payment Block Key

Block Key

1.8.27 1.8.27 Payment

Payment Method

Method

1.8.28 1.8.28 Reason Code

Reason Code for

for Payments

Payments

1.8.29 1.8.29 Reference

Reference Document

Document Number

Number

1.8.3

1.8.30 0 Special G/

Special G/L I

L Indicator

ndicator

1.8.3

1.8.31 1 Company

Company Code

Code

1.8.3

1.8.32 2 Baseline Date f

Baseline Date for Due

or Due Date Calculation

Date Calculation

1.9 DataSources

1.9.1 1.9.1 Accounts Payable:

Accounts Payable: Line I

Line Items

tems

1.9.2 1.9.2 Accounts Payable:

Accounts Payable: Line I

Line Items

tems

1.9.3 1.9.3 Accounts Payable:

Accounts Payable: Transaction Figures

Transaction Figures with Delta Extr

with Delta Extraction

action

1.9.4

(5)

!--a11y--> !--a11y-->

1

1 Accounts

Accounts

Payable

Accounting

!--a11y--> !--a11y-->

1.1 Roles

!--a11y--> !--a11y-->

1.1.1

1.1.1 Accounts

Accounts

Payable

Accountant

Technical Name:

Technical Name: 0ROLE_000ROLE_001010

Task Field

The task field of an accounts payable accountant consists of: The task field of an accounts payable accountant consists of:

Processing vendor master data Processing vendor master data Carrying out invoice verific

Carrying out invoice verification (optional)ation (optional) Creating and checking payment

Creating and checking payment proposalsproposals Executing payment runs

Executing payment runs

Structure

Tasks in the

Tasks in the Business Information WarehouseBusiness Information Warehouse

In order that the accounts payable accountant can accomplish these tasks, BW makes business content information available in workbooks. Every task In order that the accounts payable accountant can accomplish these tasks, BW makes business content information available in workbooks. Every task corresponds to a clus

corresponds to a cluster from one or more workbooks. The workbooks cter from one or more workbooks. The workbooks contain one or more querontain one or more queries that yies that yield the relevant information.ield the relevant information. The following workbooks are available for the tasks of the accounts payable accountant:

The following workbooks are available for the tasks of the accounts payable accountant: T Taasskk((CClluusstteerr)) WWoorrkkbbooookk V Veennddoorrss VVeennddoorrss::OOvveerrvviieeww !--a11y--> !--a11y-->

1.2 Workbooks

!--a11y--> !--a11y-->

1.3.1

1.3.1 Accounts

Accounts

Payable:

Overview

Use

This workbook displays the total debit postings, the total credit postings, the accumulated balance, and the sales of the period by vendor account number, This workbook displays the total debit postings, the total credit postings, the accumulated balance, and the sales of the period by vendor account number, company code, and currency type.

company code, and currency type.

Structure

This workbook contains

This workbook contains the following queries:the following queries:

T

Teecchhnniiccaal l NNaamme e oof f TThhe e QQuueerryy NNaamme e aannd d SShhoorrt t DDeessccrriippttiioonn 0FIAP_C02_Q0001

(6)

!--a11y-->

1.3 Queries

!--a11y-->

1.3.1 Accounts Payable: Overview

Technical name: 0FIAP_C02_Q0001 Based on InfoCube:

0FIAP_C02

Use

This query shows the total debit postings, the total credit postings, the accumulated balance and the sales of the period by vendor account number, company code, and currency type.

Filters

InfoObject Description of the Info Object (and restriction or calculation formula)

0FISCVARNT Fiscal year variant

0CURTYPE Currency type (10 = company code currency)

User-Defined Characteristics

InfoObject Description

0COMP_CODE Company code

0FISCPER Fiscal year/period

Rows

0CREDITOR Account number of the vendor

Columns

Debit Totaldebitpostings

Credit Totalcreditpostings

Balance Debit–Credit

Accumulated balance Accumulated balance

Sales Salesfortheperiod

!--a11y-->

(7)

!--a11y-->

1.9.2 Accounts Payable: Line Items

Technical Name: 0FIAP_C03

Use

This InfoCube contains all the Accounts Payable line items that were loaded from the integrated source system(s).

InfoSources

0FI_AP_3: Accounts Payable: Line items

Characteristics

InfoObject Description Data element Field in

transfer structure

Source

0RC_ACCOUNT Reconciliation account SAKNR SAKNR BSIK-SAKNR

0CLR_DOC_NO Clearing document number AUGBL AUGBL BSIK-AUGBL

0BLINE_DATE Baseline date for due date calculation

DZFBDT ZFBDT BSIK-ZFBDT

0AC_DOC_TYP Document type BLART BLART BSIK-BLART

0DOC_DATE Receiptdate BLDAT BLDAT BSIK-BLDAT

0TXTLG Longtext SGTXT SGTXT BSIK-SGTXT

0PSTNG_DATE Posting date in the document BUDAT BUDAT BSIK-BUDAT

0COMP_CODE Company code BUKRS BUKRS BSIK-BUKRS

0POST_KEY Postingkey BSCHL BSCHL BSIK-BSCHL

0LAST_DUNN Date of last dunning MADAT MADAT BSIK-MADAT

0CLEAR_DATE Clearing date AUGDT AUGDT BSIK-AUGDT

0CREATEDON Date the record was created CPUDT CPUDT BSIK-CPUDT

0REASON_CDE Reasoncode RSTGR RSTGR BSIK-RSTGR

0FI_XARCH Indicator: Original document archived

XARCH XARCH BSIK-XARCH

0CHRT_ACCTS Chart of accounts KTOPL KTOPL T001-KTOPL

0ACCT_TYPE Account ty pe KOART KOART Fixed 'K'

0FI_SUBSID Branch account number FILKD FILKD BSIK-FILKD

0CREDITOR Vendor LIFNR LIFNR BSIK-LIFNR

0C_CTR_AREA Credit control area KKBER KKBER BSIK-KKBER

0COUNTRY Countrykey LAND1 LAND1 T001-LAND1

0DUNN_AREA Dunning area MABER MABER BSIK-MABER

0DUNN_KEY Dunningkey MSCHL MSCHL BSIK-MSCHL

0DUNN_BLOCK Dunning block MANSP MANSP BSIK-MANSP

0DUNN_LEVEL Dunning level MAHNS_D MANST BSIK-MAHNS

0NETDUEDATE Due date for net payment NETDT NETDT Calculated

0FI_DOCSTAT Item status STATUSPS STATUSPS Calculated

0INV_YEAR Invoiceyear REBZJ REBZJ BSIK-REBZJ

0INV_DOC_NO Invoice number REBZG REBZG BSIK-REBZG

0INV_ITEM Invoiceitem REBZZ REBZZ BSIK-REBZZ

0REF_DOC_NO Reference document number XBLNR XBLNR BSIK-XBLNR

0REF_KEY1 Reference key 1 XREF1 XREF1 BSIK-XREF1

(8)

0PMNT_BLOCK Payment block key DZLSPR ZLSPR BSIK-ZLSPR 0DSCT_DATE1 Due date for cash discount 1 SK1DT SK1DT Calculated 0DSCT_DATE2 Due date for cash discount 2 SK2DT SK2DT Calculated

0SP_GL_IND Special G/L indicator UMSKZ UMSKZ BSIK-UMSKZ

0DOC_NUMBER Sales Document VBELN VBELN BSIK-VBELN

0PMNTTRMS Terms of payment key DZTERM ZTERM BSIK-ZTERM

0PYMT_METH Payment method DZLSCH ZLSCH BSIK-ZLSCH

Time Characteristics

transfer structure

Source

0FISCPER Fiscal year/period RSFISCPER FISCPER BSIK-GJAHR

BSIK-MONAT

0FISCVARNT Fiscal year variant RSFISCVAR FISCVAR T001-PERIV

Units

transfer structure

Source

0LOC_CURRCY Local currency LCURR LCURR T001-WAERS

0DOC_CURRCY Document currency WAERS WAERS BSIK-WAERS

Key Figures

transfer structure

Source

0DEB_CRE_DC Amount in foreign currency WRSHB WRSHB Calculated

0DEB_CRE_LC Amount in local currency DMSHB DMSHB Calculated

0NETTERMS Terms for net condition DZBD3T ZBD3T BSIK-ZBD3T

0CREDIT_DC Credit amount in foreign currency

WRHAB WRHAB Calculated

0CREDIT_LC Credit amount in local currency

DMHAB DMHAB Calculated

0DSCT_PCT1 Cash discount percentage 1 DZBD1P ZBD1P BSIK-ZBD1P

0DSCT_DAYS1 Cash discount days 1 DZBD1T ZBD1T BSIK-ZBD1T

0DSC_AMT_DC Cash discount amount WSKTO WSKTO BSIK- WSKTO

0DSC_AMT_LC Cash discount amount SKNTO SKNTO BSIK- SKNTO

0DISC_BASE Cash discount base SKFBT SKFBT BSIK- SKFBT

0DEBIT_DC Debit amount in foreign currency

WRSOL WRSOL Calculated

0DEBIT_LC Debit amount in local currency DMSOL DMSOL Calculated

Other Fields

transfer structure

Source

0RECORDMODE BW delta procedure: Update mode

(9)

!--a11y-->

1.4.2 Accounts Payable: Transaction Data

Technical name: 0FIAP_C02

Use

This InfoCube contains all accounts payable data (transaction figures) that was downloaded from the connected source system(s).

InfoSources

0FI_AP_1: Accounts Payable: Transaction Figures

Characteristics

0CREDITOR Account number of the vendor or creditor

0CURRENCY Currency type

Time Characteristics

0FISCYEAR Fiscal year

0FISCPER3 Posting period

Key Figures

0SALES Sales of t he period

0DEBIT Total debit postings

0BALANCE Accumulated balance

0CREDIT Total credit postings

Units

0CURRENCY Currency key

!--a11y-->

1.5 ODS Objects

!--a11y-->

1.9.2 Accounts Payable: Line Items

(10)

Use

The ODS object Accounts Payable: Line Items contains all line items transferred from the source syst em(s) using the InfoSource Accounts Payable Line Items (0FI_AP_3). All fields in the InfoSource are transferred to the ODS object.

InfoSources

0FI_AP_3

Characteristics

0RC_ACCOUNT Reconciliation account

0CLR_DOC_NO Clearing account number

0AC_DOC_TYP Document type

0DOC_DATE Document date

0TXTLG Long text

0PSTNG_DATE Posting date in document

0POST_KEY Posting key

0LAST_DUNN Last dunned

0CLEAR_DATE Clearing date

0CREATEDON Date the record was created

0REASON_CDE Reason code

0CHRT_ACCTS Chart of accounts

0ACCT_TYPE Account ty pe

0FI_SUBSID Branch account number

0CREDITOR Vendor

0C_CTR_AREA Credit control area

0COUNTRY Country key

0DUNN_AREA Dunning area

0DUNN_KEY Dunning key

0DUNN_BLOCK Dunning block

0DUNN_LEVEL Dunning level

0NETDUEDATE Due date for net payment

0FI_DOCSTAT Item status

0INV_YEAR Invoice year

0INV_DOC_NO Invoice number

0INV_ITEM Invoice item

0REF_DOC_NO Reference document number

0REF_KEY1 Reference key 1

0GL_ACCOUNT Account number

0PMNT_BLOCK Payment block key

0DSCT_DATE1 Due date for cash discount 1

0DSCT_DATE2 Due date for cash discount 2

0SP_GL_IND Special G/L indicator

0DOC_NUMBER Sales document

0PMNTTRMS Terms of payment key

(11)

Time Characteristics

Key Figures

0DEB_CRE_DC Amount in foreign currency

0DEB_CRE_LC Amount in local currency

0NETTERMS Net payment terms period

0DSCT_PCT1 Cash discount percentage 1

0DSCT_DAYS1 Cash discount days 1

0DSCT_PCT2 Cash discount percentage 2

0DSCT_DAYS2 Cash discount days 2

0DSC_AMT_DC Cash discount amount

0DSC_AMT_LC Cash discount amount

0DISC_BASE Cash disc. base

0DEBIT_LC Debit amount in local currency

Units

0LOC_CURRCY Local currency

0DOC_CURRCY Document currency

Other Fields

0RECORDMODE BW delta method: Update mode

!--a11y-->

1.5.2 FI-AP: Transaction Figures

Technical name: 0FIAP_O06

Use

This ODS Object contains all transaction figures determined from the source system(s) using the InfoSource Accounts Payable: Transaction Figures Using Delta Procedure (0FI_AP_6). All fields of the InfoSource are transferred to the ODS Object.

Key Fields

KeyFields Description

(12)

0COMP_CODE Companycode

0FISCPER Fiscalyear/period

0FISCVARNT Fiscalyearvariant

Navigation Attributes

None

Delta Update

This ODS object is supported for the delta update After Images via Extractor with the DataSource Accounts Payable: Transaction Figures Using Delta Extraction (0FI_AP_6).

!--a11y-->

FI-AP Special General Ledger Transaction Figures

Technical name: 0FIAP_O07

Use

This ODS Object contains all special general ledger transaction figures determined from the source system(s) using the InfoSource Accounts Payable: Special General Ledger Transaction Figures Using Delta Procedure(0FI_AP_7). All fields of the InfoSource are transferred to the ODS Object.

Key Fields

KeyFields Description

0CREDITOR Accountnumberofvendor

0COMP_CODE Companycode

0FISCYEAR Fiscalyear

0FISCVARNT Fiscalyearvariant

0SP_GL_IND Special general ledger indicator

0ACCT_TYPE Accounttype

Navigation Attributes

None

Delta Update

This ODS object is supported for the delta update After Images via Extractor with the DataSource Accounts Payable: Special General Ledger Transaction Figures Using Delta Extraction (0FI_AP_7).

!--a11y-->

1.6 InfoSources

!--a11y-->

1.9.2 Accounts Payable: Line Items

(13)

Based on DataSource: Accounts Payable: Line Items (0FI_AP_4)

Use

This InfoSource provides Accounts Payable Accounting line items from tables BSIK (open items) and BSAK (cleared items) in the R/3 source system. InfoSource 0FI_AP_4 replaces InfoSource 0FI_AP_3. It provides a modified extraction procedure (direct accessing of tables instead of accessing the records when updating). The communication st ructures of the previous InfoSource 0FI_AP_3 and the new InfoSource 0FI_AP_4 are identical. This means that the update rules for data targets (ODS tables) can be retained. The migration from InfoSource 0FI_AP_3 to I nfoSource 0FI_AP_4 is desc ribed in note 410797. For more information about the extraction procedure, see Financial Accounting: Procedure for Line Item Extraction..

Special Features of the InfoSource

As of Plug-In 2002.2, it is no longer necessary to have DataSources linked. This means that y ou can now load 0FI_GL_4, 0FI_AR_4, 0FI_AP_4, and 0FI_TX_4 in any order. You can also us e the 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 s oon 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 to be carried out.

Therefore, from the t ransfer of the data requests in delta initial mode to the delta only operation, the data request in delta mode of 0FI_GL_4 should be carried out first.

Linking of DataSources in the delta helps to ensure consistent extraction of FI data with regard to time limits. The consistency of the data extracted has to be ensured via the init selection criteria.

This InfoSource is delta-compatible. However, due to the Delta procedure used (after image Delta) it is not suitable for loading InfoCubes directly. An ODS object can be used as data target to determine the changes made to individual InfoObjects when loading Delta datasets.

Characteristics

InfoObject Description Data Element Field in Transfer Structure Source 0RC_ACCOUNT Reconciliation account SAKNR SAKNR BSIK-SAKNR 0CLR_DOC_NO Clearing document number AUGBL AUGBL BSIK-AUGBL 0BLINE_DATE Baseline date for due date

calculation

0AC_DOC_TYP Documenttype BLART BLART BSIK-BLART

0DOC_DATE Documentdate BLDAT BLDAT BSIK-BLDAT

0AC_DOC_NO Document number BELNR_D BELNR BSIK-BELNR

0TXTLG Long description SGTXT SGTXT BSIK-SGTXT

0PSTNG_DATE Posting date in document BUDAT BUDAT BSIK-BUDAT

0COMP_CODE Companycode BUKRS BUKRS BSIK-BUKRS

0LAST_DUNN Last dunning notice MADAT MADAT BSIK-MADAT

0CLEAR_DATE Clearingdate AUGDT AUGDT BSIK-AUGDT

0CREATEDON Date on which the record was added

CPUDT CPUDT BSIK-CPUDT

0FI_DSBITEM Due date item number UPOSZ UPOSZ BSIK-UPOSZ 0FI_XARCH Indicator: Original document

archived

0ACCT_TYPE Account type KOART KOART fix `K´

0DUNN_AREA Dunningarea MABER MABER BSIK-MABER

0DUNN_BLOCK Dunningblock MANSP MANSP BSIK-MANSP

0NETDUEDATE Netduedate NETDT NETDT Calculated

0ITEM_NUM Lineitem BUZEI BUZEI BSIK-BUZEI

(14)

0REF_KEY1 Referencekey1 XREF1 XREF1 BSIK-XREF1

0GL_ACCOUNT Account number SAKNR HKONT BSIK-HKONT

0PMNT_BLOCK Key for payment block DZLSPR ZLSPR BSIK-ZLSPR 0DSCT_DATE1 Due date for cash discount 1 SK1DT SK1DT Calculated 0DSCT_DATE2 Due date for cash discount 2 SK2DT SK2DT Calculated 0SP_GL_IND Special general ledger indicator UMSKZ UMSKZ BSIK-UMSKZ

0DOC_NUMBER Sales document VBELN VBELN BSIK-VBELN 0PMNTTRMS Terms of payment key DZTERM ZTERM BSIK-ZTERM

0RECORDMODE BW delta procedure: Update mode

RODMUPDMOD UPDMOD fix ‘ ‘

Time Characteristics

InfoObject Description Data Element Field in Transfer Structure Source 0FISCPER Fiscal year/period RSFISCPER FISCPER BSIK-GJAHR

BSIK-MONAT 0FISCVARNT Fiscal year variant RSFISCVAR FISCVAR T001-PERIV

Units

InfoObject Description Data Element Field in Transfer Structure Source

0LOC_CURRCY Localcurrency LCURR LCURR T001-WAERS

Key Figures

InfoObject Description Data Element Field in Transfer Structure Source 0DEB_CRE_DC Amount in foreign currency WRSHB WRSHB Calcula ted 0DEB_CRE_LC Amount in local currency DMSHB DMSHB Calcula ted 0NETTERMS Terms for net condition DZBD3T ZBD3T BSIK-ZBD3T 0CREDIT_DC Credit amount in foreign

currency

WRHAB WRHAB Calculated

0CREDIT_LC Credit amount in local currency DMHAB DMHAB Calculated 0DSCT_PCT1 Cash discount percentage 1 DZBD1P ZBD1P BSIK-ZBD1P 0DSCT_DAYS1 Cash discount days 1 DZBD1T ZBD1T BSIK-ZBD1T 0DSCT_PCT2 Cash discount percentage 2 DZBD2P ZBD2P BSIK-ZBD2P 0DSCT_DAYS2 Cash discount days 2 DZBD2T ZBD2T BSIK-ZBD2T 0DSC_AMT_DC Cash discount amount WSKTO WSKTO BSIK- WSKTO 0DSC_AMT_LC Cash discount amount SKNTO SKNTO BSIK- SKNTO 0DISC_BASE Cash discount basis SKFBT SKFBT BSIK- SKFBT 0DEBIT_DC Debit amount in foreign currency WRSOL WRSOL Calculated 0DEBIT_LC Debit amount in local currency DMSOL DMSOL Calculated

!--a11y-->

(15)

Technical name: 0FI_AP_3

Since Release 3.0A (BW PlugIn 2001.1), BW offers consistent data extraction to the BW system in the Delta update procedure for line items from General Ledger Accounting (FI-GL), Accounts Receivable Accounting and Accounts Payable Accounting (FI-AP).

For information on how to start using this new procedure, see OSS note 410797. This explains how to c onvert from using the old extraction procedure (DataSources 0FI_AP_3 and 0FI_AR_3) to the new one (DataSources 0FI_GL_4, 0FI_AP_4 and 0FI_AR_4). As a prerequisite for using this note, y ou must have been using the old DataSources (FI_AP_3 and FI_AR_3) and intend to replace them

with the new ones (0FI_GL_4, 0FI_AP_4 and 0FI_AR_4).

Characteristics

0RC_ACCOUNT Reconciliation account SAKNR SAKNR BSIK-SAKNR

0CLR_DOC_NO Clearing document number AUGBL AUGBL BSIK-AUGBL

0AC_DOC_TYP Document type BLART BLART BSIK-BLART

0DOC_DATE Receiptdate BLDAT BLDAT BSIK-BLDAT

0AC_DOC_NO Document number BELNR_D BELNR BSIK-BELNR

0TXTLG Description (long) SGTXT SGTXT BSIK-SGTXT

0PSTNG_DATE Posting date in the document BUDAT BUDAT BSIK-BUDAT

0COMP_CODE Company code BUKRS BUKRS BSIK-BUKRS

0LAST_DUNN Lastdunned MADAT MADAT BSIK-MADAT

0CLEAR_DATE Clearing date AUGDT AUGDT BSIK-AUGDT

0CREATEDON Date the record was created CPUDT CPUDT BSIK-CPUDT

0FI_DSBITEM Due date item number UPOSZ UPOSZ BSIK-UPOSZ

0ACCT_TYPE Account ty pe KOART KOART fix `K´

0DUNN_AREA Dunning area MABER MABER BSIK-MABER

0DUNN_BLOCK Dunning block MANSP MANSP BSIK-MANSP

0NETDUEDATE Due date for net payment NETDT NETDT calculated

0ITEM_NUM Lineitem BUZEI BUZEI BSIK-BUZEI

0FI_DOCSTAT Item status STATUSPS STATUSPS calculated

0GL_ACCOUNT Account number SAKNR HKONT BSIK-HKONT

0PMNT_BLOCK Payment block key DZLSPR ZLSPR BSIK-ZLSPR

0DSCT_DATE1 Due date for cash discount 1 SK1DT SK1DT calculated 0DSCT_DATE2 Due date for cash discount 2 SK2DT SK2DT calculated

(16)

0DOC_NUMBER Sales document VBELN VBELN BSIK-VBELN

0PMNTTRMS Terms of payment key DZTERM ZTERM BSIK-ZTERM

Time Characteristics

0FISCPER Fiscal year/period RSFISCPER FISCPER BSIK-GJAHR

BSIK-MONAT

0FISCVARNT Fiscal year variant RSFISCVAR FISCVAR T001 - PERIV

Units

0LOC_CURRCY Local currency LCURR LCURR T001-WAERS

Key Figures

0DEB_CRE_DC Amount in foreign currency WRSHB WRSHB calculated

0DEB_CRE_LC Amount in local currency DMSHB DMSHB calculated

0NETTERMS Net payment terms period DZBD3T ZBD3T BSIK-ZBD3T

WRHAB WRHAB calculated

DMHAB DMHAB calculated

0DSC_AMT_DC Cash discount amount WSKTO WSKTO BSIK-WSKTO

0DSC_AMT_LC Cash discount amount SKNTO SKNTO BSIK- SKNTO

0DISC_BASE Cash disc. base SKFBT SKFBT BSIK-SKFBT

WRSOL WRSOL calculated

0DEBIT_LC Debit amount in local currency DMSOL DMSOL calculated

Other Fields

InfoObject Description Data Element Field in Transfer Structure Source 0RECORDMODE BW delta procedure: Update

mode

RODMUPDMOD UPDMOD fix ' '

!--a11y-->

1.6.3 Vendor: Transaction Figures

The OLTP database of the source system contains annual records. The balance carryforward is specified, as well as 16 period values, for debits , credits , and sales .

The extraction program, however, determines data records for each period and generates the accumulated balance including the balance carryforward per period. The balance carryforward no longer exists as a separate value in the BW System, however.

(17)

BW System by the extraction program. These zero data records cannot then be displayed in a query.

Characteristics

0CURTYPE Currency type RSCURTYPE CURTYPE FIX `10´

0COMP_CODE Company code BUKRS BUKRS LFC1-BUKRS

0CREDITOR Vendor LIFNR LIFNR LFC1-LIFNR

Time Characteristics

0FISCVARNT Fiscal year variant RSFISCVAR FISCVAR T001-PERIV

0FISCPER Fiscal year/period RSFISCPER FISCPER calculated

Units

0CURRENCY Currency RSCURRENCY CURRENCY T001-WAERS

Key Figures

0BALANCE Accumulated balance RR_KUMSL UM01K calculated

0CREDIT Total credit postings RR_UMHAB UM01H LFC1-UMxxH

0SALES Sales of the period RR_SALES UM01U LFC1-UMxxU

0DEBIT Total debit postings RR_UMSOL UM01S LFC1-UMxxS

!--a11y-->

Accounts Payable: Transaction Figures Using Delta Procedure

Use

This InfoSource contains the transaction figures for Accounts Payable (table LFC1). In contrast to the InfoSource Accounts Payable: Transaction Figures (0FI_AP_1), it can produce delta figures and therefore can be used instead. The delta procedure means that y ou can also load large volumes of data.

The extraction program, however, determines data records for each period and creates the accumulated balance including the balance carryforward per period. The balance carryforward no longer exists as a separate value in the BW System, however.

!--a11y-->

Accounts Payable: Special General Ledger Transaction Figures

Using Delta Procedure

(18)

This InfoSource c ontains the special general ledger transaction figures for Ac counts Payable (table LFC3) and is c apable of producing delta figures.

The extraction program, however, determines data records for each period and creates the accumulated balance including the balance carryforward per period. The balance carryforward no longer exists as a separate value in the BW System, however.

!--a11y-->

Financial Accounting: Procedure for Line Item Extraction

General Comments on Extraction Procedure

The consistent data extraction in the delta procedure is possible for line items from General Ledger Accounting (FI-GL) and selected subledgers ( Accounts Receivable (FI-AR) and Accounts Pay able (FI-AP) ) and tax reporting with effect from SAP BW 3.1 Content. The extraction procedure delivered with the business content for SAP BW 2.0B, which is based on the DataSources 0FI_AR_3 and 0FI_AP_3, can be replaced. This is described in note 410797. The decisive advantage of choosing R/3 line item tables as the data source is that additional fields can be transferred to the BW. These are not available for the transaction figures. This provides more extensive and flexible analysis options in BW.

To enter a consistent delta dataset, you can use any of the following InfoSources (with the corresponding DataSources and extractors in SAP R/3):

Application InfoSource Name

FI-GL 0FI_GL_4 Generalledger:LineItems

FI-AP 0FI_AP_4 Accountspayable:LineItems

FI-AR 0FI_AR_4 Accountsreceivable:LineItems

FI-TX 0FI_TAX_4 General ledger: Data for taxes on sales and purchases

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). 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 consistent recording of data from General Ledger Accounting and Subledger Accounting is provided by means of c oupled delta extraction in the time stamp procedure. General ledger accounting is the main process i n 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 BW only that 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 extract ed and does not need to be deleted before a new load. This improves performance compared with periodic extraction of the entire dataset.

Financial Accounting line items are read by extractors directly from the tables in SAP R/3. 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 stored in a time stamp table. The delta dataset is transferred to BW directly, without records being transferred to the delta queue in SAP R/3 (extractor delta method).

The Financial Accounting line items are extracted from SAP R/3 in their most recent status (after-image delta method). This delta procedure is not suitable for filling InfoCubes in BW directly. Therefore, firstly, 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, ODS objects) can be provided with data from this ODS object.

If the ODS object permits BEx Reporting , queries can be defined directly there.

Time Stamp Method

With Financial Accounting line items that have been posted in SAP R/3 since the last data request, the extractors identify the following delta dataset using the time st amp in the document header (BKPF-CPUDT).

When a delta dataset has been selected successfully, SAP R/3 logs two time stamps that delimit a selection interval for a DataSource in table BWOM2_TIMEST:

FieldName 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)

(19)

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 Timezone

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 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 Constraints

Per day, no more than one delta dataset c an be transferred for InforSource 0FI_GL_4. The extract ed data therefore has the status of the previous day. For further data requests on the same day, the InfoSource does not provide any data. However, you can change this standard delivery. For more information, see note 485958.

In delta mode, data requests with I nfoSource 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 BW for Accounts Receivable and Accounts Payable Accounting is exactly as up to date as t he data for General Ledger Accounting.

Recording Changed Line Items

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, t ogether with the document key and the time of the last change are recorded in table BWFI_AEDAT:

MANDT X Client

BUKRS X Companycode

BELNR X Accountingdocumentnumber

GJAHR X Fiscalyear

AEDAT Date of last document change

AETIM Time of last document change

MANDT BUKRS BELNR GJAHR AEDAT AETIM

600 1000 1900000010 2001 21.02.2001 10:23:17

600 1000 1000000016 2001 21.02.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. The changed line items are recorded in the following transactions:

(20)

· Manual changing of Financial Accounting line items · Clearing line items

· Changing dunning data for a line item Prerequisite

To be able to record changed line items, v arious update programs in SAP R/3 need to be changed. Therefore, the following support packages must be implemented:

Release SupportPackage

4.0B 64

4.5B 42

4.6B 30

4.6C 22

If these support packages are not implemented in your system, see note 401646.

Recording of the changed line items must be started a reasonable amount of time (see 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. Functionmodule

00005011 BWFIP_WRITE_AEDAT_POINTER

If you delete the last initialization selection in the source system for the InfoSources 0FI_*_4 in the BW syst em 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.

Linking InfoSources

As of Plug-In 2002.2, it is no longer necessary to have DataSources linked. This means that y ou 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 us ed independently of one another (see note 551044).

As s oon 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 extract ion 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 firs t.

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 Plug-In 2002.2 SAP BW 3.1 Content, selections by company c ode 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

You 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 f ollowing customer includes are supported:

Application DataSource R/3Table IncludeStructure

GeneralLedger 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 customer include struct ure 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.

· If there are fields in the cust omer include structure that are not contained in the above-mentioned R/3 able, these fields c ant be filled using a function module created by the user. For more information see 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.

(21)

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 SE 16 (table maintenance):

OLTPSOURCE PARAM_NAME PARAM_VALUE Default Value

<space> BWFILOWLIM YYYYMMDD 19910101

<space> BWFISAFETY <Days> 1

<space> ORGSYSONLY <space>orX <space>

<space> DELTIMEST <Days> 60

<space> BWFIOVERLA <space>orX <space>

<space> BWFITIMBOR <Time> 020000

· BWFILOWLIM

Here, you can set the lower time limit of the time stamp selection for data requests i n 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 s elect a parameter value smaller than 1, s ince 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 c an set the retention period of entries that are no longer required in time stamp table BWOM2_TIMEST. The default s etting for deletion of entries that are no longer required in the time s tamp table is 60 days.The minimum retention period for entries in the time s tamp table is 15 days. When entries are deleted from table BWOM2_TIMEST, the c orresponding 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 s et for this parameter, selection is made up to the previous day if the time limit is not reached.

- If 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.

SAP recommends that you do not change the s tandard value.

!--a11y-->

Financial Accounting: Procedure for Delta Extraction of Transaction

Figures

General Comments on Extraction Procedure

The data extraction in the delta procedure is possible for transaction figures from General Ledger Accounting (FI-GL) and selected subledgers ( Accounts Receivable (FI-AR) and Accounts Payable (FI-AP) ) with effect from SAP BI Content 3.2 Add-On. The extraction procedure delivered with the business content for SAP BW 1.2B, which is based on the DataSources 0FI_GL_1, 0FI_GL_2, 0FI_AR_1, and 0FI_AP_1, can be replaced.

To enter a delta dataset, y ou can use any of the following InfoSources (with the c orresponding DataSources and extractors in SAP R/3):

Component InfoSource Name

FI-GL 0FI_GL_6 General Ledger: Transaction Figures Using Delta Extraction

0FI_GL_7 General Ledger: Cost of Sales Accounting Ledger Using Delta Extraction

FI-AP 0FI_AP_6 Accounts Payable: Transaction Figures Using Del ta Extraction

0FI_AP_7 Accounts Payable: Special General Ledger Transaction Figures Using Delta Procedure

FI-AR 0FI_AR_6 Accounts Receivable: Transaction Figures Using Delta

(22)

Extraction

0FI_AR_7 Accounts Receivable: Special General Led ger Transaction Figures Using Delta Extraction

For the General Ledger, selection is made from the tables GLT0/GLFUNCT, while selection for the subledgers is made from tables KNC1/KNC3 (Accounts Receivable) and LFC1/LFC3 (Accounts Pay able).

Delta Procedure

With delta extraction, only new data or data that has changed since the last extraction is loaded into SAP BW. Data that has already been loaded and has not changed is not ext racted and does not need to be deleted before a new load. This improves performance compared with periodic extraction of t he entire dataset.

The respective extractors read the Financial Accounting transaction figures directly from the SAP R/3 tables. A time stamp on the transaction figures

determines the delta dataset. Time stamp intervals that have already been read are then stored in a time stamp table. The delta dataset is transferred directly, without records being transferred to the delta queue in the SAP R/3 s ystem (extractor delta procedure).

The transaction figures are extracted from the SAP R/3 system in their most recent status (after-image delta procedure). This delta procedures is not suitable for filling InfoCubes directly in the BW system. The transaction figures must therefore first be loaded in an ODS object that determines the changes to

individual characteristics and key figures within a delta data record. Other data destinations (InfoCubes, ODS objects) can be provided with data from this ODS object.

If the ODS object permits BEx Reporting , queries can be defined directly there.

Time Stamp Method

When a delta dataset has been selected successfully, the SAP R/3 system logs two time stamps that define a selection interval for a DataSource in table BWOM2_TIMEST:

MANDT X Client

OLTPSOURCE X DataSource

AEDAT X SYSTEM: Current date

AETIM X SYSTEM: Time

UPDMODE Data update mode (full, delta, delta initial)

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 Indicator: 'X' = Last time stamp interval of the delta extraction

TZONE Timezone

DAYST Daylight saving time active?

The time stamps are determined from the system date and time and converted into the format seconds since 1/1/1990 (with consideration of 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 documents the loading history of Financial Accounting transaction figures. 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 have been omitted:

OLTPSOURCE AEDAT/AETIM UPD DATE_LOW DATE_HIGH LAST_TS 0FI_GL_6 16.05.2004/20:15 Initial 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_6 18.05.2004/21:23 Initial 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_6 17.05.2004/18:45 Initial 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 Constraints:

(23)

No more than one delta dataset can be transferred for the InfoSources 0FI_*_6 und 0FI_*_7 each day. The ex tracted data therefore has the st atus of the previous day. The InfoSource does not provide data for further data requests on the same day. This is the standard delivery, which you can change. For more information, see note 485958.

Recording Changed Transaction Figures

Where transaction figures in Financial Acc ounting have been created and/or changed in SAP R/3 since the las t data request, there is no reliable time stamp that documents the date of creation or the time of t he last c hange. Therefore, all transaction f igures that are changed in a way relevant for BW must be logged in the SAP R/3 system. Changed transaction figures are recorded in table BWFI_AEDA2 with the document key and the date/time of the last change.

MANDT X Client

TABNAME X Tablename

KONTO X Account BUKRS GJAHR GSBER X X X Company code Fiscal year Business area

AEDAT Date of last document change

AETIM Time of last document change

MANDT TABNAME KONTO BUKRS GJAHR AEDAT AETIM

100 GLT0 0000080000 0001 2003 22.12.2003 13:13:53

2004 08.09.2004 16:47:21

0000100000 2003 12.12.2003 10:07:18

2004 27.09.2004 16:44:28

The extractors can use this log table and the time stamp procedures described above to determine a delta dataset of changed transaction figures in Financial Accounting.

Prerequisite:

To record changed line items, v arious update programs in the SA P R/3 sy stem need to be c hanged. Therefore, the following support packages must be implemented:

Release SupportPackage

4.6B 54

4.6C 44

Enterprise 11

If these support packages are not implemented in your system, see note 619454.

The recording of changed transaction figures should be started at an appropriate time interval before the first data request in update mode initialization of delta procedure. To do this , you add the f ollowing entry to table TPS31 using transact ion SM30 (view maintenance):

Process Country Appl. FunctionModule

00005012 BWFI2P_WRITE_AEDA2_POINTER

Global Settings

To transfer transaction figures from Financial Accounting, you can make important global settings in SAP R/ in the table BWOM_SETTINGS. To do this, change the table using transaction SE16 (table maintenance):

OLTPSOURCE PARAM_NAME PARAM_VALUE Standard Value

<space> BWFILOWLIM YYYYMMDD 19910101

<space> BWFISAFETY <Days> 1

<space> ORGSYSONLY <space>orX <space>

<space> DELTIMEST <Days> 60

<space> BWFIOVERLA <space>orX <space>

<space> BWFITIMBOR <Time> 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 procedure . In addition to the selection criteria, this parameter is a determining factor for the data volume for data requests in this update mode.

(24)

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 s elect a parameter value smaller than 1, s ince 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 transaction figures that were originally posted to the BW system will be transferred there from the SAP R/3 system. This prevents transaction figures being transferred several times to BW from various SAP R/3 systems.

· DELTIMEST

With this parameter, you c an set the retention period of entries that are no longer required in time stamp table BWOM2_TIMEST. The default s etting for deletion of entries that are no longer required in the time s tamp table is 60 days. The minimum retention period for entries in the t ime stamp table is 15 days. When entries are deleted from table BWOM2_TIMEST, the c orresponding entries for the changed transaction figures 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 s et 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.

SAP recommends that you do not change the s tandard value.

!--a11y-->

1.7 Key Figures

!--a11y-->

1.7.1 Accumulated Balance

Technical name: 0BALANCE Technical Data

Available from Release 3.0D

Data element RR_KUMSL

Unit 0CURRENCY currency k ey

Aggregation Summation

Exception aggregation Last value

!--a11y-->

1.7.2 Total Credit Postings

Technical name: 0CREDIT Technical Data

Data element RR_UMHAB

Exception aggregation Summation

(25)

1.7.3 Credit Amount in Foreign Currency

Technical name: 0CREDIT_DC Technical Data

Data element WRHAB

Unit 0DOC_CURRCY s ales document currency

!--a11y-->

1.7.4 Credit Amount in Local Currency

Technical name: 0CREDIT_LC Technical Data

Data element DMHAB

Unit 0LOC_CURRCY local currency

!--a11y-->

1.7.5 Total Debit Postings

Technical name: 0DEBIT Technical Data

Available from Release 3.0C

Data element RR_UMSOL

!--a11y-->

1.7.6 Debit Amount in Foreign Currency

Technical name: 0DEBIT_DC Technical Data

Data element WRSOL

(26)

!--a11y-->

1.7.7 Debit Amount in Local Currency

Technical name: 0DEBIT_LC Technical Data

Data element DMSOL

!--a11y-->

1.7.8 Foreign Currency Amount with Sign (+/-)

Technical name: 0DEB_CRE_DC Technical Data

Data element WRSHB

!--a11y-->

1.7.9 Local Currency Amount with Sign (+/-)

Technical name: 0DEB_CRE_LC Technical Data

Data element DMSHB

!--a11y-->

1.7.10 Cash Discount Base

Technical name: 0DISC_BASE Technical Data

Data element SKFBT

(27)

!--a11y-->

1.7.11 Cash Discount Days 1

Technical name: 0DSCT_DAYS1 Technical Data

Data element DZBD1T

Aggregation NOP

Exception aggregation No aggregation (if more than one value is not equal to 0)

!--a11y-->

1.7.12 Cash Discount Days 2

Technical name: 0DSCT_DAYS2 Technical Data

Data element DZBD2T

Aggregation NOP

!--a11y-->

1.7.13 Cash Discount Percentage 1

Technical name: 0DSCT_PCT1 Technical Data

Data element DZBD1P

Aggregation NOP

!--a11y-->

1.7.14 Cash Discount Percentage 2

Technical name: 0DSCT_PCT2 Technical Data

Data element DZBD2P

Aggregation NOP

(28)

1.7.15 Cash Discount Amount in Document Currency

Technical name: 0DSC_AMT_DC Technical Data

Data element WSKTO

!--a11y-->

1.7.16 Cash Discount Amount in Local Currency

Technical name: 0DSC_AMT_LC Technical Data

Data element SKNTO

!--a11y-->

1.7.17 Net Payment Terms Period

Technical name: 0NETTERMS Technical Data

Data element DZBD3T

Aggregation NOP

!--a11y-->

1.7.18 Sales of the Period

Technical name: 0SALES Technical Data

Data element RR_SALES

(29)

1.8 Characteristics

!--a11y-->

1.8.1 Posting Date

Technical name: 0PSTNG_DATE Technical Data

Data element BUDAT

Reference characteristic 0DATE

External hierarchy Available

!--a11y-->

1.8.2 Balance Sheet Account

Technical name: 0BAL_FLAG

Use

This characteristic is a navigation attribute for the characteristic

G/L account. You can use the balance sheet account characteristic to define a query in which you display only your balance sheet, for example. You must define the balance sheet account characteristic as a filter for the G/L account characteristic in your query.

Technical Data

Data element XBILK

External hierarchy Not available

!--a11y-->

1.8.3 Group Chart of Accounts

Technical name: 0CH_ACC_COM Technical Data

Data element KKTPL

Reference characteristic 0CHRT_ACCTS

!--a11y-->

1.8.4 Clearing Date

Technical name: 0CLEAR_DATE Technical Data

(30)

Data element AUGDT

Reference characteristic 0DATE

External hierarchy Available

!--a11y-->

1.8.5 Terms of Payment Key

Technical name: 0PMNTTRMS Technical Data

Data element DZTERM

!--a11y-->

1.8.6 Chart of Accounts

Technical name: 0CHRT_ACCTS Technical Data

Data element KTOPL

!--a11y-->

1.8.7 Business Area

Technical name: 0BUS_AREA Technical Data

Data element GSBER

!--a11y-->

1.8.8 Company

Technical name: 0COMPANY Technical Data

Data element RCOMP_D