318915021-BW-320-FICA-e.pdf

Contract Accounts Receivable and Payable

T U _ S I _ W B D N . N O D D A

Release 320

SAP Online Help

13.05.2003

Copyright © Copyright 2003 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation. IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/390®, OS/400®, OS/400®, iSeries, pSeries, pSeries, xSeries, zSeries, zSeries, z/OS, AFP, Intelligent Intelligent Miner, WebSphere®, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries. ORACLE® is a registered trademark of ORACLE Corporation. UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group. Citrix®, the Citrix logo, I CA®, Program Neighborhood®, Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Technology. JAVA® is a registered trademark trademark of Sun Microsystems, Inc. JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are trademarks of their respective companies.

Contract Accounts Receivable and Payable 330

2

SAP Online Help

13.05.2003

Icons Icon

Meaning Caution Example Note Recommendation Syntax

Typographic Conventions Type Style

Description

Example text

Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options. Cross-references to other documentation.

Example text

Emphasized words or phrases phrases in body text, titles of graphics and tables.

EXAMPLE TEXT

Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text

Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT

Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text

Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. documentation.

text>

Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.


3

SAP Online Help

13.05.2003

Contract Accounts Accounts Receivable Receivable and Payable Payable ............................................................................. 7 Individual Roles in Contract Accounting ................................................................................ 7 FI-CA: Item Analysis........................................................................................................... Analysis........................................................................................................... 7 Workbooks in Contract Accounting........................................................................................ Accounting........................................................................................ 7 FI-CA: Historical Open Open Items.............................................................................................. Items.............................................................................................. 7 FI-CA: Open Open Items30-60-90 Items30-60-90 ............................................................................................ ............................................................................................... ... 8 FI-CA: Cleared Cleared Historical Open Items................................................................................ 8 Queries in Contract Contract Accounting Accounting ............................................................................................. 9 FI-CA: Historical Open Open Items.............................................................................................. Items.............................................................................................. 9 FI-CA: Open Open Items 30-60-90 30-60-90 .............................................................................................. 9 FI-CA: Cleared Cleared Items........................................................................................................ Items........................................................................................................ 10 InfoCubes in Contract Accounting ....................................................................................... 11 FI-CA: Historical Open Open Items............................................................................................ Items............................................................................................ 11 FI-CA: Cleared Cleared Items........................................................................................................ Items........................................................................................................ 12 Collection Agencies.......................................................................................................... 12 Installment Plan Header Header and and Item Data ........................................................................... 12 Installment Plan Header Data .......................................................................................... 13 InfoSources in Contract Accounting .................................................................................... 13 FI-CA: Open Items ................................................................................... ........................................................................................................... ........................ 13 FI-CA: Cleared Cleared Items........................................................................................................ Items........................................................................................................ 13 Contract Account: Account: Non-Partner-Ba Non-Partner-Based sed Data.................................................................... Data .................................................................... 14 Contract Account: Account: Partner-Based Partner-Based Data............................................................................ 14 FI-CA: Account Account Relationships Relationships of a Partner Partner ...................................................................... 14 DataSources DataSources in Contract Contract Accounting Accounting................................................................................... ................................................................................... 14 Open Items Items at Period End .......................................................................................... ................................................................................................ ...... 14 Open Items Items on Key Date.................................................................................................. 15 Cleared Items for the Interval........................................................................................... 16 Posting Totals for for Debit Debit Positions Positions .................................................................................... 18 Reversals and Write-Offs ................................................................................................. 19 Items Submitted to Collection Collection Agencies........................................................................... Agencies........................................................................... 20 Header Data for for Installment Installment Plans ................................................................................... 21 Installment Plan Items ................................................................................................ ...................................................................................................... ...... 22 Partner-Independe Partner-Independent nt Contract Account Account Data ................................................................... 23 Partner-Independe Partner-Independent nt Contract Account Account Data ................................................................... 24 Texts for Account Account Relationships....................................................................................... Relationships....................................................................................... 25 Account Relationships Relationships of a Partner.................................................................................. Partner.................................................................................. 26 Texts for Contract Accounts........................................................................................ Accounts ............................................................................................. ..... 26 Texts for Contract Account Categories Categories ............................................................................ 27 Texts for Clearing Clearing Reasons.............................................................................................. Reasons.............................................................................................. 28


4

SAP Online Help

13.05.2003

Installment Plan Source Item ........................................................................................... 28 ODS Objects in Contract Accounting................................................................................... 30 FI-CA: Open Items ........................................................................................................... 30 Installment Plan Header and Item Data ........................................................................... 31 Installment Plan Header Data .......................................................................................... 31 Key Figures in Contract Accounting .................................................................................... 32 FI-CA: Open Items ........................................................................................................... 32 FI-CA: Cleared Items........................................................................................................ 32 Charges Receivable......................................................................................................... 32 Amount to Collect ............................................................................................................. 33 Interest Receivable........................................................................................................... 33 Amount Collected ............................................................................................................. 33 Data Record Counter ....................................................................................................... 34 Number of Confirmed Items ............................................................................................. 34 Payment Amount.............................................................................................................. 34 Amount Not Collected ...................................................................................................... 35 Amount (Time of Deactivation)......................................................................................... 35 Characteristics in Contract Accounts Receivable and Payable........................................... 35 FI-CA: Start of Clearing Period......................................................................................... 35 FI-CA: End of Clearing Period.......................................................................................... 36 FI-CA: Clearing Reason ................................................................................................... 36 FI-CA: Clearing Grid as String.......................................................................................... 37 FI-CA: Interval Number .................................................................................................... 37 FI-CA: Analysis Key Date................................................................................................. 38 FI-CA: Record Number..................................................................................................... 38 FI-CA: Identification of Mass Activity................................................................................ 38 FI-CA: Date Identification of Mass Activity ....................................................................... 39 Account Category............................................................................................................. 39 Application Area ............................................................................................................... 39 Contract Account of Collector........................................................................................... 39 Contract account (partner-independent data) .................................................................. 40 Dunning Block Reason..................................................................................................... 40 Grouping Category – Dunning Notices ............................................................................ 40 Dunning Procedure .......................................................................................................... 41 Interest Key ...................................................................................................................... 41 Main Transaction: Defines Posting Procedure with Subtrans.......................................... 41 Settlement Category......................................................................................................... 41 Settlement Type ............................................................................................................... 42 Subtransaction: Defines Posting Procedure with Main Trans.......................................... 42 Contract Account (Partner-Dependent Data) ................................................................... 42


5

SAP Online Help

13.05.2003

