FS Financial Services

________________________________________________________________

Copyright
Copyright(c) 2003 SAP AG. All rights reserved.

Neither this document nor any part of it may be copied or reproduced in any form or by any
means or translated into another language, without the prior consent of SAP AG. The
information contained in this document is subject to change without notice.

SAP is a registered trademark of SAP AG.

All other products which are mentioned in this documentation are registered or not registered
trademarks of their respective companies.
SAP AG Contents R/3 System
________________________________________________________________

1 FS Financial
Services 1
1.1 FS-CD
Collections/Disbursements 1
1.1.1 General New Developments 1
1.1.2 Account Balance Display 1
1.1.3 Account Maintenance for Reinsurance
Business 3
1.1.4 Archiving 4
1.1.5 Argentina Sales and Revenue Tax
Reporting 5
1.1.6 Authorization Objects 6
1.1.7 Insurance-Specific BAPIs 6
1.1.8 New BAPIs in Contract Accounts
Receivable and Payable 8
1.1.9 Broker Collections 9
1.1.10 Business Information Warehouse 13
1.1.11 Cash Journal 14
1.1.12 Submission of Receivables to Collection
Agency 16
1.1.13 Correspondence 18
1.1.14 Credit Processing 20
1.1.15 Creditworthiness 20
1.1.16 Country-Specific Reports 21
1.1.17 Processing Incoming Payments from
External Payment Offices 21
1.1.18 Balance Interest Calculation 25
1.1.19 Insurance Dunning 26
1.1.20 Dunning Notices 28
1.1.21 Insurance-Specific Events 30
1.1.22 New and Changed Events 31
1.1.23 Main and Subtransactions 35
1.1.24 Payment Medium Formats: IDoc Interface 35
1.1.25 Interface for Transferring IDOCs 36
1.1.26 Changes to IMG for Contract Accounts
Receivable and Payable 37
1.1.27 New IMG Activities in Contract Accounts
Receivable and Payable 38
1.1.28 Information System 39
1.1.29 Insurance Invoices 40
1.1.30 Insurance Object 40
1.1.31 Deferral and Installment Plan 41

________________________________________________________________
SAP AG 14.10.2003 iii
R/3 System Contents SAP AG
________________________________________________________________

1.1.32 Debit Memo Notice Procedure (Direct

Debiting) Using BACS (GB) 42
1.1.33 Interest Calculation 45
1.1.34 Job Commander 47
1.1.35 Business Locks 47
1.1.36 Mass Activities 47
1.1.37 Master Data 50
1.1.38 Processing Payments 51
1.1.39 Payment Plans 55
1.1.40 Payment Transactions 56
1.1.41 Postings and Documents 58
1.1.42 Prenotification Functions 65
1.1.43 Print Workbench 66
1.1.44 Receipt Management (New) 67
1.1.45 New Reports 68
1.1.46 Revenue Distribution 70
1.1.47 Reporting Taxes to the Tax Authorities 71
1.1.48 Transferring Business Partner Items 72
1.1.49 Payment Transactions and Processing
Payments in the USA 72
1.1.50 Workflow 73
1.1.51 Write-Offs 74
1.2 FS-CM Claims
Management 75
1.2.1 Activity Management (New) 75
1.2.2 Activity Management: Profile and
Explanation Component (New) 78
1.2.3 Appraisal (New) 79
1.2.4 Incoming Documents in the Claims
Management System (New) 81
1.2.5 Benefit Type Trees (New) 83
1.2.6 Benefit Types (Changed) 84
1.2.7 Business Rule Framework (New) 85
1.2.8 Processing Collective Invoices (New) 88
1.2.9 Integration with BW (Changed) 88
1.2.10 (Statutory) Care Insurance (New) 89
1.2.11 Claim Bundle (Changed) 90
1.2.12 Customizing Internal Claim Types
(Changed) 92
1.2.13 Compensation Calculation (BAdI)
(Changed) 92

________________________________________________________________
iv 14.10.2003 SAP AG
SAP AG Contents R/3 System
________________________________________________________________

1.2.14 Correspondence (Changed) 93

1.2.15 CRM Interface (New) 94
1.2.16 Damaged Objects (Changed) 95
1.2.17 Diagnoses (Changed) 96
1.2.18 Direct Input (Changed) 98
1.2.19 Changes to SAP Easy Access Insurance
(Changed) 99
1.2.20 EDI (New) 100
1.2.21 Home Health Care (HHC) (Changed) 102
1.2.22 IBNR Reserve (Changed) 104
1.2.23 Changes in IMG (Changed) 105
1.2.24 Invoice Entry / Invoice Processing
(Changed) 109
1.2.25 Changes to Main Program (Changed) 110
1.2.26 Medical Devices (New) 112
1.2.27 List of My Claims (Changed) 116
1.2.28 Notes (Changed) 116
1.2.29 Notice of Loss (Changed) 117
1.2.30 Participants (Changed) 118
1.2.31 Payments (Changed) 119
1.2.32 Changes in the BAdI for Policy Interface
(ICL_POLS_IMPORT_POLS) 120
1.2.33 Multiple Prescription (New) 121
1.2.34 Procurement (Changed) 122
1.2.35 Reimbursement of Simple Invoices
(Changed) 123
1.2.36 Reporting (Changed) 123
1.2.37 Reserve (Changed) 124
1.2.38 Structured Facts Capture (Changed) 124
1.2.39 Notes on Upgrading to Release 4.71 125
1.2.40 Where-Used List and Deletion Check in
Customizing (New) 125
1.2.41 SAP Business Workflow in the Claims
Management System (New) 126

________________________________________________________________
SAP AG 14.10.2003 v
 R/3 System
________________________________________________________________

1 FS Financial Services

1.1 FS-CD Collections/Disbursements

1.1.1 General New Developments

Use
o Unicode: The Collections/Disbursements (FS-cd) system is now Unicode capable.
o No barriers: The central functions and the central transactions in the Collections/Disbursements
system will be usable without barriers.

1.1.2 Account Balance Display

Use

New Fields in the Structure FKKEPOS

Fields ORINO, ORINO_REF

For all items that are read from the database, a unique sequential number is assigned in the field ORINO.
For all simulated items, the entry in field ORINO_REF specifies which sequential number (ORINO) the
item for which the simulation took place has. You can therefore uniquely determine which items were
simulated for which items.

Field VRGNG

Field VRGNG (transaction) consists of the contact actions of the fields Main Transaction and
Subtransaction, and enables you to search for items with specific main/subtransactions by entering only
one selection criterion.

Fields CPUDT and CPUTM

The fields CPUDT (date of entry) and CPUTM (time of entry) are now available.

Exclusion from Selections

When you enter selection conditions, you can now also specify values to be excluded from the selection.

________________________________________________________________
SAP AG 14.10.2003 1
R/3 System
________________________________________________________________

Selection of Document Category

On the detail screen for the list category, in the area Selection for Installment Plans, you can control
whether you want to display the underlying original receivables or the installment plan items. In both
cases, all items that have not been included in an installment plan are selected.

Enhancement to the function Field-Sensitive Doubleclick

If you select this field in the user-specific settings, when you doubleclick on the following line items, the
corresponding object is displayed:
o Installment plan item
o Cash security deposit request
o Budget billing plan

When you doubleclick on the installment plan item, the installment plan is also displayed. You can also
access the line items via Environment -> Document -> For Installment Plan Items -> -> Installment
Plan .

Changes in the Menu

The following entries have been added to the menu Environment -> Account:
o Mass Change (Branch to transaction Document Mass Changes)
o Account Maintenance (Branch to transaction Account Maintenance)
o Security Deposits (Display securities)
o Installment Plans (Display installment plans)
o Budget Billing Plans (Display budget billing Plans)

Item Selection

By doubleclicking on the light icon you can display the item inversed.

Buttons IP (Installment Plan) and BP (Budget Billing Plan)

The scope of functions of the buttons IP (Installment Plan) and BP (Budget Billing Plan) has been
extended. If the cursor is not on one specific line item, when you select the button, a list of all installment
plans or budget billing plans that exist for the master data selected is displayed.

This is the same for the pushbutton.

Changes to Event 1203

For event 1203 you can now also define that, for example, credits and receivables can be displayed in
different colors.

________________________________________________________________
2 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

Changes to Event 1205

For event 1205 you can now also define that an item does not appear in the normal list (receivables/down
payments) but is still to be displayed in the payment list. This means that you can hide clearing from the
list of receivables but retain them in the payment list.

Changes to Event 1207

For event 1207 you can now also define that the totals displayed on the tab page Totals are output in the
header area of the list.

Changes to Event 1211

For event 1211 you can define whether an additional button for displaying the original document is
displayed in the account balance display. You can define the text for this button via the field
E_FTEXT_1117. The button is displayed in the application toolbar and the module defined for event
1117 is called.

Alternative Display Option as ALV Grid

As an alternative to the previous list, on the initial screen you can select the display as ALV Grid list. The
usual tab pages (for example, Receivables, Down Payments) are retained. The detailed display of a
payment on the tab page Payment List is replaced by doubleclicking on the payment. The document
display appears. There you can display the items for the clearing document and thereby the cleared items.

The functions in the list and the functions that you can use via the menu are generally the same as those
in the standard list.

You can define the layout of the header area individually via the new event 1217 by specifying the
number of a subscreen on which you want the additional data to be displayed.

Effects on Customizing

Define the installation-specific function modules for the events stated in the Implementation Guide for
Contract Accounts Receivable and Payable under Program Enhancements -> Define
Customer-Specific Function Modules.

1.1.3 Account Maintenance for Reinsurance Business

Use

Manual account maintenance (transaction FP06) will provide an insurance-specific subscreen, to allow
the selection of items with certain clearing restrictions (cash losses, estimation postings). The following
prerequisites have to be met to display the function:

________________________________________________________________
SAP AG 14.10.2003 3
R/3 System
________________________________________________________________

o You have installed SAP Reinsurance (FS-RI) and an entry is available in the AVERS table
o You have the appropriate authorizations (authorization objects I_CDRI_SE and I_CDRI_SB).

The following processing options are available:

o Standard account maintenance: The system selects all items that do not have a clearing restriction
o Including cash losses: In addition to the open items, the system selects receivables and payables with
the clearing restriction cash loss
o Only process estimation postings: The system only selects receivables and payables with the clearing
restriction estimation posting.

Effects on Customizing
o Cash losses are transferred from FS-RI to FS-CD as payment plan items and are posted statistically
as payment requests after the payment plan has been executed. The payment run clears these items
and creates open items with the clearing restriction cash loss, which prevents clearing with other
open items. In order to flag cash losses as statistical items with the cash loss clearing restriction,
choose Collections/Disbursements -> Basic Functions -> Postings and Documents -> Document ->
Define Account Assignments for Automatic Postings -> Define Account Assignments for Down
Payments and Charges.
o Estimation postings are transferred from FS-RI to FS-CD as payment plan items and are posted as
receivables and payables with the clearing restriction estimation posting after the payment plan has
been executed. In order to flag items with the estimation posting clearing restriction, mark the
appropriate main and subtransactions with the clearing restriction estimation posting. Choose
Collections/ Disbursements -> Basic Functions -> Postings and Documents -> Maintain Document
Assignments -> Maintain Transactions SAP Insurance (FS-CD) -> Define Clearing Restrictions for
External Transactions.

1.1.4 Archiving

Use

All FI-CA archiving objects have been adjusted to SAP Basis 6.20.

All report interfaces have been unified; the archiving objects now also support the interruption of the
archiving transaction.

Archiving of Requests and Standing Requests

You can use the archiving object FI_MKKORDR to archive requests and standing requests.

________________________________________________________________
4 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

Archiving of Revenue Distributions

You can use the archiving object FI_MKKREVD to archive revenue distributions.

Archiving of Documents

The document archiver considers the posting date when you select the documents to be archived. The
archiving key date influences the quantity of documents selected.

The fields FIKEY, XBLNR, BLDAT, BUDAT, BLART, WAERS , and HERKF from structure
DFKKKO have been added to the field catalog SAP_FICA_DOC001.

The field FIKEY has been added to the archive information structure SAP_FICA_DOC001. Document
itemizations can now also display archived documents.

The archiving program RFKKAR10 no longer checks whether the archive information structure
SAP_FICA_DOC001 is active. Instead, when reading, the program always checks whether the search
fields requred exist in the primary key or the index.

Archiving of Contract Accounts

You can now reload archived contract accounts.

Archiving of Returns

When you archive returns, tables DFKKRP3 and DFKKRF are archived.

Archiving of Additional Tables for Generic Tax Reporting

You can use the archiving object FI_MKKGENS to archive the additional table for generic tax reporting.

Archiving of Payment Lots

When you archive payment lots, table DFKKZPT is archived.

Effects on Customizing

1.1.5 Argentina Sales and Revenue Tax Reporting

Use

As of FI-CA Release 4.71, you can generate the following sales and revenue tax reports for Argentina:

________________________________________________________________
SAP AG 14.10.2003 5
R/3 System
________________________________________________________________

o Daily VAT Report RFKKARVAT_BOOK

o VAT Magnetic Support RFKKARVAT_MAG_SUPPORT
o VAT Fiscal Position RFKKARFISCAL_POSITION (includes fiscal debit and fiscal credit reports)
o VAT Perception RFKKARVAT_PERCEPTION
o Gross Income Perception for Buenos Aires RFKKAR_GI_PERCEPTION
o Gross Income Tax Declaration RFKKARREVTAX_R
o Municipal Tax Declaration RFKKARREVTAX_C

Effects on Customizing

To run these reports, you must make a number of settings in Customizing for Financial Accounting,
under Contract Accounting -> Basic Functions -> Tax Reports -> Tax Reporting - Argentina. Refer
to the respective report documentation for further details.

1.1.6 Authorization Objects

Use

Requests and Standing Requests

You can use the following authorization objects to protect the functions for processing requests and
standing requests dependent on the company code, the request class, and the request category:
o F_KK_ODBUK
o F_KK_ODCLS
o F_KK_ODTYP

Correspondence History

When you change the amount manually, the new activity U2 for authorization object P_CORR is
checked.

1.1.7 Insurance-Specific BAPIs

Use

________________________________________________________________
6 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

Master Data
o The FSCDInsuranceObject object and the CD_INSOBJ object category are rendered obsolete from
Release 4.71. From Release 4.71, use the FSCD_InsuranceObject object and the BUSISI003 object
category for the Business Object insurance object.
Take note of the following changes to the methods:
- BAPI_CD_INSOBJ_CHANGE is now instance-dependent and has the new INSOBJNUMBER
parameter.
- BAPI_CD_INSOBJ_GETDETAIL is now instance-dependent. The import parameter was
changed from INSOBJ_NUMBER to INSOBJNUMBER.
o The FSCDContractAccount object and the BUSISI004 object category are rendered obsolete from
Release 4.71. From Release 4.71, use the FSCD_ContractAccount object and the BUSISI004 object
category for the Business Object contract account.

Broker Collections

You will be able to use BAPIs to process broker reports. The Broker Report Business Object (object
category BUSISI001) has been created for this. The following methods and events are available:
o BrokerReport.Create(): Create a broker report
- V580 (sample module ISCD_SAMPLE_V580): Check
- V592 (sample module ISCD_SAMPLE_V592): More processing steps
o BrokerReport.Change(): Change a broker report
- V596 (sample module ISCD_SAMPLE_V596): Check
- V598 (sample module ISCD_SAMPLE_V598): More processing steps
o BrokerReport.Remove(): Delete a broker report
- V599 (sample module ISCD_SAMPLE_V599): Check and more processing steps
o BrokerReport.Close(): Close a broker report
- V597 (sample module ISCD_SAMPLE_V597): Check and more processing steps
o BrokerReport.GetDetail(): Display a broker report
- V585 (sample module ISCD_SAMPLE_V585): Check and more processing steps
o BrokerReport.GetList(): Search for broker reports
- V586 (sample module ISCD_SAMPLE_V586): Check
- V587 (sample module ISCD_SAMPLE_V587): More processing steps
o BrokerReport.ExistenceCheck(): Check for existence of broker report
o BrokerReport.AddItem(): Create broker report items
- V581(sample module ISCD_SAMPLE_V581): Check
- V593 (sample module ISCD_SAMPLE_V593): More processing steps
o BrokerReport.ChangeItem(): Change broker report items

________________________________________________________________
SAP AG 14.10.2003 7
R/3 System
________________________________________________________________

- V582 (sample module ISCD_SAMPLE_V582): Check

- V595 (sample module ISCD_SAMPLE_V595): Other processing steps
o BrokerReport.RemoveItem(): Delete broker report items
- V579 (sample module ISCD_SAMPLE_V579): Check and other processing steps
o BrokerReport.ItemGetDetail(): Display a broker report item
- V584 (sample module ISCD_SAMPLE_V584): Check and other processing steps
o BrokerReport.ItemGetList(): Search for broker report items
- V588 (sample module ISCD_SAMPLE_V588): Check
- V589 (sample module ISCD_SAMPLE_V589): More processing steps
o BrokerReport.GetOpenItems(): Select open items in broker collections
- V590 (sample module ISCD_SAMPLE_V590): Check
- V591 (sample module ISCD_SAMPLE_V591): More processing steps
o BrokerReport.CollectItems(): Create broker report items from open items
- V583 (sample module ISCD_SAMPLE_V583): Check
- V594 (sample module ISCD_SAMPLE_V594): More processing steps

Note

The BAPIs and the Business Object have not been released, but they can be used. Release will take place
at a later date.

1.1.8 New BAPIs in Contract Accounts Receivable and Payable

Use

Creditworthiness of a Business Partner

You can now use new BAPIs for the business object CtrAcCreditRating to process the creditworthiness.
The BAPIs enable you to determine the creditworthiness value and to create and reverse external
creditworthiness entries:

The following methods are supported:

Get Determination of creditworthiness value

(BAPI_CTRACCREDITRATING_GET) for a specific date

CREATE Creation of an external

(BAPI_CTRACCREDITRATING_CREATE) creditworthiness entry

________________________________________________________________
8 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

CANCEL Reversal of an external

(BAPI_CTRACCREDITRATING_CANCEL) creditworthiness entry

Transfer of Open Business Partner Items

For the business object CtrAcDocument there is a new BAPI for method Transfer:

Transfer Transfer of open

(BAPI_CTRACDOCUMENT_TRANSFER) business partner items

Write Off Items

For business object CtrAcDocument there is a new BAPI for method Writeoff:

Writeoff (BAPI_CTRACDOCUMENT_WRITEOFF) Write off items

Change an Installment Plan

For business object Installmentplan there is a new BAPI for method Change:

Change Change an existing

(BAPI_INSTMNTPLN_CHANGE) installment plan

1.1.9 Broker Collections

Use

Master Data: Broker Contract

o Two new fields will be available for broker contracts (internal insurance object category 20) on the
Broker Collections tab page, which enable totals posting from customer accounts and the
commission account to the broker account, with a shifted due date. To post with a shifted due date,
specify a period and a number of periods. You can find more information in this release note, in the
section entitled Posting (Totals Documents).
o You will be able to set a dunning lock for broker contracts (internal insurance object category 20) on
the Broker Collections tab page, which locks all insurance relationships that are assigned to the
broker contract. You can find more detailed information about this in the release note for dunning.

________________________________________________________________
SAP AG 14.10.2003 9
R/3 System
________________________________________________________________

Broker Report: Selection of Open Items

When selecting open items for a broker report item, the company code for the broker report item is no
longer taken into account, meaning that open items from more than one company code can be selected for
a broker report item. If you want to use a company code for selection, you must create an appropriate
selection category in the Implementation Guide.

Note

Open items that have already been selected for a broker report are not processed again in another broker
report, as long as the corresponding item has not been posted. The open items excluded in this way are
passed to event V520 with exception reason 016 (line item already selected in other report) and can then
be included in the selection on a customer-specific basis (see the sample module documentation for
ISCD_SAMPLE_V520).

Broker Report: Automatic Creation

If you create broker reports automatically (Create broker report, transaction IBR50), theInclude Items
Before Invoicing Period flag will be available. If you set the flag, the system recognizes those open items
on customer accounts and the commission account that are due before the invoicing period (reporting
interval) for the broker report.

Broker Report: Create and Edit

o Previously, you defined screen variants for broker report item entry in the Implementation Guide.
You will now be able to define line layout variants, which use Table Controls to enter items for
premiums, commission, claims and costs. This has caused the following changes:
Screen variants are no longer valid; you have to create line layout variants.
The system offers support for the conversion to line layout variants, in the form of the
IBRO_VAR_MIGRATE program. This allows you to migrate screen variants. As the old screen
variants permitted a 5-figure key, but the new line layout variants only allow 3 figures, the old keys
will be changed the simplest way to do this is to remove the last two characters from the key. The
variant names will remain unchanged.
You can use event V541 to set field attributes for customer fields.
o You will be able to differentiate the specifications for broker report entry for each category,
according to the external insurance object category. The line layout variant has replaced the screen
variant in the detail screen for a category.
o You will be able to execute the proposal function on the fast entry screen. A proposal is then
executed for the associated premium and commission item.

Broker Report: Grouping Broker Report Items and Effects on Postings

Broker report items will no longer be grouped according to the company code and the business area as
standard. You can therefore select open items from more than one company code and/or business area in
a broker report. To do this, you have to have set the Can Be Used for Multiple Groups of Open Items
indicator for the company code that you use to post the broker report item.

________________________________________________________________
10 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

o If you use the posting rules 01 or 21 (Posting according to proposal) and 06 or 26 (Clearing
according to clearing rules), the open items to be cleared are grouped according to company code
and business area. The resulting totals documents contain separate G/L items on the clearing account
or the business partner items on the broker contract, differentiated according to company code and
business area. The totals documents do not contain just one G/L item and a business partner item, but
the number of items is determined from combinations of company code and business area.
o If you use other posting rules, the company code and business area for the broker report item are
used when posting. If items from multiple company codes/business areas are cleared, but no
grouping takes place, the broker report item is included in the totals posting with its company code
and business area.

If you want to group broker report items according to the company code and/or business area, you must
use groupings that contain the appropriate selection categories.

Broker Report: Posting (Single Documents)

When clearing open items on customer accounts and the commission account, with the permitted
tolerance, the expense/revenue account to be used for posting is determined with the new posting area
V305. The tolerances are distributed proportionally to each created G/L item.

Broker Report: Posting (Totals Documents)

The due date is taken into account during summation for single documents in totals documents, in
addition to the business area and the company code, as long as you have defined specifications for the
shifted due date on the broker contract.

In this case, the open items for the customer are also grouped according to the due date and posted to the
broker contract as a total with shifted due date, corresponding to the specifications on the broker contract.
As with grouping according to company code and business area, this is only valid if you use posting rules
01 or 21 and 06 or 26. If you use other posting rules, the posting data from the broker report header is
used as the due date for net payment for the totals postings on the broker contract. The new event V551
can be used to adjust the base date for shifting items. For example, this allows you to specify a one-month
shift for the due date for a broker, so that open items from customers with a due date before the 15th of a
month are posted on the 15th of the following month, and open items from customers with a due date
after the 15th of a month are always posted to the broker contract at the end of the following month.

You will have to define a clearing reason in the specifications for the broker totals posting. If you do not
define a clearing reason, the totals postings cannot be posted with non-original brokers.

Broker Report: Withholding Tax

If line items (commission, claims) with withholding tax, which can be retained by the insurance
company, are used when posting the broker report, only the net amount is posted to the broker contract.
The withholding tax to be retained is posted to the withholding tax account determined in Customizing.
This means that the broker report posting is interpreted as a payment-relevant transaction.

A field for the withholding tax to be deducted when clearing the selected items is available in the item
overview and the detailed view, as long as the reported amount and the proposal amount correspond to

________________________________________________________________
SAP AG 14.10.2003 11
R/3 System
________________________________________________________________

the net amount.

Broker Report: Reversal of Broker Report or Broker Report Item

When reversing a broker report or a broker report item, a check is made on the new Reverse activity (85)
for the authorization object I_VVBR_STM.

Broker Report: Italian Tax Correction

When you post a broker report item, the system checks that items to be cleared to see whether the tax
specifications in the items are up to date. If this is not the case, the item is not posted and the broker
report has the status Broker Report Awaiting Tax Correction. You can also execute the tax correction run
from the Process broker report transaction (IBR01), and then post the broker report.

Broker View Authorization Level

In user maintenance, you can define the brokers that a user can edit. This was previously mapped with a
reference to the broker (Business Object category BUS1006 Business partner). You will now have to
enter a reference to the new Business Object category Broker contract (BUSISI002, key fields broker,
broker contract). You also have to make appropriate changes to existing references to user master
records. You can find more information in the document for the ISCD_BROK_AUTHORITY_INIT
function module

Broker Collections: BAPIs

You will be able to use BAPIs to process broker reports. You can find more detailed information in the
release note entitled Insurance-Specific BAPIs.

Correspondence Dunning

You can find detailed information for brokers, for which you have chosen the Periodic report request
report category, in the release note for correspondence.

New Events

The following events will be available:

o V551 (sample module ISCD_SAMPLE_V551): Adjustments to totals posting for broker with shifted
due date
o V541 (sample module ISCD_SAMPLE_V541): Setting field attributes for customer fields in the line
layout variants for item entry

Effects on Customizing
o In order to be able to set a dunning lock for broker contracts for assigned customer contracts, you

________________________________________________________________
12 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

have to set the Dunning Lock for Dependent Contracts on Broker Contract flag. Choose
Collections/Disbursements -> Broker Collections -> Activation of Basic Functions.
o In order to use the company code, business area or the due date as selection categories for item entry
in the broker report, choose Collections/Disbursements -> Broker Collections -> Define Selection
Categories for Broker Reports and Define Groupings for Broker Report Items.
o In order to execute postings with company code and business area, choose
Collections/Disbursements -> Broker Collections -> Configure Clarification Codes. Set the Can Be
Used for Multiple Groups of Open Items indicator for clarification codes that use suitable posting
rules.
o Define a clearing rason in the Specifications for Broker Totals Postings. Choose
Collections/Disbursements -> Broker Collections -> Settings for Posting Broker Reports.
o In order to define line layout variants, choose Collections/Disbursements -> Broker Collections ->
Line Layout Variants for Broker Report Item Entry. Define line layout variants in the Specifications
for Automatic Broker Report Postprocessing.
o In order to define expense/revenue accounts for writing off tolerances, choose
Collections/Disbursements -> Broker Collections -> Define Expense/Revenue Accounts for Payment
Differences.

