How to Configure FSCM With Multiple Back-Ends

How to…

configure SAP Financial Supply Chain Man-

agement with multiple back-ends

ECC 6.0

SAP FSCM 6.0 (Dispute-, Credit-, Collections Management)

Enhancement Pack 4 for SAP ERP

Version Date

1.0 18/09/2008

SAP AG assumes no responsibility for errors or omissions in these materials.

These materials are provided “as is” without a warranty of any kind, either express or implied, in-

cluding but not limited to, the implied warranties of merchantability, fitness for a particular pur-

pose, or non-infringement.

SAP shall not be liable for damages of any kind including without limitation direct, special, indi-

rect, or consequential damages that may result from the use of these materials.

SAP does not warrant the accuracy or completeness of the information, text, graphics, links or

other items contained within these materials. SAP has no control over the information that you

may access through the use of hot links contained in these materials and does not endorse your

use of third party web pages nor provide any warranty whatsoever relating to third party web

pages.

SAP “How-To” papers are intended to simplify the product implementation. While specific product

features and procedures typically are explained in a practical business context, it is not implied

that those features and procedures are the only approach in solving a specific business problem

using SAP software. Should you wish to receive additional information, clarification or support,

please refer to SAP Professional Services (Consulting/Remote Consulting).

Value Scenario FSCM for Multi-Backend Systems

SAP AG July 2008 of 65

A. Dispute Management ..................................................................................... 4

1. Configuring ALE-Scenarios ............................................................................ 4

1.1. Definition of logical Systems (cross client setting) .......................................... 4

1.1.1 Definition of logical systems in AR-Systems ............................................. 4

1.1.2 Definition of logical systems in FSCM System (ECC6.0) .......................... 6

1.2 Assign Logical System to Client (cross client setting) ..................................... 7

1.2.1 Assign Logical System to Client in AR-Systems ....................................... 7

1.2.2 Assign Logical System to Client in the FSCM System (ECC6.0) .............. 7

1.3 Authorization Settings in AR-System AND FSCM-System ............................. 8

1.4 Setting up the Trusted Trusting RFC - Connections ..................................... 10

1.4.1 Definition of RFC-Connection from AR-Systems (trusting system) to

FSCM system (trusted system) .............................................................................. 10

1.4.2 Definition of RFC-Connection from FSCM system (trusting system) to AR

system (trusted system) ......................................................................................... 13

1.5 Determine RFC-Destinations for Method Calls ............................................. 13

1.5.1 Determine RFC-Destination for Method Calls in the AR-System ............ 13

1.5.2 Determine RFC-Destination for Method Calls in the FSCM-System ....... 14

1.6 Maintain Distribution model .......................................................................... 14

1.6.1 Create the Distribution model in the FSCM system ................................ 14

1.6.2 Settings in the AR system ...................................................................... 16

1.7 Configure Serialization ................................................................................. 16

1.7.1 Settings in the AR system ...................................................................... 16

1.7.2 Settings in the FSCM system ................................................................. 17

2 Business Customizing for Dispute Processing in the FSCM System ............ 18

2.1 Creating a Records Management System (RMS) ......................................... 18

2.2 Creating Element Types ............................................................................... 18

2.3 Create and Process Case Record Model ..................................................... 19

2.4 Create Element Type for Case Record......................................................... 23

2.5 Assign logical System to Element Types for SAP Business Objects ............ 24

2.6 Defining Case Types .................................................................................... 25

2.7 Process Integration ...................................................................................... 27

2.7.1 Define Derivation of Element Types ....................................................... 27

3 Customizing of the Process Integration with Accounts Receivable ............... 28

3.1 Defining Default Values ................................................................................ 29

3.2 Customer Disputed Objects in Dispute Cases .............................................. 29

3.3 Automatic Writing-off Dispute Cases ............................................................ 29



3.4 Automatic Document Changes ..................................................................... 29

3.5 Integration Biller Direct ................................................................................. 30

3.6 Assigning Open Items .................................................................................. 30

B. Collections Management .............................................................................. 31

C. Credit Management...................................................................................... 35

1. Check system settings for new credit management ............................................... 35

1.1 Check User Settings .................................................................................... 40

2 Business Customizing ............................................................................................ 41

2.1 Settings in ERP FI-AR ....................................................................................... 41

2.1.1 Assign Permitted Credit Control Area to company code ......................... 41

2.1.2 Assign sales area to credit control area .................................................. 42

2.1.3 Define Risk Categories ........................................................................... 42

2.1.4 Define automatic credit control in SD/FI System ..................................... 42

2.2 Settings in ERP FI-AR/SD ................................................................................ 46

2.2.1 Maintain Item Categories .............................................................................. 46

2.2.2. Maintain material master data in SD/AR ................................................. 49

2.3 Settings in SAP Credit Management (FIN-FSCMCR) ................................... 60

2.3.1 Define Events and Follow-On Processes ............................................... 61

