Set Up and Load Guide for Business Agreement / Contract

Account
General
The business agreement in SAP CRM is replaced by the contract account in SAP ERP. The unique
allocation of a business agreement to a contract account, and vice versa, always takes place by
means of a unique ID (GUID).
As a prerequisite for creating a business agreement or contract account in the other system using the
CRM middleware, the respective sold-to party or contract partner must also be created in that system.
The business agreement only contains some of the fields from the contract account, whereby some of
these also have different field formats. Special mapping tables are available for these fields.
During creation of a business agreement in SAP CRM, a BDoc containing the relevant data is sent to
SAP ERP. In SAP ERP, the contract account is copied from a template. The contract account template
is determined using the business agreement class specified in the business agreement:

If you create a contract account in SAP ERP, the process takes place the other way round.

The contract account is created in a specific number range. As the number ranges are synchronized,
the CRM system is able to find the same number range. This number range automatically defines the
business agreement class.

A 1:1 relationship between the business agreement class and the contract account category is
technically possible, but not a requirement.

Customizing
In Customizing for Customer Relationship Management under Master Data
Business Partner
Business Agreement
Define Basic Settings, you have to set FI-CA to an active account in table
CRMC_BUAG_ACTV.
Depending on the business agreement class, the contract account templates are stored in SAP ERP
in table TFK_BUAG_REF.
You can find this table in Customizing for Financial Accounting under Contract Accounts Receivable
and Payable
Integration
Customer Relationship Management
Business Agreement
Determine Template for Contract Account for Replication.
If you use SAP Utilities, SAP Telecommunications, or SAP Media, the following tables are also
relevant:
The allocation of tax features (depending on the business agreement class) to the account
determination ID takes place in table TFK_MAP_KOFIZ_SD. You can find this table in
Customizing for SAP ERP under Financial Accounting
Contract Accounts Receivable and
Integration
Customer Relationship Management
Business Agreement
Payable
Allocate Field Values for CRM Tax Features to Account Determination IDs.
The payment conditions are allocated to one another in table TFK_MAP_ZAHLKOND (in
Customizing for Financial Accounting under Contract Accounts Receivable and Payable
Integration
Customer Relationship Management
Business Agreement
Allocate Field
Values for CRM Payment Conditions to Payment Conditions).

Determination of Business Agreement Class

During download of a contract account, the system can use FI-CA event 1022 (see tables TFKFBM,
TFKFBS, and TFKFBC in SAP ERP) to determine the business agreement class. Note that as the
business agreement and contract account numbers are identical, the system can change the business
agreement class again (see the Number Assignment section).

Standard Business Agreement

There is no standard contract account checkbox (as there is for the standard business agreement) for
the contract account in SAP ERP. Use FI-CA event 1023 to determine whether the business
agreement should be selected as a standard business agreement when it is downloaded. You can
check the contract accounts of the business partner and decide whether you want to select the
checkbox.

Note
The checkbox for the standard business agreement is not a required entry field. If you select it, it
may affect performance.

Number Assignment
In some components, such as Utilities, the business agreement and the corresponding contract
account have the same number. This is achieved by the CRM system determining a business
agreement class with a matching external number range. The ERP system determines a contract
account category to which a matching external number range is allocated. The system checks the
checkboxes in tables TFK002a and TE002a (for SAP IS-U only).
The number ranges must be set up so that the internal number ranges have a corresponding external
number range in the other system.
During the initial download, you have to temporarily convert the number ranges to external number
ranges and allocate each one to at least one business agreement class.

Event Modules
This section lists the necessary event modules. Most of them should already have been delivered
correctly.
In SAP ERP, you have to make the following settings for the business agreement object in table
COM_BUPA_CALL_FU (with selected call indicator):

Event

Item

Name of Function Module

Mapping Inbound
Processing
Mapping Outbound
Processing

100000

COM_BUAG_MWX_MAP_MAIN_CENTRAL

100000

COM_BUAG_MWX_BPS_FILL_CENTRAL

In SAP CRM, you have to make the following settings for the business agreement object in table
CRMC_BUT_CALL_FU (transaction SM30) (with selected call indicator):

Event

Item

Name of Function Module

CRM Inbound
Processing
CRM Inbound
Processing
CRM Outbound
Processing
CRM Outbound
Processing
Extractor

50000

CRM_BUAG_BDOC_MAP_NUMRANGE

100000

CRM_BUAG_MWX_PROCESS_EXT_STRUC

100000

CRM_BUAG_MWX_FILL_EXT_FROM_MEM

200000

CRM_BUAG_MWX_FILL_EXT_FROM_DB

100000

CRM_BUAG_MAIN_GET_ID_LIST

For the following FI-CA events, you also have to allocate a function module.
Table TFKFBS in SAP ERP:

Event

No.

Standard Module

1020
1021

0
0

FKK_EVENT_1020
FKK_EVENT_1021