1.1.10 Business Information Warehouse

Use

Extraction of Open Items

The extraction of open item uses the same method as the extraction of cleared items, that is, you can sort
values and also extract derived fields (for example, days overdue) if you define this in Customizing.

Extraction of Open and Cleared Items

The legibility of the sorting has been improved. Instead of (0040)-0000, A(40)-0 is output.

Extraction of Collection Items

You can now extract entries from the history for the submission of items to collection agencies
(DFKKCOLLH) (menu: Periodic Processing -> Extraction for Business Information Warehouse).

Effects on Customizing

You define derived fields for the extraction of items in the Implementation Guide for Contract Accounts
Receivable and Payable under Integration -> Business Information Warehouse -> Define Fields for
the Extraction of Items .

________________________________________________________________
SAP AG 14.10.2003 13
R/3 System
________________________________________________________________

1.1.11 Cash Journal

Use

Cash Balance

The cash balance displays the type of payment (for example, cash payment). In the display, you can
display details by doubleclicking, for example, individual payments and deposits.

Historical Data

In the Historical Data display the individual nodes are displayed with their names. By doubleclicking on
the nodes, you can display the additional information or also individual documents from which, for
example, the total amount of a deposit is made up and is displayed under Deposit.

Automatic Creation of Lots

The cash journal automatically creates the corresponding payment lot depending on the payment
category.

In the cash desk, this lot is only displayed in the field Lot; you cannot change it.

To create a lot manually, you have to use the function Create Lot in the menu under Cash Desk. The
cash journal checks whether an appropriate lot has already been created. If this is the case, no new lot is
created.

Before you can create a new lot manually, you may have to close existing lots. To do this, use the
function Close Lot under Cash Desk in the menu.

Only create the lot manually as an exception, for example, if you want to document specific incoming
payments separately in a lot created for this purpose.

Check Lot

In the cash journal, incoming and outgoing check lots are managed in separate check lots to simplify
reconciliation.

Posting Deposits, Differencs, and Withdrawals

You can post deposit, difference, and withdrawal postings as line items. If you have set the indicator Line
Item, the G/L items are not grouped in the reconciliation key and line items are created when you transfer
the relevant reconciliation key from FI-CA to the general ledger.

________________________________________________________________
14 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

Carry Out and Display Cash Desk Closing

In cash desk closing, the totals of the deposits and withdrawals posted are displayed. Therefore, for the
post withdrawals function, only payments with the same payment category are withdrawn
simultaneously.

Overview of Cash Desk Closing

You use the overview (menu: Payments -> Cash Desk) to display the closing carried out in the cash
journal across all cash desks and all branches. In the cash journal you can only display cash desk closing
for the current cash desk and branch. The transaction enables you to display the cash desk closing
dependent on the following selection criteria:
o Cash desk
o Branch
o Date of cash desk closing
o Closing carried out by
o Status of closing

Only the closing data that is permitted in accordance with the role of the current user is displayed. The
following roles are considered:
o Branch office manager
o Clerk with special tasks
o Clerk

The data display and the functions available agree with the display of cash desk closing in the cash
journal. Only the fields Branch and Cash Desk are displayed in addition in the tree of the grouping
fields.

Note the information about the new and changed events in the release information FICA_471_EVENTS.

Effects on Customizing

Cash Journal

The Customizing for the cash journal is located under Business Transactions -> Payments ->
Processing Incoming and Outgoing Payments -> Cash Journal

There you can maintain the role-specific activities (Maintain Role-Specific Activities for the Cash
Journal) and, for example, define that a clerk is not permitted to carry out the activity Change Cash
Desk. Note that certain activities exclude each other. The corresponding indicator not being active shows
you this.

Under Maintain Specifications for the Cash Journal you can make further settings. You can define,
for example, whether you want to permit a partial withdrawal or the withdrawal of negative amounts.

________________________________________________________________
SAP AG 14.10.2003 15
R/3 System
________________________________________________________________

Overview of Cash Desk Closing

Using this transaction is only recommended if you have activated the cash journal and cash desk closing,
otherwise no cash desk closing data arises and you cannot display anything. If you do not use roles in the
cash journal, all cash desk closing is displayed according to the selection criteria.

Check your system settings in the Implementation Guide for Contract Accounts Receivable and Payable
under Business Transactions -> Payments -> Processing of Incoming and Outgoing Payments
-> Cash Journal -> Maintain Specifications for the Cash Journal .

1.1.12 Submission of Receivables to Collection Agency

Use

You can now forward additional information to collection agencies. There are also new functions for
submitting receivables, for managing receivables submitted, for processing incoming information, and for
calling back items.

Information for Collection Agencies

Using the mass run Information for Collection Agencies (menu: Periodic Procesing -> For Contract
Accounts -> Submission for Collection), you can forward additional information to the collection
agencies you use. You can create information files as follows:
o The business partner has paid part or all of the outstanding amount to you directly.
o You want to call back one or more items because the collection agency could not collect these items
within a specified period.
o The master data of one or more business partners has changed.
o You have reversed the direct payment of a customer for a previously submitted item.
o After the direct payment by a customer, you have partially or completely reset the clearing for a
previously submitted item.
o The direct payment by a customer for a previously submitted item leads to a return, so that the
receivable is now open again.

Automatic Submission of Receivables to Collection Agencies

The functions for submitting receivables to collection agencies are now available as mass activities to
improve performance. Using a submission run is particularly recommended if you are processing a large
volume of data.

________________________________________________________________
16 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

History of Collection Items

You can track the history of a collection item in the transaction Collection Item History (menu: Account
-> More Information).

Calling Back Submitted Items

You can call back items that have been submitted to a collection agency and possibly submit them to
another collection agency. You can use the transaction Callback Receivables (menu: Periodic
Processing -> For Contract Accounts -> Submission for Collection) and a separate mass activity in
the form of function module FKK_RECALL_FROM_AGENCY_0350 to call back items submitted
automatically.

Transfer of Information from a File

Using report RFKKCOPM, in addition to a payment lot, you can also create an incoming check or credit
card lot from the incoming payment data from a collection agency.

Payment Form ID for Collection Agency

When you submit items, you can group all items for a business partner under one payment form ID.

The payment form ID appears in every item in the submission file for the collection agency. When the
agency reports collected receivables, it can specify the payment form ID as payment reference. This
enables you to automatically assign the incoming payments to the submitted collection items.

Effects on Customizing

Define the installation-specific function modules for the events described below in the Implementation
Guide for Contract Accounts Receivable and Payable under Program Enhancements -> Define
Customer-Specific Function Modules.

Exclude Items from Release

In addition to partially paid items, credit memos, budget billing amounts and open items, you can also
release statistical receivables for collection.

As standard, in event 5059, you can only submit statistical items with the statistical indicators G (other
statistical receivables such as charges and interest) and P (budget billing plan items) for collection.

Submit Additional Documents to Collection Agency

Via event 5069 you can select additional documents during the submission of receivables to a collection
agency.

________________________________________________________________
SAP AG 14.10.2003 17
R/3 System
________________________________________________________________

Additional Submission Checks

Via event 5058, you can carry out additional checks before submitting receivables to a collection agency.

Add Information File

Via events 5051, 5052, and 5053, you can fill industry- and customer-specific fields of the file header,
file body, and file footer with information for the collection agency.

Information for Collection Agencies

You define the specifications for transferring information to collection agencies in the Implementation
Guide for Contract Accounts Receivable and payable under Business Transactions -> Submission of
Receivables to Collection Agency -> Specifications for Transferring Information to Collection
Agencies. Here you define the information that is to be placed in the file for the collection agency.

1.1.13 Correspondence

Use

Correspondence Dunning History

In the correspondence dunning history you can assign the next dunning level to an entry. When you then
start the correspondence dunning run, this assigns the new dunning level to the relevant incoming
correspondence. You can therefore, for example, dun an entry that has already reached the highest
dunning level with the highest dunning level again.

There are also new example dunning activities for correspondence dunning:
o Enter business partner in a telephone list
SAP delivers the function module FKK_SAMPLE_0746_TEL_ITEM for this. This is the same
telephone list that is used to dun overdue receivables.
o Write a creditworthiness entry for the dunned business partner
(FKK_SAMPLE_0746_CREDIT_RATING)
o Change the amount of the dunned correspondence that is saved in the correspondence history
(FKK_SAMPLE_0746_DOUBLE_AMOUNT).

Correspondence Dunning: Reminders

When you dun incoming correspondence, you can now send a reminder to your customer before the
correspondence becomes due. This reminder is an optional dunning level. Read the information about the
required Customizing settings in the correspondence dunning level in the section 'Effects on

________________________________________________________________
18 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

Customizing' and about the changes to the Correspondence Dunning Run in the section 'Mass
Activities'.

Correspondence History

In the correspondence history you can change amounts manually. The amount visible in the
correspondence history is only for information purposes, but changing the amount can be helpful for
incoming correspondence if the correspondence dunning run is supposed to react to it. For example, the
charges calculation or a dunning activity can be dependent on the incoming correspondence amount.
When you manually change the amount, the system checks the new activity U2 for the authorization
object P_CORR.

When you reverse correspondence dunning, the new event 0747 is called. You can use this to carry out
customer-specific reversal activities.

Write-Off Notification

To inform customers that you are waiving specific receivables or parts of receivables, you can use
correspondence type 0034 (write-off notification). The relevant form class is FI_CA_WRITEOFF. The
application form example is FI_CA_WRITEOFF_SAMPLE. The correspondence creation event is
1917, the print event is 1918.

You carry out write-offs in the transactions Write-Off Items in the menu under Account or Write-Off
Run in the menu under Periodic Processing -> For Contract Accounts). Then you can use the new
dunning activity C034 to create the write-off notifications (menu: Periodic Processing -> For
Contract Accounts -> Create Write-Off Notifications). This creates entries in the correspondence
container for the selected write-offs. The write-offs created are printed separately by correspondence
print (FPCOPARA).

Correspondence Dunning Run (Changed)

In order to realize the reminder before due date (see section 'Correspondence Dunning: Reminders'), the
parameter Correspondence Dunning Run Type has been added to the correspondence dunning run. If
this field is empty, this corresponds to the behavior up to now - that is, only dunning notices are created.
On the tab page Mode of the correspondence dunning run you can choose between the correspondence
dunning run types Dunning Notice, Reminder, or Dunning and Reminder.

Note

If the parameter Correspondence Dunning Run Type is not visible in your installation, you have to
add the group frame 3007 (Correspondence Dunning Run Type) to the layout 0020 (correspondence
dunning) on tab page 02 (Mode).

Balance Notification

When you create balance notifications you can enter a key date for the selection of the open items -
previously the date of issue was always used.

You can also list items that you have already informed the customer about separately to the new items

________________________________________________________________
SAP AG 14.10.2003 19
R/3 System
________________________________________________________________

posted in the balance notifications. To do this, on the tab page select Date and Period and Key Date for
New Items:
o Last key date
All of the items posted since the key date of the last run are listed as 'new' in the balance
notifications.
o Other date
All items posted since the key date specified here are listed as 'new' in the balance notifications.

The mass activity transfers two tables to the correspondence form.

Effects on Customizing

To make the parameter Correspondence Dunning Run Category visible, in the Implementation Guide
for Contract Accounts Receivable and Payable choose Technical Settings -> Define Layouts for Mass
Activities.

1.1.14 Credit Processing

Use

In credit memo clarification (menu: Payments -> Credits) you can now trigger the creation of a
clarification letter (correspondence type 0032) when you process individual credit items. Here you can
ask the customer how they want to use the credit.

Correspondence type 0032 uses the application form FI_CA_CRED_CLAR_SAMPLE (SAPScript

Form FI_CA_CRED_CLAR ) from form class FI_CA_CRED_CLAR.

Effects on Customizing

You make the settings for controlling correspondence type 0032 in the Implementation Guide for
Contract Accounts Receivable and Payable under Basic Functions-> Correspondence -> Define
Correspondence Types.

1.1.15 Creditworthiness

Use

You can now enter creditworthiness entries manually. This enables even business transactions, such as
customer complaints about unjustified returns (improved creditworthiness) or 'black lists' from external
credit assessors such as SCHUFA (Society for General Credit Security) in Germany (decline in

________________________________________________________________
20 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

creditworthiness), to influence the creditworthiness of a business partner.

Manual creditworthiness entries

o Have the same influence on the creditworthiness of a business partner as creditworthiness entries
created in the system
o Can have positive (creditworthiness decline) and negative (creditworthiness improvements) values
o Can also be reversed

You can use an info text to describe the business transaction that led to the creditworthiness change.

You can create and reverse creditworthiness entries manually:

o In transaction Change Business Partner Creditworthiness in the menu under Account ->
Additional Information -> Creditworthiness
o with the BAPIs BAPI_CTRACCREDITRATING_CREATE and
BAPI_CTRACCREDITRATING_CANCEL

Effects on Customizing

1.1.16 Country-Specific Reports

Use

Effects on Customizing

To make these reports visible in the SAP Easy Access menu, you need to enter them in Customizing. All
country-specific reports are stored in one table, accessible via the following activities in Customizing for
Financial Accounting, under Contract Accounting >
o Basic Functions > Tax Reports > Define Programs for Creating Tax on Sales and
Purchases Returns
o Business Transactions > Payments -> Incoming/Outgoing Payments Processing > Define
Programs for Converting Country-Specific Formats into MultiCash

You can choose from all available reports via the input help. By entering them in one of these activities,
you define that they are accessible via the SAP Easy Access menu. For instance, you wish to display only
those reports relevant to your country. You can set the PND indicator for a given report, and the
corresponding report is then not displayed in the menu.

________________________________________________________________
SAP AG 14.10.2003 21
R/3 System
________________________________________________________________

1.1.17 Processing Incoming Payments from External Payment Offices

Use

In Japan, in addition to paying their invoices direct to the company concerned, customers of
telecommunications companies and utility companies can also pay their invoices to third party payment
service providers (external payment collectors) such as post offices, banks, or chain stores (convenience
stores/CVS) using a payment form. Once an external payment collector has received payments from
customers, it sends two sequential files to the billing company:
o Advance information with the payments collected
The receipt of the payments contained in this file is not guaranteed and the payments have the status
Unconfirmed in the system.
o Confirmation of the payments contained in the advance information
The receipt of the payments is guaranteed. The payments have the status Confirmed in the system.
In this file, an external payment collector can also inform the company about the recall of payments
that have already been notified or correct payment information. In these cases the advance
notification is reversed. The company does not receive a payment.

The payment data from the advance information file is transferred using a payment lot; the payment data
from the confirmation file is transferred using program RFKK_CVSPAY_CONFIRM (menu: Payments
-> External Payment Collectors -> Transfer Payment Confirmations).

Recalled payments are processed in returns lots. SAP delivers the payment and returns lots templates for
processing and storing the data.

You use the payment form number to assign payments and therefore clear open receivables.

Dunning notices and the calculation of interest on open items are based on the data of the payment
confirmation.

In the account balance display, the items concerned have a separate icon (Payment Notified by External
Payment Collector).

At the end of the month, the external payment collectors send the company a bill for the stamp tax and
commission. Using program RFKK_CVSPAY_EXAM, you can compare the receivables in these
invoices with the confirmed payments posted in the system.

Post offices and banks only transfer one file with the confirmed payments. The payments are posted using
payment lots. Since the payments have already been confirmed, the stamp tax due is determined
automatically. This means that you do not have to transfer the payment data with program
RFKK_CVSPAY_CONFIRM. The stamp tax and commission is also invoiced separately. You can use
program RFKK_CVSPAY_EXAM to compare the data.

Details in Payment Lots

Currently, Contract Accounts Receivable and Payable supports the processing of payments from post

________________________________________________________________
22 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

offices, convenience stores, and banks in payment lots.

To process unconfirmed payments from convenience stores in payment lots, enter the following data in
the payment lot header:
o Code of the external payment collector
o Payment status Unconfirmed
o Clearing reason 26

Also specify the account defined for the interim posting as the bank clearing account. This is defined in
Customizing under Business Transactions -> Payments -> Processing of Incoming/Outgoing
Payments External Payment Collectors -> Account Determination for Payment Confirmation.

Choose the payment form number as selection criteria and then specify only the payment form number as
selection criteria in the items.

To process payments from post offices and banks in payment lots, enter the following data in the payment
lot header:
o Code of the external payment collector
o Payment status Confirmed
o A clearing reason

Choose the payment form number as selection criteria and then specify only the payment form number as
selection criterion in the items.

Events

In the following events you can influence the processing of payments from external payment collectors:
o 0020: FKK_EVENT_0020_CVS (industry-specific)
o 1500: FKK_SAMPLE_1500
o 0110: FKK_CLEARING_PROPOSAL_0110_CVS (customer-specific)
o 0242: FKK_EVENT_0242_CVS (industry-specific)

Transfer of Confirmed Payments

You transfer payments confirmed by external payment collectors using the program
RFK_CVSPAY_CONFIRM. The structure of the payment data transferred in the files must correspond
to the structure predefined by the program. This enables you to summarize payment data reported by
different payment collectors in different files and to process this data in one activity.

The program
o Carries out a transfer posting from the interim account to the bank clearing account for all valid
payment entries in the file
o Calculates the commission due to the external payment collectors for receiving the payments

________________________________________________________________
SAP AG 14.10.2003 23
R/3 System
________________________________________________________________

o Updates the entries for the confirmed payments in table DFKKCVS. It sets the status of the
payments to Confirmed and saves the date of the payment confirmation, the amount of the
commission, and the transfer posting document created for the transfer posting from the interim
account to the bank clearing account.

Calling Back Payments

You can process payments that have been called back and which the external payment collector has
informed you of in the advance information file in returns lots. Note that you also use the payment form
number as selection criterion here. When you post the returns lot, the system sets the status Called Back
for the payment concerned in table DFKKCVS.

To process payments that cannot be called back, you can use event 0061 (customer-specific).

Correcting Payments

You can also process payment corrections that the external payment collector informs you of by file after
items have been called back in Contract Accounts Receivable and Payable. There are two steps to the
processing:
1. In the first step, you group all of the adjustments reported by external payment collectors in a file and
post them in one payment lot as described above. Set the status of the reported payments to
Corrected. When you post the payment lot, the system creates a new entry with the status
Corrected for the corrected payment in table DFKKCVS.
2. Then transfer the payment data from the confirmation file using program
RFKK_CVSPAY_CONFIRM.

If you want to exclude specific payments from a correction, you have to implement the corresponding
criteria for event 0240. Function module FKK_EVENT_0240_CVS (customer-specific) is available as an
example.

Reversal of Payments Reported by External Payment Collectors

SAP provides the sample function module FKK_EVENT_0070_CVS (customer-specific) for reversing
payments.

Monitoring of Payments

You can use report RFKK_CVSPAY_EXAM (menu: Payments -> External Payment Collectors ->
Monitor Payments) to monitor payments reported and confirmed by external payment collectors and the
commission and stamp tax invoiced by the external payment collectors.

You can use this report to:

o Monitor the incoming payments reported by external payment collectors
o Check invoices from external payment collectors for stamp tax and commission
o Check unconfirmed payments after a specific period

________________________________________________________________
24 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

You can use sample function module FKK_SAMPLE_1510 in event 1510 to calculate the commission
and stamp tax due.

Effects on Customizing

Activate the processing of incoming payments by third parties by setting the indicator Payment via
External Payment Collector in the Implementation Guide for Contract Accounts Receivable and
Payable under Basic Functions -> Postings and Documents -> Basic Settings -> Maintain Central
Posting Settings.

You make the system settings for processing of payments collected by external payment collectors in the
Implementation Guide for Contract Accounts Receivable and Payable under Business Transactions ->
Payments -> Processing of Incoming and Outgoing Payments -> External Payment Collectors.

1.1.18 Balance Interest Calculation

Use

Summarization of Interest Documents

Previously, rounding took place individually in balance interest calculation for every interest document
that was created for each interest period. This produced a business partner and a G/L item for every
interest document. You will now be able to group interest items and summarize business partner items
and/or G/L items. Summarization only affects the interest items and not the withholding tax or rounding
items, for example.

This has the following effects on the rounding of interest amounts:

o If you have entered the value 'space' for the Rounding field in posting area 1082, rounding takes
place after all events that influence the creation of business partner items or G/L items have run.
o If you have entered the value '2' for the Rounding field, rounding takes place after all events that
influence the creation of business partner items have run.

In event V089 (sample module VVOZINS_SAMPLE_V089), you can change business partner items for
interest items.

Balance Interest Calculation Run

The responsible company code (OPBUK_KK) will be available as a further selection criterion in the
balance interest calculation run (transaction VVOZ). By restricting to all responsible company codes,
interest is calculated for all insurance objects on whose contract account this responsible company code is
defined.

________________________________________________________________
SAP AG 14.10.2003 25
R/3 System
________________________________________________________________

New Events

The following events will be available in balance interest calculation:

o V089 Sample module VVOZINS_SAMPLE_V089: Change business partner items
o V090 Sample module VVOZINS_SAMPLE_V090: Change balance tables

Effects on Customizing

In the Implementation Guide, you define summarization categories for interest documents ad assign them
to insurance object categories, which you use for balance interest calculation. Choose
Collections/Disbursements -> Business Transactions -> Interest Calculation -> Balance Interest
Calculation.

1.1.19 Insurance Dunning

Use

Dunning Lock on Broker Contract for Assigned Insurance Objects

Previously, you had to set a dunning lock for insurance objects assigned to a broker contract, to prevent a
dunning notice being issues for items due for dunning. There will now be a dunning lock for insurance
objects that are assigned to internal insurance object category Broker contract (20).

If you set a dunning lock, dunning does not take place for items due for dunning on insurance objects that
are assigned to this broker contract. The system produces an appropriate message in the application log
for the dunning program.

Inclusion of Additional Receivables in Insurance Dunning

Settings for additional receivables that are relevant to dunning are will be taken into account for
insurance dunning.

End Date for Dunning Procedure

Previously, the dunning end run set the clearing date for the item due for dunning as the end date for a
dunning procedure. The dunning end run will now use the document date (BLDAT) for an incoming
payment, which leads to clearing for an item due for dunning, as the end date for a dunning procedure. If
multiple items are required to clear an item due for dunning, the dunning end run uses the document date
for the most recent incoming payment that is required for clearing.

________________________________________________________________
26 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

Variant for Collective Dunning Grouping Category

Previously, a collective dunning notice meant that all items for an insurance object, which were due for
dunning, were dunned with one dunning procedure. You will now also be able to define collective
dunning that enable multiple simultaneous dunning procedures for an insurance object. This means that
all items due for dunning, which refer to a collective dunning procedure, are dunned together.

Delete Dunning Proposal Run

If you delete a dunning proposal run (Environment -> Delete Dunning Proposal), the entries in the
dunning history table (FKKMAZO, FKKMAZE) will be deleted synchronously.

Event for Insurance Dunning History

Previously, the header data for the insurance dunning history included the business partner, the insurance
object and the contract balance, when accessed from the contract-related dunning history, and the
business partner, the contract account and the account balance, when accessed from the account-related
dunning history. Event V310 will be available (sample module VKKMA6_SAMPLE_V310), and you
will be able to use it to output more header data in the insurance dunning history.

Event for Dunning Proposal Run

Event V311 (sample module VKKMA1_SAMPLE_V311) will be available in the dunning proposal run.
The event allows you to execute further processing for items and insurance objects or contract accounts
for which a dunning lock is set.

Automatic Clearing for Dunning Procedure with Legal Proceedings Dunning

Level Category (09)

Previously, all items for a business partner or contract account were excluded from automatic clearing, if
the dunning level category 09 (legal proceedings) was reached for multiple insurance objects. Now only
those items from an insurance object in legal proceedings are excluded.

Dunning Program Behavior with Credit

You will be able to use set a flag to control the behavior of the dunning program, if receivables and credit
due for dunning are available on the business partner account.

Dunning Program Behavior with Last Dunning Level

The flag will be taken into account for the individual dunning notice.

Archiving Dunning Notices

Previously, the VVKK_DUNN archiving object was used for insurance-specific dunning notices. The
FI_MKKDUNN archiving object will now be used for dunning notices. Transaction VYM7 was replaced

________________________________________________________________
SAP AG 14.10.2003 27
R/3 System
________________________________________________________________

by transaction FPARM1.

Effects on Customizing

To enable the setting of a dunning lock for broker contracts, choose Collections/Disbursements -> Broker
Collections -> Basic Settings for Broker Collections and set the appropriate flag. To define dunning lock
reasons, choose Collections/Disbursements -> Business Transactions -> Dunning Notices -> Define
Dunning Lock Reasons .

To define rules for additional receivables for insurance dunning, choose Collections/Disbursements ->
Business Transactions -> Additional Receivables -> Define Rules for Additional Receivables.

To permit the execution of multiple dunning procedures in collective dunning for an insurance object,
define a dunning grouping category in the IMG that contains the dunning procedure (MAHNV) as a
separating criterion. The dunning grouping category cannot contain the document number (OPBEL), item
number in document (OPUPK) and repetition item in the document (OPUPW) grouping fields. Define a
dunning variant Assign the dunning grouping category to the dunning variant and leave the Only include
oldest item in dunning (XSIOP_VK) and Only one dunning procedure per contract or account
(XSIMV_VK) flags inactive. Choose Collections/Disbursements -> Business Transactions -> Dunning
Notices -> Define Dunning Grouping Categories and Define Dunning Variants.

Set the Behavior with Credit flag in the Implementation Guide in the dunning procedure, under Business
Transactions -> Dunning Notices -> Configure Dunning Procedure.

The insurance-specific IMG activity for archiving dunning notices was deleted. To define runtimes for
dunning notices, choose Collections/Disbursements -> Business Transactions -> Dunning Notices ->
Archiving.

