CD - SAP End-to-End Configuration

BASIC FUNCTIONS
In the following activities you make settings that are of fundamental importance to contract accounting.
Application Area
 In this activity, you specify the application area active within the client. As a rule you only use one
application area, such as the application area "Insurance company".
If only one active application area is specified, all users automatically work with this application area which is
stored in the user defaults.
Standard settings
The application area relevant for your company is entered by SAP.
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Basic Functions/Application
Area
Activation of Basic Functions
 In this step you make the basic settings for the functionality of the Collections/Disbursements system.
The following settings have a cross-client effect:
 Forwarding data to Profitability Analysis (CO-PA)
 Main and sub-transactions
The following settings are client-dependent:
 Checking suspicious transactions (money laundering)
 Customer-specific account determination
 Dunning grouping for the dunning variant
 Dunning lock on broker contract for assigned insurance objects
The following settings control the functionality of payment plans:
 Summarization and grouping
 Clarification for customer-initiated payments
 Algorithm for customer-initiated payments
 Rounding to first payment plan item
 Always smooth payment plan sub items
Activities
Activate the appropriate settings when you use them.
C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

1
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Basic Functions/Activation of
Basic Functions
Controls whether monitoring is active for suspicious transactions (money laundering monitoring).
If you set the indicator, then monitoring is active for suspicious transactions.
Note
You make more settings for suspicious transactions in the Implementation Guide.
Choose Business Transactions -> Payments -> Incoming/Outgoing Payment Processing -> Settings for
Checking Suspicious Transactions (Money Laundering)

2
COLLECTIONS/DISBURSEMENTS
Organizational Units
Your enterprise structure has already been created in the system (see under "Enterprise structure" in the IMG
structure). You should make specifications for your organizational unit here for contract accounts receivable
and payable.
Set Up Company Codes for Contract Accounts Receivable and Payable BP 01-1 Business
Partner
 In this activity you define the company codes that you want to use in Contract Accounts Receivable and
Payable.
Requirements
1. You have defined the company codes required (see IMG Structure Enterprise Structure).
2. You have made the specifications necessary for the company codes required in the Financial
Accounting Global Settings (see IMG structure Financial Accounting -> Financial Accounting Global
Settings -> Company Code).
Activities
Assign the attributes required for controlling postings in Contract Accounts Receivable and Payable to each
company code that you want to use in Contract Accounts Receivable and Payable.
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Organizational Units/Set Up
Company Codes for Contract Accounts Receivable and Payable
Define Company Code Groups BP 01-1 Business Partner
 In this activity, for each contract account you define the company codes to be used for posting to the
contract account. These company codes are summarized in company code groups.
Activities
1. Define which combinations of permitted company codes where the contract accounts managed in
your system may appear. Define a company code group for each combination. The groups must not
overlap.
2. Define a name for each company code group and assign a paying company code to the group. This
paying company code is responsible for paying the accounts in automatic payment transactions.
3. Then carry out the activity Assign Company Codes to Company Code Groups

3
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Organizational Units/Define
Company Code Groups
Assign Company Codes to Company Code Groups BP 01-1 Business Partner
 In this activity, you assign the required company codes to the company code groups that you defined in the
previous activity.
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Organizational Units/Define
Company Code Groups

4
Basic Functions/Contract Accounts
In the following activities, you will make settings for creating and processing contract account master data.
Number Ranges and Contract Account Categories

In the following activities, you will create definitions for number ranges and contract account
categories.

Intervals BP 01-1 Business Partner
In this activity, you define number ranges for contract accounts.
You then assign the number ranges to contract account categories in the activity: Define Contract Account
Categories and Assign Number Ranges
Contract accounting number ranges are valid for all clients.
Note for the industry component Insurances
Assign the number ranges to the contract account categories in the activity: Configure Contract Account
Categories and Assign Number Ranges (FS-CD).
Standard settings
The SAP standard delivery contains number ranges for the contract account categories delivered.
Recommendation
For contract accounts that are transferred from external systems with the same number, you should define
number ranges with external number assignment.
Activities
1. Check the number ranges delivered and change them if necessary.
2. You may need to define new number ranges.
Further notes
You transport number range objects as follows:
Choose Interval -> Transport in the accounting document Number Range screen.
All intervals for the selected number range object are deleted in the target system first. After the import, only
the intervals you export are present. The number statuses are imported with their values at the time of export.
Dependent tables are not transported or converted.
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Basic Functions/Contract
Accounts/Number Ranges and Contract Account Categories/Define Number Ranges/Intervals

5
Configure Contract Acct Categories and Assign Number Ranges
 In this activity, you define contract account categories for the contract account.
The defined contract account categories are assigned to contract accounts when contract account master data
is created.
Requirements
The number ranges for contract accounts are defined.
Activities
1. Check and change the standard contract account categories if necessary.
2. If you have to define new contract account categories, define the relevant attributes.
PATH:
Accounts/Number Ranges and Contract Account Categories/Configure Contract Acct Categories
and Assign Number Ranges

6
7
Configure Contract Acct Categories and Assign Number Ranges (FS-CD)
 In this activity you define contract account categories.

The defined contract account categories are assigned to contract accounts when creating the contract account
master data.
You define an account creation variant for the contract account category. During the creation of an account,
the default values defined for the account creation variant are used as default values (which can be changed)
for the contract account master data.
Note
The Configure Contract Account Categories and Assign Number Ranges IMG activity (SIMG
_FICABFCA_TFK002A) is not required for insurance companies.
Requirements (BP 01-4 Bank Maintenance)

You have defined number ranges for contract accounts.
Activities
1. Check the delivered contract account categories and change them if required.
2. Define possible new contract account categories and define the associated attributes.

8
PATH:
Accounts/Number Ranges and Contract Account Categories/Configure Contract Acct Categories
and Assign Number Ranges (FS-CD)

9
10
Field Modifications
Configure Field Attributes for Contract Account Category BP 01-1 Business Partner
In the following activities, you will create definitions for field groupings for the processing screens.
 In this activity you determine which fields: require an entry (required entry), are ready for input (optional
entry), are displayed (display), are hidden (hide) - for master record maintenance, depending on the contract
account category.
For each field this specification is linked to the field status of other criteria. The status taken on by the field in
the entry screen for master data is established by this link.
Linking Rules
Linking Similar Criteria (Except the Activity)
Similar criteria can be, for example, two or more roles that a business partner can take on, or several roles that
form a role grouping. The field statuses of two similar criteria are linked. The result is then linked to a third
criterion, and so on. Required entry has highest priority, followed by optional entry, display, hiding a field and
non-specified entry. In this way the field statuses are reduced to a single status.
Examples of Linking:
Criterion 1 Hide Optional Entry Optional Entry
Criterion 2 Optional Entry Display Required Entry
Interim Result Optional Entry Optional Entry Required Entry
Linking All Remaining Different Criteria (Except the Activity)

Different criteria can be role(s) and BP type (application object business partner) or relationship category and
client (application object relationships), for example. The field statuses for two different criteria are linked, then
the result is linked with the third criteria and so on. Hiding a field has the highest priority, followed by display,
required entry, optional entry and non-specified entry.
Interim Result Hide Display Required Entry
Linking the Result with the Activity

The result from above is linked with the field status for the activity. The same rules as above apply
here in principle. Also, in the case of the activity display the fields are no longer ready for input.
Interim Result Required Entry Required Entry Optional Entry
Field Status Activity Optional Entry Non-Specified Entry Display
Data Maintenance Activity Create Display Change
Result Required Entry Display Display
Activities
Check and, if necessary, change the standard settings.
PATH:
Accounts/Field Modifications/Configure Field Attributes for Contract Account Category

11
Field Grouping button – Highlight a field and click the Field grouping button to view details

12
Field Modifications
Configure Field Attributes per Activity
 Depending on the activity in question, you determine in this activity which fields during account master data
maintenance: Require an entry to be made (required entry), Do not require an entry to be made (optional
entry), Can be displayed (display), Are suppressed (suppress).
Your entry is linked with the field status for the other criteria (per field). This link determines the status of the
field on the entry screen for the master data.
Linking Rules
form a role grouping. The field statuses of two similar criteria are linked. The result is then linked to a third
criterion, and so on. Required entry has highest priority, followed by optional entry, display, hiding a field and
non-specified entry. In this way the field statuses are reduced to a single status.

Different criteria can be role(s) and BP type (application object business partner) or relationship
category and client (application object relationships), for example. The field statuses for two different
criteria are linked, then the result is linked with the third criteria and so on. Hiding a field has the
highest priority, followed by display, required entry, optional entry and non-specified entry.

13
Example
Only in exceptional cases should it be necessary to control the field status via the activity, for example if an
entry is to be made in a field when it is created, but should not be changeable later.
Activities
Check, and if necessary change the attributes in the delivery system.
PATH:
Accounts/Field Modifications/Configure Field Attributes per Activity
Field Modifications
Define Field Groups for Authorization Check
 You can define whether a field group in the contract account is to be checked for authorizations. Here you
can define the field groups you want to use for checking authorizations. The related authorization object is
F_KKVK_FDG. If the user has no authorization for the field groups to be checked, the fields will not appear. If
the user has authorization to display only, then the fields will only be displayed in change or create modes.

14
PATH:
Accounts/Field Modifications/Define Field Groups for Authorization Check

15
16
Contract Account Relationships
Define Contract Account
In the following activities, you create definitions for contract account relationships.
This is the relationship of Business Partner to Contract Account. The account relationship defines the role that
a business partner plays for a contract account. The account relationship serves to differentiate between
several business partners belonging to a contract account. During automatic payment clearing for example,
this then enables you to specify that a payment on account is always assigned to the holder of the account.
The account holder relationship can only be assigned to one business partner per contract account.
If a contract account category is flagged as being a one-time account, you can nevertheless maintain several
business partners as the account holder with a contract account.
Contract Account Relationships BP 01-1 Business Partner

Define Contract Account/Business Partner Relationships
 In this activity, you define contract account relationships.

Activities
1. Check and change the standard account relationships if necessary.
2. You may have to define new account relationships
PATH:
Accounts/Contract Account Relationships/Define Contract Account/Business Partner Relationships

17
Basic Functions/Insurance Object
You maintain the settings for insurance objects in the following activity.
Define Insurance Object Categories

External Insurance Object Categories BP 01-1 Business Partner
 In this activity, you define (external) insurance object categories and assign these to the (internal)
insurance object categories delivered by SAP, such as: insurance contract, broker contract, commission
contract, claim number or deposit contract.
Internal insurance object categories are hard coded and cannot be changed. The internal insurance object
category determines the usage and processing of an insurance object. The insurance object category
determines the selection of fields and tab pages when creating an insurance object, checks (when assigning a
deposit contract to a deposit account, for example) and input helps (when calling up broker contracts for
transactions, which are only relevant for brokers).
You can assign default values to the insurance object categories that you have defined. The default values are
automatically taken as a proposal (that can be changed if required) when creating an insurance object.
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Basic Functions/Insurance
Object/Define Insurance Object Categories/External Insurance Object Categories

18
19
Account Creation Variant Settings BP 01-1 Business Partner
In this activity you define account creation variants and group insurance object categories for account creation
variants that use rule 5.
 In this activity you define the creation variants for automatic account creation. This forms the
prerequisite for the automatic creation or definition of a contract account by the system, when assigning a
business partner to a new or existing insurance object.
You also define default values, which the system uses as default values (which can be changed) when
creating a contract account.
You define account creation variants as follows: Define a key and a name for the account creation variant.
You assign a rule to an account creation variant, which the system uses to check whether to create a (new)
contract account or use an existing account for a partner (you can find more information about these rules
below).
You define whether the settings are active for the insurance object, or for the contract account master data.
You assign a contract account category to every account creation variant.
You assign field contents for the mandatory fields (at the least) on the contract account, for every account
creation variant.
All other fields for the contract account can be populated with default values. For fields that are available for
the insurance object as well as for the contract account, you can decide whether the field value from the
insurance object is used, or a default value is assigned.
If you use the contract account relationship (VKBZ) as the default value, define two values: The first value is
used when creating a new contract account, and names the account holder. The second value is used if a new
partner is added. Note that there can only be one account holder for each account.
Standard settings
SAP delivers the following rules for checking whether the system creates a (new) contract account, or uses an
existing account, and you can assign these rules to the creation variants that you have defined:
Every new insurance object-partner relationship receives a new account.
According to this rule, the system does not have to check whether an account already exists for the partner in
the system. In this case, the system always creates a new account for each partner - both when creating a
new insurance object and when adding a new partner to an existing insurance object.
There is just one account for each insurance object.
According to this rule, the system normally creates a new account when creating an insurance object. The
system also checks which account was assigned to the already assigned partners when adding a new partner.
If different accounts have been assigned to the partners, the system produces an error message. If the
account is the same for all partners, only one record with partner-related data is created for this account.
There is just one account for every business partner.
According to this rule, the system checks whether one or more accounts already exist for this partner. If
multiple accounts are available, an error message is the result. If no account exists, the system creates a new
account. If just one account is assigned, this account is automatically defined. This is valid for the creation of a
new insurance object, and for the addition of a new partner to an existing insurance object.
There is just one account for the claim object and the associated insurance policy.
According to this rule, the system uses the appropriate partner to search for the referenced insurance object-
partner relationship and uses the account defined there. This is valid for the creation of a new insurance
object, and for the addition of a new partner to an existing insurance object.

20
Note
A prerequisite for this is that a reference number is entered manually for an insurance object from the
insurance policy category, when creating a claim object.
Just one account belongs to a relationship between a business partner and a group of insurance object
categories.
According to this rule, the system checks whether the insurance object category selected online belongs to a
group of multiple insurance object categories. If this is the case, the system selects all insurance objects from
this group, which are assigned to the partner mentioned above. If these insurance objects are all assigned to
the same account, this account is used. If they are assigned to different accounts, the system produces an
error message. If no account is found, the system creates a new account.
Requirements
You have defined groups of insurance object categories and assigned (external) insurance object categories to
them.
Note
If many insurance objects are assigned to the business partner, the usage of rule 5 can greatly affect system
performance.
Partner or account can be freely assigned.

In this case, the system does not create a new account when creating an insurance object-partner relationship,
but defines an available account.
Assignment is possible, using a contract account or a partner. If assignment takes place using a partner, only
one account can be defined for this. If the partner, for which a new insurance object relationship is created,
has not been assigned to the account, this partner is automatically assigned to the account. If multiple
accounts are assigned to a partner, the system produces an error message. If assignment takes place using
the account, a check is made to see whether the partner is already assigned to this account. If this is not the
case, this partner is automatically assigned to the account.
There is just one account with a certain account category for every business partner.
According to this rule, the system checks whether one or more accounts exist for this partner, with the account
category defined with the creation variant. If multiple accounts exist, an error message is output. If no account
exists, the system creates a new account. If just one account with this account category is assigned, this
account is defined automatically. This is valid for the creation of a new insurance object and for adding a new
partner to an existing insurance object.
Just one account with a certain account category belongs to a relationship between a business partner and a
group of insurance object categories.
According to this rule, the system checks whether the insurance object selected online belongs to a group of
multiple insurance object categories. If this is the case, the system selects all insurance objects from this
group, which are assigned to the partner mentioned above. A check is then made to see whether insurance
objects are assigned to one or more accounts with the account category defined for the creation variant. If
these are assigned to just one account with the account category, this is used. If they are assigned to various
accounts with the same specified account category, the system outputs an error message. If no account is
found, the system creates a new account.
Requirements
You have defined groups of insurance object categories and assigned (external) insurance object categories to
them.

21
PATH:
Object/Account Creation Variant Settings/Define Account Creation Variants
Creation Variant, Creation Rule

22
23
Account Creation Variant Settings
Define Grouping of Insurance Object Cats for Account Creation Rule 5 and 8
 In this activity you define groups of insurance object categories: You group such object categories in one
