PUBLIC
Document Version: SAP S/4HANA 1909 – 2019-09-20
© 2019 SAP SE or an SAP affiliate company. All rights reserved.
SAP Credit Management Configuration Guide
THE BEST RUN
Content
1
SAP Credit Management Configuration Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1
Documentation Landscape for SAP Applications and Business Scenarios . . . . . . . . . . . . . . . . . . . . . 5
1.2
See Also. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3
Process Integration with Logistics and Finance Systems: Overview Overview. . . . . . . . . . . . . . . . . . . 7
1.4
Preparing Use of SAP NetWeaver Business Intelligence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.5
Setting Up Portal Connection (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.6
System and Component Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Integration with External Credit Agencies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Service interfaces: Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Integrating Services in the System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1.7
Integration of Systems in a Multiple-System Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Connecting Accounts Receivable Accounting in SAP S/4HANA Systems or as of SAP ERP 6.0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Connecting Accounts Receivable Acounting SAP ERP2004. . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Connecting Contract Accounts Receivable and Payable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Connecting Contract A/R & A/P from EHP4 for SAP ERP 6.0. . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Connecting Sales and Distribution in SAP S/4HANA Systems or as of SAP ERP 6.0. . . . . . . . . . . 29
Connecting Sales and Distribution SAP ERP 2004. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Connecting Customer Relationship Management (as of SAP CRM 2006s) . . . . . . . . . . . . . . . . . 32
Connecting Customer Relationship Management (SAP CRM 5.0 and SAP CRM 4.0 Service
Industries Add-On) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Replicating Master Data of Accounts Receivable Accounting (FI-AR) . . . . . . . . . . . . . . . . . . . . . 34
Replicating Master Data of Contract Accounts Receivable and Payable (FI-CA) . . . . . . . . . . . . . . 36
Replicating SAP CRM Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
1.8
Data Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
1.9
Providing Business Partner Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
1.10
Business Customizing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Settings in SAP Credit Management (FIN-FSCM-CR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Process Integration with SAP Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Defining Credit Master Data in the Business Partner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Workflow Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
1.11
Current Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Importing Exchange Rates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Recreating Data (Troubleshooting). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Credit Check If Technical Problems Occur. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Converting Organizational Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
2
PUBLIC
SAP Credit Management Configuration Guide
Content
Ensuring Data Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
SAP Credit Management Configuration Guide
Content
PUBLIC
3
1
SAP Credit Management Configuration
Guide
Purpose
This configuration guide applies to the use of SAP Credit Management with the corresponding release of the
related SAP application components.
Contents
The configuration guide describes which Customizing structures and activities you have to process to
implement the business process.
 Note
You can find information on theindividual activities in Customizing of your SAP system. This configuration
guide provides additional contexts and background that may be useful for Customizing.
Target Audience
● Technical consultants
● Application consultants
● Project team members during the implementation of an SAP solution
● IT department of the SAP customer
Integration
Documentation Landscape of SAP Solutions, Business Scenarios, and Business Processes
The system landscape has already been set up using the master guide and other documentation. For
information on further documentation and where the latest versions are published, see Documentation
Landscape of SAP Solutions and Business Scenarios [page 5].
Feedback on Configuration Guide
We would appreciate your feedback with a view to continually improving the usefulness of this configuration
guide. If you find errors in the configuration guide, enter a message in SAP Support Portal under the internet
for the SAP Credit Management (FIN-FSCM-CR) component.
address https://support.sap.com
4
PUBLIC
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
1.1
Documentation Landscape for SAP Applications and
Business Scenarios
This documentation gives you an overview of the most important sources of information that you need in
connection with SAP applications, business scenarios, and business processes. Make sure that you always use
the most up-to-date documents for your implementation.
Document Storage Location
Document
Location
Master Guide, Installation Guide, and Upgrade Guide
service.sap.com/instguides
Customizing
SAP System
Business Scenario Description, Business Process Descrip­
SAP Solution Manager
tion
SAP Library
help.sap.com
Comment: Also available under
Help
SAP Library
in
the SAP system
SAP Notes
service.sap.com/notes to search for notes
service.sap.com/instguides listed by installation and up­
grade guide
Platforms
service.sap.com/platforms
Sizing
service.sap.com/sizing
Security
service.sap.com/security
Description of the Documents
● Master Guide, Installation Guide, and Upgrade Guide
These documents describe how you install or upgrade the system landscape required for a business
scenario. The central initial access document for every SAP application is the Master Guide . For each
business scenario, it lists the SAP application components and third-party applications required, and refers
to their installation and upgrade guides. These guides are Component Installation Guides, Business
Scenario Upgrade Guides, and Component Upgrade Guides.
● Customizing
This tool enables you to adapt SAP systems to meet specific customer requirements. Customizing
contains the Customizing activities for all SAP components with general documentation. The structure is
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
5
component-oriented, and has no reference to a business scenario. If this reference is required, it is created
as follows: By the configuration documentation, with a textual link to Customizing, and by the content of
SAPSolution Manager that links to the Customizing activities for each business scenario and process.
● Business Scenario Description
This document describes how a business scenario runs once all components have been installed and
configured. For each business process of a business scenario there is a business process description and a
component view as graphical representation. This shows the process steps in the respective SAP
component.
● SAP Library
This documentation describes the different SAP components.
1.2
See Also
Definition
The following list contains useful information for the configuration:
Use
See Also
Information
Storage
SAP Credit Management Application Documentation
SAP Credit Management (FIN-FSCM-CR)
SAP Best Practices Explorer
Open the link and then select your release, your country and
language:
BI Business Content of SAP Credit Management
●
Basic Credit Management (BD6)
●
Advanced Credit Management (1QM)
SAP Library for SAP NetWeaver on the SAP Help Portal un­
der http://help.sap.com/netweaver
In the SAP Library, choose
NetWeaver by Key Capability
Key Capability
BI Content
Supply Chain Management
SAP NetWeaver Library
SAP
Information Integration by
Financials
SAP Financial
SAP Credit Management (FIN-
FSCM-CR)
Service Interfaces for SAP Credit Management
6
PUBLIC
Service interfaces: Overview [page 14]
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
Information
Storage
Documentation for SAP Exchange Infrastructure
SAP Library for SAP NetWeaver on the SAP Help Portal un­
der http://help.sap.com/netweaver
In the SAP Library, choose
NetWeaver by Key Capability
Capability
Documentation on Portal Content
SAP NetWeaver Library
SAP
Process Integration by Key
SAP Netweaver Exchange Infrastructure
SAP Library for SAP ERP on the SAP Help Portal under
http://help.sap.com/erp
In the SAP Library, choose
Cross-Application Functions in SAP ERP
Roles
Business Packages (Portal Content)
SAP Credit Management in the SAP S/4HANASecurity Guide SAP Help Portal under https://help.sap.com/s4hana
Product Documentation
Security Guide
 Note
Familiarize yourself with the documentation landscape for SAP solutions, business scenarios, and
business processes. For more information on the documentation available and where the latest versions
are published, see Documentation Landscape of SAP Solutions and Business Scenarios [page 5].
1.3
Process Integration with Logistics and Finance
Systems: Overview Overview
SAP Credit Management provides direct integration with the Sales and Distribution (SD), Accounts Receivable
Accounting (FI-AR) and Contract Accounts Receivable and Payable (FI-CA) processes. This ensures full
monitoring of the credit risk from order entry through to invoice payment by the customer.
You have the following integration options for SAP Credit Management:
SD (S/4HANA 4.6C, S/4HANA Enterprise, SAP ERP 2004, SAP ERP 6.0 and
its enhancement packages)
● Credit limit check on creating or changing sales documents, deliveries and service orders
● Credit exposure report on saving a sales document
● Credit exposure report on saving a delivery
● Credit exposure report on creating a billing document
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
7
Restrictions
The credit limit check and credit exposure update when you create or change a delivery or a service order are
only available from SAP ERP 6.0.
FI-AR (S/4HANA 4.6C, S/4HANA Enterprise, SAP ERP 2004, SAP ERP 6.0
and its enhancement packages)
● Regular credit exposure report for open customer line items
● Regular update of the payment behavior summary in SAP Credit Management based on payment
information
 Note
For a process description of the integration of SAP Credit Management with the SD and FI-AR components,
see the documentation for SAP Credit Management in the SAP Library.
Industry Release of Contract Accounts Receivable and Payable (FI-CA 4.72,
SAP ERP 6.0 and its enhancement packages)
● Regular credit exposure report for open customer items on a totals item basis
● Regular update of the payment behavior summary in SAP Credit Management
● Import of FI-CA creditworthiness to the master data of SAP Credit Management
● Support of commitment query of SAP Credit Management
● Support of partner messages of SAP Credit Management
SAP CRM (4.0 Service Industries Add-On, SAP CRM 5.0, SAP CRM 2006s,
SAP CRM 2007)
● Customer credit limit check on creating or changing a CRM sales order (Order Management)
● Credit exposure update when saving a CRM sales order (Order Management)
● Display of master data from SAP Credit Management in SAP CRM
Restrictions
The integration with CRM 4.0 is available with the Industry Add-On for CRM 4.0.
You can currently only connect a CRM system as part of a customer project. An exception exists as of SAP
CRM 2006s for telecommunications and utilities.
The integration of CRM service orders has not yet been implemented.
8
PUBLIC
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
1.4
Preparing Use of SAP NetWeaver Business Intelligence
Use
In SAP Credit Management you can use Business Content to evaluate your credit management data. The
following analysis scenarios are provided:
● Credit Profile
● Credit Risk
● New Rating and Simulation Analysis
● Business Partner Rating
The settings you have to make to use Business Content for SAP Credit Management are described in this
section.
 Note
For more information about SAP NetWeaver Business Intelligence (SAP NetWeaver BI) , see SAP Library
under
SAP NetWeaver Library
Capability
SAP NetWeaver by Key Capabilities
Information Integration by Key
.
● For information about configuration, see Business Intelligence .
● For information about BI Content of SAP Credit Management , see
Financial Supply Chain Management
BI Content
Financials
SAP
SAP Credit Management (FIN-FSCM-CR).
Prerequisites
You use SAP NetWeaver BI .
Procedure
1. Your SAP NetWeaver BI runs in a separate system, the BI System . This is separate from the OLTP systems
in which you run Dispute Case Processing and Process Integration with Accounts Receivable. You need to
set up a connection between the source system and the BI system for each OLTP system that you run for
SAP Credit Management .
For more information, see the SAP Library for Business Intelligence under
Acquisition
Source System
Data Warehousing
Data
Data Warehousing
Data
Create SAP Source System.
2. In each OLTP system, transfer the DataSources to the active version.
For more information, see the SAP Library for Business Intelligence under
Acquisition
Data Extraction from SAP Source Systems
DataSource
Transferring Business Content
DataSources into Active Version.
For the list of existing DataSources see the BI Content of Credit Management (FIN-FSCM-CR) detailed
above.
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
9
3. In the BI system, activate the Business Content for SAP Credit Management.
For more information, see SAP Library for Business Intelligence under
Warehouse Management
Business Content (Versions)
Data Warehousing
Data
Installing Business Content.
4. Replicate the DataSources from the OLTP system to the BI system.
For more information, see the SAP Library for Business Intelligence under
Acquisition
Source System
Data Warehousing
Data
Connection between Source System and BW.
5. By planning InfoPackages for the different InfoSources, you can load data into the BI system. Use either the
full update or the delta update.
For more information about scheduling InfoPackages, see SAP Library for Business Intelligence under
Data Warehousing
1.5
Data Warehouse Management
Scheduler (3.x)
Schedule InfoPackage
.
Setting Up Portal Connection (Optional)
Use
In SAP Credit Management you can use a wide range of analysis and processing functions in SAP NetWeaver
Portal .
For more information about Business Package for Credit Manager (SAP ERP) 1.4, see the SAP Library under
Roles
1.6
Business Packages (Portal Content)
.
System and Component Landscape
You can use SAP Credit Management and other integrated components in a single system landscape or a
multiple system landscape. You can collect, manage, and analyze credit information from connected systems
and components centrally; this architecture also enables you to distribute and use the credit information
effectively in the systems and components connected.
 Example
Examples of the cross-system/component information flow are:
● Credit exposure update from Accounts Receivable Accounting (FI-AR) to SAP Credit Management
● Credit check in SAP Credit Management on creation of a sales order in Sales and Distribution (SD)
● Update of the credit exposure in SAP Credit Management based on data from Sales and Distribution
(SD) and Accounts Receivable Accounting (FI-AR)
The data exchange is processed via XML interfaces, which means that you can connect both SAP and non-SAP
systems. For a list of the interfaces used, see Service Interfaces: [page 14]. Overview [page 14]
The exchange of messages can be made using SAP NetWeaver Process Integration (PI in the following) or – for
all synchronous and for certain asynchronous service interfaces – direct using the Web Services Reliable
Messaging protocol as point to point connection. This option is available not just in a one system landscape but
also if you are using central SAP Credit Management in a multiple system landscape, in which there is a
10
PUBLIC
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
separate system for Contract Accounts Receivable and Payable (FI-CA) or several separate systems for
Accounts Receivable Accounting (FI-AR).
For a one system landscape, you are advised to use the simplified Web service configuration with a local
shortcut.
For additional information which service interfaces allow point to point connection using the Web Services
Reliable Messaging (WS-RM) protocol, see also Service Interfaces: [page 14]. Overview [page 14]
 Note
For more information about Web Services, see:
● SAP NetWeaver Library under
Capability
ABAP Technology
SAP NetWeaver by Key Capability
ABAP Workbench (BC-DWB)
Application Platform by Key
ABAP Workbench Tools
Web
Services
● SAP NetWeaver Knowledge Center on SAP Help Portal under
Warehouse
SAP NetWeaver BI Content
Administration of SAP NetWeaver IT Scenarios
Tasks
Technology Platform
SAP Business
SAP NetWeaver Technical Operations Manual
Enabling Enterprise Services
Special Administration
Configure Web Service Runtime
System and Component Architecture for Multiple System Scenarios
The following figure gives you an overview of the maximum connection options and data flows that the system
architecture of SAP Credit Management provides.
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
11
System Requirements and Prerequisites for Multiple System Scenarios
The following table provides an overview of all components and systems that you have to or can connect in SAP
Credit Management.
 Note
You can connect either Accounts Receivable Accounting (FI-AR) or Contract Accounts Receivable and
Payable (FI-CA) as the SAP Financial Accounting components. For detailed information about the
integration of Contract Accounts Receivable and Payable, see the documentation for Contract Accounts
Receivable and Payable under Integration with SAP Credit Management.
Application Components and Minimum Release
Component/System
Minimum SAP Release
Comments
SAP Credit Management (FIN-FSCM-
Financial Basis 6.06
Mandatory
7.0
Mandatory
CR)
SAP NetWeaver Application Server
12
PUBLIC
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
Component/System
Minimum SAP Release
SAP NetWeaver Exchange Infrastructure 7.0 (without WS-RM)
Comments
Mandatory
7.0 SP14 (with WS-RM)
Accounts Receivable Accounting(FI-
4.6C; PlugIn 2004.1
AR)
Optional

Caution
Note that the integration for
Accounts Receivable
Accounting(FI-AR) in releases that
are earlier than SAP ERP 6.0 is sub­
ject to a restricted level of func­
tions. For more information, see
SAP Note 1096883.
Contract Accounts Receivable and
As of Industry Release 4.72
Optional
Payable (FI-CA) for the following solu­

tions:
Caution
●
SAP for Insurance
Note that the integration for
●
SAP Utilities
Contract Accounts Receivable and
●
SAP Telecommunications
●
SAP Media
●
Collection and Disbursement
Payable(FI-CA) in releases that are
earlier than SAP ERP 6.0 is subject
to a restricted level of functions.
(PSCD)
●
SAP Contract Accounts Receivable
and Payable (FI-CA)
Sales and Distribution (SD)
4.6C; PlugIn 2004.1
Optional

Caution
Note that the integration for Sales
and Distribution (SD) in releases
that are earlier than SAP ERP 6.0 is
subject to a restricted level of func­
tions. For more information, see
SAP Note 1096882.
SAP NetWeaver Business Intelligence
BI Business Content 3.5.2
Optional
SAP Customer Relationship
4.0; CRM Industry AddOn Edition 2004
Optional: for SAP for
Management (CRM)
Telecommunications and SAP for
Utilities released from SAP CRM 2006s,
for other projects only as a customer
project
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
13
Component/System
Minimum SAP Release
Comments
SAP Enterprise Portal
6.0
Optional
External Credit Information
Non-SAP system
Optional
Financial Accounting
Non-SAP system
Optional
Sales and Distribution
Non-SAP system
Optional
1.6.1 Integration with External Credit Agencies
You can integrate the services of external credit agencies using the solution SAP S/4HANA Cloud for credit
integration on SAP Cloud Platform.
For more information on how to integrate the credit integration solution with SAP Credit Management, see the
product documentation at https://help.sap.com/creditintegration .
1.6.2 Service interfaces: Overview
You can use the following service interfaces in SAP Credit Management:
Service Interfaces in the SAP Credit Management System (FIN-FSCM-CR)
Service Interface
Description
FICARatingReplicateQuery_In
Compare FI-CA creditworthiness with score from SAP Credit
Management
FICARatingReplicateResponse_Out
Compare FI-CA creditworthiness with score from SAP Credit
Management
CreditCommitmentNotification_In
Update credit exposure
CreditCommitmentQuery_Out
Request credit exposure
CreditManagementAccountByIDQuery_In
Provide credit master data
CreditManagementAccountChangeNotification_In
Change credit account data
CreditPaymentBehaviourSummaryNotification_In
Update payment behavior summary
CreditManagementAccountERPPaymentBehaviourSum
Request payment behavior summary
maryByDebtorPartyQueryResponse_Out
CreditWorthinessChangeInformation_Out
14
PUBLIC
Report events to connected systems
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
Service Interface
Description
CreditWorthinessCriticalPartiesQuery_In
Provide critical business partners
CreditWorthinessQuery_In
Carry out credit check
CreditAgencyReportERPDebtRecoveryScoreByDebto
Forward debt recovery score to FI-CA;
rPartyQuery_In
CreditAgencyReportERPDebtRecoveryScoreByDebto
Forward debt recovery score to FI-CA;
rPartyResponse_Out
CreditLimitChangeRequestERPByIDQueryResponse_
Read credit limit request
In
CreditLimitChangeRequestERPByIDQueryResponse_
Read credit limit request
Out
CreditLimitChangeRequestERPCreateRequestConfi
Create credit limit request synchronously
rmation_In
CreditLimitChangeRequestERPCreateRequestConfi
Create credit limit request synchronously
rmation_Out
CreditLimitChangeRequestERPUpdateRequestConfi
Change credit limit request synchronously
rmation_In
CreditLimitChangeRequestERPUpdateRequestConfi
Change credit limit request synchronously
rmation_Out
CreditLimitChangeRequestERPCheckQueryResponse
Change data of a credit limit request
_In
CreditLimitChangeRequestERPCheckQueryResponse
Change data of a credit limit request
_Out
CreditLimitChangeRequestERPBasicDataByElement
Find credit limit requests
sQueryResponse_In
CreditLimitChangeRequestERPCreateRequest_In
Create credit limit request asynchronously;
not WS-RM capable
CreditLimitChangeRequestERPChangeRequest_In
Change credit limit request asynchronously;
not WS-RM capable
CreditLimitChangeRequestERPCancellationReques
t_In
CreditLimitChangeRequestERPConfirmation_Out
Delete credit limit request asynchronously;
not WS-RM capable
Confirm credit limit request asynchronously;
not WS-RM capable
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
15
Service Interface
Description
DocumentedCreditDecisionERPBusinessTransactio
Create or change documented credit decision
n DocumentNotification_In
The service interfaces given above are located in the following namespaces:
● http://sap.com/xi/FSCM
● http://sap.com/xi/FSCM/Global
● http://sap.com/xi/FSCM/Global2
Service Interfaces in the Accounts Receivable (FI-AR) and Sales and Distribution (SD) System
Service Interface
Description
CreditCommitmentNotification_Out
Send credit exposure
CreditManagementAccountByIDQuery_Out
Request credit master data
CreditPaymentBehaviourSummaryNotification_Out
Send payment behavior summary
CreditWorthinessQuery_Out
Start credit check
DocumentedCreditDecisionERPBusinessTransactio
Create or change documented credit decision
nDocumentNotification_Out
The above service interfaces are found in the namespace http://sap.com/xi/PI/FIN/Operational/Global.
Service Interfaces in the Contract Accounts Receivable and Payable (FI-CA) System
Service Interface
FICARatingReplicateQuery_Out
Description
Compare FI-CA creditworthiness with score from SAP Credit
Management
FICARatingReplicateResponse_In
Compare FI-CA creditworthiness with score from SAP Credit
Management
CreditCommitmentNotification_Out
Send credit exposure
CreditCommitmentQuery_In
Provide credit exposure
CreditPaymentBehaviourSummaryNotification_Out
Send payment behavior summary
CreditWorthinessChangeInformation_In
Report events to connected systems
CreditWorthinessCriticalPartiesQuery_Out
Request critical business partners
CreditWorthinessQuery_Out
Start credit check
CreditAgencyReportERPDebtRecoveryScoreByDebto
Request debt recovery score;
rPartyQuery_Out
16
PUBLIC
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
Service Interface
Description
CreditAgencyReportERPDebtRecoveryScoreByDebto
Provide debt recovery score;
rPartyResponse_In
CreditManagementAccountERPPaymentBehaviourSum
Provide payment behavior summary
maryByDebtorPartyQueryResponse_In
The service interfaces given above are located in the following namespaces:
● http://sap.com/xi/FICA/Global
● http://sap.com/xi/FICA/Global2
● http://sap.com/xi/FICA
 Note
For documentation for the individual service interfaces, see the SAP Help Portal under http://
help.sap.com/erp . Call up the documentation, and select process component Credit Management.
The following figures give you an overview of the use of individual service interfaces for data exchange in SAP
Credit Management.
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
17
Choreography in SAP Credit Management (Part 1)
18
PUBLIC
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
Choreography in SAP Credit Management (Part 2)
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
19
1.6.3 Integrating Services in the System
Technical preparations
The settings described here have to be made by the system administrator:
● Configure SOAP Runtime [page 20]
● Activate HTTPS Port [page 21]
● Import Security Certificates (for Web service use without local shortcut) [page 21]
● Maintaining Table T000 [page 22]
● Set Up Web Service Configuration [page 22]
1.6.3.1
Configure SOAP Runtime
Use
Run the automatic setup of SOAP. If you experience errors, or not all of the settings detailed below are
automatically activated, you have to perform individual steps manually.
Procedure
Automatic Setup of SOAP Runtime
1. Call transaction SRT_TOOLS, and choose Technical Configuration of SOAP Runtime.
2. Choose Automatic Setup and Run Technical Setup.
3. Run the automatic setup.
4. In transaction SRT_TOOLS
Check Administrative Environment of SOAP Runtime , check whether all of
the required settings have been made. You have to do this client 000, and in those clients in which you are
working.
In particular, check whether the following areas are given the status
:
○ Service Destination
○ Inbound Destination
○ bgRFC Configuration
○ ICF Nodes
○ IDP Settings
○ Task Monitor
If any of the required settings have not been made following the automatic setup, you need to do them
manually.
Configure SOAP Runtime Manually
 Note
You can use SAP Note 1043195
20
PUBLIC
as a reference for the manual configuration of the SOAP runtime.
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
Before configuring any values manually, make the following settings:
1. Call transaction SRT_TOOLs and choose
Configuration
Technical Configuration of SOAP Runtime
bgRFC
Define Supervisor Dest. . Define and register the bgRFC_supervisor destination for
client 000.
2. Start the automatic setup again as described above.
3. In transaction SRT_TOOLS
Check Administrative Environment of SOAP Runtime , check whether all of
the required settings have been made. You have to do this client 000, and in those clients in which you are
working.
If the values have not been automatically set, you can make the settings manually as follows:
● Inbound Destination settings:
○ Define manually:
Transaction SRT_TOOLS
bgRFC Konfiguration
Define Inbound Dest.
○ Manual registration:
Transaction SRT_TOOLS
Technical Configuration of SOAP Runtime
Manual Setup . Activate the
Register Name of Inbound Destination checkbox.
● Make ICF settings:
Transaction SRT_TOOLS
Technical Configuration of SOAP Runtime
Under Web Service-Specifc ICF Settings, set the Make Settings checkbox.
In transaction SRT_TOOLS
Check Administrative Environment of SOAP Runtime , check whether all of the
required settings have been made.
1.6.3.2
Activate HTTPS Port
Carry out the following steps to activate the HTTPS port:
1. Call transaction SMICM.
2. Enter the ICM parameter under
Goto
Parameter
Change .
3. Save your entries.
4. Restart the application.
1.6.3.3
Import Security Certificates (for Web Service Use
Without Local Shortcut)
Use
Import the SSL and WS security certificates for the Web service concerned by using transaction STRUST. Add
the security certificates for SSL, and WS if necessary.
You can find instructions for this configuration in SAP Help Portal under Configuring the AS ABAP for
Supporting SSL.
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
21
You may have to restart the application server to ensure the changes become effective.
More Information
X.509-Based Log On to NW AS via the SAP Web Dispatcher, which you can find on SAP Help Portal under
Technology Platform
1.6.3.4
SAP Process Integration
Maintain Logical System
Use
Run transaction SE11 to check whether the logical system has been maintained correctly in table T000. If this
is not the case, enter the logical system for the clients that you use.
Procedure
1. Start transaction SM31.
2. Enter T000 in the Table/View field.
3. Choose Maintain.
4. On the "Change Clients" View: Overview screen, select the relevant client and choose
.
5. Enter your logical system in the Logical System field.
6. Choose
1.6.3.5
.
Set Up Web Service Configuration
In this section, you can find the settings for the Web service configuration.
If you are using a multiple-system scenario, you have to make the Web service configuration as described
below.
If you are using a one-system scenario, these settings are not relevant.
To be able to call the Web services, you need to add authorizations for the user roles in addition to the settings
in this section. For additional information, see the section Define Authorization for Web Services [page 45].
22
PUBLIC
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
Prerequisites
You have specified the logical system of your multiple-system scenario in the Business Add-In (BAdI)
UKM_R3_ACTIVATE. You can find this BAdI in the following places in Customizing:
●
Financial Supply Chain Management
Accounting
●
SAP Credit Management
Integration with Accounts Receivable
BAdI: Activation of SAP Credit Management
Financial Supply Chain Management
SAP Credit Management
Integration with Sales and Distribution
BAdI: Activation of SAP Credit Management
For more information, see the BAdI documentation.
Settings in a Multiple-System Scenario
1. In the receiver system:
1. Choose one of the following navigation options:
○ Transaction SOAMANAGER
○ Transaction SRT_TOOLS
WS Configuration
SOA Manager
2. On the initial page of SOA Management, choose Web Service Configuration.
3. In your receiver service, choose (Service Definition). If no connection has been maintained there,
choose Create Service.
 Note
You are recommended to configure the service with transport security setting SSL. You have to
enter the access URL for this connection in the sender service.
2. In the sender system:
1. Choose one of the following navigation options:
○ Transaction SOAMANAGER
○ Transaction SRT_TOOLS
WS Configuration
SOA Manager
2. On the initial page of SOA Management, choose Web Service Configuration.
3. Select your sender service (Consumer Proxy), and choose Define Logical Standard Port.
 Note
Your user requires the role SAP_FIN_FSCM_CR_USER.
4. Enter the URL, the computer name, and the port name of the receiver system. Save your entries, and
check the connection by pinging the receiver system via the sender system.
 Note
Alternatively, you can connect the systems in a multiple-system scenario with WS-RM or XI. For
additional information about this, see the section Connecting the Systems for Multiple System
Scenarios [page 24].
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
23
1.7
Integration of Systems in a Multiple-System Scenario
Use
This section contains information about connecting the systems in an SAP system landscape. This involves, for
example:
● Defining logical systems and assigning clients in the Online Transaction Processing System (OLTP)
● Determining the systems, servers, clients, distribution models and so on, in the system in which the SAP
application component is installed
● Completing the configuration settings and performing other activities required for the interactions in a SAP
system landscape
Activities
Perform the steps in these guidelines in the sequence in which they appear.
1.7.1 Connecting Accounts Receivable Accounting in SAP S/
4HANA Systems or as of SAP ERP 6.0
Use
To update in SAP Credit Management items and payment behavior summaries from Accounts Receivable
Accounting (FI-AR) in the SAP S/4HANA system or as of SAP ERP Release 6.0, use service interfaces to
connect your FI-AR system to the SAP Credit Management system.
For additional information about the following service interfaces, see http://help.sap.com/erp
documentation for the enterprise services of process component Credit Management:
in the
● CreditCommitmentNotification_In
● CreditCommitmentQuery_Out
● CreditPaymentBehaviourSummaryNotification_In
Prerequisites
You have created the business systems concerned in the System Landscape Directory and are familiar with the
configuration environment of the Integration Builder.
For more information, see the SAP Library under
NetWeaver
Key Functional Areas of Process Integration
and Configuration Time
24
PUBLIC
SAP NetWeaver Library
Integration Builder
Key Functional Areas of SAP
SAP NetWeaver Exchange Infrastructure
Design
and also Configuration.
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
Procedure
If you use a PI server, proceed as follows:
1. Integrate the sender interface CreditCommitmentNotification_Out from the namespace http://
sap.com/xi/PI/FIN/Operational/Global with the receiver interface
CreditCommitmentNotification_In from the namespace http://sap.com/xi/FSCM/Global via
the receiver communication channel.
The sender is the FI-AR system and the receiver is the SAP Credit Management system.
Using this connection, you can now update commitment information from Accounts Receivable
Accounting to SAP Credit Management.
2. Integrate the sender interface CreditPaymentBehaviourSummaryNotification_Out from the
namespace http://sap.com/xi/PI/FIN/Operational/Global with the receiver interface
CreditPaymentBehaviourSummaryNotification_In from the namespace http://sap.com/xi/
FSCM/Global via the receiver communication channel.
The sender is the FI-AR system and the receiver is the SAP Credit Management system.
Using this connection, you can now update payment behavior summaries from Accounts Receivable
Accounting to SAP Credit Management.
If you use WS-RM, proceed as follows:
1. Create an endpoint for the receiver interface.
2. Create a logical port for the sender interface with the WSDL file of the endpoint.
1.7.2 Connecting Accounts Receivable Acounting SAP
ERP2004
Use
To update items and FI summaries from Accounts Receivable Accounting (FI-AR) Release SAP ERP 2004 in
SAP Credit Management, connect your FI-AR system to the SAP Credit Management system via PI interfaces.
For additional information about the corresponding service interfaces CreditCommitmentNotification_In,
CreditCommitmentQuery_Out and CreditPaymentRecordNotification_In, see the documentation of the
process component Credit Management under
help.sap.com
SOA
SAP ERP .
Prerequisites
You have created the business systems concerned in the System Landscape Directory and are familiar with the
configuration environment of the Integration Builder.
For more information, see the SAP Library under
NetWeaver
SAP NetWeaver Library
Key Functional Areas of Process Integration
and Configuration Time
Integration Builder
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
Key Functional Areas of SAP
SAP NetWeaver Exchange Infrastructure
Design
and Configuration.
PUBLIC
25
Procedure
If you use a PI server, proceed as follows:
1. Integrate the sender interfaceCreditCommitmentNotification_Out from the namespace http://
sap.com/xi/PI/FIN/Operational/Global with the receiver interface
CreditCommitmentNotification_In from the namespace http://sap.com/xi/FSCM/Global via the
receiver communication channel.
The sender is the FI-AR system and the receiver is the SAP Credit Management system.
Using this connection, you can now update liability information from Accounts Receivable Accounting to
SAP Credit Management.
2. Integrate the sender interface CreditPaymentRecordNotification_Out from the namespace http://
sap.com/xi/PI/FIN/Operational/Global with the receiver interface
CreditPaymentRecordNotification_In from the namespace http://sap.com/xi/FSCM/Global via the
receiver communication channel.
The sender is the FI-AR system and the receiver is the SAP Credit Management system.
Using this connection, you can now update FI summaries from Accounts Receivable Accounting to SAP
Credit Management.
If you use WS-RM, proceed as follows:
1. Create an endpoint for the receiver interface.
2. Create a logical port for the sender interface with the WSDL file of the endpoint.
1.7.3 Connecting Contract Accounts Receivable and Payable
Use
To integrate Contract Accounts Receivable and Payable (FI-CA) with SAP Credit Management, you have to
integrate your FI-CA system with the service interfaces of the system in which SAP Credit Management runs.
For additional information about the following service interfaces, see the documentation of the process
component Credit Management at
http://help.sap.com
SOA
SAP ERP :
● CreditCommitmentNotification_In
● CreditCommitmentQuery_Out
● CreditWorthinessCriticalPartiesQuery_In
● CreditWorthinessQuery_In
● CreditPaymentBehaviourSummaryNotification_In
● FICARatingReplicateQuery_In
● CreditWorthinessChangeInformation_Out
26
PUBLIC
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
Prerequisites
You have created the business systems concerned in the System Landscape Directory and are familiar with the
configuration environment of the Integration Builder.
For more information, see the SAP Library under
NetWeaver
SAP NetWeaver Library
Key Functional Areas of Process Integration
and Configuration Time
Integration Builder
Key Functional Areas of SAP
SAP NetWeaver Exchange Infrastructure
Design
and Configuration.
Make sure that the PI content of the software components FI-CA and FSCM is installed in the Integration
Repository of your PI server. You can access the PI content for Contract Accounts Receivable and Payable as a
patch on SAP Service Marketplace under the respective industry solution (for example SAP IS-T 6.00).
Procedure
If you use a PI server, proceed as follows:
1. Connect the sender interface CreditCommitmentNotification_Out from the namespace http://
sap.com/xi/FICA/Global to the receiver interface CreditCommitmentNotification_In from the
namespace http://sap.com/xi/FSCM/Global using the receiver communication channel. The sender is the
FI-CA system. The receiver is the SAP Credit Management system. Using this connection you can update
liability information from Contract Accounts Receivable and Payable in SAP Credit Management.
2. Integrate the sender interface CreditCommitmentQuery_Out from the namespace http://sap.com/xi/
FSCM/Global with the receiver interface Interface CreditCommitmentQuery_In from the namespace
http://sap.com/xi/FICA/Global via the receiver communication channel. The sender is the SAP Credit
Management system. The receiver is the FI-CA system. Using this connection, you can query credit
exposure information from SAP Credit Management in Contract Accounts Receivable and Payable
(commitment query).
3. Connect the sender interface CreditPaymentBehaviourSummaryNotification_Out from the
namespace http://sap.com/xi/FICA/Global to the receiver interface
CreditPaymentBehaviourSummaryNotification_In from the namespace http://sap.com/xi/FSCM/
Global using the receiver communication channel. The sender is the FI-CA system. The receiver is the SAP
Credit Management system. Using this connection, you can update payment behavior summaries from
Contract Accounts Receivable and Payable in SAP Credit Management.
4. Connect the sender interface FICARatingReplicateQuery_Out from the namespace http://
sap.com/xi/FICA/Global to the receiver interface FICARatingReplicateQuery_In from the namespace
http://sap.com/xi/FSCM/Global using the receiver communication channel. The sender is the FI-CA
system. The receiver is the SAP Credit Management system.
Using this connection, you can:
○ Import the FI-CA creditworthiness from Contract Accounts Receivable and Payable to SAP Credit
Management.
○ Query the current master data from SAP Credit Management to make the relevant master data
changes in Contract Accounts Receivable and Payable (to the contract account, for example).
5. Connect the sender interface FICARatingReplicateResponse_Out from the namespace http://
sap.com/xi/FSCM/Global to the receiver interface FICARatingReplicateResponse_In from the
namespace http://sap.com/xi/FICA/Global using the receiver communication channel. The sender is the
SAP Credit Management system. The receiver is the FI-CA system.
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
27
Using this connection, you can:
○ Import the score from SAP Credit Management to Contract Accounts Receivable and Payable.
○ Transfer the current master data from SAP Credit Management to make the relevant master data
changes in Contract Accounts Receivable and Payable (to the contract account, for example).
6. Connect the sender interface CreditWorthinessChangeInformation_Out from the namespace
http://sap.com/xi/FSCM/Global to the receiver interface CreditWorthinessChangeInformation_In
from the namespace http://sap.com/xi/FICA/Global using the receiver communication channel. The
sender is the SAP Credit Management system. The receiver is the FI-CA system. You can use this
connection to transfer information about events from SAP Credit Management to Contract Accounts
Receivable and Payable (such as changes to master data).
7. Connect the sender interface CreditWorthinessCriticalPartiesQuery_Out from the namespace
http://sap.com/xi/FICA/Global to the receiver interface
CreditWorthinessCriticalPartiesQuery_In from the namespace http://sap.com/xi/FSCM/Global
using the receiver communication channel. The sender is the FI-CA system. The receiver is the SAP Credit
Management system. Using this connection, you can query business partners marked for special attention
from Contract Accounts Receivable and Payable in SAP Credit Management.
8. Connect the sender interface CreditWorthinessQuery_Out from the namespace http://sap.com/xi/
FICA/Global to the receiver interface CreditWorthinessQuery_Out_In from the namespace http://
sap.com/xi/FSCM/Global using the receiver communication channel. The sender is the FI-CA system. The
receiver is the SAP Credit Management system. Using this connection, you can:
○ Query credit information for a business partner from Contract Accounts Receivable and Payable in SAP
Credit Management
○ Perform a credit check for a business partner from Contract Accounts Receivable and Payable in SAP
Credit Management
 Note
Please note that you have option of setting up a point to point connection using the Web Services
Reliable Messaging (WS-RM) protocol for all synchronous and for certain asynchronous service
interfaces.
If you use WS-RM, proceed as follows:
1. Create an endpoint for the receiver interface.
2. Create a logical port for the sender interface with the WSDL file of the endpoint.
1.7.4 Connecting Contract A/R & A/P from EHP4 for SAP
ERP 6.0
Connecting Contract Accounts Receivable and Payable for EHP4
1. Carry out the activities that are described under Connecting Contract A/R & A/P (FI-CA) as of SAP ERP
6.0 [page 26]. In addition, carry out the following activities:
2. Integrate the sender interface CreditAgencyReportERPDebtRecoveryScoreByDebtorPartyQuery_Out from
the namespace http://sap.com/xi/FICA/Global2 with the receiver interface
CreditAgencyReportERPDebtRecoveryScoreByDebtorPartyQuery_In from the namespace http://
sap.com/xi/FICA/Global2 via the receiver communication channel.
28
PUBLIC
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
The sender is the FI-CA system. Receiver is the SAP Credit Management system.
Using this connection, you can request information about the debt recovery score from Contract Accounts
Receivable and Payable via SAP Credit Management.
3. Integrate the sender interface CreditAgencyReportERPDebtRecoveryScoreByDebtorPartyResponse_Out
from the namespace http://sap.com/xi/FSCM/Global2 with the receiver interface
CreditAgencyReportERPDebtRecoveryScoreByDebtorPartyResponse_In from the namespace http://
sap.com/xi/FICA/Global2 via the receiver communication channel.
The sender is the SAP Credit Management system. The receiver is the FI-CA system.
Using this connection, you can transfer the externally calculated debt recovery score from SAP Credit
Management to Contract Accounts Receivable and Payable.
Connecting Contract Accounts Receivable and Payable for EHP5
1. In addition to the activities described above under 'Connecting Contract Accounts Receivable and Payable
for EHP4', carry out the following:
2. Integrate the sender interface
CreditManagementAccountERPPaymentBehaviourSummaryByDebtorPartyQueryResponse_Out from the
namespace http://sap.com/xi/FSCM/Global2 with the receiver interface
CreditManagementAccountERPPaymentBehaviourSummaryByDebtorPartyQueryResponse_In from the
namespace http://sap.com/xi/FICA/Global2 via the receiver communication channel.
The sender is the SAP Credit Management system. The receiver is the FI-CA system.
Using this connection, SAP Credit Management can request payment behavior summaries in Contract
Accounts Receivable and Payable.
 Note
Please note that you have option of setting up a point to point connection using the Web Services
Reliable Messaging (WS-RM) protocol for all synchronous and for certain asynchronous service
interfaces.
1.7.5 Connecting Sales and Distribution in SAP S/4HANA
Systems or as of SAP ERP 6.0
Use
With the multi-system scenario, you use service interfaces to connect your SD system(s) for SAP S/4HANA or
as of Release SAP S/4HANA 6.0 with SAP Credit Management to enable the following:
● Performance of credit checks from sales orders
● Update of commitments from sales documents, deliveries and from billing documents not yet transferred
to accounting
● From SAP enhancement package 4 for SAP ERP 6.0, the system can create a documented credit decision if
there is a credit check with a negative outcome.
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
29
For additional information about the following service interfaces, see http://help.sap.com/erp
documentation for the enterprise services of process component Credit Management:
in the
● CreditWorthinessQuery_In
● CreditCommitmentNotification_In and CreditCommitmentNotification_Out
● DocumentedCreditDecisionERPBusinessTransactionDocumentNotification_In
Prerequisites
You have created the business systems concerned in the System Landscape Directory and are familiar with the
configuration environment of the Integration Builder.
For more information, see the SAP Library under
NetWeaver
SAP NetWeaver Library
Key Functional Areas of Process Integration
and Configuration Time
Integration Builder
Key Functional Areas of SAP
SAP NetWeaver Exchange Infrastructure
Design
and Configuration.
Procedure
If you use a PI server, proceed as follows:
1. Integrate the sender interface CreditWorthinessQuery_Out from the namespace http://
sap.com/xi/PI/FIN/Operational/Global with the receiver interface CreditWorthinessQuery_In
from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel.
The sender is the Sales and Distribution (SD) system and the receiver is the SAP Credit Management
system.
Using this connection, you can now carry out credit checks of sales orders.
2. Integrate the sender interface CreditCommitmentNotification_Out from the namespace http://
sap.com/xi/PI/FIN/Operational/Global with the receiver interface
CreditCommitmentNotification_In from the namespace http://sap.com/xi/FSCM/Global via
the receiver communication channel.
The sender is the Sales and Distribution (SD) system and the receiver is the SAP Credit Management
system.
Using this connection, you can now update commitment information from the sales documents to SAP
Credit Management.
3. From SAP enhancement package 4 for SAP ERP 6.0: Integrate the sender interface
DocumentedCreditDecisionERPBusinessTransactionDocumentNotification_Out from the
namespace http://sap.com/xi/PI/FIN/Operational/Global with the receiver interface
DocumentedCreditDecisionERPBusinessTransactionDocumentNotification_In from the
namespace http://sap.com/xi/FSCM/Global2 via the receiver communication channel. The sender is
the Sales and Distribution (SD) system and the receiver is the SAP Credit Management system.
Using this connection, you can now update data for the documented credit decision to SAP Credit
Management.
If you use WS-RM, proceed as follows:
1. Create an endpoint for the receiver interface.
30
PUBLIC
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
2. Create a logical port for the sender interface with the WSDL file of the endpoint.
1.7.6 Connecting Sales and Distribution SAP ERP 2004
Use
You connect your SD system(s) with Release SAP ERP 2004 with SAP Credit Management through service
interfaces to enable the following:
● Performance of credit checks from sales orders
● Update of liabilities from orders or from billing documents not yet transferred to accounting
For additional information about the corresponding service interfaces CreditCommitmentNotification_In,
CreditCommitmentQuery_Out and CreditPaymentRecordNotification_In, see the documentation of the
process component Credit Management under
help.sap.com
SOA
SAP ERP .
Prerequisites
You have created the business systems concerned in the System Landscape Directory and are familiar with the
configuration environment of the Integration Builder.
For more information, see the SAP Library under
NetWeaver
SAP NetWeaver Library
Key Functional Areas of Process Integration
and Configuration Time
Integration Builder
Key Functional Areas of SAP
SAP NetWeaver Exchange Infrastructure
Design
and Configuration.
Procedure
1. Integrate the sender interface CreditWorthinessQuery_Out from the namespace http://
sap.com/xi/PI/FIN/Operational/Global with the receiver interface CreditWorthinessQuery_In
from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel.
The sender is the Sales and Distribution (SD) system and the receiver is the SAP Credit Management
system.
Using this connection, you can now carry out credit checks from sales orders.
2. Integrate the sender interfaceCreditCommitmentNotification_Out from the namespace http://
sap.com/xi/PI/FIN/Operational/Global with the receiver interface
CreditCommitmentNotification_In from the namespace http://sap.com/xi/FSCM/Global via the
receiver communication channel.
The sender is the Sales and Distribution (SD) system and the receiver is the SAP Credit Management
system.
Using this connection, you can now update commitment information from SD (order values and values of
blocked billing documents) to SAP Credit Management.
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
31
1.7.7 Connecting Customer Relationship Management (as of
SAP CRM 2006s)
Use
You connect your CRM system(s) with SAP Credit Management through service interfaces to enable the
following:
● Performance of credit checks from CRM transactions
● Update commitments from CRM transactions or billing documents
● Display of master data from SAP Credit Management in SAP CRM
● Request for external information from SAP CRM
 Note
CRM is connected to SAP Credit Management in a customer project solution. An exception exists from
SAP CRM 2006s for telecommunications. An exception also exists as of SAP CRM 2006s for utilities,
but only for displaying master data from SAP Credit Management and requesting external information
from SAP CRM.
For additional information about the following service interfaces, see the documentation of the process
component Credit Management under
help.sap.com
SOA
SAP ERP
:
● CreditWorthinessQuery_In
● CreditCommitmentNotification_In
● CreditCommitmentQuery_Out
● CreditManagementAccountByIDQuery_In
Prerequisites
You are using SAP CRM 2006s or SAP CRM 2007.
You have created the business systems concerned in the System Landscape Directory and are familiar with the
configuration environment of the Integration Builder .
For more information, see the SAP Library under
NetWeaver
SAP NetWeaver Library
Key Functional Areas of Process Integration
and Configuration Time
Integration Builder
Key Functional Areas of SAP
SAP NetWeaver Exchange Infrastructure
Design
and Configuration .
Procedure
1. Integrate the sender interface CreditWorthinessQuery_Out from the namespace http://
sap.com/xi/CRM/Global with the receiver interface CreditWorthinessQuery_In from the namespace
http://sap.com/xi/FSCM/Global via the receiver communication channel.
32
PUBLIC
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
The sender is SAP CRM, and the receiver is SAP Credit Management .
Using this connection, you can now carry out credit checks from CRM transactions. You also need this
connection for requesting external information from SAP CRM.
2. Integrate the sender interface CreditCommitmentNotification_Out from the namespace http://
sap.com/xi/CRM/Global with the receiver interface CreditCommitmentNotification_In from the
namespace http://sap.com/xi/FSCM/Global via the receiver communication channel.
The sender is SAP CRM, and the receiver is SAP Credit Management .
Using this connection, you can now update commitment information from CRM transactions to SAP Credit
Management .
3. Integrate the sender interface CreditManagementAccountByIDQuery_Out from the namespace http://
sap.com/xi/CRM/Global with the receiver interface CreditManagementAccountByIDQuery_In from the
namespace http://sap.com/xi/FSCM/Global via the receiver communication channel.
The sender is SAP CRM, and the receiver is SAP Credit Management .
You can use this connection to display the master data from SAP Credit Management in SAP CRM.
1.7.8 Connecting Customer Relationship Management (SAP
CRM 5.0 and SAP CRM 4.0 Service Industries AddOn)
Use
You connect your CRM system(s) with SAP Credit Management through service interfaces to enable the
following:
● Performance of credit checks from CRM transactions
● Update commitments from CRM transactions or billing documents
 Note
CRM is connected to SAP Credit Management in a customer project solution.
For additional information about the following service interfaces, see the documentation of the process
component Credit Management under
help.sap.com
SOA
SAP ERP
:
● CreditWorthinessQuery_In
● CreditCommitmentNotification_In
● CreditCommitmentQuery_Out
Prerequisites
You use CRM 5.0 or have installed CRM 2004 Industry Add-On Edition on your CRM system with Release 4.0.
You have created the business systems concerned in the System Landscape Directory and are familiar with the
configuration environment of the Integration Builder .
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
33
For more information, see the SAP Library under
NetWeaver
SAP NetWeaver Library
Key Functional Areas of Process Integration
and Configuration Time
Integration Builder
Key Functional Areas of SAP
SAP NetWeaver Exchange Infrastructure
Design
and Configuration .
Procedure
1. Integrate the sender interface CreditWorthinessQuery_Out from the namespace http://
sap.com/xi/CRMFSCM/Global (CRM Release 4.0) or http://sap.com/xi/CRM/Global (CRM
Release 5.0) with the receiver interface CreditWorthinessQuery_In from the namespace http://
sap.com/xi/FSCM/Global via the receiver communication channel.
The sender is the CRM system and the receiver is the SAP Credit Management system.
Using this connection, you can now carry out credit checks from CRM transactions.
2. Integrate the sender interface CreditCommitmentNotification_Out from the namespace http://
sap.com/xi/CRMFSCM/Global (CRM Release 4.0) or http://sap.com/xi/CRM/Global (CRMRelease 5.0) with the receiver interface CreditCommitmentNotification_In from the namespace
http://sap.com/xi/FSCM/Global via the receiver communication channel.
The sender is the CRM system and the receiver is the SAP Credit Management system.
Using this connection, you can now update commitment information from CRM transactions to SAP Credit
Management .
1.7.9 Replicating Master Data of Accounts Receivable
Accounting (FI-AR)
Use
The master data required for SAPCredit Management is grouped in a separate business partner role based on
SAP Business Partner .
For the master data replication of customers in business partners, you can use the master data synchronization
of the SAP standard delivery. You can also use other technology for the master data replication, for example,
your own development.
SAPCredit Management provides the Business Add-In (BAdI) UKM_CONV2PARTNER for reading the mapping
information in order to be able to react to where the information is stored for the mapping of customers to
business partners.
Procedure
If you use the master data synchronization of the SAP standard delivery, perform the following Customizing
activities. To access the Customizing of Master Data Synchronization , choose
Components
34
PUBLIC
Master Data Synchronization
Cross-Application
.
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
Customizing Activities
Menu Path
Comments
Cross-Application Components
Synchronization
TOMER delivered with the standard exist.
Synchronization Control
Synchronization Control
Synchronization Objects
Cross-Application Components
Functions
Make sure that the synchronization objects BP and CUS­
Master Data
General Application
Postprocessing Office
Business Processes
Activate Creation of Postprocessing Orders
Cross-Application Components
Synchronization
synchronization cockpit for the master data synchroniza­
tion, activate the the creation of postprocessign orders for
the business processes of the software component AP-MD.
Set the activation indicator for the PPO object BP. This
Master Data
means that where synchronization attempts fail, PPO re­
Synchronization Control
Synchronization Control
Since the Postprocessing Office (PPO) is connected via the
quests where the errors are logged are written. The PPO re­
Activate PPO Requests for
quests are available via the Post Processing Desktop (trans­
action MDS_PPO2) or from the Synchronization Cockpit
Platform Objects in Dialog
(transaction MDS_LOAD_COCKPIT).
Cross-Application Components
Synchronization
Activate the master data synchronization for source object
Master Data
BP in target object CUSTOMER and source object CUS­
Synchronization Control
Synchronization Control
TOMER in target object BP.
Activate Synchronization
Options
Cross-Application Components
Define the business partner role categories and customer
Master Data
Synchronization
Customer/Vendor Integration
Business
Partner Settings
Settings for Customer Integration
account groups to be synchronized.
Configure BP Role Category for Direction BP to Customer
and Define BP Role for Direction Customer to BP
Cross-Application Components
Define the number assignment for both direction of the syn­
Master Data
Synchronization
Customer/Vendor Integration
Partner Settings
Settings for Customer Integration
Assignment for Customer Integration
Business
chronization.
Field
Assign Keys
Define Number Assignment for Direction BP to Customer
and Define Number Assignment for Direction Customer to BP
 Note
If you are using a central SAP credit management system for several FI systems, you can map customers
with an identical key to several business partners. To do this, you use the connection of the Unified Key
Mapping Service to SAPNetWeaver Process Integration (UKMS connection to SAPNetWeaver PI ).
For more information, see Customizing for SAP Credit Management under
Credit Risk Monitoring
Business Partner.
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
35
1.7.10 Replicating Master Data of Contract Accounts
Receivable and Payable (FI-CA)
Use
The master data required for SAPCredit Management is grouped in a separate business partner role based on
SAP Business Partner .
The business partner master data is distributed using the service interface ABABusinessPartner. For more
information about this interface, see XI Content for Business Partners .
Prerequisites
You are using a two-system scenario with the following constellation:
● System with FI-CA (industry components Utilities and Telecommunications )
● System with SAPCredit Management
● You are not using an SAP CRM system, that is, the business partner master records are not replicated
using CRM Middleware.
Procedure
1. Perform mapping between the roles Contract Partner (MKK) and Business Partner Credit Management
(UKM000) as follows:
○ Replication from FI-CA to SAP Credit Management : Mapping of role MKK to role UMK000
○ Replication from SAP Credit Management to FI-CA: Mapping of role UMK000 to role MKK
For this mapping, you have to make the following entries in the FI-CA system in the table
CRMC_BUT_CALL_FU ( Definition of Function Modules for BP Data Exchange ):
Event
Object
Item
Function Name
CRMIN
BUPA
2100000
BUPA_IN­
BOUND_MAP_ROLES_CM
CRMIN
BUPA
2200000
BUPA_IN­
BOUND_MAIN_ISU
CRMIN
BUPA
6666688
UKM_MAP_PROXY_TO_D
DIC_CMS_ADD
36
PUBLIC
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
Event
Object
Item
Function Name
CRMOU
BUPA
2100000
BUPA_OUT­
BOUND_BPS_MAP_ROLE_
CM
CRMOU
BUPA
2200000
BUPA_OUT­
BOUND_BPS_FILL_ISU
CRMIN
BUPA
0230000
BUPA_XI_MAP_NUM­
RANGE
1. For the replication of business partner master data from SAP Credit Management to FI-CA, you can also
create the SD business partner using a sample customer. To do this, implement and activate the BAdI
REF_CUSTOMER_XI_GET. In the implementation, in the method GET_REF_CUSTOMER, you have to set the
export parameter E_REFERENCE_CUSTOMER to the required SD sample customers.
2. Replicate the business partner data using the service interface ABABusinessPartner.
1.7.11 Replicating SAP CRM Master Data
Use
The master data required for SAP Credit Management is grouped in a separate business partner role based on
SAP Business Partner.
The master data is distributed using CRM Middleware.
Prerequisites
You use the following systems:
● A system with FI-CA (Telecommunications industry component) and SAP Credit Management as of SAP
ECC 6.0
● System with SAP CRM as of 2006s
 Note
CRM is connected to SAP Credit Management in a customer project solution. An exception is SAP CRM
2006s for telecommunications and utilities.
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
37
Procedure
When the business partner is replicated from SAP CRM, the business partner is created in the Credit Mgt
Business Part. role (UKM000) as well as in the Contract Partner role (MKK).
For this mapping, you have to make the following entries in table COM_BUPA_CALL_FU (Definition of Function
Modules for BP Data Exchange) in SAP ECC: Note the sequence of the table entries:
Entries in Table COM_BUPA_CALL FU
Event
Object
Item
Function Name
R3IN
BUPA
90005
COM_BUPA_MWX_MAP_UK
M
R3IN
BUPA
100000
COM_BUPA_MWX_MAP_MAI
N_CENTRAL
R3OUT
BUPA
150000
COM_BUPA_MWX_BPS_FILL
_ISU
R3OUT
BUPA
200000
COM_BUPA_MWX_BPS_FILL
_UKM
If you want the system to calculate the score and risk class automatically when it creates the Credit Mgt
Business Part. role (UKM000), you must carry out the following IMG activities in SAP ECC. To do this, choose in
the Implementation Guide for
Monitoring
Financial Supply Chain Management Credit Management
Credit Risk
.
Settings in Customizing of Financial Supply Chain Management
Activity
Master Data
Comments
Create Rule for Scoring and Credit Limit
Calculation
Credit Limit Check
Processes
Define Check Rules
Define Events and Follow-On Processes
Make sure that one of the rules is selected as the default rule
for new customers.
Make sure that one of the check rules is selected as the de­
fault rule for new customers.
Define these entries according to the table below.
Define Events and Follow-On Processes
Activity
Event Category
Follow-On Process
Maintain Business Partner (MAIN)
Score Invalid (S)
Determine Score (EVL_RATING)
Maintain Business Partner (MAIN)
Score Changed (IC)
Determine Risk Class (EVL_RISK_C)
38
PUBLIC
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
So that the system can create the credit segments correctly as part of a subsequent credit check, you must
define the following events and follow-on processes:
Activity
Event Category
Follow-On Process
Credit Check (REQUEST)
Score Invalid (S)
Determine Score (EVL_RATING)
Credit Check (REQUEST)
Score Changed (IC)
Determine Credit Limit of All Accounts
of Partner(EVL_LIMITS)
Credit Check (REQUEST)
Score Changed (IC)
Credit Check (REQUEST)
Credit Limit Invalid (CL)
Determine Risk Class (EVL_RISK_C)
Determine Credit Limit of Account
(EVL_LIMIT)
Using role grouping, you can create both roles MKK and UKM000 for the business partner. To fill the
mandatory field Rule for Scoring and Credit Limit Calculation automatically, in Customizing (transaction
UKM_LIMIT_RULE) select one rule as default.
1.8
Data Migration
Use
When you are using SAP Credit Management for the first time, you have to migrate data, meaning you have to
transfer and supplement the master data either from a different SAP system or from a non-SAP system.
In the SAP S/4HANA migration cockpit, you can find more information about the migration:
● Here you can find the latest Application Help topics about migration: SAP S/4HANA Migration Cockpit.
● General information about migration objects: Available Migration Objects.
● Information about the migration object specific to Credit Management: Customer - extend existing record
by Credit Management data.
In addition, you have the option of migrating from the old Credit Management (FI-AR-CR for SAP ERP with at
least ECC 6.0) to the new SAP Credit Management (FIN-FSCM-CR with SAP S/4HANA, on-premise edition). The
prerequisite for this is that you have installed SAP S/4HANA, on-premise edition on your system. The following
migration tools are available to you in Customizing under the following paths for Credit Management:
●
Conversion of Accounting to SAP S/4HANA
Customizing: Preparations and Migration
Preparatory
Activities and Migration: Customizing for Credit Management
●
Conversion of Accounting to SAP S/4HANA
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
Data Migration
Credit Management Migration
PUBLIC
39
1.9
Providing Business Partner Data
Use
The master data of SAP Credit Management is implemented as an enhancement for the SAP Business Partner.
For each business partner that you wish to monitor in SAP Credit Management, a master record of the SAP
Business Partner must exist in the system and client in which SAP Credit Management is run.
Integration
● If you install SAP Credit Management in a system in which business partner master data already exists,
SAP Credit Management can access this data without any problems. The system creates the credit master
data as an enhancement of the existing business partner master records.
● If you install SAP Credit Management in a system in which no business partner master records exist, such
as in a stand-alone system with its own server, you have to supply the business partner master records
with business partners or customers from another business system of your landscape (by means of
master data replication). With replication, copies of the master data of SAP Business Partner are created in
SAP Credit Management.
For more information about the distribution of SAP business partners, see the Implementation Guide
(IMG) for Cross-Application Components under
SAP Business Partner
Data Distribution .
Features
● For information on Accounts Receivable Accounting master data, see Replicating Master Data of Accounts
Receivable Accounting (FI-AR) [page 34].
● For information on Contract Accounts Receivable and Payable master data, see Replicating Master Data of
Contract Accounts Receivable and Payable (FI-CA) [page 36].
● For information about the master data of Customer Relationship Management, see Replicating Master Data
of SAP CRM [page 37].
Enriching business partners with attributes specific to credit management
This section is not relevant to you if, as part of your migration of Credit Management to SAP S/4HANA, you
have already performed the steps in Customizing under
Migration
Conversion of Accounting to SAP S/4HANA
Data
Credit Management Migration .
1. Define a default procedure for the business partners for calculating the score as well as a check rule. From
the SAP Easy Access screen, choose
Management
Accounting
Master Data Mass Changes
Financial Supply Chain Management
Credit
Rule for Scoring and Credit Limit Calculation and Check
Rule .
40
PUBLIC
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
2. Assign the role SAP Credit Management (UKM000) to the transferred business partners. Use transaction
UKM_MASS_UPD5 for this.
3. Recalculate the score. From the SAP Easy Access screen, choose
Management
Credit Management
Master Data Mass Changes
Accounting
Financial Supply Chain
Score .
4. Create the credit segments with the appropriate credit limit for the business partners. From the SAP Easy
Access screen, choose
Accounting
Master Data Mass Changes
Financial Supply Chain Management
Credit Management
Credit Limit .
Result
You have transferred the business partner data and, in addition to this, created the credit master data that you
require for SAP Credit Management.
1.10 Business Customizing
Use
This section contains information about the Customizing settings in each system. Business Customizing
adjusts the company-neutral functions delivered to the specific requirements of the company. This involves, for
example:
● Organizational unit Customizing
● Master data Customizing
● Process Customizing
Activities
Perform the steps in these guidelines in the sequence in which they appear.
1.10.1 Settings in SAP Credit Management (FIN-FSCM-CR)
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 Customizing of the individual IMG activities, see the Implementation Guide (IMG)
under Financial Supply Chain Management Credit Management Credit Risk Monitoring . The following
sections of the configuration guide provide additional information to supplement the documentation in the
IMG; this additional information does not replace the documentation in the IMG. The sections explain the
relationships and background of business Customizing and should help you to adjust these to benefit your
organization in the best possible way.
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
41
1.10.1.1 Activating the Business Partner Role for Credit
Management
Use
Your business partners’ Credit Master Data is the basis of SAP Credit Management; it controls all creditrelevant valuations and analyses. To be able to process your customer’s credit master data, the business
partner role for SAP Credit Management (UKM000BPartner Credit Management) must be active.
Procedure
1. On the SAP Easy Access screen, enterBUPT with no other characters in front.
The Business Partner: Task Menu screen appears.
1. Choose Business Partner Control Applications .
In the detail screen of the UKM application, set the Active indicator.
2. Choose Business Partner Control Screen Sequences .
Make sure that the BUP001 screen sequence contains the UKM100 screen.
3. Choose Business Partner
view UKM000:
Control
Divisibility
BP Views
.
Ensure the following entries for BP
○ Enter applications UKM and FS08 as calling applications.
○ As Subheader ID, enter subheader UKM110.
2. Use transaction SM30 to call up view V_TBZJ1C. Insert the following new table entry unless it already
exists:
○ Subheader: UKM110
○ Item: 6
○ Active: X
3. In Customizing, choose
Basic Settings
Cross-Application Components
Business Partner Roles
SAP Business Partner
Business Partner
Define BP Roles .
1. Insert the following new role category unless it already exists:
○ Role Type: UKM000
○ Title: SAP Credit Management
○ Name: SAP Credit Management
○ Differentiation Category: 9
○ Possible Business Partner Categories: Select all three categories.
You need differentiation category 9 to enter additional information for each segment.
2. Add the following business partner role unless it already exists:
○ BP Role: UKM000
○ Title: SAP Credit Management
○ Name: SAP Credit Management
○ BP Role Category: UKM000
○ Standard Assignment BP Role
42
PUBLIC
BP Role
BP Role Category : X
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
○ BP View: UKM000
Result
In the master data editing for the business partner, you can now edit the credit master data of your customers.
If you choose the role for Credit Management ( UKM000BPartner Credit Management), the system displays not
only the Credit Profile tab page but also the Credit Segment Data pushbutton.
1.10.1.2 Configuring Business Partner Additional Information
Use
You use credit-specific additional information to define collateral, credit insurance, check exceptions, and
negative credit events in the business partner master record. You define the additional information for SAP
Credit Management in the standard system in the additional information for the SAP Business Partner for
Financial Services. If your release is earlier than SAP NetWeaver Release 7.31, you have to implement and
activate Business Add-In (BadI) FSBP_BP3100_UPDATE as a prerequisite. Use the example coding for this as
set out in 842975
.
You can change the attribute selection via the methods FILL_ADD_INFOS and SAVE_ADD_INFOS of the
Business Add-In UKM_BP_ADD_FIELDS. For more information, see the Credit Management System and the
Implementation Guide for Credit Management under Credit Risk Monitoring → Enhancements → BAdI:
Additional Attributes for the Business Partner.
The following procedure describes the Customizing activities required in SAP Credit Management and in SAP
Business Partner for Financial Services.
Procedure
Navigation
Menu Path in SAP Customizing Implementation Guide (In
Transaction Code
Credit Management System)
Financial Supply Chain Management
Management
Credit Risk Monitoring
Credit
UKM_INFOCAT
Credit Limit Check
Define Info Categories
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
43
Menu Path in SAP Customizing Implementation Guide (In
Transaction Code
Credit Management System)
If you are using SAP Banking, then also:
SAP Banking
Services
Otherwise:
SAP Business Partner for Financial
Settings for Financial Services
Enhancement Options
SM30 with views V_TP19 and V_TP22
General Settings
Additional Information
Set
Information Category
1. In the Customizing activity Define Info Categories (UKM_INFOCAT), check whether the info types delivered
for the info category Collateral are sufficient for your needs; if necessary, define further info types for this
info category.
2. If you have created new info types in step 1, enter the corresponding entries in view V_TP19 with
transaction SM30.
 Note
In Business Partner Maintenance, you can now select collateral with additional info types.
3. In the Customizing activity Define Info Categories (UKM_INFOCAT), check whether the info types delivered
for the info category Negative Characteristic are sufficient for your needs; if necessary, define further info
types for this info category.
4. If you have created new info types in step 3, enter the corresponding entries in view V_TP19 with
transaction SM30.
 Note
In Business Partner Maintenance, you can now select negative credit events with additional info types.
5. In the Customizing activity Define Info Categories (UKM_INFOCAT), check whether the info types delivered
for the info category Credit Insurance are sufficient for your needs; if necessary, define further info types
for this info category.
6. If you have created new info types in step 5, enter the corresponding entries in view V_TP19 with
transaction SM30.
 Note
In Business Partner Maintenance, you can now select credit insurances with additional info types.
7. For the info category Check Exception, SAP delivers three info types (see Customizing activity Define Info
CategoriesUKM_INFOCAT). This means that you can temporarily deactivate up to three check steps in a
check rule for a business partner without having to define a new check rule.
If you want to deactivate more than three check steps, make additional entries here based on the existing
entries.
8. If you have created new info types in step 7, enter the corresponding entries in view V_TP19 with
transaction SM30.
 Note
44
PUBLIC
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
In Business Partner Maintenance, you can now deactivate more than three check steps.
This means that in business partner maintenance you can overrule the general settings for the check rule.
To do this, call up your business partner in the role SAP Credit Management (transaction BP), navigate to
the Credit Profile tab and select or deselect the check box in the Relevant column under Additional
Information.
9. If you have defined your own check steps (using customer-specific implementations of the Business AddIn UKM_CHECK_STEP) and also want to deactivate these check steps as check exceptions, then use
transaction SM30 to make entries for your check steps in the view V_TP22 based on existing entries.
You can now deactivate your own check steps using the check exceptions in the business partner master
record.
1.10.1.3 Define Authorizations for Web Services
Use
To be able to access the configured Web services of SAP Credit Management, you have to assign them to your
role.
Procedure
Carry out the following steps to do this:
1. Call transaction PFCG.
2. Either call up an existing role or create a new one.
3. On the Menu tab, choose
Transaction
Authorization Default .
4. In the Service window, select the following values:
○ Authorization Default: External Service
○ Type of External Service: WebService
5. Add the following Web services in the External Service column:
○ CREDITMANAGEMENTACCOUNTBYIDQU1/EXECUTE_SYNCHRONOUS
○ CREDITWORTHINESSQUERY_IN/EXECUTE_SYNCHRONOUS
○ DOCUMENTEDCREDITDECISIONERPBUS/EXECUTE_ASYNCHRONOUS
○ UKM_CREDITCOMMITMENTNO/EXECUTE_ASYNCHRONOUS
○ UKM_CREDITPAYMBEHAVSUMNO/EXECUTE_ASYNCHRONOUS
6. Choose Copy and save your entries.
More Information
Set Up Web Service Configuration [page 22]
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
45
1.10.1.4 Define Authorizations for Authorization Objects
Use
You can control the right of access to SAP Credit Management by assigning authorizations separately by credit
segment and activity - to the authorization object F_UKM_SGMT. This authorization object has the following
fields:
● Credit segment
● Activity, with the following definitions:
○ Add or create (01)
○ Change (02)
○ Display (03)
○ Delete (06)
○ Display change documents (08)
○ Release (43)
The role SAP_FIN_FSCM_CR_USER is delivered with all authorizations for this authorization object.
You can restrict the access to credit segment-independent master data of SAP Credit Management (for
example, the score) by using the authorization object for business partner roles (B_BUPA_RLT) with the role
Business Partner Credit Management (UKM000).
You can restrict the access to logs (application logs) of SAP Credit Management using the authorization object
S_APPL_LOG. This authorization object has the following fields:
● Application Log: Object Name
● Application Log: Subobject
● Activity, with the following definitions:
○ Display (03)
○ Delete (06)
For SAP Credit Management, the following forms are relevant for object name and subobject:
Object Name
Subobject
Meaning
FIN-FSCM-CR
BW-SCORING
Transfer of score from BW
FIN-FSCM-CR
COMMITMENT
Credit exposure update
FIN-FSCM-CR
CREDITCHECK
Credit check
FIN-FSCM-CR
MONITOR
Update of entries for external credit in­
formation
FIN-FSCM-CR
SEARCH_ID
ID search at the information provider
FIN-FSCM-CR
REPLICATE
Replicate the FI-CA creditworthiness
FIN-FSCM-CR
EVENTING
Logs of events
46
PUBLIC
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
Object Name
Subobject
Meaning
FIN-FSCM-CR-MASS
ERROR, ERROR_BIG, ERROR_PROG,
Logs of mass changes, can be differen-
ERROR_UPD, INFO, STATISTICS,
tiated by the severity of the error
SUCCESS, WARNING
Procedure
You can organize the authorizations of your users as follows:
Activities
Authorization
Restrict access to one or more credit
F_UKM_SGMT with specified credit seg­
segments
ment
Edit master data
F_UKM_SGMT
Activity
01
02
03
Display master data
F_UKM_SGMT
03
Delete master data
F_UKM_SGMT
06
Display change documents for master
F_UKM_SGMT
08
Release and reject credit limit changes/ F_UKM_SGMT
43
data changes
increases requested (dual control prin­
ciple)
Edit and display master data of SAP
B_BUPA_RLT with the BP role UKM000
Credit Management
Display and/or delete application logs
S_APPL_LOG with the object names
of SAP Credit Management
and subobjects listed above
03
06
Display and process documented credit S_SCMG_CAS and other authorization
decisions
objects of the Case Management com­
ponent
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
47
1.10.1.5 Define Events and Follow-On Processes
Use
Events can be linked with follow-on processes in SAP Credit Management. Events that occur in such follow-on
processes can also trigger follow-on processes. Depending on the activity performed, you can define whether
an event is to be considered – that is, whether the follow-on processes assigned to this event are to be
triggered or not.
Procedure
1. You make these settings in the SAP Credit Management system. In Customizing for SAP Credit
Management,choose
Credit Risk Monitoring
Processes
Define Events and Follow-On Processes .
2. Define the events for which the system is to trigger follow-on processes.
For more information, see the documentation for this Customizing activity.
The two tables below should be considered as one unit. They show which events can trigger follow-on
processes.
Table 1
Assignment Number of Follow-On
Name of Follow-On Process
Follow-On Process Key
1
Determine Credit Limit of Account
EVL_LIMIT
2
Determine Credit Limit of All Accounts
EVL_LIMITS
Process for Table 2
of Partner
3
Determine Score
EVL_RATING
4
Determine External Rating(s)
EVL_EXT_RT
5
Invalidate Credit Limit of Account
INV_LIMIT
6
Invalidate Credit Limit of All Accounts of
INV_LIMITS
Partner
7
Invalidate Score
INV_RATING
8
Call Business Add-In
BADI
9
Set “Special Attention” Indicator
SET_FLAG
10
Block Business Partner in Credit
SET_BLOCK
Segment
11
48
Perform credit check
PUBLIC
CRD_RECHCK
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
Assignment Number of Follow-On
Name of Follow-On Process
Follow-On Process Key
12
Check Request for Limit Change
LIMIT_REQ
13
Start workflow
WF
14
Process Credit Exposure in Correct
RESEQUENCE_ITEM
Process for Table 2
Sequence
15
Create or update documented credit
DCD_CREATE
decision for account
Table 2
Event
Value
Follow-On Process According to Assignment Number from Ta­
ble 1
1
Score Invalid
IS
Score Changed
IC
External Rating Invalid
ES
External Rating Changed
EC
Credit Limit Invalid
CL
Credit Limit Changed
Change to Credit Limit
2
3
4
5
x
x
6
8
9
10
11
12
13
x
x
x
x
x
x
x
x
x
x
x
x
x
x
7
x
x
x
x
LC
x
x
LR
x
Credit Refused
CF
x
x
x
Payment Behavior Summary:
VD
x
x
x
VO
x
x
x
VP
x
x
x
VX
x
x
x
x
x
14
15
x
x
x
x
x
Requested
Dunning Data Invalid
Payment Behavior Summary:
Due Date Invalid
Payment Behavior Summary:
Payment Data Invalid
Payment Behavior Summary:
Payment Behavior Index
Invalid
Generic Event Occurred
GE
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
x
x
x
x
x
x
x
x
x
x
PUBLIC
49
Event
Value
Follow-On Process According to Assignment Number from Ta­
ble 1
1
2
3
4
5
6
7
8
RC
x
x
x
x
x
x
x
x
x
Risk Class Changed
XC
x
x
x
x
x
x
Limit Utilization Changed
UC
x
Limit Utilization Exceeds
UU
x
UD
x
VC
x
Rule for Scoring and Credit
9
10
11
12
13
14
15
Limit Calculation Changed
x
x
x
x
x
x
x
x
x
100%
Limit Utilization Below 100%
x
x
Again
Payment Behavior Summary
x
x
x
x
x
x
x
x
x
x
Changed
Check Procedure Changed
TC
x
Error during Credit Exposure
CE
x
x
or Commitment Update
Error in Sequence
CS
x
Block Set in Credit
BL
x
x
Special Attention Indicator Set SP
x
x
x
Management
1.10.1.6 Settings for Documented Credit Decisions
You may be obligated to document credit decisions for legal reasons. This documentation is necessary if a
customer contests the reasons for a decision when they are disclosed. Documented credit decisions are used
to enable you to meet this obligation, and as a basis for the further processing of the documents.
There are two different types of documented credit decision:
● The documented credit decision for the document documents the data used as the basis of a negative
credit check, resulting in a blocked SD document.
● The documented credit decision for the account documents the status of a credit account at a particular
time, for example, if a credit analyst blocks the account.
50
PUBLIC
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
Activities
You make the settings for the documented credit decision in Customizing under the following path:
●
SAP Reference IMG
Financial Supply Chain Management
Credit Management
Credit Risk
Monitoring Documented Credit Decision
Some of these configurations for documented credit decisions are available in the UKM_DCD_CUST
Business Configuration Set (BC Set).
Note also the following settings:
● Further Settings for Documented Credit Decisions for Documents [page 51]
● Further Settings for Documented Credit Decisions for Accounts [page 53]
In the SAP Easy Access menu under
Management
Accounting
Financial Supply Chain Management
Credit
Documented Credit Decisions , the following applications are available:
● Cases in SAP Credit Management: Enables you to search for documented credit decisions in the system,
and to process them.
● My Documented Credit Decisions: Enables direct access to the documented credit decisions in a worklist
for which the user is assigned as credit analyst. Here the credit analyst can release or reject blocked SD
documents.
Related Information
Documented Credit Decision
1.10.1.6.1 Further Settings for Documented Credit Decisions
for Documents
Make additional settings for the documented credit decision for a document.
System Administration
● Make sure that the Adobe Document Server is available and that a virus scanner has been connected.
● In a multiple-system scenario:
○ Assign a copy of the business role SAP_FIN_CR_DCD_WF to the sales employee. This business role
contains all the necessary authorizations for creating documented credit decisions in SAP Credit
Management.
○ If you want to create or change a documented credit decision asynchronously, configure the service
DocumentedCreditDecisionERPBusinessTransactionDocumentNotification_In.
For more information, see Integrate Services in the System [page 20].
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
51
● In a one-system scenario:
○ Automatically created documented credit decisions are created with the workflow user SAP_WFRT.
Consequently, you need to assign a copy of the user role SAP_FIN_CR_DCD_WF to this user. This
business role contains all the necessary authorizations for creating documented credit decisions in
SAP Credit Management.
This setting is necessary so that a documented credit decision after a credit check can be created
automatically in Sales and Distribution (SD).
○ Prerequisite:
The SAP Business Workflow must be set up in Customizing under the following path:
NetWeaver
Application Server
Business Management
SAP Business Workflow
SAP
Maintain
Standard Settings
In addition, the relevant event linkage must be activated:
1. Enter transaction SWE2 or choose the following path in the SAP menu:
Tools
Business Workflow
Development
Administration
Event Manager
Type Linkages
2. Display the object type CL_UKM_DCD_WF_EVENT and make sure that the field Linkage Activated is
active.
The following settings need to have been made:
Field
Setting
Object Category
CL ABAP Class
Event
PUSH_DCD
Receiver Type
PUSH_DCD
Receiver Call
M Method
Event Delivery
Using tRFC (Default)
Linkage Activated
Yes
Behavior upon Error Feedback
3 Do Not Change Linkage
Receiver Status
0 No Errors
Customizing
To include particular liability categories in the period due, make the necessary settings under the following
path:
SAP Reference IMG
Credit Exposure Update
Financial Supply Chain Management
Credit Management
Credit Risk Monitoring
Define Liability Categories
Configuration in systems in which SD is running
● To be able to use documented credit decisions, you have implemented method DCD_ACTIVATE of
Business Add-In UKM_R3_ACTIVATE. In Customizing for SAP Credit Management, choose
52
PUBLIC
Integration
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
with Accounts Receivable Accounting and Sales and Distribution
Integration with Sales and Distribution
BAdI: Activation of SAP Credit Management .
● The system makes the documented credit decision data available in Business Add-In BADI_SD_CM. In
Customizing for SAP Credit Management, choose
Sales and Distribution
Integration with Accounts Receivable Accounting and
Integration with Sales and Distribution
Customer Enhancements
BAdI:
Connection of Sales and Distribution to SAP Credit Management .
 Recommendation
SAP recommends you to use implementation UKM_SD_FSCM_INTEGR1 for this BAdI. If you use your
own implementation instead, you have included the documented credit decision there yourself.
● A Business Add-In is available to change a documented credit decision before you send it. If this applies, in
Customizing for SAP Credit Management, choose
Sales and Distribution
Integration with Accounts Receivable Accounting and
Integration with Sales and Distribution
Customer Enhancements
BAdI: Sending
a Documented Credit Decision .
1.10.1.6.2 Further Settings for Documented Credit Decisions
for Accounts
Make additional settings for the documented credit decision for an account.
Customizing
● You have made the settings for the documented credit decision. To do this, in Customizing of SAP Credit
Management, choose Credit Risk Monitoring Documented Credit Decision .
In particular, you have defined a case type that is to apply to the documented credit decision. To do this, go
to Customizing for SAP Credit Management and choose
Decision
Credit Risk Monitoring
Documented Credit
Define Case Types for Documented Credit Decision .
● You have defined the follow-on process Create Documented Credit Decision (DCD_CREATE) for the change
to the credit master data. In Customizing for SAP Credit Management, choose
Processes
Credit Risk Monitoring
Define Events and Follow-On Processes .
1.10.2 Process Integration with SAP Systems
In addition to the settings in SAP Credit Management , you must also make settings for all other components
that you use for the business processes of SAP Credit Management .
The following components are affected:
● Accounts Receivable Accounting (FI-AR)
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
53
● Industry releases and Enhancement Packages of Contract Accounts Receivable and Payable (FI-CA) for the
following solutions:
○ SAP for Insurance
○ SAP Utilities
○ SAP Telecommunications
○ SAP Media
○ Collection and Disbursement (PSCD
○ SAP Contract Accounts Receivable and Payable (FI-CA)
● Sales and Distribution (SD)
● SAP Customer Relationship Management (CRM)
 Note
You can find information on the Customizing activities in your SAP system.
The following sections of the configuration guide provide additional information to supplement the
Customizing documentation; this additional information does not replace the Customizing documentation.
The sections explain the relationships and background of business Customizing and should help you to
adjust these to benefit your organization in the best possible way.
1.10.2.1 Making Settings in FI-AR as of SAP ERP 6.0 or for
SAP S/4HANA
Use
To update credit exposures and payment behavior summaries from one or more FI-AR systems from Release
SAP ERP 6.0 or for SAP S/4HANA in SAP Credit Management, you have to make the following settings.
You integrate FI-AR and SAP Credit Management by implementing Business Add-Ins (BAdIs) and by
performing some Customizing activities.
Procedure
Navigation
Menu Path in SAP Customizing Implementation Guide (in
Transaction Code
FI-AR system)
Enterprise Structure
Definition
Financial Accounting
Define Credit Control Area
54
PUBLIC
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
Menu Path in SAP Customizing Implementation Guide (in
Transaction Code
FI-AR system)
Enterprise Structure
Accounting
Assignment
Financial
Assign Company Code to Credit Control
Area
Financial Supply Chain Management
Management
Credit
Integration with Accounts Receivable
Accounting and Sales and Distribution
Accounts Receivable Accounting
Integration with
Define Credit Segment
Financial Supply Chain Management
Management
Credit
Integration with Accounts Receivable
Accounting and Sales and Distribution
Accounts Receivable Accounting
Integration with
Assign Credit Control
Area and Credit Segment
Financial Supply Chain Management
Management
Credit
Integration with Accounts Receivable
Accounting and Sales and Distribution
Accounts Receivable Accounting
Integration with
Define Reconciliation
Accounts without Credit Management Update
Financial Accounting
Accounts Payable
Accounts Receivable and
Business Transactions
Alternative Reconciliation Account
Ledger Transactions
OBL3
Postings with
Other Special General
Create List for Special General
Ledger
Settings for Credit Exposure Update
1. The credit exposure data is read online. If you do not want this to happen but would rather have replication
of the data, implement and activate Enhancement Spot BAdI UKM_R3_ACTIVATE. During the
implementation, in method FI_AR_UPDATE_MODE, you have to set the default value X for the export
parameter E_DIRECT_UPDATE and set the default value <empty> for the export parameter
E_E_READ_VIEW.
2. Select the credit-relevance of special general ledger indicators for which you require a credit exposure
update (optional). To do this, navigate from the special general ledger list to the details for a special general
ledger indicator, and in the properties set the indicator Consideration for Credit Limit.
3. During the update of open items to SAP Credit Management, the fields of the outbound interface of FI-AR
are determined according to the following rules:
○ Business Partner Number = Customer
○ Credit Segment = Segment assigned to the credit control area
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
55
○ Credit Exposure Category = 200
You can influence this behavior by implementing the method FILL_FIELDS of the BAdI UKM_FILL.
4. For postings in FI-AR, you can perform a credit check after you have entered the amount. If you want to
perform this credit check, change the message type of message UKM_PI 139. In the standard system the
credit check is not made.
Additional settings for updating the payment behavior summary
1. The payment behavior summary is determined from the modules delivered with the standard system. If
you want to determine further key figures or use other algorithms, use the implementation of BAdI
BADI_UKM_VECTOR_CALCULATE.
2. During the update of payment behavior summaries to SAP Credit Management, the fields of the outbound
interface of FI-AR are determined according to the following rules:
○ Business Partner Number = Customer
○ Credit Segment = Segment assigned to the credit control area that is assigned to the company code
updated to
You can influence this behavior by implementing the method FILL_VECTOR of Business Add-In UKM_FILL.
1.10.2.2 Making Settings in SD as of SAP ERP 6.0 or for SAP
S/4HANA
Use
The following settings are necessary for calling up the credit check when you create or change sales
documents and deliveries (from one or more SD systems) and to update commitments from SD in SAP Credit
Management. SD and SAP Credit Management are integrated by implementing various Business Add-Ins
(BAdIs) as well as by performing some Customizing activities.
Creating documented credit decisions in a multiple-system scenario for SAP S/4HANA systems or for systems
as of SAP enhancement package 4 for SAP ERP 6.0 for sales documents with a credit block.
 Note
The commitment update is not supported for service orders.
Prerequisites
In order to use the update options specified, you must also integrate your SD system with SAP Credit
Management using service interfaces (see configuration step Connecting Sales and Distribution from SAP ERP
6.0 [page 29]). You can execute these steps independently of each another and in any order.
You have configured the business partner data for SAP Credit Management (for additional information, see the
Configuration Guide for SAP Credit Management, SAP Enhancement Package 6 for SAP ERP 6.0
Data
Replication ).
56
PUBLIC
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
Procedure
Make Customizing Settings
Make the following entries in Customizing:
Navigation
Menu Path in Customizing of SD System
SAP Customizing Implementation Guide
Structure
Definition
Transaction Code
Enterprise
Financial Accounting
Define
Credit Control Area
Financial Supply Chain Management
Management
Integration with Accounts Receivable
Accounting and Sales and Distribution
Sales and Distribution
Integration with
Define Credit Segment
Financial Supply Chain Management
Management
Credit
Credit
Integration with Accounts Receivable
Accounting and Sales and Distribution
Sales and Distribution
Integration with
Assign Credit Control Area and
Credit Segment
Financial Supply Chain Management
Management
Credit
Integration with Accounts Receivable
Accounting and Sales and Distribution
Sales and Distribution
Integration with
Assign Sales Area to Credit Control
Area
Financial Supply Chain Management
Management
Integration with Accounts Receivable
Accounting and Sales and Distribution
Sales and Distribution
Integration with
Enter Settings
Financial Supply Chain Management
Management
Credit
Credit
Integration with Accounts Receivable
Accounting and Sales and Distribution
Sales and Distribution
Integration with
Define Active Receivable per Item
Category
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
57
Menu Path in Customizing of SD System
Financial Supply Chain Management
Management
Credit
Integration with Accounts Receivable
Accounting and Sales and Distribution
Sales and Distribution
Integration with
Define Credit Groups
Financial Supply Chain Management
Management
Transaction Code
OVAK
Credit
Integration with Accounts Receivable
Accounting and Sales and Distribution
Sales and Distribution
Integration with
Assign Sales Documents and
Delivery Documents
Financial Supply Chain Management
Management
Integration with Accounts Receivable
Accounting and Sales and Distribution
Sales and Distribution
Integration with
Define Automatic Credit Control
Financial Supply Chain Management
Management
Credit
Credit
Integration with Accounts Receivable
Accounting and Sales and Distribution
Sales and Distribution
Integration with
Define Risk Categories
 Note
The risk category in SD and the risk class in SAP Credit Management (FIN-FSCM-CR) are differentiated. To
ensure the integration of SD with SAP Credit Management, you have to define a risk class (FIN-FSCM-CR)
for every risk category (SD).
● You can define risk categories (SD) in Customizing under the following path:
Financial Supply Chain Management
Accounting and Sales and Distribution
Credit Management
Integration with Accounts Receivable
Integration with Sales and Distribution
Define Risk
Categories
● You can define risk classes (FIN-FSCM-CR) in Customizing under the following path:
Financial Supply Chain Management
Credit Management
Credit Risk Monitoring
Master Data
Create Risk Classes
If SAP Credit Management and your SD system are located in different systems, you have to define the
risk class (CR) in your SAP Credit Management system.
You can then assign a risk class (CR) to each business partner in SAP Credit Management. The system
operates as follows for the automatic credit check:
1. It calls the risk class (CR) of the business partner in SAP Credit Management.
2. It translates the risk class (CR) automatically into a risk category (SD). Example : Risk class (CR) A
becomes risk category (SD) A.
58
PUBLIC
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
3. It makes the automatic credit check as defined in the corresponding risk category (SD).
Implementing BAdIs
You can implement BAdI BAdI BADI_SD_CM. You can use the following methods:
Method
Description
FSCM_GET_MASTER_DATA
Determine master data of partner before credit check, in
particular the risk category
FSCM_CREDIT_CHECK_ORDER
Call credit check from order
FSCM_CREDIT_CHECK_DELVRY
Call credit check from delivery
FSCM_COMMITMENT_UPDATE_ORDER
Update new or changed order values
FSCM_COMMITMENT_UPDATE_DELVRY
Update new or changed delivery values
FSCM_COMMITMENT_UPDATE_INVOICE
Reduce order values during billing and create open billing
values if no immediate transfer to FI
FSCM_DISPLAY_CREDIT_MESSAGES
Control output of messages for credit check in dialog
FSCM_CREDIT_CHECK_SM_ORDER
Call credit check from service order
For sample code, see the implementation UKM_SD_FSCM_INTEGR1 (delivered inactive) that is also available
with SAP Note 1130061.
1.10.2.3 Make settings as of SAP CRM 2006s
Use
You require settings for the following transactions:
● The credit check when you create or change a CRM transaction (call up in one or more CRM systems)
● Update the CRM credit exposure in SAP Credit Management
● Display of master data of SAP Credit Management in SAP CRM
● Requesting external credit Information through SAP CRM for SAP Credit Management
 Note
CRM is connected to SAP Credit Management in a customer project solution. An exception exists as of
SAP CRM 2006s for telecommunications. An exception also exists as of SAP CRM 2006s for utilities,
but only for displaying master data of SAP Credit Management and requesting external information
using SAP CRM.
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
59
Prerequisites
In order to use the functions specified, you have integrated your CRM system(s) with SAP Credit Management
using service interfaces (see Connecting Customer Relationship Management (as of SAP CRM 2006s) [page
32]).
You have configured the business partner data in SAP Credit Management (see Providing Business Partner
Data [page 40]).
Procedure
Display of Master Data of SAP Credit Management in SAP CRM (available for Utilities and
Telecommunications
In the CRM system, make the required settings: You can find these in Customizing of Customer Relationship
Management under
Basic Functions
Credit Management
Business Partner Rating
Display Credit Master
Data from Credit Management System :
1. General Settings
2. Define Texts for Risk Classes and Make Categorization
3. Define Symbols for Categories of Risk Class
4. Define Texts for Displaying Credit Segment
5. Define Texts for Displaying Lock Reason
For more information, see the documentation for these Customizing activities.
Credit Check and Credit Exposure Update (available only for Telecommunications)
In the CRM system, make the required settings: Choose the following activities in Customizing of Customer
Relationship Management:
1.
2.
Basic Functions Credit Management Credit Check and Credit Exposure Update Edit Credit Group
Define a new credit group with check rule 02 . If you use this credit group for document types for which a
credit exposure update is to take place, set the Credit Update Active indicator.
Basic Functions
Credit Management
Credit Check and Credit Exposure Update
Assign Credit Group
to Item Type
Assign the new credit group to the item types for which a credit check is to be carried out.
3.
Basic Functions
Check in Transaction
Credit Management
,
Credit Check and Commitment Notification
Definition of Transaction Types
Activate Credit
Assignment of Business Transaction Types
Customizing Header
Activate the credit check for the transaction types for which a credit check is to be carried out.
4. To activate the update of commitments to SAP Credit Management, using transaction SM30, make two
new entries in table SMW3FDCUST.
Make the settings according to the following table:
60
PUBLIC
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
Field Name
Description
User Action and Values
BDOC_TYPE
BDoc Type
CMDOC_NOTIFY
FCTXT
Context
mBDOC notification (additional calls)
CNTR
Sequence
10
FNAME
Service Function
CRM_UPLOAD_FSCM_CR_SRV
ACTIV
Entry Active
X
Also make the following settings:
Field Name
Description
User Action and Values
BDOC_TYPE
BDoc Type
C MD OC_NOTIFY
FCTXT
Context
Multiple mBDOC notification (addi­
tional calls)
CNTR
Sequence
10
FNAME
Service Function
CRM_UPLOAD_FSCM_CR_SRV
ACTIV
Entry Active
X
Requesting External Credit Information through SAP CRM for SAP Credit Management
In the CRM system and ERP system, make the required settings: For more information, see the documentation
for this Customizing activity:
Business Partner Rating
Update of Credit Data
Customer Relationship Management
Basic Functions
Display Credit Master Data from Credit Management System
Credit Management
Define Profiles for
.
1.10.3 Defining Credit Master Data in the Business Partner
Use
In the master data of the business partner you define the following:
● Which rule is used to calculate the score, the risk class, and the credit limit?
Alternatively, you can define the score, risk class, and/or the credit limit manually.
● Which check steps are executed in a credit check for the business partner?
You can also define the following:
● Which customer credit group does the business partner belong to?
● Which analyst or analyst group is the business partner assigned to?
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
61
● Should credit checks also be carried out for additional business partners that are related to him or her?
● External credit information
● Collateral and credit insurance
● Negative credit events, block reasons, indicator for special attention
Prerequisites
● You have created a general master data record for the business partner (for example, category, name,
address).
● You have made the Customizing settings for the rule for scoring and credit limit calculation, the check
rules, and the risk classes.
● You have, if necessary, portrayed your analysts and analyst groups as business partners in the system.
● You have configured the Customizing of the customer credit groups, the block reasons, and the rating
procedures.
● If you want to use collateral, credit insurance, negative credit events, or business partner-specific check
exceptions, make sure that you have made the corresponding Customizing settings for the additional
information (see Configuring Business Partner Additional Information [page 43]).
● If you want to import external credit information automatically, make sure that the external information
providers are connected (see Integration with External Credit Agencies [page 14]).
Procedure
Navigation
Menu Path
SAP Menu
Management
Transaction Code
Accounting
Financial Supply Chain
Credit Management
UKM_BP
Master Data
Business Partner Master Data
1. Call up Business Partner Maintenance in the Business Partner Credit Management role. On the Credit Profile
tab page, enter a rule for scoring and credit limit calculation and a check rule. To have the system calculate
the score, choose Calculate with Formula.
2. If required, enter a customer credit group.
You can use the customer credit group as selection criterion in the transactions for mass changes to credit
master data.
3. If required, enter a business partner relationship of the Managed in Credit Management By category; to do
this, choose Relationships. The business partner that you refer to is an analyst or an analyst group. You can
restrict the relationship to one credit segment or it can be valid for all credit segments.
You can use the analyst or analyst group as selection criterion in the credit limit utilization list.
4. If required, enter business partner relationships of the type Higher Level Credit Account of or Lower Level
Credit Account of; to do this, choose Relationships. You can restrict the relationship to one credit segment
or it can be valid for all credit segments.
62
PUBLIC
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
In a credit check for a business partner, higher level credit accounts are also checked. This means that the
check can stretch over several hierarchy levels.
5. If required, enter external credit information or import it via the service interface.
You can use the external credit information as input parameter for scoring.
6. If required, under the additional information in the general data (valid for all credit segments there) or in
the data for a credit segment, enter collateral and/or credit insurance with amount and currency, and set
the relevance indicator and a validity interval.
In a credit check with the check steps Statistical Check of Credit Limit Utilization or Dynamic Limit Check
with Credit Horizon, before the comparison with the credit limit, the credit exposure is reduced by the
amount of the collateral and/or credit insurance if the indicator Consider Collateral or the indicator
Consider Credit Insurance is set in Customizing and the current date is in the validity period of the collateral
or credit insurance and the relevance indicator is set.
7. If required, under the additional information in the general data (valid for all credit segments there) or in
the data for a credit segment, enter check exceptions with a validity interval. The Information Type field is a
counter that enables you to enter several check exceptions.
In a credit check for this partner, those checks for which check exceptions are defined are omitted if the
current date is within the validity period for the check exception and the indicator Consider Check
Exceptions is set in the Customizing for the check rule. This means that you can achieve a temporary
relaxation in the checks for a business partner without having to define a new check rule.
8. If required, under the additional information in the general data, enter negative credit events with a validity
interval, deletion date, and an information type for categorization.
In the definition of formulas for scoring or the credit limit calculation, you can use the NEGATIVE_CHARS
function to check the existence of negative credit events. You usually use this function to assign a bad
score to a partner in such a case.
9. If required, in the data for a credit segment, set the block indicator, with block reason (optional).
A credit check for a blocked credit account (that is, partner and credit segment) always has a negative
result if the block indicator is set. Any block reason appears in the log for the credit check.
10. If required, in the data for a credit segment, set the Special Attention indicator.
This indicator is a selection criterion, for example, in the credit limit utilization list. You can set the indicator
manually, or automatically via the follow-on process Set Indicator for Special Attention in Customizing for
Events and Follow-On Processes.
11. If required, in the data for a credit segment, set the resubmission date.
This resubmission date is a selection criterion, for example, in the credit limit utilization list.
 Caution
Under certain circumstances, you may have to delete the business partner data in the previous
segment and recreate it in a different credit segment. This could be the case, for example, if a customer
becomes a major customer, and different distribution channels therefore apply.
Before you delete date in the previous credit segment, make sure that the credit exposure is zero!
To delete the data in the previous credit segment, in change mode choose Delete Data in Segment.
1.10.4 Workflow Settings
Process
To be able to use the various workflows of SAP Credit Management , you need to make the following settings:
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
63
● Configure notifications [page 64]
● Configure approvals for credit limit changes [page 65]
1.10.4.1 Configuring Notifications
Use
Where changes are made to the credit master data of a business partner, in particular, changes that are not
made manually, you can use workflow functions to have an analyst (recipient) notified of these events.
Procedure
Navigation
Menu path (in the system for SAP Credit Management)
SAP Customizing Implementation Guide
Supply Chain Management
Financial
Credit Management
Processes
Risk Monitoring
Transaction Code
Credit
Define Events and Follow-On
Processes
SAP Menu
Tools
Administration
SAP Menu
Event Manager
Tools
Definition Tools
Business Workflow
SWETYPV
Type Linkage
Business Workflow
Workflow Builder
Development
Development
SWDD
Workflow Builder
1. In the IMG activity Define Events and Follow-On Processes, define which event types are to be dealt with in
which activities; enter the follow-on process Start Workflow for the required event types.
SAP Credit Management supports the following event types:
○ Invalid Score
○ Changed Score
○ Changed Rule for Scoring and Credit Limit Calculation
○ Changed Risk Class
○ Changed Check Rule
64
PUBLIC
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
2. Make sure that, under Event Manager
type CL_UKM_BUSINESS_PARTNER:
Type Linkages , the following settings are defined for the object
Detailed Settings
Field Name
User Action and Values
Comments
Object Category
ABAP Class
Object Type
CL_UKM_BUSINESS_PARTNER
Event
WF_TRIGGER
Receiver Type
WS01700047
Receiver Call
Function Module
Receiver Function Module
SWW_WI_CREATE_VIA_EVENT_IBF
Linkage Activated
Active
Select indicator
3. Call up the Workflow Builder for the multistep task WS01700047 (ID UKM_BUPA).
Choose Goto Basic Data and then choose
the task is identified as a general task.
Goto
Agent Assignment for Task . Make sure that
Result
When an event with the event type defined above occurs during master data processing, a workflow item is
created. In the standard configuration of the workflow, the user whose action has triggered the event is also the
recipient of this workflow item.
1.10.4.2 Configuring Approvals for Credit Limit Changes
Use
A credit limit is only to be manually or automatically increased by more than a specific percentage with the
approval of a further processor. This processor can approve or reject the required limit.
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
65
Procedure
Navigation
Menu Path
Transaction Code
SAP Customizing Implementation Guide → Financial Supply
Chain Management → Credit Management → Credit Risk
Monitoring → Master Data → Create Rule for Scoring and
Credit Limit Calculation
SAP Customizing Implementation Guide → Financial Supply
Chain Management → Credit Management → Credit Risk
Monitoring → Processes → Define Events and Follow-On
Processes
SAP Menu→ Tools → Business Workflow → Development →
SWETYPV
Administration → Event Manager → Type Linkage
SAP Menu→ Tools → Business Workflow → Development →
SWDD
Definition Tools → Workflow Builder → Workflow Builder
1. For each rule for scoring and credit limit calculation and for each credit segment, define a percentage rate
for the maximum credit limit increase permitted without approval.
An empty entry is interpreted as 0%, that is, in this case, each credit limit increase requires approval.
2. In the activity Define Events and Follow-On Processes, define the activities in which event type Credit Limit
Change Requested is to be dealt with; enter the follow-on processes Check Request for Limit Change and
Start Workflow for this event type.
Make sure that, under Event Manager → Type Linkages, the following settings are defined for the object type
CL_UKM_ACCOUNT:
Detailed Settings
Field Name
User Action and Values
Object Category
ABAP Class
Object Type
CL_UKM_ACCOUNT
Event
WF_TRIGGER
Receiver Type
WS01700048
Receiver Call
Function Module
Receiver Function Module
SWW_WI_CREATE_VIA_EVENT_IBF
Linkage Activated
Active
Comments
Select indicator
3. Call up the Workflow Builder for the multistep task WS01700048 (ID UKM_ACC).
4. Choose Goto → Basic Data and then Goto → Agent Assignment for Task. Make sure that the task is identified
as a general task.
66
PUBLIC
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
Result
If the credit limit of a credit account is increased, manually or via an automatic process (for example, mass
change), by more than the percentage rate defined in the rule, the increased value is not transferred to the
Credit Limit field immediately; instead, it is entered in the Credit Limit Requested field. At the same time, a
workflow item is generated that provides information about this request and offers access to the business
partner maintenance. If the user has the relevant authorization, he can accept the limit requested (it is included
in the credit limit) or reject it.
1.11
Current Settings
Use
This section contains information about settings required for productive operations. This involves, for example:
● Data replication
● Business Customizing
As a rule, ABAP-based production systems are locked for Customizing. There are, however, certain cases in
which Customizing settings must be made in the production system, for example, to change currency
exchange rates. You can make these current settings in the menu in ABAP-based systems. This section also
contains information about current settings that must be made in non-ABAP systems.
Procedure
Perform the steps in these guidelines in the exact sequence in which they are listed.
1.11.1 Importing Exchange Rates
Use
In SAP Credit Management , you can monitor a credit limit in the credit segment currency independently of the
currency in which the commitment is reported to SAP Credit Management. The system can, if necessary,
determine the credit exposure dynamically in the credit segment currency by converting the commitment
reports using exchange rates and translation factors.
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
67
Prerequisites
You have defined the exchange rates and translation factors in the SAP Credit Management system. You can do
this either manually or automatically using the file interface.
In the SAP Credit Management system, you have defined in Customizing for the credit segments which
exchange rate type is used for the currency translation.
Procedure
● To enter the exchange rates manually, perform the following Customizing activities:
Navigation
Menu Path
Transaction Code
SAP Customizing Implementation Guide
Supply Chain Management
Market Data
S_BCE_68000174
Cash and Liquidity
→ Cash Management
Management
Financial
General Settings
Manual Entry of Market Data
Enter
Exchange Rates
SAP Customizing Implementation Guide → SAP
NetWeaver→ General Settings → Currencies → Define
Translation Ratios for Currency Translation
● Alternatively, you can use a file interface to upload exchange rates into the system automatically. You do
this by executing the following program.
Navigation
Menu Path
Transaction Code
SAP Menu
Accounting
Financial Supply Chain
Management
Cash and Liquidity Management
Management
Environment
Interface
Market Data
TBDM
Cash
File
Import
For more information, see the documentation for this program.
Result
By entering the exchange rates, you can always monitor the credit exposure of a customer in the currency of
the credit segment, independently of the currency in which the commitment was reported to SAP Credit
Management.
68
PUBLIC
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
 Note
The translation is not saved in the system. This is to ensure that every time you call a report with credit
exposure and commitment information, a translation is run using the current exchange rates.
1.11.2 Recreating Data (Troubleshooting)
Use
You recreate transaction data for one or more business partners in one or more credit segments if, for example,
the derivation of one or more credit segments has changed (for example, in an implementation of the Business
Add-In UKM_FILL), or if transaction data has become inconsistent due to incorrect updates.
You can recreate the data manually, or schedule one-time processing in the background.
Integration
The credit exposure transferred is displayed in the master record of the business partner per credit segment.
There you can navigate to the relevant commitments.
Procedure
From the SAP Easy Access screen, choose Financials Financial Supply Chain Management Credit Management
List Displays Credit Exposure.
With this function, delete the credit exposure line items and totals for the business partners and credit
segments concerned in SAP Credit Management.
Set both indicators Delete Totals and Delete Line Items.
You can then reload the credit exposure information from the systems connected to SAP Credit Management,
as described below.
The following reports are available to recreate the credit exposures from an SD system from SAP ERP 6.0:
UKM_RFDKLI20 to recreate the credit exposure after organizational changes
UKM_RVKRED77 to recreate the credit exposure where you have removed the cause of the error in the case of
data inconsistencies
UKM_RVKRED88 to simulate report UKM_RVKRED77 without setting blocks on the documents affected. This
report prepares an update run of report UKM_RVKRED77 to determine suitable selection parameters, for
example.
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
69
In SAP Credit Management, the transaction data is recreated from the credit exposure information of SD.
For more information, see the report documentation.
To recreate the liabilities from an FI-AR system, on the SAP Easy Access screen, choose Financial Supply Chain
Management→CreditManagement → Integration of Credit Management with FI-AR Asynchronous Credit
Exposure Update . Select the open items concerned in both sections of the selection screen and set the
indicator Start Recreation. Run the function.
In SAP Credit Management, the transaction data is recreated from the credit exposure information of FI-AR.
1.11.3 Credit Check If Technical Problems Occur
Use
The system can make credit checks only if the necessary servers are available. Otherwise, the system is unable
to determine the following credit management account master data that is required for a credit check:
● Risk Class
Determining the risk class when creating sales documents is necessary in order to be able to make the
Customizing settings for automatic credit control.
● Block of the credit management account
The check as to whether the credit management account is blocked is required for all processing, as order
and delivery processing is not permitted if there is a block.
To ensure that you are not prevented completely from working if SAP Credit Management or SAP NetWeaver
Process Integration are not available, you can still create new sales documents in the event of such technical
problems, and then perform the credit check later.
 Note
Note that you cannot perform the following activities in the event of technical problems:
● Change sales documents
● Create and change deliveries
● Process service orders
Activities
To connect Sales and Distribution to SAP Credit Management, use an implementation of the Business Add-In
BADI_SD_CM. If a technical problem occurs during the credit check, the system terminates processing and
issues error message UKM_PI 008.
70
PUBLIC
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
However, if you want to use the option of creating sales documents despite this and performing the credit
check later, proceed as follows:
1. Configure message UKM_PI 008 so that it is issued solely as a warning message when technical problems
occur. You do this using transaction OBA5.
2. Create the sales documents as usual. The system creates the documents but sets an indicator in the
document header to denote that they are blocked for technical reasons.
3. Make a new check of the blocked sales documents once the error has been solved. Use program
UKM_RVKRED09_XI for this.
On account of the indicator set in the document header, this program recognizes which documents have
been blocked for technical reasons and then releases those documents following a successful check. For
more information about this program, see the program documentation.
1.11.4 Converting Organizational Changes
Use
If you make changes to the SAP Credit Management master data or in Customizing during daily operations, you
may have to carry out corrections.
Procedure
Navigation
Menu Path
Transaction Code
SAP Customizing Implementation Guide
Supply Chain Management
Processes
Risk Monitoring
Financial
Credit Management
Credit
Define Events and Follow-On
Processes
SAP Menu
Management
Changes
Financial Supply Chain
Credit Management
UKM_MASS_UPD3
Master Data Mass
Credit Limit
SAP Menu
Management
Changes
Accounting
Accounting
Financial Supply Chain
Credit Management
UKM_MASS_UPD2
Master Data Mass
Score
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
71
Menu Path
SAP Menu
Management
Transaction Code
Logistics
Sales and Distribution
Sales Documents
Credit
All
●
Transaction VKM4
(Releases before SAP ERP 6.0)
●
Report UKM_RFDKLI20
(Releases from SAP ERP 6.0)
SAP Customizing Implementation Guide
Supply Chain Management
Risk Monitoring
Processes
Financial
Credit Management
Credit
Define Events and Follow-On
Processes
The following tables give you an overview of possible changes and the corresponding corrections:
Change
Measures Required
Currency of a credit limit changed
The credit limits of all business partners for this credit seg­
ment have to be recalculated. If necessary, adjust the formu­
las for determining the credit limit and carry out the mass
change Credit Limit for this credit segment.
You do not have to convert the transaction data because this
is managed in report currency and is translated into the cur­
rency of the credit segment at the current rate during a
check.
Indicator Additive Contribution to Main Credit Segment
changed in Customizing of a credit segment
No correction required.
The credit exposure of the main credit segment is always de­
termined dynamically at runtime according to the current
Customizing.
Customizing of a rule for scoring and credit limit calculation
changed
Carry out a mass change.
Depending on the type of change (formula of score or limit),
you choose the appropriate report and then select the busi­
ness partners and/or credit accounts affected via the rule.
Customizing of a check procedure changed
The modified check procedure has an effect on subsequent
checks. A new credit check of open SD orders for the partner
concerned only, that is, selection by check procedure, is cur­
rently not supported; however, you can check all open SD or­
ders again.
Derivation of one or more credit segments changed
(for example, in implementations of the Business Add-In
UKM_FILL)
Delete and recreate the transaction data in the credit seg­
ments concerned.
For more information about the procedure, see Recreating
Data (Troubleshooting) [page 69].
72
PUBLIC
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
Change
Measures Required
Business partner relationship changed, added, or deleted
No correction required.
The credit exposure contributions of other partners are al­
ways determined dynamically.
Rule for score and credit limit change in master record of
The change to the rule for scoring and credit limit calculation
business partner changed
of a business partner is published as an event.
In the Customizing settings for Events and Follow-On
Processes, you can define that the rule for scoring and credit
limit calculation is triggered.
Check rule in master record of business partner changed
The change to the check procedure triggers the event with
the same name.
In Customizing, you can define that a follow-on process
Carry Out Credit Check in All Segments is triggered for this
event, that is, the system carries out a credit check (with
credit exposure change 0) in all segments. Events that occur
as a result (for example, limit utilized to x%, credit rejected
for following reasons) are published according to the Cus­
tomizing settings.
1.11.5 Ensuring Data Protection
Use
Data that refers to natural persons is subject to legal data protection requirements that are different in each
country. Typical requirements are, for example, that unauthorized access to the data must be prevented and
that the purpose limitation of saved data must be adhered to.
Procedure
To implement the data protection guidelines, you have the following options in SAP Credit Management:
Restrict access to data
You can restrict the access to master data and transaction data using the authorizations for the role
SAP_FIN_FSCM_CR_USER. For more information, see Defining Authorizations [page 46].
Log changing accesses to master data
The update of change documents with time, user, and transaction is supported for all master data fields of SAP
Credit Management. Note the following special case: If the system determines master data, for example, a
credit limit that is no longer valid, automatically as the result of a follow-on process during a credit check or an
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
73
update of the commitment, the change document for this change contains the technical user defined in the
communication channel (for example, CREDITXIUSER).
Create own information
To provide a business partner with information about the data saved for him in SAP Credit Management,
compile the following data:
● Overview of the master data in SAP Credit Management with transaction UKM_MASS_DSP2
● Overview of the transaction data in SAP Credit Management with transaction UKM_COMMITMENTS
● If required, a list of additional information with report UKM_ADD_INFOS_DISPLAY
● If required, the history of the credit limit and the score from SAP NetWeaver Business Intelligence, if you are
using it.
● From SAP enhancement package 4 for SAP ERP 6.0, you can use a documented credit decision for your
own information. This contains a summary of the credit relevant data and a chronology of the changes. If
this data proves insufficient, you can either supplement the documented credit decision or use the options
already mentioned.
Correct the incorrect data for a business partner
Your business partner has the right to have you correct any incorrect data. Depending on the field, you have the
following options:
● You can change the risk category and the credit limits manually, for example, if the system determined
them based on an incorrect formula or on incorrect input parameters. Alternatively, you can have the
system recalculate these fields once you have corrected the formula or input parameters concerned.
● You can manually change a score calculated incorrectly if you use a rule for the scoring and credit limit
calculation that does not contain a formula for scoring. Alternatively, you can have the system recalculate
this field once you have corrected the formula or input parameters that were incorrect.
● You can change negative credit events and data for collateral and credit insurances manually.
● You can delete incorrect commitment and credit exposure data with transaction UKM_COMMITMENTS; you
then have to send the data from the client systems again.
Delete or initialize data for the business partner
● You can delete the master data for a business partner manually per credit segment in transaction UKM_BP.
● For each rule for scoring and credit limit calculation, you can restrict the validity period for the scores and
credit limits calculated. In a subsequent mass activity, you can, for example, select (via custom selections)
all business partners with a specific rule for scoring and credit calculation and where the score is no longer
valid and assign a new rule to them, whereby the formulas in the new rule initialize the score and the credit
limit.
● You should enter negative credit events and data for collateral and credit insurances with a valid to date.
Once this date has passed, the system no longer considers the events and data but they remain in the
system. You can use report UKM_ADD_INFOS_DISPLAY to determine information that is no longer valid
and then delete it manually.
● Transaction data, that is, line items with commitment information, is not stored permanently in SAP Credit
Management; the system deletes it after clearing.
● You can delete data that you have extracted to SAP Netweaver Business Intelligence for a business partner
from the ODS objects 0CDM_DS00 and 0CDM_DS01.
● The master and transaction data that you use in SAP Credit Management can be archived and deleted
using the following archiving objects once the legally required retention time has been reached:
○ Data for the business partner: Archiving Object CA_BUPA
74
PUBLIC
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
○ Data for the documented credit decision from SAP enhancement package 4 for SAP ERP 6.0:
Archiving Object SCMG
Purpose limitation
Data that arises in SAP Credit Management should only be used in that component.
● By implementing the method READ_RESPONSE of the Business Add-In UKM_CREDIT_INFO appropriately,
you can enter a text for external credit information in order to document the use in SAP Credit
Management.
● For example, you can restrict mass changes by rule for scoring and credit limit calculation or (via custom
selections) by the credit group to prevent external information, scores, or credit limits being recalculated
unnecessarily or without a legal requirement.
Consent statement of the business partner for external credit information
Inform your business partner explicitly if you use a rule that evaluates information from external credit
information providers. Make sure that the rating only takes place if the business partner (natural person) has
consented to this. You can document a withdrawal of consent by setting a block reason in the master data.
SAP Credit Management Configuration Guide
SAP Credit Management Configuration Guide
PUBLIC
75
Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
●
●
Links with the icon
: You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
●
The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
●
SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
Links with the icon
: You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Beta and Other Experimental Features
Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.
76
PUBLIC
SAP Credit Management Configuration Guide
Important Disclaimers and Legal Information
SAP Credit Management Configuration Guide
Important Disclaimers and Legal Information
PUBLIC
77
www.sap.com/contactsap
© 2019 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form
or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP SE and its distributors
contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for
informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.
Please see https://www.sap.com/about/legal/trademark.html for
additional trademark information and notices.
THE BEST RUN