Contract Account Category .............................................................................................. 43 Relationship of Business Partner to Contract Account .................................................... 43 Bank Details ID for Incoming Payments........................................................................... 43 Tax Rate........................................................................................................................... 44 Collections Agency........................................................................................................... 44 Submission Frequency..................................................................................................... 44 Execution Date of the Transaction ................................................................................... 44 Date of Submission to the Collections Agency ................................................................ 45 Submission Status of the Receivable............................................................................... 45 Start Date ......................................................................................................................... 45 End Date........................................................................................................................... 46 Deactiviation Date ............................................................................................................ 46 Installment Plan Category ................................................................................................ 46 Installment Plan Number.................................................................................................. 46 Item Number for Contract Accounts Receivable and Payable......................................... 47 Repetition Item ................................................................................................................. 47 Receivable Sold ............................................................................................................... 47 Transaction Duration........................................................................................................ 48 Subitem Number .............................................................................................................. 48 Process Chain in Contract Accounts Receivable and Payable ........................................... 48 Process Chain: Installment Plan Delta Load and Update ................................................ 48


6

SAP Online Help

13.05.2003

Contract Accounts Receivable and Payable

Individual Roles in Contract Accounting

FI-CA: Item Analysis Technical name: SAP_BW_FICA_ANALYSIS

Tasks This role provides you with an extensive view of FI-CA items in a whole company. To help you do this, you are provided with operative and strategic reports that can be used to compare or format items at the end of a month. The historic, strategic analysis reports, on the other hand, enable you to recognize trends or characteristics early and make the appropriate decisions.

Activities in operative FI-CA Reporting Typical activities for this role: •

Open items 30-60-90 Open items divided according to due date and displayed in grids

Activities in Strategic FI-CA Reporting Typical activities for this role: •

Historical open items Enable you to recognize trends and take the necessary steps

•

Cleared historical items Trends are made visible and actions supported. Delayed payments cost the company a lot of money. Activities that improve the payment habits of customers are therefore a great advantage to a company. Before you can introduce any measures, however, you must carry out analyses that provide information on the payment habits of customers and allow you to recognize connecting factors.

Workbooks in Contract Accounting

FI-CA: Historical Open Items Use This workbook enables you to analyze open items at periodic intervals according to their company codes and for a key date. You can also include the business area or division in the analysis.


7

SAP Online Help

13.05.2003

To gain a meaningful result, you must enter an analysis period.

Structure The workbook contains the following queries: Technical Name of Query

Name and Short Description

0FC_C01_Q0001

Open items (historical)

FI-CA: Open Items30-60-90 Use This workbook displays open items due on a key date as well as overdue open items in the grids 0, 1-30, 31-60, 61-90 and more than 90 days. You can also include the business area or division in the analysis. For the selection to be successful, you must enter the key date when the open items are to be determined.



0FC_DS01_Q0001

Open items 30-60-90

FI-CA: Cleared Historical Open Items Use This workbook enables you to analyze clearing amounts at periodic intervals according to a user-defined clearing grid and clearing reason. You can also include the company code in the analysis. To gain a meaningful result, you must enter an analysis period. In order to sort the amounts in a sensible way using the clearing grid, you must start the grid description with a sort criterion such as 1_10-0 days before due date or 2_1-10 days after due date.



0FC_C02_Q0001

Cleared items


8

SAP Online Help

13.05.2003

Queries in Contract Accounting

FI-CA: Historical Open Items Technical name: 0FC_C01_Q0001

Use This query enables you to analyze open items at periodic intervals according to their company codes and for a key date. You can also include the business area or division in the analysis. To gain a meaningful result, you must enter an analysis period.

Free Characteristics Info Object

Description

0BUS_AREA

Business area

0DIVISION

Division

Variables Used Variable

Description

0S_FCKDA

Key date period (select option)

0CMPCODE

Company Code

Rows Info Object

Description of the InfoObject (and Restriction or Calculation Formula)

0COMP_CODE

Company Code

Columns Info Object

Description of the InfoObject (and Restriction or Calculation Formula)

0FC_KEYDATE

Key date (date when the open items were determined by the mass activity)

0FC_OI

Open items

FI-CA: Open Items 30-60-90 Technical name: 0FC_DS01_Q0001


9

SAP Online Help

13.05.2003

Use This query displays an overview of overdue open items in a company code on a key date in the grids 0, 1-30, 31-60, 61-90 and more than 90 days. You can also include the business area or division in the analysis. For the selection to be successful, you must enter the key date when the open items are to be determined.


Description

0BUS_AREA

Business Area

0DIVISION

Division


Description

0P_FCKDA

Key date (date when the open items were determined by the mass activity)

0P_DUEDN

Due date from key date

0CMPCODE

Company code

A SAP exit provides the 0P_DUEDN variable with the key date value (0P_FCKDA). This value is then used to determine the open items for the individual due periods.

Rows Info Object

Description of the InfoObject (and restriction or calculation formula)

0FC_KEYDATE

Key date

0COMP_CODE

Company code

Columns Info Object


0FC_OI

Open items

FI-CA: Cleared Items Technical name: 0FC_C02_Q0001

Use This query enables you to analyze clearing amounts at periodic intervals according to a userdefined clearing grid and clearing reason. You can also include the company code in the analysis. To gain a meaningful result, you must enter an analysis period. In order to sort the amounts in a sensible way using the clearing grid, you must start the grid description with a sort criterion such as 1_10-0 days before due date or 2_1-10 days after due date.


10

SAP Online Help

13.05.2003


Description

0COMP_CODE

Company code


Description

0S_COCD

Company code

0S_ECIPE

End of clearing period

Rows Info Object


0FC_DELAY

Clearing grid

0FC_CLERARR

Clearing reason

Columns Info Object


0FC_CITO

End of clearing (to-date of the clearing period entered during data extraction)

0FC_CI

Cleared items

InfoCubes in Contract Accounting

FI-CA: Historical Open Items Technical Name: 0FC_C01

Use This InfoCube contains information about the open items determined on a key date by the mass activity. The non-cumulative value is managed according to key dates and must be determined at periodic intervals (for example, once a month) if it is to provide useful information about the individual analysis periods. You can select the evaluation Calendar year / month. The system determines the value from the key date. You can evaluate the key figures Open items and Number of document items contained in the InfoCube according to different attributes. •

Company code

•

Business area

•

Division

•

Dunning procedure


11

SAP Online Help

•

13.05.2003

Regional characteristics

FI-CA: Cleared Items Technical Name: 0FC_C02

Use This InfoCube contains information about cleared items determined at a certain interval by the mass activity. If you want to compare different intervals from different analyses, the intervals must contain comparable periods (for example, monthly) and must be determined periodically. You can select the evaluation Calendar day , Calendar year / month, Calendar month and Calendar year . The system determines each value from the interval end. You can evaluate the key figures Cleared items and Number of document items contained in the InfoCube according to different attributes. •