group that is to be billed with the same contract account.
You create the prerequisite that an appropriate check is executed by the system when using an account
creation variant that is linked to rule 5 (just one account belongs to a relationship between a business partner
and a group of insurance object categories) or rule 8 (just one account with a certain account category belongs
to a relationship between a business partner and a group of insurance object categories). (See the description
of rules 5 and 8 in the documentation for the Define Account Creation Variants IMG activity.
PATH:
Object/Account Creation Variant Settings/Define Grouping of Insurance Object Cats for Account
Creation Rule 5 and 8
Field Groupings and Authorizations
In the following activities you define the display or entry properties for each field group, for fields that are
grouped in this group. You can also define an authorization check for each field group.

Configure Field Attributes per Activity
 Dependent on the activity, in this activity you define which fields: require input (required entry), are ready for
input (optional entry), are displayed (display), are hidden (hide), during master data maintenance.

24
For each field, this definition is linked to the field status for the other criteria. The link is used to determine the
status that the field takes in the input screen for master data.
Linking Rules
form a role grouping.
The field statuses of two similar criteria are linked. The result is then linked to a third criterion, and so on.
Required entry has highest priority, followed by optional entry, display, hiding a field and non-specified entry.
In this way the field statuses are reduced to a single status.
client (application object relationships), for example.
The field statuses for two different criteria are linked, then the result is linked with the third criteria and
so on. Hiding a field has the highest priority, followed by display, required entry, optional entry and
non-specified entry.
The result from above is linked with the field status for the activity. The same rules as above apply here in
principle. Also, in the case of the activity display the fields are no longer ready for input.
Example
In exceptional cases it can be necessary to control the field status using the activity. This can be the case, for
example, if a field is filled when created, and is then not to be changed at a later date.
Activities
Check the delivered attribute assignments and change them where necessary.
PATH:
Object/Field Groupings and Authorizations/Configure Field Attributes per Activity

25
Configure Field Attributes for Insurance Object Categories
 In this activity, you define which fields: require input (required entry), are ready for input (optional entry), are
to be displayed (display), are hidden (hide) during master data maintenance, dependent on the insurance
object category.
Linking Rules
Linking Similar Criteria (Except the Activity). Similar criteria can be, for example, two or more roles that a
business partner can take on, or several roles that form a role grouping. The field statuses of two similar
criteria are linked. The result is then linked to a third criterion, and so on. Required entry has highest priority,
followed by optional entry, display, hiding a field and non-specified entry. In this way the field statuses are
reduced to a single status.

client (application object relationships), for example.
The field statuses for two different criteria are linked, then the result is linked with the third criteria and
so on. Hiding a field has the highest priority, followed by display, required entry, optional entry and
non-specified entry.
Activities
Check the delivered attribute assignments, and change them where necessary.
PATH:

26
Object/Field Groupings and Authorizations/Configure Field Attributes for Insurance Object
Categories

27
Define Field Groups for Authorization Check
 You can define whether an authorization check is to be made for every field group in the insurance object.
Define the field groups that you want to use for the authorization check.
The associated authorization object is called I_INSO_FDG.

1. INSO_FDG Field groups number
2. ACTVT Activity
Authorizations for a user and presentation procedure

1. No authorization: Fields are hidden
2. Display authorization only: Fields are set to display only in all processing activities
3. Change authorization only: Fields are ready for input for the Create and Change activities. They are hidden
for the Display activity.
4. Creation authorization only: Fields are only ready for input for the Create activity. They are hidden for the
Change and Display activities.
PATH:
Object/Field Groupings and Authorizations/Define Field Groups for Authorization Check

28
29
Maintain Authorization Types for Insurance Objects
 In this activity you maintain authorization types for insurance objects. You define the fields for the values
defined in the authorization object.
Requirements
You have maintained the I_INSO_AUT authorization object.
PATH:
Object/Field Groupings and Authorizations/Maintain Authorization Types for Insurance Objects
Blank in system

30
Basic Functions/Postings and Documents
In the activities that follow, you make basic settings for posting documents as well as for <DS:GLOS.summary
record>posting totals.
Basic Settings
In the following activities, you make settings that are important for posting documents.
Basic Settings
Define Authorizations for Field Changes
 In this activity you can group fields into field groups. You can then give individual users a change
authorization for authorization object F_KKKO_AEN for these field groups.
Fields that cannot be changed retain their "not changeable" status even if they are assigned to a field group.
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Basic Functions/Postings
and Documents/Basic Settings/Define Authorizations for Field Changes
Field Group - The field group is used to assign authorizations. Every user can be given the authorization to
change fields in one or several groups. This means that a user may either change all or none of the fields in a
group. You should bear this in mind when organizing the fields into groups. The field group is numerical.

31
Document
In the following activities, you make basic settings for posting documents.
Document
Maintain Document Assignments
In the following activities, you maintain document account assignments that were either specified
manually during document entry or were already stored in customizing for manual and automatic document
entry.
Document
Maintain Document Assignments/Document Types
In the following activities you make settings for document types.
Document Type - The document type classifies contract accounting documents, and is saved in the document
header when you post a document. Each document type is assigned a number range that you use when
creating documents online. The number range determines the entries in the document number field. You can
assign additional number ranges for the automatic generation of a large number of documents in parallel
background processes. These documents may, for example, be needed by the payment program. If an
external number range is assigned to the document type, then you do not need any more number ranges.
Document
Maintain Document Assignments/Document Types/Maintain Document Types and Assign
Number Ranges
 In this activity you maintain your document types for your business transactions in contract accounts
receivable/payable. Document types differentiate different business transactions. The number ranges
assigned to them also control the way documents are stored. During document posting, the system determines
the document number from these number ranges. Although you can use a given number range for more than
one document type, note that you require number ranges when processing documents both individually and en
masse. Document types are valid for all clients.
Requirements
The number ranges that you want to assign to the document types are defined.
Standard settings - internal notice
The SAP standard system contains predefined document types.
Activities
1. Check and where necessary change these predefined document types.
2. Create your own document types.

32
PATH:
and Documents/Document/Maintain Document Assignments/Document Types/Maintain Document
Types and Assign Number Ranges
Maintain document types

33
Number range for mass postings - Key under which a number range for number assignment is defined for
documents in Contract Accounts Receivable & Payable and which should be used in mass runs. In mass
processing several number ranges are also assigned to every possible document type. This is the only way to
guarantee unhindered processing of mass runs by parallel processing. Each processing process reserves a
number range for the duration of its activities. Assign as many number ranges to the document types so that
each parallel process can use its own number range. For example; If you normally spread a payment run over
5 parallel processes, you should assign at least 5 number ranges to the document types used. You can
assign the same number ranges to different document types.
Maintain Number ranges for mass processing
Document
Maintain Document Assignments/Document Types/Maintain Control Information for Document
Types
 In this activity you can take each document type and define the field status of standard SAP fields in the FI-
CA document when posting: Required field - Document data is not posted if the field does not contain a value,
Optional field - If there is no entry in this field, the system determines the field value, Hide - With these fields,
field values cannot be skipped.
If a field value is skipped with a hidden field, the document is not posted. This field status is used for testing
purposes, for posting data transfer. This guarantees that all data required for posting the document in the SAP
system is available. You can also define a receivable type to determine the dunning procedure.
Requirements
You have created document types.

34
PATH:
and Documents/Document/Maintain Document Assignments/Document Types/Maintain Control
Information for Document Types
Click on ‘Variable list’ button to view the control data for document type

35
Document
Maintain Document Assignments/Document Types/ Maintain Main Transactions
 In this activity you define your main transactions.

Activities
Define your main transactions.
PATH:
and Documents/Document/Maintain Document Assignments/Maintain Main Transactions
Document
Maintain Document Assignments/ Maintain Sub- Transactions
 In this activity you define your sub-transactions.
Activities
Define your sub-transactions

36
PATH:
and Documents/Document/Maintain Document Assignments/Maintain Sub- Transactions

37
38
39
Document
Maintain Document Assignments/Maintain Transactions for IS-IS-CD
In the following activities you configure main and sub-transactions, and assign your own transactions
to the hard-programmed internal transactions. Requirements: You have defined your own main and sub-
transactions.
Document
Maintain Document Assignments/Maintain Transactions for IS-IS-CD/Define and Parameterize
External Transactions BP 03-3 Document Create/Change/Review
 In this activity, you define external main and transactions, meaning those that are relevant for your
company, and assign parameters for document control (such as company code, product group, statistical key
and so on) to them. The determination of attributes for the item, processing control and account determination
are set for the external main and sub-transactions.
Note
You can maintain parameters for invoicing, for item categories and for broker collections at this point, or in the
following activities: Assign invoicing parameters to main and sub-transactions, Assign main and sub-
transactions to item categories, Assign categories for broker collections to main and sub-transactions
Standard settings
SAP delivers a series of transactions as standard, which have a 1:1 relationship to the hard-coded internal
transactions. These transactions and their assignment form proposals, which you can accept, or adjust to your
own company-specific requirements. Take the executions of internal transactions into account in the Assign
external transactions IMG activity.
Activities
Define Main Transactions. If "external main transaction" is activated in the navigation screen, then the table
for main transaction definitions is available on screen. If you do not want to make use of the standard settings
delivered by SAP, you have the following definition options:
You can assign other names to the keys for main transactions preset by SAP
You can delete the entries delivered by SAP. Select the entry to be
deleted and then click on the deletion icon.
You can define your own main transactions. Choose "New entries", assign
a key for the main transaction to be defined, and assign a name to it (such as 'Premium').

40
Define Sub-transactions
Activate "External sub-transactions" in the navigation screen, and proceed in the same way as for main
transactions.
Parameterize Transactions
Activate "Document parameters" in the navigation screen and assign the parameters for document control to
the transactions, which you have defined in other Customizing activities.
PATH:
and Documents/Document/Maintain Document Assignments/Maintain Transactions for
IS-IS-CD/Define and Parameterize External Transactions

41
Document
Maintain Document Assignments/ Maintain Document Assignments/Maintain Transactions for
IS-IS-CD/Assign External Transactions BP 03-3 Document Create/Change/Review
 In this activity, you assign the external main and sub-transactions that you have defined to the internal main
and sub-transactions hard-coded by SAP.
Internal transactions are important for internal system creation of documents (such as charges, postings on
account, transfer postings in broker collections). In these cases, the external transactions that are written in the
newly created items are read for the internal transactions. The internal transactions are assigned to the
external ones for these cases as the determination of more attributes for the item, processing control and
account determination are basically set for the external transactions. The assignment is necessary to give you
the option of including this type of document in your own concept of main and sub-transactions, and to allow
you to process it further.
We recommend that you define an external transaction for every internal transaction, and that you assign one
of your own external transactions to every internal transaction. Do not assign a transaction for externally
created documents to the transactions for internally created documents. If you have defined an external
"Premium" category, for example, and have assigned a G/L account for expense/revenue to this, and if this
external transaction is then assigned to the "Returns charge" internal transaction, then every returns charge is
posted as a premium.
Requirements
You have defined the external transactions.
PATH:
and Documents/Document/Maintain Document Assignments/Maintain Transactions for
IS-IS-CD/Assign External Transactions

42
Document
Maintain Document Assignments/Define Product Groups
 In this activity, you define product groups. The product group is a criterion for determining the
receivables account and payables account. You can assign dunning procedure types to the product group,
which are used to determine the dunning procedure and map the dunning grouping categories.

43
Note
From Release 4.62 you can choose whether the dunning grouping categories are active on the product group
or on the dunning variant.
We recommend that you set the parameters for the dunning variant, as the settings for the product group will
not be developed further.
Recommendation
If you use the product group, to determine the dunning procedure and the dunning procedure type for an item,
you should define your product groups with reference to this specific usage.
Activities
Check the delivered product groups and enhance then where necessary.
PATH:
and Documents/Document/Maintain Document Assignments/Define Product Groups
Document
Define Account Assignments for Automatic Postings
In the activities that follow, you store account assignments needed by the system to carry out automatic
postings.
 In this activity you define account assignments for down payments and charges that are posted
automatically when down payment requests, budget billing requests or statistical outstanding charges are

44
cleared. The basis for the postings are the statistical items. Account assignments that cannot be taken from
the statistical items have to be defined in the system at this point. Part of the activity is a main transaction and
a sub-transaction, insofar as these fields are used.
Example: Utilities
Activities
Define the required account assignments.
PATH:
and Documents/Document/Define Account Assignments for Automatic Postings/Define Account
Assignments for Down Payments and Charges

and Documents/Document/Define Account Assignments for Automatic Postings/Automatic G/L
Account Determination/Define Accounts for Sales/Purchase Tax
Automatic G/L Account Determination
In the activities that follow, you store numbers of G/L accounts needed by the system to automatically
generate line items during document entry or open item clearing. They include the following transactions: tax
on sales/purchases, cash discount, exchange rate differences, smaller payment differences (unauthorized
deductions within tolerance limits), revenue from charges, and offsetting postings. Make sure that you can
differentiate account determination by key fields.

45
You define additional accounts for individual business transactions (payments or returns). Further mention is
made of definitions in each section.

Define Accounts for Down Payment Tax Clearing
 In this activity, you define the numbers of the tax clearing accounts (differentiated by key). These clearing
accounts are used to display down payments gross. If displayed gross, the down payment is posted to the
contract account and the down payment account inclusive of tax on sales/purchases. The tax on
sales/purchases is posted to the input/output tax account and to the tax clearing accounts (for clearing
purposes).
Note
The system does not allow you to post down payments without a tax portion (net display of down payments).
Requirements
The G/L accounts you require have been created (see IMG structure Financial Accounting -> General Ledger
Accounting -> G/L accounts). G/L accounts must be managed in local currency only, for which reason you
must select the field Balances in local currency only in the company code area of the master record.
Activities
Define the numbers for your tax clearing accounts for down payments.
PATH:
Account Determination/Define Accounts for Down Payment Tax Clearing

Define Accounts for Company Code Clearing
 In this activity you define the G/L account numbers for the clearing postings that the system makes when
posting cross-company code transactions.
Clearing postings display the receivables and payables that can arise during central posting or central clearing
between company codes involved.
Requirements
The required G/L accounts are created in the chart of accounts and also for the company code (see IMG
structure Financial Accounting -> General Ledger Accounting -> G/L Accounts).
Activities
Define the numbers of the clearing accounts you require.

46
PATH;
Account Determination/Define Accounts for Company Code Clearing

Define Alternative Accounts for Aperiodic Postings
 In this activity, you define the accounts to be posted to when you post in a different fiscal year.
If the posting periods of a fiscal year are closed, you cannot subsequently post revenues and expenses for
accruals purposes for this year to the standard accounts. You have to post to alternative accounts.
Requirements
You have created the G/L accounts required (see IMG structure Financial Accounting -> General Ledger
Accounting -> G/L Accounts)
Activities
Define a G/L account if, for a document posting, you want to replace a standard G/L account with another
account. Enter the number of the G/L account and the number of the alternative account.
PATH:
Account Determination/Define Alternative Accounts for Aperiodic Postings

Define Accounts for Charges Receivable Revenue
 In this activity, you define the numbers of the G/L accounts to which revenues from outstanding charges are
posted. The account numbers are differentiated by key. When statistical outstanding charge items are
cleared, one line item is generated for the charge item and one for the revenue posting. You should specify the
G/L account numbers for the revenue postings in the activity.
Activities
Define G/L account numbers for revenue postings from outstanding charges. By using the transaction SM34 /
View cluster VC_TFKCOK you can define IDs which can be used, in conjunction with the company code and
the business area, to derive the account assignment for cost accounting (for example the cost center).
PATH:

47
Account Determination/Define Accounts for Charges Receivable Revenue

Define Accounts for Exchange Rate Differences
 In this activity, you define the numbers of G/L accounts to which realized gains or losses from exchange
rate differences that occur when items are cleared are posted.
Note
To define the account numbers for posting gains or losses from foreign currency valuation, go to the following
section: Accounts for OI exch. rate differences.
Requirements
The G/L accounts you require have been created (see IMG structure Financial Accounting -> General Ledger
Accounting -> G/L accounts). G/L accounts must be managed in local currency only, for which reason you
must select the field Balances in local currency only in the company code area of the master record.
Activities
Define the numbers of G/L accounts for realized gains or losses from exchange rate differences.
PATH:
Account Determination/Define Accounts for Exchange Rate Differences

Define Accounts for Cash discounts and Payment Differences
 In this activity, you define the numbers of the G/L accounts to which cash discount and payment differences
are to be posted. These line items are created by the system where open items are cleared by the payment
program, the payment lot or manually, and payment differences within the tolerance limits or cash discounts
are either determined or entered.
Requirements

48
Activities
Define the G/L account numbers for cash discount and payment differences. By using the transaction SM34 /
View cluster VC_TFKCOK you can define IDs which can be used, in conjunction with the company code and
the business area, to derive the account assignment for cost accounting (for example the cost center).
PATH:
Account Determination/Define Accounts for Cash Discounts and Payment Differences

Define Accounts for Rounding Differences
 In this activity you define the accounts that can be posted automatically if there are rounding differences.
Rounding differences arise when: amounts are rounded (e.g. 5-centime rounding), open items are cleared in a
different currency to the one in which they were posted
Requirements
You have defined the rounding rules (see IMG structure: Contract Accounts Receivable and Payable -> Basic
Functions -> Postings and Documents -> Define Rounding Rules for Currencies ).
Activities
Define the G/L accounts for rounding differences.
PATH:
Account Determination/Define Accounts for Rounding Differences
Automatic G/L Account

Determination
Define Accounts for
Receivables/Payables BP 02-1 Data Validation/Postings, BP 02-2 Bank Determination, and BP

03-3 – Document Create/Change/Review
Posting Area VC10

49
 In this IMG activity you define the reconciliation accounts to which receivables and payables are to be
posted.
When posting to a contract account, the document assignments are used to automatically determine and post
to the relevant reconciliation account. The account number for the reconciliation account is stored in a sub-
ledger accounting document. In the Activation of Basic Functions IMG activity, you decide whether the SAP
standard account determination or customer-specific account determination is active in your system.
Requirements
The following prerequisites are valid, regardless of the choice of account determination.
1. You have configured an account plan. Make the appropriate settings in the section of the IMG entitled
Financial Accounting.
2. You have created G/L accounts as reconciliation accounts. To make this setting from the SAP Easy
Access menu, choose Accounting -> Financial Accounting -> General Ledger -> Master Data -> Individual
Processing -> In Company Code (FSS0). Choose the value Contract accounts receivable and payable from
the input help for the Reconciliation account for account type field.
Setting the SAP Standard Account Determination (Posting Area V011)
The following key fields are available: Product group, Main transaction, Sub-transaction, Contract account
category. To define the selection of key fields, choose Goto -> Key selection after calling up the activity
You can control the access sequence for the key fields. To do this, choose Environment -> Access sequence
Requirements
You have made the following settings in the Implementation Guide:
1. You have activated the SAP standard account determination in the Activation of Basic Functions IMG
activity.
2. You have activated the main and sub-transactions in the Activation of Basic Functions IMG activity.
3. You have defined and configured the key fields.
Setting the Customer-Specific Account Determination (Posting Area VC20)
In this activity, you choose the key fields for your account determination. To define key fields, choose Define
characteristics. To edit characteristics, choose Maintain data. Then choose Goto -> Key selection
You can control the access sequence for the key fields. Choose Environment -> Access sequence
Requirements
1. You have activated customer-specific account determination in the Activation of Basic Functions IMG
activity.
2. You have defined and configured the key fields.
Activities
Check the delivered settings for account determination, and change them if necessary.
PATH:
Account Determination/Define Accounts for Receivables/Payables
Click on the ‘Maintain Data’ button to display reconciliation account (rec/pay) detailed data

50
Define Accounts for Receivables/Payables BP 02-1 Data Validation/Postings and BP 02-2
Bank Determination
Posting Area VC20

51
 In this IMG activity you define the G/L account, on which revenues and expenses are posted.
When posting to a contract account, the relevant G/L account is determined automatically and posted to, using
the document assignments. The account number for the G/L account is stored in the sub-ledger accounting
document.
In the Activation of Basic Functions IMG activity, you decide whether the SAP standard account determination
is active, or customer-specific account determination.
Requirements
The following prerequisites are valid, regardless of the choice of account determination:
1. You have configured an account plan. Make the appropriate settings for this in the section of the IMG
entitled Financial Accounting.
2. You have created G/L accounts.
3. You have defined CO short account assignments.
Setting the SAP standard account determination (posting area V021)

The following key fields are available: Insurance type, Business type, Risk type, Claim type, Main transaction,
Sub-transaction
To define the selection of key fields, choose Goto -> Key selection after calling up the activity.
Define a CO short account assignment in the detail screen.
Requirements
1. You have made the following settings in the IMG:
2. You have activated the SAP standard account determination in the Activation of Basic Functions IMG
activity.
3. In the Activation of Basic Functions IMG activity, you have activated the main and sub-transactions.
4. You have defined and configured the key fields for account determination.
Setting customer-specific account determination (posting area VC20)

In this IMG activity, choose the key fields for your account determination.
To define key fields, choose Define characteristics
To edit characteristics, choose Maintain data. Then choose Goto -> Key selection
Define a CO short account assignment on the detail screen.
Requirements
In the Activation of Basic Functions IMG activity, you have activated customer-specific account determination.
You have defined and configured the key fields for account determination.
Activities
Check the delivered settings for account determination, and change where necessary.
PATH:
Account Determination/Define Accounts for Revenues/Expenses
Click on the ‘Maintain Data’ button to display P+L account (revenue/expenses) detailed data

52
Tolerance Groups for Amount Limits
In the following activities you maintain the tolerance groups for amount limits and assign users. The
tolerance groups defined here ensure that users can only post documents up to a determined amount.
 In this activity, you define tolerance groups

PATH:
and Documents/Document/Tolerance Groups for Amount Limits/Define Tolerance Groups

53
 In this activity, you assign the tolerance groups to users.
PATH:
and Documents/Document/Tolerance Groups for Amount Limits/Assign Tolerance Groups to Users
General Ledger Posting Totals

In the following activities, you create definitions for posting totals.
 In this activity, you define your line layout variants for displaying and processing summary records.
Standard settings
The SAP standard system contains line layout variants.
Activities
1. Check and change the standard line layout variants.
2. You may have to create new line layout variants.
PATH:
and Documents/General Ledger Posting Totals/Define Line Layout Variants for Posting Totals
Variants
Variant Fields

54
 In this activity, you choose the fields that will be available for the search function in line item display for a
summary record. These fields will only be shown in line item display, not in summarized display.
Activities
Choose the fields you require.
PATH:
and Documents/General Ledger Posting Totals/Select Fields for Search Function

55
 In this activity, you choose the fields that will be available for the sort function in line item display for a
summary record. These fields are only shown in line item display, not in summarized display.
Activities
PATH:
and Documents/General Ledger Posting Totals/Select Fields for Sort Function
Archiving
In the following activities, you will create definitions for archiving documents.
 In this activity, you define how many days a document has to be in the system before it can be archived.
You create this definition in terms of the document type.
Activities
Define the document type life.

56
and Documents/Archiving/Define Life of Document Types
Document Type - Key representing a document type.
The document type classifies contract accounting documents, and is saved in the document header when you
post a document. Each document type is assigned a number range that you use when creating documents
online. The number range determines the entries in the document number field. You can assign additional
number ranges for the automatic generation of a large number of documents in parallel background
processes. These documents may, for example, be needed by the payment program. If an external number
range is assigned to the document type, then you do not need any more number ranges.
Maintain Document Type

57
Basic Functions/Account Balance Display
You make specifications for the account balance display in the following activities.
Define List Category
 In this activity, you define your list types.

Activities
Define your list types
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Basic Functions/Account
Balance Display/Define List Category
Define Line Layout Variants for Account Balance BP 02-1 Data Validation/Postings and BP
02-2 Bank Determination
 In this activity you define your line layout variants for the account balance display.
Note
You can define totals variants. You can specify subsequent variants for each total variant so as to display
variants which are well-suited to each other in a hierarchy. You specify both using the attributes for a variant.
Standard settings
Line layout variants are contained in the SAP standard system.
Activities
1. Check and, if required, change the standard line layout variants.
2. Create your own line layout variants if necessary.
Further notes
You maintain the attributes for a variant using Edit -> Attributes.

58
PATH:
Balance Display/Define Line Layout Variants for Account Balance

59
60
Assign Transactions for Account Balance Display
 No business partner items are saved for certain documents (for example, payment documents). No text is
displayed in the account balance display for these transactions. In this IMG activity, you can store dummy
transactions dependent on the clearing reason, so that texts for these transactions are displayed.
Requirements
You have maintained main and sub-transactions.
Activities
Define the required dummy transactions in the system and assign them to the clearing reasons.
PATH:
Balance Display/Assign Transactions for Account Balance Display
Maintain Sorting Variants
 In this activity, you maintain the sorting variants for displaying account balances.
Sorting variants consist of a freely definable key and up to three fields. You can define (per field) whether the
account balances are to be displayed in ascending or descending order. You specify a sort variant on the initial
screen of the account balance.
Activities
Maintain the sort variants.

61
PATH:
Balance Display/Maintain Sorting Variants
Define Proposal for Line Layout
 In this activity you define the key for a line layout variant which the system then uses as a default setting
when displaying the account balance.
Activities
Define your default value.
PATH:
Balance Display/Define Proposal for Line Layout
Select Fields for Search Function
 In this activity you select the fields which are to be available for the search function in the account balance
display.
Activities
Select the required fields.

62
PATH:
Balance Display/Select Fields for Search Function
V_TFK021R
Choose Fields for Selection Function
 In this activity you select the fields which are to be available for the selection function in the account
balance display.
Activities
PATH:
Balance Display/Choose Fields for Selection Function

63
Select Fields for Sort Function
 In this activity, you choose the fields that will be available for the sort function in account balance display.
Activities
PATH:
Balance Display/Select Fields for Sort Function
V_TFK021R
Select Additional Fields to be Displayed
 In this activity you select the fields for which the field contents can also be shown in the account balance
display.
Activities

64
PATH:
Balance Display/Select Additional Fields to be Displayed
Define Account Balance Roles
 The account status offers account status roles on the initial screen. These are an enhancement of the
master data selection.
Example
You can, for example, develop the account status role 'corporate group parent' to be installation-specific. To do
this, assign in Customizing a function module to the account status role that determines all the corporate group
subsidiaries.
If you now enter the business partner in the account status initial screen leave the account status role field
blank, all the items for this business partner are displayed.
If, however, you enter a business partner and the account status role 'corporate group parent' on the account
status initial screen, all the items for this business partner and all the items for the group subsidiaries are
displayed.
If no account status roles are defined in the system, this field is not displayed for entry on the initial screen.
Account status roles are delivered industry-specifically.
You can, however, add installation-specific account status roles in the customer name range. If you add
installation-specific roles, you define the key, name and function module to be used in this activity.
The function module to be used must correspond to the event 1210 interface.

65
PATH:
Balance Display/Define Account Balance Roles
Application area - column

Identification code for an application area which uses functions from Contract Accounts Receivable and
Payable. Application areas are recorded in all major datasets in Contract Accounts Receivable and Payable,
so that data can be processed in an application-specific fashion. This then makes application-specific
additional functions available or enables you to replace standard processing methods with application-specific
processing. For example; Application-specific algorithms are used to allocate incoming payments to open
items automatically. You define your application area in the user parameters or in the general selection of
application area Proceed.

66
Role in Account Balance - column
In the initial screen for the account balance, you can specify account balance roles as well as the
business partner. This is an extension of the master data restrictions. For example; You can also
maintain the "corporate group parent" account balance role per installation. In the Contract Accounts
Receivable and Payable IMG you must define a function module for the account balance role to determine all
corporate group subsidiaries. If you only enter one business partner in the initial screen for account balance
and leave the account balance role empty, all items are displayed for just this business partner.
However, if you specify the business partner and the "corporate group parent" account balance role, all items
for this business partner and all items for the corporate group subsidiaries are displayed.
If there is no account balance role defined in the system, this field is not offered in the initial screen.
Account balance roles are delivered specifically for industries. However, you can extend these using
installation-specific account balance roles in the customer name
Name of Function Module for Account Balance Role - Function module that carries out the account balance
master data supplement for the account balance role. The interface of this function module corresponds to the
interface of the event 1210.

67
Basic Functions/Open Item Management
In the following activities, you create definitions for open item processing.
Define Line Layout Variants for Open Item Processing
 In this activity you define your line layout variants to be used when processing open items.
Standard settings
The SAP standard system contains predefined line layout variants.
Activities
1. Check and if necessary adapt these predefined line layout variants.
2. Define your own line layout variants as appropriate.
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Basic Functions/Open Item
Management/Define Line Layout Variants for Open Item Processing
Variants
Variant Fields

68
Specify Selection Categories
 In this activity you define the selection types that are to be used in: payment lots for selecting open items,
returns lots for selecting payment documents
Assign a technical field name to a freely selectable ID that represents the field according to which the selection
is to take place. You can call a list of possible field names from the input help of the field Field Name when
maintaining the entries. The selection types have the advantage that you can decide which fields are to be
used for selecting open items within a screen variant. The selection fields are not predefined in the screen
variant. You can determine them using the selectable selection types.
Activities
Specify the required selection types.
PATH:
Management/Specify Selection Categories
Select this field if you would also like to use the selection category for entry in the returns lot.
Define Default Values for Account Maintenance
 In this activity, you define a document type and a clearing reason. The system uses this information when
posting the clearing document and defaults it when you clear open items.
Requirements
The document type is created.
Activities
Define your default values.
PATH:
Management/Define Default Values for Account Maintenance

69
Short Account Assignments for Transfer Postings in Account Maintenance
 In this activity you define short account assignments for transfer postings in account maintenance.
Using the short account assignments entered here, you can post amounts to the account defined under the
short account assignment in account maintenance, without having to create G/L account items.
Example: Insurance Industry Component
A business partner of a reinsurance company makes a partial payment of an open receivable. The accounting
clerk responsible is already aware when the payment is received that this business partner has filed for
bankruptcy, and that further payments are unlikely. In this instance, the accounting clerk can manually clear
the receivable with the partial payment received in account maintenance, and post the remaining difference
direct to an individual adjustment account using short account assignment.
PATH:
Management/Short Account Assignments for Transfer Postings in Account Maintenance

70
A key that can be used for a transfer posting to an appropriate general ledger account. Fast entry option for
transfer postings to certain accounts defined in Customizing. If you want to carry out a transfer posting to a
general ledger account, enter the required short account assignment here. For example; In the payment lot,
incoming payments that should be assigned to other departments can be transferred to an appropriate clearing
account.
Business area specified explicitly for the posting. If you state a business area here, and the G/L account
permits account assignment of a business area, the business area stated is used. If you do not state a
business area here, and the G/L account permits account assignment of a business area, the business area
from the payment posting is used.
Define Default Values for Automatic Clearing
 In this activity you define the default values required for automatic clearing. You start the program for
automatic clearing from the Contract Accounts Receivable and Payable menu (see Periodic processing ->
Automatic clearing).
Activities
Define the required default values.
PATH:
Management/Define Default Values for Automatic Clearing
Define Default Values for Resetting Clearing
 In this activity, you define a document type and a clearing reason. The system uses this information when
posting the clearing document and defaults it when you clear open items.

71
Requirements
The document type is created.
Activities
PATH:
Management/Define Default Values for Resetting Clearing
 In this activity you define a main transaction and a sub-transaction as a default value. This information is
used when resetting cleared items to be able to post the clearing document. The following takes place when
you reset a clearing:
1. The clearing document gets open items instead of the reset clearing items. The total of these open items
matches the previous clearing amount.
2. For further processing, however, the clearing amount should be made available in an item. A document is
posted for this purpose which offsets the open items generated and creates an item for the same amount as
the clearing amount. You define the main and partial transaction for the open item in this activity in
dependence on the previous clearing reason for the open item in this activity.
Requirements
You defined a main transaction and a sub-transaction.
Activities
PATH:
Management/Define Default for Resetting Clearing
Maintain Tolerance Groups
 In this activity you define tolerance groups for clearing open items when processing incoming payments.
You assign tolerance groups to contract accounts in the master records of the contract accounts.

72
Activities
1. Define the tolerance groups.
2. Ensure that you have defined the appropriate tolerance groups in the contract account master records.
The tolerance values are otherwise not effective.
PATH:
Management/Maintain Tolerance Groups
Assign Item Categories to Main and Sub-Transactions
 In this work step you assign item categories to main and sub-transactions.
Main transactions and sub-transactions fulfill these functions:
They document which aspect of a business transaction or process the line item entry is based on. A short
description is assigned to each main and sub-transaction for this purpose, and this can be used in
correspondence. In many processes, main and sub-transactions can influence automatic account
determination.
An internal main transaction can be assigned to the main transaction, and an internal sub-transaction can be
assigned to the sub-transaction. Internal transactions control the way in which application-specific processing
programs run. The sub-transaction differentiates the main transaction.
If your application area is using main and sub-transactions, then specify the appropriate ones during document
entry.
PATH:
Management/Assign Item Categories to Main and Sub-Transactions

73
Clearing Control
Clearing Variants
With clearing control you can display your company's automatic assignment and clearing strategy. It can be
displayed differently depending on the contract account or the business transaction. You can use your
individual settings to determine which contract account items are to be selected for clearing. You can also
group items according to different criteria and use amount-based clearing rules for these groups. If you wish to
determine a particular clearing sequence, you can sort the items accordingly and carry out partial clearing
using special distribution algorithms.
Clearing control can be used in the following areas: Payment assignment, Payment lots, Check lots,
Payment at cash desk
In payment assignment, each payment to be entered has a particular note to payee from the payer. The
payer's note to payee can differ in terms of detail.
Clearing Control
Clearing Variants/Define Grouping and Sorting Features BP 04-1 Process ACH
 In this activity you can define open item sorting and grouping characteristics. These usually refer to a
particular feature, for example when the item is a cash security deposit, or when the item is due. The
characteristics defined here are used in a clearing step for two purposes:
1. One purpose is to group open items. Open items found in one clearing step that bear identical grouping
characteristic values are viewed as one unit in this step, for example all items with the same due date. All
items in a group such as this are either all included in, or all excluded from, settlement, depending on the
clearing rule being applied.

74
2. The characteristics are also used to define the sorting sequence for open items. Sorting determines the
sequence in which the groups are processed and the sequence in which clearing takes place within the
groups.
SAP Standard delivers a selection of grouping and sorting characteristics. If you find these to be insufficient,
you can add new ones for clearing control. There are two ways of going about this:
1. Characteristic is an attribute of the open item
If the new characteristic is stored in the open item as a database field (database table FKKOP), you can add
the characteristic and enter the relevant database field names into the definition for the characteristics. The
field Active module will then remain empty.
2. Characteristic is derived
If the new module is not stored in the open item as a database field, but is derived from the clearing
information available, you can add a characteristic. Select a name in the customer range (X*, Y* and Z*) for
the field. The characteristic is then derived using the function module you have entered in the field Active
module. This module's interface must correspond to the interface of sample module FKK_SAMPLE_TFK116.
You will find detailed information on this in its documentation.
Standard Settings
You cannot change the entries that have been delivered to you. You can use the following name ranges: X*,
Y*, Z* (customer name range).
If the grouping and sorting characteristics delivered by SAP are insufficient, you can add new ones.
Activities
 Define the additional grouping and sorting characteristics you require.
 If necessary, generate a function module to derive characteristics and assign this to the new
characteristic.
PATH:
Management/Clearing Control/Clearing Variants/Define Grouping and Sorting Features

75
Clearing Control
Clearing Variants/Define Amount Check Group
Amount Check Group for Checking Value Limits During Clearing - Key under which the value limits for amount
difference checks are stored. Amount check groups are used within a clearing step for defining amount-
dependent clearing conditions. Within the group of open items determined by the grouping string, the following
is checked: A) When creating payment procedures: The difference between the payment amount available and
the total balance of the open items in the group already posted. B) For other 'clearing' business transactions:
The difference between the total of credit items and the total of receivables items in the group.
 In this activity you maintain the amount check groups. These are used in a clearing step to define amount-
