Integration

PDF download from SAP Help Portal:

http://help.sap.com/erp2005_ehp_05/helpdata/en/0f/7dcb53f0f67314e10000000a174cb4/frameset.htm

Created on December 09, 2014

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.

Note

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

© 2014 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 permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE
and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by
SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, 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 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 Germany and other
countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC Page 1 of 14
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Table of content
1 Integration
1.1 Integration with Other Insurance Components
1.2 General Ledger Accounting
1.3 Cash Management
1.4 Controlling
1.4.1 Updating CO-PA
1.5 Sales and Distribution
1.5.1 Transferring SD Billing Documents to FI-CA
1.6 Integrating External Billing Systems
1.7 Integration with Funds Management (PSM-FM)
1.8 Dispute Management in Contract Accounts Receivable and Payable
1.9 Integration with SAP Credit Management
1.10 Integration with SAP Global Trade Services
1.11 Debt Recovery Management (FIN-FSCM-DR)
1.12 Integration with Customer Relationship Management (CRM)

PUBLIC Page 2 of 14
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 1 Integration

Use
This component provides you with comprehensive functions for integration with other components.

Features
Collections/Disbursements provides interfaces and functions for data exchange with the following components:
Integration with Other Insurance Components
Forwarding Clearing Information
Determination of the Paid-To Date
Information Container
Reinsurance
In-force business management system/policy management
Claims management system
Other business areas
G/L Accounting
Cash Management
Controlling
Sales
Integration with External Billing Systems
Integration with Funds Management
SAP Dispute Management
Integration with SAP Credit Management
Integration of SAP Global Trade Services
Internal Collection Procedure
Settlement in Contract Accounts Receivable and Payable
Integration with Customer Relationship Management

1.1 Integration with Other Insurance Components

Use
As the 'settling system', Collections/Disbursements (FS-CD) is responsible for subledger accounting for insurance companies. To allow you to manage this
subledger accounting, the appropriate 'calculating' systems (Claims Management, Policy Management, Reinsurance) must provide Collections/Disbursements
with information and posting data. A central FS-CD interface is available for this (see Interfaces and Data Transfer Tools ).
To allow the participating insurance systems to receive relevant posting information, to derive any necessary follow-up activities, you must also transfer information
from Collections/Disbursements to other systems for certain business transactions and situations.

Features
The following functions and components are available for data exchange with other insurance components:
Forwarding Clearing Information
Determination of the Paid-To Date
Quotation Monitoring
Information Container as medium for data transfer to recipient systems
Reinsurance

1.2 General Ledger Accounting

Purpose
This component enables the periodic update of the general ledger with postings from Contract Accounts Receivable and Payable .

Features
The transaction figures are not automatically updated in the general ledger during posting in Contract Accounts Receivable and Payable . Instead, the data is
summarized and recorded periodically in the general ledger to improve system performance and to limit the volume of documents in the general ledger.
The system groups the documents from Contract Accounts Receivable and Payable (FI-CA) automatically and records posting totals for each group. You have to
transfer these totals to the postings in the general ledger later. Each group is uniquely identified by a reconciliation key. If no further postings are to be added to a
group, the reconciliation key for the group must be closed. No further postings are possible under a closed posting key and you can transfer the posting totals
recorded under this key to general ledger accounting.
There are posting programs and reconciliation programs available for transferring data to the general ledger. The prerequisite for these programs is that you run
General Ledger Accounting (FI-GL) and Contract Accounts Receivable and Payable (FI-CA) in the same system. If you run General Ledger Accounting in a

PUBLIC Page 3 of 14
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 separate system, in the system in which you run FI-CA, you have to configure the component General Ledger Accounting (FI-GL) such that a data transfer from
FI-CA is possible. You can then transfer the data to the central general ledger using ALE methods of the component General Ledger Accounting (FI-GL).

1.3 Cash Management

Purpose
This component enables you to update data in Cash Management (TR-CM) .

Features
This update is madedirectly when you post a document in Contract Accounts Receivable and Payable . This means that the Cash Management liquidity forecast
and cash position are always up-to-date.
In the contract account master record, you can define the following data for updating the liquidity forecast:
Planning group
This way, contract accounts with collection authorization can be considered separately from contract accounts to be paid on demand. The system proposes
the planning group when you enter a document.
Additional days
These days are considered when determining the expected cash receipt date. The due date for net payment or the cash discount date (if cash discount was
agreed) is used as the baseline date for this.
Line items that are locked for payment can be assigned to an alternative planning group automatically.
In the G/L account master record, you define a planning level for G/L accounts that require the cash position to be updated. The system determines the planning
level when you post the document and enters it in the G/L item.
For mass postings that run in parallel processes, waiting time may occur due to competing accesses during the update of data for Cash Management . For
these postings, Contract Accounts Receivable and Payable offers a parallel update mode that you can activate for specific categories of mass runs in the
Implementation Guide for Contract Accounts Receivable and Payable under Technical Settings Activate Parallel Update of Cash Management . Cash
Management is then updated at the end of each process. If the process is terminated before the Cash Management update, the update takes place when you
close the relevant reconciliation key. If the update also fails here, you can transfer the data recorded separately individually. To do this, in the SAP menu choose
Periodic Processing Cash Management Transfer .
Utilities Industry (IS-U) Component
The system automatically determines the planning group in the contract account when you transfer billing documents and then saves it in the corresponding line
items.
Insurance (FS-CD) Industry Component
The system automatically determines the planning group in the contract account for the debit entry and then saves it in the corresponding line items.

1.4 Controlling
Purpose
This component enables data to be updated in Overhead Cost Controlling (CO-OM) .
Features
Overhead Cost Controlling is updated automatically during the general ledger update.

1.4.1 Updating CO-PA