Company Code

•

Division

•

Clearing reason

•

Dunning procedure

•

Regional characteristics

•

Clearing grid

Collection Agencies Technical Name: 0FC_C03

Use This InfoCube allows you to assess collection agencies by analyzing the delivered receivables and the responses that were generated as a result. You can use the transaction date or the submission date of the receivable to obtain more time-based details. You can analyze the data from various aspects such as the process duration, the receivables sold, or the submission status of the collection items. For example, you can compare the percentage rates of the receivables collected by the various agencies within a month.

Installment Plan Header and Item Data Technical Name: 0FC_C04

Use This InfoCube allows you to analyze the open and cleared installment plan items.


12

SAP Online Help

13.05.2003

You can use the end or start date of the installment plan, the due date for net payment, or the clearing date to obtain more time-based details. You can analyze the data from various aspects, in particular according to the attributes of the installment plan items. For example, you can call up a structured display of the sum of the expected monthly installment payments by installment plan category.

Installment Plan Header Data Technical Name: 0FC_C05

Use This InfoCube allows you to analyze installment plans. You can use the start date, the end date, or the deactivation date of the installment plan to obtain more time-based details. You can analyze the data from various aspects, in particular according to the attributes of the installment plan header data. For example, you can display how many installment plans were created in each month and the amount of each installment.

InfoSources in Contract Accounting

FI-CA: Open Items Technical name: 0FC_OP_01

Use This InfoSource enables you to access the data basis for the Historical open items InfoCucube and the ODS object Open items. The system determines the data using tables from contract accounts receivable and payable and the business partner.

FI-CA: Cleared Items Technical Name: 0FC_CI_01

Use This InfoSource provides you with the data basis for the Cleared item InfoCube. The system determines the data using tables from contract accounts receivable and payable and the business partner.


13

SAP Online Help

13.05.2003

Contract Account: Non-Partner-Based Data Technical name: 0CACONT_ACC

Use This InfoSource contains information about the non-partner-based data of the contract account. This information enables you to group contract accounts according to contract account categories, for example.

Contract Account: Partner-Based Data Technical name: 0FC_ACCNTBP

Use This InfoSource contains information about the partner-based data of the contract account. This information includes, for example, whether the business partner is the account holder, and whether bank details are stored.

FI-CA: Account Relationships of a Partner Technical name: 0FC_ACCTREL

Use You use this InfoSource to determine whether a business partner is the account holder for a contract account.

DataSources in Contract Accounting

Open Items at Period End Technical name: 0IS_PHOPITPEND

Technical Data Type of DataSource

Transaction Data

Application Component

Contract Accounts Receivable and Payable (FI-CA)

Available from OLTP Release

4.62

RemoteCube Compatibility

No

Prerequisites The source table DFKKREP04 has been filled using report RFKKPD02.


14

SAP Online Help

13.05.2003

Use This DataSource extracts open item totals at the period end according to specific criteria.

Delta Update A Delta update is not supported.

Fields of Origin in the Extract Structure Field in Extraction Structure

Description of Field in the Extract Structure

Table of Origin

Field in Table of Origin

MANDT

Client

DFKKREP04

MANDT

BUKRS

Company code

DFKKREP04

BUKRS

GSBER

Business area

DFKKREP04

GSBER

SPART

Division

DFKKREP04

SPART

VARKY

Variable keys (industry fields + customer fields)

DFKKREP04

VARKY

GJAHR

Posting year

DFKKREP04

GJAHR

GMONT

Posting month

DFKKREP04

GMONT

AJAHR

Reporting year

DFKKREP04

AJAHR

AMONT

Reporting month

DFKKREP04

AMONT

BETRH

Local currency amount (+/- DFKKREP04 )

BETRH

WAERS

Currency key

WAERS

T001

Open Items on Key Date Technical name: 0FC_OP_01


Transactional data (movement data)




FI-CA 4.63 (4.6C)

Available from Plug-In Release

DataSource is shipped with the OLTP release


No

Prerequisites This DataSource must be adjusted using Customizing in OLTP. It is a generic DataSource that extracts the content of table DFKKOPBW in OLTP. The structure of this table is adjusted within the OLTP project. As a result, the DataSource must also be adjusted. Once this has been done, the DataSource must be replicated in BW, and the transfer and update rules must be set and generated.


15

SAP Online Help

13.05.2003

Use You use this DataSource to extract open items from the OLTP. In OLTP, open items are written in table DFKKOPBW by a mass activity (transaction code FPBW) and are normally pre-aggregated.

Delta Update Delta update is not available. Delta occurs as a result of repeated mass activity in OLTP.

Fields of Origin in the Extraction Structure Field in Extraction Structure

Description of Field in the Extraction Structure

ADDRNUMBER

Address number

BETRH

Amount in local currency (+/-)

BETRW

Amount in transaction currency (+/-)

BUKRS

Company code

COUNTRY

Country key

FAEDN

Net due date

GPART

Business partner number

GSBER

Business area

HWAER

Currency key in local currency

INTNR

Interval number in the variant

KEYDT

Key date for analysis of open items

LAUFD

Run date

LAUFI

Additional ID

MAHNV

Dunning procedure

MANDT

Client

POST_CODE1

Postal code

RECCOUNT

Number of summarized open items

RECNO

Record number

SPART

Division

VKONT

Contract account number

WAERS

Transaction currency

Features of the Extractor The DataSource is only an example and must be adjusted for individual customer needs during the appropriate project.

Cleared Items for the Interval Technical name: 0FC_CI_01


16

SAP Online Help

13.05.2003






FI-CA 4.64 (4.6C)

Available from Plug-In Release

DataSource is shipped with the OLTP release


No

Prerequisites The DataSource must be adjusted using Customizing in OLTP. It is a generic DataSource that extracts the content of table DFKKCIBW in OLTP. The structure of this table is adjusted within the OLTP project. As a result, the DataSource must also be adjusted. Once this has been done, the DataSource must be replicated in BW, and the transfer and update rules must be set and generated.

Use You can use this DataSource to extract cleared items from OLTP. In OLTP, cleared items are written in table DFKKCIBW by a mass activity (transaction code FPCIBW) and are normally pre-aggregated. In OLTP, the system only includes clearing information covering a predefined period.

Delta Update Delta update is not available. Delta occurs as a result of repeated mass activity in OLTP.



ADDRNUMBER

Address number

AUGRD

Clearing reason

BETRH

Amount in local currency (+/-)

BETRW

Amount in transaction currency (+/-)

BUKRS

Company code

CIFROM

Key date for extraction, clearing start

CITO

Key date until which the cleared items are analyzed

COUNTRY

Country key

DELAY

Grid name

HWAER

Currency key in local currency

INTNR