dependent clearing conditions.
Within a group of open items, the check groups are used as follows:
1. In the case of incoming payments, the difference between the payment amount and the overall balance of
the open items of a group already posted is subjected to an amount check.
2. With all other transactions, the difference between the total of the credit items and the total of the
receivable items is checked.
Amount checks enable you to establish whether there are any amount discrepancies where clearing is
permitted. Note that the amount check group does not have the functions of the tolerance group defined in the
contract account. It is only used to determine whether clearing should take place. The amount differences that
are determined from the payment and item assignment in accordance with the specifications of the amount
check group are not written off explicitly, but, depending on additional specifications of the clearing activity,
they can be written off, cleared, or posted on account.
Activities
Create the amount check groups that you require. Ensure that you define the check groups to be currency-
dependent.
PATH:
Management/Clearing Control/Clearing Variants/Define Amount Check Group
Amount Check Group (Header)

76
Amount Check Group
Clearing Control
Clearing Variants/Define Clearing Variants BP 04-1 Process ACH
 In this activity you define clearing variants. A clearing variant consists of two components: Clearing variant
key, Clearing steps
Additionally, you can define alternative groupings and ranking orders for the individually used characteristics
for each clearing step.
Clearing variant key

The clearing variant key defines the name of the clearing variant. Additionally, a short description of the
clearing variant can be defined.
Clearing steps
Every clearing variant should consist of at least one clearing step. The individual steps are to run consecutively
in ascending order, as long as no subsequent step rule has been defined explicitly.
The individual steps are largely independent of one another. They only get the amount to be cleared that still
remains from the previous clearing step. Items that have been fully cleared in a clearing step are not
transferred to the subsequent steps. With the exception of this rule, all clearing steps work independently of
one another on the quantity of open items provided.
The definition of a clearing step consists of entries in the: Grouping string, Sorting string, Grouping rules
and the Clearing step end specifications.
Activities
1. Maintain the grouping string
2. Define a rule for grouping characteristic values.
3. Maintain the sorting string.
4. Maintain a ranking order and a sorting.

77
PATH:
Management/Clearing Control/Clearing Variants/Define Clearing Variants
Clearing Steps

78
Clearing Control
Define Clearing Categories BP 04-1 Process ACH
 In this activity you define the clearing categories. The clearing categories are used in combination with the
clearing types to determine the clearing variants. The clearing category is defined in the contract account.
This means that you can assign individual clearing rules to different customer groups, such as budget,
industry, and public institutions using the clearing category.
PATH:
Management/Clearing Control/Define Clearing Categories

79
Clearing Control
Define Clearing Types
 In this activity, you maintain the clearing types. The clearing type represents the business transaction in
which item assignment or grouping takes place for the clearing posting. The clearing types are structured
according to their area of implementation (for example, incoming payment, account maintenance).
You cannot change the clearing types delivered by SAP. They correspond to the source used in the clearing
process, with some exceptions.
Special Features of Clearing Types for IS-U Billing (Industry component Utilities)
In billing, you can override the predefined clearing types using a customer-specific form of the FI-CA event
R400. The form of the event as delivered by SAP controls the clearing type dependent on the respective
settlement transaction of the billed settlement document. The system only uses clearing type R4 if it cannot
find a unique settlement transaction.
For more information, see the documentation of sample function module ISU_SAMPLE_R400.
Example
The following clearing types are possible: Payment lot, Cash, Account maintenance, Payment run, Periodic
billing, Closing billing
Standard settings
You cannot change the entries delivered. Use the naming conventions X*, Y*, and Z* (customer naming
conventions).
Activities
If you require additional clearing types (for billing, for example), define them in the system.

80
PATH:
Management/Clearing Control/Define Clearing Types
Clearing Control
Define Specifications for clearing Types
 Specifications maintenance is structured according to the usage areas for clearing types: Incoming payment
specifications, Account maintenance specifications, Collective bill/installment plan specifications and so on,
Invoicing specifications (IS-U)
Clearing variant determination

Clearing variant determination takes place in all usage areas according to a uniform logic. Clearing category-
specific determination is supported, as is determination independent of the clearing category. If no clearing
variant is entered for the clearing category of the contract account to be paid, or if this is not unique in cross-
contract account analysis (for example when paying on a business partner) the general (default) clearing
variant is used.
Restricting item selection at transaction level

In addition to entering a clearing variant you can also make a pre-selection for clearing in this activity (not for
collective bill/installment plan specifications and so on). Selection of open items takes place as standard
under the clearing restriction defined in the item, in the context of the respective business transaction.
Additionally, for each transaction you can define selection restrictions prior to the actual item assignment for
clearing. In this activity you make some basic definitions for item selection, dependent on the clearing type and
clearing category, for example which due dates are to be taken into account or which transactions are to be
completely excluded from clearing analysis.
Restriction maintenance is possible on multiple levels. If a valid entry is found for an open item, the system
decides whether the item takes part in the clearing analysis or not on the basis of the selection rule and the
grace days.

81
PATH:
Management/Clearing Control/Define Specifications for Clearing Types/Define Defaults for Incoming
Payments
Clearing Control
Define Defaults for Account Maintenance BP 04-1 Process ACH
 Same details as defined in the ‘Clearing Control’ Define Specifications for clearing Types section.
PATH:
Management/Clearing Control/Define Specifications for Clearing Types/Define Defaults for Account
Maintenance

82
Key that references the contract account reference in automatic clearing postings. In combination with the clearing type it
forms the key under which clearing rules are defined in Contract Accounts Receivable and Payable.
Key under which the rules for automatic assignment of open items for clearing postings are defined.

83
Clearing Control
Define Defaults for Collective Invoice/Installment Plan/Summarization Group
 You will find detailed information in the documentation for chapter ‘Clearing Control’ Define
Specifications for clearing Types section
Usage
You use the clearing types maintained in this activity to distribute back to the original items any clearing
amount that might ensue from any clearing processing (such as incoming payment, account maintenance)
conducted on a collective bill, installment plan and so on.
Special Features
The clearing variant defined for these clearing types must guarantee that the clearing amount in question can
be distributed in full to the related dependent single items. The variant may not use any rules for automatically
writing off tolerance discrepancies. Otherwise, processing will be terminated.
Special Features with a Collective Invoice

You should note that when you distribute a clearing amount made with respect to a collective invoice back to
the relevant tenant items, you must make the definition of the variant that depends on the clearing category
depend on the clearing category of the collective contract account.
PATH:
Management/Clearing Control/Define Specifications for Clearing Types/Define Defaults for
Collective Invoice/Installment Plan/Summarization Group

84
Basic Functions/Correspondence
In the following activities, you create settings for correspondence generation.
Define Correspondence Types BP 09-2 Correspondence for Payment Confirmation and

Notification
 In this activity you can define your own correspondence types. The definition of own correspondence types
should be carried out by experienced ABAP developers, and requires the implementation of the following
function modules: Creation of correspondence - (for an example of this see Creating Account Statements),
Printing correspondence – (for example, Printing Account Statements)
Own correspondence types must be developed in the customer name range, otherwise they will be considered
as modifications.
Example
Correspondence type 0002 can be taken as an example (balanced account statement).
This uses the function modules mentioned above Creating Account Statements and Printing Account
Statements. Please note that the mass creation of account statements was implemented using Mass
activities. For this, an interval module for Event 1700 and an additional parameter module for Event 1701 were
implemented.
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Basic
Functions/Correspondence/Define Correspondence Types

85
Define Charge Types for Correspondence
 In this step you define charge types for correspondence. The defined charge types are assigned to charge
schemas in step Configure charge schemas for correspondence.
Note
The charge types are used in various application components. You may find, therefore, that charge types have
already been maintained.
Activities
1. Check the charge types provided and change them as required.
2. Define new charge types if necessary.

86
PATH:
Functions/Correspondence/Define Charge Types for Correspondence
Configure Charge Schedules for Correspondence

 In this step you configure the charge schemas for correspondence. The defined charge schemas are
assigned to correspondence variants in step Configure correspondence variants.
Note
The charge schemas are used in various application components. You may find, therefore, that charge
schemas have already been maintained.
Requirements
The necessary charge types are maintained.
Activities
1. Check the charge schemas provided and change them as required.
2. To create a new charge schema, proceed as follows:
a) Define the charge schema
b) Assign up to three charge types to the charge schema
c) Create charge scales for each charge schema
PATH:
Functions/Correspondence/Configure Charge Schedules for Correspondence

87
Configure Correspondence Variants
 In this step you configure correspondence variants. The defined correspondence variants can be assigned
to contract accounts at the business partner/contract account level.
Requirements
The necessary charge schedules are maintained.
Activities
1. Check the provided correspondence types and change them as needed.
2. To create a new correspondence variant, proceed as follows:
a) Define the correspondence variant
b) Determine the correspondence types required, each in connection with a charge schema
and other data
PATH:
Functions/Correspondence/Configure Correspondence Variants
Define Correspondence Roles

 Here you can define correspondence roles.
PATH:
Functions/Correspondence/Define Correspondence Roles

88
Configure Address Determination
 In this activity you can configure the address determination for the individual correspondence types and
roles.
Example
- If you enter the address type 'dunning address' for correspondence type 003 (dunning), then the dunning
notices will always be sent to the dunning address of the correspondence recipient.
- If do not enter a dunning address for the correspondence recipient, the standard address of the
correspondence recipient is used.
- If you do not enter an address type for the correspondence type, the correspondence is always sent to the
standard address of the correspondence recipient.
Requirements
The address types must be maintained.
Further notes
If you enter the address determination for a correspondence type and leave the correspondence role blank,
this address determination applies for all the correspondence roles for this correspondence type.
You can, however, enter address types for any combination of correspondence type and role.
You can, for example, enter the following:
 Account statement in role First recipient -> Address type 'Account statement original address
 Account statement in role Second recipient -> Address type 'Account statement address copy'
PATH:
Functions/Correspondence/Configure Address Determination
Configure Correspondence Activities

 In this activity you can define the correspondence activities.
Example
Algorithms are used to define additional correspondence recipients, e.g. to determine the broker of an
insurance contract. In this case the correspondence activity module is defined for the correspondence activity
that carries out this calculation.
Requirements
 The required function modules exist in the system
 The required function modules all have the interface FKK_CORR_ACTIVITY_INTERFACE.
Activities
1. Check and make any necessary changes to the correspondence activities
delivered
2. If required, define new correspondence activities

89
PATH:
Functions/Correspondence/Configure Correspondence Activities
Define Standard Form Classes for Correspondence
 In this activity, you can define form classes for correspondence types. Standard correspondence types
delivered by SAP are already assigned to form classes. Changing the form classes of standard
correspondence types amounts to modifying the system. This is a task best attempted by developers
experienced with ABAP.
You can define a form class from the print workbench for any correspondence types you have developed
yourself in the customer name range at this point.
PATH:
Functions/Correspondence/Define Standard Form Classes for Correspondence

90
Define Application Forms for Correspondence
 In this activity you define an application form for each correspondence type and correspondence role.
The defined application forms are used when printing correspondence from the print workbench.
You can maintain application forms for some business transactions that override the forms defined in this
activity. This would allow you to define a separate form for each dunning activity.
Requirements
The necessary correspondence forms have been maintained.
Activities
Check the assignments provided and change them as needed.
Further notes
If you enter the form determination for a correspondence type and leave the correspondence role blank, this
form determination applies for all the correspondence roles for this correspondence type.
You can, however, also enter application forms for any combination of correspondence type and role.
You can, for example, enter the following:
 Account statement in role First recipient -> Application form 'Account statement original form'
 Account statement in role Second recipient -> Application form 'Account statement form copy

91
PATH:
Functions/Correspondence/Define Application Forms for Correspondence
Check Number Ranges for Payment Forms
 In this activity you check whether the number ranges for payment forms have been created correctly in the
system. When payment forms are printing, assignment of numbers is automatic.
The system requires the following number ranges:
Number
from to
range
00 000000000001 009999999999
01 010000000000 019999999999
02 020000000000 029999999999
03 030000000000 039999999999
04 040000000000 049999999999
05 050000000000 059999999999
06 060000000000 069999999999
07 070000000000 079999999999
08 080000000000 089999999999
09 090000000000 099999999999
These number ranges are in the standard system.
Activities
Check that the above number ranges are available and create any that are missing. If necessary you can also
create number ranges 10 - 99 in addition to the above list.
PATH:

92
Functions/Correspondence/Check Number Ranges for Payment Forms

93
94
Archiving
In the following activity, you create definitions for the archiving of correspondence.
Archiving
Define Archives for Paper Records
 In this activity, you define the document types to be used for the optical archiving of a correspondence type.
Requirements
The standard pre-assignment must be specified in the activity customizing document types for the SAP
Archive link.

95
PATH:
Functions/Correspondence/Archiving/Define Archives for Paper Records

96
Archiving
Activate Archive Information Structure for Correspondence Archive
 In this activity, you can activate the archive information structure for the correspondence archive.
Requirements
If you wish to access or display the archive, the archive info structure must be activated.
Activities
Select active
PATH:
Functions/Correspondence/Archiving/Activate Archive Information Structure for Correspondence
Archive

97
Basic Functions/Check Management BP 04-3 Process Check (Incl. Stale dated
checks)
In the following activities, you make the default settings for processing outgoing checks.
Specify Component for Reconciling Check Deposits
 In this activity, you define whether you want to reconcile cashed outgoing checks in Contract Accounts
Receivable and Payable (FI-CA) or in General Ledger Accounting (FI-GL).
In FI-GL, the reconciliation is done in a check clearing account that is managed on an open item basis. Checks
with automatic assignment of check number (payment document number = check number) are reconciled
there automatically. If you use the internal and external check number assignment as well as automatic check
assignment, that is the payment document number and check number are different, you have to carry out the
reconciliation in Contract Accounts Receivable and Payable.
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Basic Functions/Check
Management/Specify Component for Reconciling Check Deposits
Define Document Type for Check Encashment
 In this activity, you define the document type that you want to use for posting check encashments.
PATH:
Management/Define Document Type for Check Encashment
Define Bank Clearing Account for Encashment of Outgoing Checks
 Here you can define the bank clearing account to which cashed checks are posted individually against the
check clearing account. You can also specify the bank account to which the checks are cashed.

98
PATH:
Management/Define Bank Clearing Account for Encashment of Outgoing Checks

99
100
Expense and Revenue Accounts for Posting Cashed Outgoing Checks
 In this activity you define the expense and revenue accounts that you use to post amount differences
automatically in clarification processing of check management. You have to post amount differences if the
cashed amount reported by the bank is different to the issue data of a check.
PATH:
Management/Expense and Revenue Accounts for Posting Cashed Outgoing Checks

101
Settings for Check Creation
 In this activity you define general specifications for printing checks, such as bank data and specifications for
check number distribution.
PATH:
Management/Settings for Check Creation

102
Define Void Reasons for Checks BP 03-1 Void Checks
 In this activity you make the specification for the lock and voiding reasons that you want to use for voiding
and locking outgoing checks. You can assign the reasons as required.
Activities
- You can use voiding reasons for the check status Voided.
- You can use reasons that have the indicator Lock for the check status Locked.
- You can also define whether the cashing of a locked or voided check is to be posted automatically or whether
a clarification case (for check encashment) is to be created.
In the field Activity, you can enter a 6 digit code to control additional activities (for example, setting limited
clearing locks) in installation-specific customer modules. You can evaluate this field directly or use it as a key
for your own customer table.

103
PATH:
Management/Define Void Reasons for Checks

104
Assign Bank Accounts for Online Check Printing
 In this activity you define bank clearing accounts for online check printing.
Select the online check valid field to activate the account for outgoing online checks.
The bank clearing accounts are used as follows:
 When posting outgoing payments by check with the cash desk, the system checks the entered
clearing account. Only accounts that are defined in Customizing are permitted.
 When printing a check, the system defines the bank details data. If the account does not allow online
check printing, then printing is not possible.
Requirements
 The bank master data has been transferred to the SAP system (see IMG structure Financial
Accounting -> Bank Accounting Bank Directory Data Transfer). It is possible to maintain this master
data manually. Choose Accounting -> Financial Accounting -> Accounts Receivable from the SAP
Easy Access screen, then choose Master Data -> Bank.
 The house banks are defined in the SAP System (see IMG structure Financial Accounting -> Bank
Accounting -> Bank Accounts -> Define House Banks).
Activities
Define the required clearing accounts and bank data.

105
PATH:
Management/Assign Bank Accounts for Online Check Printing

106
Define Details for Lots for Manual Outgoing Checks
 In this activity, you define the man and sub-transaction and the payment block for posting business partner
items. In addition, you can define default values for the payment method and document type, which you can
then use for manual posting outgoing checks.
PATH:
Management/Define Details for Lots for Manual Outgoing Checks
Line Layout Variants for Lots for Manual Outgoing Checks
 In this activity, you define the line layout variants for manually entering outgoing checks in lots.
Activities
Create a variant and assign the desired fields to it.
PATH:
Management/Define Line Layout Variants for Lots for Manual Outgoing Checks

107
Variant Fields
Variant Fields

108
Define Check Clearing Account for Outgoing Checks
 In this activity, you define the clearing account that you want to post cashed, manually issued outgoing
checks to.
PATH:
Management/Define Check Clearing Account for Outgoing Checks
Define Specifications for the Clarification of Cashed Checks BP 05-7 check Clarification
 In this activity you can define document types that you use for posting expenses and revenues for the