1.1.20 Dunning Notices

Use

Dunning Activity Setting a Dunning Lock

In the dunning run, you can automatically set a dunning lock for the dunned contract account. You can
use sample function module FKK_SAMPLE_0350_LOCK_VKONT to do this - it writes a dunning lock
reason in the master data. This function module is used to define a dunning activity that you can define in
the dunning procedure. Using function module FKK_SAMPLE_0395_UNLOCK_VKONT, in event
0395, you can delete the dunning lock set by the dunning program if you reverse the dunning notice.
Read the documentation for both function modules.

Event for Reversing Dunning Notices

Event 0395 now has the property Additional Function. This means that you can now call up more than

________________________________________________________________
28 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

one function module. If you have previously defined a customer-specific function module for event 0395,
enter this in Customizing with a counter larger or equal to 1.

With the new function module FKK_SAMPLE_0395_DELETE_CC, in event 0395 you can delete
entries in correspondence containers that were created by a dunning notice and not yet printed. If
necessary, define this function module for event 0395.

Dunning History

On the selection screen you can specify whether you want to display dunning notices that have been
executed or not executed. With this specification, if, for example, you select only dunning notices without
print date, after a dunning activity run you receive a list of the dunning notices not executed successfully.

The fields Dunning Procedure and Dunning Level have been added to the selections.

Determination of the Correspondence Recipient and the Address

You can now determine the recipient and the address for a dunning notification dependent on the dunning
level. You can use the dunning procedure and the dunning level in the correspondence header in the
existing events 0770 and 0773 to do this.

Dunning of Receivables in Payment Orders

Using the new event 0366 you can dun items that are in a payment order. If you want to check how long
the item has been in the payment order, define a customer-specific function module for the existing event
0365.

Dunning Charges if Interest Exists

Using the new indicator Interest before Charges in Customizing for the dunning level, you can make the
calculation of dunning charges dependent on whether interest has been calculated for items due for
dunning. SAP delivers an example implementation for such a calculation with function module
FKK_SPECIALCHARGE_0360.

Restriction of Dunning Charges if Dunning Interest is Charged

If dunning interest (penalty charges) is charged as well as dunning charges, it may be useful to restrict the
amount of the dunning charges. You can implement this restriction in event 0360 using an installation-
specific function module. SAP provides a sample module: FKK_SPECIALCHARGE_0360.

Telephone Dunning

Using function module FKK_SAMPLE_0350_TEL_ITEM you can implement a new dunning activity in
which business partners that have received a dunning notice are included in a telephone list. A clerk then
telephones this business partner, thereby processing the list. You can forward this list created by the
dunning activity run to an external system (for example, call center in mySAP CRM) automatically using
function module FKK_TRANSFER_CALL_LIST_1799 in event 1799 or manually using report
RFKKMADUTLTRANF. The call center then processes the list further.

________________________________________________________________
SAP AG 14.10.2003 29
R/3 System
________________________________________________________________

With the new correspondence type 3003 you can use the correspondence recipient control to enter an
alternative business partner in the telephone list. You can use events 9010, 9012, and 9013 to forward the
entries. SAP delivers function module FKK_CALLLIST_CRM_9010 as an example.

Alternatively, you can use the new transaction Telephone List Dunning in the menu under Periodic
Processing -> For Contract Accounts -> Dunning to clarify the telephone list using more than one
clerk. In this transaction, a clerk can set an entry to completed once he has successfully called the dunned
business partner. To document the communication with the business partner, the clerk can create
customer contacts manually or automatically. In the existing Customizing for customer contacts you can
define contact configurations for the program context SAPLFKKDUTL for this.

In order to be able to give the business partner information, from the detail information for an entry in the
telephone list, the clerk has access to the account balance, the objects linked with the dunning notice, and
a customer- or industry-specific function that you can call in event 9011.

You can change the functions of the clarification worklist via Customizing. In particular, you can define
customer-specific processing statuses and redefine the user commands. SAP delivers function module
FKKDUTL_EVENT_UCOMEXIT_OTHER as an example for the latter.

For actions for entries in the telephone list, the system checks the authorization object F_KKDUTL.

To delete old entries from the table of business partners to be called, you can use report RFKKMADUTL.

If you use the function Correspondence Dunning, you can also use a new dunning activity there
(function module FKK_SAMPLE_0746_TEL_ITEM) (see release information forCorrespondence).
You can process an entry created in thetelephone list using the same tools.

Effects on Customizing

Set the indicator Interest before Charges in the Implementation Guide for Contract Accounts
Receivable and Payable under Basic Functions -> Correspondence -> Configure Dunning
Procedure in the dunning level.

Implement the required dunning activities in the Implementation Guide for Contract Accounts Receivable
and Payable under Basic Functions -> Correspondence -> Configure Dunning Activities.

Define the contact configurations for the program context SAPLFKKDUTL in the Implementation Guide
for Contract Accounts Receivable and Payable under Basic Functions -> Customer Contacts ->
Define Configurations.

You define installation-specific function modules in the Implementation Guide for Contract Accounts
Receivable and Payable under Program Enhancements -> Define Customer-Specific Function
Modules.

________________________________________________________________
30 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

1.1.21 Insurance-Specific Events

Use

The following events will be available:

o V017 - Sample module ISCD_SAMPLE_V017: Customer fields for summarization in the debit entry
o V067 - Sample module VKKSA2_SAMPLE_V067: Determining tax lines in the debit entry
o V068 - Sample module VKKSA2_SAMPLE_V068: Determining documents for payment plan
reversal
o V069 - Sample module VKKSA2_SAMPLE_V069: Determining documents in payment plan item
reversal
o V072 - Sample module ISCD_SAMPLE_V072: Customer-specific checks for subledger transfer
postings
o V073 - Sample module ISCD_SAMPLE_V073: Customer-specific checks for G/L transfer postings

The following events have changed:

Previously Now
1722 V722
1723 V723
1748 V748
1749 V749
1766 V766
1767 V767

1.1.22 New and Changed Events

Use

New Events

0062 ,0102
0103 ,2412
0292 ,2413
0195 ,2414
0196 ,2415

________________________________________________________________
SAP AG 14.10.2003 31
R/3 System
________________________________________________________________

0253 ,24172442
309 ,2443
366 ,2447
510 ,2448
590 ,2450
661 ,2451
699 ,2455
783 ,2456
784 ,2460
791 ,2461
792 ,2465
801 ,2466
802 ,2470
988 ,2471
989 ,2475
990 ,2476
1026 ,2800
1053 ,2801
1070 ,2802
1071 ,2803
1072 ,2815
1073 ,2810
1127 ,4253
1401 ,4254
1728 ,4800
1738 ,4801
1739 ,4805
1772 ,4806
1773 ,4807
1779 ,4808
1780 ,5006
1782 ,5008
1783 ,5058
1810 ,5415
1811 ,5510

________________________________________________________________
32 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

1815 ,5512
1816 ,6056
1820 ,6160
1821 ,6300
1830 ,6301
1831 ,6304
1831 ,6305
1917 ,6350
1918 ,6504
2075 ,6505
2085 ,6506
2092 ,6514
2095 ,6521
2220 ,6522
2225 ,9010
2400 ,9011
2401 ,9012
2402 ,9013
2403 ,9551
2405 ,2409
2406 ,2410
2407 ,2411
2408 ,1215

Deleted Events

1109 ,1766
1111 ,1767
1716 ,2228
1717 ,2500
1722 ,6025
1723 ,6110
1742 ,6503
1743 ,6511
1744 ,6512

________________________________________________________________
SAP AG 14.10.2003 33
R/3 System
________________________________________________________________

1745 ,6513
1748 ,7000
1749 ,7010

Changed Events

Account balance display

o 1205: Sample: Account Balance - Add Data
o 1211: Document: Sample: Account Balance - Transfer of All Selected Line Items before Output
o 1203: Sample: Account Balance-Status Icons/Colors
o 1207: Table of totals (T_TOTALS) is provided, therefore totals
o Payment Run

In events 600, 601, 610, 615, 620, 660, and 680 messages can also be assigned to a problem class from
the application log, which means that you can control the problem class in which a message appears in
the log.

Postings and Documents

o 1117: Document: Display Original Document

Cash Journal
o Event 6110 FI-CA: Create Lot and Check Validity has been deactivated, since customer-specific
data cannot be added to in database table DFKKCJT or, unlike the standard, no change may be made
in the data records.
o In event 6150 FPCJ: Default for Deposit, Difference, and Withdrawal Posting, you can define,
dependent on the process, that is, dependent on whether a deposit, difference, or withdrawal is to be
posted, defaults for the input parameters.
o Event 6160 FPCJ: Amount Check per Clerk for Difference Posting, Deposits, and so on, enables you,
dependent on the process, that is, dependent on whether a deposit, difference or withdrawal is posted,
to carry out a user-specific amount check. The module can be called up in two variants for checks
and in update mode.

Write-Offs
o Event 5008 Check Rule after Industry-Specific Additional Details queries industry-specific
specifications, that is, for example, additional check rules for write-offs. In addition, you can use the
event to exclude open items for a category or according to certain characteristics that you define,
from write-off.
o The interface has been changed for event 5070 Write-Off: Tax Items (Special Features). The
structure FKKCL must not be changed and therefore, the change parameter C_FKKCL was deleted
and the import parameter I_FKKCL added instead.
o The interface has been changed for event 5075 Write-Off: Adjustment of Revenue Items. Structure
FKKCL must not be changed and change parameter I_FKKCL has beenadded instead.

________________________________________________________________
34 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

Effects on Customizing

You define installation-specific function modules in the Implementation Guide for Contract Accounts
Receivable and Payable under Program Enhancements -> Define Customer-Specific Function
Modules .

1.1.23 Main and Subtransactions

Use

You can set the Manual posting permitted flag for the configuration of main and subtransactions in the
Implementation Guide. If the flag was not set, documents that were set manually could not be changed
manually in FS-CD (with regard to dunning procedures or settingg locks, for example). The flag will only
be checked when posting a line item in the ISCD_OP_CHECK_0040 function module. The check in
function module ISCD_OP_CHECK_0040_XPMAN is executed when changing a document.

The change has already been delivered for Release 4.64 with note 538915.

Effects on Customizing

To permit changes to documents if the Manual posting permitted flag is not set, define the
ISCD_OP_CHECK_0040_XPMAN function module as an installation-specific module for event 40. In
the Implementation Guide, choose Collections/Disbursements -> Program Enhancements -> Define
Customer-Specific Function Modules.

1.1.24 Payment Medium Formats: IDoc Interface

Use

Two payment medium formats will be available for electronic data exchange, using the IDoc interface:
o Payment medium format IDOC_PEX uses the basic type PEXR2002 set for payments in SAP FI.
o Payment medium format IDOC uses the basic type PEXFI03.

PEXR2002 and PEXFI03 differ in the following ways:

o PEXFI03 is more compact than PEXR2002, which leads to improved performance.
o Unlike PEXR2002, PEXFI03 has not implemented inbound processing of IDocs.

The basic types are assigned to the DIRDEB and PAYEXT message types.

________________________________________________________________
SAP AG 14.10.2003 35
R/3 System
________________________________________________________________

Effects on Customizing

The IDOC and IDOC_PEX payment medium formats are defined by SAP and do not have to be
maintained. To view the current settings, choose Collections/Disbursements -> Program Enhancements
-> Define Payment Medium Formats.

Make the following settings:

o Make the settings for the distribution of data between application systems. Choose SAP Web
Application Server -> Application Link Enabling (ALE).
o Define an EDI partner number in the EDI partner agreements for the house banks that you
communicate with, using the IDoc interface. Choose Financial Accounting -> Bank Accounting >
Bank Accounts -> Define House Banks.
o Define these EDI partner numbers under partner type B in the partner agreements. Choose SAP
Web Application Server -> Application Link Enabling (ALE) -> Model and Implement Business
Processes -> Set Partner Agreement and Time of Processing -> Maintain Partner Agreement
Manually .

1.1.25 Interface for Transferring IDOCs

Use

The IDoc interface is a standard communication procedure of the R/3 System and is used to exchange
business information with an external system or another R/3 System.

In order to be able to receive and process data from an external billing system (EBS) efficiently and carry
out a mass transfer of data effectively, the IDoc interfaces of Contract Accounts Receivable and Payable
(FI-CA) use the infrastructure of the IDoc technology. With the FI-CA IDoc interfaces, you can:
o Transfer invoice documents and (optional) update data in CO-PA
o Set an archive link to optically archived invoices or archive external documents
From an FI-CA document, the corresponding interface enables you to access the corresponding
original invoice created by the EBS and archived optically.
o Transfer reversals of invoices
o Transfer open items to the EBS to be printed on invoices
This interface enables you to print open items on the invoices created periodically in the EBS.

Using the interfaces provided you can transfer invoices created in an external billing system to FI-CA and
post them there as open items automatically. If required, you can also transfer additional data for the
profitability analysis (CO-PA) such as characteristics, quantities, and revenues of the settlement
documents, and thus make the data available for the contribution margin calculation automatically.

An optimized processing of the usually large data volume created, for example, in an invoicing or

________________________________________________________________
36 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

reversal run, is achieved by scaled parallelization of processing in mass runs where you can process
intervals of IDocs on several application servers in parallel. Via a remote function call the sending system
(for example, EBS) can start the parallel IDoc processing as part of a mass activity in the R/3 System.

The IDocs reach the R/3 system via a port defined for this purpose. The further processing of the IDocs is
defined via special message types. The transaction code assigned to a message type refers to the function
modules that process the IDoc data (for example, posting the invoice documents).

Effects on Customizing

You make the settings required for the IDoc interfaces in the Implementation Guide for Contract
Accounts Receivable and Payable under Data Transfer -> Communication with External Billing
Systems.

1.1.26 Changes to IMG for Contract Accounts Receivable and Payable

Use

The following activities in the Implementation Guide for Contract Accounts Receivable and Payable have
been changed:

Basic Functions
o Postings and Documents
The activities Define Screen Variant for the List Entry of Business Partner Items, Define Screen
Variant for the List Entryof General Ledger Items and DefineSelectable Fields for Screen Variants in
the section Preparations for Processing Screens have beendeleted.
The section Dependencies with the activity Maintain Conditional Locks has been moved from
Business Transactions to Basic Functions.

Business Transctions
o Payments
- Processing of Incoming/Outgoing Payments
The settings for the Cash Desk and the Cash Journal have been separated.
The activity on which the activity Define Screen Variants for Payment Lot is based has been
replaced.
o Creation of Incoming/Outgoing Payments
The activity Define Parameters for Foreign Payment Transactions has been renamed.
o Dunning of Incoming Correspondence
The Customizing of the correspondence dunning levels (see Configure Correspondence Dunning

________________________________________________________________
SAP AG 14.10.2003 37
R/3 System
________________________________________________________________

Procedure) has been adjusted for the creation of reminders before the due date (see Correspondence
Dunning: Reminders). There you can now define whether each dunning level is an optional dunning
level. You can also specify the number of reminder days. The reminder days specify how many days
before the due date of a correspondence a reminder is to be sent.
o Submission of Receivables to Collection Agency
The activities Define Collection Agencies and Define Submission Status have been renamed.
o Transfers
This section has been renamed from Transfer Postings to Transfers.
The activities Define Transfer Reasons and Define Specifications and Default Values for the
Transfer have also been renamed.
o Correspondence
The activity Define Fields for the Selection of Master Data Changes has been renamed.

Integration
o Business Information Warehouse
This section has been moved; the definition of the fields for the extraction can now be made for all
items (open and cleared) in the activity Define Fields for the Extraction of Items.
o Financial Supply Chain Management
The section Biller Direct (previously Customer Portal in the Internet) is now under the section
Integration -> Financial Supply Chain Management.
Basic Settings for the Customer Portal in the Internet has been renamed.
Logging of User Activities has been renamed and the underlying maintenance transaction has been
changed.

Data Transfer

This section has been restructured into subsections:

o Generate Structures for Transferring Data
o Communication with External Billing Systems

Program Enhancements

The function of the activity Define Customer-Specific Function Modules has been improved and
enhanced. This activity now offers you a central access for implementing installation-specific function
modules within the FI-CA event concept. You can now create, copy, edit, and find function modules here
and display their documentation.

1.1.27 New IMG Activities in Contract Accounts Receivable and Payable

________________________________________________________________
38 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

1.1.28 Information System

Use

Open Item List for Closing Operations

Transaction FPO1 (Report RFKKOP03)

o Displays the due date interval also for accounts with reclassifications
o Supports the authorization checks for access by the auditor as part of fulfilling the German
Principles of Data Access and Verifiability of Digital Documentation (GdPdU) (see the
documentation for report RFKKOP03)

Open Item List

In the transaction Open Item List (meun: Periodic Processing -> Evaluation of Open Items) you can
now use the following functions:
o Simulation of a credit assignment in the due date grid
o Supports authorization checks for access by the auditors as part of fulfilling the German Principles
of Data Access and Verifiability of Digital Documentation (GdPdU) (see the documentation for
report RFKKOP04)

Document Journal

In the transaction Document Journal (menu: Periodic Processing -> Closing Preparations) you can
create consecutive document numbers by setting the corresponding indicator. Documents posted in one
company code and fiscal year are then numbered according to their posting date. The program also
supports authorization checks for access by the auditors as part of fulfilling the German Principles of
Data Access and Verifiability of Digital Documentation (GdPdU) (see the documentation for report
RFKKBELJ00)

Document Extracts

In order to comply with the German Principles of Data Access and Verifiability of Digital
Documentation (GdPdU), you have to ensure that the auditor has access to all documents posted within
the last 10 years. To fulfill this requirement, the required document data is saved in tables
DFKKKO_SHORT, DFKKOP_SHORT and DFKKOPK_SHORT. You can use the following
transactions to manage these tables (menu: Periodic Processing -> Data for Government Tax Audit
-> Documents):
o FPDE_EXP - Exports an extract of the abbreviated documents in a file
o FPDE_AEXP - Exports an extract of the abbreviated docments to a file from an archive file

________________________________________________________________
SAP AG 14.10.2003 39
R/3 System
________________________________________________________________

o FPDE_IMP - Imports a file with an extract of the documents in tables DFKKKO_SHORT,

DFKKOP_SHORT, and DFKKOPK_SHORT
The extract can also contain documents from other releases or from external systems.
o FPDE_EXTR - Exports an extract of the short documents (from DFKK*_SHORT) for further
analysis (audig)
o FPDE - Provides an overview of the imported extracts
o FPDE_DEL - Deletes an imported extract

1.1.29 Insurance Invoices

Use

Event V459 (sample module ISISCD_SAMPLE_V459 ) enables you to switch on collective invoicing.
The new E_AVOID_FKKVKP_ACCESS export parameter will be available in the module. If you set the
parameter to X in an installation-specific module, the system no longer accesses the contract account
relationship data (FKKVKP table) to determine the collective invoice partner and the collective invoice
account. The system only determines the collective invoice partner and the collective invoice account
from the insurance object-partner relationship data (DIMAIOBPAR table). This improves system
performance.

Note

Only set the parameter if you determine the collective invoice partner and the collective invoice account
exclusively using the insurance object relationship in your system.

Further notes

The parameter was delivered with note 571672 for Release 4.64.

1.1.30 Insurance Object

Use

________________________________________________________________
40 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

n Accounts for each Insurance Relationship

You will be able to define n contract accounts for each insurance relationship, if you have installed
mySAP Insurance Reinsurance. The function is available if you have installed mySAP Reinsurance and an
entry is available in the AVERS table. The function is valid for external insurance object categories, for
which you have set the n accounts flag in the Implementation Guide.

You can assign your own payment parameters to every contract account.

The following conditions are effective if you define multiple contract accounts for each insurance
relationship:
o The contract accounts must be assigned to different responsible company codes.
o The collection/disbursement parameters are active for the insurance relationship and are valid for all
accounts assigned to the insurance relationship.
o The correspondence parameters are active for the insurance relationship and are valid for all
accounts assigned to the insurance relationship.
o The accounts cannot be created with account creation variants.

The account data is stored in the DIMAIOBPAR_RE table.

Account Creation Variants

Other rules for account creation variants will be available.

o Rule 7: There is just one account with a set account category for every business partner.
o Rule 8: Just one account with a set account category belongs to a relationship between a business
partner and a group of insurance object categories.

Effects on Customizing

To define multiple contract accounts for each insurance relationship, you must set the n accounts flag for
the insurance object category. In the Implementation Guide, choose Collections/Disbursements -> Basic
Functions -> Insurance Object -> Define Insurance Object Categories.

To set account creation variants, choose Collections/Disbursements -> Basic Functions -> Insurance
Object -> Define Account Creation Variants in the Implementation Guide.

1.1.31 Deferral and Installment Plan

________________________________________________________________
SAP AG 14.10.2003 41
R/3 System
________________________________________________________________

Use

Effects on Customizing

1.1.32 Debit Memo Notice Procedure (Direct Debiting) Using BACS (GB)

Use

For the debit memo notification procedure via BACS you can use the following functions in Contract
Accounts Receivable and Payable (FI-CA):
o Provision of the data required for AUDDIS via automated recording of relevant master data changes
o Creation of AUDDIS files for BACS
o Notification of debit memos to the business partner with consideration of deadline specified
o Creation of debit memos and transfers using the corresponding transaction codes (first debit memo,
normal debit memo, new debit memo after bank return, credit memo)

The following enhancements to the contract account have been made:

Via the new field Own Bank Details, you can define the Originator's Identification Number (OIN) and
thereby implicitly fix the house bank to be used for the bank collection.

If the reference number is different to the contract account number, you can enter the reference number in
a customer-defined field.

Recording of master data changes

Changes at business partner and contract account level that are relevant for the bank collection procedure
via BACS, that is, they reflect the collection authorization - such as bank details of the business partner,
account holder, incoming payment method, bank details ID, own bank details, and reference number - are
recorded by the system automatically and are then available for subsequent processes.

Creation of AUDDIS files

Using the master data changes recorded, the system creates the required files in AUDDIS format - you
can use these to report both new and changed collection authorizations via BACS to the banks. The
system creates one file per OIN.

History of collection authorizations

You can display both current and historical collection authorizations and use them for evaluations.

Manual reporting of collection authorizations

________________________________________________________________
42 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

You can select individual collection authorizations that you have already sent by AUDDIS file to send
them again. As soon as you start the AUDDIS run again, it selects these authorizations and creates
records for them in the AUDDIS file(s).

Master data changes via ADDACS file

You can process incoming master data changes in ADDACS format using the new functions for master
data returns. The prerequisite for this is that you have converted the incoming file into the format
specified by SAP and have made the required Customizing settings. For more information, see the release
information for master data.

Debit memo notification

Using a new mass activity you can notify your business partners about bank collections that are about to
take place (see menu Periodic Processing -> For Contract Accounts -> Payment Notifications ->
Create).

In addition to the selection of open items by business partner, contract account, and company code, you
can also define the due date up to which you want to collect open items. The system can determine the
collection date or you can define a collection date for all selected items (for example, for individual case
processing). In the standard case, the earliest possible collection date is 11 days after the creation of the
debit memo. If the due date is further in the future, the collection date is the due date or the deferral date.
For more information, see the section 'Effects on Customizing'.

The system creates one debit memo notification per collection date. The documents covered by a
notification receive an entry in the fields Payment Grouping and Payment Method. If the notification
refers to several documents, these all receive the same values in these fields.

In event 0612 you can influence the creation of debit memo notifications.

You can create correspondence using the new correspondence type 0033.

Display/change debit memo notifications

You can use two new transactions to display and change debit memo notifications (see menu Periodic
Processing -> For Contract Accounts -> Debit Memo Notifications -> Display/Change).

In change mode, you can change the date of a debit memo, specifying a reason, and you can also
deactivate a debit memo notification.

Checks in the payment run

In event 0610, the payment run checks the existence of a valid collection authorization. As standard, a
collection authorization must have been processed by AUDDIS at least three working days before it is
first used.

The payment run also checks the due items for the existence of a debit memo notification. The collection
amount must agree with the amount in the notification and the collection must take place on the date
notified or be within the tolerances defined in Customizing. If the amounts are different, for example, as
the result of a document reversal that has already been notified together with other items, or the deadline
has been exceeded, the items are not paid by the payment run and appear in an exception list.

________________________________________________________________
SAP AG 14.10.2003 43
R/3 System
________________________________________________________________

You can overwrite the date checks carried out by the system in event 0611.

Effects on clearing transactions

Documents for collection that you have notified you business partners about are locked for clearing by
manual or automatic processing. The open items are displayed in the respective dialog transactions, but
have a note about the notification that has already taken place.

Enhancements in the document display and document change

From the document display and document change transactions, you can display the related notification.

Note for SAP Insurance (FS-CD)

Recording Master Data Changes

Changes on insurance object level, which are relevant to the bank collection procedure using BACS,
meaning those that represent a collection authorization - such as the bank details for a business partner,
account holder, incoming payment method, bank details ID, own bank details and reference number - are
automatically recorded by the system and are available to the subsequent processes.

Effects on Customizing

In the Implementation Guide for Contract Accounts Receivable and Payable under Business
Transactions -> Payments -> Creation of Incoming/Outgoing Payments make the following
settiings:

Own bank details

Define Own Bank Details and User Numbers

In this activity, define your own bank details by defining the relevant house bank and account for each
BACS user number (OIN). There can be several user numbers for each house bank/account.

Payment methods

Define Payment Methods

o Define specifications for responsible company code
Select the field Debit Memo after Notification.
o Payment methods in country
Via the field Notification Category define whether a debit memo notification is a prerequisite for
the payment method concerned. If this is the case, set the value 1. For the payment method that you
want to use once a return has occurred, set the value 2. This means that the payment cannot be made
if the collection date defined in the debit memo notification has been exceeded.
o Payment methods in company code

________________________________________________________________
44 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

For BACS payment methods, select the field Own Bank Details from Contract Account. This
means that the collection is made using the BACS user number (OIN) agreed with the business
partner and therefore with the corresponding house bank.

General settings for debit memo notifications

Define Specifications for Debit Memo Notifications in United Kingdom