Interval number in the variant

LAUFD

Run date

LAUFI

Additional ID

MAHNV

Dunning procedure

MANDT

Client

POST_CODE1

Postal code

RECCOUNT

Number of summarized open items


17

SAP Online Help

13.05.2003

RECNO

Record number

SPART

Division

WAERS


Features of the Extractor The DataSource is only an example and must be adjusted for individual customer needs during the appropriate project.

Posting Totals for Debit Positions Technical name: 0IS_PHDEBTOTALS


Transaction Data




4.62


No

Prerequisites The source table DFKKREP03 has been filled using report RFKKPD01.

Use This DataSource extracts posting totals for debit entries in Contract Accounts Receivable and Payable for the selected period.




Table of Origin


MANDT

Client

DFKKREP03

MANDT

BUKRS

Company code

DFKKREP03

BUKRS

GSBER

Business area

DFKKREP03

GSBER

SPART

Division

DFKKREP03

SPART

VARKY


DFKKREP03

VARKY

GJAHR

Posting year

DFKKREP03

GJAHR

GMONT

Posting month

DFKKREP03

GMONT

BETRH

Local currency amount (+/-)

DFKKREP03

BETRH

WAERS

Currency key

T001

WAERS


18

SAP Online Help

13.05.2003

Reversals and Write-Offs Technical name: 0IS_PHREV_WR_OFFS


Transaction Data




4.62


No

Prerequisites You have executed the steps described in the Implementation Guide for Contract Accounts Receivable and Payable under Information System → Configure Reporting for Payment Processing.

Use This DataSource extracts total reversals and write-offs within a specific period according to specific criteria.




Table of Origin


MANDT

Client

DFKKREP05

MANDT

BUKRS

Company code

DFKKREP05

BUKRS

GSBER

Business area

DFKKREP05

GSBER

SPART

Division

DFKKREP05

SPART

VARKY


DFKKREP05

VARKY

GJAHR

Posting year

DFKKREP05

GJAHR

GMONT

Posting month

DFKKREP05

GMONT

AJAHR

Reporting year

DFKKREP05

AJAHR

AMONT

Reporting month

DFKKREP05

AMONT

SBETR

Total amount of reversal DFKKREP05 in local currency

SBETR

ABETR

Write-offs in local currency

DFKKREP05

ABETR

WAERS

Currency key

T001

WAERS


19

SAP Online Help

13.05.2003

Items Submitted to Collection Agencies Technical Name: 0FC_COLL_01


Transaction data

Application component


Available from OLTP release

4.71

Available from Plug-In release No

RemoteCube-capable

Use The DataSource extracts collection agency items.

Delta Update The delta update is supported.

Source Fields of the Extraction Structure Field in the Extraction Structure

Description of the Field in the Extraction Structure

Source Table

Field in the Source Table

MANDT

Client

DFKKCOLLH

MANDT

INKGP

Collection agency

DFKKCOLLH

INKGP

BUKRS

Company code

DFKKCOLLH

BUKRS

AGDAT

Date of submission of a receivable to a collection agency

DFKKCOLLH

AGDAT

PROCDAT

Date of current transaction

DFKKCOLLH

PROCDAT

WAERS

Currency key

DFKKCOLLH

WAERS

BETRW

Amount in transaction currency with +/- sign

DFKKCOLLH

BETRW

BETRZ

Payment amount in transaction currency

DFKKCOLLH

BETRZ

NINKB

Uncollectible amount

DFKKCOLLH

NINKB

INTBT

Interest request from collection agency

DFKKCOLLH

INTBT

CHARB

Charges receivable from collection agency

DFKKCOLLH

CHARB

AGSTA

Status of an item DFKKCOLLH submitted to a collection agency

AGSTA


20

SAP Online Help

13.05.2003

XSOLD

Item sold to collection agency

DFKKCOLLH

XSOLD

PROCDURA

Period between submission and reporting of item

DFKKCOLLH

No source table exists, value determined by extractor

NUMSUBM

Number of submissions to collection agency

DFKKCOLLH


DOCITEMS

Number of summarized items

DFKKCOLLH


NUMRESP

Number of reported items

DFKKCOLLH


Header Data for Installment Plans Technical Name: 0FC_IPL_HEAD_01


Transaction data




4.71

Available from Plug-In release RemoteCube-capable

No

Use This DataSource extracts the header data of installment plans.


Source Fields of the Extraction Structure Field in the Extraction Description of the Field Structure in the Extraction Structure

Source Table


RPNUM

Number of the installment plan in FI-CA

FKK_INSTPL_HEAD

RPNUM

RECORDMODE

BW delta procedure: Update mode

GPART

Business partner number FKK_INSTPL_HEAD

GPART

VKONT

Contract account number FKK_INSTPL_HEAD

VKONT

BUDAT

Posting date in document DFKKKO

BUDAT

STTDT

Start date of the

STTDT


FKK_INSTPL_HEAD

21

SAP Online Help

13.05.2003

installment plan ENDDT

End date of the installment plan

FKK_INSTPL_HEAD

ENDDT

RPCAT

Category of the installment plan

FKK_INSTPL_HEAD

RPCAT

DEADT

Deactivation date of the installment plan

FKK_INSTPL_HEAD

DEADT

DEOFF

Open amount at the time of deactivation

FKK_INSTPL_HEAD

DEOFF

WAERS

Currency key

FKK_INSTPL_HEAD

WAERS

COMPA

Total of the individual installments of the installment plan

INTBETG

Total interest amount of an installment plan

FKK_INSTPL_HEAD

INTBETG

Special Features of the Extractor To support the delta update, the extractor saves the dataset in its own tables at the time of the last extraction. After the initialization in BW, you have to run the extraction completely once. To do this, set the indicator No Delta – Extract All in the extractor.

Installment Plan Items Technical Name: 0FC_IPL_ITEM_01


Transaction data




4.71

Available from Plug-In release RemoteCube-capable

No

Use This DataSource extracts the items of installment plans.


Source Fields of the Extraction Structure Field in the Extraction Structure

Description of the Field in the Extraction Structure

OPBEL

Number for a document DFKKOP in Contract Accounts Receivable and Payable

OPBEL

OPUPW

Repetition item in a

OPUPW


Source Table

DFKKOP


22

SAP Online Help

13.05.2003

document from Contract Accounts Receivable and Payable OPUPK

Item number in a DFKKOP document from Contract Accounts Receivable and Payable

OPUPK

OPUPZ

Subitem for a partial clearing in the document

DFKKOP

OPUPZ

RECORDMODE

BW delta procedure: Update mode

BUKRS

Company code

DFKKOP

BUKRS

GSBER

Business area

DFKKOP

GSBER

GPART


DFKKOP

GPART

VKONT