If you want to transfer account assignment data from Contract Accounts Receivable and Payable to CO-PA, choose one of the following paths:
Role Transfer General Ledger and Profitability Analysis(SAP_FI_CA_TRANSFER_GL_PROFIT) Transfer to Profitability Analysis
SAP Menu Periodic Processing Forward Postings Execution Transfer to Profitability Analysis .
In the SAP menu under Periodic Processing Forward Postings Execution Transfer to Profitability Analysis (Mass Run), you can also use this
function as a mass activity.
You can display reconciliation keys that are closed but were only partially transferred or not at all with report RFKKABS5.
Using report RFKKCO20 you should regularly carry out a reconciliation between Profitability Analysis (CO-PA) and Contract Accounts Receivable and Payable
(FI-CA) (SAP menu: Periodic Processing Forward Postings Reconciliation Checks/Adjustments Check CO-PA Documents ). Make sure you read
the report documentation.To process large volumes of data, in the SAP menu under Periodic Processing Forward Postings Reconciliation
Checks/Adjustments Check CO-PA Documents (Mass Run), you can use this function as a mass activity.
For more information about scheduling program runs, see the section Functions for Scheduling Program Runs .

1.5 Sales and Distribution

As part of the integration of Contract Accounts Receivable and Payable (FI-CA), the Utilities (IS-U/CCS), Telecommunications (IS-T), Insurance (FS-CD),
and Public Sector Contract Accounts Receivable and Payable (PSCD) industry solutions can transfer bills from Sales and Distribution (SD) to Contract
Accounts Receivable and Payable instead of to standard Accounts Receivable Accounting (FI-AR).

1.5.1 Transferring SD Billing Documents to FI-CA

Features

PUBLIC Page 4 of 14
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 You can integrate Sales and Distribution (SD) with Contract Accounts Receivable and Payable (FI-CA) by:
Activating in Customizing the direct posting of SD billing documents in FI-CA based on the customer account groups
Transferring SD billing documents to invoicing of the industry component Utilities (IS-U) or to Invoicing in Contract Accounts Receivable and Payable
This transfer is made using sample documents that are based on billing category U (billing request) of the billing type.
Automatically transferring SD billing documents to Invoicing in Contract Accounts Receivable and Payable
The transfer is based on both the customer account group and the billing type; the accounting interface in Sales and Distribution (SD) is still processed
during the transfer, but no direct postings are made. Instead of creating posting documents, the system generates special invoicing orders that can be
processed by Invoicing in Contract Accounts Receivable and Payable. During invoicing, the system derives postings in FI-CA for the SD billing
documents, and – as necessary – clears down payments.
After the transfer, you can:
Follow the further processing steps in Invoicing in Contract Accounts Receivable and Payable in the document flow of Sales and Distribution (SD).
The invoicing order is displayed as a follow-on document for the SD billing document. Using the navigation to the document display for the invoicing
order, you can go directly to the monitoring of the invoicing orders in Invoicing in Contract Accounts Receivable and Payable. Once the invoicing order
has been processed, then the system displays the invoicing document (instead of the invoicing order) as well as the posting document in FI-CA as
follow-on documents.
Print the invoicing order for an SD billing document together with the invoicing orders of other source processes in one common invoice
Use the central functions of Contract Accounts Receivable and Payable on open items that were created in invoicing from SD billing documents
That means that you can include open items arising from SD billing documents in various processes of Contract Accounts Receivable and Payable:
dunning, interest calculation, and automatic and manual account maintenance. The system treats open items that were created in Invoicing from SD
billing documents the same as all other open items of a contract account.

( ) If you update Profitability Analysis (CO-PA) directly in the RWIN interface (for example, during direct posting to FI-CA without using invoicing), the system
determines the value fields dependent on the condition type.
If you update Profitability Analysis (CO-PA) in FI-CA (for example, during processing of SD billing documents in invoicing), the system determines the value
fields dependent on the cost element.

Prerequisites
If you want to transfer SD billing documents to Contract Accounts Receivable and Payable, you have to make various settings in Customizing for both Contract
Accounts Receivable and Payable and Sales and Distribution (SD).
For each account group, you define whether billing documents are to be transferred to Accounts Receivable Accounting (FI-AR) or to Contract Accounts
Receivable and Payable (FI-CA). In the account group, you specify whether the related customers are to be transferred to FI-AR or FI-CA during SD billing.

Prerequisites in Sales and Distribution

You have specified the receivables accounts for Contract Accounts Receivable and Payable in the reconciliation account determination in Sales and
Distribution (see Customizing for Sales and Distribution under Basic Functions Account Assignment/Costing Reconciliation Account Determination
). It is especially important that you entered a G/L account with reconciliation indicator V (Contract Accounts Receivable and Payable) in the activity
Assign G/L Accounts .
When entering an SD order, you must select a contract account. This contract account must be assigned to the FI-CA business partner. If there is exactly
one contract account for the payer, this contract account is transferred automatically to the order.

Prerequisites in Contract Accounts Receivable and Payable

If you create a business partner for the customer in FI-CA, then you have to enter an SD sample customer so that the SD views required for creating the
order are available in the background. The system creates an SD customer with a customer number identical to that of the FI-CA business partner.
Direct posting of SD billing documents in FI-CA takes place at the level of the customer account group. This means that for each account group, you define
whether SD billing documents for these customers should be transferred to Accounts Receivable (FI-AR) or to Contract Accounts Receivable and Payable
(FI-CA). (See Customizing for Contract Accounts Receivable and Payable under Integration Sales and Distribution Define Posting to FI-CA for
Customer Account Groups.) .)Note that when you create an order you can only enter customers from one of the two account groups as being the payer.
This means that you can use either only customers that trigger a posting in FI-AR during invoicing, or only customers that trigger a posting in FI-CA. Note
that you are not allowed to activate the SD/FI-CA transfer for one-time account groups.
You make specifications for the transfer to invoicing in Customizing for Contract Accounts Receivable and Payable under Integration Sales and
Distribution Define Posting to FI-CA for Customer Account Groups and under Define Settings for Transfer to Invoicing. As an alternative, you can
make these settings in Customizing for Sales and Distribution under Billing Billing Documents Integration with Contract Accounts Receivable and
Payable (FI-CA) .
The system derives the main and subtransactions used in Contract Accounts Receivable and Payable from the SD billing documents during the transfer
based on your Customizing settings. (See Customizing for Contract Accounts Receivable and Payable underIntegration Sales and Distribution
Derive Main/Subtransaction from SD Information. )
The system also derives the document type with which SD billing documents are posted in Contract Accounts Receivable and Payable during the transfer
of the SD billing documents based on your Customizing settings. (See Customizing for Contract Accounts Receivable and Payable under Integration
Sales and Distribution Derive Document Type from SD Billing Doc Data.)
Using event 4000, you can enrich the billing data. (See Customizing for Contract Accounts Receivable and Payable under Program Enhancements
Define Customer-Specific Function Modules. )