Here you define the number of days between notification and planned debit memo collection and whether
these are calendar or working days in accordance with a factory calendar that you define. In this activity
you also define the tolerance days for the collection. You can also define that outgoing payments have to
be notified.

Defining events

Define the function modules under Program Enhancements -> Define Customer-Specific Function
Modules :
o To record changes to the contract account that are relevant for the collection procedure, define
function module FKK_PRENOTE_BACS_1025 for event 1025.
o To record changes to the business partner that are relevant for the collection procedure, define
function module FKK_PRENOTE_BACS_1052 for event 1052.
o To activiate the check for the existence of a valid collection authorization in the payment run, define
function module FKK_GB_BACS_0610 in event 0610.
o To collect the debit memo after a return, define event 0292 and make the Customizing settings listed
above.

1.1.33 Interest Calculation

Use

Grouping of Items before Interest Calculation

For item interest calculation, since Release 4.62, you can round items before the interest calculation. If
interest is calculated on several items together, each item is rounded individually. From Release 4.64, you
can group subitems before the interest calculation so that a split item is subject to interest in exactly the
same way as an item that has not been split. With Release 4.71, event 2085 provides you with further,
more extensive options for grouping items before the interest calculation - provided you have set the
indicator Group Subitems before Interest Calculation in the interest key. See also the documentation for
function modules FKK_SAMPLE_2085 and FKK_CONDENSE_2085.

Therefore, for example, if you use different interest rates to calculate interest on receivables and
payables, you can group items in event 2085 before the interest calculation and use the interest rate for
receivables if the amount of the receivables exceeds that of the payables.

________________________________________________________________
SAP AG 14.10.2003 45
R/3 System
________________________________________________________________

Calculate Interest Based on the Net Amount

This function is currently only released for Japan.

You can now also calculate interest on items based on the net amount. The net amount is composed of the
fields Tax Portion in Local Currency of FI-CA (SCTAX) and Tax Amount as Statistical Information
in Document Currency (STTAX). If these fields are empty, you have to calculate the tax amount. In this
case, function module FKK_TAX_LINES_CREATE (determine tax items) is called in event 2095 and
this calculates the net amount.

In posting area 1084 you can define whether the net amount is to be used for the interest calculation.

Calculation of Interest for Clearing Installment Plan Items

This function is currently only released for Japan.

The system can now check installment plan items during clearing and if necessary, calculate interest on
the original items that the system assigns to the cleared installments based on the settings in the clearing
control.

In posting area 1084 you can define whether you want to calculate interest on the original items of
installment plans.

Calculate Days without Interest Supplement

Using a function module processed in event 2092, you can determine the number of days for which you
can charge your customers interest without a supplement to the reference interest rate. In the fields
Exception Type (E_IEXCT) and Exception Value (E_IEXCV) of the function module defined in event
2092, you can ouput the exceptions from the standard interest calculation. The following exceptions are
supported:
o Exception type: I = (Days without supplement to reference interest rate in Italy)
o Exception value: Number of days without supplement

Rounding Calculated Interest

Using a function module processed in event 2075 you can round the result of the interest calculation up or
down.

If you enter function module FKK_ROUND_INT_AMOUNT in event 2075, you can round the interest
calculated using function module FKK_INTEREST_CALC according to the values defined in
Customizing (see section, 'Effects on Customizing').

In contrast, with function module FKK_SAMPLE_ROUND_2040, which is processed in event 2040,

rounding only takes place once the line items for the interest document to be posted have been created
and the interest items have been grouped.

________________________________________________________________
46 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

Effects on Customizing

In the Implementation Guide for Contract Accounts Receivable and Payable under Business
Transactions -> Interest Calculation, make the required settings for the following activities:
- Define Interest Key
- Activate Additional Functions for Interest Calculation (posting area 1084).

Define the customer-specific function modules under Program Enhancements -> Define
Customer-Specific Function Modules and define Rounding Rules for Currencies under Basic
Functions -> Postings and Documents -> Basic Settings.

1.1.34 Job Commander

Use

The maximum number of levels of a process chain has been increased from 10 to 100.

1.1.35 Business Locks

Use

Evaluation of Processing Locks

With the new transaction Evaluate Conditional Locks in the menu under Periodic Processing -> For
Contract Accounts, you can create a list with processing locks. You can select the lock entries by the
parameters Business Partner, Contract Account, Lock Type, Process and Lock Reason. The list is
either a report list or an ALV list, whereby you can sort by business partner or contract account.

1.1.36 Mass Activities

Use

Counters for Mass Activities

You can now add your own counters in an interval to the existing standard counters, such as number of
errors or number of hits.

________________________________________________________________
SAP AG 14.10.2003 47
R/3 System
________________________________________________________________

Preparations

Before you can implement the counter in the mass activities, you have to create it in Customizing (see
below).

Implementation

You implement the counters in the interval module defined for a mass activity. In the interface of the
interval module, define a table T_COUNTER with the structure FKK_MASS_ACT_COUNT. The
structure FKK_MASS_ACT_COUNT consists of two elements that are filled in table T_COUNTER.
countid contains the counter number, value contains the value of the counter. An example
implementation in the interval module has the following form:

DATA: wa_t_counter LIKE LINE OF t_counter.

wa_t_counter-countid = <counter number>.
wa_t_counter-value = <counter value>.
APPEND wa_t_counter TO t_counter.

Application Log: Enhanced Message Management

You can monitor the application logs that are output in mass activities and that are often very extensive in
Enhanced Message Management using the tool EMMA. There you can display both jobs that have
been processed successfully and terminated jobs and batch jobs as well as the business objects processed.

The error messages output in the application logs are categorized and, for example, forwarded to the
clerk responsible for further processing in a workflow or a case worklist. This enables you to:
o Quickly get an overview of the status of a job
o React to errors immediately
o Increase the stability of your system and thereby ensure that errors in mass processing (for example,
creating invoices), do not lead to losses for your company.

You can also use EMMA independently of the application logs to enter cases and forward these, together
with other cases, to the clerk responsible.

The clarification worklist provides the clerk with a standardized business process for solving problem
cases quickly.

Via the status management, you can monitor the current status of the processing of the error. You can
therefore also monitor jobs that are run regularly, such as settlement, invoicing, and online transactions
automatically. This means that the effort required to manually check entries in the application log is no
longer applicable.

Preparation and Analysis of Logs

You can use the application logs to get an overview of the jobs that have been processed and, for
example, read the number of business objects that have been processed successfully or have not been
processed, as well as the number of warnings and error messages.

________________________________________________________________
48 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

You can group error messages that occur according to business objects (for example, contract account) if
required.

Generation of Clarification Cases

The transactions supported by EMMA are categorized by clarification case types. Error messages that
lead to clarification cases are assigned to case categories of the corresponding clarification case types.
This enables you to treat error messages created by different transactions (for example, dialog transaction
and mass activity for the same business process) in the same way, since they are assigned to the same
category.

A clarification case category can be defined dependent on a business object. However, it can also be
independent of business objects. If the same error message is to be output for different business objects,
for example, 'Customizing missing', only one clarification case is opened for all messages affected.

A clarification case generated automatically can be created by a single error message or by a combination
of different error messages. Alternatively, you can define a complex rule for creating clarification cases,
which is based on the attributes of the business object referenced in the error message.

Using the case categories defined in Customizing, the system generates a clarification worklist that is
based on the error messages. The clarification cases are then prioritized and can be assigned to a clerk for
processing in a workflow. In administrator mode you can monitor the status of the clarification processes
and the status of processing.

Processing clarification cases

In the clarification worklist, the attributes of the clarification cases, such as status, priority, and due date
are displayed.

Depending on their authorization profile, clerks can do the following in clarification processing:
o Display clarification cases
o Select clarification cases and place them in processing
o Forward clarification cases to other clerks
o Return clarification cases to the clarification worklist
o Check the status of clarification cases and change their attributes
o Trigger business processes directly
o Define processing notes and reasons for creating a new clarification case

Shortcut keys, that you can define for specific selection criteria for clarification cases in Customizing,
provide the clerks with fast access to the existing clarification cases.

In the menu under Periodic Processing -> Administration of Mass Processing -> Enhanced
Message Management, you can access the transactions required for processing clarification cases:
o Create clarification worklist
o Create clarification case
o Change clarification case

________________________________________________________________
SAP AG 14.10.2003 49
R/3 System
________________________________________________________________

o Display clarification case

Enhancement Options

You can add additional processing screens to clarification case processing. On these screens you can
display additional customer- specific attributes and implement your own functions.

Handling Existing Logs

If you want to process application logs that were created before the introduction of EMMA, you can load
the existing logs using the report REMMAOLDMA.

Effects on Customizing

Counters for Mass Activities

To create your own counters, in the Implementation Guide for Contract Accounts Receivable and
Payable, choose Technical Settings -> Prepare Mass Activities and select the mass activity for which
you want to make the settings. Then proceed as follows.

Standard counter

If you do not want to display the standard counter in the logs, you can hide it. To do this, in the tree
structure, choose General Control and then the tab page Other. If the indicator Display Standard
Counter in the area Standard Counters is not set, the standard counter is not displayed.

Counters
1. In the tree structure, choose Counter Definition.
2. In the field Counter, specify the counter number. The number corresponds to the field countid of
the structure FKK_MASS_ACT_COUNT implemented in the interval module.
3. In the field Counter Type, enter a description of the counter. The description is required for
displaying the counter in the application log.
4. In the field Element, specify a data element. The field names of the data element specified are
required for displaying the counter in the job log.
5. In the field Application Log, specify whether the counter is to be listed in the applicaiton log.
6. In the field Job Log, specify whether the counter is to be displayed in the display of the job logs.

EMMA: Enhanced Message Management

You make the settiings required for generating clarification worklists and for processing the resulting
clarification cases in the Implementation Guide for Contract Accounts Receivable and Payable under
Basic Functions -> Enhanced Message Management.

________________________________________________________________
50 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

1.1.37 Master Data

Use

Master Data Returns for Debit Memo Notification Procedure

If you process debit memos via an institution, such as the British BACS (Bankers Automated Clearing
Service), and the master data of the business partners changes, master data returns may occur in payment
transactions. In such a case, the insitution cannot guarantee correct processing of payments and sends a
file with the changed business partner master data to the company concerned. This file has a specified
format. In the United Kingdom, the ADDACS format is defined for transferring such files via BACS.
The file contains records with change information about the master data, such as the name of the business
partner and his bank details.

This means that you can transfer master data changes reported in this way into a lot using a
format-specific transfer program and then process them. When you post a lot, the master data objects in
the system are changed by direct input.

Master data lots are processed in the same way as returns lots. For any errors that occur during processing
of lot items, the system creates clarification cases that you can then process manually in a clarification
transaction.

In Customizing, for the error reasons that have occurred, you can define which activities are to be
triggered in the system. You can then process these activities when you process the lot.

Effects on Customizing

Maintain the required settings in the Implementation Guide for Contract Accounts Receivable and
Payable under Business Transactions -> Payments -> Reporting of Incorrect Bank Data:
o Configure Error Reasons
o Assign Error Reasons for Institutions
o Define Screen Variants

1.1.38 Processing Payments

Use

Payment Lot: Entry

A technical change over to Table Control has been carried out for entering and processing payment lots.
This has resulted in the following changes:

________________________________________________________________
SAP AG 14.10.2003 51
R/3 System
________________________________________________________________

o The old screen variants are no longer valid.

You have to create new variants. Notes about how the system supports you in this are detailed below.
o The new screen variants permit a larger number of fields.
The fields considered in a variant can have a total length of 250 characters.
o Fields that are not currently required are hidden automatically.
The column Document Number is hidden during the entry transaction. The column Check
Number is also hidden automtacally if the lot being processed is not a check lot.

Notes for Creating Variants

You can create variants as usual in the IMG. You can also use the following functions:
o When a payment lot is to be processed and no variant has been created, the system automatically
generates the variant SAP, which you can use to process payment lots, check lots, and credit card
lots.
o Using report RFKK_VAR_MIGRATE you can migrate old variants. Since the old variants had a 5
digit key, but the new ones a 3 digit key, the keys used previously have also been changed. In the
most simple case, the digits after the first three are simply cut off. The names of the variants remain
the same.

Payment Lots: Subsequent Changes to Specifications

In the payment lot header, the details Company Code, Business Area, Document Type, Posting
Date, Document Date and Value Date were no longer modifiable once the items existed for a lot.

Using the new function Change Specifications you can change the entries in the fields specified. The
new values that you enter are inherited to all of the payment lot items when you save. The new function is
available in the header of the payment lot and is active provided you have not scheduled or carried out
postings.

Payment Lots: Clarification

When you are clarifying payments that are to be distributed to different partners, accounts, or contracts,
you can switch the processing screen so that more selections are displayed per screen. The other detailed
data of the screen is then hidden. For more details, choose the Info Button on the clarification screen.

Payment Lot: Partial Clarification

For partial clarifications, you can now also clarify amounts that exceed the payment amount or have a
different +/- sign to the payment amount.

Example

A customer pays 98 EUR, which consists of 118 EUR residual repayment for a loan, and a 20 EUR credit
memo for negotiating a new insurance contract. For the 118 EUR you have to carry out a transfer posting,
and the credit memo for 20 EUR is to be cleared.

________________________________________________________________
52 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

There are therefore two partial clearings for 118 EUR and -20 EUR to be posted. From Release 4.71, the
system accepts these partial clarification amounts.

Payment Lots: Repayment by Check

You can now repay payments that have been received in error by check. If you enter a repayment method
in clarification processing, for which address data is required, you have to enter this in an additional
dialog box.

Payment Lots: Changing Bank Details for Repayment

A repayment by transfer is normally made using the bank details specified in the payment lot item. If a
repayment is to be made using alternative bank details, or if the bank details are missing in the payment
lot, you can enter the bank data of the recipient in an additional dialog box. To default alternative bank
details, the user requires the authorization with value '013' for the authorization object F_KK_SOND.

Automatic Transfer Posting of Clarification Cases to Incoming Payments

With immediate effect, you can transfer payments from payment or check lots that are in clarification,
and that you cannot assign, after a predefined period using a program and thus remove them from the
clarification worklist. You carry out the transfer posting by specifying a short account assignment to
which a minimum retention period is assigned. The transfer posting program is RFKKUMBKL.

Payment Lots: Transfer Program

The field BFKKZP-CVSCD has been added to the transfer structure BFKKZK.

In the transfer structure BFKKZP, the field BFKKZP-KOINH (name of payer/check issuer/cardholder)
has been extended from 35 characters to 60 characters.

Payment Order Lots: Different Currencies and Exchange Rates

From Release 4.71, in payment order lots, you can also include payment orders in different currencies
and with different exchange rates.

Returns: Outgoing Checks for Returns

You can now cancel issued checks that are returned using returns processing. This means that you can use
all of the returns activities and the events for returns processing.

New Option for Returns: Delete Payment Method in Item

In the items that were cleared by the payment for which the return is being posted, you can use this option
to delete the payment methods entered.

________________________________________________________________
SAP AG 14.10.2003 53
R/3 System
________________________________________________________________

New Option for Returns: Change Payment Method in Item

In event 0292, you can set a new payment method in the item dependent on the existing payment method
in the item.

Payment Lots: Interpretation Rules for Note to Payee

To simplify the Customizing settings for the interpretation rules for the note to payee, you can use
transaction FP_NOTE_TEST to test the note to payee analyses.

Cash Desk

In the cash desk, you can now carry out transfer postings for incoming and outgoing payments.

To carry out a transfer posting, on the initial screen of the cash desk, enter an amount on the tab page
Specifications for Payment and, if you want to post the payment using a payment lot, specify a
payment lot. In the area G/L Account Posting, specify the following:
o The required short account assignment that the system is to use for the transfer posting to a relevant
G/L account
o An explanatory text (posting text)
o An assignment number

Receipt Printing in the Cash Desk

If, in Customizing for the Specifications for the Cash Desk, you have set the indicator Automatic
Printing or Confirm Print, you can create an entry in the correspondence container for cash desk receipts.
The following events are processed:
o 6040: Entry in correspondence container
o 6041: Receipt creation event
o 6042: Receipt printing event

You can now also carry out repeat prints for cash desk receipts - provided you printed a receipt when you
received the payment.

Process Flow

If a customer makes a payment and you have set the indicator Confirm Print in Customizing, when you
call up receipt printing in the cash desk menu under Extras -> Print Receipt, a dialog box appears where
you can enter specifications for the output parameters and the storage mode. You can then configure the
receipt in the print worklist for mass printing or print it immediately.

To trigger a repeat print for a receipt, choose Receipt Printout. In the dialog box that appears, in addition
to the parameters for the output and storage of the receipt, you also have to specify the document number
of the payment document for which the receipt is to be printed. When you then confirm the entry, a
replacement receipt is printed.

________________________________________________________________
54 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

Effects on Customizing

Automatic Transfer Posting of Clarification Cases to Incoming Payments

You define the G/L account for transfer postings in the clarification worklist and the period for
calculating a key date up to which all older, incorrect and unclarified payments are to be posted in the
Implementation Guide for Contract Accounts Receivable and Payable under Business Transactions ->
Payments -> Processing of Incoming/Outgoing Payments -> Define Short Account Assignments
for Transfer Postings.

Interpretation Rules for Note to Payee

You define interpretation rules for the note to payee and test them in the Implementation Guide for
Contract Accounts Receivable and Payable under Business Transactions -> Payments -> Processing
of Incoming/Outgoing Payments.

Cash Desk

You define short account assignments for transfer postings to the cash desk in the Implementation Guide
for Contract Accounts Receivable and Payable under Business Transactions -> Payments ->
Processing of Incoming/Outgoing Payments -> Cash Desk.

1.1.39 Payment Plans

Use

Changes to the ISCD_SCPOS_MAINTAIN Function Module

o The function module will be able to process payment plan items that belong to multiple partners or
insurance objects.
o Error handling in the function module was changed. A ROLLBACK WORK is executed after most
errors in the module. Two new parameters are available for this:
- The I_ERROR_ROLLBACK parameter decides whether a ROLLBAK WORK is executed
within the function module, or whether the caller wants to do this. The parameter is filled with X
as default, meaning that thefunction module executes the ROLLBACK WORK.
- The E_ERROR_INFO parameter delivers information about whether an error occurred and
whether a ROLLBACK WORK was executed, or if this still needs to be done by the caller.
You must use at least one of these parameters when you call up the function module.
o The I_COMMIT_BETW parameter will be available. Set the parameter if you want to reset clearing
and the underlying receivables/payables. The parameter is filled with space as default. To avoid
problems with the data structure do not set the parameter in other business processes.

________________________________________________________________
SAP AG 14.10.2003 55
R/3 System
________________________________________________________________

o The I_NO_MASS parameter will be filled with X as default and therefore leads to individual
postings.
o The I_POST_TO parameter enables you to specify a date up which posting can take place.

1.1.40 Payment Transactions

Use

Payment Program: Posting Exchange Rate Differences

When you post clearing documents, exchange rate differences are always posted. Previously, by setting
the indicator No Exchange Rate Differences, you could explicitly suppress the posting of exchange
rate differences in table TFK042B. You can no longer do this.

This means that in the bank posting, the amount in local currency is always the translation of the foreign
currency amount using the current exchange rate and not the total of local currency amounts of the paid
items.

Payment Program: Agreement of Payment Amounts

You can now make payment amount agreements for open items in any currencies. In transaction Agree
Payment Amounts in the menu under Payments, you can maintain these agreements. There, for each
payment amount agreement, you can specify whether this is to be valid only for clearing online or also
for the payment program. You do this by setting the indicator Evaluation in Payment Run. When you
clear the item with a payment agreement, any differences that arise are posted as exchange rate
differences.

You can create payment amount agreements for payables and for credits. You can also restrict their
validity. In addition, you can create the defined payment amounts for an open item in different currencies.

Payment Program: Find Payments

In the same way as the payment search for incoming payments for a business partner which were posted
via payment lot, you can now search for a specific payment in the payments created by the payment run.
You can use this function, for example, for returns, if you can only see the bank data and the amount, but
cannot determine the business partner because of an incomplete entry in the note to payee.

You access the new function in the menu Payments -> Payment Run under Find Payment.

Payment Media Creation: Format DTAUS0 for Germany

The field Run Date has a value which, depending on the due date of the item cleared, can be in the
future. However, if the payment media is to be created by the bank immediately, you should leave this
field blank. You can also select the corresponding parameter in the variant for scheduling the payment

________________________________________________________________
56 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

media creation. Any existing customer module for payment media event 0021, with which the field was
subsequently deleted, is therefore obsolete.

Payment Media Creation: Parallelization of File Creation

In the definition of the payment media, you can define that the file(s) is/are to be created in parallel. With
Release 4.71, you can also specify a minimum number of payments within a payment group from which
parallel processing is to apply. This means that you can prevent smaller payment runs creating files, each
with very little payment data.

Note

If a payment group has fulfilled the minimum requirement, you still cannot forecast how big the
individual files will be.

The parallelization is currently only released for the German format DTAUS0.

Payment Media Creation: Event 0699 after Completion of All Jobs

From Release 4.71, you can use event 0699 to start your own programs/workflows after the payment
media has been created or to issue additional logs. This event is processed once all payment media jobs
that have been started have been completed.

To get a current overview of the status of the payment media jobs, you can also run report
RFKKPAYMJOBC manually and display the job logs.

Payment Media Creation: Settings for Note to Payee

In the Customizing activity Maintain Note to Payee Type for Payment Media, you can test the settings for
the note to payee, even if you have not yet carried out a payment run.

Payment Media Creation: Printing Replacement Checks in Check Management

Previously, you could only create and print replacement checks for payments in online check printing or
you had to void the original check manually in Check Management and then schedule the payment media
creation again.

You can now initiate check printing for a payment in Check Management via the menu Void -> Print via
Payment Run. Depending on the user settings, the check is either printed in the background or via the
selection screen for payment media creation.

You maintain the user settings on the initial screen for Check Management on the tab page Program
Control.

However, you can only use this function if the payment originates from a payment run and the relevant
payment data has not been reorganized yet.

________________________________________________________________
SAP AG 14.10.2003 57
R/3 System
________________________________________________________________

Payment Media Creation: DME Format for Switzerland

For the Swiss data format DME, you can use transaction type TA836 - payments with IBAN
(International Account Bank Number) (domestic and foreign) in Swiss Francs (CHF) and foreign
currency - immediately.

Effects on Customizing

Payment Program: Agreement of Payment Amounts

If you want to use payment amount agreements, you have to activate the function in Customizing. To do
this, in the Implementation Guide for Contract Accounts Receivable and Payable, choose Basic
Functions -> Postings and Documents -> Basic Settings -> Maintain Central Posting Settiings
and set the indicator Payment Amount Agreement Possible.

Test Note to Payee

To test the settings for the note to payee, in the Implementation Guide for Contract Accounts Receivable
and Payable, in the activity Maintain Note to Payee Type for Payment Media (Business
Transactions -> Payments -> Creation of Incoming/Outgoing Payments), choose the button
Simulation in the note to payee type.

1.1.41 Postings and Documents

Use

Postings and Documents: Swapping the Posting Date

Using the new event 0062, you can now swap the original predefined posting date for another posting
date for each document. This option covers requirements for a dependency of the posting date on the
current date and current time.

If, in event 0062, you use an installation-specific module to assign a new posting date for a document, the
document header and all items are checked with the new date specification. This ensures that you cannot
post in a closed posting period and also that time-dependent posting locks in the contract account or
contract are taken into consideration.

Time-dependent clearing locks for the open items that are to be cleared are not checked. A clearing with
the original posting date that was not invalid due to locks is still not invalid if you subsequently change
the posting date.

If you want to prevent such clearing, you should carry out an individual check in the module which is
created for event 0062 specifically for your installation.

________________________________________________________________
58 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

Postings and Documents: Parallel Number Ranges for Individual Postings

If you frequently carry out individual postings of a specific category online (for example, cash desk or
cash journal), and usually, all postings are carried out with the same document type, the user may have to
wait, because all users access the same number range for the document number assignment.

You can now assign several number ranges for individual postings to a document type and thereby avoid
or reduce these waiting times. For more information see the extended Customizing for document types
under Additional Number Ranges for Individual Processing. On the following screen, call up the
field documentation for the field Number Range.

Postings and Documents: Clearing in Alternative Currency

If open items are cleared in a different currency to the one in which they were posted, the system
automatically translates the amounts. The translation takes place in two steps:
1. Translation of document currency to local currency
2. Translation of local currency to clearing currency

The system uses the current average rate according to the exchange rate table for the translation. If you
have agreed alternative exchange rates or amounts with the customer in question, differences arise from
the translation.

You can now change the translated amounts in the account maintenance (menu: Account ->
Maintain) on the screen Account Maintenance: Process Open Items and thereby avoid differences.

Prerequisites
o The user must have the authorization for activity 15 of authorization object F_KK_SOND.
o On the processing screen, choose the settings such that the posting and clearing amounts are both
gross, and the amounts are displayed in the clearing currency.

Procedure

When you are clearing open items, you can overwrite the translated amount for each line displayed. To
do this, you have to select the button Translated Amounts Modifiable in the area Clearing in
Alternative Currency in the settings.

Alternatively, you can select a group of items and then choose the function key Change Translated
Amounts on the right hand side below the open items. In this case a dialog box appears with the total of
the items in original currency, the internally translated amount, and the input fields for the required
amount or the required translation factors. If you enter an amount here, this is distributed to the selected
items proportionately.

Checks

Amount changes are only permitted within predefined tolerances. The setting in the field Maximum
Exchange Rate Variance in the company code table is decisive. If several company codes are involved,
the lowest tolerance specified is valid.

________________________________________________________________
SAP AG 14.10.2003 59
R/3 System
________________________________________________________________

Postings and Documents: Bundling of Open Items for Clearing

When you are clearing open items manually you can bundle items. After the bundling, instead of the
individual items, there is only one new item for the total amount. The bundling is then retained, even if
you do not carry out clearing. You can therefore retain interim statuses for complicated clearing
processes.

Prerequisites