clarification of cashed checks. They system then proposes the document types defined here automatically
during posting.
Expense postings arise from clarification, for example, if you write off an encashment completely; revenue
postings arise, for example, if you post an encashment despite minor amount differences between the data at
the time of issue and the time of encashment.
PATH:
Management/Define Specifications for the Clarification of Cashed Checks

109
Basic Functions/Withholding Tax
In the following activities you execute the settings for the simple withholding tax
Check Sub-transactions for Withholding Tax Relevance
 In this activity, you can check whether withholding tax has to be posted for the sub-transactions you have
defined. If withholding tax is to be posted for certain sub-transactions, choose the relevant setting from the
input help in the column Withholding Tax Withheld.
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Basic Functions/Withholding
Tax/Check Sub-transactions for Withholding Tax Relevance

110
111
112
113
Define Withholding Tax Code
 The system requires a withholding tax indicator to be able to determine withholding tax. For every indicator
you must stipulate the following: Taxable portion: Here it is possible to calculate withholding tax with a
calculation basis of over 100%. This procedure is sometimes used in Spain., Withholding tax rate:
Percentage to be applied to the withholding tax base amount to calculate the withholding tax amount. In this
field you can also enter the German "reunification tax" as a percentage, Reduced withholding tax rate: if a
valid exemption certificate is in hand, Withholding tax formula: Only select the withholding tax formula field if
the tax percentages are graduated.
Withholding tax indicators must be defined country-specific.
Standard settings
The SAP standard system includes defined withholding tax indicators for those countries in which withholding
tax must be posted.
Activities
Check the standard list of withholding tax indicators and make any corrections, as necessary.
Further notes
Do not change or delete any indicators and their related definition as long as there are still any open items for
this indicator. Otherwise errors will occur during payment transactions.
PATH:
Tax/Define Withholding Tax Code

114
Define Formulas for Withholding Tax Calculation
 In this activity you define the formulae for calculating withholding tax, if the tax percentage rate is scaled
dependent on the base amount.
Activities
1. Supplement the delivered list.
2. For each withholding tax country and withholding tax code you need to enter the amount and the
withholding tax rate according to which the withholding tax is calculated.
PATH:
Tax/Define Formulas for Withholding Tax Calculation
Account Assignments for Withholding Tax Postings with Outgoing Payments
 In this activity you define the account assignments for withholding tax postings for outgoing payments.
Withholding Tax Account
General ledger account to which the withholding tax for outgoing payments is to be posted.
PATH:
Tax/Account Assignments for Withholding Tax Postings with Outgoing Payments

115
Account Assignments for Withholding Tax Supplements with Outgoing Payments
 In this activity you define the account assignments for additional withholding taxes for incoming payments.
PATH:
Tax/Account Assignments for Withholding Tax Supplements with Outgoing Payments
Account Assignments for Withholding Tax Postings with Incoming Payments

 In this activity you define the account assignments for withholding tax postings in the case of incoming
payments. Statistical withholding tax account. With every receivable where a customer can retain withholding
tax when paying the receivable, a statistical credit note item is created to the amount of the expected
withholding tax retention figure (credit note for withholding tax). The general ledger account for this credit note
item must be stated here. Withholding tax account. Here you enter the G/L account to which withholding tax
is posted when the statistical withholding tax item of the invoice document is cleared with an incoming
payment.
PATH:
Tax/Account Assignments for Withholding Tax Postings with Incoming Payments
Account Assignments for Withholding Tax Supplements with Incoming Payments

 In this activity you define account assignments for additional withholding taxes for incoming payments.
PATH:
Tax/Account Assignments for Withholding Tax Supplements with Incoming Payments

116
Payment Plans
In the following activities, you make the necessary settings for the payment plan functionality in the
Collections/Disbursements system. Note: To activate some of the settings made here, choose
Collections/Disbursements-> Activation of Basic Functions.
Define Number Ranges for Payment Plan items
 In this activity, you define number ranges for payment plan items.
Activities
Specify an internal number range and assign the number range number 01 to this.
The definition of an internal number range is only required if you do not transfer any external payment plan
numbers.
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Payment Plans/Define
Number Ranges for Payment Plan Items

117
Define Number Ranges for Payment Plan Items
 In this activity, you define number ranges for payment plan sub-items.
Activities
Specify an internal number range and assign the number range number 01 to this. As external numbers for
payment plan sub-items are not transferred to the interface, the definition of number ranges for payment plan
sub-items is obligatory.
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Payment Plans/Define
Number Ranges for Payment Plan Sub-items
Configuration of Payment Plans
In the following activities, you make the settings for configuring payment plans

Define Payment Plans and Attributes
 In this activity you define payment plans, define the most important attributes and activities for the
configuration of payment plans that are to be executed at certain times in the payment plan functionality.
The attributes are:
 The payment form, that is the periodicity of payments (weekly, monthly and so on), the number of
payments, the positioning of the due date within the period (start and end) and the period offset.
 The charge schedule
 Information about the splitting of difference or remaining amounts if a payment plan locks expires, if
the amount is changes or if a payment plan is finished early.
 Smoothing specifications, with which you create standard and even payment plan sub-items according
to your settings.
These attributes give you great freedom in payment plan configuration in respect of the number of partial
amounts that the payment plan items are split into to, the due date time and the amounts of the respective
partial amounts.
Three options are available to you:
Variant 1:
You use the periodicity proposals delivered by SAP (payment every week, every fourteen days, twice a month,
monthly, and so on).
1. Then click on the New entries pushbutton on the activity initial screen. This takes you to the detail screen
for defining the payment plan and maintaining the payment plan attributes.
2. Enter a payment plan keys, allocate a description for the payment plan to be configured and defined the
abovementioned attributes. Example: You want to define a payment plan that has a runtime of one year. The
partial amounts are due on a monthly basis according to this payment plan, and the amount of each partial
amount remains the same for each due date. In this case, use the input help to enter the value monthly in the
periodicity field.
118
Variant 2:
If the amount of each partial amount is not to be the same on each due date, you execute manual distribution.
You can then allow for possible specific receivables for certain insurance products in
Collections/Disbursements.
1. Now proceed as for the first variant.
2. Then go to the manual distribution view. For each period, enter the percentage rate for the payment plan
item that is due for this period. Alternatively you can create a proposal by pressing the generate distribution
button that you can adjust manually.
Note
By using manual distribution you can also define the payment plan so that no partial amount at all falls due in
certain periods. In this case, enter the value "Space" for the affected periods.
Variant 3:
You execute individual distribution of the partial amounts for payment plan items. You can then allow for the
possible specific wishes of individual policyholders in respect of the distribution of partial amounts. Individual
distribution is different from manual distribution in that you can deviate from the standard time units (weekly, bi-
weekly, monthly and so on) for the partial amount due dates. You define the individual distributions for the
insurance object in the payment plan items. In Customizing you just determine that individual distribution
should be executed. Set the corresponding indicator on the payment plan attribute maintenance detail screen.
Assigning activities
You can define activities that are to be executed for the following events in the payment plan functionality by
using the payment plan attribute maintenance:
 Posting a payment plan
 Changing the amount of payment plan items
 Ending a payment plan
Select the posting events node and/or change events from the dialog structure and enter the following data in
the table:
 ID number of the event.
 Key for the activity to be executed for this event.
 Function module that executes this activity.
You have already created this data in the Define Activities for Payment Plan Posting or Define Activities When
Changing Payment Plan Items Customizing activities.
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Payment Plans/Configuration
of Payment Plans/Define Payment Plans and Attributes

119
Define Payment Options
 In this activity, you define payment options. In a payment option, you group payment plans together and
define the payment plans that you can use for a change.
For payment plan changes, you make settings for the change date, the reversal procedure, charges and your
own function modules, if required, which trigger payment plan change activities.
PATH:
of Payment Plans/Define Payment Options

Define Specifications for Reversal
 In this activity, you define the document types that are required for a payment plan change, if documents
have already been posted for the original payment plan, or clearing has taken place. The document types for
this are "Reversal" (upper field), and "Resetting clearing" (lower field).
Example
A payment plan with monthly payment form was set to debit from 1/1 to 1/6; the premiums for January and
February have already been paid. The policyholder changes the payment plan on March 15th, to a quarterly
payment from, effective retroactively from 1/1. Dependent on the selected reversal procedure, which you have
defined for this payment plan change, clearings can be reset and open items can be reversed. The documents
produced receive the document types defined here.
PATH:
of Payment Plans/Define Specifications for Reversal

120
Define Specifications for Payment Plan Charges
 In this activity you define specifications for payment plan charges.
PATH:
of Payment Plans/Define Specifications for Payment Plan Charges

Define Charge Categories for Payment Plans
 In this activity you define charge categories for payment plans. The defined charge categories are assigned
to the charge schedules in the Define Charge Schedules for Payment Plans activity.
Note
The charge categories are used in different application components. It is possible that charge categories are
already maintained here.
Activities
 Check the delivered charge categories and change them where appropriate.
 Define possible new charge categories.
PATH:
of Payment Plans/Define Charge Categories for Payment Plans

121
Define Charge Schedules for Payment Plans
 In this activity you configure charge schedules for payment plans.
 You assign the defined charge schedules to payments plans in the Define payment plans and
attributes activity. The charges are created during the debit entry for payment plan items.
 You assign the defined charge schedules to payment plans in the Define payment plans activity, and
you can switch between the payment plans.
Note
The charge schedules are used in different application components. It is therefore possible that charge
schedules have already been maintained here.
Requirements
The required charge categories are maintained.
Activities
Check the delivered charge schedules and change where necessary.
To create a new charge schedule, proceed as follows:
1. Define the charge schedule.
2. Assign up to three charge categories to the charge schedule.
3. Create charge scales for each charge schedule.
PATH:
of Payment Plans/Define Charge Schedules for Payment Plans

122
/Payment Plan Posting/Assign Subtransactions to Payt Plan-Specific Main Transactions (S/L
item)
 Items are created in the execute payment plan function from the payment plan items that come from the
operational system into the Collections/Disbursements system. The main transaction that is assigned to the
payment plan item for data transfer, is transferred to these items. If there is also a sub-transaction assigned to
the payment plan item, then this is also transferred to the item.
It is only possible to specify payment plan items according to sub- transactions during the transfer from the
operational system in certain cases, where just one item comes from the payment plan item (with charges, for
example). If, however, the payment plan item is split into several individual items in the
Collections/Disbursements system (as with premium requests), then assignment of individual items to sub-
transactions can only take place within the Collections/Disbursements system. Then the
Collections/Disbursements system can recognize whether the individual items are initial or subsequent
premiums, for example.
Make the necessary settings in this IMG activity for this assignment: You define which sub-transactions are to
be assigned to the individual items. You can differentiate between the following sub-transactions:
 Initial premium
 Initial premium for a renewed payment plan item
 Subsequent premium
 Final premium for a renewed payment plan item
 Final premium
PATH:

123
of Payment Plans/ Payment Plan Posting/Assign Subtransactions to Payt Plan-Specific Main
Transactions (S/L item)

Payment Plan Posting/Assign Subtransactions to Payt Plan-Specific Main Transactions (G/L
item)
 In the execute payment plans function, items are created from the payment plan items that come to the
Collections/Disbursement system from the operational system. The main transaction that was assigned to the
payment plan item in data transfer is transferred to this item. If a sub-transaction is also assigned to the
payment plan item, this is also transferred to the item.
It is only possible to specify payment plan items when transferring from the operational system according to
sub-transactions if just one item comes from the payment plan item (such as with charges, for example).
However, if the payment plan item in the Collections/Disbursements system is split into multiple individual
items (as with premium receivables), the assignment of the individual items to sub-transactions can only take
place within the Collections/Disbursements system itself. Only the Collections/Disbursements system can
recognize whether the individual items are initial or subsequent premiums.
Unlike the IMG node Assign Sub-transactions to Payment Plan-Specific Main Transactions (S/L Item), the
main and sub-transactions define for the general ledger items are used to influence general ledger account
determination.
PATH:
of Payment Plans/ Payment Plan Posting/Assign Subtransactions to Payt Plan-Specific Main
Transactions (G/L item)

124
Payment Plan Posting/Define Activities for Payment Plan Posting
 In this activity you define one or more
Activities that are to be executed in conjunction with a payment plan posting. These can include creating
correspondence, or informing the policy management system.
If the respective activity occurs during correspondence creation, define a suitable application form in the "form
for correspondence" field.
Requirements
You have defined your own application forms for correspondence as a result of payment plan postings, if you
do not want to use the forms delivered by SAP (see IMG structure Insurance Industry Component ->
Collections/Disbursements -> Basic Functions -> Correspondence -> Define Application Forms)
Activities
The function modules delivered by SAP must have customer-specific maintenance.
PATH:
of Payment Plans/ Payment Plan Posting/ Define Activities for Payment Plan Posting
Settings for Debit Entry

In the following activities, you make the settings that affect the debit entry in a payment plan

Define Item Grouping Categories
 In this activity you can define grouping categories for open items. This allows certain payment plan items to
be grouped in one document with multiple line items.
The following fields are obligatory for grouping, and defined in the system:
 Business partner
 Insurance object
 Currency
 Document type
Activities
1. First define a grouping category by entering a key and a description.
2. Subsequently, define the item grouping fields (criteria), which are used to characterize this grouping
category.
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Payment Plans// Settings for
Debit Entry/Define Item Grouping Categories

125
Define Item Summarization Categories
 In this activity you define summarization categories for open items. This allows certain payment plan items
to be grouped in a single item.
The following fields are obligatory for summarization and are defined in the system: Business partner,
Insurance object, Currency, Due date, Deferral date, Document type, Main and sub-transaction, Statistical
indicator, Insurance tax schedule
Activities
1. First define a summarization category by entering a key and a description.
2. Subsequently, define the item summarization fields (criteria), which are used to characterize this
summarization category.
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Payment Plans/Settings for
Debit Entry/ Define Item Summarization Categories

Define Clearing Specifications
 In this activity, you define parameters for clearing
 For payment plans with customer-initiated payment method, if an incoming payment for the
policyholder and an open item are cleared using the Execute payment plans (VYSPA) function.
 For payment plan items, which are delivered from an operational system with the specification that
they are to be cleared with credit internally.
PATH:

126
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Payment Plans/Settings for
Debit Entry/ Define Clearing Specifications
Item Display Setting

 In this IMG Activity you set the length of time (in days) that payment plan items and payment plan sub-
items, which have not been set to debit, will be displayed in the account balance chronology.
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Payment Plans/Item Display
Setting
Data Transfer
In the following activity you make definitions for transfer of business partner data or business partner
relationship data from an external system to a SAP R/3 System. These activities are not relevant if you are
using a CRM/EBP System.
Data transfer takes place in several stages:

1. Relevant data is read from the external system and placed in a sequential file by the data selection
program. The data structure of the file is defined in the sender structure.
This procedure takes place outside of the R/3 environment and is not supported by R/3 programs. For this
reason, data changes can be made at this point by the data selection program.
2. The sequential file is stored on an R/3 application server or an R/3 presentation server.
3. The R/3 transfer program reads data from the file and places this in the sender structure. This does not
change the data. This step is carried out internally by the system and does not affect the user.
4. Following transfer rules that have to be defined, the R/3 transfer program takes the data from the sender
structure and places it in the receiver structure. During this step you can change or convert data.
The receiver structure is firmly defined in the SAP system. Assignment of the sender structure to the transfer
program, and of the transfer program to the receiver structure is made using a defined transfer category.
5. The data records in the receiver structure are processed one after the other and, if they do not contain any
errors, they are saved in the database.
Before you transfer external data for the first time, make the following determinations:

127
 The structure of the data in the external system may not match the structure expected by the SAP
system. You may have to supplement data.
There are two ways in which you can adapt the structure:
o You make the required conversions and enhancements within the data selection program prior to
beginning the transfer to the SAP system. This will be the most practical solution in most cases
since you have the most freedom at this point.
o You do the conversion using a specially developed R/3 transfer program and transfer rules.
 You then define the fields of the sender structure. The system offers you the option of automatically
generating a sender structure that is compatible with the receiver structure.
 You define transfer rules to create rules according to which the fields of the sender structure are linked
with those of the receiver structure.
You now carry out the transfer.
Data Transfer
Define Sender Structure
 For every sender structure, you need to define the makeup of the records which will be transferred from a
source system into R/3. This depicts the data record structure of the data to be transferred, which includes the
order and technical description of the fields (field category, length, and text). In defining these structures, you
can use existing structures and tables from the ABAP Dictionary (for example, receiver structures), or define
your own sender structure. When using SAP structures and tables please note that these can change with a
new release.
This Customizing function as well as the one for defining the transfer rules are used in various applications
(such as EC-EIS, CO-PA, TR-TM and IS Banking). For each individual application there are several small
differences in the functions, each of which is noted in the application.
Initial screen
On the initial screen you see a table of the sender structures already defined. When you implement R/3, this
may be empty.
Overview screen
The input fields on this screen are divided into three areas:
 The upper part contains the input fields for the name (user-defined) of the sender structure to be
defined, and for a short descriptive text.
 The middle part differs in the individual applications. It serves, for example, to assign the sender
structure to an object (transfer type, aspect, characteristic, etc.), and also to enter necessary details.
 The lower part shows a table (in EC-EIS, several tables) in which you input the names of structures
which already exist in the ABAP Dictionary, or the names of ones which you wish to define as new. If
you use an existing structure, it has the disadvantage that you can not change it subsequently. If you
want to define and include a new ABAP dictionary structure, the name always has to begin with
'RKCT'. You must then add three additional alpha-numeric characters of your choice. You define the
new ABAP Dictionary structure in a detail screen.
Detail screen
In the detail screen you can define a new ABAP Dictionary structure or change one that you defined before.
To define the structure, you can either use a template in this screen, or define the structure yourself. The
system will automatically generate a receiver structure based on the specifications for the object in the middle
part of the previous screen.
If you want to define the sender structure yourself, you have two options. You can either define the sender
fields yourself or use ones from the ABAP Dictionary.
In the first instance, you can choose the name yourself. Then you have to complete the following entries in the
column:
o Meaning, as a short descriptive text;
o Category, field category (C, N, P, X, D, T, I, F);
o Length of the field;
o Decimal place, the number of decimal places (only for field category P).

128
In the second instance you enter the name of a field from the ABAP Dictionary in the column sender field in the
table, and the name of the table in which it is found (reference table) in the column table. The entries are then
automatically taken from the ABAP Dictionary.
For general information on creating structures see the SAP Library: BC-ABAP Workbench -> BC-ABAP
Dictionary.
Activities
1. In order to define a new sender structure, choose Edit -> New entries. The overview screen appears.
2. Assign a name to the sender structure and provide a short description.
3. Enter a transfer category and confirm your entry. When you assign a transfer category, the fields in the
receiver structure are set.
If you choose transfer category '1' (finance objects) or '2' (periods), you will be prompted to enter additional
information in the profitability or risk management areas.
4. In the table in the lower part enter '1' under item. You can ignore the other rows in the table because the
sender structure only uses one ABAP Dictionary structure.
5. Under Dictionary structure, enter the name of an ABAP Dictionary structure, or a name which conforms to
the naming convention.
6. To define a new ABAP Dictionary structure, select the row and choose Goto -> Choose. The detail screen
appears.
7. If you want to use the receiver structure as a template for the new ABAP Dictionary structure, choose
Sender structure -> Include template (If you get a deletion message, choose LS>continue). The fields from the
receiver structure will be included.
8. Save your entries.
Note
Output fields for the log can only be filled with values if the field names of the sender structure match those or
the receiver structure. We therefore recommend that you use the receiver structure as a template and that you
do not change the field names.
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Payment Plans/ Data
Transfer/Define Sender Structure

129
Archiving
In the following activities you make definitions for archiving
Archiving
Define Runtime for Payment Plans
 In this activity you define the minimum number of days a payment plan must be in the system before it can
be archived.
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Payment Plans/
Archiving/Define Runtime for Payment Plans

130
Business Transactions
You make specifications in the following activities which are important for the special business
transactions.
Define Alternative Currencies
 In this activity, you can define the use of a different currency to the transaction currency for specific
business transactions for each company code.
Activities
For the business transactions where you want to use alternative currencies, define the required currency in the
field Alternative Currency.
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Business
Transactions/Define Alternative Currencies
Invoicing (FS-CD)
In the following activities, you create definitions that are required to invoice items.
Invoicing (FS-CD)
Assign Invoicing Parameters to Main and Sub-Transactions
 In this work step, you set the transaction excluded from invoicing indicator for main and sub-transactions
selected by you

131
PATH:
Transactions/Invoicing (FS-CD)/Assign Invoicing Parameters to Main and Sub-Transactions

132
Invoicing (FS-CD)
Define Invoicing Types
 In this activity, you define invoicing types.
Activities
1. Check and change the standard invoicing types where necessary.
2. Define any additional invoicing types you require.
Further notes
You use the Correspondence component to create print forms for invoices.
PATH:
Transactions/Invoicing (FS-CD)/Define Invoicing Types

133
Invoicing (FS-CD)
Define Additional Payment Methods for Invoicing Types
 In this activity, you define additional payment methods for an invoicing type
Example
On items from those business partners for which no payment method is entered in the contract account /
insurance object master data (direct payer), are taken into account for invoicing. However, it may be that you
want items that refer to a payment method (clearing with deposit contract, for example) to appear on the
insurance invoice. In this case, assign an appropriately configured payment method to an invoicing type.
Recommendation
If you want to take all payment methods into account for invoicing, maintain the Invoicing for all payment
methods field in the Define invoicing types activity.
Activities
1. Check the defined payment methods, and change where necessary.
2. Add or delete payment methods where necessary.
PATH:
Transactions/Invoicing (FS-CD)/Define Additional Payment Methods for Invoicing Types
Blank in system

134
Invoicing (FS-CD)
Maintain House Banks for Invoicing
 In this activity you define which house bank should be printed e.g. on an enclosed payment document when
an invoice is issued. The house bank is assigned to a company code and a certain invoice category.
Example
When invoicing an account first check whether a house bank has been defined under the company code and
invoice category. With invoice category Invoicing and company code V001 the house bank is Deutsche Bank.
If this entry exists, the account can be invoiced, otherwise it will be skipped.
Requirements
 Company code is defined.
 House bank is defined.
Activities
Define the desired house bank for each company code and invoice category.
PATH:
Transactions/Invoicing (FS-CD)/Maintain House Banks for Invoicing
Invoicing (FS-CD)
Define Lock Reasons for Invoicing
 In this activity you define invoicing lock reasons. The lock reasons you define can be assigned to insurance
objects or individual line items.
Activities
1. Check and change the standard invoicing lock reasons if necessary.
2. Define any new invoicing lock reasons.
PATH:
Transactions/Invoicing (FS-CD)/Define Lock Reasons for Invoicing

135
Invoicing (FS-CD)
Archiving
In the following activities, you create definitions for archiving insurance invoices.
Invoicing (FS-CD)
Archiving/Define General Runtime for Invoicing History
 In this activity you define how many days an insurance invoice has to be in the system before it can be
archived.
PATH:
Transactions/Invoicing (FS-CD)/Archiving/Define General Runtime for Invoicing History
Invoicing (FS-CD)
Archiving/Define Runtime per Invoicing Type
 In this activity you define –in dependence on the invoicing type—how many days an insurance invoice has