Features

Automatic Reconciliation Key Determination

The system automatically determines the reconciliation key during the transfer of SD billing documents. This function is the same for individual bills and mass
runs. In both SD billing methods, the reconciliation key is assigned according to the same procedure. The key is determined as follows:SDxxxxyyy_zz
The components of this key are explained in the table below:

PUBLIC Page 5 of 14
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Part of Key Meaning

XXX Current year

YYY Current day in year

ZZ Sequence number

The system assigns a new reconciliation key for SD billing documents for each day of the year. If this reconciliation key is closed during the course of the day, or if
two processes try to open the same reconciliation key simultaneously, a new (second) reconciliation key is opened with the next higher sequential number.
Reconciliation keys generated this way are only permitted for posting SD billing documents. The reconciliation key is not closed automatically.

Automatic Determination of Reconciliation Account for SD Billing Documents

The system automatically determines the reconciliation account when creating the SD billing documents for Contract Accounts Receivable and Payable based on
your Customizing settings. (See Customizing for Sales and Distribution under Basic Functions Account Assignment/Costing Reconciliation Account
Determination. )
Reconciliation Account Determination for Down Payment Requests in SD
During the transfer of SD down payment requests (billing documents) to Contract Accounts Receivable and Payable, event 1101 is run to determine the
reconciliation account.
The industry components Utilities and Telecommunications (IS-UT) execute function module ISU_EVENT_1101 (posting area R000 or T000).
The industry component Contract Accounts Receivable and Payable (FI-CAX) executes the function module FSC_EVENT_1101 (posting area S000).
In each of the mentioned posting areas, you have to enter a G/L account with the reconciliation indicator V (Contract Accounts Receivable and Payable).

Default Value for Payment Conditions

In the SD order, the default value for payment conditions is derived from event 4010 in Contract Accounts Receivable and Payable, provided that a corresponding
function module has been defined in this event. If no function module has been defined or if no default value can be found, then the system determines the terms of
payment in the standard SD manner.
For the industry components Utilities and Telecommunications, a function module has been defined in event 4010 in Contract Accounts Receivable and Payable.
This function module determines the default value for the terms of payment from the contract account named in the order header. Depending on the order type, it
determines either the payment conditions for incoming payments or for outgoing payments, in accordance with the relevant payment conditions defined in the
contract account.

Contract Account in the Order

The Contract Account field is available as an entry field for Contract Accounts Receivable and Payable in the header and items in the SD order. The SD
business partner whose contract account is specified is the payer of the order. If there is exactly one contract account for the payer, this contract account is
transferred automatically to the order. If there is more than one contract account, a selection list appears when you create an order. You can enter a separate
combination of payer and contract account for each order item. The billing documents are then split for different contract accounts.
The contract account from the accounting viewpoint has to be entered in the order header.
From the accounting viewpoint, the following entry fields are not considered during the transfer to Contract Accounts Receivable and Payable:
Dunning Key
Dunning Lock
Payment Method
Assignment
In event 4040, you can restrict the selection of contract accounts when you create/change an SD order.
Contract Object in the Order
You can also make the Contract Object field available as an entry field in the SD order. To do so, you make the necessary settings in Customizing for Contract
Accounts Receivable and Payable under Integration Sales and Distribution Permit Contract-Referenced Postings from SD . After you define the
contract object field, it appears in the header data on the Accountingtab page and in the items on the Billing Documenttab page for the order (similar to the
situation on the contract account).
When you create a customer order, after entering the business partner, you can select a combination of contract object and contract account. You also have the
option of choosing the contract object using the input help.
The system runs a check when a contract object is entered. If the contract object you entered does not exist, you can create it.
The contract object is adopted by subsequent documents (usually a billing document).
When the billing document is released for accounting, then the contract object is adopted by the FI-CA document.

Business Area Determination

In the SD order, the system derives the default value for the business area using event 4020 of Contract Accounts Receivable and Payable, provided that a
corresponding function module has been defined in this event. If no function module has been defined, or if no default value can be found there, then the business
area is determined in the standard SD manner.
For the industry components Utilities and Telecommunications, separate function modules have been defined for each component that determine the default value
for the business area from the contract account specified in the order header.

Restriction on the Payment Conditions that Can Be Used

Due to the payment control in Contract Accounts Receivable and Payable (due date for cash discount + discount% / due date for net payment), you cannot use all
standard FI terms of payment. The following restrictions apply:
Only one cash discount date can be defined. The second cash discount date is interpreted as being the net due date and must have 0.00 as the discount
percentage rate.
The terms of payment must be defined for the entire month and be valid throughout this period

PUBLIC Page 6 of 14
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Installment payment conditions are not supported.
It is not possible for you to use the feature of the industry component Utilities of using a factory calendar to convert terms of payment to the corresponding
due dates.
A check is made to ensure that payment terms are suitable for use with FI-CA. This check is made during assignment of the payment condition in the sales and
distribution area data (customer billing), and also when the SD order is created.

Reconciliation CO-PA and FI-GL