Bundling is only possible for items that are themselves neither installment plan items nor collective bill
items and that are not included in installment plans or collective bills. Bundled items cannot be bundled
further and an item that is already included in a bundle cannot be simultaneously included in another
bundle.

You cannot bundle payables for which withholding tax is to be deducted or receivables that have been
submitted to a collection agency.

All items that are to be bundled must also have the same business partner, currency, paying company
code, and cash discount percentage rate.

Since the items to be bundled can have different contract account, contract, company code, business area,
division, and due date, the corresponding values are inherited from the item with the largest amount in the
bundled items. As far as the due date is concerned, different behavior may therefore result for dunning
and payments than if the items had not been bundled. The same applies to the cash discount amount
proposed for clearing if the original items have different due dates for cash discount.

To carry out or cancel bundling, you need authorization for activity 16 of the authorization object
F_KK_SOND.

Procedure

In clearing processing you can use two new function keys to carry out bundling or cancel bundling. To
bundle, you have to select the required items first. To cancel bundling, select the bundle or place the
cursor on the item and then choose the relevant button.

Note that the bundling functions are only active if you have selected Gross for displaying the invoice and
clearing amounts in your personal settings.

You can also cancel bundling when you are changing a document by choosing a corresponding button.
You can use the button for the bundled item and the items that have been bundled.

Technical Realization

Bundling results in a new document that contains exactly one statistical item. This statistical item has
exactly the same properties as a collective bill item, and therefore has the statistical indicator S. The same
cleariing functions are available as for collective bills. Therefore, when you are carrying out partial
clearing, the clearing amount can be split over the original items automatically via event 0120.
Alternatively, you can distribute the amount manually.

The original items refer to the bundling. This reference is also realized in the same way as for a collective
bill.

________________________________________________________________
60 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

If you cancel bundling, all references in the original items are deleted, the statistical bundle items are
deleted, and the document header for the bundling is marked as 'Canceled'. Since no new document is
created, '*' appears as the reversal document number.

From the document display for the bundling, you can display the relevant original items via
Environment -> Original Items -> For Bundling. A similar function exists in the account balance
display.

Postings and Documents: Partial Reset of Clearing

When you are partially resetting clearing, you can select the items in which the clearing is to be reset by
reference number or by document number.

Procedure

An additional selection screen appears on the first processing screen. You can use this to decide how to
select:
o By partner/account/contract (only option in older releases)
o By reference number
o By document number

If you decide on reference number or document number, on the following selection screen, there is at
least one line for selection for each reference number or document number. If several company codes,
business areas, divisions, partners, accounts, or contracts are affected in one document, there are more
lines for selection.

Restrictions

You cannot reset clearing per document or per reference number if

o The clearing document was posted in a release before 4.71 and budget billing requests, down
payment requests, or statistical charges requests have been cleared
o Interest on arrears was calculated and posted for clearing

Effect on other functions

You cannot post reversals and returns if the document to be reversed or the payment document contain
items that have already been cleared. Typical examples are payments on account, budget billing
payments, and other down payments that have already been cleared.

You can reset obstructive clearing for returns and for reversals.

In the returns lot, select the field Enhanced Returns Processing. In an online reversal, the obstructive
clearings are listed and you can reset them in the background or online.

In previous releases, you could only reset obstructive clearing completely. From Release 4.71, you can
partially reset clearing and thereby reset only the clearing information in the document/payment
document to be reversed. Clearing is only completely reset if the above-mentioned restrictions apply.

________________________________________________________________
SAP AG 14.10.2003 61
R/3 System
________________________________________________________________

Postings and Documents: Prevent Retroactive Clearing

Via a system setting in the company code, you can prevent clearing where the posting date of the clearing
is before the posting date of one of the items to be cleared. You can do this for manual account
maintenance and automatic clearing. You make the setting when you assign the company code to the
responsible company code. For more details see the field documentation for the field No Retroactive
Clearing.

Postings and Documents: Additional Details for Account Maintenance

In the account maintenance, via an include screen, you can enter additional restrictive selection details or
permit the consideration of items with specific clearing restrictions.

Procedure

In event 0102, process a function module by specifying the program name and the screen number of the
include screen. You must also name another function module with which the additional selection criteria
specified can be returned. For more information, see the documentation of the function module
FKK_SAMPLE_0102.

Postings and Documents: Clearing Processing

You can define an initial sorting for processing open items.

Procedure

Enter a function module for event 0103 that names the fields to be used for sorting.

You can use the functions Filter and Select in combination.

Procedure

Once you have called the function Filter, you can select the new items found using the button Select
Filtered Items and then activate or deactivate them.

Postings and Documents: Mass Reversal

In a mass reversal you can now also reverse documents that already contain cleared items. As for
individual reversal, you can reset obstructive clearing automatically.

Procedure

When you call up the mass reversal, in the details for the reversal posting select the field Enhanced
Reversal Processing .

Postings and Documents: Enter/Display Documents

A technical changeover to Table Control has been made for the document entry and display functions.
This results in the following changes:

________________________________________________________________
62 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

o The old screen variants are no longer valid.

You have to create new variants. Notes about how the system supports you in this action are detailed
below.
o The new screen variants permit a larger number of fields.
The fields considered in a variant can have a total length of 250 characters.
o Fields that are not currently required are hidden automatically.

Notes for creating variants

You can create variants as usual in the IMG. In addition, you can use the following functions:
o If a document is to be processed, and no variant has been created, the system automatically generates
the variant SAP - you can use this variant to process the line items.
o Using report RFKK_VAR_MIGRATE_DOCUMENT you can migrate old variants. Since the old
variants have a 5 digit key, and the new ones a 3 digit key, the keys used up to now have been
changed accordingly. In the most simple case, the digits after the first three have been cut off. The
names of the variants are the same.

The previous SPA/GPA parameters 802 and 803 have been replaced by the new parameters 802TC and
803TC. On the initial screen of the transaction Post Document, you can enter both line layout variants
in the area Line Layout for List Entry. If you select the function Display/Change Settings, a dialog
box appears. Here you can search for variants using input help and then save them, whereby the variants
are saved in the user parameters.

Postings and Documents: Display from Optical Archive

When you display/change an SD document that has been optically archived in the SAP ArchiveLink, you
can display the archived document via the menu: Environment -> Documents from Optical Archive.

Postings and Documents: Changes to Layouts

The information that an item has been included in an installment plan or a collective bill is now in the
document display on the tab page Basic Data and not on the tab page Additional Data as before.

Mass Changes to Documents

The transaction for carrying out mass changes to documents previously consisted of a mass selection of
items and then individual changes, that is, you had to enter the required changes (for example, new due
date, new deferral date, new payment locks) in each item selected individually.

You can now select the items to be changed, enter the changes once, and then copy them into the selected
items.

Procedure

Select the items to be changed. On the top part of the screen, either enter new values (for example, new
due date, new deferral date, payment lock) or select Delete, whereby the corresponding fields are deleted

________________________________________________________________
SAP AG 14.10.2003 63
R/3 System
________________________________________________________________

in the selected items.

You can delete all locks with a specific lock reason or all locks regardless of the lock reason. You can
also add new locks and change existing locks.

You can display simultaneously existing locks in the list by including the new fields SPZAH_LST,
MANSP_LST, SPERZ_LST, CLRLO_LST with the texts Payment Locks, Dunning Locks, Interest
Locks, Clearing Locks. You can doubleclick on these fields or on the lock fields themselves to display
all locks, whereby you can then also edit the locks in the dialog box that appears.

The function Copy New Values then copies the changes into all items selected. Via Save, you can save
the changes to the database.

You can define an initial sorting for processing open items.

Procedure

Enter a function module for event 0103 that names the fields to be used for sorting.

Postings and Documents: Document Transfer

The field BFKKOPK-MWSZKZ has been added to the transfer structure BFKKOPK.

The field BFKKOPK-PS_PSP_PNR_TXT has been added to the transfer structure BFKKOPK. You
can use this field to transfer the WBS elements as text.

The field BFKKOPL-OPUPZ has been added to the transfer structure BFKKOPL.

Postings and Documents: Statement of Gaps in Document Numbers

Since document numbers are assigned cross-company code in Contract Accounts Receivable and
Payable, from the view of an individual company code, document numbers are not necessarily assigned
without gaps. You can use the statement report RFKKGAPFICANUM00 to explain the gaps.

Effects on Customizing

Postings and Documents: Parallel Number Ranges for Individual Postings

You define the additional number ranges in the Implementation Guide for Contract Accounts Receivable
and Payable: Basic Functions -> Postings and Documents -> Document -> Maintain Document
Account Assignments -> Document Types -> Maintain Document Types and Assign Number
Ranges.

Postings and Documents: Enter/Display Documents

You define screen variants for entering, displaying, and changing business partner and G/L items in the
Implementation Guide for Contract Accounts Receivable and Payable: Basic Functions -> Postings
and Documents -> Document -> Prepare Processing Screens:

________________________________________________________________
64 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

o Define Screen Variant for List Entry of Business Partner Item

o Define Screen Variant for List Entry of G/L Item

Postings and Documents: Bundling Open Items

Define the Specifications for Bundling in the Implementation Guide for Contract Accounts Receivable
and Payable under Basic Functions -> Open Item Management.

You can define customer-specific fields for the new bundling item via event 0251. For more information,
see the documentation of the function module FKK_SAMPLE_0151.

Postings and Documents: Prevent Retroactive Clearing

You make the setting to prevent retroactive clearing in the Implementation Guide for Contract Accounts
Receivable and Payable under Basic Functions -> Open Item Management -> Prohibit Retroactive
Clearing.

1.1.42 Prenotification Functions

Use

As of Release 4.71 for Contract Accounts Receivable and Payable (FI-CA), prenotification functions are
available, under Periodic Processing -> For Contract Accounts -> Prenotification. These functions
enable you to:
o Create a prenotification file to your bank
You send a test entry in the amount of zero in order to verify the accuracy of customer account data
and authorizations on the account - before you submit a debit or credit request on the account. In
many cases, a clearing house (such as ACH in the United States or BACS in the United Kingdom)
performs the actual validation and later the credits/debits. You create a prenotification file with
report RFKKPNFC00.
o Display prenotification data
You can display all changes made to data that is relevant for the creation of a prenotification, such as
a change of the account holder's name. This includes data already sent in a file, as well as data not
sent, but which is relevant. In the display transaction, FPPNH, you can view all such data. In the
update transaction, FPPNU, you can additionally select prenotification records and change their
processing status - to, for example, manually include records which have already been sent in a file.
o Process a prenotification return file
If the bank or clearing house is unable to verify a prenotification, it informs you in a returns file.
Using report RFKKPNR00, you import the file and trigger subsequent processing, such as updating
of customer master data.

Prenotification functions are currently for use in the United States and United Kingdom only. For detailed

________________________________________________________________
SAP AG 14.10.2003 65
R/3 System
________________________________________________________________

information, refer to the corresponding Release Notes:

o Payment Transactions and Payment Processing in the United States
o Direct Debiting via BACS (GB)

1.1.43 Print Workbench

Use

In the Print Workbench, in addition to SAPscript, you can also use Smart Forms to create and
maintain application forms. The previous use of SAPscript is not affected by this function enhancement.

Smart Forms have the following advantages over SAPscript:

o More flexible creation of form layout (for example, with tables and templates)
o More efficient creation and maintenance of forms (reduces the time by half)
o Form adjustment without programming knowledge as a result of completely graphical user interface
o Web publishing using a generated XML output
o Performance improvement
o Clear separation between data selection, form preparation, and form logic
o XML-based SAP standard interfaces (XSF, XDF) for external further processing

With Smart Forms you can make simple changes to forms and in the form logic using graphics tools
without programming.

The Print Workbench procures the data for the Smart Forms: As before, you can configure this data
flexibly in the application form and add customer data using user exits.

The Print Workbench transfers the data to the Smart Form via an interface configured in the Smart
Form. When you activate the Smart Form, the system generates an ABAP function module that is called
when you run the Print Workbench.

You create the forms using a graphic form painter and a table painter. The form logic is reflected in a
hierarchy structure with individual nodes; in these nodes you define, for example, global settings, texts,
output tables, or graphics. You make changes using Drag&Drop and Copy&Paste and by selecting
attributes. You can subject both the nodes of the hierarchy structure and the entire form to a check.

You can integrate graphics as part of the form or as a background picture. You can suppress the
background picture for printing.

To use Smart Forms in the Print Workbench, you have to activate the form classes delivered by SAP
for use by Smart Forms. The form classes activated for Smart Forms have a corresponding indicator in
the attributes. If a form class is defined for use by Smart Forms, you can create application forms of the
type Smart Forms based on these.

________________________________________________________________
66 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

1.1.44 Receipt Management (New)

Use

Note

The functions described below have been developed as part of a project for Japan and are currently only
used in Japan.

You can now use the transaction Receipt Management to manage printed rceipts and to repeat the
printout of individual receipts.

Receipt Management

In the transaction Receipt Management in the menu under Payments you can display all receipts
printed for a payment document that correspond to selection criteria that you specify in an overview.

You output the list with the ABAP List Viewer, whereby you can define required layouts to structure the
display to meet your requirements. You can select the layouts in the menu under Output Parameters.

You can display the selected receipts as follows:

o Display individual receipts using the button Execute
In this display variant, the receipts that meet the selection criteria are displayed individually. For
payment documents for which no receipt exists, the program simulates a line with the print
information for the - as yet not printed - receipts. When you subsequently print the receipt from the
report, the program accesses these simulated lines. However, the receipt lines are only simulated if
you have not set the indicator Display Only Receipts on the initial screen of Receipt Management.
o Output without line item display
When you select the button Without Line Item Display, the amounts, net amounts, and tax amounts
are displayed totaled above the company code, the origin of the payment document, the clerk, the
branch, and the cash desk. The ABAP List Viewer is also used here. By selecting a totals item you
can branch to the display of the line items that are considered in the corresponding totals item.

In the display you can use the following functions:

o If you also display line items in the list, you can print receipts for the payment documents displayed.
o If the payment document has already been reversed, you can also reverse receipts that have already
been printed in the list.
o You can navigate to the display of the payment document.
o You can navigate to the transaction for mass printing of receipts.

________________________________________________________________
SAP AG 14.10.2003 67
R/3 System
________________________________________________________________

Mass Printing of Receipts

Using the mass run Receipt Printing (menu: Periodic Processing -> For Contract Accounts), you
can print receipts for payment documents that were posted by the payment run or a payment order lot. If a
payment is posted by the payment run or a payment order lot, the system assigns a receipt number during
clearing. For items that have been cleared by the payment run or a payment order, the system also sets a
status that permits receipt printing or a download to a hand held PC.

Payments from the payment run or a payment order lot that have not been printed or downloaded, and
that correspond to the selection criteria entered in the mass activity, are placed in the correspondence
container for receipt printing.

Using Correspondence Printing (menu: Periodic Processing -> For Contract Accounts ->
Correspondence -> Print), you can print the receipts contained in the correspondence container.

On the tab page General Selections in Receipt Printing, you can restrict the payment docments to be
selected by business partner, contract account, contract, company code of the payment document and/or
the posting date. On the tab page Free Parameters you can restrict further using all the fields of the
table in which the clearing information of the payment document required for printing the receipt is
stored.

You can also start mass receipt printing in simulation mode for test purposes.

Effects on Customizing

If you want to use Receipt Management, make the following settings in the Implementation Guide for
Contract Accounts Receivable and Payable:
o Activate Receipt Management under Basic Functions -> Postings and Documents -> Basic
Settings -> Maintain Central Posting Settings. Set the indicator Receipt Management Used. If
the indicator is set, when you post payments, clearing information required is recorded in the system.
This information is used in Receipt Management to (repeat) print receipts.
o Define the Specifications for Managing Receipts under Business Transactions -> Payments ->
Processing Incoming/Outgoing Payments -> Receipt Management.
o Each printed receipt receives a separate receipt number. The assignment of these numbers is
controlled via a separate number range. Maintain the number range 01 under Business
Transactions -> Payments -> Processing Incoming/Outgoing Payments -> Receipt
Management -> Maintain Number Ranges for Receipt Printing.
o You can also define reasons for the repeat print. You define these under Business Transactions ->
Payments -> Processing of Incoming/Outgoing Payments -> Receipt Management ->
Define Reasons for Repeat Print ).

________________________________________________________________
68 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

1.1.45 New Reports

Use

EMMA: Enhanced Message Management

If you want to process application logs created before the introduction of EMMA, you can load the
existing logs using the report REMMAOLDMA.

Test for Customizing for Interpretation of Note to Payee

Using the report FP_NOTE_TEST, you can test the settings for the note to payee, even if you have not
carried out a payment run yet.

Determination of Missing FI-CA Documents

You can use the report RFKKGAPFICANUM00 to determine missing FI-CA documents in a company
code.

RFKKABS2: Correct Totals Tables

This report is no longer available for correcting totals tables and has therefore been removed from the
menu. In future, use the report Check Totals Tables in the menu under Periodic Processing -> Forward
Postings -> Preparation -> Check Totals Records .

If you want to make the correction in background processing, set the indicator Correction Run.

RFKKABS6: Statment for General Ledger Transfer

This report has been enhanced. You can now use this report to create a statement for postings in the
general ledger.

RFKKGL01: Correct General Ledger Documents

This report is no longer available for correcting general ledger documents and has therefore been
removed from the menu. You can now make corrections using the report General Ledger Reconciliation
in the menu under Periodic Processing -> Forward Postings -> Check -> Check General Ledger
Documents.

If you want to make the correction in background processing, set the indicator Correction Run.

RFKKGL20: Reconciliation to General Ledger

For improved documentation of corrections, this report adjusts the totals records. The transfer of the
corrections is started automatically. In the case of an error, you can transfer the corrections after

________________________________________________________________
SAP AG 14.10.2003 69
R/3 System
________________________________________________________________

processing - similar to report RFKKABS1 - using report RFKKGL00 in correction mode.

RFKKCO20: Value Flow FI-CA -> COPA

For the reconciliation with the profitability analysis (CO and COPA) you can use the report RFKKCO20
(menu: Periodic Processing -> Forward Postings -> Check -> Check CO-PA Documents). The
report carries out a direct reconciliation with CO. Corrections are currently not possible.

1.1.46 Revenue Distribution

Use

Main and Subtransaction for Distribution Posting

Previously, you could only define a main and subtransaction for debit and credit for the distribution
posting to the final recipient. Now, depending on the original main and subtransaction for the distribution
posting, you can derive the same or an alternative main and subtransaction.

Update of the Distribution Posting

If you have added customer-defined fields to the revenue distribution history (table DFKKRDI) and the
summarization structure FKKRDFINAM, previously you had to define a customer function module for
event 5410 to update the distribution history taking into account customer-defined fields. The field update
has been changed so that you no longer have to define event 5410. Your customer module is therefore
obsolete.

Timed Deferral of Revenue Distribution

In event 5415 you can exclude individual documents or line items from the revenue distribution. For
example, you can allow a period of four weeks before you forward a payment received to the final
recipient.

Reversal of Distribution Documents

To prevent an inconsistent status in the distribution history after the reversal of a distribution document,
the reversal of revenue distribution documents is suppressed in Release 4.71.

Archiving of Revenue Distribution

You can archive the revenue distribution entries in table DFKKRDI with the archiving program
RFKKAR33. To delete and reload the data, you can use programs RFKKAR34 and RFKKAR35.

You can display the archived revenue distribution entries in the transaction Revenue Distribution: List of
Documents in the menu under Account -> Additional Information -> Revenue Distribution History

________________________________________________________________
70 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

together with the entries that have not yet been archived.

Revenue Distribution Evaluation

You can evaluate the documents posted and distributed for the final recipient in the transaction Evaluate
Revenue Distribution (menu: Account -> Additional Information). For more information, see the
documentation of the report.

Effects on Customizing

Define the specifications for deriving the main and subtransaction in the Implementation Guide for
Contract Accounts Receivable and Payable under Business Transactions -> Revenue Distribution ->
Define Main and Subtransactions for the Distribution Posting.

If you want to exclude individual documents or line items from the revenue distribution, program a
corresponding installation-specific function module and define this in the Implementation Guide for
Contract Accounts Receivable and Payable under Program Enhancements -> Define
Customer-Specific Function Modules for event 5415.

1.1.47 Reporting Taxes to the Tax Authorities

Use

Extraction of Tax-Relevant Data

On 01.01.2002, the Principles for Data Access and Verifiability of Digital Documentation (GdPdU) came
into force in Germany. These new legal requirements - that exist, for example, in similar form in France
and Switzerland - have been implemented in Contract Accounts Receivable and Payable. This means that
you can now provide the auditors from the tax office with all tax-relevant data as follows:
o Access 1: Immediately in the online system (Z1)
o Access 2: Immediately in the online system or via reports (Z2)
o Access 3: To data media that can be evaluated automatically (Z3)

You can restrict the auditors' access to the saved data to a specific period using an extended authorization
concept.

Since the tax-relevant data cannot be saved permanently in the production system for data access due to
the large quantity of data in Contract Accounts Receivable and Payable, you can extract the data before
archiving and transfer it to a separate system which is exclusively for the government tax audit. Based on
the data held in this system, you can carry out analyses and create extracts that you then provide to the
auditor in a data medium that can be evaluated automatically (access 3).

Due to the mass data processed in Contract Accounts Receivable and Payable, the SAP Data Retention
Tool (DART) cannot be used to create data extracts. For all releases in maintenance, Contract Accounts

________________________________________________________________
SAP AG 14.10.2003 71
R/3 System
________________________________________________________________

Receivable and Payable therefore provides own extractors. In the first step, an FI-CA document extractor
is provided, which you can use to extract also industry- and customer-specific fields and carry out field
transformations in events. In the second step, SAP industry solutions that use Contract Accounts
Receivable and Payable can add additional extractors to this Basis function.

See also the release information for the Information System.

1.1.48 Transferring Business Partner Items

Use

Transferring Open Items to Another Responsible Company Code

The new Transfer post items to other company code transaction (menu: Account; FPU2) will be available.
This will enable you to transfer post open items from multiple accounts for an insurance relationship,
with differing responsible company codes (and possibly with differing currencies), to another account for
this insurance relationship and therefore a responsible company code. During transfer posting, the
selected items are cleared, and many items are posted correspondingly to the target account, in the local
currency for the responsible company code. The target account is determined from the company code that
you specify in the transaction.

To enable you to select more open items in the transaction, you can define your own subscreen in event
989. You can find more information in the document for sample module FSCD_SAMPLE_0989.

Note

The function is available for insurance object categories, for which you have set the n accounts for each
insurance relationship flag. You can set this flag if you have installed SAP Reinsurance.

Effects on Customizing

In the Implementation Guide for Contract Accounts Receivable and Payable, choose Business
Transactions -> Transfers -> Define Transactions for Transferring Items.

To define activities and document types for the Transfer post items to other company code transaction,
choose Business Transactions -> Payments -> Incoming/Outgoing Payment Creation -> Specifications
for Transfer Posting of OIs to Responsible Company Code.

________________________________________________________________
72 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

1.1.49 Payment Transactions and Processing Payments in the USA

Use

Recording Direct Debit Instructions

The system automatically records changes entered on the business partner and contract account levels that
are relevant for the automatic debit procedure of the Automated Clearing House (ACH) - such as the
business partner's bank details, the account holder, the incoming or outgoing payment method, the bank
details ID, or your own bank information. These changes are then made available for subsequent
processes.

Creating ACH Prenotification Files

The system creates prenotification files in ACH format based on the master data changes that have been
recorded. You can specify whether such a change is to be included in the file you create: Either directly
or by means of a Business Add-In, FKK_ID_PRENOTE (see Customizing for Contract Accounts
Receivable and Payable: Business Transactions -> Payments -> Incoming/Outgoing Payment Creation ->
Add-In: Preselection of Mandatory Prenotifications).

Manually Activating the Creation of ACH Prenotification Files

You can select master data changes either individually or automatically on the basis of predefined
selection criteria, and specify that they are to be sent.

You can re-select and re-send master data changes that have already been sent.

History of Direct Debit Instructions

You can choose direct debit instructions - both current and those from the past - for display and
evaluation purposes.

Checks During Payment Runs

If, after you have already sent a prenotification file, you want to block the corresponding account from
being debited for a certain period, you can use event 0610. During event 0610, the payment run checks
that the period you have defined is taken into account.

1.1.50 Workflow

Use

________________________________________________________________
SAP AG 14.10.2003 73
R/3 System
________________________________________________________________

You can use two new workflows for the following activities:
o Write-off
o Entering a request

Check and Approval of Write-Offs

You can now subject the write-off of documents to a check under the multiple control principle with
subsequent release, dependent on the document data. For each write- off, a function module is processed
in event 5512; this function module is installation-specific. It checks whether the write-off has to be
confirmed and released by another clerk in a workflow. If a check is required, the module must return the
required number of checks. You can also output a check reason and additional parameters for role
determination.

If the write-off is accepted, the document is written off and the workflow ended. If the write-off is
rejected, the workflow is stopped.

SAP delivers the sample workflow WS21000102 FICA_WRTOFF for write-offs. You can use role
21000067 for the role resolution.

Activities

Define an installation-specific function module for event 5512.

If line item information is to be output in open item processing or the account balance display for
approval, you can define installation- specific modules for events 0105 and 1205. For example, you can
use the function modules FKK_WF_TEXT_1205 and FKK_WF_TEXT_0105. To execute
application-specific standard modules, call these up directly from the customer-specific module.

Workflow for Creating Requests

You can also subject requests to a check with subsequent approval.

For more information about implementing the workflow, see the section 'Approval via Workflow' in the
release information for Requests.

Effects on Customizing

Define the required check reasons in the Implementation Guide for Contract Accounts Receivable and
Payable under Basic Functions -> Postings and Documents -> Workflows for Postings and
Approvals -> Define Check Reasons.

You define installation-specific function modules in the Implementation Guide for Contract Accounts
Receivable and Payable under program Enhancements -> Define Customer- Specific Function
Modules.

________________________________________________________________
74 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

1.1.51 Write-Offs

Use

New Parallelization Object VKONT