DFKKOP

VKONT

SPART

Division

DFKKOP

SPART

BUDAT

Posting date in document

DFKKOP

BUDAT

FAEDN

Due date for net payment

DFKKOP

FAEDN

BETRW

Amount in transaction currency

DFKKOP

BETRW

WAERS


DFKKOP

WAERS

BETRH

Amount in local currency

DFKKOP

BETRH

HWAER

Local currency

T001

HWAER

AUGDT

Clearing date

DFKKOP

AUGDT

AUGRD

Clearing reason

DFKKOP

AUGRD

Special Features of the Extractor To support the delta update, the extractor saves the dataset in its own tables at the time of the last extraction. After the initialization in BW, you have to run the extraction completely once. To do this, set the indicator No Delta – Extract All in the extractor.

Partner-Independent Contract Account Data Technical name: 0CACONT_ACC_ATTR


Attributes (Master Data)


Contract Accounts Receivable and Payable (FI-CAIO)


23

SAP Online Help

13.05.2003


IS-U 4.63 (4.6C)


No

Use This DataSource extracts information not based on t he partner for contract accounts. This will be primarily used as navigation attributes of the InfoCube 0UCMA_C01 (target group selection according to turnover and consumption) in BW.

Delta Update ALE update pointer



Table of Origin


VKONT


FKKVK

VKONT

VKTYP

Contract account category

FKKVK

VKTYP

APPLK

Application area

FKKVK

APPLK

LOEVM

Indicator: Set contract account for deletion

FKKVK

LOEVM

MANDT

Client

FKKVK

MANDT

Partner-Independent Contract Account Data Technical name: 0FC_ACCNTBP_ATTR Technical Data Type of DataSource



Contract Accounts Receivable and Payable (FI-CA-IO)


IS-U 4.63 (4.6C)


No

Use This DataSource extracts partner-dependent information for contract accounts. This data is primarily used as navigation attributes of the InfoCube 0UCMA_C01 (target group selection according to turnover and consumption) in BW.


Fields of Origin in the Extraction Structure Field in Extraction

Description of Field in


Table of Origin

Field in Table of

24

SAP Online Help

13.05.2003

Structure

the Extraction Structure

Origin

VKONT


FKKVKP

VKONT

GPART


FKKVKP

GPART

VKBEZ

Relationship of business partner to contract account

FKKVKP

VKBEZ

EBVTY

Bank details ID for incoming payments

FKKVKP

EBVTY

LOEVM

Select contract account for deletion

FKKVKP

LOEVM

VKPBZ


FKKVKP

VKPBZ

FDGRP

Planning group

FKKVKP

FDGRP

MANDT

Client

FKKVKP

MANDT

Texts for Account Relationships Technical name: 0FC_ACCTREL_TEXT


Texts (Master Data)




4.63


No

Use This DataSource extracts texts for contract account relationships.


Fields of Origin in the Extract Structure Field in Extract Structure


Table of Origin


SPRAS


TFK002FT

SPRAS

TXTLG

Description (long)

TXTMD

Medium description

TXTSH

Short description

TFK002FT

TEXT

VKPBZ


TFK002FT

VKPBZ


25

SAP Online Help

13.05.2003

Account Relationships of a Partner Technical name: 0FC_ACCTREL_ATTR




FI-CA Master Data FI-CA-IO


FI-CA 4.64


No

Use This DataSource transfers information to the InfoSource 0FC_ACCTREL (Account Relationships of a Partner) in BW. This information allows you to determine whether the business partner for a contract account is the contract partner.

Delta Update A delta update is neither possible nor necessary as there is only a small amount of Customizing data.



Table of Origin


VKPBZ

Account relationship

TFK002F

VKPBZ

XKTIN

Indicator: Account holder

TFK002F

XKTIN

Texts for Contract Accounts Technical name: 0FC_ACCNTBP_TEXT


Texts (Master Data)




4.63


No

Use This DataSource extracts texts for contract accounts.


26

SAP Online Help

13.05.2003




Table of Origin


GPART


FKKVKP

GPART

TXTLG

Description (long)

FKKVKP

TXTMD

Medium description

FKKVKP

TXTSH

Short description

FKKVKP

VKONT


FKKVKP

VKBEZ

VKONT

Texts for Contract Account Categories Technical name: 0FC_ACCTCAT_TEXT


Texts (Master Data)




4.63


No

Use This DataSource extracts texts for contract account categories.




Table of Origin


APPLK

Application area

TFK002AT

APPLK

SPRAS

Language key

TFK002AT

SPRAS

TEXT

Text field

TFK002AT

TEXT

VKTYP

Contract account category

TFK002AT

VKTYP


27

SAP Online Help

13.05.2003

Texts for Clearing Reasons Technical Name: 0FC_CLEARR_TEXT


Texts (Master Data)




4.64

Available from Plug-In Release RemoteCube Compatibility

No

Prerequisites This DataSource extracts texts for clearing reasons.




Table of Origin


SPRAS


TFK001AT

SPRAS

TXTLG

Description (long)

TXTMD

Medium description

TXTSH

Short description

TFK001AT

TXT50

AUGRD

Clearing reason

TFK001AT

AUGRD

Installment Plan Source Item Technical name: 0FC_IPL_ORIG_01






4.71


No

Use This DataSource extracts the source items for installment plans.



28

SAP Online Help

13.05.2003



Table of Origin


OPBEL

Document number of contract accounts receivable and payable

DFKKOP

OPBEL

OPUPW

Repetition item in DFKKOP document of contract accounts receivable and payable

OPUPW

OPUPK

Item number in DFKKOP document of contract accounts receivable and payable

OPUPK

OPUPZ

Subitem for a partial clearing in document

DFKKOP

OPUPZ

RECORDMODE

BW Delta procedure: Update mode

ABWBL

Representative document number of contract accounts receivable and payable

DFKKOP

ABWBL

BUKRS

Company code

DFKKOP

BUKRS

GSBER

Business area

DFKKOP

GSBER

SPART

Division

DFKKOP

SPART

GPART


DFKKOP

GPART

VKONT


DFKKOP

VKONT

HVORG

Main transaction of line item

DFKKOP

HVORG

TVORG

Subtransaction of line item

DFKKOP

TVORG

BUDAT

Posting date in the document

DFKKOP

BUDAT

FAEDN

Net due date

DFKKOP

FAEDN

BETRW

Amount in transaction currency

DFKKOP

BETRW

WAERS


DFKKOP

WAERS

BETRH

Amount in local currency

DFKKOP

BETRH

HWAER

Local currency

T001

WAERS

AUGDT

Clearing date

DFKKOP

AUGDT

AUGRD

Clearing reason

DFKKOP

AUGRD


29

SAP Online Help