Reconciliation between the individual components can only be made for closed posting periods and for points in time at which all Contract Accounts Receivable
and Payable reconciliation keys have been transferred completely to the general ledger.

Completing Documents
The system enriches the customer line items of the SD billing document that is transferred to the financial accounting interface with the following information:
General information (for example, reference details)
Information from the contract account (for example, account determination ID)
Information on main and subtransactions for each company code and division (such as dunning, interest, or payment)
The business partner items in Contract Accounts Receivable and Payable are created from the customer line items.
The information is derived using event 4000, which is called to supplement customer items and G/L account items.
The main and subtransactions of an SD document are determined in event 4030. In this event you have access to all of the information in an SD billing document,
which means that a more detailed transaction determination is possible here, in contrast to Customizing.

Down Payment Requests/Down Payment Clearing

You can use the functions implemented in SD for creating down payment requests from billing plans as well as for the subsequent down payment clearing for
down payments made.

Installment Plan

The system can create installment plans automatically. For it to do so, call function module FKK_INSTSD_WRITE in event
4000 and fill the structure I_INST. For example, you can fill it with various installment plan categories dependent on your own
customer-specific definition (such as the billing type).

Invoicing External Transactions

You can use the function for invoicing external transactions. For this, the contract account must also be included in the communication structures.

Reversal of SD Billing Documents

When reversed billing documents are transferred to accounting, the accounting documents arising out of this are flagged as reversed and the open items are
cleared immediately. If this cannot be done, an accounting document is created with the +/- signs reversed. This may occur, for example, if the invoice has
already been cleared or if the payment order has already been created.

Note
No Reversal of SD Bill in the Case of Subrogation
If the change of customer and the receivables (open items) are transferred, the SD billing document can no longer be reversed after that point. The billing
document cannot be reversed, since the open item(s) were cleared in Contract Accounts Receivable and Payable with reason 21 (subrogation).

Display FI-CA Documents

In the document flow for Sales and Distribution (SD), you can display FI-CA documents and archived FI-CA documents.

Enhancements for Argentina

The interface between SD and Contract Accounts Receivable and Payable meets special requirements in Argentina. For more information, see SAP Note
211917.
Reconciliation Between Sales and Distribution (SD) and Contract Accounts Receivable and Payable
There is a report you can use for reconciling FI-CA documents and SD billing documents. On the SAP Easy Access screen, choose Periodic Processing
Reconciliation of Documents with Source Data Reconciliation with SD Billing Documents . The report determines the differences between SD billing
documents and FI-CA documents, and displays an overview of the SD billing documents and the print documents and FI-CA documents generated from them. For
more information, see the report documentation.

1.6 Integrating External Billing Systems

Purpose
For exchanging data between Contract Accounts Receivable and Payable (FI-CA) and an external (billing) system, in SAP Exchange Infrastructure (XI), SAP
provides various different message interfaces.

PUBLIC Page 7 of 14
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Notes on Implementation
Make sure that the process integration content of the software component FI-CA has been imported to your integration repository. The process integration content
for Contract Accounts Receivable and Payable is on SAP Service Marketplace. Here the content is displayed as a patch under the respective industry solution
(for example, SAP IS-T).

Features
You configure the link between the message interfaces of the software component FI-CA and external systems in the Integration Directory of your Integration
Server (see Basics ).
For more information about the interfaces and their use, see the following section. You can use the following message interfaces in Contract Accounts Receivable
and Payable for the connection to external (billing) systems:

Interface of SAP Exchange Infrastructure Description

FICAExterningBillingNotification_In Document transfer with revenue item

OpenItemAccountingSummaryNotification_Out Outbound interface of business partner information

BillImageRequest_Out External archive connection

The process integration content under the software component FI-CA still contains the IDocs ContracDocument_Create and ContracDocument_Reverse
and the BAPI BAPI_CTRADOCUMENT_GETLIST as imported objects.

1.7 Integration with Funds Management (PSM-FM)

Purpose
SAP supports the integrated use of Funds Management with Contract Accounts Receivable and Payable, the industry component Utilities, a nd the industry
component Public Sector Contract Accounts Receivable and Payable . For all other industry components that use Contract Accounts Receivable and Payable
, the integration with Funds Management is supported in a customer project.
The integration of Contract Accounts Receivable and Payable (FI-CA) and Funds Management (PSM-FM) enables you to forward actual data from FI-CA to
PSM-FM on a totals basis and thereby manage budget planning. By doing this, you can map the areas of responsibility within your organization in a hierarchical
structure, and control both the movement of financial funds (revenues and expenditures) as well as the budget at your disposal.

Note
Note that there are restrictions for forwarding actual data from FI-CA. For more information, see SAP Note 686383. You can only use FI-CA with Fund
Accounting if PSM-FM is active.

Caution
Note that moving revenue and expenditure postings to FI-CA can restrict the availability control function in Funds Management . For more information, see
FM Availability Control in Contract Accounts Receivable and Payable .

For more information about using Funds Management , see the Accounting documentation under Public Sector Management Funds Management .

Integration
The FM document data is updated simultaneously when you transfer totals records from FI-CA to the general ledger (FI-GL) using program RFKKGL00 (see SAP
Easy Access screen: Periodic Processing Forward Postings Execute General Ledger Transfer ).
Receivables, down payments, payments, and clearing transactions are updated in FI-CA automatically. The system updates the data online in the totals tables of
FI-CA.
If Funds Management is active and you have activated the check of old activities (FMISPS-AUTHACT_OLD) in Customizing for Funds Management, the system
checks the Funds Management account assignments when you post, edit, and display documents and requests, and in the account balance display. The
system checks the authorization objects for the account assignment elements for Funds Management (commitment item, funds center, fund).
In the document (business partner items and general ledger items), the FM account assignments are on the tab page Funds Management .
Subsequent FM Activation
You can integrate Funds Management with FI-CA at a later point in time (after FI-CA is already active), or you can post to additional company codes that were
previously not assigned to an FM area using active FM integration. In doing so, you can write a dummy FM account assignment to all existing documents that
were created before the integration with Funds Management.
FM Account Assignment Logic for Documents Created Automatically
To derive FM account assignments in documents created automatically, you have to define FM derivation rules in Customizing. The system derives the
automatically assigned FM account assignments from the business transaction data.
FM Account Assignment Logic for Documents Created Manually
In manual document entry, entry of requests, and posting of cash security deposits, you can use derivation rules for determining default values. On the processing
screen, the commitment item, fund, funds center, and functional area are ready for input. If you do not enter an FM account assignment, the system derives these
values automatically from the rules defined.
FM Account Assignment Logic for Doubtful Entries and Individual Value Adjustments
In both business transactions, the posting data is provided with the FM account assignment automatically. The system determines the FM account assignment