to be in the system before it can be archived.
PATH:
Transactions/Invoicing (FS-CD)/Archiving/Define Runtime per Invoicing Type

136
Invoicing (FS-CD)
Archiving/Activate Archive Information Structure for Correspondence Archive
 In this activity you activate the archive info structure for the correspondence archive. When you access the
archive or want to display it, the archive info structure must be activated.
PATH:
Transactions/Invoicing (FS-CD)/Archiving/Activate Archive Information Structure for
Correspondence Archive
Payments
Incoming/Outgoing Payment Processing
In the following activities, you make settings for entering and processing incoming and outgoing
payments with the payment lot.
Define Default Values for Payment Lot
 In this activity you define a document type, a clearing reason and up to three selection types. These
specifications are proposed when entering payment lots and used for posting the clearing documents.

137
Requirements
 The required document type is defined.
 The required selection types are defined.
Activities
Define the required default values.
PATH:
Transactions/Payments/Incoming/Outgoing Payment Processing/Define Default Values for Payment
Lot
Define Default Values for Check Lot

 In this activity you define a document type, a clearing reason and up to three selection categories. These
entries are proposed as default when creating check lots and used for posting clearing documents.
Requirements
 The required selection categories are defined.
Activities
Define the desired default values.
PATH:
Transactions/Payments/Incoming/Outgoing Payment Processing/Define Default Values for Check
Lot

138
Define Default Values for Credit Card Lots
 In this activity you define a document type, a clearing reason, the type of processing with the credit card
company and up to three selection categories. These specifications are suggested when entering credit card
lots and are used for posting clearing documents.
Requirements
Activities
PATH:
Transactions/Payments/Incoming/Outgoing Payment Processing/Define Default Values for Credit
Card Lots
Define Default Values for Payment Order Lots

 In this activity you define a document type, a clearing reason and a selection category. These specifications
are suggested when entering payment order lots and are used for posting clearing documents.
Requirements
PATH:
Transactions/Payments/Incoming/Outgoing Payment Processing/Define Default Values for Payment
Order Lots

139
Define Bank Clearing Accounts for Payment Lots
 In this activity, you can define bank clearing accounts for the payment, check, payment card and returns
lots.
You can make the following settings:
 Choose the ValPaymtLot field to activate the account for payment lots
 Choose the ValCheck field to activate the account for check lots
 Choose the ValPCard field to activate the account for payment card lots
 Choose the ValRet field to activate the account for returns lots
The bank clearing accounts are used depending on the type of lot as follows:
 When you create or change a payment, check or payment card lot, the systems checks the clearing
accounts entered. Only accounts defined in Customizing are permitted
 During the check lot, the system uses the clearing account in the check lot to determine the bank
details data for the check deposit list.
Requirements
 The bank master data is transferred to the SAP system (see the IMG structure Financial Accounting ->
Bank Accounting -> Bank Directory Data Transfer).
It is possible to maintain the master data manually. To do so, go to SAP Easy Access and choose
Accounting -> Financial Accounting Accounts Receivable, and then Master records -> Bank.
 The house banks have been defined in the SAP system (see the IMG structure under Financial
Accounting -> Bank Accounting -> Bank Accounts -> Define House Banks).
Activities
Define the necessary clearing accounts and bank data.
PATH:
Transactions/Payments/Incoming/Outgoing Payment Processing/Define Bank Clearing Accounts for
Payment Lots

140
Define Clarification Account
 In this activity you define an interim account differentiated by keys. The incoming payment is automatically
posted to this G/L account if the selection specifications in a payment lot are not sufficient: For selecting open
items for payment, for determining a contract account for posting a payment on account. The interim account
defined is used if an interim account was not specified in the payment lot item.

141
Note
Additional automatic postings can be generated for the payment lot (such as exchange rate differences).
Requirements
You have created and defined the G/L accounts for the above-mentioned automatic postings.
Activities
Define the interim account for the payment lot.
PATH:
Transactions/Payments/Incoming/Outgoing Payment Processing/Define Clarification Account
Define Clearing Account for Check Deposit

 In this activity you define clearing accounts required for posting incoming checks. Two accounts are
necessary to post incoming checks: Check deposit account, Check clearing account
Activities
Define the clearing accounts.
PATH:
Transactions/Payments/Incoming/Outgoing Payment Processing/Define Clearing Account for Check
Deposit
Define Specifications for Repayment of Incoming Payments

142
 In this activity you define the G/L accounts in which clearing entries are generated automatically when
posting a payment lot, if the incoming payment amount is to be paid back. These G/L accounts are
differentiated by key. This is necessary if the system could not locate a business partner for the payment.
Example
You also define the payment method for repayment and a house bank key used to determine the house bank
data.
Requirements
Activities
Define the numbers of the repayment clearing accounts.
PATH:
Transactions/Payments/Incoming/Outgoing Payment Processing/Define Specifications for
Repayment of Incoming Payments
Check Number Ranges for Repayment Requests

 In this IMG activity, you check whether the number ranges for repayments in the system are correctly
created. If the payment program makes repayments, it requires the following number range for the automatic
issue of numbers:
Number range From number To number
01 000000000001 009999999999
**This is the number range that is provided for you, and is the only valid one.
Activities
Check whether the number range given above exists, creating it if necessary.
PATH:
Transactions/Payments/Incoming/Outgoing Payment Processing/Check Number Ranges for
Repayment Requests
Blank in the system.

143
Define Transactions for Electronic Bank Statement Transfer
 In this activity, you enter the external transaction code of the electronic bank statement that is to be
transferred to FI-CA, and classify it as ‘payment’, ‘return’, ‘payment order lot’, or ‘check encashment’.
Activities
Enter the transaction codes.
PATH:
Transactions/Payments/Incoming/Outgoing Payment Processing/Define Transactions for Electronic
Bank Statement Transfer
Group together the bank accounts which contain the same external transactions in one transaction type. You
can thereby reduce the processing work involved in Customizing for external transactions.
Incoming Amount
For an account statement item in the transfer to the payment, payment order, returns lot, or check
encashment, this controls whether and to what lot the item is to be transferred. The identification is derived as
standard from Customizing and can be defined in the function module for event 0955 according to customer-
defined rules.

144
The following values are possible: ‘01’ – Transfer to payment lot, ‘02’ – Transfer to returns lot, ‘03’ –
Transfer to payment order lot, ‘04’ – Transfer to check encashment
Define Programs for Converting Country-Specific Formats into MultiCash

 In this activity, you define the programs that you need to convert the payment media formats that you use
into MultiCash. The programs are offered for selection on the initial screen under Periodic Processing ->
Transfer Data -> From MultiCash File -> Convert Country-Specific Formats into MultiCash.
In this activity, you can: Set the indicator RNA for a program delivered by SAP if you do not use the
corresponding format, Add your own programs to the table
PATH:
Transactions/Payments/Incoming/Outgoing Payment Processing/Define Programs for Converting
Country-Specific formats into MultiCash
Blank in the system
Define Prefix for Created Lot IDs during Account Statement Transfer
 If you use transaction Electronic Account Statement (FPB7) (Periodic Processing -> Transfer Data) to
transfer payment data from the bank data storage to payment, returns, and payment order lots, in this activity,
you can define a prefix for every type of lot created during the transfer.
This prefix is taken into consideration for the generation of the key for the corresponding lot. You can
differentiate the prefixes for lot types by company code, house bank, and house bank account. The prefix
details are always considered during the transfer if you enter a maximum 8 figure character string in the
parameters for the transfer run (FPB7). In this case, the transfer program generates a key for the lot as
follows:
Prefix (2 figure) - character string (8 figure) - sequential number (2 figure)
 If you do not enter a character string in the parameters for the transfer run, the key for the lot is
generated as previously:
h = Housebank ID
y = Year
a = Statement number
l = Lot type ( 'P' - payment lot, 'R' - returns lot, 'O' - payment order lot)
n= sequential number
PATH:
Transactions/Payments/Incoming/Outgoing Payment Processing/Define Prefix for Created Lot IDs
during Account Statement Transfer

145
Define Bank Accounts with Individual Clarification Proposal
 In this activity, for selected business partner bank accounts, you can define alternative rules and individual
proposal values for the creation of proposals for the clarification of incoming payments.
These specifications are useful for example, if payments for a large number of business partners are to be
processed via the same bank account. In clarification processing, you can integrate the evaluation of all
existing clarifications cases for this account which, under certain circumstances, would lead to too large a
number of clarification proposals.
Example
Receivables from some of your customers are paid by the welfare office, and clarification cases occasionally
arise. To clarify payments transferred by the welfare office, all previous clarification cases for this account are
displayed in the clarification processing. To avoid this, you can:
 Integrate the evaluation of similar clarification cases
 Define explicit proposals (for example, business partner whose invoices are paid by the welfare office)
PATH:
Transactions/Payments/Incoming/Outgoing Payment Processing/Define Bank Accounts with
Individual Clarification Proposal

146
Define Short Account Assignments for Transfer Postings
 In this activity you can define the following specifications: Short account assignments for transfer postings
between G/L accounts, Addresses for notification mails
With the help of the short account assignments defined here, when you are working with a payment lot or
clarifying incoming payments, you can post amounts to the account defined in this short account assignment
without having to enter G/L account items. This is necessary, for example, if you do not want to clear items in a
contract account, or post them to a clarification account because the payment amount is meant for another
department.
If you select the workflow field, an event is triggered when entering the corresponding short account
assignment that can be processed further by other applications; to start a workflow in another department, for
example.
You can define mailing addresses for each short account assignment so that the processing clerks affected
will always receive a notification by mail. You can define external users with internet addresses and internal
addresses.
Activities
Define short account assignments and mail addresses.

147
PATH:
Transactions/Payments/Incoming/Outgoing Payment Processing/Define Short Account Assignments
for Transfer Postings
Define Forms for Check Deposit List

 In this activity, you define forms for the check deposit list.
Standard settings
The delivered form is used if you do not define your own form.
Activities
1. Define the required forms with SAPScript. Execute function
2. Define the form keys in this activity.
PATH:
Transactions/Payments/Incoming/Outgoing Payment Processing/Define Forms for Check Deposit
List
Click on ‘Form’ to display details
Assign DME Items to Document Types

 In this activity you define the document type with which a DME (data medium exchange) item is posted.
Incoming and outgoing payments not initiated by the payment program are posted with the document types
defined at this point. Each item in a data medium contains information that refers to the type of payment. You

148
assign the classifying data field along with its characteristics to a document type. If the specifications in the
data medium are not unique, you can define a function module with the correct interpretation of the data
medium item. The structure of the data medium varies from one country to another.
Example
Incoming and outgoing payments for a bank in Austria are processed in company code AT01 The Austrian
data medium format (stored in structure DTABATB) contains a classification of the business transaction in field
13. If the entry in the field is 15, this is a cash payment order that in this example must be assigned to
document type ZB. If you see 43 for a bank transfer instead, the payment document will be posted with ZU.
You have to maintain the following entries in this regard:
CoCde Country Structure Fld name Fld value Document type
AT01 AT DTABATB FIELD13 15 ZB
At01 AT DTABATB FIELD13 43 ZU
Requirements
The necessary document type is defined.
Activities
1. Identify the classifying data fields in Data Medium Exchange (DME).
2. Determine the name of the associated data structure. Execute function
3. Create a new data structure if necessary. Execute function
4. Assign document types to the contents of the classifying data fields.
5. Create a function module if you need a broader interpretation of the data medium items.
PATH:
Transactions/Payments/Incoming/Outgoing Payment Processing/Assign DME Items to Document
Types
Define Bank Clearing/Clarification Account for Bank Details - DME
 In this activity, you define bank clearing accounts and/or clarification accounts for transferring payment lot
or returns lot data with the Austrian format. More information is available in the following program
documentation: DME Inbound Processing (Austria)

149
Requirements
Activities
Define the necessary data.
PATH:
Transactions/Payments/Incoming/Outgoing Payment Processing/Assign DME Items to Document
Types
Define Workflow for Clarification Worklist for Payment Lots
 You can include your clarification worklist in a workflow. SAP provides the following two sample workflows
that you can use to create your own workflows:
 Simple workflow - WS21000078

You have to assign an agent before a clarification worklist can land in a clerk's workflow inbox. By
assigning an agent (clerk) and making restrictions on who is to process the case, you can ensure that
clarification cases are only assigned once to an agent. This means that if a clerk is unable to work
completely through a clarification case, the case is automatically transferred to a different agent for
further processing.
 Ad-hoc Workflow - WS21000077
With this workflow you do not have to assign an agent or make any restrictions. If a clerk is unable to
clarify the case, he/she is free to name another agent and to transfer the case in this way.
For this type of workflow, you make the Customizing setting Workflow with direct advance when you
are making general workflow settings, to ensure that the name of the next agent is always queried
directly after a clarification attempt.
Requirements
Make general Customizing settings for the workflow. (See R/3 Customizing Implementation Guide -> Cross-
Application Components -> Distribution (ALE) -> Error Handling -> Basic Workflow Settings).
Maintain processing statuses (see Contract Accounts Payable and Receivable -> Technical Settings ->
Prepare Processing of Clarification Worklist). For every processing status you can define a number of days for
which a clarification case should be deferred if a clerk selects the processing status. Here you can also define
whether a history should be updated if the clerk changes the processing status or general status.
Every workflow in a clarification worklist must contain the standard task Increase workflow counter of
clarification case so that the clarification case is marked as "being processed in a workflow". To remove this

150
marking, the workflow must contain the last step Workflow counter of clarification case -1 so that the name of
the next agent is always queried directly after the clarification attempt.
PATH:
Transactions/Payments/Incoming/Outgoing Payment Processing/Define Workflow for Clarification
Worklist for Payment Lots
** This path is for instructions and document information only – No screen prints available.
Define Splitting Type for Credit Splitting

 In this IMG activity, you define an allocation type for credit splitting. The allocation type specifies which
rules are used to allocate the disbursement amount to the various alternative payment recipients. You use the
Allocation Type field for the contract account or the contract, and dependent on the allocation type you can
only enter the Amount in Local Currency and Flag for Remaining Amount or Amount in Percent fields.
Activities
You define the following values:
 Allocation type ID
 Description of allocation type
 Function module for the input help for the Amount in Local Currency, Flag for Remaining Amount and
Amount in Percent fields (used in the Create/Change/Display Contract Account or
Create/Change/Display Insurance Object applications)
 Check module for the Amount in Local Currency, Flag for Remaining Amount and Amount in Percent
fields. According to the allocation type, you can define a function module here that checks the values
for the individual fields and their values (used in the Create/Change/Display Contract Account or
Create/Change/Display Insurance Object applications)
 Function module that allocates the amounts for an open credit item to the various alternative payment
recipients (used in the Allocate Credit to Multiple Recipients application, transaction VAZE)
This gives you the option of formatting the allocation of the disbursement for various contracts in different
ways. SAP provides a range of function modules for input help, the check module and the allocation of the
disbursement. If you have any other specific requirements for the allocation of a disbursement to various
payment recipients, you have to develop your own appropriate function modules in the customer namespace
and include them in the program with an allocation type configuration.
PATH:
Transactions/Payments/Incoming/Outgoing Payment Processing/Define Splitting Type for Credit
Splitting
Settings for Checking Suspicious Transactions (Money Laundering)

In this activity you make settings to check suspicious transactions

151
Define Criteria for Transactions to be Investigated
 In this activity you define criteria for the transactions that are to be investigated as a result of the money
laundering law, and for the transactions to be classified as suspicious.
You can define the conditions for a transaction to be considered suspicious for each company code, insurance
type and document type for a document. You can determine how suspicious a transaction is by checking the
clearing of line items. Transactions that are classified as suspicious as a result of this check go to the money
laundering clarification worklist from where they can be processed manually.
The following criteria are currently supported, that are dependent on the minimum/maximum amounts and
payment method defined for the account, contract or document:
 Returns: The transaction is suspicious if returns occur for a document that has already been cleared.
 Payment: That transaction is suspicious is a document is cleared by an externally initiated document.
This check makes sense above all if the payment method agreed with the customer is debit memo.
 Clearing: The transaction is suspicious is clearing takes place, for example if an outstanding life
insurance premium is cleared by a non- life insurance credit.
 Amount: The transaction is suspicious if it exceeds the set amount limits.
Requirements
The "money laundering active" indicator must be set in the TKKVBASIC table. Select
Collections/Disbursements -> Basic Functions -> Activation of Basic Functions in the IMG structure.
Activities
Enter the criteria for the suspicious transactions and transactions to be investigated.
Further notes
The money laundering checks run at event 0020, and you can make customer-specific definitions for the
VVKKREPCL_REPORT_CLEARING_0020 sample module called then.
PATH:
Transactions/Payments/Incoming/Outgoing Payment Processing/Define Criteria for Transactions to
be Investigated

Define Runtime for Suspicious Transactions
 In this activity you define how long documents remain in the system before they can be archived
PATH:
Transactions/Payments/Incoming/Outgoing Payment Processing/Define Criteria for Transactions to
be Investigated
Payments
Incoming/Outgoing Payment Creation

152
In the following activities, you make settings for the automatic creation of incoming and outgoing
payments with the payment program
Maintain Note to Payee Type for Payment Medium
 In this activity, you maintain the note to payee specifications for payment media in a note to payee type.
You assign the note to payee types to the payment methods in a country in the activity Define Payment
Methods.
Activities
1. Maintain your note to payee types
2. Make sure that the note to payee types are assigned to the payment methods.
With the button Simulation in the note to payee type, you can test the settings for the note to payee, even if
you have not carried out a payment run yet.
PATH:
Transactions/Payments/Incoming/Outgoing Payment Creation/Maintain Note to Payee Type for
Payment Medium
Define Payment Methods BP 02-1 Data Validation/Posting an BP 02-2 Bank Determination

153
 In this IMG activity, you define the payment methods per country. You need to specify a document type for
posting payment documents, and a format for all payment methods. The formats contain a description for the
sentence structure of the files created by the payment medium program. You can also define instruction keys
for the payment methods here. These control which instructions are given to the banks involved for the
execution of a payment order. The payment medium format defines whether an instruction key is executed.
Requirements
The document type required is created. Note that you need to assign a number range to the document type for
mass processing.
Standard settings
The SAP standard system contains payment methods and formats.
Activities
1. Check, and if necessary, change the payment methods provided.
2. If required, define new payment methods.
3. Determine which instructions are to be defined for the data medium exchange in the system. Define
these instructions.
PATH:
Transactions/Payments/Incoming/Outgoing Payment Creation/Define Payment Methods
Highlight and click ‘Payment Methods’

154
Define Specifications for Paying Company Code
 In this activity, you define the required specifications for the paying company code.
Requirements
 Each company code where you post must be assigned to at least one company code group; this is
then defined in the contract account. Then assign a paying company code to each company code
group.
 You have created the payment method for the country of the paying company code.
 You have transferred the bank master data to the SAP System (see IMG structure Financial
Accounting -> Bank Accounting -> Bank Directory Data Transfer).

155
You can maintain this master data manually. To do this, from the menu choose Accounting ->
Financial Accounting -> Accounts Receivable then Master Data -> Bank.
 You have defined the house banks in the SAP System (see IMG structure Financial Accounting ->
Bank Accounting -> Bank Accounts -> Define House Banks).
Activities
1. Make your specifications for the paying company code.
2. Define the required formula with SAPScript. Proceed
PATH:
Transactions/Payments/Incoming/Outgoing Payment Creation/Define Specifications for Paying
Company Code
Highlight and click ‘Payment Methods in Company Code
Define Accounts for Payment Program
 In this activity you define the numbers of the bank accounts or bank sub-accounts (G/L accounts) to which
the payment program posts in the R/3 System.
Note
The payment program makes any additional postings, such as cash discount or exchange rate differences.
Requirements
The G/L accounts for the above-mentioned additional automatic postings are created and defined in the
system.
Activities
Define the account numbers of the required bank accounts or bank sub-accounts.

156
PATH:
Transactions/Payments/Incoming/Outgoing Payment Creation/Define Accounts for Payment
Program

157
Maintain Bank Selection
 In this activity you can define the IDs for bank selections. In the ID, for each company code, payment
method, and currency, you define which bank the payment program should select for making payments.
You can enter the bank selection ID in the payment run on the tab strip Bank Selection in the field Selection
ID.
PATH:
Transactions/Payments/Incoming/Outgoing Payment Creation/Maintain Bank Selection
Highlight Bank ID and click on ‘Bank Selection Values’ field
BANK ID: ADP5

158
BANK ID: ADP1
BANK ID: ADP3
BANK ID: ADP4

159
BANK ID: ADPW
Define Payment Lock Reasons

 In this activity, you define payment lock reasons. You use payment lock reasons to prevent contract
accounts or individual line items from being paid with the payment program. Payment lock reasons also give
you the opportunity to explain why an item has been locked for payment. Locked items are output in an
exception list by the payment program. If you have marked the field "to clarify", the items are also included in
the clarification worklist for the payment run.
Standard settings
Payment lock reasons are defined in the standard system.
Activities
Check and change the standard lock reasons as necessary.
PATH:
Transactions/Payments/Incoming/Outgoing Payment Creation/Define Payment Lock Reasons

160
Select Item Indicator for the Clarification Worklist
 In this IMG activity, you specify which payment exceptions should go into the clarification worklist. To do
this, the item indicator must be set to "To clarify", and if a locking reason exists, this must also be indicated as
"To clarify".
Activities
1. In this IMG activity, enter the item indicators that are relevant for clarification.
2. Check that the payment locking reasons are correctly indicated (see IMG activity Define Payment
Locking Reasons).
PATH:
Transactions/Payments/Incoming/Outgoing Payment Creation/Select Item Indicator for the
Clarification Worklist

161
Define Scope of Exception List
 You can define the scope of the exception list here. Payment exceptions that you include in this list are not
taken into account for the payment run and so do not appear in the exception list.
PATH:
Transactions/Payments/Incoming/Outgoing Payment Creation/Select Item Indicator for the
Clarification Worklist
Define Correspondence for Insufficient Deposit Coverage

 In this activity, you define:
 The payment methods with internal clearing, for which insufficient coverage correspondence is created
 The minimum period (in days) that has to pass before the creation of the next correspondence
Amount categories
Choose Amount according to enclosed item so that the items that are not covered are listed in the
correspondence.
Correspondence for insufficient deposit coverage on a clearing account is created if you set the coverage letter
indicator on the Free selections tab page, in the payment run.
Correspondence types 24, 27, V036 and V037 are available for insufficient coverage letters.
Example
You use insufficient coverage letters if you pay insurance objects
Requirements
 You have defined payment methods and set the indicator for internal clearing for the payment method.
 You have assigned correspondence types for the insufficient coverage letter to correspondence
variants.
You can assign all correspondence types for insufficient coverage to a correspondence variant. In this
case, the system checks whether an insufficient coverage letter is created for each business partner,
contract account or payment group (in that order).
 To create insufficient coverage letters for a clearing account, set the Execute coverage check indicator
for the clearing account.
PATH:
Transactions/Payments/Incoming/Outgoing Payment Creation/Define Correspondence for
Insufficient Deposit Coverage