13.05.2003

ODS Objects in Contract Accounting

FI-CA: Open Items Technical name: 0FC_DS01

Use This ODS object enables you to analyze open, due and overdue items. Since the dataset transferred to BW is determined by key date, all analyses must be carried out by key date. As a chronological analysis period, you can group the open items by due date periods. The drilldown can take place according to business partner attributes, regional structure data, company code, business area, division or dunning procedure. In order to restrict the dataset to the necessary level of detail, we recommend, for example, that you only transfer business partner data of company customers to BW since it only makes sense to analyze this data in great detail.

Key Fields Key Field

Description

0FC_RUNDATE

Run date of mass activity

0FC_RUN_ID

Mass activity ID

0COMP_CODE

Company Code

0NETDUEDATE

Due date for net payment

0BUS_AREA

Business Area

0DIVISION

Division

0CADUNN_PRC

Dunning procedure

Data Fields Data field

Description

0FC_KEYDATE

Key date of analysis

0FC_OI

Open items

0CURKEY_LC

Currency key for local currency

0DOC_ITEMS

Number of Document Items

Navigational Attributes Navigation attribute

Description

0COMP_CODE__0COMPANY

Company for company code


30

SAP Online Help

13.05.2003

Delta Update The data for this ODS object is determined in OLTP by a mass activity (by key date) and loaded in the ODS object using generic extraction. The DataSource is not delta compatible. The old data in the ODS object must be deleted manually.

Installment Plan Header and Item Data Technical name: 0FC_DS02

Use This ODS object is used to complete the installment plan item data with data f rom the installment plan header for reporting and update it in InfoCube 0FC_C04. The completion of the item data with the header data occurs in the start routine of the update rules. Therefore, the header data must be loaded before the item data can be loaded. Even though the separate update of the header data from ODS 0FC_DS03 ensures that the data is consistent, it is updated a second time with the latest header data.


Description

0FCIPL_NUMB

Installment plan number

0FCITEM_RPT

Repetition item

0FCITEM

Item number for contract account receivable and payable

0FCSUBITEM

Subitem

Delta Update This ODS object is intended for use in the AIMD delta update with the 0FC_IPL_ITEM_01 DataSource.

Installment Plan Header Data Technical name: 0FC_DS03

Use This ODS object is used to complete the item data in the 0FC_DS02 ODS object with data from the installment plan header for reporting and update it in InfoCube 0FC_C05. Therefore, the header data must be loaded before the item data can be loaded Even though the separate update of the header data in ODS object 0FC_DS02 ensures that the data is consistent, it is updated a second time. First with the old header data and the second time with the up-to-date version.


Description

0FCIPL_NUMB

Installment plan number


31

SAP Online Help

13.05.2003

Delta Update This ODS object is intended for use in the AIMD delta update with the 0FC_IPL_HEAD_01 DataSource.

Key Figures in Contract Accounting

FI-CA: Open Items Technical name: 0FC_OI

Use Open items represent unfinished business transactions. An unpaid bill item, for example, is an open item until it is paid and cleared.

Technical data Available as of release

FI-CA 4.63 (4.6C)

Aggregation

Total

Exception aggregation

Total

FI-CA: Cleared Items Technical Name: 0FC_CI

Use A cleared item is created when an open item is cleared by a business transaction such as payment or reversal.


FI-CA 4.63 (4.6C)

Aggregation

Total


Total

Charges Receivable Technical name: 0FC_AMNTCHRG

Use This is the confirmation from the collections agency regarding the charges to be paid on a receivable.


32

SAP Online Help

13.05.2003

Technical Data Available as of release

BW 3.2, OLTP 4.71

Aggregation

Total


Total

Amount to Collect Technical name: 0FC_AMTCOLL

Use The Amount to Collect is the receivable to be paid to the collections agency.


BW 3.2, OLTP 4.71

Aggregation

Total


Total

Interest Receivable Technical name: 0FC_AMNTINT

Use This is the confirmation from the collections agency regarding the interest to be paid on a receivable.


BW 3.2, OLTP 4.71

Aggregation

Total


Total

Amount Collected Technical name: 0FC_AMTPAID

Use The amount collected is the confirmation from the collections agency regarding the payment or partial payment of a receivable.


BW 3.2, OLTP 4.71


33

SAP Online Help

13.05.2003

Aggregation

Total


Total

Data Record Counter Technical Name: 0FC_COUNT

Use You can use this counter in the FI-CA content to determine the number of data records.


BW 3.2, OLTP 4.71

Aggregation

Total


Total

Number of Confirmed Items Technical name: 0FC_NUMRESP

Use The Number of Confirmed Items specifies, how many items from the confirmed receivables were cumulated in the data record. It is possible for one receivable to consist of two confirmed items. This occurs if, for example, a receivable with two payments made at different times is cleared.


BW 3.2, OLTP 4.71

Aggregation

Total


Total

Payment Amount Technical name: 0FC_TO_PAY

Use This is the amount that must be paid.


IS-U 4.64


34

SAP Online Help

13.05.2003

Aggregation

Total


Total

Amount Not Collected Technical Name: 0FCAMTNCOLL

Use The amount not collected is the confirmation from the collections agency regarding the unsuccessful collection of a receivable.


BW 3.2, OLTP 4.71

Aggregation

Total


Total

Amount (Time of Deactivation) Technical name: 0FCIPL_AMDC

Use Amount that was open at the time the installment plan was deactivated and that has been changed to a receivable.


BW 3.2, OLTP 4.71

Aggregation

Total


Total

Characteristics in Contract Accounts Receivable and Payable

FI-CA: Start of Clearing Period Technical Name: 0FC_CIFROM


35

SAP Online Help

13.05.2003

Use Clearing transactions of open items take place at different times: Before due date, on the due date or afterwards. In the extractor, you can use Start of clearing periods to determine the period in which you want the system to process clearing information. If you do not do this, the system reads the whole dataset in Contract Accounts Receivable and Payable. You can define the processing period by using this function in conjunction with the characteristic End of clearing periods. Make sure that the number of days between the start and end of clearing always remain the same once the period has been defined. If the historical analysis of the clearing transactions in BW is to be of any use, the length of the clearing periods must always remain the same. Reading clearing transactions over two days will definitely produce different amounts to clearing transactions that are read over two weeks. Use this characteristic as display in the query. It is better to use the characteristic End of the clearing periods as a drilldown or filter. Technical Data Available as of release

FI-CA 4.64 (4.6C)

FI-CA: End of Clearing Period Technical Name: 0FC_CITO