PUBLIC Page 8 of 14
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 In both business transactions, the posting data is provided with the FM account assignment automatically. The system determines the FM account assignment
data using the derivation rules.
You can make individual value adjustments with tax adjustments using an installation-specific function module defined for event 1750. The FM account
assignment is adjusted accordingly.
FM Account Assignments for Posting Deferred Revenues
The system transfers the FM account assignment from the original document to the deferred revenue posting automatically. To use this function, you have to
include the structure IFKKFMOBJ in table FKKDEFREV.

Prerequisites
Funds Management
For information on activating the Funds Management (PSM-FM) component, see Customizing for Public Sector Management under Funds Management
Government Prepare Funds Management Installation.
Contract Accounts Receivable and Payable
If you want to use Funds Management, you have to activate the business function FI-CA Core, Funds Management (FICA_FM) in the Switch Framework .
When you activate the function, the system automatically writes the structures SI_FKKFMOP and SI_FKKFMOPK with the FM table fields in the document tables.
Make sure that you activate the EA-PS business function in the Activate Business Functions Customizing activity.
Currently, you cannot use the account assignment element Grant of the component Public Sector Management.
SAP also provides the following function modules as standard modules for the enhancement:
Event 0032: FKK_FM_SAMPLE_0032
Event 1102: FKK_EVENT_FM_1102
Event 1108: FKK_FM_EVENT_1108
Event 1119: FKK_FM_EVENT_1119
If Funds Management is not active, the function modules are not processed.
In order to be able to process the FI-CA data in Funds Management , you have to define rules for defining FM account assignments in Customizing for Contract
Accounts Receivable and Payable under Integration Funds Management (PSM-FM) . Contract Accounts Receivable and Payable uses the derivation
strategy of Funds Management (see Customizing for Funds Management Government under Master Data Allocations to Account Assignments from Other
Components Define Account Assignment Derivation). ).If you want to continue to use the derivation strategy FMCADERIVE in Contract Accounts Receivable
and Payable, you have to set the indicator Use Derivation Strategy from Contract Accounts Receivable and Payable in the maintenance view
TFK_FMDERIVSTRAT. Call up the view directly using transaction SM30. Note, however, that SAP no longer supports this derivation strategy.
If you want to use the Fund Accounting component, you have to:
Activate the fund in Customizing for Public Sector Management under Basic Settings Activate Account Assignment Elements. .In Customizing for
Contract Accounts Receivable and Payable , you can see the activation status in the activity Fund Accounting Activation Status under Integration
Funds Management (PSM-FM) . If the fund is activated, the system creates additional fund clearing lines that ensure that the balance is cleared per
document and company code. Define the G/L accounts for Fund Accounting in the activity Define Accounts for Fund Clearing.
Define the function module FKK_FM_SAMPLE_0032 ( Fund Accounting: Add Line Items ) for event 0032 in Contract Accounts Receivable and Payable
.
SAP provides this function module as a standard function module. If Fund Accounting is not active, the function module is not processed.
You enter the FM account assignment for a subsequent FM activation in Customizing for Contract Accounts Receivable and Payable under Integration
Funds Management (PSM-FM) . For more information about converting existing documents, see the Customizing activity.

Features
The figure depicts the functional relationships for updating document data in Contract Accounts Receivable and Payable in Funds Management, and
Accounting .

PUBLIC Page 9 of 14
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 1. Assigning an FM account assignment
The integration with Funds Management requires that each document item in the document must be assigned to one FM account assignment.
For manual document entry, you can fill these FM account assignment fields. If you do not make any entries here, the system automatically assigns the FM
account assignments you defined in the derivation rules when you save the document. The derivation rules are especially required for documents created
automatically. In any one document, the amounts for each FM account assignment must be cleared. For more information, see Derivation Logic for Funds
Management (PSM-FM) .
2. Classification in FM categories and transaction classes
Documents are saved in the header and item tables of Contract Accounts Receivable and Payable. The system classifies the business transactions for
Funds Management at the same time. The document is assigned to a transaction class and each line item of the document receives an FM category
assignment. The FM category for the line item determines whether this is relevant for Funds Management or not. For more information, see Funds
Management Category .
3. Summarizing line items in totals records
Line items are summarized in totals records in totals table DFKKSUM before they are transferred to Funds Management and collected in an open
reconciliation key . The summarization in totals records is determined according to FM account assignments and FM category, as well as other criteria, such
as company code, G/L account, posting data, and CO account assignment. When you close a reconciliation key, it is prepared for the transfer to Funds
Management (or general ledger). At the same time, the reconciliation key is blocked for other postings. For more information about processing reconciliation
keys, see Creating Reconciliation Keys or Closing Reconciliation Keys .
4. Transferring posting data
You transfer update-relevant data in Funds Management by using the same program (RFKKGL00) that forwards the data records to the general ledger.
You transfer the totals records for each reconciliation key. For more information about transferring posting data, see Transferring Postings to the General
Ledger .

Note
Payment Matching between Funds Management and Accounting for posting data from FI-CA takes place per reconciliation key. You cannot match
documents that are posted in FI-CA but that have not yet been transferred.