2.3.2 Settings for a global credit limit check..................................................... 62



A. Dispute ManagementIf you use SAP Dispute Management in a multiple system scenario, first perform the set-

tings for the ALE scenario for SAP Dispute Management before starting the business

Customizing.

1. Configuring ALE-ScenariosIn order to implement SAP Dispute Management as a multi-system scenario, you have

to make all the settings required for the ALE scenario of SAP Dispute Management in

both the system for Dispute Case Processing, and in all the Accounts Receivable sys-

tems involved.

When you set up the RFC destinations for the ALE scenario, check whether the option of

trusted/trusting system relationship is relevant for you. For more details, please see the

SAP Library, under SAP NetWeaver Library SAP NetWeaver by Key Capability Applica-

tion Platform by Key Capability Platform-Wide Services Connectivity Components of

SAP Communication Technology Classical SAP Technologies (ABAP) RFC RFC Pro-

gramming in ABAP Maintain Remote Destinations Trusted System: Trust Relationships be-

tween SAP Systems.

In connection with the ALE scenario, see also the information in SAP Dispute Manage-

ment Configuration Guide for FI/AR page 16 ff. (SAP Dispute Management Configura-

tion Guide) as well as SAP Dispute Management Security Guide Release 6.0., available

on SAP Service Marketplace at sevice.sap.com/securityguide. Choose SAP ERP 2005 Security Guides SAP ERP 2005 Security

Guides SAP Dispute Management Security Guide.pdf.

1.1. Definition of logical Systems (cross client setting)

1.1.1 Definition of logical systems in AR-Systems

Enter the customizing activity ‘Define Logical System’ using the following customizing

path:



Define the client of the FI-system as logical system

Define the client of the FSCM-system that you want to link the FI-clients with as logi-

cal system

Settings have to be done in all AR-Systems



1.1.2 Definition of logical systems in FSCM System (ECC6.0)

Enter the customizing activity ‘Define Logical System’ using the following customizing

path:

Define the client of the FSCM-system as logical system

Define clients of the FI-systems that you want to link the FSCM-client with as logical

system



1.2 Assign Logical System to Client (cross client setting)

1.2.1 Assign Logical System to Client in AR-Systems

Enter the customizing activity ‘Assign Logical System to Client’ using the following

customizing path:

Enter or choose the clients of the AR System that you want to link to the FSCM sys-

tem

Assign the logical system that you defined for this client in the previous step to the

chosen client in the detail view (and also do the other settings for the client)

Settings for backend systems have to be done for all AR-Systems

1.2.2 Assign Logical System to Client in the FSCM System (ECC6.0)

Enter the customizing activity ‘Assign Logical System to Client’

Enter or choose the client of the FSCM System that you want to link to the FI sys-

tems



1.3 Authorization Settings in AR-System AND FSCM-System

The technical users for Dispute & Collections Management user (collections specialists,

collections supervisor, Dispute case processors etc.):

have to be defined in both systems (if possible with the same technical username)

AND

have to have an authorization related to the authorization object S_RFCACL

The following description shows how to set up a new profile including all necessary au-

thorizations for the authorization object S_RFCACL and how to assign it to the technical

user. This has to be done in both systems!

Choose transaction SU02 + press ‘create work area for profiles’:



Click ‘create’ (F6):

Enter the name of the profile that you want to create (‘Z_S_RFCACL’):

Enter ‘S_RFCACL’ as object and Authorization ‘S_RFCACL_ALL’ the status of

the profile is NEW and NOT SAVED:



Save the profile + activate it (two times) the status of the profile is now ACTIVE

and SAVED

Leave the transaction

Choose transaction SU01 and assign the profile you have defined.

1.4 Setting up the Trusted Trusting RFC - Connections

1.4.1 Definition of RFC-Connection from AR-Systems (trusting sys-tem) to FSCM system (trusted system)

First step is to create a dummy RFC-connection (SM59: with no logon settings /

trusted trusting settings) to the FSCM system in order to register the FSCM system as‘trusted system’ (smt1) in the AR systems:

enter transaction sm59 and choose button ‘create’ (F8):



enter a ‘dummy’ name for this connection, choose connection type 3 and enter the IP

address and the system number of the FSCM server in the technical settings

DON’T make any settings at the TAB Logon / Security

Save the data, leave transaction sm59 and choose transaction smt1

choose the button ‘create’ and enter the name of the dummy RFC-destination that

you’ve created in the previous step

confirm the pop up the system is jumping to the Logon screen of the FSCM sys-

tem (It’s doing a remote logon)

Enter the client of the FSCM system that you want to link and enter the username +

password that you have in this client of the FSCM system

Choose ‘enter’ to logon the FSCM system is now registered as ‘trusted system’ in

the AR system [you can check that again in transaction smt1 in the AR]



Second step is to create a ‘real’ trusted RFC-Connection in the AR system to the cor-

responding client of the FSCM system.