Use Clearing transactions for open items take place at different times: Before due date, on the due date or afterwards. In the extractor, you can use End of clearing periods to determine the period in which you want the system to process clearing information. If you do not do this, the system reads the whole dataset in FI-CA. You can define the processing period by using this function in conjunction with the characteristic Start of clearing periods. Make sure that the number of days between the start and end of clearing always remain the same once the period has been defined. If the historical analysis of the clearing transactions in BW is to be of any use, the length of the clearing periods must always remain the same. Reading clearing transactions over two days will definitely produce different amounts to clearing transactions that are read over two weeks. Use this characteristic as a filter or drilldown in the query. Technical Data Available as of release

FI-CA 4.64 (4.6C)

FI-CA: Clearing Reason Technical name: 0FC_CLEARR


36

SAP Online Help

13.05.2003

Use The clearing reason is saved in the cleared document item and can be used during evaluation. During some clearing transactions, the system determines the clearing reason for the transaction. This happens, for example, during reversal and also automatic clearing of items (for example using a payment program). This characteristic is an important distinguishing characteristic in analysis since clearing caused by reversal and clearing caused by payment triggers two different business transactions. You should, therefore, use this characteristic as a drilldown characteristic in every query. Technical Data Available as of release

FI-CA 4.64 (4.6C)

FI-CA: Clearing Grid as String Technical name: 0FC_DELAY

Use Clearing transactions of open items take place at different times: Before due date, on the due date or afterwards. In analysis, it is not the exact number of days that is important but a grid. In Contract Accounts Receivable and Payable, you can predefine the grid in which the items are to be grouped together during extraction. This enables you to display, for example, all clearing transactions in BW made 10 – 30 days after the due date. The grid can be defined in different ways according to customer grouping since it makes sense to analyze major customers differently to mass customers. We recommend that you do not change the grid definition for a long period of time, so that periods can be more easily compared. We also recommend that you use the grid as a predefined drilldown in every query and maintain text entries manually in BW. Define a counter at the start of the text so that the grid can be sorted in the query. This ensures that the values are more clearly displayed. Technical Data Available as of release

FI-CA 4.64 (4.6C)

FI-CA: Interval Number Technical name: 0FC_INT_NR

Use You can define the number of intervals (processes) the program run is to be divided into before the mass activity for determining open or cleared items is executed. The characteristic Interval number provides the allocation between data and the process to be determined. Technical Data


37

SAP Online Help

Available as of release

13.05.2003

FI-CA 4.63 (4.6C)

FI-CA: Analysis Key Date Technical name: 0FC_KEYDATE

Use This characteristic specifies the date used for the selection of open items in Contract Accounts Receivable and Payable. This means that the system checks in Contract Accounts Receivable and Payable for any items that were open on this key date. You must select the key date during evaluation otherwise the query result will not produce any usable amounts. Technical Data Available as of release

FI-CA 4.63 (4.6C)

FI-CA: Record Number Technical name: 0FC_REC_NR

Use This characteristic identifies the record in a mass activity process. The characteristic is not informative and as a result, is not needed in InfoProviders or queries. Technical data Available as of release

FI-CA 4.64 (4.6C)

FI-CA: Identification of Mass Activity Technical name: 0FC_RUN_ID

Use In conjunction with Date ID of mass activity , this characteristic forms the key that identifies the mass run for determining open or cleared items. Technical data Available as of release

FI-CA 4.63 (4.6C)


38

SAP Online Help

13.05.2003

FI-CA: Date Identification of Mass Activity Technical name: 0FC_RUNDATE

Use In conjunction with Identification of Mass Activity , this characteristic forms the key that identifies the mass run for determining open or cleared items. Technical data Available as of release

FI-CA 4.63 (4.6C)

Account Category Technical name: 0CAACCT_CAT

Use The account category classifies the type of account. It also determines the field control of this class and its associated/readable fields. Technical data Available from Release

IS-U 4.63 (4.6C), BW 3.0/01

Application Area Technical name: 0CAAPPLK

Use The application area (known as application component in OLTP) classifies the total application for Contract Accounts Receivable and Payable. You generally only use one application area, for example application area R (Utilities Industry). Technical data Available from Release

IS-U 4,51 (4.6B), BW 3.0/01

Contract Account of Collector Technical name: 0CACOLL_ACC

Use If you have grouped together contract accounts for collective bill accounts in the OLTP System, and therefore want to evaluate amounts and quantities (for example), you can activate this characteristic and include them in the sales statistics as a characteristic (for


39

SAP Online Help

13.05.2003

example). As a result the contract accounts are linked in BW and you can select them by the characteristic. Technical data Available as of release

IS-U 4.61 (4.6B), BW 3.0/01

Contract account (partner-independent data) Technical name: 0CACONT_ACC

Use This characteristic contains additional information about the contract account. This data is partner-independent information such as the contract account category. Technical data Available as of release

IS-U 4.61 (4.6B), BW 3.0/01

Dunning Block Reason Technical name: 0CADUNN_BLO

Use You can use the dunning block reason to analyze why and how many items or contract accounts are blocked for dunning. Based on the specification in your source system, you can use this characteristic to create analyses for dunning blocking. Technical data Available from Release

IS-U 4.61 (4.6B), BW 3.0

Grouping Category – Dunning Notices Technical name: 0CADUNN_GRP

Use You can use the dunning notices grouping category to group together contract accounts, in order to consider their items together in the dunning run. This means that you can group together items of a business partner that are due for dunning, for all his/her contract accounts. Technical data Available from Release


IS-U 4.61 (4.6B), BW 3.0/01

40

SAP Online Help

13.05.2003

Dunning Procedure Technical name: 0CADUNN_PRC

Use The dunning procedure characteristic enables you to analyze contract accounts or document line items and to valuate customers’ payment history. Technical data Available from Release

IS-U 4.61 (4.6B), BW 3.0/01

Interest Key Technical name: 0CAINT_KEY

Use The interest key characteristic is used in the contract account to calculate interest for open items, provided that no separate key is stored in the business transaction. Technical data Available from Release

IS-U 4.63 (4.6C), BW 3.0/01

Main Transaction: Defines Posting Procedure with Subtrans. Technical name: 0CAMNTRANS

Use The main transaction and the sub-transaction together form the posting information for the document. The transactions are used to define account determination in the Financial Accounting (FI) and Controlling (CO) components. They are also used to define rate steps. Technical data Available as of release

IS-U 4.61 (4.6B), BW 3.0/01

Settlement Category Technical name: 0CASETTLCAT


41

SAP Online Help

13.05.2003

Use The settlement category key is stored in the contract account. It is used in combination with the settlement type to define the settlement rules, and thus to settle open items. Technical data Available from Release

IS-U 4.63 (4.6C), BW 3.0/01

Settlement Type Technical name: 0CASETTLTYP

Use The settlement type key refers to the business transaction in automatic clearing postings. It is used in Contract Accounts Receivable and Payable to determine the payment allocation rules or settlement rules. Technical data Available from Release