See also:
FM Availability Control in Contract Accounts Receivable and Payable
FM Fiscal Year Change with Documents from Contract Accounts Receivable and Payable
For more information on integration with components Accounting , Controlling, and Sales and Distribution,see Contract Accounts Receivable and Payable
Integration .

1.8 Dispute Management in Contract Accounts Receivable and

Payable

Purpose
With Dispute Managementin Contract Accounts Receivable and Payable, you can create and manage complaints (disputes) from your business partners with
regard to incorrect invoices and credits or missing invoices and credits as dispute cases. Using Dispute Management in Contract Accounts Receivable and
Payable is particularly useful if your company fulfills one or more of the following conditions:
You create numerous invoices or credit memos for your customers.
You have long processing times for invoice-related and payment-related complaints from customers.
Your communications structure is complex.

Implementation Considerations
Dispute Management in Contract Accounts Receivable and Payable uses technical components of SAP Dispute Management (FIN-FSCM-DM). If you use
Contract Accounts Receivable and Payable in connection with an industry component with Release 4.72, Contract Accounts Receivable and Payable and dispute
case processing are in different systems.
If you use Contract Accounts Receivable and Payable in connection with an industry component with Release 6.00, you can run Contract Accounts Receivable
and Payable and dispute case processing in different systems or in the same system.
For more information about the multiple system scenario, see the configuration guide for SAP Dispute Management (FIN-FSCM-DM).

Integration
Dispute Management in Contract Accounts Receivable and Payable consists of the following subareas:
Dispute Case Processing
Process Integration of Dispute Case Processing with Contract Accounts Receivable and Payable
Integration with Other SAP Components

Function Desired Component Required

Creating dispute cases in Contract Accounts Receivable and Payable
Linking documents from Contract Accounts Receivable and Payable
Linking with the business partner/contract account/contract from Contract Accounts
Receivable and Payable
SAP for Insurance , SAP for Media , SAP for Public Sector ( Public Sector
Contract Accounts Receivable and Payable ), SAP for Telecommunications ,
SAP for Utilities, or SAP Contract Accounts Receivable and Payable from Release
4.72

Linking invoices and contracts with the dispute cases Contract Accounts Receivable and Payable, and also, for example, the accounting
system or contract management

Creating link with ArchiveLink objects Contract Accounts Receivable and Payable, and also SAP ArchiveLink

PUBLIC Page 10 of 14
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Creating link with Office documents Contract Accounts Receivable and Payable, and also Knowledge Provider

Analyzing results from SAP Dispute Management Contract Accounts Receivable and Payable, and also Business Information
Warehouse (BW)

Creating dispute cases from SAP Biller Direct Contract Accounts Receivable and Payable, and also SAP Biller Direct (FIN-FSCM-
BD) from Release 3.0

Features
It is always a customer that initiates the creation of a dispute case in Contract Accounts Receivable and Payable. Based on a customer message, you can create
a dispute case by collecting all of the data and information required for processing the case. This information can already be available in Contract Accounts
Receivable and Payable, or you may have to enter additional information for the dispute case.
As coordinator for dispute cases, you can structure your investigations, and distribute and manage the results for all parties involved in your company.
Clerks can include other colleagues and departments in the resolution of a case directly in Contract Accounts Receivable and Payable, and see the current status
of the dispute case. Due to the automatic update of dispute cases, the processor of a dispute case can get information about the current processing status at any
time and react quickly.
For the component SAP Dispute Management, SAP delivers two sample roles:

Technical Name Description Holder

SAP_FIN_FSCM_DM_USER FSCM Dispute Management – Processor Processor forSAP Dispute Management

SAP_BC_CM_ADMINISTRATOR Administrator for Case Management Administrator forSAP Dispute Management

You can also create dispute cases in SAP Customer Relationship Management in the Interaction Center for Financial Customer Care. You can replicate these
dispute cases to Contract Accounts Receivable and Payable.
Conversely, you can replicate dispute cases that were created in Contract Accounts Receivable and Payable in SAP Customer Relationship Management. In that
case, the dispute cases are processed in SAP Customer Relationship Management and not in Contract Accounts Receivable and Payable.
For more information, see the SAP Library for SAP Customer Relationship Management on the SAP Help Portal at http://help.sap.com SAP Business Suite
SAP Customer Relationship Management Application Help SAP Customer Relationship Management SAP CRM for Industries in the documentation
for your industry component under Functions in the Interaction Center for Financial Customer Care .

Example
In customer service, you frequently receive queries that relate to accounting transactions, such as invoices and credits. Customers can
Query the amount of an invoice, even if this invoice has already been cleared in the accounting system
On receipt of a dunning notice, report that they have already transferred the dunned amount
Raise queries about credits promised but not applied
These cases need to be resolved by your having to find payments paid and missing payments, and locate missing credits.

1.9 Integration with SAP Credit Management

Purpose
SAP Credit Management enables your company to operate centralized credit management. The business systems connected (for example, Contract Accounts
Receivable and Payable, CRM, or SD) report the commitments of business partners to SAP Credit Management using XML. SAP Credit Management
consolidates these reports into a credit exposure and checks this against the current credit limit of the business partner. This means that you can manage the
score, the payment behavior summary, and the credit exposure (that is, the total of all open items) of your business partners centrally.

Implementation Considerations
SAP Credit Management is part of SAP Financial Supply Chain Management. For more information about SAP Credit Management, see the documentation for
SAP Credit Management . For information about system configuration, see the Configuration Guide for SAP Credit Management .
You can use Contract Accounts Receivable and Payable and SAP Credit Management in a single or multiple system landscape without an XI server. This
means that you can connect an instance of Contract Accounts Receivable and Payable directly with SAP Credit Management without using an XI server. Contract
Accounts Receivable and Payable and SAP Credit Management can be running in the same system or in separate systems.
The prerequisite for this is as follows: You have installed enhancement package 5 for both Contract Accounts Receivable and Payable and SAP Credit
Management, and you activated the business function FSCM Functions 3 (FIN_FSCM_CCD_3). Activating a business function in Contract Accounts Receivable
and Payable is not a requirement.
You set up the connection between SAP Credit Management and Contract Accounts Receivable and Payable by configuring the appropriate endpoints and
logical ports in SOA Manager.
Message exchange takes place using Web Services Reliable Messaging (WS-RM), which guarantees the transfer of messages and monitors the correct
sequence of incoming messages.