Go back to the AR system, enter transaction sm59 and create a new RFC-

Destination again.

enter the name of the logical system that you’ve created for the relevant client of the

FSCM system as name of the ‘real’ RFC-Connection, choose connection type 3 and

enter the IP address and the system number of the FSCM server in the technicalsettings

make the following settings at the TAB Logon / Security:

Trusted System: YES

Language: the language that you want to set up for the project

FLAG for ‘Current User’

Save the destination + choose the button ‘Remote Logon’

The system should automatically jump to the SAP Menu (Start SAP Easy Access)

of the defined client in the FSCM system without requiring another Logon

The same settings have to be done in all other AR- Systems!



1.4.2 Definition of RFC-Connection from FSCM system (trusting sys-tem) to AR system (trusted system)

The exactly same steps described in 4.1 have to be done in the FSCM system:

Dummy RFC-connection to be defined from FSCM to FI-AR

‘real’ trusted RFC-connection from FSCM to FI-AR

1.5 Determine RFC-Destinations for Method Calls

1.5.1 Determine RFC-Destination for Method Calls in the AR-System

The logical system for the corresponding FSCM client that has already been defined in

the various AR systems, has to be ‘linked’ to the defined RFC-Connection for the

FSCM client.

Enter transaction BD97 and set the cursor on the logical system defined for the

FSCM client.

Choose the Button ‘Standard BAPI destination’ and enter the existing RFC-

Destination for the FSCM Client as the valid ‘RFC destination for BAPI calls’:



Choose the Button ‘Standard dialog destination’ and enter the existing RFC-

Destination for the FSCM Client as the valid ‘RFC destination for dialog calls’.

1.5.2 Determine RFC-Destination for Method Calls in the FSCM-System

The exactly same steps described in 1.5.1 have to be done in the FSCM system foreach backend AR-System

1.6 Maintain Distribution model

1.6.1 Create the Distribution model in the FSCM system

Enter the FSCM system, transaction BD64 in the change mode ‘Change Distribution

Model’



Choose button ‘create model view’ and enter the short text and the name for the new

ALE model.

An entry for the new model is created

Mark this entry and choose ‘Add BAPI’

Define the ‘AttributesChange’ for the Object ‘Dispute’ as a method that has to be

called from the AR-system client as the sender in the FSCM system client as the re-

ceiver

Use the same procedure to define all methods that are called from the AR-system

[sender: AR-system & receiver: FSCM-system]:

Methods ‘AttributesChange ‘ (see screen), ‘Create’, ‘Display’, ‘GetdetailMulti’ and

‘Process’ for the Object ‘Dispute’

Method ‘SendItems ‘ for the Object ‘CollectionData’

Use the same procedure to define all methods that are called from the FSCM-system