IS-U 4.63 (4.6C), BW 3.0/01

Subtransaction: Defines Posting Procedure with Main Trans. Technical name: 0CASUBTRANS

Use The sub-transaction and the main transaction together form the posting information for the document. The transactions are used to define account determination in the Financial Accounting (FI) and Controlling (CO) components. They are also used to define rate steps. Technical data Available as of release

IS-U 4.61 (4.6B), BW 3.0/01

Contract Account (Partner-Dependent Data) Technical name: 0FC_ACCNTBP

Use This characteristic contains partner-dependent data for the contract account. You use the navigational attributes to obtain information about the relationship with the business partner, the payment conditions and the valid budget billing procedure. Technical data


42

SAP Online Help

13.05.2003


IS-U 4.63 (4.6C), BW 3.0/01

Compounding

0CACONT_ACC

Contract Account Category Technical name: 0FC_ACCTCAT

Use With this characteristic you can group and select contract accounts according to the contract account categories, dependent on the specification in your OLTP System. Technical data Available as of release

IS-U 4.63 (4.6C), BW 3.0/01

Relationship of Business Partner to Contract Account Technical name: 0FC_ACCTREL

Use The characteristic OFC_ACCTREL identifies the business partner, as account holder, contract partner or claimant (in case of insurance companies) for example. Technical data Available from Release

IS-U 4.63 (4.6C) BW 3.0/01

Bank Details ID for Incoming Payments Technical name: 0FC_INBNKID

Use The bank details ID is provided by the bank details specified in the business partner for the contract account. For payment runs, the bank details ID is used to carry out the direct debit. If a business partner has several bank details for different contract accounts, you can select them using the bank details ID. Technical data Available from Release


IS-U 4.63 (4.6C), BW 3.0/01

43

SAP Online Help

13.05.2003

Tax Rate Technical name: 0FC_TAXRATE

Use You can use the tax rate to select sales for customers with VAT reductions or fixed rates. You can valuate sales volume/quantities for these customers, based on this information. Technical data Available from Release

IS-U 4.63 (4.6C), BW 3.0/01

Collections Agency Technical Name: 0FC_COLLAC

Use The Collections Agency characteristic relates to the business partner (0BPARTNER) and uniquely identifies a collections agency. As this involves a reference to the business partner, the collections agency master data is loads using the DataSource of the business partner. Technical Data Available as of release

BW 3.2, OLTP 4.71

Submission Frequency Technical name: 0FC_NUMSUBM

Use This characteristic specifies how often a receivable is submitted to a collections agency. Technical Data Available as of release

BW 3.2, OLTP 4.71

Execution Date of the Transaction Technical name: 0FC_PROCDAT

Use This characteristic specifies the date on which a submission was created or changed. This means that all transactions can be displayed with reference to the submission date. Technical Data


44

SAP Online Help


13.05.2003

BW 3.2, OLTP 4.71

Date of Submission to the Collections Agency Technical Name: 0FC_SUBMDAT

Use This characteristic specifies the date on which the receivable was submitted to the collections agency and remains constant for all transactions relating the submitted item. Technical Data Available as of release

BW 3.2, OLTP 4.71

Submission Status of the Receivable Technical Name: 0FC_SUBMSTAT

Use The submission status specifies the status of the receivable. You can use it to determine which receivables were sold, for example. The characteristic is defined as a master data characteristic so that it can load submission status texts. Technical Data Available as of release

BW 3.2, OLTP 4.71

Start Date Technical name: 0FCDATEFROM

Use The start date is a general characteristic of the FI-CA content. It should be interpreted in each individual business context. When taken in context with the installment plan, it is the date when the first installment payment is due. Technical data Available as of release

BW 3.2, OLTP 4.71


45

SAP Online Help

13.05.2003

End Date Technical name: 0FCDATETO

Use The end date is a general characteristic of the FI-CA content. It should be interpreted in each individual business context. When taken in context with the installment plan, it is the date the last installment payment is due. Technical Data Available as of release

BW 3.2, OLTP 4.71

Deactiviation Date Technical name: 0FCDEACDATE

Use The deactivation date is a general characteristic of the FI-CA content. It should be interpreted in each individual business context. It specifies the time at which the installment plan was ended before schedule. Technical Data Available as of release

BW 3.2, OLTP 4.71

Installment Plan Category Technical name: 0FCIPL_CAT

Use The Installment Plan Category is an evaluation criterion that you define in Customizing. The characteristic is defined as a master data characteristic so that it can load texts. Technical Data Available as of release

BW 3.2, OLTP 4.71

Installment Plan Number Technical name: 0FCIPL_NUMB

Use The installment plan number uniquely identifies the installment plan and allows you to display either individual plans or all items that belong to one installment plan.


46

SAP Online Help

13.05.2003


BW 3.2, OLTP 4.71

Item Number for Contract Accounts Receivable and Payable Technical name: 0FCITEM

Use The item number identifies an installment in connection with the installment plan number and the repetition item of an item. Technical Data Available as of release

BW 3.2, OLTP 4.71

Repetition Item Technical name: 0FCITEM_RPT

Use The repetition item identifies an installment in connection with the installment plan number and the item of an installment. Technical Data Available as of release

BW 3.2, OLTP 4.71

Receivable Sold Technical name: 0FCITEMSOLD

Use This characteristic indicates a receivable that was sold to the collections agency. You can use it to analyze receivables that were submitted and sold without having to take the submission status into account. Technical Data Available as of release

BW 3.2, OLTP 4.71


47

SAP Online Help

13.05.2003

Transaction Duration Technical name: 0FC_PROCDURA

Use This characteristic specifies the number of days since submission of the receivable and st confirmation by the collections agency. For example, if a receivable is submitted on the 1 of th the month and confirmed as paid on the 15 of the same month, the transaction duration is 14 days. Technical Data Available as of release

BW 3.2, OLTP 4.71

Subitem Number Technical name: 0FCSUBITEM

Use The subitem number identifies an installment in connection with the installment plan number, the repetition item, and the item number. Technical Data Available as of release

BW 3.2, OLTP 4.71

Process Chain in Contract Accounts Receivable and Payable

Process Chain: Installment Plan Delta Load and Update Purpose The process chain: Installment Plan Delta Load and Update •

Loads the header data and item data of the installment plan and updates it to the corresponding ODS objects and InfoCubes

•

Contains all processes that are necessary for the delta load of the installment plan data

•

Takes into account the sequence in which the header data and item data are to be loaded in order to avoid updating irrelevant data records

•

Is assigned to the Contract Accounts Receivable and Payable component.


48

318915021-BW-320-FICA-e.pdf

Recommend Documents