162
Check Number Ranges for Payment Orders
 In this activity you check whether the number ranges for payment orders have been created correctly in the
system. When the payment program creates payment orders, the following number ranges are required for
automatic number assignment:
Number range Interval
00 0000000001 - 09999999999
01 1000000000 - 19999999999
..
09 9000000000 - 99999999999
Activities
Check whether the number ranges specified above are available; create them if necessary.
Only maintain number ranges for payment orders if:
 The specified number ranges have not been correctly preset
 The available number ranges contain errors
 You want to increase the number of number ranges for intensive use of parallel processing
PATH:
Transactions/Payments/Incoming/Outgoing Payment Creation/Check Number Ranges for Payment
Orders

163
Further Prerequisites for the Payment Program
 So that the payment program and the payment medium program can process the items to be paid correctly
and can provide the data necessary for payment transactions, you have to make specifications in the master
data.
Activities
1. Make sure that all information necessary for payment transactions is entered in the business
partner's master data, such as the bank details.
2. Make sure that all information necessary for payment transactions is entered in the corresponding
contract account's master data, such as payment methods.
PATH:
Transactions/Payments/Incoming/Outgoing Payment Creation/Further Prerequisites for the Payment
Program
**No screen prints available. Informational ONLY.
Define Workflow for Clarification Worklist for Payment Run

 You can include your clarification worklist in a workflow. SAP provides the following two sample workflows
that you can use to create your own workflows:
1. Simple workflow - WS21000076

You have to assign an agent before a clarification worklist can land in a clerk's workflow inbox. By assigning
an agent (clerk) and making restrictions on who is to process the case, you can ensure that clarification cases
are only assigned once to an agent. This means that if a clerk is unable to work completely through a
clarification case, the case is automatically transferred to a different agent for further processing.
2. Ad-hoc Workflow - WS21000075
With this workflow you do not have to assign an agent or make any restrictions. If a clerk is unable to clarify
the case, he/she is free to name another agent and to transfer the case in this way.
For this type of workflow, you make the Customizing setting Workflow with direct advance when you are
making general workflow settings, to ensure that the name of the next agent is always queried directly after a
clarification attempt.
Requirements
Make general Customizing settings for the workflow. (See R/3 Customizing Implementation Guide -> Cross-
Application Components -> Distribution (ALE) -> Error Handling -> Basic Workflow Settings.
Maintain processing statuses (see Contract Accounts Payable and Receivable -> Technical Settings ->
Prepare Processing of Clarification Worklists). For every processing status you can define a number of days
for which a clarification case should be deferred if a clerk selects the processing status. Here you can also
define whether a history should be updated if the clerk changes the processing status or general status.
Every workflow in a clarification worklist must contain the standard task Increase workflow counter of
clarification case so that the clarification case is marked as "being processed in a workflow". To remove this
marking, the general workflow settings must contain the last step Workflow counter with direct advance so that
the name of the next agent is always queried directly after the clarification attempt.
PATH:
Transactions/Payments/Incoming/Outgoing Payment Creation/Define Workflow for Clarification
Worklist for Payment Run
**No screen prints available. Informational ONLY.

164
Payment Cards
In the following activities, you maintain the settings for processing payments with payment cards.
Requirements
You make general settings for payment cards in the R/3 Customizing Implementation Guide under Cross-
Application Components -> Central Business Partner -> Business Partner -> Basic Settings -> Payment Cards.
Payment Cards
Define Accounts for Payment Card Institute
 In this activity you define the following for each payment card company:
 A reporting account, to which you make transfer postings of receivables (that are to go to a payment
card company) when you execute a settlement run.
 A clearing account, to which the receivables for the company are posted.
Requirements
The G/L accounts have been created.
Activities
Define the required accounts for each payment card company
PATH:
Transactions/Payments/Incoming/Outgoing Payment Creation/Payment Cards/Define Accounts for
Payment Card Institute
Payment Cards
Define Specifications for Posting Settlement Document
 In this activity, you define specifications for posting an invoicing document
Activities
Define the necessary values

165
PATH:
Transactions/Payments/Incoming/Outgoing Payment Creation/Payment Cards/Define Specifications
for Posting Settlement Document
Extended Grouping
Using the settings in the following activities, you can adjust the standard grouping of line items carried
out by the payment program to comply with characteristics that you select (for example, by company code for
the automatic payment transactions, paying account partner, currency). The aim of this grouping is to group
the items in units that can be paid by a separate posting document.
The grouping that is controllable via Customizing is always carried out in addition to the standard grouping
carried out in the payment run, and is therefore called extended grouping.
Using the settings maintained here, you can also exclude line items from payment via the payment program.
Maintenance of the following Customizing settings is optional and only required if you require a finer grouping
of items than is carried out as standard in the payment program.
In order for the Customizing settings to be effective, you have to assign function module
FKK_GROUPING_PROPOSAL_GEN_0600 to event 0600 that is executed in the payment program - provided
it has not already been defined as industry module (see Program Enhancements -> Define Customer-Specific
Function Modules). In the industry component Insurance, this module is already integrated in the industry-
specific module for event 0600.
This module evaluates the Customizing settings and triggers the extended grouping or the exclusion of items
in the payment program. You maintain the settings for the extended grouping in the payment program similar
to the settings for item grouping as part of the clearing control, but separate Customizing tables are used.
Extended Grouping
Grouping Variants
Under a grouping variant, you summarize one or more grouping steps that control the extended
grouping in the payment program.
Define Grouping Characteristics

 In this activity, you define the characteristics that you want to use to group the items to be paid in the
payment program - in addition to standard grouping - or that you want to use to exclude items from payment.
Open items that have the same value for grouping characteristic in a grouping step are considered as one unit
in this grouping step. Depending on the derivation rule, the items of such a group are either paid together or
excluded from payment together. The exclusion of items can refer to one individual grouping step or to all
following grouping steps.

166
You can define grouping characteristics as follows:
1. Characteristic is an open item attribute. If the new characteristic is an attribute in the open item (structure
FKKOP), add the characteristic and enter the corresponding field name from structure FKKOP in the
characteristic definition. The field Active Module remains empty.
2. Characteristic is derived. If the new characteristic is not an attribute in the open item, but can be derived
from the existing information as part of the payment program, add the characteristic. Choose a name within the
customer naming convention (X*, Y*, and Z*) for the field name. The function module that you entered in the
field Active Module is used to derive the characteristic. The interface of this module must correspond to the
interface for sample function module FKK_SAMPLE_TFK126.
PATH:
Transactions/Payments/Incoming/Outgoing Payment Creation/Extended Grouping/Grouping
Variants/Define Grouping Characteristics
Define Grouping Variants
 You can define one or more grouping steps for a grouping variant. For items that you want to exclude from
payment, assign an item indicator that is defined in table TFKPK. You can define new item indicators under
Maintain Item Indicators for the Payment Program.

167
PATH:
Variants/Define Grouping Variants
Assign Item Indicator to Payment Lock Reasons
 If you have defined rules within the grouping variant, and these rules lead to items being excluded from
payment in the payment program, define the payment blocking reasons used together with the item indicator in
the grouping steps in this activity.
If no payment blocking reason is defined for an item indicator that you use, '*' is taken as the standard value.
The item indicator and payment blocking reason are displayed in the exception list for the payment program.
PATH:
Variants/Assign Item Indicator to Payment Lock Reasons
**Blank in system
Extended Grouping
Define Defaults for the Payment Run BP 04-1 Process ACH
 In this activity, you define which grouping variant is to be used for extended grouping in the payment
program. For the determination of the grouping variant, the system supports both determination dependent on
and independent of clearing type. If you do not specify a grouping variant for the clearing type of the contract
account to be paid, the general (default) grouping variant is used.

168
In this activity, assign the required grouping variant either dependent on or independent of clearing type to
clearing type '06' - payment run. You can define clearing types under the following path: Basic Functions ->
Open Item Management -> Clearing Control -> Define Clearing Types.
Requirements
In the activity Define Clearing Types, you have assigned clearing type '06' - payment run, and set the attribute
Usage to value '4' - payment run for this clearing.
PATH:
Transactions/Payments/Incoming/Outgoing Payment Creation/Extended Grouping/Define Defaults
for the Payment Run
Highlight ‘General Grouping Variant’ and Click on the ‘Alternative Grouping Variants

169
Add-In: Preselection of Forced Prenotifications
 This Business Add-In is used in the Contract Accounts Receivable and Payable (FI-CA) component. It
enables you to define your own rules for preselecting pre-notification records to be included in a pre-
notification file. This Add-in is called when you run the Display Pre-notification Data program in update mode,
which enables you to change the processing status of pre-notification records (transaction FPPNU).
Standard settings
In the standard system, the Business Add-In is activated.
Activities
To implement the Add-In, follow the instructions.
PATH:
Transactions/Payments/Incoming/Outgoing Payment Creation/Extended Grouping/Define Defaults
for the Payment Run
Payments
Archiving
In the following activity you can define the specifications for archiving payment lots.
Define Payment Lot Period
 In this activity you specify the minimum number of days a payment lot must reside in the system before it
can be archived.

170
PATH:
Transactions/Payments/Archiving/Define Payment Lot Period
Activate Archive Info Structure for Payment Lot Archive
 In this activity, you activate the archive information structure for the payment lot archive.
Requirement
You must activate this structure if you wish to access or display the archive.
Activities
Choose active
PATH:
Transactions/Payments/Archiving Activate Archive Info Structure for Payment Lot Archive

171
Automatic Clearing
Using the settings in the following activities, you can group the open items selected in the transaction
Automatic Clearing (FPMA) for a business partner/contract account according to characteristics that you define
(for example, company code, contract reference). The grouping that you control here corresponds to the
extended grouping function of the payment run. The aim of this grouping is to group open items for logical
units for each of which separate clearing is to be carried out. A clearing document is posted for each unit if
clearing takes place. The clearing consideration itself takes place via the clearing algorithm defined in clearing
control for the automatic clearing run.
The grouping that you define in the following activities is therefore an extension of the clearing control
functions. In contrast to the clearing control, maintaining this grouping is optional and only makes sense if you
are faced with the commercial requirement of posting clearing for specific item groups of a business
partner/contract account in a separate clearing document.
Example 1
Receivables and credit items for a contract account should only be cleared against one another if they both
belong to the same company code. In addition, you want to post a separate clearing document for each
company code.
Solution
Here, the grouping by company code is sufficient. Note that if the additional request for the separate clearing
document did not exist, the solution could be reflected in the clearing control.
Example 2
In addition to example 1, the payments on account assigned to a specific company code (for example, local
company code) should be cleared with receivables from other company codes.
Solution
This additional requirement can only be partially met by the methods of the grouping to be defined here.
According to this configuration, an item is assigned to a group uniquely and cannot be cleared cross-group.
Therefore, the payment on account can only be assigned to one of the groups, and therefore only cleared with
the receivables of one dependent company code.
Grouping Variants
You use a grouping variant to summarize one or more grouping activities that control the grouping in
the clearing run. You maintain the settings for this grouping similar to the settings for grouping items as part of
the clearing control. However, here you use separate Customizing tables.
Define Grouping Characteristics
 In this activity, you define the characteristics that you use to group the items to be paid in the clearing run,
or that you use to exclude the items from payment.
Open items that have the same values for grouping characteristics in a grouping activity are seen as one unit
in this grouping activity. The items in such a group are paid together or excluded from payment together
depending on the derivation rule used. The exclusion of items can refer to a single grouping activity or all
subsequent grouping activities.
You can define grouping characteristics as follows:

1. Characteristic is an attribute of the open item
If the new characteristic is an attribute in the open item (structure FKKOP), add the characteristic and
enter the corresponding field name from structure FKKOP to the characteristic definition. The field
Active Module remains empty.
2. Characteristic is derived

172
If the new characteristic is not an attribute in the open item but can be derived from the existing
information as part of the clearing run, add the characteristic. Choose a name within the customer
naming conventions (X*, Y*, and Z*) as the field name. The characteristic is thereby derived using the
function module that you entered in the field Active Module. The interface for this module must
correspond to interface of the function module FKK_SAMPLE_TFK126.
PATH:
Transactions/Automatic Clearing/Grouping Variants/Define Grouping Characteristics
Define Grouping Variants

 you can define one or more grouping steps for a grouping variant. You then maintain the settings for this
grouping in the same way as you maintain the settings for the grouping of items in the clearing control. For
items that you want to exclude from payment, assign an item indicator that is defined in table TFKPK. You
define new item indicators under Maintain Item Indicators for the Payment Program.
PATH:
Transactions/Automatic Clearing/Grouping Variants/Define Grouping Variants
Highlight Grouping Variant and Click on Grouping Activity

173
Define Specifications for Automatic Clearing
 In this activity you define which grouping variant is to be used for grouping for the automatic clearing run.
For the grouping variant determination, clearing category-specific and clearing category-independent
determination are both supported. If you do not specify a grouping variant for the clearing category of the
contract account to be paid, the system uses the general (default) grouping variant.
In this activity, assign the required grouping variant either specific to or independent of the clearing category to
Clearing Type '04' - Automatic Account Maintenance. You can define clearing categories under the following
path: Basic Functions -> Open Item Management -> Clearing Control -> Define Clearing Categories.
PATH:
Transactions/Automatic Clearing/Define Specifications for Automatic Clearing
Highlight General Grouping Variants and Click on Alternative Grouping Variants

174
175
Dunning Notices
In the following activities, you create definitions necessary for the dunning program.
Define Dunning Procedure Categories
 In this activity, you define dunning procedure types for dunning procedures. The defined dunning
procedure types are assigned to dunning procedures in the Configure dunning procedure activity.
Example
Insurance Company
Activities
1. Define a new dunning procedure types if necessary, copy event 300 and modify it accordingly (depending
on the new type).
PATH:
Transactions/Dunning Notices/Define Dunning Procedure Categories
Define Dunning Level Categories
 In this activity you define level types for dunning levels. These dunning level types are assigned to dunning
levels in the activity Configure dunning procedure.
Example
Insurance Company
Activities
1. Check, and if necessary change the dunning level types defined in the
2. Standard system
3. Define new dunning level types as appropriate.

176
PATH:
Transactions/Dunning Notices/Define Dunning Level Categories
+
Define Charge Categories for Dunning
 In this activity you define the dunning charge categories. These charge categories are assigned to the
charge schedules in the Configure Charge Schedules for Dunning Procedure activity.
Note
The charge categories are used in various application components. It is possible to maintain existing charge
categories here.
Example
Insurance Companies
Activities
1. Check, and if necessary change the delivered charge categories.
2. Define possible new charge categories.
PATH:
Transactions/Dunning Notices/Define Charge Categories for Dunning

177
Define Document Types for Dunning Charge Categories
 In this activity you define a document type for each dunning charge category. The system then uses the
document categories defined here to create documents when you post dunning charges.
Requirements
 You have maintained the document types you require.
 The charge categories are maintained.
Activities
Assign a document type to each charge category.
PATH:
Transactions/Dunning Notices/Define Document Types for Dunning Charge Categories
Configure Charge Schedules for Dunning Procedure
 In this activity, you configure your charge schemas for dunning procedures.
These charge schemas are then assigned to the dunning levels in the activity Configure dunning procedure.
Note
The charge schemas are used in various application components. You may find, therefore, that charge
schemas have already been maintained.
Example
Insurance Company
Requirements
The necessary charge types are maintained.
Activities
1. Check the charge schemas in your standard system and change them where necessary.
2. To create a new charge schema, proceed as follows:
a) Define the charge schema.
b) Assign up to three charge types to the charge schema.
c) Create charge scales for each charge schema.

178
PATH:
Transactions/Dunning Notices/Configure Charge Schedules for Dunning Procedure
Define Specifications for Interest on Arrears
 In this activity you store the attributes for the document that represents interest on arrears.
PATH:
Transactions/Dunning Notices/Define Specifications for Interest on Arrears

179
Configure Dunning Activities
 In this activity, you define dunning activities for dunning open, overdue items.
You then assign the activities to the dunning levels in the activity Configure Dunning Procedure.
Requirements
 The function modules required exist in the system.
 You have maintained the required application forms.
Activities
1. Check the dunning activities delivered and change them if required.
2. Define any new dunning activities that you require. Use only activity types 01 and (only for industry
component Insurance) 02.
PATH:
Transactions/Dunning Notices/Configure Dunning Activities
Configure Dunning Procedure
 In this activity you configure dunning procedures for Contract Accounts Receivable and Payable.
Firstly you define dunning procedures, and then assign dunning levels to each individual dunning procedure.
The dunning levels basically determine the dunning interval, the charge schedule used for determining the
dunning charges, and how interest is calculated and posted. In addition, you must define currency-dependent
amount limits and dunning activities for every dunning level.
Example
Insurance companies
Requirements
You must have maintained the following: Interest keys, Dunning procedure types, Dunning level types,
Dunning charges schema, Dunning activities
Activities
1. Check the dunning procedures defined in the standard system, changing them where necessary.
2. To create a new dunning procedure, proceed as follows:
a) Define the dunning procedure.
b) Create the dunning levels for the dunning procedure.
c) Define currency-dependent amount limits for the dunning levels.
d) Define the required dunning activities for the dunning levels.
Note for insurance companies:

Dunning procedures are not assigned at the contract account level, but dunning variants. This also applies to
the partner-contract relationships level.

180
PATH:
Transactions/Dunning Notices/Configure Dunning Procedure
Define Dunning Variants

 In this activity, you define dunning variants. You assign a dunning grouping category to a dunning variant,
as well as the following indicators, if required:
 Only on dunning procedure per contract or account
 Only include oldest item in dunning notice
 Individual dunning notice on document or line item level
You make the assignment of the dunning procedure to the items due for dunning, on the basis of the dunning
variant, company code, product group and main and sub-transaction criteria, in the Determine Dunning
Procedure (FS-CD) activity.
Standard settings
The following grouping categories are delivered as standard for the Insurance industry solution:
01 Grouping for individual dunning
02 Grouping for collective dunning
03 Grouping for contract dunning
Grouping category One item? One dunning procedure=
Individual dunning 01 Yes No
Collective dunning 02 No Yes
Contract dunning 03 Yes Yes
Multi-collective dunning XX No No
Further notes
From Release 4.62, you can choose whether the dunning grouping categories are active for the dunning
variant or the product group. You make this decision in the Activation of Basic Functions activity.
We recommend that you set the dunning grouping category for the dunning variant, as the setting of the
dunning grouping category for the product group will not be developed further.
The setting of the German Civil Code dunning grouping category for the product group is not supported.
If no dunning variant is defined on contract account or contract level (or for the insurance object-partner
relationship), the program works with the standard dunning variant '*'.
PATH:

181
Transactions/Dunning Notices/Define Dunning Variants
Define Dunning Procedure (FS-CD)

 In this activity, you assign a dunning procedure to the combination of dunning variant, product group and
main and sub-transaction. This means that the relevant dunning procedure can be determined by the system
when you execute the dunning proposal run.
Requirements
You have maintained the following settings in the Implementation Guide:
 Product groups
 Dunning variants
 Main and sub-transactions
Activities
Check the delivered assignments and change them if necessary.
PATH:
Transactions/Dunning Notices/Define Dunning Variants (FS-CD)
Define Dunning Grouping Categories

182
 In this activity, you define dunning groupings for Contract Accounts Receivable and Payable.
You can then assign these groupings to contract accounts.
Standard settings
For Insurance companies
Activities
1. Review the dunning grouping criteria in the standard system and change it if necessary.
2. To create a new dunning grouping key, proceed as follows:
a) Define the dunning grouping criteria.
b) Define the grouping fields for the dunning grouping criteria.
PATH:
Transactions/Dunning Notices/Define Dunning Grouping Categories
Define Dunning Lock Reasons

 In this activity you define dunning lock reasons. You can then assign these reasons to contract accounts or
individual line items.
Activities
1. Review the dunning lock reasons in the standard system, changing them if necessary.
2. Define new dunning lock reasons as appropriate.
PATH:
Transactions/Dunning Notices/Define Dunning Lock Reasons

183
Interaction with Other Business Transactions
In the following activities you can define the settings that are relevant for the interaction between
dunning and other business transactions.
Specifications for Automatically Deactivating Installment Plans
 In this step you maintain the installment plan deactivation reason used by the system during automatic
deactivation of installment plans from the dunning run.
Recommendation
You maintain this reason for deactivation so that the installment plan always contains information as to
whether an installment plan was deactivated manually (using the change installment plan transaction (FPR2))
or by the dunning run.
PATH:
Transactions/Dunning Notices/Interaction with Other Business Transactions/Specifications for
Automatically Deactivating Installment Plans
Define Runtimes for Dunning Archiving

 In this activity, you define the minimum number of days a dunning notice must exist in the system before it
can be archived.
Activities
Specify the number of days that must have elapsed before dunning notices can be archived.
PATH:
Transactions/Dunning Notices/Archiving/Define Runtimes for Dunning Archiving

184
Inbound Correspondence Dunning
In the following activities you make definitions that are required for the correspondence dunning
program.
Define Dunning Activities for Correspondence Dunning

 In this activity, you define the dunning activities for correspondence dunning. You assign the dunning
activities that you define to the dunning levels in the activity Configure Correspondence Dunning Procedure.
Requirements
 The required function modules exist in the system and have the same interface as the function module
FKK_SAMPLE_0746_DUNNING_CCC.
 You have maintained the required application forms.
Activities
Check the dunning activities delivered and change them if necessary. You may have to define new dunning
activities. To do this, use only activity type 03.
PATH:
Transactions/Inbound Correspondence Dunning/Define Dunning Activities for Correspondence
Dunning
Configure Correspondence Dunning Procedure

 In this activity you configure the dunning procedures for FI-CA correspondence.
The dunning procedures defined can be assigned to contract accounts and are valid across all clients.
Requirements
 The dunning charges schedules are maintained
 The dunning activities are maintained
Activities
1. Check the delivered dunning procedures and change where appropriate.
2. To create a new dunning procedure, proceed as follows: Define the dunning procedure, Create the
dunning levels for the dunning procedure, Define the desired dunning activities for the dunning levels
Further notes
Note to insurance companies:
Correspondence dunning procedures can also be assigned to the partner-contract relationship.
PATH:
185
Transactions/Inbound Correspondence Dunning/Configure Correspondence Dunning Procedures
Define Correspondence Dunning Lock Reasons
 Here you can define the reasons for the correspondence dunning lock.
PATH:
Transactions/Inbound Correspondence Dunning/Configure Correspondence Dunning Procedures
Blank in system
Additional Receivables
In the following activities you can define external transactions that you can flag as additional
receivables. Such an indicator can be useful for interest and charges items. NOTE: The following applies for
balance interest calculation in the industry component Insurance.
The system takes account of whether an item is included in the balance for the interest calculation. An interest
key for the additional receivables rule is however not taken into account.
Postprocess Sub- Transactions
 At this point you can process sub-transactions defined above further. It is possible for you to indicate
transactions as additional receivables. In order to do this, enter one of the rules previously defined for
additional receivables for the affected sub-transaction.
Example
- You do not want to calculate interest on interest and charges and want to confirm this for the transaction.
- On the basis of the transaction, you would like to determine whether an item should be taken into account in
a dunning group when calculating the amount of the dunning balance.
Requirements