[sender: FSCM-system client & receiver: AR-system:

Methods ‘StatusChanged ‘ (see screen) and ‘Writeoff’ for the Object ‘Dispute’

Method ‘AccessProcessReceivables’ for the Object ‘CollectionData’

Choose Environment Generate Profile and enter the name of your model view

(FSCM)

Execute the report (if you want do a check run first): the result list should show only

‘green’ entries

Go back to the screen for the Distribution model (BD64) and choose Edit Modelview Distribute

A pop up arises receiver of the model view is the logical system for the AR system

client



Confirm the pop up by pressing enter (the model view is now distributed to the AR

system)

The partner Profile is to be generated in all integrated AR-SystemsThe Distribution has to be done in all involved AR-Systems

1.6.2 Settings in the AR system

Enter transaction BD64 in the AR system: the FSCM distribution model that you cre-

ated in the FSCM system should be displayed (cannot be changed here)

Choose Environment Generate Profile and enter the name of your model view

(FSCM)

Execute the report (if you want do a check run first): the result list should show only

‘green’ entries

These settings have to be done in all AR-Systems

1.7 Configure Serialization

Using the serialization you can make sure that the system processes the IDocs of the

method PROCESS for a dispute case in the correct order. The BAPI of the method

PROCESS checks whether all IDocs of the preceding process steps have already been

posted. If this is not the case, the IDoc remains in the inbox as an error with status 51

and can be posted later once the preceding process steps have been posted. If you use

the program for writing off dispute cases automatically, then this situation can occur.

1.7.1 Settings in the AR system

Enter the following customizing path and choose activity ‘Activate Outbound Busi-ness Objects’:



Enter the Logical System name of the FSCM system client, assign the object type

BUS2022 and set the serialization flag

Settings to be done in all AR-Systems

1.7.2 Settings in the FSCM system

Enter the following customizing path and choose activity ‘Activate Inbound Busi-ness Objects’:

Enter the Logical System name of the AR system client, assign the object BUS2022

and set the serialization flag.



2 Business Customizing for Dispute Processing in theFSCM System

Business Customizing is aimed at adjusting the cross-company functions delivered to

the requirements of a specific company.

For the business Customizing for SAP Dispute Management, the SAP Implementation

Guide (IMG) contains two structures that you have to process completely. These struc-

tures are in different systems since you are using SAP Dispute Management in a multi-

ple system scenario. The Dispute Case Processing has to be configured in the central

FSCM System whereas the settings for Process Integration with Accounts Receivable

Accounting are to be done in the Accounts Receivable Systems.

The following steps are to be carried out in the central FSCM System.

2.1 Creating a Records Management System (RMS)

With the Records Management System (RMS), you define the areas that are visible in

Dispute Case Processing of SAP Dispute Management.

SAP Dispute Management delivers an RMS: UDM_DISPUTE. You can use this RMS or

create your own. Usually, it makes sense and reduces the effort required in configuring

the application if you use the RMS UDM_DISPUTE delivered.

If you want to create your own RMS, in Customizing for Dispute Case Processing,

choose the IMG activity Create RMS ID.

For more details, please see SAP Dispute Management Configuration Guide for FI/AR

page 20.

2.2 Creating Element Types

For SAP Dispute Management, you need certain element types in the Dispute Case

Processing system. When you create the element types, you define which types of ele-

ments can be used and which properties the individual element types have. Element

types are, e.g. Dispute cases, SAP business objects (for example, line item, accounting

document, account statement item, customer billing document), Documents and SAP

ArchiveLink objects.



Procedure

SAP Dispute Management delivers different element types in the standard.

In order to prepare the element types that have to be assigned to the different AR-

Systems, always use the element type delivered for the case record (starting with

UDM_SPS_) as a copy template and create your own element type for the case record

(be aware of naming convention at SAP). There are no further adjustments needed.

2.3 Create and Process Case Record Model

The case record model determines the structure of the dispute case record that contains

all element objects that are either part of the case or that contribute to the resolution of

the case. With different node types, you can define the type and order of the objects for



each case record (also linked objects) in the case record models. For more information,

please see SAP Dispute Management Configuration Guide for FI/AR, page 24 ff.

For more information on how to use the modeller, see the Records Management docu-

mentation in the SAP Library under Records Management Tools -> Processing Tool for

Record Models: The Records Modeller -> Creating a Record Model.

Procedure

You create or edit a case record model in the Implementation Guide for SAP Financial

Supply Chain Management under Dispute Management Dispute Case Processing

Element Types and Case Record Models Create and Process Case Record Model.

The case record model UDM_DISPUTE is only a sample. Use it as a copy template for

your own case record model. SAP reserves the right to make non-compatible changes to

the sample case record model.

This procedure for copying the case record model depends on the whether you use the

Records Management system (RMS) UDM_DISPUTE or your own Records Manage-

ment. Settings regarding these two scenarios can be found in the SAP Dispute Man-

agement Configuration Guide for FI/AR page

Activities

In the standard system, the case record model Dispute Management is in the RMS

UDM_DISPUTE, if you use Accounts Receivable Accounting (FI-AR).

You can use the activity Define Case Types to define which case record model should

be used in which case type.

Do not use the case record model Dispute Management delivered with the standard;

create your own case record model. The case record model Dispute Management is

only an example. SAP reserves the right to make non-compatible changes to the sample

case record model Dispute Management. When you create your own case record model,

you can use the case record model Dispute Management as template.

Copy case record model UDM_DISPUTE in RMS UDM_DISPUTE1. Choose the IMG activity Element Types and Case Record Model Create and Proc-

ess Case Record Model. The Case Management screen appears.

2. On the left side of the screen, choose with the quick info text Change RMS.

3. Enter RMS UDM_DISPUTE in the dialog box that follows and choose Continue.



4. On the left side of the screen, choose SAP Dispute Management Record and Case

Record Models, with the second mouse key click on Modeler for Case Records in Dis-

pute Management, and choose Find.

If your element type has a different name for the record modeler, a different name to

Modeler for Case Records in Dispute Management appears here.

The dialog box Search in Element Type “Modeler for Case Records in Dispute Manage-

ment” appears.

5. Choose Execute Search, and then double-click on the entry Dispute Management

(UDM_DISPUTE) in the results list. The system creates an entry for the case record

model Dispute Management in the screen area History on the left.

6. In the area History, click on the entry Dispute Management with the second mouse

button and choose Other Functions Copy Model.

7. To change the name of the case record model you have copied, click on the icon with

the quick info text Model Attributes in the center of the screen and overwrite the pro-

posed texts for the fields Short Description and Unique ID.

8. Confirm your entries and then save.

The system creates an entry for your copy in the screen area History on the left.

9. Adjust the copied case record model to suit your requirements.

On the right side of the screen are the element Types that contain only the name of an

SAP business object type so far. When you maintain the records model, in the field Ele-

ment Type enter an element type that you have created in the IMG activity Create Ele-

ment Type for this SAP business object type. You can create only one case model con-



taining all element types of each AR- backend System or you build up different different

case models that contain the corresponding element types.

10. Once you have completed and saved your adjustments, in the central area of the

screen choose Model Change Status. In the dialog box that appears, choose Status

Released and confirm this entry by clicking Continue. You do not have to set the status

Final in the record model.

11. If you want to transport your case record model, in the central area of the screen

choose Model Administration Transport Entry. In the subsequent dialog box,

choose the relevant transport request or create a new one.

Remember that you have to transport the case record model that you want to use in

productive operations to your productive system.

12. When you create your element type for the case records, enter the case record

model ID of your case record model in this element type. Choose the IMG activity Ele-

ment Types and Case Record Model Create Element Type for Case Record. You

must also enter the ID of your case record model in the case type you use (IMG activity

Case Types Define Case Types).

Copy case record model UDM_DISPUTE into your own RMS

For more information on creating and editing case record models, see the documenta-

tion for the IMG activity Element Types and Case Record Model Create and Process

Case Record Model and SAP Dispute Management Configuration Guide for FI/AR page

26 ff.



2.4 Create Element Type for Case Record

In this IMG activity you define one or more element types for case records.

Activities

1. Choose S_AREA_CMG.

2. Under the node SCMG_SP_CASE_RECORD choose the following node:

UDM_SPS_CASE_RECORD, using Accounts Receivable Accounting (FI-AR)

From the context menu, choose the function Copy and assign the name and description

(be aware of the SAP naming convention and use the prefixes Z_).

On the tab page Classification, change the following parameters:

a) RMS_ID: Enter the RMS ID defined in the IMG activity Create RMS ID (You can find

the ID under modeller History right mouse click Information technical Informa-

tion). If you have defined more than one RMS, you can enter more than one RMS ID.