Integration
If you use SAP Credit Management , the internal processes of Contract Accounts Receivable and Payable do not use the score (creditworthiness) determined in
FI-CA; instead, they automatically access the score in SAP Credit Management .

PUBLIC Page 11 of 14
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 You can display the SAP Credit Management score in the transaction Display Business Partner Creditworthiness (see the SAP Easy Access screen under
Account More Information Creditworthiness ).
You can influence the program flows in Contract Accounts Receivable and Payable at certain events. For more information, see the configuration guide for SAP
Credit Management , in particular the sections Making Settings in Contract Accounts Receivable and Payable 4.72 and 6.00 and Settings in Contract Accounts
Receivable and Payable from 6.00, EHP 2005.1 .

Features
The open items of business partners are managed in Contract Accounts Receivable and Payable; the credit decisions take place in SAP Credit Management .
To ensure credit decisions are based on a current dataset, you therefore have to transfer the credit exposure - the total of open items - to SAP Credit
Management at regular intervals.

Note
In the credit exposure update from Contract Accounts Receivable and Payable , the total of all current open items for the business partner is always
transferred to SAP Credit Management . It is not a delta update.

In FI-CA there are mass activities for the following functions:

Sending the credit exposure for a business partner to SAP Credit Management
Sending the payment behavior summary to SAP Credit Management
Replication of the creditworthiness values between Contract Accounts Receivable and Payable and SAP Credit Management
Contract Accounts Receivable and Payable supports the commitment query of SAP Credit Management . In SAP Credit Management , for each check step
in a credit check, you can specify whether the current commitment is queried in the connected systems.
Contract Accounts Receivable and Payable supports the partner messages of SAP Credit Management . The partner messages enable the credit exposure to
be updated in SAP Credit Management across module and system boundaries for a business transaction, with no chronological gaps.
You can display the credit information from SAP Credit Management in Contract Accounts Receivable and Payable , for example, to display them in the
Interaction Center . The function module FKK_CR_GET_CREDIT_INFORMATION uses the XI interface CreditWorthinessQuery .
In Contract Accounts Receivable and Payable , you can also carry out a credit check for a business partner in SAP Credit Management .

1.10 Integration with SAP Global Trade Services

Purpose
SAP Global Trade Services (SAP GTS) supports enterprises in managing foreign trade activities, in adhering to trade laws, and in optimizing global trade.
The integration of SAP GTS with Contract Accounts Receivable and Payable (FI-CA) enables you to comply with legal regulations by using sanctioned party list
screening in handling your payment transactions. A sanctioned party list is a list of persons and companies, with whom you are not permitted by law to trade.
Sanctioned party lists are published by government agencies and legal authorities and you can obtain them from data providers. Sanctioned party lists are legally
binding for all those participating in trade. The integration of GTS and FI-CA makes it possible for you to automatically compare your business partner addresses
with each relevant sanctioned party list. The results of this comparison are used in the payment program in Contract Accounts Receivable and Payable.

Prerequisites
You can obtain sanctioned party lists from data providers and import them to the relevant system using the XML interface. You can also create your own lists and
use them for the check. To do this you have to create internal sanctioned party lists in SAP GTS.
You define which lists are used for the check in SAP GTS in Customizing. In addition, you create legal regulations in SAP GTS. Each legal regulation determines
which sanctioned party lists are relevant for it.
You make the system settings in Customizing under Materials Management Purchasing Foreign Trade/Customs SAP Global Trade Services .
For more information about S AP Global Trade Services , see the SAP Help Portal at http://help.sap.com Analytics Governance, Risk, and Compliance
(GRC) SAP Global Trade Services Application Help Compliance Management Sanctioned Party List Screening

Process Flow
Sanctioned party list screening ensures that you can prevent transactions with the persons and companies listed.
You can implement the SAP GTS component in one of the following ways:
In the same system as Contract Accounts Receivable and Payable, in the same client or different clients
In a separate system
Note
If you choose to use SAP GTS in the same client, you are restricted to using the scenario described here.
All other processes, such as checking logistics documents, are not possible in that case.
If you run SAP GTS and Contract Accounts Receivable and Payable in different clients or systems, the business partner data is replicated to SAP GTS by
means of an ALE scenario. You also have to configure the ALE standard scenario for master data distribution and check it periodically. The first time you use SAP
GTS, you have to carry out a legacy data transfer. This means that you have to transmit all business partners to SAP GTS and check them there. You also
communicate new business partners or changes to business partners using this scenario. For more information, see SAP Note 831743.
The business partners created in SAP GTS receive the status Not Checked . The comparison with the sanctioned party lists takes place through a comparison
of the addresses. Depending on the result of the check, a business partner receives the status Locked or Released .
SAP customers and vendors that you access, for example, from Financial Accounting (FI), are always transferred to SAP GTS and created there separately as