186
You have defined at least one rule for additional receivables.
Further notes
An interest calculation lock for interest and charges items in other R/3 implementation projects is realized in a
different way, i.e. not via rules for additional receivables.
PATH:
Transactions/Additional Receivables/Configure Correspondence Dunning Procedures

187
Returns
In the next activities, you will create definitions required for processing returns.
Configure Returns Reasons

 In this activity you configure company-specific return reasons for contracts accounts receivable and
payable. You can assign the company-specific return reasons to the bank-specific return reasons in the
activity Assign return reasons to house banks. Return reasons for contracts accounts receivable and payable
apply to all clients.
Requirements
 The required tolerance groups are maintained.
 The required payment methods are maintained.
 The required payment block reasons are maintained.
 The required dunning block reasons are maintained.
Standard settings - internal note
Activities
1. Check and, if required, change the standard return reasons.
2. To create a new return reason, proceed as follows: Define the return reason, Maintain the settings for the
return activities, Define currency-dependent lot charges, Define the maximum permitted difference amounts for
each currency.

188
PATH:
Transactions/Returns/Configure Returns Reasons

189
Assign Return Reasons to House Banks
 In this activity you define a company-specific return reason for each house bank return reason for your
house banks.
Requirements
 The company-specific return reasons are maintained.
 The necessary settings for the house banks are maintained (see IMG structure Financial Accounting -
> General Ledger Accounting -> Bank-Related Accounting -> Bank Accounts).
Activities
Define the bank-specific return reasons for each house bank and assign the company-specific return reasons.
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Business Transactions/
Returns/Assign Return Reasons to House Banks
Define Bank Clearing Account for Returns

 In this activity, you specify bank clearing accounts for returns. To activate the account for returns lots, select
the field for valid returns. If you select the field for valid payment lots, the account will also be used for payment
lots.
Depending on the type of lot, the bank clearing accounts are used as follows:
 When you create or change a returns lot, the system checks the clearing accounts you entered. Only
those accounts defined in Customizing are permitted.
Requirements
 Bank master data has been transferred to the SAP system (see Customizing for Financial Accounting
under Bank Accounting -> Bank Directory Data Transfer).

190
You can maintain this master data manually. To do so, from the R/3 System initial screen, choose
Accounting -> Financial accounting -> Accounts receivable followed by Master records -> Bank.
 The house banks are defined in the SAP System (see Customizing for Financial Accounting under
Bank Accounting -> Bank Accounts -> Define House Banks.
Activities
Define the clearing accounts and bank data you require.
PATH:
Returns/Define Bank Clearing Account for Returns

191
Define Clarification Accounts for Returns
 In this activity, define a clarification account for each house bank and returns reason.
PATH:
Returns/Define Clarification Accounts for Returns
*** DO NOT HAVE ACCESS
Define Charges Accounts for Returns

 In this activity you define G/L accounts for return charges for the return types as well as for clearing the
return amounts (bank clearing accounts). The G/L accounts defined are determined automatically when
posting a returns lot and are posted to with the return charges/return amounts.
Note
The bank clearing accounts can be overridden manually when editing a returns lot.
Requirements
The G/L accounts required are created (see IMG structure Financial Accounting -> General Ledger Accounting
-> G/L Accounts).
Activities
Define the corresponding G/L accounts for each return type.

192
PATH:
Returns/Define Charges Accounts for Returns
Define Account Assignments for New Items with Returns

 When posting returns, a mode can be agreed that leads to the creation of new open items. You can define
the main and sub-transactions for items here.
PATH:
Returns/Define Account Assignments for New Items with Returns

193
Determine Document Type and Clearing Reason for Returns
 In this IMG activity, you store a document type and a clearing reason as default values for processing a
returns lot. The specifications are used for reversing payment clearing with a return, to post the clearing
document if required.
Requirements
The document type is defined.
Activities
Store the default values
PATH:
Returns/Determine Document Type and Clearing Reason for Returns
Define Field Selection

 In this activity you define the field selection for the returns header data processing screen. You can display
or hide fields on a screen, or define whether a field appears as a required entry field, an input/output field, or
only as an output field.
SAP provides a standard variant (SAP01) that is not modifiable; however, you can transfer the properties of
this variant when you create a new variant, and you can then process your new variant according to your
requirements.
You can specify a new screen number, where the screen must be in the same function group/program as the
original screen. To control the fields, you can use the behavior and display attributes.
The behavior attribute defines whether fields

 Have to appear
 May appear
 Are modifiable
 Are only intended for output
The display attribute defines whether fields
 Are switched to input/output
 Are only switched to output
 Are invisible
 Are required entry fields
Example
If a field has the behavior attribute Output Only, only the display attributes Invisible or Output Field are
available.

194
Activities
You can add new fields as follows:
1. Insert an empty line and fill it accordingly. To do this, choose Insert Line.
2. You can insert a line from a table in the Data Dictionary. To do this, choose Insert Table Line. In the
subsequent dialog box, enter the name of the table to be read; the definition of this table then appears. Select
the field required.
If you selected a line before choosing the function, this is overwritten with the definition selected; otherwise
your selection is added at the end.
3. You can import a complete table definition and then delete the lines you do not require. To do this choose
Read Table and enter the name of the table in the subsequent dialog box.
If you have made all definitions as required, you can define the variant as a standard variant. If you have set
up several variants, the users can select different views of the data depending on the situation.
Further notes
Note that you cannot define the following fields as pure output fields:
 DFKKRK-BLDAT Document Date in Document
 DFKKRK-BUDAT Posting Date in Document
 DFKKRK-VALUT Value Date
 DFKKRK-SELT1 Default Value for Selection Category
 DFKKRK-XSTEB Bank Charges Contain Tax
 DFKKRK-XRLSB Returns Amounts Contain Bank Charges
 DFKKRK-XCALCGEB Calculate Charges Automatically
 DFKKRK-ACCEPTCHARGES RL: Accept Charges Above Tolerance Limit
PATH:
Returns/Define Field Selection
Define Field Selection for Returns

 In this activity you define which fields are to be displayed in the listing of returns.
Activities
Copy the SAP standard variant and then modify the attributes of the individual fields to meet your
requirements.

195
PATH:
Returns/Define Field Selection for Returns
Define Transactions for Electronic Account Statement Transfer

 In this step you enter the external transaction codes that you want to transfer to FI-CA and which are found
on the account statement, and you classify them as payments or returned items.
Activities
Enter the transaction codes.
PATH:
Returns/Define Transactions for Electronic Account Statement Transfer
Returns
Archiving
In the following activities you can define the archiving of returns.
Define Returns History Runtime

 In this activity, you define how many days a return must be in the system before it can be archived.

196
PATH:
Returns/Archiving/Define Returns History Runtime
Define Returns Lot Runtime

 In this activity, you determine the minimum number of days a returns lot must reside in the system before it
can be archived.
PATH:
Returns/Archiving/Define Returns Lot Runtime
Activate Info Structure for Returns Lot Archive

 In this activity, you activate the archive information structure for the returns lot archive.
Requirements
To be able to access or archive the archive, you must have activated the archive information structure.
Activities
Choose Activate.
PATH:
Returns/Archiving/Activate Info Structure for Returns Lot Archive

197
Deferral and Installment Plans
In the following activities, you make settings for the installment plan.
Define Default Values for Installment Plan

 In this IMG activity, you store default values for entering and changing installment plans.
You can maintain the following settings:

 Default document type value displayed when entering installment plans.
 Default deactivation reason automatically displayed when deactivating an installment plan.
 Print type for the payment form printout.
Requirements
 The installment plan indicator is set in the central settings for posting. Repetitions are allowed for
statistical items (Rep. status field).
Recommendation
It is recommended that you use your own document type and number range for installment plans. This enables
you to always identify the plans by the document number.
Activities
Define the desired default value for document type, deactivation reason, and the payment type for payment
forms.

198
PATH:
Deferral and Installment Plans/Define Default Values for Installment Plan
Categories for Installment Plan

 In this IMG activity, you enter the categories for the installment plan. You can use the installment plan
category to split the plans up into different groups, to grade the issue of installment plans. Depending on the
installment plans previously issued, when you create a new one, you can decide whether another installment
plan should be issued for a particular open item. When you create a new installment plan, all open items
already in an installment plan are displayed with an icon. By double-clicking on this icon, you go to a list of all
installment plans that have already contained this receivable. You can use this list to decide whether to issue
another plan or not.
Example
If an installment plan with category '01' was already issued for a receivable, then you should not create any
more installment plans with this category for this receivable. Instead, you can create one with category '02'.
.
PATH:
Deferral and Installment Plans/Categories for Installment Plan
Blank in the system

199
Define Installment Plan Category
 In this activity you define default values for an installment plan type that you can then call up when entering
an installment plan.
Example
You can, for example, define an installment plan type with a fixed installment amount of 200 EUR a month, 50
EUR fees and a rounding amount of 5 EUR.
Activities
Define default values for an installment plan type.
PATH:
Deferral and Installment Plans/Define Installment Plan Category
Define Default Values for Installment Plan Charge

 In this step you define a document type to be used when posting installment plan fees.
Requirements
The document type has been created.
Activities
If you charge installment plan fees, determine the document type for posting the fee document here.
PATH:
Deferral and Installment Plans/Define Default Values for Installment Plan Charge
Define Default Values for Interest on Installment Plans

 In this step you define a document type and an interest key for the interest calculation on installment plans.
You are provided with these default values when calculating the interest on an installment plan. When

200
calculating the interest, the interest is calculated from the starting date to the due date of the individual
installment payment.
Requirements
The document type and interest key must be defined.
Activities
PATH:
Deferral and Installment Plans/Define Default Values for Interest on Installment Plans
Deactivation Reasons for Installment Plan

 In this activity, you maintain deactivation reasons for installment plans. By deactivating an installment plan
you cancel it. The deactivation reason and date are stored in the installment header. You can view these at
any time.
Example
You can use deactivation reasons to store the following information in the installment plan:
1. The installment plan was cancelled manually by an administrator
2. The installment plan deactivated as part of the dunning run.
Recommendation
Maintain at least one deactivation reason for manual deactivation and one additional deactivation reason for
deactivation of the dunning run.
PATH:
Deferral and Installment Plans/Deactivation Reasons for Installment Plan
Write-Offs

201
In the following activities you define the data required for charging off receivables or credit. You
charge off receivables if: It is certain that they will never be paid; The costs involved in collection are higher
than the amount to be collected.
You can charge off credit if disbursement to the customer is no longer possible.
Define Write-Off Reasons
** No Details available
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Business Transactions/ Write-
Offs/Define Write-Off Reasons

202
Define Specifications and Default Values for Write-Off
 In this activity you define the fixed values document type and clearing reason and the default values check
level and charge-off currency that are used when posting a charge-off document (Menu)
Requirement
You have defined the document type required, the clearing reason, check level, and the charge-off currency.
Recommendation
The fixed Value for the charge-off reason is ‘04’ = Charge-off.
Activities
Enter the fixed values and default values.
PATH:
Offs/Define Specifications and Default Values for Write-Off

203
Define Specs and Default Values for Mass Write-Offs
 In this activity, you define the fixed values check level and clearing reason and the default values document
type and charge-off currency, that are used when posting a charge-off document in a mass run.
Requirements
The document type, clearing reason, check level, and charge-off currency are defined.
Recommendation
The fixed value for the clearing reason is "14" = mass charge-off.
Activities
Enter the fixed values and default values.
PATH:
Offs/Define Specs and Default Values for Mass Write-Offs

204
Automatic G/L Account Determination for Write-Offs
 In this activity you define the expense and revenue accounts for write-offs. You can differentiate these with
the following key fields:
 Company code
 General ledger account
 Write-off reason
 Main transaction
 Sub-transaction
 Division
 Account determination characteristic
With the exception of the write-off reason, all key fields are checked for the corresponding entries in the
business partner item that is to be written off.
The first G/L account (expense account) is for debit items to be written off, the second G/L account (revenue
account) is for credit items to be written off.
Recommendation
Activities
Define the required G/L accounts.
Further notes
The G/L account can be overridden at event 5030 (see IMG structure Contract Accounts Receivable &
Payable -> Program Enhancements -> Define Customer-Specific Function Modules).
PATH:
Offs/Automatic G/L Account Determination for Write-Offs

205
Automatic G/L Account Determination for Writing Off Value Adjustments
 This activity is only relevant for the Czech Republic and Slovakia. In this activity you maintain account
determination for account-based value adjustments.
In the Czech Republic and Slovakia there is a difference between:

 Statutory value adjustments and
 Account-based value adjustments
Statutory value adjustments can influence the posting to expense account with write-offs, whereas account-
based value adjustments do not have any effect when writing off an item. Statutory value adjustments are
therefore tax-relevant and must be posted to separate accounts.
Further notes
You maintain the settings for statutory value adjustments in posting area 0120 ( Automatic G/L Account
Determination for Write-Offs).
PATH:
Offs/Automatic G/L Account Determination for Writing Off Value Adjustments

206
Maintain Alternative Expense and Contract Account
 In this activity you define alternative revenue and expense accounts to those defined in posting area 0120 in
the activity Write-Off: Automatic G/L Account Determination. You can differentiate these with the following key
fields:
 Company Code
 G/L Account
You should note that the relevant alternative expense and revenue account only allow postings with CO
account assignments. When you create the write-off document, you can enhance the CO account assignment
data for event 5030. In the case of inheritance, you may find that due to account assignments in the document
to be written off, no CO account assignment data can be inherited. However, if a CO account assignment is a
definite prerequisite for the expense and revenue account from posting area 0120, then the alternative account
from the setting made here for posting area 0123 is used. This function is not supported for every industry-
specific component. Check whether:
 SAP delivers an industry-specific function module for the industry-specific component for event 5030
that you use
 The function module FKK_INHERIT_CO_ACC_ASSIGNMENTS is called up for the industry-specific
characteristic of the event when inheriting the CO account assignment
Recommendation
Activities
Enter the required G/L accounts.
Further notes
You can override the G/L account for event 5030. To do this, define a corresponding function module under
Program Enhancements -> Define Customer-Specific Function Modules.
PATH:
Offs/Maintain Alternative Expense and Contract Account

207
** Not authorized for transaction
Reversal
In the following activities, you create definitions that are necessary for reversing documents.
Define Alternative Accounts for Reversal in Following Year
 In this activity, you can define accounts to be posted to for reversal in another fiscal year.
Requirements
The necessary G/L accounts have been created (see IMG structure Financial Accounting -> General Ledger
Accounting -> G/L Accts).
Activities
Define a G/L account if you want to replace the G/L account posted to originally for a reversal document in the
following year with a different account. Enter the number of the G/L account and the number of the alternative
account.
PATH:
Transactions/Reversal/Define Alternative Accounts for Reversal in Following Year
Define Default Values for Reversal
 In this activity, you define a document type and a clearing reason. The system then defaults your entries in
the selection screen for the reversal transaction.
Requirements
You have created the document type
Activities
Define your default values
PATH:
Transactions/Reversal/Define Default Values for Reversal

208
Define Specifications for Clearing Item
 In this activity, you define main and sub-transactions for creating open items when resetting clearing,
reversal and posting of returns. The open item replaces the clearing item in the clearing item. The main and
sub-transaction are determined using the clearing reason from the line item already cleared.
Activities
Define main and sub-transactions
PATH:
Transactions/Reversal/Define Specifications for Clearing Item
Doubtful Items and Individual Value Adjustment
In the following activities you maintain the settings for doubtful entries and individual value
adjustments. For doubtful entries you take the fact into account, for accounting purposes, that the customer

209
may not settle his receivables. You must, for accounting purposes, separate the doubtful receivables from
those beyond doubt. For individual value adjustments you can post the probable cancellation of the receivable
to a separate expense account.
Maintain Account Determination for Doubtful Item Entries

 In this activity you can define the accounts for doubtful entries. You can maintain an account for doubtful
entries for each combination of company code and receivables account. You should also set up an adjustment
account that can be used as an offsetting account for doubtful entries.
Example
You have maintained receivables account 140000. For this account you have maintained account 140003 as
the account for doubtful entries and account 140001 as the adjustment account. Post the transfer posting for
doubtful entries as follows: Doubtful receivables (140003) to adjustment account (140001).
PATH:
Transactions/Doubtful Items and Individual Value Adjustment/Maintain Account Determination for
Doubtful Item Entries
Maintain Account Determination for Ind. Value Adjustment

 In this activity you can define the accounts to which the individual charge-offs are to be posted. Maintain an
account for charge-off expenses and an adjustment account for each combination of company code and
receivables account. You can also create a revenue account that is posted to when a charge-off is reset. A
charge-off can be reset when:
 A payment receipt is made to an item that has already been charged off
 A manual reset is made in the edit transaction for charge-offs ( FPZW)
If you do not create a revenue account, the reset is posted to the expense account.
In posting area 0140, you can maintain an aperiodic revenue account for a reset. This account is posted to if
the cause of the reset is in the year following the year in which the charge-off has been made.
Recommendation
For each receivables account to which items that can be charged off are posted, maintain an account for
charge-offs and an adjustment account.

210
PATH:
Transactions/Doubtful Items and Individual Value Adjustment/ Maintain Account Determination for
Ind. Value Adjustment
Maintain Default Values for Transfer Posting Run

 In this activity you can define the document type for the documents generated by the transfer run for
doubtful entries and individual value adjustments.
Recommendation
Use a separate document type for the correction of receivables
PATH:
Transactions/Doubtful Items and Individual Value Adjustment/ Maintain Default Values for Transfer
Posting Run
Credit
In the following activity, you make credit settings
Define Selection Criteria for Credit Clarification
 In this activity you can define the parameters used to select credits for processing in the clarification
worklist.
Activities
Define the following: Company code, Document type, Main Transaction, Sub-transaction, Currency, Amount
‘from’ which or ‘to’ which is to be selected. If you enter the amount 0.00 for both, the selection is only made
according to the other criteria.

211
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Business Transactions/Credit/
Define Selection Criteria for Credit Clarification
Define Document Types for Credit Clarification

 In this activity, you define the document types that you want to use for clarification of credit
PATH:
Define Document Types for Credit Clarification
Define Clearing Account for Transferring Credits

 In this activity, you define a clearing account and a company code for each country and company code for
the posting of payments of credits. This clearing account is used for credit clarification if you transfer a credit
to a customer and the credit does not originate from a payment received from this customer.
The clearing account for the repayment of a payment received is determined via posting area 0130. (See
Business Transactions -> Payments -> Processing Incoming/Outgoing Payments -> Define Specifications for
Repayment of Incoming Payments)
PATH:
Define Clearing Account for Transferring Credits
** Not authorized for transaction

212
Broker Collections
In the following activities, you create definitions necessary for using the functionality of broker
collections.
Broker Collections
Basic Settings
Activation of Basic Functions
 In this IMG activity, you activate the basic functions for broker collections. You use the dunning lock for
department contracts on broker contract flag to decide whether you exclude insurance objects, which are
assigned to the broker contract, from a dunning notice.
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Broker Collections/Basic
Settings/Activation of Basic Functions
** Blank in system
Broker Collections
Settings for Posting Broker Reports
Assign Categories for Broker Collections to Main and Subtransactions
 In this activity, you assign the categories relevant for broker collections to a constellation of sub-
transactions, main and sub-transactions, company code and product group. Items that are posted with main
and sub-transactions, which are not assigned to a category, are not included in broker collections and are not
selected for broker reports. Items of this type are paid by the original business partner, and not the broker.
Requirements
You have defined and parameterized main and sub-transactions. Choose SAP Insurance ->
Collections/Disbursements -> Basic Functions -> Postings and Documents -> Document -> Maintain
Document Assignments -> Maintain Transactions for SAP Insurance (FS-CD) -> Define and Parameterize
External Transactions. At this point, you can also maintain the main and sub-transactions that are relevant for
broker collections.
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Broker Collections/Settings
for Posting Broker Reports/Assign Categories for Broker Collections to Main and Subtransactions

213
Highlight ‘External Main Transactions’ and click on ‘External Subtransaction
Highlight ‘External Subtransaction’ and click on ‘Broker Parameters’
Product Group

214
Define Clearing Accounts
 In this activity you define a clearing account. This clearing account functions as an interim account when
posting a broke report. When posting a broker report, the following postings are executed during broker report
item posting:
 Broker report items from the premiums/claims category:

o Open items on customer accounts are cleared against the clearing account.
o Postings on accounts to customer accounts are posted against the clearing account.
 Broker report items from the commission/costs category:
o Open items on the commission account are cleared against the clearing account.
o Postings on accounts to the commission account are posted against the clearing account.
 The total for the items is then posted from the clearing account to the broker account.
Requirements
You have created a chart of accounts and a corresponding G/L account.
PATH:
for Posting Broker Reports/Define Clearing Accounts
Configure Clarification Code

 In this activity, you configure clarification codes. A clarification code controls posting and further processing
for an item entered in the broker report. You set the following parameters:
 Category
 Posting rule
 Transactions for newly created items
 Payment locks
The following flags give you further control options:

 Usable for missing master data
 No clarification processing
 OnAcct comm. posting to assigned broker
 No clarification processing
You then assign the clarification codes or activities for processing a broker report.
Requirements
You have configured activities for clarifying broker reports. For clarification codes that use posting rules for
clarification cases, a clarification case is created without you explicitly having to assign the Create clarification
case activity to the clarification code.

215
PATH:
for Posting Broker Reports/Configure Clarification Code
Highlight ‘Clarification code’ and click on ‘Activities’
Define Specs for Broker Reports

 In this activity, you define the specifications for each category, which are relevant to automatic selection
when entering a broker report. You can define specifications for every external insurance object category that
you have assigned to the broker contract insurance object category (20).
These include:
 Clarification code for overpayment, underpayment and equal amounts
 Posting parameters such as document type, clearing reason, main and sub-transaction
 A grouping for broker report items
 A line layout variant
Activities
1. Select the category by clicking once on the field to the left. The line is then marked in color.
2. Click on the Detail icon. This takes you to the detail screen, where you can enter or change the
specifications mentioned above.
3. Enter the required values.
Further notes
These settings cause entries (proposals) when entering a broker report, which can be changed manually.

216
PATH:
for Posting Broker Reports/Define Specs for Broker Reports
Highlight and click on ‘Details’
Define Specs for Broker Summary Postings

 In this activity you can define, for each posting area, a document type for each item category. This
allocation is for posting premium and benefits totals to the premium/benefits clearing account
Activities
1. Using F4 input help, select the relevant posting area for which you wish to allocate document types to item
categories.
2. In the window on the right, enter the key of the document type you wish to allocate to the item category.
If you would like to find out more about existing document types using input help, place the cursor on a line
and click on the detail icon. You will be shown a detail screen with the document types from which you can
make a selection.
3. If you wish to make new allocations, click on the create icon.
a) Select the category you wish to reallocate from the window which appears.
b) You will see the detail screen for maintaining default values for broker totals postings where you
can select and allocate the document type.
4. You can delete the allocation using the delete icon.

217
PATH:
for Posting Broker Reports/Define Specs for Broker Summary Postings
Define Number Ranges for Autom. Creation of Broker Reports

 In this activity you can maintain, in interval 01, the number range which determines the key for a broker