However, you can also create different element types for the different RMS. Here you

have to add the Parameter ID from the case model created beforehand.

b) LOG_KEEP_DAYS (optional): Retention period for the log

c) LOG_LEVEL (optional): Level of detail for the log

3. On the tab page Connection Parameter Values, change the parameter: MODEL_ID.

Enter one or more records models that you want to use in these case records and that

you have created in the record modeller. Use the input help.



2.5 Assign logical System to Element Types for SAP Business

Objects

Since the SAP business objects for which you have created element types under Create

Element Types are in a different logical system to Dispute Case Processing, you need to

assign the logical system of the SAP business objects to the relevant element type.

Activities

For each element type that you have created for SAP business objects, and where the

business objects are in a different logical system to Dispute Case Processing, create an

entry with the following details:

Element Type ID: Element type of the business objects

LogSystem: Logical system of business objects regarding the different AR-Systems

(in the example Q42 and Q43 would be the AR-systems)

Before defining the case types, you can make further settings concerning Internal Num-

ber Range, Attribute Profile, Function Profile, Status Profile and Text Profile. For more

information, please see the Customizing IMG path of Dispute Case Processing as well

as SAP Dispute Management Configuration Guide for FI/AR page 28.



2.6 Defining Case Types

The case type is a central Customizing object in SAP Dispute Management and controls

the structure and properties of the dispute cases.

Activities

1. Consider whether you need different case types in your company. You need different

case types if the dispute cases (grouped per case type) have different Customizing set-

tings or if you want to differentiate between dispute cases with regard to authorizations.

2. Create the case type. To do this, copy the case type template F_DM or F_D2 (Cus-

tomer Disputed Objects) delivered by SAP Dispute Management and adjust your copy.

For more information, see the IMG of Dispute Case Processing under Case Types

Define Case Types.



3. To have the case type determined automatically during the creation of dispute cases

in Accounts Receivable Accounting, assign the required case types to the company

codes in your Accounts Receivable system. For more information, see the Implementa-

tion Guide of the Process Integration with Accounts Receivable under Define Default

Values when Creating Dispute Cases.

4. With a double click you get into the details of your case type. Under Element Type ID,

you have to choose your own ID. Under Case rec. model, you then have to assign the

RMS ID of your Case Record Model created beforehand.



2.7 Process Integration

2.7.1 Define Derivation of Element Types

The integration to accounting adds automatic links to SAP business objects to the dis-

pute case in different processes: If you use Accounts Receivable Accounting (FI-AR),

when you create a dispute case, for example, the selected open item is added under

Disputed Objects, and the customer under Business Partner in the dispute case. To add

links to these SAP business objects to the dispute case automatically, the system has to

determine the element type with which the object is to be added. You define the deriva-

tion of these element types in this IMG activity.

Activities

For the following SAP business object types (BKPF, BSEG, BUS4498, KNA1, VBRK,

SCASE), for each logical system for accounting, define the related element types that

you have created in the section Create Element Types (in our example this would be

UDM_SPS_* element types and the Z_ UDM_SPS_*element types).



The following settings (e.g. automatic status change, document category, ect.) can be

adjusted, but this is not a necessary step. For more information, please see IMG Cus-

tomizing Dispute Case Processing Process Integration.