In addition to the parallelization object GPART, you can now use the parallelization object VKONT in
Mass Run: Write-Offs (menu: Periodic Processing -> For Contract Accounts -> Write-Off Run).

Write-Off Reasons

You can now define whether a write-off reason is to apply only to the transaction Write Off Items, only
to the transaction Write Off Mass Run, or for both transactions.

Additional Activities after Write-Off

Event 5040 for additional activities after write-off has been enhanced by the parameters
I_TRANSACTION and I_RFKA1 . For more information, see the documentation of the sample function
module FKK_SAMPLE_5040.

New Events
o Event 5006: In transaction Write Off Items, you can use a new event 5006 to check and default
write-off details.
o Event 5008: In transaction Write Off Items and in the write-off run, you can use the new event
FKK_SAMPLE_5008 for checks with industry- specific check rules. In this event, you can also
apply check rules that are independent of whether the indicator Do Not Apply Write-Off Rules is
set in the transactions named. This event is always processed.

Effects on Customizing

You define the transaction for which a write-off reason is permitted in the Implementation Guide for
Contract Accounts Receivable and Payable under Business Transactions -> Write-Offs -> Define
Write-Off Reasons in the column Validity of Write-Off Reason.

1.2 FS-CM Claims Management

1.2.1 Activity Management (New)

________________________________________________________________
SAP AG 14.10.2003 75
R/3 System
________________________________________________________________

Use

From Release 4.71, you can use Activity Management to process pending tasks in the Claims
Management system.

Pending tasks are processed as follows in the Claims Management system:

o Recognition of pending tasks using the Business Rule Framework (BRF); you use rules in the BRF
to decide which facts will become a pending task (see also the release note for BRF).
o Assignment of pending tasks to claim handlers using SAP Business Workflow (see also the release
note entitled SAP Business Workflow in the Claims Management System)
o Support for the claim handler when processing pending tasks with Activity Management
The system displays the tasks in the section entitled Pending Tasks List. Activity Management leads
you through the individual processing steps required to complete the tasks. When processing a task,
you can suppress underlying abnormal issues (for example, a longer period needs to be scheduled
when checking an annuity request. In this period, the Make annuity request task is not to appear in
the claim handler's inbox).

Enhancements in Tasks Area

The introduction of Activity Management has enhanced the Tasks area as follows:
o In Customizing, assign 0 to n activities to a task. Every activity is suitable for completing a task.
o In Customizing, you define a priority for the task. Your value range is from 0 to 999. The priority is
preset to zero. Lower priority value means a more important task. The priority is only effective for
tasks that are created by the system. Manually created tasks always have a priority of zero.
o You set the activity task category in Customizing. A task category groups multiple tasks from a
certain standpoint (for example, all tasks for authorization, all tasks for invoice verification, and so
on).
The task category is used as a sort and filter criterion in the open tasks list.
o You can define time limits for first submission, start of task and end of task.
o You can define the validity for a task, in days.
o A task can be related to a control predicate (link between task and abnormal issue). A control
predicate is a special Boolean expression that suppresses an abnormal issue, if the resulting task is
already being processed by another clerk.

Displaying Pending Tasks in the Claim

The list of pending tasks contains manually created tasks as well as those created by the system. The
system displays all tasks for the claim subject, sorted according to priority and due date. The more
important tasks can be found at the top of the list. For tasks with the same priority, the ones that have to
be dealt with first are at the top of the list. You can also sort the list according to other criteria, such as the
task category.

________________________________________________________________
76 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

Using Task Management

The following steps are required to complete a task, when using Activity Management:
o Execute activity, if the activity is not assigned to a task
To execute an activity, click on the task in the Executed process step column.
The system navigates to the location of the abnormal issue.
The most recently executed task is marked by a pin in the Selection field and the row being colored
green.
The task can be marked as completed in one of the following ways:
- The system marks as completed those tasks for which you have made Customizing settings so
that they will be marked as completed when navigating to the abnormal issue.
- You can mark all other tasks as completed manually.
If activities are assigned to a task, the task can only be marked as completed after the activity has
been executed.
o Execute activity (if one or more activities are assigned to the task)
If activities are assigned to a task, the Execute activity icon is available in change mode. This icon
refers to the last task executed.
If you choose the Execute activity icon, the system displays all activities that are assigned to this
task. You can then execute the desired activity.
If an alternative navigation target is available for the combination of task and activity, the system
navigates to the alternative navigation target.
The system enters the activity used in the Activity field.
You can then mark the task as completed, using the methods described above.
o Mark task as executed
In change mode, the Mark task as executed icon is available for the last task executed. If activities
are available for a task, you have to execute an activity before the icon is available.
You can mark the task as completed manually.

The following additional functions are available for tasks:

o Note to clerk
In change mode, the Note to clerk icon is available for the last task executed. In the subsequent
window, you can see:
- Explanation component (cause of abnormal issue is normally determined dynamically from the
rule tree)
- Working note (note entered in Customizing about processing the task, generally required by
inexperienced clerks).
o Create task
In change mode, the Create task icon is available.

________________________________________________________________
SAP AG 14.10.2003 77
R/3 System
________________________________________________________________

If you click on this icon, the system offers all tasks that you can create manually, in the Task field in
the subsequent dialog box. Choose a task and confirm with Enter. The system transfers the task to
the list of open tasks, as long as it not already in that list.
You can also create a task on the Activities screen in the New Entry section.

The following standard functions are available in the open tasks list:
o Sort ascending
o Sort descending
o Set filter
o Views
o Layout settings
o Close task management

Effects on Customizing
o The following fields have been added to the Define Tasks and Log Entries IMG activity:
- Task category
- Priority
- First submission time limit
- Task start time limit
- Task end time limit
- Validity
o Customizing for a control predicate takes place in the FS-CM Task Menu: Claims Management
screen (transaction ICLWM).
Choose menu option Customizing -> Rules. On the subsequent screen, click on the Expression
button.
You can create, edit or delete and expression. A control predicate is an expression of the
implementing class Control predicate. A control predicate is assigned to just one abnormal issue and
one task.

1.2.2 Activity Management: Profile and Explanation Component (New)

Short text

Activity Management: Profile and Explanation Component (New)

Use

________________________________________________________________
78 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

Activity Management has the following accompanying components:

Profile

Using this Profile component you can notify the claim of predefined facts (predicates) that can be
described by a Boolean expression.

You define predicates in the Business Rule Framework (BRF). A predicate always refers to exactly one
claim subobject.

When a predicate is calculated during rule calculation, the truth content is transferred to the profile
manager.
o If the predicate is true, it is added to the profile and displayed on the Profile screen in claims
processing, provided it was not already in the profile.
o If the predicate is false, it is removed, provided it already existed.

You can display the profile at both claim and subclaim level in claims processing. Add screens ICLC38
or ICLC39 (or screens that contain the views ICLC37 /or ICLC35) to the screen sequence for the claim
overview (screen sequence CL01) or to the screen sequence for the general subclaim (screen sequence
SUBG).

Explanation component

Using the explanation component you can present all the BRF objects calculated in the claim together
with their respective dependent BRF objects that have been evaluated. The presentation is in the form of a
hierarchy with the result and an explanatory text. Depending on the truth content, the text with Boolean
BRF objects has different features.

In the case of an expression, you can specify that it should contribute to the explanation component. If a
BRF object with this setting is evaluated in the claim, the results of lower-level objects are also collected
in the explanation component. This is done regardless of whether the flag is set for these lower-level
objects.

It is sufficient to consider any abnormal issues involved (such as control predicates).

1.2.3 Appraisal (New)

Short text

Appraisal (New)

Use

________________________________________________________________
SAP AG 14.10.2003 79
R/3 System
________________________________________________________________

As of Release 4.71 you can enter and process appraisal orders and appraisal receipts in the lines of health
insurance and care insurance.

You can create several appraisal orders and receipts for a prescription or a request.

You can also reverse (cancel) appraisal orders as well as appraisal receipts.

Appraisal order

You can enter the following data for an appraisal order:

o External reference (such as reference number)
o Type of appraisal
o Appraisal reason
o Appraisal (business partner)
o Alternative recipient (business partner)
o Set Order Date
o Resubmission date

The Issued on date and the Send Date of the appraisal order are filled by the system.

If you enter a resubmission date, the system creates a related task for checking receipt of the appraisal.

The following other functions are available:

o Free text for comments
o Use of document proposals
o Display and storage of archived documents
o Option of integrating structured facts capture

You can explicitly set an appraisal order to Commissioned, whereby the document proposals for the
appraisal order are placed in mass printing and the Commissioned status is set.

Once an appraisal has the status of Commissioned, you can no longer change most of the input fields.

Appraisal receipt

You can enter the following data for an appraisal order:

o External reference (such as reference number)
o Type of appraisal
o Appraisal reason
o Appraisal (business partner)
o Date Appraisal Made

________________________________________________________________
80 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

o Date issued
o Date received
o The Receipt via DME flag is set by the system if the appraisal receipt was created via direct input.

The following other functions are available:

o Free text for comments
o Display and storage of archived documents
o Entry of diagnoses
o Option of integrating structured facts capture

You can assign an appraisal receipt to the triggering appraisal order. The values of the appraisal order
regarding external reference, appraisal type, appraisal reason, and appraiser are transferred to the
appraisal receipt providing that no other opposing value has been entered.

Effects on Customizing

Perform the following IMG activities for appraisal types:

o In IMG activity Define Types of Procurement Document Category, define all possible appraisal
types.
o In IMG activity Configure Internal Claim Types assign the permitted appraisal types to an internal
claim type. Select the Subclaim button. Under Permitted Coverage Type -> Permitted Procurement
Document Category -> Permitted Type, assign the permitted appraisal types.

Perform the following IMG activities for appraisal reasons:

o In IMG activity Define Reasons for Creation, define all possible appraisal reasons.
o In IMG activity Configure Internal Claim Types assign the permitted appraisal reasons to an internal
claim type. Select the Subclaim button. Under Permitted Coverage Type -> Permitted Procurement
Document Category -> Permitted Reason, assign the permitted appraisal reasons.

To enable you to use the resubmission date with an appraisal order, perform IMG activity Appraisal:
Define Resubmission Date.
o

1.2.4 Incoming Documents in the Claims Management System (New)

Use

From Release 4.71, you can use the Archive Link to store incoming documents in an archive, and then
assign them to a claim or a subobject (claim, subclaim, damaged object, and so on).

________________________________________________________________
SAP AG 14.10.2003 81
R/3 System
________________________________________________________________

You can store and assign documents in one of the following ways:
o You can use the navigation tree to store assign documents, for the Claim and Subclaim subobject
categories only:
In the context menu for the subobject, select the Store document entry.
In the subsequent Store document dialog box, you can store documents for the following objects:
- For the current subobject
- For all subordinate subobjects in the hierarchy
- For cross-subclaim subobject categories (such as participants)
If you click on the Store document icon on the Archived documents screen, this takes you back to the
Store document screen.
o Documents button
The Documents button is available in the details for the claim item, appraisal order and for invoice
processing. This allows you to call up a window for document storage. You can only store
documents for the current subobject here.
o Direct Input
You can use the Direct Input interface to assign incoming documents to a claim or subobject. You
can find more information in the release note for Direct Input.

You have to specify the folder and the name for the document to be stored on the local hard disk in the
respective windows.

In the Direct Input interface, you can either specify an access path for the document, or an existing
archive ID.

Irrespective of the processing type, the system also requires information about the business type of the
document (such as invoice, appraisal, accident sketch). You can also specify a short text, to enable more
accurate identification of the stored document.

You are able to get an overview of already assigned documents as follows:

o On claim header level, the Documents tab page provides a list of documents that were assigned
directly to the claim, or to an associated subobject.
o On subclaim level, the Archived Documents tab page provides a list of documents that were assigned
to the relevant subclaim, or to a subobject within this subclaim. Assignments to cross-subclaim
subobjects (such as participants) are also displayed.
o You can use the Documents button to get an overview of documents for the current subobject. The
color of the button denotes whether documents have already been assigned to the subobject. If
documents have already been assigned to the subobject, the button is green.
In display mode, the button is only displayed if documents have already been assigned.

In all variants, a double click allows you to display documents, create more assignments and delete
existing assignments.

If you store or assign incoming documents, the BRF event AL001 is triggered. If this event is triggered,

________________________________________________________________
82 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

the system logs the document assignment as standard in the activities log.

If an error occurs during archiving or document assignment, the BRF event ALUNDO is triggered. This
can have an effect on previously executed actions.

If you delete a document assignment, the BRF event ALDEL is triggered. You can define actions that are
to be executed.

1.2.5 Benefit Type Trees (New)

Use

From Release 4.71, the permitted benefit types are grouped in the new benefit type tree entity. Previously,
the permitted benefit types were stored in the permitted coverage types for an internal claim type.

The benefit type tree contains the hierarchy for permitted benefit types.

The new benefit type tree entity has the following advantages:
o You can maintain and transport the permitted benefit types, irrespective of the internal claim type
o Every benefit type tree has its own versioning
o You can use a benefit type tree in multiple internal claim types
o You have more flexibility, thanks to the use of various internal claim types, which contain the same
permitted benefit types.

Effects on Existing Data

Changes to Data Maintenance

o Customizing data:
The following data for permitted benefit types is now maintained with the benefit type tree (no
longer in the TICL056, TICL083, TICL076 and TICL057 tables, but in the tables TICL162 to
TICL165):
- Assigned limits and deductibles
- Permitted payment reason groups
- Permitted object types
o Data for Claims Management system
The version for the internal claim type is saved in the claim header, or in the respective subclaim.
You can find out the version of the actual claim by following the menu path: Edit -> Further

________________________________________________________________
SAP AG 14.10.2003 83
R/3 System
________________________________________________________________

processing -> Product setting.

Required Activities

The data for earlier releases remains in the TICL056, TICL083, TICL076 and TICL057 tables. From
Release 4.71, this data is no longer updated by the Customizing transactions. Nor is it used by the Claims
Management system.

Therefore, after upgrading to 4.71, you must copy the data to the new Customizing tables and update the
claim tables, before you can proceed with claim processing.

Execute the following steps:

o Customizing data:
Using the RICL_TICL056_162_UPGRADE_471 report, copy the data from the old Customizing
tables to the new ones.
Generate the keys for a benefit type tree as follows:
- The first four characters correspond to the key for the internal claim type. If the key for the
internal claim type has less than four characters, the key for the benefit type tree then contains
corresponding spaces.
- The last four characters correspond to the key for the coverage type (or space, if the benefit type
tree is valid for the claim header).
o Data for Claims Management system
Save the correct versions of the benefit type trees, using the RICL_UPG_CLAIMS_BENTREE_471
in the claim and subclaim tables.

Effects on Customizing

You maintain the benefit type trees in the Configure Benefit Type Trees IMG activity.

In the Configure Internal Claim Types IMG activity, you assign a benefit type tree to an internal claim
type, on subclaim level (in the detail view).

The following rules have to be adhered to:

o If the benefit types for the benefit type tree are to be valid for just one permitted coverage type,
assign the benefit type tree to this permitted coverage type.
o If the benefit types for the benefit type tree are to be valid for the claim header, on a cross-coverage
type basis, create an entry without specifying a coverage type. Leave the coverage type field empty,
and define a benefit type tree for this entry. This is valid for the claim header.

If you create a subclaim or the claim header in the Claims Management system, the system determines
the assigned benefit type tree. The system determines the valid generation and version for the benefit type
tree in the same way as for the policy product and the internal claim type.

________________________________________________________________
84 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

1.2.6 Benefit Types (Changed)

Short text

Benefit Types (Changed)

Use

As from Release 4.71 you can use a benefit type either just cross-subclaim, or just for a certain subclaim
(or claim header). Select the Cross-Subclaim checkbox in IMG activity Define Benefit Types.

Using this restriction you can determine whether a payment item

o Comes directly from a certain subclaim (or claim header), or
o Whether it was created by the system when a cross-subclaim item was split

As from Release 4.71 the permitted benefit types are grouped in the benefit type tree in a hierarchy (see
Release Note on Benefit Type Trees). Previously, the permitted benefit types were stored in the permitted
coverage types for an internal claim type.

When you configure benefit type trees, you must ensure that you use the correct benefit types, that is to
say
o Benefit types in which the Cross-Subclaim checkbox is not selected can only be used for benefit type
trees in which the For Subclaim checkbox is selected. Set this in the detail view of the version of the
benefit type tree.
This means that you can only use benefit types of this benefit tree for a specific subclaim or claim
header.
o Benefit types in which the Cross-Subclaim checkbox is selected can only be used for benefit type
trees in which the For Subclaim checkbox is not selected.
This means that benefit types of this benefit type tree can only be used cross-subclaim.

Effects on Customizing
o In IMG activity Define Benefit types, select the Cross-Subclaim checkbox.
o In IMG activity Configure Benefit Type Trees, define the permitted benefit types for each benefit
type tree, and arrange the benefit types hierarchically.
o In IMG activity Configure Internal Claim Types, assign a benefit type tree to an internal claim type
at subclaim level.

________________________________________________________________
SAP AG 14.10.2003 85
R/3 System
________________________________________________________________

1.2.7 Business Rule Framework (New)

Use

The Business Rule Framework (BRF) completely replaces the Business Rule Tool (BRT). There will be
no support for the BRT from Release 4.71. Existing BRT code will be removed.

The usage of the BRF is obligatory for the Claims Management system.

The BRF supports the previous BRT functionality, and enhances it in the following ways_
o Application-independence
o Modification-free extensibility

You can use the BRF rule tool to define and implement technical and business process-oriented sets of
rules. The Claims Management system uses the BRF exclusively as a business process-oriented set of
rules.

The BRF contains the following central objects:

o Events
o Rules
o Expressions
o Actions

Events form the entry point for the BRF. SAP delivers predefined events. You can assign any number of
rules to every event, and a rule normally consists of a Boolean expression and an action. If the event is
triggered, the expression is calculated. If the expression delivers the result TRUE, the action is executed.

In addition to replacing the BRT, the BRF has the following new functions:
o BRF Network Graphics
A BRF network graphic represents the relationships between the BRF objects in graphical form. The
dependencies of events and their expressions and actions are displayed, thus making rule
administration easier.
The events form the starting point. The associated expressions and actions are displayed in a tree.
o Where-Used List for BRF Objects
The where-used list enables those objects in the BRF and in an application class, which have a
certain expression or action, to be determined and listed. This allows you to see whether a specified
expression or action is used by another BRF object, or by the corresponding application class.
o BRF Rule Groups
You can use rule groups to group rules that belong to the same business process. Rule groups are
simple units for managing rules.
o BRF Workbench

________________________________________________________________
86 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

You can also create, display and change BRF objects in a display similar to the ABAP Workbench
(BRF Workbench mode). Call up the BRF transaction.
The following functionalities are available in the BRF Workbench:
- Create, display and change all BRF objects for a specified application class
- Navigation from BRF objects to Workbench objects for example, from an action (BRF object)
to a class (Workbench object)
- Navigation from a BRF object (such as an event) to another BRF object (such as an expression)
- Backwards navigation, similar to Workbench objects
- Navigation to BRF network graphics
- Navigation from one application class to another
- Where-used list for BRF objects
o BRF Object Overview
In an overview, you can display all BRF objects that belong to an application class and an
implementing class.
Choose the menu option Extras -> Overview from the BRF initial screen.
On the subsequent screen, enter the application class and the implementing class, and click on the
Execute icon.
You have the following options on the next screen:
- You can print the BRF objects
- You can export the BRF objects (and generate an Excel file, for example)

Effects on Customizing

The IMG has the following activities for the BRF:

o Enhance Events
o Enhance Data Sources
o Define Expressions
o Define Actions

Network Graphics

You require a graphical profile for the network graphics, which is used as the basis for creating the
graphics. The profile defines the form of the nodes, the types of links, the colors, and so on.

Call up transaction CNG4. Select the following entry:

o Group: BRF0
o Name: Default
o Index: 0

________________________________________________________________
SAP AG 14.10.2003 87
R/3 System
________________________________________________________________

Click on the Detail View icon and make the desired settings.

In the M_TBRF500 maintenance view, you can create and assign technical profiles for certain users.

1.2.8 Processing Collective Invoices (New)

Use

As of Release 4.71 you can also process collective invoices in addition to individual invoices. A
collective invoice is assigned to one or several individual invoices, and marked by an own collective
invoice header.

The main functions available are as follows:

o On the Invoice Overview screen you see a list of assigned individual invoices with the relevant
invoice items
o You can navigate to processing of the individual invoices
o On the initial screen you can search for a collective invoice using the F4 help. A search mask is
available.
o In collective invoice processing you can call a dialog window in which you can perform mass entry
of individual invoices.

Other release notes on Invoices:

o Invoice Entry/Invoice Processing
o Reimbursement of Simple Invoices

Effects on Customizing

If you want to use own collective invoice types other than those prescribed by SAP, you must perform
IMG activity Enhance Collective Invoice Types .

1.2.9 Integration with BW (Changed)

Short text

________________________________________________________________
88 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

Integration with BW (Changed)

Use

As from Release 4.71, the following additional transaction data extractors are available for integration
with the Business Information Warehouse (BW) system. They mainly deliver specific information on
health insurance to the BW system:
o 0ISCM_ACTIVITY_01
Enables extraction of data fields in the Activities application table (ICLACTIVITY), which contains
information on the claim activities.
To enable calculation of lead times with activities (history times), historicized activity data
(ICSACTIVITY) is extracted to the BW system with this extractor.
o 0ISCM_DIAGNOSIS_01
Enables extraction of data fields in the Diagnoses Made application table (ICLDIAGNOSIS), which
contains information on the diagnosis.
o 0ISCM_PROCURE_01
Enables extraction of data fields in the Procurement application table (ICLPROCURE), which
contains information on the claim item groupings.
The claim item groupings are a technical construction with attributes for procurement documents
(such as request, prescription, approval, cost estimate, invoice).

The required master data for these transaction data extractors is also provided as master data extractors in
the form of texts and attributes.

1.2.10 (Statutory) Care Insurance (New)

Short text

(Statutory) Care Insurance (New)

Use

As of Release 4.71 the Statutory Care Insurance line is supported in the Claims Management system.

The following functionalities are available for statutory care insurance:

o You can create a request for home health care for all permitted coverage types in the form of a
procurement document. The system checks the existing approvals during the creation process. There
may only be one approval for each request. The only incidence in which more than one approval is

________________________________________________________________
SAP AG 14.10.2003 89
R/3 System
________________________________________________________________

permitted, is if reversed approvals exist.

o You can cancel (reverse) a request.
o You can reject a request.
o You can transfer the data from a request to the approval.
o You can check existing care levels by comparing data on business partners. The only area in which
this is not possible is with coverage type Ongoing Care.
You can also create a new care level.
o You can create an approval for home health care for all permitted coverage types. Data is changed if
the request is locked.
o You can cancel (reverse) an approval.
o You can reject an approval.
o You can approve an approval.
o At subclaim level you can view all previous claims of the relevant claimant. You can restrict the
display to one or several coverage types.
o The system displays the relevant status information at the level of the relevant procurement
document.

Effects on Data Transfer

The system stores the data of the request or the approval in the ICLPROCURE table.

Exceptions:
o The data from the grid controls is stored in the ICLITEM table.
o The data from structured facts capture is stored in the ICLLOSSDES table.
o The data on the occurrences of claim participants is stored in the ICLPARTOCC table.

Effects on Customizing

Perform the required IMG activities for use of care insurance. In particular, these are:
o Define Coverage Types
o Define Reasons for Creating a Subclaim
o Configure Internal Claim Types
o Configure Benefit Type Trees

________________________________________________________________
90 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

1.2.11 Claim Bundle (Changed)

Short text

Claim Bundle (Changed)

Use

From Release 4.71, the following new functionalities are available for claim bundles:
o In addition to standard claim bundle types (such as cumulative claim, loss aggregate), you can also
manage collective invoices (see Release Note on Collective Invoices).
o You can create subrogation cases for claim bundles on the Recovery screen.
o Activity Management is also used in the claim bundle component (see Release Note on Activity
Management. On the Activities screen the system also shows pending tasks and their status.
o You can create a claim when you are processing a claim bundle. To do so, select the Create Claim
button on the Assigned Claims screen. The new claim is assigned to the number of the relevant claim
bundle. You can only create a claim in change mode, since beforehand no claim bundle number
exists.
o When you are processing a claim bundle, the following new menu entries are available under
Utilities:
- Settings
Similarly to claims processing, you can control the behavior of claim bundle processing after
saving.
- Display Task List
o You can define rules for claims bundles in the sense of the Business Rule Framework (BRF). To do
so, on the claim bundle initial screen (transaction ICLEWM) choose menu path Customizing ->
Rules.
You can find more information on the BRF in the Release Note for BRF.
o Depending on the claim bundle type you can assign authorizations for processing claim bundles. You
do so in role maintenance (transaction PFCG).
o The following changes have been made in Customizing of the claim bundle:
- In IMG activity Define Claim Bundle Types you can define a value request for setting a claim
bundle status.
- In IMG activity Define Claim Bundle Types you can define a company code.
- You can specify claim bundle types for each transaction code.
- You can enhance collective invoice types.
o As of Release 4.71 you can maintain claim bundles in direct input. There is no dialog in this
maintenance.

________________________________________________________________
SAP AG 14.10.2003 91
R/3 System
________________________________________________________________

For further information on direct input, see Transfer of Data from Legacy or Operational Systems in
the application help for the Claims Management system.

Effects on Customizing

The following changes have been made in Customizing of the claim bundle:
o In IMG activity Define Claim Bundle Types you can define a value request for setting the claim
bundle status.
o In IMG activity Define Claim Bundle Types you can define a company code.
o You can specify claim bundle types for each transaction code.
o You can enhance collective invoice types.

1.2.12 Customizing Internal Claim Types (Changed)

Use

From Release 4.71, you no longer maintain the permitted benefit types in the Configure Internal Claim
Types IMG activity, but in the new Configure Benefit Type Trees IMG activity (see the release note on
benefit type trees).

1.2.13 Compensation Calculation (BAdI) (Changed)

Short text

Compensation Calculation (BAdI) (Changed)

Use

Note:

This release note is only relevant if you implemented own enhancements for the compensation
calculation in Release 4.64 and want to upgrade to Release 4.71.

As of Release 4.71 the following interfaces have changed:

o IF_EX_ICL_CCALC_BENTYPE_EV of BAdI Application Type of Limits and Deductibles in
Compensation Calculation (ICL_CCALC_BENTYPE_EV)
o IF_EX_ICL_CLAIM_OTHER_READ of BAdI Search and Read Method for Reading Data from
Claims (ICL_CLAIM_OTHER_READ)

________________________________________________________________
92 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

The functionality of the interfaces has not changed. However, the input and output parameters have been
regrouped. In addition, the categories of parameters have changed to prevent major problems in later
releases. This means that the changes are compatible with future releases of the Claims Management
system.

After the upgrade to 4.71 your BAdI implementations will contain syntax errors, that is to say the Claims
Management system will not run. You should therefore perform the release upgrade on your development
system first, and update the BAdI implementations there. You can use the BAdI implementations
supplied by SAP as a template for updating your BAdI implementations.

1.2.14 Correspondence (Changed)

Use

From Release 4.71, the following new correspondence functionalities are available.

Differences Log

You can create a differences log for a procurement document category (such as authorization, invoice).
The differences log has its own application form, which can be output using the Print Workbench.

Authorization and invoice processing contain the Differences Log tab page, on which you can generate
the differences log.

For other procurement document categories, you have to create a new screen for the differences log in
BDT Customizing. You can use the screens for authorization (ICLC28) and invoice processing (ICLH27)
as templates.

Free Text Entry for Correspondence

SAP delivers fixed form classes, which form the basis for application forms (a claim document in this
case). The form levels, which you can use as free text levels in an application form, are already defined in
these form classes. Free text levels are the items in a form, for which a sample text module is output as a
free text module, meaning that the user can add free text here.

In claim processing, mark the relevant document (such as the claim opened letter) in the document
proposal list, and select print preview for the document. In the subsequent dialog box, you can assign a
sample text module for every defined placeholder, and then change its text. This text is then saved as your
own free text module.

You can use the ICL_FREETEXT form as an example for free text entry. This consists of a form header
(logo, date and location, address, subject line and introductory sentence) and a blank main section in
which you can place the free text.

________________________________________________________________
SAP AG 14.10.2003 93
R/3 System
________________________________________________________________

Attachments to Correspondence

You can take received documents referring to a claim, which have been stored in an archive, and assign
them to a document as attachments. Mark the appropriate document in the document proposal list, and
then click on the Display attachment icon. You can assign these attachments from the subsequent dialog
box.

You can only assign the attachments to documents, and it is not possible to output the attachments using
the Print Workbench. The system can only provide the identifier (archive ID and document ID) in the
Print Workbench.

Correspondence on Appraisal Procurement Document Category Level

You can put documents in the proposal list on the Appraisal procurement document category level. You
can do this within an appraisal, on the Appraisal request tab page.

Correspondence Output During Direct Input

Documents that are put in the document proposal list during Direct Input can be output during processing,
in the correspondence container (mass print). The system uses the corrout variable in the iclcorr_di
structure to control this.

Effects on Customizing

Differences Log

If you want to use the differences log, you must perform the following IMG activities:

1. Define Text Objects and Text IDs for Sample Text Modules

2. Generate SAPscript Sample Text Modules

3. Differences Log: Assign Sample Text Module to Category

4. Configure Internal Claim Types; this is where you assign the text object and the text ID (and its
sample text modules) to a procurement document category.

Free Text Entry for Correspondence

If you want to use the sample text modules as free text modules, perform the following IMG activities:

1. Define Text Objects and Text IDs for Sample Text Modules

2. Generate SAPscript Sample Text Modules

3. Assign Text Object and Text ID to Form Level for a Claim Document

________________________________________________________________
94 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

1.2.15 CRM Interface (New)

Use

From Release 4.71, the following additional functionalities are available for the interface between the
Claims Management system and an external system.

Provision of External Policy Information

You can use the ICL_EXIT_POL_IMPORT BAdI to provide policy information from an external system,
which is then used within the Claims Management system. Structures defined by the ACORD insurance
industry standard are used.

You have the following options:

o You can check the existence of the policy in the external system (check_ext_pol_exists method).
o You can provide policy data (including policy details, coverages, participants) The policy_load
method is used to return this information to the Claims Management system. The method uses
structures derived from the ACORD standard.
o You get additional policy clauses (such as additional clauses, risks, valid-from date, valid-to date,
free texts) (fill_addcl_pol method).
o You get the free text for a specific additional clause (read_addcl_freetext method).

Provision of Claim Information for an External System

You can use the ICL_CRM_CLAIMS_OF_BP_GET function module to provide all claims for a business
partner. This provides you with the following information:
o Claim information
o Payments
o Reserves

See also

For the provision of policy data, you can view the ICL_POLS_IMPORT_ACRD implementation for the
ICL_POLS_IMPORT_POLS BAdI, in particular the check_policy_exists and policy_load methods.

1.2.16 Damaged Objects (Changed)

Use

________________________________________________________________
SAP AG 14.10.2003 95
R/3 System
________________________________________________________________

New Fields for Damaged Vehicle

From Release 4.71, you can enter the following additional data for a damaged vehicle:
o Seasonal plate (new Month from and Month to fields)
o Next mandatory technical inspection (in month/year format)
o Date of last owner change

Direct Input for the Home Contents and Building damage categories

From Release 4.71, Direct Input for the entry of damaged home contents and buildings will be enhanced.
Function module ICL_DOBJ_DI (called up in function module ICLC_ICL_EVENT_DINP2_DOBJ) has
correspondingly been enhanced for these damage categories.

1.2.17 Diagnoses (Changed)

Short text

Diagnoses (Changed)

Use

As of Release 4.71, the following new functions and changes are available with diagnoses:

Field modification of diagnosis grid via case type (internal claim type)

On the basis of the Customizing settings you can display or hide the individual columns of the Overview
of Diagnoses Made section, depending on the case type (internal claim type). This enables you to adjust
display of diagnoses to the different case types.

Make these settings in the IMG activities Internal Claim Type: Define Claim Handler Group and Screen
Sequences for Expert Mode and Internal Claim Type: Define Claim Handler Group and Screen
Sequences for Other Processing Modes. Select the relevant internal claim type and then press the Field
Modification button. On the next screen, under Data Set, select Views Without Data Set Assignment and
then the Details icon. Under Field Groups, configure the field groups for diagnoses (key from 1300).

Assignment of the diagnosis to a subcase and injured person

Each diagnosis is assigned to a subcase and an injured person. You can only create an injured person and
assign to a diagnosis if you create a claimant for the relevant procurement document (such as
prescription) which contains the diagnosis.

________________________________________________________________
96 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

An injured person must be assigned to a diagnosis for diagnosis history purposes, enabling the system to
create a person-specific diagnosis history.

Diagnosis history (previous illnesses)

To navigate to the diagnosis history, in the Overview of Diagnoses Made section choose the Diagnosis
History -> Previous Illnesses icon. The system navigates to the previous illnesses of the claimant. By
default the system displays the diagnoses of all case types going back six months from the currenct date.

To view previous illnesses using your own selection criteria, choose the Diagnosis History -> Previous
Illnesses via Free Selection icon. For example, you can restrict the display of previous illnesses to a case
type or a period of your choice.

Field modification of diagnosis history grid via case type (internal claim type)

On the basis of the Customizing settings you can display or hide the individual columns of the Previous
Illnesses section, depending on the case type (internal claim type). This enables you to adjust display of
previous illnesses to the different case types.

Make these settings in the IMG activities Internal Claim Type: Define Claim Handler Group and Screen
Sequences for Expert Mode and Internal Claim Type: Define Claim Handler Group and Screen
Sequences for Other Processing Modes. Select the relevant internal claim type and then press the Field
Modification button. On the next screen, under Data Set, select Views Without Data Set Assignment and
then the Details icon. Under Field Groups, configure the field groups for diagnoses (key from 1327 to
1329).

New IMG activities for diagnoses

o Define Diagnosis-Specific Additional Attributes

o Define Diagnostic Certainty
o Define Specialist Departments

Customizing for side localization, severity, excoriation

Customizing for side localization, severity, and excoriation is performed independently of diagnoses.
This means that when you enter diagnoses, all the side localizations, severities, and excoriations that have
been defined are available.

New events in BRF

The BRF has the following new events for diagnoses:

o DIAG01
Triggered when a diagnosis is created
o DIAG02
Triggered when a diagnosis is changed

________________________________________________________________
SAP AG 14.10.2003 97
R/3 System
________________________________________________________________

o DIAG03
Triggered when a diagnosis is deleted

Tooth notation

You can capture dental treatment (particularly dental restoration) in a tooth notation. This tooth notation
allows users to enter a dental diagnosis, treatment (planning), and tooth connector for each numbered
tooth.

The following IMG activities are available for defining possible dental diagnoses, treatments, and tooth
connectors in the system:
o Define Dental Diagnosis
o Define Planning (Dental Treatment)
o Define Tooth Connectors

Note: There is a view for entering dental treatment (ICLH57), but in this release there is not yet an
internal claim type for dental treatment. As a result, in this release SAP does not supply a screen sequence
or screens in which this view is used.

However, if you want to use this view, you can perform one of the following activities:
o Define a new screen with this view and add the new screen to an existing screen sequence
o Add the view to an existing screen of a screen sequence

1.2.18 Direct Input (Changed)

Use

As from Release 4.71 the following changes or updates have been made to Direct Input for the Claims
Management system:

General Changes

o The OBJCAT, CLOBJET fields are now contained in the ICLCLAIMA_DI Direct Input structure.
You can now assign more than one object category (such as a claim bundle) and claim object (such
as a claim bundle number) to a claim.
o The ICL_CLAIM_DI function module has the es_iclclaima_di structure as an import parameter.

Store/Assign Incoming Documents with Direct Input (New)

From Release 4.71, you can use the Direct Input interface to store incoming documents in an archive, and
then assign them to a claim or subobject. The following fields are available in the ICL_AL_DI Direct
Input structure:

________________________________________________________________
98 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

o ARC_DOC_ID
If the document has already been stored in an archive, enter the existing archive ID in this field.
o FILE
If the document has not yet been stored in the archive, enter the access path for the document in this
field. In this case, the system stores the document in the archive and then creates the desired
assignment.
o AR_OBJECT
Business type for the document (such as invoice, appraisal, accident sketch)
o DESCR
Short text to enable easier document identification
o SUBOBJCAT
Subobject category to which the document is to be assigned. Permitted categories include the claim
itself, subclaim, claim items, claim item grouping, damaged object, participant.
o SUBCLAIM_REF
Reference number for the subclaim to which the document is to be assigned. If the subclaim is also
created using the interface, you can specify temporary numbers in this field, such as ###1.
o ITEM_REF
Reference number for the claim item to which the document is to be assigned. If the claim item is
also created using the interface, you can specify temporary numbers in this field, such as ###1.
o PROC_REF
Reference number for the claim item grouping to which the document is to be assigned. If the claim
item grouping is also created using the interface, you can specify temporary numbers in this field,
such as ###1.
o DOBJ_REF
Reference number for the damaged object to which the document is to be assigned. If the damaged
object is also created using the interface, you can specify temporary numbers in this field, such as
###1.
o PART_REF
Reference number for the participant to which the document is to be assigned. If the participant is
also created using the interface, you can specify temporary numbers in this field, such as #%1.

Processing for the ICL_AL_DI structure takes place using the generic recipient structure ICL_GEN_DI.
In this recipient structure, enter the name ICL_AL_DI in the STRUCNAME field, and enter the data for
the previously described structure in the data part (DATA field).

________________________________________________________________
SAP AG 14.10.2003 99
R/3 System
________________________________________________________________

1.2.19 Changes to SAP Easy Access Insurance (Changed)

Use

The following menu entries for the Claims Management system have changed on the SAP Easy Access
initial screen:
o The Business Workplace transaction has been added under Claims Management -> Search.
o The List of My Claims transaction has been deleted from Claims Management -> Search.
o The Create Invoice transaction has been added under Claims Management -> Processing Steps
(Expert).
o A new Bundle node has been inserted, and the following nodes have been added to it:
- The existing Claim Bundle node with its transactions
- The new Collective Invoice node with the Create, Change, and Display transactions

1.2.20 EDI (New)

Use

From Release 4.71, you can use the SAP standard IDoc interface to import external invoices for home
health care.

The ICL_IDOC_INPUT_INV01 function module is used for processing the incoming IDoc file. You can
use this function module to create:
o Invoices in the Claims Management system
o The collective invoice number

When an invoice is created, existing claims are updated or new claims are created.

The following objects were created:

o Message category: ICL_INVOICE
o IDoc category: ICL_INVOICE01
o Business object: ICLIDOCEVT
o Business object: ICLIDOCPCK
o Standard output: 20700086
o Incoming processing code: ICL 1
o Function module for incoming processing: ICL_IDOC_INPUT_INV01

________________________________________________________________
100 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

Overview of IDoc Category ICL_INVOICE01

o Segment E1CMIR1
Represents the collective invoice
o Segment E1CMIH1
Represents an individual invoice header
o Segment E1CMII1
Represents an invoice item for an invoice

The following BAdIs are used:

o BAdI ICL_POLS_IMPORT_POLS (BAdI: Interface to Policy Management system)
The following methods are used:
- check_policy_exists
You can use this method to check whether a policy from an external policy system is available
- policy_information_get
You can use this method to get the policy data from an external policy system
o BAdI ICL_IDOC (IDOC - Customer functions)
The following methods are used:
- custom_segment
You can use this method to process the IDoc file extension
- custom_invoice_processing
You can use this method to process additional data for the invoice
o BAdI ICL_INVOICE (Customer changes for invoices)
The following method is used:
- Claim determined
You can use this method to check whether a claim is to be updated or a new claim is to be
created for the invoice

IDoc Output:

Every occurrence of the E1CMIR1 section for the collective invoice creates an IDoc with a collective
invoice number. The collective invoice number that the system displays in the IDoc status record
corresponds to the collective invoice number in the Claims Management system. In the Claims
Management system, you can see the individual claim numbers, which are linked to the invoices, on the
collective invoice screen.

________________________________________________________________
SAP AG 14.10.2003 101
R/3 System
________________________________________________________________

Effects on System Administration

Effects on Customizing

Make the following standard EDI Customizing settings:

o Partner agreement
o Port description

1.2.21 Home Health Care (HHC) (Changed)

Short text

Home Health Care (HHC) (Changed)

Use

As of Release 4.71 the following new or changed functions are available for processing cases of home
health care in the line of health insurance:
o Display of status for all procurement documents (changed)
The system displays the status of the procurement document instead of the subclaim status. You
cannot change this status manually. The status is only changed if you select one of the following
buttons:
- Reverse
- Reject
- Approve
The status controls whether entries can be made in fields.
o Enter prescription (changed)
The following data is available:
- Claimant
- Applicant
- Prescriber
- Date entered (set automatically)
- Date issued
- Date received

________________________________________________________________
102 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

- Prescription period
- Service provider
- Comments
- Facts capture
- Procurement document type as search help filter for medical device items
- Under medical device items:
Benefit type
Name of benefit type (just a display field)
Daily
Weekly
Monthly
In total
Valid-from date
Valid-to date
- Diagnoses made
(see also Release Note on Diagnoses)
o Copy prescription to approval (changed)
Transfer of data from the prescription (procurement document types and medical device items) to the
approval has been adjusted to the new fields in the prescription.
By default the system displays the currency that you defined for the relevant internal claim type at
claim header level in IMG activity Configure Internal Claim Types. However, you can change the
currency.
You can only copy a prescription to an approval if no other approval exists.
o Create appraisal (new)
You can create appraisal orders and appraisal receipts (see Release Note on Appraisals).
o Enter approval (changed)
The following data is available:
- Approval number (set automatically)
- Date entered (set automatically)
- Approval date (set automatically)
- Service provider
- External transaction number
- Approval period
- Comments
- Procurement document type as search help filter for medical device items
- Under medical device items:

________________________________________________________________
SAP AG 14.10.2003 103
R/3 System
________________________________________________________________

Benefit type
Name of benefit type (just a display field)
Amount claimed
Currency
Daily (just a display field)
Weekly (just a display field)
Monthly (just a display field)
In total (just a display field)
Daily
Weekly
Monthly
In total
Valid-from date
Valid-to date
Rejection reason
Name of rejection reason (just a display field)
o Copy approval to invoice
o Create invoice
(see Release Note on Invoices)
o Reimbursement of simple invoices
(see Release Note on Reimbursement)

1.2.22 IBNR Reserve (Changed)

Use

From Release 4.71, IBNR reserves can be set according to freely configurable procedures. Reserves can
be determined from the claims, by configurable selection criteria, and can be enhanced with statistical
values based on experience.

The system can also create artificial cases. The system then aggregates these individual reserves
according to configurable grouping criteria, to form IBNR reserves. You can also specify the IBNR
reserve directly. If the driver data is available, the system will continue to support the previous
distribution of IBNR reserves on a more detailed level.

You also have the option of creating and processing driver data and statistics manually. You can also

________________________________________________________________
104 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

process the procedure results manually.

You can configure the calculation methods and their application to the reserve group cluster. Reserve
group clusters can overlap with one another, and the calculation methods can be applied to these clusters,
more than once and in a definable order. You can also use the ICL_IBNR_CALCULATE BAdI
(Calculation methods for IBNR reserves) to define your own calculation methods and change the standard
delivered methods during implementation.

The existing data model for IBNR reserves, with the freely configurable account assignment
characteristics (indicative) and grouping technology, will still be used. This will affect grouping and
cluster formation, in particular, as well as versioning.

Effects on Customizing

You can configure the following options in the relevant IMG activities under Claims Management ->
Claim -> Business Settings -> Reserves -> Background Reserve Setting -> Reserves for Claims Incurred
but not Reported (IBNR).
o Permitted account assignment characteristics (indicative)
o Reserve group categories
o Reserve groups and the assigned account assignment intervals
o Reserve group cluster
o Versions

The BAdI methods are defined as calculation methods. In addition, the calculation methods, a calculation
parameter and the associated cluster are defined in a list with sequence. If necessary, you can overwrite
the existing calculation methods and define new methods during implementation.

1.2.23 Changes in IMG (Changed)

Short text

Changes in IMG (Changed)

Use

The following changes have been made in the IMG for the Claims Management system as from Release
4.71:

Claim Hierarchy Node

Product Configuration node:

________________________________________________________________
SAP AG 14.10.2003 105
R/3 System
________________________________________________________________

o The Collections/Disbursements: Define Reference Template for Contract Account IMG activity has
been renamed FS-CD: Define Contract Account Creation Variant and Insurance Object for Policy

Business Settings node:

o Under Claim Status a new IMG activity has been added, namely Enhance Claim Status / Subclaim
Status
o Under Claim Status, IMG activity Reasons for Changing Loss Date has been deleted
o Under Origin of Loss, IMG activity Define Faults is now directly after Define Causes of Loss
o The Coverage Check node has been renamed Coverage Referral
o Under Damaged Objects -> Diagnoses the following IMG activities have been added:
- Define Diagnosis-Specific Additional Attributes
- Define Diagnostic Certainty
- Define Specialist Departments
o Under Damaged Objects -> Diagnoses the following IMG activities have been deleted:
- Define Permitted Side Localizations with Diagnoses
- Define Permitted Severities with Diagnoses
- Define Permitted Excoriations with Diagnoses
o Under Claim Item the following new IMG activities have been added:
- Define Usage Type of a Claim Item
- Enhance Claim Item Categories
o A new node has been created, namely Procurement Document Categories. It contains the following
new IMG activities:
- Enhance Procurement Document Categories
- Define Types of Procurement Document Category
- Define Reasons for Creating a Procurement Document
- Appraisal: Define Resubmission Task
o Under External Services Integration -> Tolerance for Procurement, the IMG activity Tolerance
Group and Key has been renamed Specify Tolerance Key for Each Tolerance Group
o Under External Services Integration, the IMG activity Define Partner Roles for Procurement System
has been renamed Define Key for Partner Functions in Procurement System
o Under Invoice the following new IMG activities have been added:
- Define Tax Calculation with Invoice Items
- Enhance Data Origin of an Invoice
o Under Invoice, the IMG activity Define Invoice Types has been changed and inserted as IMG activity
Enhance Collective Invoice Types under Bundle -> Collective Invoice .
o Under Payments, the General Settings for Collections/Disbursements node has been added, and
under it the following IMG activities:
- BAdI: Interface to Collections/Disbursements

________________________________________________________________
106 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

- Assign Organizational Units to Business Areas

o Under Payments, the Special Settings for FS-CD node has been added, and under it the following
IMG activities:
- Define General Parameters for FS-CD
- FS-CD: Define Contract Account Creation Variant and Insurance Object for Policy
- FS-CD: Define Contract Acct Creation Variant and Insurance Object for Claim
- Assign Contract Acct Creation Variant + Ins.Obj. for Clm to Internl ClmType (organizational
activity, meaning that only documentation is available)
- Define Standard Data for FS-CD Document
- Assign Standard Data for FS-CD Document to an Internal Claim Type (organizational activity,
meaning that only documentation is available)
- Activate Additional Functionality in Document Clearing (Contract A/P + A/R)
o Under Payments the Payment Release node has been added, and under it all IMG activities that were
previously assigned to the Technical Settings -> User Guide -> Authorizations node. The
Authorizations node has been deleted.
o Under Reserves -> Batch Reserves, the Reserves in Health Insurance (IBNR) node has been added,
with the following structure:
- Reserve Group Categories and Indicatives with the relevant IMG activities
- Reserve Group Categories and Indicatives with the relevant IMG activities
- Reserve Group Cluster with the relevant IMG activities
- Calculation Rules with the relevant IMG activities
- Results and Account Assignments with the relevant IMG activities
o The Loss Allocation Agreement node has been added, and under it the new IMG activity Consider
Policy Data + Compenstn Calc. with Loss Alloc.Agmnt + Coinsurance
o The Coinsurance node has been added, and under it the new IMG activity Consider Policy Data +
Compenstn Calc. with Loss Alloc.Agmnt + Coinsurance
o Under Notes, IMG activity Define Claim Note Types has been renamed Define Topics for Claim
Notes
o Unter Correspondence, the following nodes have been added:
- Print Workbench, and under it the following new IMG activities:
Define Form Classes
Define Application Forms
- SAPscript Sample Text Modules, and under it the following new IMG activities:
Define Text Objects and Text IDs for Sample Text Modules
Create SAPscript Sample Text Modules
o Under Correspondence, the new IMG activity Assign Text Object and Text ID to a Form Level of a
Claim Document has been added
o The Structured Facts Capture node has been moved and is now a sub-node of the new Structuring

________________________________________________________________
SAP AG 14.10.2003 107
R/3 System
________________________________________________________________

Business Processes node.

o The new IMG activity Enhance Processes has been added

The Structuring Business Processes node has been added, and under it the following nodes:
o Business Rule Framework (BRF) with the relevant IMG activities
o Activity Management with the relevant IMG activities
o Structured Facts Capture with the relevant IMG activities

Process Control (Internal Claim Types) node

o The configuration of benefit types has been removed from IMG activity Configure Internal Claim
Types. Instead, the new IMG activity Configure Benefit Type Trees has been added.
o The IMG activity Assign Internal Claim Types to Policy Products has been renamed Assign Internal
Claim Type to a Combination of Policy Product and Loss Incident Type
o The IMG activity Define Permitted Claim Handler Groups/Screen Sequences for Expert Mode has
been renamed Internal Claim Type: Specify Claim Handler Group+Scrn Sequences f.ExpertMode
o The IMG activity Define Screen Sequences for All Other Processing Modes has been renamed
Internal Claim Type: Specify CH Group+Screen Sequences for Other Proc.Modes

Technical Settings node:

o A new node, Navigation, has been created, and under it the following new IMG activities:
- Enhance Claims Processing Modes
- Enhance Navigation Tree Types
- Define Structure of Own Defined Navigation Tree
o The User Guide node has been deleted. The nodes assigned to it have been reassigned as follows:
- The Screen Modification node has been added as a subnode to Technical Settings
- The Authorizations node has been renamed Payment Release and has been assigned to the
Business Settings -> Payments node, along with all its IMG activities
- The Rule-Based Event Control node has been renamed Business Rule Framework (BRF) and
assigned to the Structuring Business Processes node
o Under Screen Modifications the following IMG activities have been renamed:
- Define Field Modification for Activities has been renamed Configure Field Attributes for Each
Activity
- Define Field Modifications for Claim Handler Groups has been renamed Configure Field
Attributes for Each Internal Claim Type for Expert Mode
- Define Field Modifications for All Other Processing Modes has been renamed Configure Field
Attributes for Each Internal Clm Type for Other Proc.Modes
o The following changes have been made to Workflow Integration:
- IMG activity Assign BRF Expression to BOR Event Parameter has been added
- IMG activity Configure Basic Parameters for Workflow Integration has been deleted
o Under Customer Enhancements -> Business Add-Ins, the following IMG activities have been added:

________________________________________________________________
108 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

- BAdI: Interface to Policy System (redundant to assignment under Business Settings -> Policy
Product Configuration)
- Calculation Methods for IBNR Reserves
- Consider Policy Data + Compenstn Calc. with Loss Alloc.Agmnt + Coinsurance
- BAdI: Call Business Partner Full Maintenance
- BAdI: Change Node Text and Icons in Navigation Tree
- BAdI: IDOC Customer Functions
The following IMG activities have been deleted:
- Extensions to List of My Claims
- Assignment of Claim Handler

Claim Bundle Hierarchy Node

The following IMG activity has been added:

o Define Claim Bundle Type for Each Transaction Code

Notice of Loss Hierarchy Node

Under Notice of Loss the following new IMG activities have been added:
o Assign Damage Category to a Damage Descriptor
o Enhance Processing Mode of Notice of Loss
o Enhance Category of Damaged or Insured Object
o Enhance Status of Notice of Loss
o Define Required Fields for Notice of Loss
o Assign Object Category to a Damage Category
o Assign Damage Category to a Damage Descriptor

1.2.24 Invoice Entry / Invoice Processing (Changed)

Short text

Invoice Entry / Invoice Processing (Changed)

Use

From Release 4.71, the following new functionalities are available for invoice entry and invoice
processing:

________________________________________________________________
SAP AG 14.10.2003 109
R/3 System
________________________________________________________________

o You can enter individual invoices and also collective invoices (see Release Note on Collective
Invoices).
o In the case of individual invoices, a differentiation is made in expert mode between invoice entry and
invoice processing.
In invoice entry, you store data of the invoicing party without modifying it.
In invoicing processing, you can scrutinize invoice data that has been entered, and you can change it
if necessary and make payouts.
To enable this separation from a technical point of view, the entries for the header of invoice entry or
processing are saved in different claim item groupings.
o You can trigger invoice entry directly from the initial screen for individual invoices. You no longer
have to navigate through the general claim initial screen. Once you have entered certain selection
criteria, the system lists the potential approvals. You can select the approval from this list. The
system transfers the data of the selected approval as a template to the invoice entry screen.
o You can enter the deductible at invoice header level and also at invoice item level. You can enter this
deductible either as a percentage or as an amount. The deductibles entered at header level can be
distributed.
o You can enter one or several cash discount percentages with the relevant due date in a cash discount
table.
o At item level you can specify whether the requested original amount per unit contains added-value
tax or not. Depending on the selection, a tax rate is added or not added to the original amount
requested.
o On the Tools screen you can perform collective actions for all invoice items (such as replacing item
numbers or transferring original amount per quantity unit).
o Using the differences log you can record the difference (as an amount) between the invoice items
requested and those paid out. You can document this in correspondence (a letter, for example) to the
invoicing party.

There is another release note on the subject of invoices:

Reimbursement of Simple Invoices

Effects on Customizing

If you want to use the differences log, you must perform the following IMG activities:
1. Create SAPscript Sample Text Modules
2. Configure Internal Claim Types
This is where you assign the text object and the text ID (and its sample text modules) to a
procurement document category.

________________________________________________________________
110 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

1.2.25 Changes to Main Program (Changed)

Use

From Release 4.71, the following new functionalities are available in the main program for the Claims
Management system.

Title Creation in DTITL

From Release 4.71, you can create the title line yourself in the BDT for event DTITL. You no longer
have to use the functionality specified by the system.

BAdI Duplicate Check

From Release 4.71, you can implement the ICL:DUPLICATE_CHECK BAdI (Find Possible Claim
Duplicates During Creation Process). You no longer have to use the method specified by the system. The
BAdI has the following methods:
o get_entry
You can use this BAdI method to perform a duplicate search after the initial claim screen.
o get_save
You can use this BAdI method to perform a duplicate search when a new claim is saved.
o hitlist_prepare
You can use this BAdI method to prepare hit lists for both the search methods named above.

Navigation Tree

From Release 4.71, you can use the BAdI ICL_NAVTREE_NODE (Navigation Tree: Change Node Text
and Icon) to create your own node texts and icons in the navigation tree. You no longer have to use the
functionality specified by the system.

Effects on Existing Data

Title Generation in DTITL

The previous title generation functionality is delivered in the ICLC_ICL_EVENT_DTITL_CDC function

module for event DTITL.

The format is as follows:

Claim Claim Number / (Sub)Claim Description Activity: BDT Screen Title

Example:

________________________________________________________________
SAP AG 14.10.2003 111
R/3 System
________________________________________________________________

Claim 4711 / HIMI Smith (Open) Change: Activities

BAdI Duplicate Check

SAP delivers the previous search functionality as a standard implementation for the get_entry method
(duplicate search after the initial screen).

Navigation Tree

SAP delivers the previous functionality in the standard implementations for the ICL_NAVTREE_NODE
BAdI.

Effects on Customizing

Title Creation in DTITL

You can generate your own event function module and enter it in Customizing for the BDT for event
DTITL. Assign a lower item number than the SAP module (9900000) to the module, as the BDT cancels
calls to the DTITL as soon as a module has set the e_xchanged export parameter.

BAdI Duplicate Check

You can find the BAdI under the following path: Claims Management -> Claim -> Technical Settings ->
Customer Enhancements -> Business Add-Ins -> Find Possible Claim Duplicates During Creation
Process.

For more information, see the BAdI documentation.

Navigation Tree

If you want to change the specified texts, create your own implementation of the
ICL_NAVTREE_NODE BAdI for the appropriate claim processing modes.

1.2.26 Medical Devices (New)

Short text

Medical Devices (New)

________________________________________________________________
112 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

Use

As of Release 4.71 the following new or changed functions are available for processing cases involving
medical devices in the line of health insurance:
o Display of status for all procurement documents (changed)
The system displays the status of the procurement document instead of the subclaim status. You
cannot change this status manually. The status is only changed if you select one of the following
buttons:
- Reverse
- Reject
- Approve
The status controls whether entries can be made in fields.
o Enter prescription (changed)
The following data is available:
- Claimant
- Applicant
- Prescriber
- Date entered (set automatically)
- Date issued
- Date received
- Prescription period
- Service provider
- Comments
- Facts capture
- Procurement document type as search help filter for medical device items
- Under medical device items:
Item number
Item name (display)
Number
Unit (display)
- Diagnoses made
(see also Release Note on Diagnoses)
o Copy prescription to cost estimate (changed)
Transfer of data from the prescription (procurement document data and medical device items) to the
cost estimate has been adjusted to the new fields in the prescription.
By default the system displays the currency that you defined for the relevant internal claim type at

________________________________________________________________
SAP AG 14.10.2003 113
R/3 System
________________________________________________________________

claim header level in IMG activity Configure Internal Claim Types. However, you can change the
currency.
o Create cost estimate (new)
You can create a cost estimate. In contrast to Copy Prescription to Cost Estimate, the system does
not transfer (copy) any data from the prescription.
o Copy prescription to approval (changed)
Transfer of data from the prescription (procurment document types and medical device items) to the
approval has been adjusted to the new fields in the prescription.
By default the system displays the currency that you defined for the relevant internal claim type at
claim header level in IMG activity Configure Internal Claim Types. However, you can change the
currency.
You can only copy a prescription to an approval if no other approval exists.
o Create appraisal (new)
You can create appraisal orders and appraisal receipts (see Release Note on Appraisals).
o Overview of cost estimates (new)
In the overview of cost estimates the system displays the following fields:
- Service provider
- Date issued
- Total amount requested
- Currency unit
o Enter cost estimate (changed)
The following data is available:
- Service provider
- Date entered (set automatically)
- Date issued
- Date received
- External transaction number
- Approval period
- Procurement document type as search help filter for medical device items
- Under medical device items:
Item number
Item number name (display)
Number
Unit (display)
Currency
Sales tax calculation code

________________________________________________________________
114 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

Name of sales tax calculation code (display)

Usage type indicator
Name of usage type indicator (display)
Amount requested per quantity unit
Amount claimed/requested
o Reverse cost estimate (new)
You can now reverse cost estimates, and not just delete them. If you reverse a cost estimate, you are
then unable to enter any more data in the cost estimate. In addition, you cannot create an approval
from a cost estimate.
o Copy cost estimate to approval (changed)
Transfer of data from the cost estimate (procurement document data and medical device items) to the
approval has been adjusted to the new fields in the cost estimate.
By default the system displays the currency that you defined for the relevant internal claim type at
claim header level in IMG activity Configure Internal Claim Types. However, you can change the
currency.
You can only copy a cost estimate to an approval if no other approval exists (including no reversed
approval).
o Enter approval (changed)
The following data is available:
- Approval number (set automatically)
- Date entered (set automatically)
- Approval date (set automatically)
- Service provider
- External transaction number
- Approval period
- Comments
- Procurement document type as search help filter for medical device items
- Under medical device items:
Item number
Item name (just a display field)
Number
Unit (just a display field)
Currency
Code for sales tax calculation
Name of code for sales tax calculation (just a display field)
Amount requested (just a display field)

________________________________________________________________
SAP AG 14.10.2003 115
R/3 System
________________________________________________________________

Approved amount per quantity unit

Approved amount
Rejection reason
Name of rejection reason (just a display field)
o Use of the differences log for the approval
(see the Differences Log section in the Release Note on Correspondence)
o Copy approval to invoice
o Create invoice
(see Release Note on Invoices)
o Reimbursement of simple invoices
(see Release Note on Reimbursement)

1.2.27 List of My Claims (Changed)

Use

The List of my Claims function is no longer available as of Release 4.71. This function is assumed by the
workflow connection in the Claims Management system.

1.2.28 Notes (Changed)

Use

From Release 4.71, you can also use generic object services (GOS) to create notes for the object.

GOS offers various services for certain objects as its central service. You can use GOS to create notes for
a certain object.

To call up the services for the object, follow the menu path System -> Object Services in claim
processing. The object services are only active in change mode or display mode for claim processing.
They are not active in create mode, as you can only use the services for existing objects.

You can currently use the generic object services for the following subobject categories that are
registered as BOR objects:
o CLAIM (claim)
o ICLPAY (payment)

________________________________________________________________
116 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

o SUBCLAIM (subclaim)
o ICLACT (activities)
o CLAIMSUBOB (claim subobject)

Integration between the notes for the Claims Management system and the GOS service is restricted to the
Claim and Subclaim BOR objects, as you can only assign notes to one claim or subclaim in claim
processing. The system displays these assigned notes in the section entitled Notes, if you click on the
Refresh GOS Notes icon.

If you create a note for other subobject categories, such as Payment, Activities or Claim subobject, these
notes are not integrated into the application, meaning that these notes can only be seen in the GOS service
list.

The Note type field has also been renamed Topic for Release 4.71.

1.2.29 Notice of Loss (Changed)

Short text

Notice of Loss (Changed)

Use

From Release 4.71, the following new functionalities are available for the notice of loss component:
o You can now manage other lines of insurance in addition to automobile insurance. Home contents
insurance has already been realized. Enhancements to include other lines of insurance (such as
health) are possible.
o You can capture the following additional data:
- Details on the policy of the claimant.
- In the IMG activities Enhance Participant Roles and Define Visibility of Participant Roles you
can customize participant roles. This enables you to capture any number of participants. You
can also input data on injuries sustained by participants.
- You can capture any number of damaged vehicles. These vehicles can be assigned to a
participant.
- You can capture data on damaged items. These damaged items can be assigned to damaged
vehicles.
- In general, you can capture damage descriptors for persons, vehicles, and home contents.
o The following BAdIs are available:
- BAdI for additional insurance-specific plausibility checks
- BAdI for plausibility checks on postal code and telephone number

________________________________________________________________
SAP AG 14.10.2003 117
R/3 System
________________________________________________________________

o You can link an Internet service to the Notice of Loss component.

o In IMG activity Define Required Fields for Notice of Loss you can completely customize required
fields.

Effects on Customizing

To configure participant roles, you must perform the following IMG activities:
o Enhance Participant Roles
o Define Visibility of Participant Roles

To define required fields, perform IMG activity Define Required Fields for Notice of Loss.

1.2.30 Participants (Changed)

Use

The following new functions are available for participants from Release 4.71:

Extended Assignment of Business Partner Roles to Participant Roles

In the Define Characteristics of Participant Roles IMG activity, you have to assign a business partner
role or a business partner role grouping to the participant role.

If you create a new participant in the respective role in claim processing, or if the system executes a
duplicate check, you use this assignment to define the business partner role or business partner role
grouping, in which the participant has to be available.

You require this assignment in health insurance. For example, a participant with the Prescriber role can
assume one of the following business partner roles:
o Physician
o Hospital
o Rehabilitation institution

Displaying Business Partner Relationships as Participant Roles

In Customizing you can define that business partner relationships are also displayed as participant roles in
the participant list. To do this, assign a business partner relationship to a participant role in the Define
Characteristics of Participant Roles IMG activity.

When you create a claim, the system reads the business partner from the policy. The system transfers this
to the participant role (insured person, for example). A check is also made in the business partner system
to see which business partner relationships exist for the business partner.

________________________________________________________________
118 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

If the business partner relationship defined in the Define Characteristics of Participant Roles IMG
activity exists, the Claims Management system automatically creates this business partner relationship as
the participant role.

You need the business partner relationships displayed as participant roles in health insurance; for
example:
o Person (caregiver) who provides care to the claimant
o Child, this being the prerequisite for certain benefits
o Representative of incapacitated insured person

Extended Control of Use of Participant Roles

From Release 4.71, you can also use the following methods to control selection of possible participant
roles when creating a participant. This allows you to give a better overview of the list of possible
participant roles, and format it according to content-related points of view.
o In the Determ.System Oper.Mode w. Creation of Claim Participants per Int.ClaimType IMG activity,
you can define which participant roles can be used for an internal claim type. If you want to create a
participant in claim processing, the system only offers those participant roles that you have assigned
to the respective internal claim type.
o For every participant role, the system also checks whether a required subobject is available. In
Customizing, for example (IMG path: Claims Management -> Claim -> Business Settings ->
Participants -> Enhances Participant Roles), if you set it so that you can only create a participant in
the Appraiser role for the Damaged object subobject category, the system checks whether a damaged
object exists. If no damaged object exists, the system does not allow you to select the Appraiser role.

Maintaining the Business Partner in Another Business Partner System

The Full maintenance button is still available on the mini business partner screen. From Release 4.71,
clicking on this button calls up the Call Business Partner Full Maintenance BAdI
(ICL_BP_FULL_MAINTENA ).

This takes you as standard to full maintenance for the SAP Business Partner. You now have the
alternative option of using your own implementation to branch to another business partner system.

Effects on Customizing

If you have defined your own participant roles, you must make the changes described above in the Define
Characteristics of Participant Roles IMG activity.

In the Determ.System Oper.Mode w. Creation of Claim Participants per Int.ClaimType IMG activity,
define which participant roles can be used for an internal claim type. Otherwise you will not be able to
create these participant roles.

________________________________________________________________
SAP AG 14.10.2003 119
R/3 System
________________________________________________________________

1.2.31 Payments (Changed)

Use

From Release 4.71, the following new or changed functionalities are available for payments.

Repetitive Payments

You can create repetitive payments. These payments are based on the payment plans in the SAP
Collections/Disbursements system (FS-CD). That means that FS-CD is responsible for monitoring and
executing the repetitive payments.
The creation of repetitive payments is the same as for all other record types in payment. You just have to
fill the following additional fields:
o Valid-from date
o Valid-to date
o Payment plan

When you save the payment, the corresponding payment plan is stored in FS-CD.
A mini CD screen provides you with details about the payment plan in the Claims Management system.
In this release, you cannot change or reverse a payment plan.

Payment Method for Collective Payments

If you have selected a payee with collective payment authorization, the system previously only displayed
one message in the status line. This message contained a note on the usage of a suitable payment method
(clearing payment method).

From Release 4.71, the system changes the specified payment method automatically, if you have only
entered one clearing payment method in Customizing.

The note for the user appears as a dialog box from Release 4.71.

Display of Cleared Deductibles

From Release 4.71, payments and cleared deductibles (payments with a zero amount) are displayed
together instead of separately.

1.2.32 Changes in the BAdI for Policy Interface (ICL_POLS_IMPORT_POLS)

Short text

________________________________________________________________
120 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

Changes in the BAdI for Policy Interface (ICL_POLS_IMPORT_POLS)

Use

Key Field POLVNR

As from Release 4.71, key field POLVNR has been added to the interface structures of this BAdI. For the
upgrade to 4.71, enter the value of "0" in this key field.

Using this key field you can:

o Maintain multiple policy versions
o Save and display multiple policies within a claim.

These functionalities are not fully supported in Release 4.71.

Parameter ET_POL und ES_POL

As from Release 4.71, parameter ET_POL has been added. Using this parameter you can transfer
multiple policy versions or policies. You do not need to fill this parameter.

Continue to use parameter ES_POL. If multiple policy versions exist, this parameter displays the leading
policy version. The leading policy version is the one that determines the internal claim type, together with
the loss incident type.

Save Insured Persons as Insured Objects

As from Release 4.71 you can save insured persons as insured objects. This means that coverages can be
connected with certain insured persons.

STATUS Field

As from Release 4.71, the STATUS field has been added to the ICL_POLM_XIF structure. This field is
only for display purposes at present.

Effects on Existing Data

The POLVNR key field is set to zero for existing data.

Effects on Data Transfer

________________________________________________________________
SAP AG 14.10.2003 121
R/3 System
________________________________________________________________

1.2.33 Multiple Prescription (New)

Short text

Multiple Prescription (New)

Use

As of Release 4.71 you can enter multiple prescriptions for health insurance. As the system automatically
saves and displays the association of a prescription to a multiple prescription, you only have to enter the
header data of the prescription once.

Similarly, you can also enter multiple cost estimates in Release 4.71.

You can create a multiple prescription on the Prescription screen, in the Medical Device Items section
(ALV Grid). When you create a multiple prescription, the system creates another prescription and copies
the header data of the prescription. The system adds any selected medical device items to the other
prescription. You can only change the header data in the original prescription. If you have created a
multiple prescription, you can also display all medical device items of a multiple prescription.

Similarly, you can create multiple cost estimates on the Cost Estimate screen. If you only want to copy a
cost estimate without creating a multiple cost estimate, select the Only Copy Cost Estimate checkbox on
the Create Claim: Target Subclaim dialog screen.

1.2.34 Procurement (Changed)

Short text

Procurement (Changed)

Use

As from Release 4.71 you can assign external services to a make and a category of damaged object. This
is only possible for the categories of Home Contents and Equipment (key PE) and Vehicles (Key AU).

This means that you can specify which specific repair shop for a certain make of automobile should be
displayed in the ranking list of best services. The system only displays those repair shops registered for
the specific make of damaged vehicle.

To make these settings, go to the SAP Easy Access screen and select Insurance -> Claims Management
-> Claim -> Business Partner in Claim -> External Services (or Repair Shop and so on) -> Create or
Change.

________________________________________________________________
122 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

The following rules apply:

o If you define a make and a category of damaged object for an external service, this external service is
only displayed for damaged objects related to this make.
o If you only define a category for an external service, but not a make, the external service is only
displayed for damaged objects in which you did not enter any make during claims processing.
o If you only define a make/manufacturer for an external service, but not a category, the external
service is displayed for all makes/manufacturers of the damaged object.
o If you define neither a make nor a category for an external service, the external service is always
displayed.

1.2.35 Reimbursement of Simple Invoices (Changed)

Use

As of Release 4.71 there is a screen in expert mode for reimbursement of simple invoices. This is flagged
by the Reimbursement procurement document category.

This means that you can pay out simple invoices (such as documents sent in directly by the policyholder)
without there being a differentiation between invoice entry and processing, as is normally the case with
invoices (see Release Note on Invoices).

On the screen for reimbursement of simple invoices, the following main functions are available:
o You can enter receivables and payment proposal items in a list.
o You can transfer the reimbursement to a payment. This is then transferred to the collections and
disbursements system.

There is another release note on Invoices:

Processing Collective Invoices

1.2.36 Reporting (Changed)

Use

As of Release 4.71 you have an additional selection option with the worklist (Worklist screen). In the
Layout of List section, you can additionally restrict the selection by ALV Tree up to Organizational Unit.

In this case, the system displays in the result list the worklist for specific organizational units from

________________________________________________________________
SAP AG 14.10.2003 123
R/3 System
________________________________________________________________

Organizational Management.

1.2.37 Reserve (Changed)

Use

From Release 4.71, you can use quantities, prices per quantity and units of measure for setting reserves in
claims. In addition to the set reserve amount, you can define a quantity, a price for each unit of measure
and the unit of measure for each reserve, if required.

A quantity and a unit of measure often describe the expected expenses more accurately. For example, it is
more plausible to estimate the number of days and the day rate for a stay in hospital, than to estimate an
amount.

This functionality is available in addition to the existing functions for setting reserves.

If you configure a reserve type so that it is possible to specify quantities, the associated fields in the
system are ready for input (quantity, price for each quantity, unit of measure). In this case, the system
displays the reserve amount automatically. You cannot enter or change it manually.

Effects on Customizing

To activate the new functionality, you have to select the Daily Hospital Benefit or Standard (with
Quantity) reserve category in the Define Reserve Types IMG activity, and define a standard unit of
measure.

For statistical reserving you can also define default values for amount, quantity, price for each unit of
measure and the unit of measure in the Configure Internal Claim Types IMG activity. This definition
takes place at subclaim level, for each permitted reserve type.

1.2.38 Structured Facts Capture (Changed)

Use

From Release 4.71, you can execute structured facts capture for every damaged object and every
participant in the claim.

Effects on Customizing

To use the functionality,

1. Define appropriate question sequences in the Configure Structured Facts Capture IMG activity

________________________________________________________________
124 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

2. In the Configure Internal Claim Types IMG activity, assign the question sequences to an internal
claim type (from the facts capture category DO (damaged object)) or PA (participant).
If you want to call up various question sequences, dependent on the participant role for the
participant, enter an expression in the 1st Parameter field to determine the current participant role.
The system compares this participant role with the value in the 1st Value field. If the values are
identical, the appropriate question sequence is called up. Then enter a line of this type for every
participant role.

1.2.39 Notes on Upgrading to Release 4.71

Short text

Notes on Upgrading to Release 4.71

Use

Note: We advise you to contact SAP (FS-CM component) before you implement a release upgrade. First
of all it must be clarified whether you need an upgrade or just an update for any of the points listed
below.

Release 4.71 contains some significant changes over Release 4.64. For this reason, consider the following
issues when performing an upgrade to Release 4.71:
o Introduction of the Business Rule Framework (BRF)
As from Release 4.71 you must use the BRF. The Business Rule Tool (BRT) is no longer supported.
If you want to upgrade from 4.64 to 4.71, contact SAP.
You can find more information on the BRF in the Release Note for BRF.
o Introduction of the benefit type tree entity (see Release Note on Benefit Type Tree)
o Changes in the BAdI with regard to the compensation calculuation (see Release Note for this BAdI).
o Changes in the BAdI with regard to the policy interface (see Release Note for this BAdI).
o As of Release 4.71, several new BAdIs are available, including
- Find Possible Claim Duplicates During Creation Process (ICL_DUPLICATE_CHECK)
- Navigation Tree: Change Node Text and Icons (ICL_NAVTREE_NODE)
o Integration of Business Workflow in Claims Management system (see Release Note on Business
Workflow)
o Read the other Release Notes for further information on all new functions and changes in FS-CM for
Release 4.71.

________________________________________________________________
SAP AG 14.10.2003 125
R/3 System
________________________________________________________________

1.2.40 Where-Used List and Deletion Check in Customizing (New)

Use

As from Release 4.71, a deletion check and a where-used list are available in Customizing.

Delection Check

If you delete a Customizing entry, the system automatically performs a deletion check.

If there are no dependent Customizing entries, the system deletes the entry as soon as you select Save.

If dependent Customizing entries exist, the system does not delete the Customizing entry, so as to avoid
inconsistencies within the Customizing tables. The system displays the usages in an application log.

Where-Used List

To execute a where-used list for Customizing entries, choose the Where-Used List icon.

1.2.41 SAP Business Workflow in the Claims Management System (New)

Use

From Release 4.71, the claim handler assignment available up to Release 4.64 will be partially replaced
by the SAP Business Workflow.

The following workflows are available:

o ICLClaim_001
Edit claim
o ICLSubcl_001
Edit subclaim
o ICLAct_001
Edit task

If you open or reopen a claim, a subclaim or a task in claim processing, the system starts the appropriate
workflow. If you close a claim, a subclaim or a task, the system ends the appropriate workflow.

When a workflow is started, data is transferred from the application to the workflow (the policyholder,
for example). This data can be displayed in the workflow inbox; it can be used for determining a claim
handler, or for deadline monitoring.

________________________________________________________________
126 14.10.2003 SAP AG
 R/3 System
________________________________________________________________

The SAP Business Workflow integration replaces the claim handler assignment available up to Release
4.64 in the following ways:
o From Release 4.71, List of My Claims, List of My Tasks and dispatching all take place using the
workflow inbox.
o It is no longer possible to maintain claim handlers and claim handler groups in the claim. The
Business Workflow is only used to display the actual processor (user) and his organizational unit
after the workflow has been executed. You can use this to evaluate processed claims, subclaims and
tasks, for example. Before executing the workflow, the appropriate fields are empty, as a workflow
can be assigned to more than one processor (user).
o It is possible to assign positions as well as users.

Effects on Customizing
o Make the following settings in the Execute Task-Specific Customizing IMG activity (IMG path: SAP
Web Application Server -> Business Management -> SAP Business Workflow -> Execute
Task-Specific Customizing).
- Select the FS-CM application component (path: Financial Services -> Claims Management)
- Activate the triggering events and assign processors to the events:
The task IDs are:
TS20700089 Edit claim
TS20700090 Edit subclaim
TS20700091 Edit task
The workflow IDs are:
WS20700070 Edit claim
WS20700071 Edit subclaim
WS20700072 Edit task
o To use the claim-specific columns in the workflow inbox, you have to define these in the worklist
client. Call up transaction SWL1.
o In addition to the modification-free enhancements supported in the SAP Business Workflow, you can
also extend data transferred from the Claims Management system to the workflow, on a
modification-free basis. Assign BRF expressions to BOR event parameters for this (IMG activity
Assign BRF Expression to BOR Event Parameters).

See also

You can find more information about the SAP Business Workplace in the application help, under the
following path: mySAP Technology Components -> -> SAP Web Application Server -> Business
Management -> Webflow Engine.

________________________________________________________________
SAP AG 14.10.2003 127
________________________________________________________________

Copyright
Copyright(c) 2003 SAP AG. All rights reserved.

Neither this document nor any part of it may be copied or reproduced in any form or by any
means or translated into another language, without the prior consent of SAP AG. The
information contained in this document is subject to change without notice.

SAP is a registered trademark of SAP AG.

All other products which are mentioned in this documentation are registered or not registered
trademarks of their respective companies.