report when it is generated automatically.
PATH:
for Posting Broker Reports/Define Number Ranges for Autom. Creation of Broker Reports
**Not authorized to use Transaction IBR10
Broker Collections
Preparation of Broker Report Editing Screens
Define Line Layout Variants for Item Entry

 In this activity, you define the line layout variants for item entry for a broker report.
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Broker
Collections/Preparation of Broker Report Editing Screens/Define Line Layout Variants for item
Entry
**Not authorized to use Transaction FQKPT
Define Line Layout Variants for Fast Entry

 In this activity you define line layout variants for broker report fast entry.
All fields from the SIBRQENTRY structure are available for this. You can include your own fields in the line
layout variants, as long as they are contained in the customer include.
Requirements
You must define at least one line layout variant.

218
PATH:
Collections/Preparation of Broker Report Editing Screens/Define Line Layout Variants for Fast
Entry
Highlight ‘Variants’ and click on ‘Variant Fields’
Include Own Fields in Detail Screen

 In addition to the fields delivered by SAP, you can include your own fields online for processing broker
reports.
Requirements
You require the authorization to create transport requests.
Activities
Fill the customer include CI_IBROSTMP in the IBROSTMP table.
Create a function group in the customer namespace with the following objects:

219
 Sub-screen with the new customer fields. The sub-screen is displayed on the detail screen as a tab
strip.
 Function modules for processing data on the sub-screen with the interfaces to the following sample
modules:
o ISCD_BROK_SAMPLE_INI_POS
Determines the text for the tab strip on which the customer fields appear.
o ISCD_BROK_SAMPLE_PBO_POS
For setting the screen attributes for the customer fields and for data transfer for the customer
fields from the main program to the sub-screen.
You can use the following service modules in this module:
ISCD_BROK_SUBSCREENS_MODIF (read screen attributes according to processing status)
ISCD_BROK_AKTYP_GET (read processing status)
o ISCD_BROK_SAMPLE_PAI_POS
For checking the customer fields on the sub-screen and for data transfer for the customer
fields from the sub-screen to the main program.
 Define your customer program, the number of the screen and the function modules for program
SAPLVKAG, application DBRP, number 1 and application area V.
PATH:
Collections/Preparation of Broker Report Editing Screens/Include Own Fields in Detail Screen
Broker Collections
Settings for Grouping Open Items in Broker Report Items
Define Selection Categories for Broker Reports

 In this activity, you define selection categories for broker reports, to extend the standard grouping for items
in the broker report according to your requirements.
Standard Settings
The standard grouping contains the following fields: Category, Partner, Insurance object, Assigned broker,
Assigned broker contract, Company code, Currency
PATH:
for Grouping Open Items in Broker Report Items/Define Selection Categories for Broker Reports

220
Define Grouping for Broker Report Items
 In this activity, you define groupings for broker report items. You can define a maximum of five selection
categories for each grouping. You can use all fields in the FKKOP (line items) structure. You group selection
categories for broker reports together with grouping keys. You can define grouping keys as default values for
broker report categories.
PATH:
for Grouping Open Items in Broker Report Items/Define Grouping for Broker Report Items
Highlight ‘Grouping Key’ and click on ‘Grouping Criteria’
Broker Collections
Settings for Broker Report Clarification
Configure Activities for Clarifying Broker Reports
 In this activity, you configure the activities that can be executed in addition to posting a broker report.
Example
If there are differences between the broker report proposal generated by the system and the item transmitted
by the broker in correspondence, you can execute the processing activity ‘Create clarification object’.
Activities
SAP delivers a function module that can be used to execute the processing activity ‘Create clarification object’.
If you require any other processing activities, create the corresponding function modules.

221
PATH:
for Broker Report Clarification/Configure Activities for Clarifying Broker Reports
Highlight and click on ‘Display’
Custom Function Module
Assign G/L Clarification Accounts to Categories

 If you have not defined a specific sub-ledger clarification account in the master data for the broker contract,
define a G/L clarification account for each category in this IMG activity. Postings are made to the G/L
clarification account if amounts have been posted to clarification when posting a broker report item, due to the
clarification key that has been used. The G/L clarification account for coinsurance is obsolete.

222
PATH:
for Broker Report Clarification/Assign G/L Clarification Accounts to Categories
Assign General Ledger Accounts to Clarification Codes

 In this activity, you assign clarification codes to G/L accounts, on which items to be clarified are posted.
These G/L accounts override the clarification accounts that you have defined for each category, or the sub-
ledger clarification account defined for the broker contract.
If you set the No Clarification Posting flag for the clarification code, the items are posted to the G/L account
without a clarification case being created for post-processing.
Requirements
The clarification codes must contain posting rules that enable clarification processing.
Activities
Define a G/L account or a short account assignment for a clarification code. You maintain short account
assignments in the Define Short Account Assignments for Transfer Postings activity.
PATH:
for Broker Report Clarification/Assign General Ledger Accounts to Clarification Codes

223
Specifications for Automatic Broker Report Postprocessing
 In this activity, you define specifications for the automatic post-processing of a broker report. You can find
more information about the prerequisites and functionalities for the Post-process broker report automatically
mass activity in the application help in the broker collections section.
PATH:
for Broker Report Clarification/Specifications for Automatic Broker Report Postprocessing
Broker Collections
Archiving
In the following activities, you create the necessary definitions for archiving broker reports.
Define Runtime for Broker Report

 In this activity, you define how many days a broker report has to be in the system before it can be archived.
PATH:
Collections/Archiving/Define Runtime for Broker Report

224
Activate Archive Info Structure for Broker Report Archive
 In this activity, you activate the archive info structure for broker reports.
Requirements
If you want to access or display the archive, the archive info structure must be activated.
Activities
Select Active
PATH:
Collections/Archiving/Activate Archive Info Structure for Broker Report Archive

225
226
Integration
In the following activities, you create definitions that are required to link contract accounting to other
R/3 application components. This ensures that the contract accounting (FI-CA) component and its application
areas can work with the other components of the R/3 system
General Ledger Accounting
In the following activities, you make settings necessary for integrating contract accounts receivable
with the R/3 General Ledger.
Define Posting Specifications for General Ledger Transfer
 In this activity, for each chart of accounts and company code, you define the posting key for debit and credit
postings and the document type for posting the G/L documents during the transfer of totals records to the
general ledger (FI-GL). You must be able to post to this document type in all companies.
In addition, you also define the transfer accounts for the general ledger transfer.
Requirements
 The required G/L accounts are created (see IMG structure Financial Accounting -> General Ledger
Accounting -> G/L Accounts).
 The required document types are maintained (see IMG structure Financial Accounting -> Finanical
Accounting Global Settings -> Document -> Document Header).
Activities
Define a transfer account and the corresponding attributes for each company code.
PATH:
Collections/Integration/General Ledger Accounting/Define Posting Specifications for General
Ledger Transfer

Define G/L Accounts for Open Item Reconciliation
 In this activity you define G/L accounts that can occur in a business partner item. These can include
receivables, down payments made and sales tax clearing accounts, for example.
Your definitions are used to carry out reconciliation of open business partner items with the balances of the
reconciliation accounts in the general ledger (see menu path in Contract Accounts Receivable & Payable

227
Periodic processing -> Update general ledger -> Reconcile open items (technical name of program
RFKKOP10)).
Activities
Define all the G/L accounts that can occur in a business partner item.
PATH:
Collections/Integration/General Ledger Accounting/Define G/L Accounts for Open Item
Reconciliation
Cash Management
Define Alternative Planning Levels for Transactions
 Here you can set a different planning level depending on the main and sub-processes.
The planning group is entered in the contract account or contract (insurance companies only) master record.
The planning level is defined from the planning group in accordance with Customizing under Treasury -> Cash
Management -> Master Data -> Subledger Accounts -> Define Planning Levels. With these entries you can
specify either the main transaction only or main transaction and sub-transaction. The more qualified entry is
taken when the different planning level is being selected.
Notes
This assignment used to be carried out in the Treasury menu under Cash Management -> Structuring ->
Maintain Blocked Levels. However, the entries there were only taken into consideration by Accounts
Receivable (FI-AR) and Accounts Payable (FI-AP) .
PATH:
Collections/Integration/Cash Management/Define Alternative Planning Levels for Transactions

228
Business Information Warehouse
In the following activity, you make the settings for the extraction of data from Contract Accounts
Receivable and Payable (FI-CA).
Business Information Warehouse

Define Sorted list for Items Due/Overdue
 In this activity, you define a due date list for open and cleared items. This list is to be used to summarize
the items for the extraction for the Business Information Warehouse (BW). In this way, in the BW you can, for
example, display all of the items due in the next 10, 20, and 30 days together.
PATH:
Collections/Integration/Business Information Warehouse/Define Sorted list for Items Due/Overdue

229
Closing Operations
In the following activity, you make the settings for the extraction of data from Contract Accounts
Receivable and Payable (FI-CA).
Reclassifications
Here you make the preparations for reclassifying receivables and payables, that is, for displaying and
transferring receivables and payables for customers with credit balances and vendors with debit balances.
In Contract Accounts Receivable and Payable (FI-CA), you can display the reclassifications as follows:
 For the balance of a receivables or payables account per business partner and company code
 For the balance of a group of receivables payables accounts, grouped by summarization account
A summarization account is assigned to each group of receivables or payables accounts.
 For the balance of a group of receivables or payables accounts, grouped by summarization company
code
A summarization company code is assigned to each group of receivables or payables accounts.
 For the balance of a group of receivables or payables accounts in a group of company codes
Summarization accounts are required for key date-related open items whose receivables and payables
accounts are displayed in one item in the financial statements (for example, same type of legal transaction for
several utility provider divisions in the case of different receivables accounts per division).
Summarization company codes are required for company codes that are in the legal entity that has to create
the financial statements (for example, consolidated financial statements).
An extended calculation of reclassifications by summarization accounts and summarization company codes
only takes place if you have made the relevant settings in one of the following Customizing activities:
The calculation takes place in three steps:
1. Determination of the summarization company code/summarization company code group
The system determines whether there is a summarization company code/summarization company
code group for a company code and currency type. If this is the case, the summarization company
code/summarization company code group replaces the original company code.
2. Determination of the summarization account/summarization account group
The system determines whether there is a summarization account/summarization account group for a
company code and account. If this is the case, the summarization account/summarization account
group replaces the original account.
3. Determination of the reclassification per business partner and summarization account
For financial statement preparation, you can use the transaction Open Items at Key Date (Parallel) (see SAP
menu: Periodic Processing -> Closing Preparations) to determine customers with credit balances and vendors
with debit balances and to sort receivables and payables according to the remaining term. If you display the
reclassifications using summarization accounts and summarization company codes, the program totals the
balances of all general ledger accounts that are assigned to the same summarization account or
summarization company code. The system then determines whether this total has to be reclassified. The
reclassifications are however exported and posted per individual account and company code. The
summarization company code and summarization account are displayed with the reclassifications. You can
then carry out the transfer postings in the general ledger as follows:
 You post the reclassifications issued by the report manually in the transaction Post Document (FPE1)
in the SAP menu under Document -> Post.
 You export the reclassifications issued by the report and post them automatically in the transaction
Post Reclassifications (FPRECL) (see documentation for the transaction Open Items at Key Date
(Parallel)).
Example
You determine the reclassifications per receivables account and business partner - without
summarizing at company code or account level:
Company code Receivables Account Amount
0001 140001 100
0001 140002 -120 -> Reclassification: -120
0002 140001 50

230
You summarize the reclassifications of accounts 140001 and 140002 separately in summarization
account 140003. This results in the following constellation:
0002 140003 50
You summarize the reclassifications of both receivables accounts separately in company code 0001.
This results in the following constellation:
0001 140001 150
You summarize the reclassifications of company codes 0001 and 0002 in company 0001 in
summarization account 140003. This results in the following constellation:
0001 140003 30 -> No reclassification
Define Adjustment Accounts

 In this activity you define the adjustment accounts for reclassifying receivables and payables.
PATH:
Collections/Integration/Closing Operations/Reclassifications/Define Adjustment Accounts

231
Data Transfer
In the following activities, you make the settings for transferring data from external systems into
Contract Accounts Receivable and Payable.
Generate Structures for Transferring Data

In the activities of the section Generate Structures for Transferring Data, you can edit the structures delivered
by SAP for the data transfer. By copying the SAP structures, you can generate your own transfer structures in
your customer name range and adjust them to meet your requirements. You can remove the fields you do not
require from your structure and determine the order of the fields.
You can also check whether your existing transfer structures have a different status to the structures delivered
by SAP. If the status of the structures has a green or yellow light, you can carry out the data transfer using the
corresponding structure. However, if the status has a red light, there are inconsistencies that you have to
correct before you transfer data.
Communication with External Billing Systems
In the activities in the section Communication with External Billing Systems, you make the settings that enable
you to convert invoices created externally into documents in Contract Accounts Receivable and Payable.
Generate Structures for Transferring Returns Lots
 In this activity you can:

 check whether you have structures for the transfer of returns lots
 compare your existing transfer structures with the respective release of transfer structures delivered by
SAP
 adjust your structures to match the SAP transfer structures where necessary
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Data Transfer/Generate
Structures for Transferring Returns Lots

232
Technical Settings
In the following activities, you make technical settings.
Prepare Processing of Clarification Worklist
 In this activity, you enter the settings for processing clarification work lists that may be created during a
payment run, with payment lots for instance:
 You can define areas of responsibility for processing clarification work lists. These areas of
responsibility determine which agent or which organizational unit can process particular clarification
work lists (see the Role with Responsibility field in the application object). When defining the areas of
responsibility, you can use all the fields in the clarification work list table. For example, you can
stipulate that items for clarification above a given amount can be processed by certain employees
only. To do so, select the entry application objects in the view cluster.
 You can change the selection of fields that appear on the selection screen for processing clarification
work lists. Possible fields are all those that appear in the clarification work list table. Select the entry
selection fields in the view cluster.
 You can define the attributes of the possible status (status information) for a clarification work list.
 These attributes are:
o The name and the icon in the list display
o A validity period and a subsequent status that is effective once the validity period has elapsed.
In the view cluster select the entry status information.
 You can define a new status, but if you choose to do so, you will need to write function modules that
set and evaluate this status for clarification items.
The status information and event (see next point) entries in the view cluster are relevant.
 You can influence the way clarification processing takes place by way of event function modules. The
events that can be used are described in the corresponding online help documentation. Each
application (for example, industry, partner, or you as a customer) that wants to call up its own event
function modules must be entered as an application in Customizing. The new function modules must
be assigned to the application.
The applications and event entries in the view cluster are relevant.
Requirements
To be able to determine areas of responsibility for processing clarification work lists, you must define an
organizational plan. To do this, choose Tools -> Business Workflow -> Organizational Plan from the SAP
menu. For more information see the Application Help. Note however that: The standard role that must be
defined must be of the category "Role with responsibility", In the container definition, you may use the
clarification work list table only.
If you are not already using the SAP workflow, you have to maintain the following settings in Customizing to be
able to use the organizational plan (see IMG structure: R/3 Customizing Implementation Guide -> Basis
Components -> Business Management -> SAP Business Workflow -> Basic Settings (Organizational
Management):
1. Set active plan version (technical key: SIMGSIMG_WF1400AP)
2. Maintain prefix numbers (technical key: SIMGSIMG_WF1500W4)
Standard settings
SAP delivers a model customizing that you can work with if you do not make any assignment of responsibilities
with the clarification work list.
For the industry component Contract Accounts Receivable and Payable: Public Services, SAP delivers two
roles with responsibilities - to restrict the selection of the clarification work list the standard role 02100008 and
to display acute clarification cases the standard role 02100009. When you activate the roles, you have to
define the responsibilities for the required role with no gaps. For each employee, the program shows only
those clarification cases for which they are responsible based on the role definition.

233
Activities
You only have to check two points for the clarification work list:
 The fields for selecting clarification items (see entry in view cluster selection fields)
 The attributes of the possible status, particularly the validity period (see entry in view cluster status
information)
You would only need to make further settings for the payment program if you want to include payment
exceptions in a clarification work list (see Business Transactions -> Payments -> Incoming/Outgoing Payment
Creation -> Select Item Indicator for the Clarification Worklist).
If you want to define responsibilities for clarification work list processing, the points listed under "Prerequisites"
must be met.
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Broker Collections/Technical
Settings/Prepare Processing of Clarification Worklist
Choose a cluster
Activate Performance Improvement for Mass Runs

 In this activity, you can activate a shadow table for business partner data (see field documentation BP
table). The shadow table contains an extract of the business partner data that is relevant for Contract Accounts
Receivable & Payable. If you manage a large number of business partners in the SAP system, using the
shadow table improves the performance during mass runs (for example payment program and dunning
program).
Activities
1. Check whether a shadow table is required, and if so, activate it.

234
2. If business partner data already exists in your SAP system, and you subsequently activate the shadow
table, you will need to run report RFKKGPSH. For further information see report documentation.
3. If you carried out central changes independently of business partner maintenance (changing postal codes
for example) you will need to update the extract table using report RFKKGPSH.
PATH:
Settings/Activate Performance Improvement for Mass Runs
Define Job Categories

 In this activity you can define and maintain job categories. These job categories are used by mass
activities, for example, to determine modules for starting reorganization.
Activities
Create or maintain job categories
PATH:
Settings/Define Job Categories
Prepare Mass Activities
 In this activity you define the control for own, installation-specific mass activities. Implementing your own
mass activities is recommended if you want to process large quantities of data.
Program and change your own mass activities in the customer naming range Y* or Z*. You must not change or
enhance mass activities delivered by SAP.

235
Example
A process can investigate the open items of a contract account for due dates for dunning, while another
process investigates another contract account (compare mass activity 0002 - Creation of Account Statements).
Requirements
Individual data records can be processed independently of one another.
Activities
For an up-to-date, detailed description of the procedure for implementing a mass activity, see SAP note
144461.
To create your own mass activity: Program an interval module, Carry out this activity to define the control.
PATH:
Settings/Prepare Mass Activities
Define Group Frames for Mass Activities

 In this activity you define the group framework for mass activities. To do this, choose the application FI-CA-
MASS. This involves sub-screens that are determined uniquely by their number and that they belong to the
function group.
You only have to run this activity if you want to implement your own mass activities that require specific
additional parameters.
Note
For an up-to-date, detailed description of the procedure for implementing a mass activity, see SAP note
144461.
PATH:
Settings/Define Group Frames for Mass Activities

236
Define Layouts for Mass Activities
 In this activity, you define and modify the layouts for mass activities. This is necessary if you want to
implement your own mass activities.
Note
A detailed and up-to-date description of the procedure for implementing a mass activity is always contained in
SAPNet note 144461.
PATH:
Settings/Define Layouts for Mass Activities

237
238
Program Enhancements
You carry out program enhancements in the following activities.
Define Customer-Specific Function Modules
 In this activity you define the name of a function module that you have programmed yourself for an event
predefined by SAP. You can use the function module to intervene in the flow of the standard programs and to
include your own processing. Function modules are run when the event is reached in the program.
Activities
1. Perform the activity to obtain an overview of the possible events. The form in which standard processing
can be interrupted is specified for each event (see the Additional Function field). You can find the description
for an event in the documentation for the respective sample function module. Select the required event, and
select Display Function Module. You can determine the points in the program in which the event is triggered
using the where-used list for the sample function module.
2. To determine which standard function modules are delivered for an event, select the event and choose
Standard Function Modules. The list of standard function modules also specifies whether customer function
modules are permitted (see the field No Customer Modules).
3. Decide on the events for which you need your own function modules.
4. Program the required function modules. To do this, copy the sample function module into a separate
function module group.
Proceed
5. In this activity, define the names of your function modules for each event. To do this, select the required
event and choose Installation-Specific Function Modules.
PATH:
SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Broker Collections/Program
Enhancements/Define Customer-Specific Function Modules

239
Define Payment Medium Formats BP 04 Process Impounds & Disbursements
 In this activity, you define other payment medium formats. Payment medium formats come standard with
the system. Defining your own formats is thus the exception
Activities
Check, and if necessary, define new formats.
PATH:
Enhancements/Define Payment Medium Formats
Define User IDs for Bank Transactions

 In this activity you define user IDs for processing payment transactions by using the data medium
exchange. User IDs are country and application-specific. User IDs are assigned by the house banks so that
the bank can identify the users.
PATH:
Enhancements/Define Customer-Specific Function Modules
Blank in system

240
Maintain Item Indicator for Payment Program BP 04 Process Impounds & Disbursements
 In this activity, you define item indicators.
Standard settings
The SAP standard delivered system contains item indicators.
Activities
1. Check the delivered item indicators.
2. Define any indicators you may require while adhering to the name range restriction. For more information,
select number reservation after you have executed the activity.
PATH:
Enhancements/Maintain Item Indicators for Payment Program

241
INDEX
BP # Page # Section
01-1 3, 4 Collections/Disbursements: Organizational Units
5, 10, 17 Collections/Disbursements: Basic Functions/Contract Accounts
18, 20 Collections/Disbursements: Basic Functions/Insurance Object
02-1 50, 52 Collections/Disbursements: Basic Functions/Postings and
Documents
58 Collections/Disbursements: Basic Functions/Account Balance
Display
152 Collections/Disbursements: Business Transactions/Payments
02-2 50, 52 Collections/Disbursements: Basic Functions/Postings and
Documents
03-3 50 Collections/Disbursements: Basic Functions/Postings and
Documents
04-1 74, 77, 79, 82 Collections/Disbursements: Basic Functions/Open Item
Management
09-2 86 Collections/Disbursements: Basic Functions/Correspondence

242

CD - SAP End-to-End Configuration

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CD - SAP End-to-End Configuration

Uploaded by

Copyright:

Available Formats

BASIC FUNCTIONS

Activation of Basic Functions

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

Define Company Code Groups BP 01-1 Business Partner

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

Assign Company Codes to Company Code Groups BP 01-1 Business Partner

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

Number Ranges and Contract Account Categories

Number Ranges and Contract Account Categories

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

 In this activity you define contract account categories.

Requirements (BP 01-4 Bank Maintenance)

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

Linking All Remaining Different Criteria (Except the Activity)

Linking the Result with the Activity

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

Linking All Remaining Different Criteria (Except the Activity)

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

Contract Account Relationships BP 01-1 Business Partner

 In this activity, you define contract account relationships.

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

Define Insurance Object Categories

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

Every new insurance object-partner relationship receives a new account.

There is just one account for each insurance object.

There is just one account for every business partner.

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

Partner or account can be freely assigned.

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

Field Groupings and Authorizations

Field Groupings and Authorizations

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

Field Groupings and Authorizations

Linking All Remaining Different Criteria (Except the Activity)

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

Field Groupings and Authorizations

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

The associated authorization object is called I_INSO_FDG.

Authorizations for a user and presentation procedure

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

Maintain Number ranges for mass processing

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

 In this activity you define your main transactions.

 In this activity you define your sub-transactions.

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

C:\Documents and Settings\montalm1\Desktop\Config\SAP End-to-End System Configuration.doc

SPRO/SAP Reference IMG/SAP Insurance/Collections/Disbursements/Basic Functions/Postings