3 Customizing of the Process Integration with AccountsReceivable

The following sections contain the special features for business Customizing for the

Process Integration with Accounts Receivable.

Before you can use SAP Dispute Management in A/R Accounting, you must activate

process integration in the AR- Systems. This has to be done in all involved AR-Systems.

Process integration for SAP Dispute Management is not activated in the standard sys-

tem! (IMG FSCM DM Process integration with AR).



The following settings have to be carried out in all AR-Systems involved in the multi-

backend scenario.

3.1 Defining Default Values

When you create a dispute case from transactions in Accounts Receivable, a dialog box

appears in which you enter the attributes of the dispute case. You can define default

values for these attributes in Customizing. You also define the basic values for creating

a dispute case (for example, case type) in the IMG activity Customizing of the Process

Integration with Accounts Receivable: Define Default Values for Creating Dispute Cases

or in the SAP Dispute Management Configuration Guide for FI/AR, page 35.

With double click on the company code, you can set different default values.

3.2 Customer Disputed Objects in Dispute Cases

For further information of Customer Enhancements, please follow the IMG activity: Proc-

ess Integration with Accounts Receivable Customer Disputed Objects in Dispute

Cases Customer Enhancements.

3.3 Automatic Writing-off Dispute Cases

For more details, please see SAP Dispute Management Configuration Guide for FI/AR

page 37.

3.4 Automatic Document Changes

When you create or change a dispute case, you can specify certain attributes to change

automatically in the related FI documents (for example, a dunning lock can be set) by

using the Document Changes from Dispute Cases function. In this activity you specify

which fields in the FI documents are changed when the triggering attributes in the dis-

pute case change. For more information, please see the documentation for the Docu-

ment Changes from Dispute Cases function in the SAP Library under IMG SAP Dis-

pute Management for FI-AR (FIN-FSCM-DM) -> Process Integration with Accounts Re-

ceivable Accounting Automatic Document Changes from Dispute Cases.



3.5 Integration Biller Direct

If you use SAP Biller Direct in connection with SAP Dispute Management, you must

carry out different steps. Please find more details under IMG Customizing Dispute

Management Process Integration with Accounts Receivable Accounting Integration

with SAP Biller Direct.

3.6 Assigning Open Items

This function is a prerequisite for an SD credit memo request assignment for one or

more open items in FI-AR. If a credit memo request is saved, a payment advice is cre-

ated. A background program clears the open items using the credit memo.

Activate assignment of open credit memos and payments: This step is required to acti-

vate the function (when creating a credit memo request from VA01, the button “Assign

credit memo” becomes available). This function is not activated in the standard system.

More details under IMG SAP Dispute Management for FI-AR (FIN-FSCM-DM) ->

Process Integration with Accounts Receivable Accounting Assignment of open credits

and payments.



B. Collections ManagementCollections Management was not included in this test scenario since there have been

other test scenarios for the case of a multi-backend system scenario. But regarding the

Customer Master Data replication, there are new developments that are to be explained

here. We now focus on the issue that Collections and Credit need cross system master

data replication and synchronization between Financials customers and business part-

ner. The following explanations are relevant for both FSCM components, Collections and

Credit Management.

A central master data management tool that is implemented and developed by the

customer party will enhance the efficiency and functionalities of SAP Collections Man-

agement. The recoding from customer code to Business Partner can be realised via

BAdI: FDM_PARTNER_MAPPI that can be found in the following path:

The BAdI enables a mapping of master data (located in different systems), so that ID of

customer equals ID Business Partner for example.



If there is no central master data management, SAP advises customers to use the Cus-

tomer Vendor Integration (CVI, available in ECC 6.0 on Basis 7.0) to replicate customers

to business partners. In this case, the standard business partner or customer ALE repli-

cation is used for the system integration.

In general a multi backend solution would only support the direction from FI to Collec-

tions Management (FIN Basis), as the ALE scenario does not allow applicable filter crite-

ria (number ranges).

In a multi backend system scenario this leads to the restriction of a 1:1 relation, which

means that only one Financials system can be assigned to one Collections/Credit Man-

agement system. The is based on the upcoming key conflict from FI to FSCM and

routing conflict from FSCM to FI due to lacking functionality of replication, synchroniza-

tion and harmonization. Since CVI only works in a single system environment, the mas-

ter data replication therefore is not possible due to overlapping customer keys < 6.0.

This raises several questions:

How to synchronize customers (in several FI source systems) with business partners

(in one target system)?

How to avoid duplicate keys in the target systems?

How to find the original FI system of a customer when changing a business partner?

Within the scope of EHP4, the model of PI and UKMS (Unified Key Mapping Service)

has been developed to clear this deficiency.

The UKMS provides an object-independent way to store and retrieve key mappings and

is available on Basis 7.0. Generally, it solves the key conflict by exchanging the key us-

ing ABAP-mapping in PI and using the relation stored in UKMS. Additionally, it solves