PUBLIC Page 12 of 14
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 SAP business partners with a GTS role. SAP GTS saves some additional data for each business partner with this role.
Contract Accounts Receivable and Payable supports the following checks:
Comparison of business partner master data, including account holder, with sanctioned party lists
Evaluation of the results of the check in the payment program
Check in the payment program as to whether the country of the payee or payer is subject to an embargo
Check of the note to payee by SAP GTS in the payment program
For both incoming and outgoing payments, the payment program determines whether a business partner is included in a sanctioned party list and therefore
whether payment is to be prevented.
Each business partner can have one or more sets of bank details. Each of these sets of bank details can have an account holder. SAP GTS also compares this
account holder with the sanctioned party lists and, if necessary, the payment program prevents payment transactions.
The banks (in particular, all correspondence banks in the USA) check the text of the note to payee in the payment media and react accordingly depending on the
result of the check (for example, by locking a payment).
You can also use an event in Contract Accounts Receivable and Payable to compare the text in the text field with the sanctioned party lists. To do this, use the
sample module FKK_BLACKLIST_0655 to define your own function module and define it for event 0655 in Customizing for Contract Accounts Receivable and
Payable under Program Enhancements Define Customer-Specific Function Modules .
To enable the payment program to have swift access to current check data, run the Get Locked Partners and Countries report, which determines the locked data
from SAP GTS, at periodic intervals. You can access the report in the menu for Contract Accounts Receivable and Payable under Periodic Processing
Transfer Data .
The transaction for transferring data for the critical business partners and embargo countries is under Periodic Processing Transfer Data Sanctioned Party
Lists .
To access the GTS area menu in the SAP GTS system, enter transaction /SAPSLL/MENU_LEGAL in the command field.

1.11 Debt Recovery Management (FIN-FSCM-DR)

Purpose
You can use Debt Recovery Management (FIN-FSCM-DR) to collect overdue receivables using internal collection departments. Debt Recovery Management
(FIN-FSCM-DR) offers a completely integrated, seamless processing of collection activities. The master data and open items are portrayed in Contract Accounts
Receivable and Payable . The functions that you need for collecting the receivables are integrated in the collection case of the component Debt Recovery
Management (FIN-FSCM-DR). Contract Accounts Receivable and Payable and Debt Recovery Management (FIN-FSCM-DR) run either in the same system
or in different systems that have to be coupled using Application Link Enabling (BC-MID-ALE) (ALE).

Prerequisites
You have maintained the activities in the Implementation Guide for Contract Accounts Receivable and Payable under Integration → Financial Supply Chain
Management → Debt Recovery Management . With these settings you integrate the open receivables in the collection case of the component Debt Recovery
Management (FIN-FSCM-DR).
In the system in which the component Debt Recovery Management (FIN-FSCM-DR) is installed, you have made the settings in the Implementation Guide for
Collection Case Processing

Process Flow
You can create collection cases in two ways – with or without the dunning program.

Creating Collection Cases Using the Dunning Program

To create collection cases using the dunning program, start the dunning activity run . For the creation of collection cases using the dunning program, SAP delivers
the following dunning activities that are each assigned to one of the following function modules:
FKK_0350_COLL_CASE_NEW If this function module is assigned to the dunning activity, for each dunning notice the dunning activity run creates a new
collection case in the component Debt Recovery Management (FIN-FSCM-DR). The function module does not create the collection cases itself; it runs through
checks and saves the data in a table that the system needs for creating a collection case. To actually create the collection cases, you have to call the transaction
FPDM01 Create Collection Cases after Dunning Run (step 2).
FKK_0350_COLL_CASE_ADD_OR_NEW This function module checks whether collection cases already to which the dunning items can be added exist for the
business partner and if so, adds them to the cases. If there is no suitable collection case, the dunning activity run calls the function module
FKK_0350_COLL_CASE_NEW; this collects the data for the creation of a new collection case. In this case also the collection case is not actually created until
you call transaction FPDM01 Create Collection Cases after Dunning Run (step 2).
To create new collection cases in the component Debt Recovery Management (FIN-FSCM-DR) call transaction FPDM01 Create Collection Cases after Dunning
Run in Contract Accounts Receivable and Payable

( ) At event 9053, when you create a collection case you can add or change attribute values such as the priority of a collection case dependent on the
dunning level.
To update the relevant data in the collection case when you reverse a dunning notice, define the function module FKK_0395_COLL_CASE_REVERSE for event
0395.If the collection case has not been created yet, the module ensures that the entry is deleted in the dunning activity table. Otherwise the item is removed from
the collection case provided the collection cases is not locked against changes in the item list.

Creating Collection Cases without the Dunning Progarm

Call transaction FP03EC Submit Items for Internal Collection .
Enter the criteria that you want to use to select the items to be submitted.

PUBLIC Page 13 of 14
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Choose Continue
The program selects all open items that correspond to the selection criteria and issues them in a list.
To submit an item, select it and then choose the pushbutton ( ) Submit.
You can then decide, per dialog, whether you want to create a new collection case or – if a collection case already exists for the business partner – add the items
to an existing collection case.
To recall an item, selet the item and choose ( ) Recall.
Provided the collection case was not locked against changes in the component Debt Recovery Management , the program recalls the submission of the item for
internal collection. The next time you call transaction FP03EC Submit Items for Internal Collection , the item appears in the list as an item to be submitted.

( ) When you recall an item from internal collection, all subitems of a line item are recalled.

Result
IN both cases the system either creates new collection cases in the component Debt Recovery Management (FIN-FSCM-DR) or adds the items submitted to
internal collection to existing collection cases.

( ) If an item has been cleared in Contract Accounts Receivable and Payable , for example, by pazment, reversal, or write-off, the collection case is
updated in the component Debt Recovery Management (FIN-FSCM-DR) and this item is no longer displayed.

1.12 Integration with Customer Relationship Management (CRM)

Purpose
You can integrate Contract Accounts Receivable and Payable in Customer Relationship Management (CRM).

Features
The business processes and functions of FI-CA are integrated with the CRM Interaction Center Web Client by means of Financial Customer Care (FCC) as part
of the following scenarios:
Financial Customer Care
This scenario offers basic functions, such as an account overview, the display of the dunning history, and the search for payments of a customer.
Collections Management
This scenario covers important processes, such as the initiation of customer calls, processing of payments, and the granting of deferrals and installment
plans.

PUBLIC Page 14 of 14
© 2014 SAP SE or an SAP affiliate company. All rights reserved.