the routing conflict by using ABAP-routing in PI and using the relation stored in UKMS. In

detail, the process of UKMS for PI is split into following steps:

Creation of new object in source system (business partner data)

1. Creation of new object in source system

2. Send message to distribute object

3. Receiver determination in PI Configuration

4. Key mapping in ABAP class (default implementation)

a. Key not found in UKMS

b. Get number range and prefix from message type (new table)

c. Number get next



d. Add key mapping to UKMS

e. Return key to PI run time

5. Receive message in target systems

6. Creation of new object in target systems

Change of an existing object (in FI-AR system):

1. Change object in source system

2. Send message to distribute changes

3. Receiver determination in PI Configuration

4. Key mapping in ABAP class

• Key found in UKMS

5. Receive message in target systems

6. Change object in target systems

Change of an existing object (in FSCM system):

1. Change object in target system

2. Send message to distribute changes

3. Receiver determination in ABAP class

• Source system found in UKMS

4. Key mapping in ABAP class

• Key found in UKMS

5. Receive message in source systems

6. Change object in source systems

The message containing new business partners generates global unique keys for new

customers/ business partners. This key mapping is stored. Regarding the mapping for

messages coming from Financials, the key mapping has to be retrieved and the key in

the message is to be replaced with a global key. Reversely, mapping for messages

going to Financials requires that key mapping is retrieved and thereupon the global key

is replaced with key known in Financials. Finally, the route message to Financials sys-

tem needs to be found in mapping.

By the means of PI an enhanced replication of master data will be available which en-

sures the replication of customer data from different systems to different business part-

ners. As a result, Collections Management meets the needs of a multi-backend scenario,



even without a central master data management. But nevertheless, even with EhP4,

open items of identical customers (located in different FI-AR systems) will still be bun-

dled separately on the work list. This is due to the mapping that assigns different keys to

the business partners.

For more information regarding the settings for UKMS and PI, please see the guide UK-

MPI for Collection Management and the Configuration Guide for Collections Manage-

ment as well as the information in the IMG.



C. Credit Management

1. Check system settings for new credit managementThe new credit management (ERP2005) has to be activated in the system. Before you

try to make settings, please check the activation.

Open transaction SE18 and flag the BAdI: UKM_R3_ACTIVATE

Choose display button.

On the next screen, go to menu implementation overview.

You can also follow the IMG path:



Select BAdI ZUKM_R3_ACTIVATE and press enter.



Choose Tab: Interface

Double click on SET_ACTIVE and check coding if ERP2005 is active (coding should

look as follows).



Close and go back to initial screen of SE18. Display BAdI BADI_SD_CM.



Select ZBADI_SD_CM and display. Go to tab interface and make sure that the following

settings are made.



1.1 Check User Settings

Open transaction SU01. The following parameters are necessary and have to be added

if they aren’t already maintained. Check own entries.



2 Business Customizing

This section contains information about the Customizing settings in each system. Busi-

ness Customizing adjusts the company-neutral delivered functionality to the specific re-

quirements of the company.

2.1 Settings in ERP FI-AR

Log on to the SD/AR system. The following instructions are special for a multi-backend

scenario, but don’t cover the overall settings for credit management. For general infor-

mation regarding the set up of customizing, please see the Configuration Guide at the

service marketplace (page 200 ff.) as well as the Customizing path: IMG Financial

Supply Chain Management Credit Management Integration with Accounts Receiv-

able Accounting and Sales and Distribution.

2.1.1 Assign Permitted Credit Control Area to company code

Follow the following path: IMG Financial Supply Chain Management Credit Man-

agement Integration with Accounts Receivable Accounting and Sales and Distribution

Integration with Accounts Receivable Accounting Assign Permitted Credit Control

Areas to Company Code. Here you can assign your company code to a specific credit

control area.

You have possibly already made an assignment between the company code and credit

control area under Enterprise Structure -> Assignment -> Financial Accounting -> Assign

Company Code - Credit Control Area.

All other settings in this IMG activity (see screenshot) are to set up like in every imple-

mentation. For this settings, please get the information from the Configuration Guide on

the service market place.



2.1.2 Assign sales area to credit control area

Map your sales area to your credit control area by using the path: IMG Financial Sup-

ply Chain Management Credit Management Integration with Accounts Receivable

Accounting and Sales and Distribution Integration with Sales and Distribution As-

sign sales area to credit control area.

2.1.3 Define Risk Categories

In order to create an automatic credit control in different FSCM and FI-AR systems, risk

classes in SD/FI must be equal to the risk class in FSCM system. Check the settings in

both systems and make sure that the same classes are set.

IMG Financial Supply Chain Management Credit Management Integration with

Accounts Receivable Accounting and Sales and Distribution Integration with Sales

and Distribution Define Risk Categories

2.1.4 Define automatic credit control in SD/FI System

In order to create an automatic credit control in different FSCM and FI-AR systems, risk

classes in SD/FI must be equal to the risk class in FSCM system. Check the settings in

both systems.

Open transaction OVA8 in the AR system or follow the path: IMG Financial Supply

Chain Management Credit Management Integration with Accounts Receivable Ac-



counting and Sales and Distribution Integration with Sales and Distribution Define

Automatic Credit Control

Make the settings seen as follows:

Exemplary settings for risk class A are to be made like this:



These settings have to be done for all risk classes and credit groups.



2.2 Settings in ERP FI-AR/SD

2.2.1 Maintain Item Categories

Open transaction VOV7 or follow the path in the screenshot. Go to but-

ton and search for the category TAN. Select and double click.

Make sure that following settings are maintained. Save and go back to IMG.



Open transaction VOV8, choose and search for OR. Select and

double click to go into details. Check the settings and save. Go back to IMG.



2.2.2. Maintain material master data in SD/AR

First, you have to assign storage locations to a plant in the FI/SD system. Open Custom-

izing/ IMG and search for transaction: “assign plants and storage locations” or take the

following IMG path:

Name your plant and the storage locations of your SD/FI system.

Save the data and go back to IMG.



In case that there is no material maintained in the system, you have to create one. Open

transaction MM01. Choose a name for the material and execute (e.g. P-100).

Select all data and execute.

First press button and fill in the following data:



Enter any amount for the price of the material.



!



2.3 Settings in SAP Credit Management (FIN-FSCMCR)

You make the basic settings for SAP Credit Management (FIN-FSCM-CR) in the system

in which you have installed SAP Credit Management. For information about the general

Customizing of the individual IMG activities, see the Implementation Guide (IMG) under

Financial Supply Chain Management Credit Management Credit Risk Monitoring.

This refers to documentation for the settings regarding Master Data, Credit Limit Check

and Credit Exposure Update.



The following sections of this guide only provide additional information for the set up of a

multi-backend scenario and do not replace the documentation in the IMG or Configura-

tion Guide.

2.3.1 Define Events and Follow-On Processes

In this activity, you have to define the events for which the system is to trigger follow-on

processes. The following settings are essential and should be customized:



The two tables below should be considered as one unit. They show which events can

trigger follow-on processes. For more information, see the documentation for this IMG

activity.

An important event to prevent system errors is OBLIGO Credit Exposure Update with the

respective event type CS. The corresponding follow-on process is called RSEQ_ITEM

(Determine Credit Exposure of Item Again). Therewith, you manage that an error in the

sequence in credit exposure does not lead to a failure, but will determine credit exposure

of item again. Regardless the wrong document flows.

For more details regarding the other events and follow-on processes, please see the

Configuration Guide page 94 ff.

2.3.2 Settings for a global credit limit check

In order to manage a global credit limit for business partners that are located in different

FI-AR backend systems, but originally are the same customers, a few settings are nec-

essary in the FSCM system. In general, there are two possibilities to illustrate the sce-

nario of a global credit check.

2.3.2.1 Relationship

Imagine a business partner that is maintained and located in different FI-AR systems. In

order to enable a global credit check for the business partner, commitments can be put

together by way of hierarchy nodes that are based on built relationships. A relationship

exists between two business partners, whereas the business partner relationship cate-

gory characterizes the features of the relationship. In order to check a global commit-

ment, the keys of identical business partners have to be mapped to a common hierarchy

node. Thereby, it will be possible (when working with different systems) to maintain dif-

ferent customers/business partners with same keys as well as maintaining identical cus-

tomers/business partners with different keys. This is a manual setting and has to be car-

ried out for each business partner individually. Basis and prerequisite for the master data

mapping is the described setup of a XI connection via UKMS.

The relationship has to be created in the business partner master data in the central

FSCM system.

Log on to FSCM system and open transaction UKM_BP. Choose your business partner

and open the data in the UKM000 SAP Credit Management Role. Go to tab “Relation-

ships”.



You can now enter the desired relationship between several business partners in order

to combine the accounts.

Press button and the relationship will be created. Save the business

partner data. By the means of that, a global credit limit monitoring is possible, although

business partners have different keys coming from different backend systems.

2.3.2.2 Central master data management

The concept of a central master data management with harmonized keys for business

partners and customer number in all systems is recommended by SAP in order to fully

benefit from all advantages of SAP Credit Management und SAP Collections Manage-

ment. With the help of a central master management tool, implemented and developed



on the customer side, both customers and business partners get the same ID number,

so that a mapping of a customer and business partner numbers in both systems is not

necessary any longer.

In this manner, Credit Management is able to check global commitments per business

partner. The XI Mapping here will be default 1:1, so that, in case of identical keys for

customer and business partners, there is no further recoding required.



D. Biller DirectFor settings regarding Biller Direct, please see the configuration guide and the IMG.

How to Configure FSCM With Multiple Back-Ends

Documents

Transcript of How to Configure FSCM With Multiple Back-Ends