You can use the credit information received from external information providers for calculating the score. To import the information from other systems either manually with an import button or automatically, you first have to connect and configure the XI landscape of the information providers in question.
For more information on the XI interfaces, see SAP B2B Interface CreditAgencyReport [Page 40].
Prerequisites
● You are a customer of the external information provider.
● The external information provider provides an interface for data queries in the Internet. You must be able to map the fields of the provider’s interface on the XI interface of SAP
Credit Management.
● You have a description of the information provider's interface in the format of a WSDL- XSD or DTD file.
Procedure
...
1. Make an entry for the external information provider in the Implementation Guide of
Credit Management under Master Data → Define Rating Procedure.
If you wish to use different products of an information provider (for instance, information of various scope), you should make an entry for each product. For each rating procedure, you should define the different forms of results of the query. (The information of an information provider generally contains a large number of fields and key figures.) Consequently, the ‘result’ is taken to mean the key figures that you want to use to calculate your score.
2. In the Integration Builder of your XI server, call up the Integration Repository and create
the following objects in a separate software component:
a. Two interface objects of the External Definition type into which you load the interface description for the query and response of the information provider . b. A message interface with the inbound und synchronous attributes and
external message type where you reference the external definitions that you have created.
3. Define how the interface of SAP Credit Management is to be mapped with the interface of the information provider. The mapping can either be handled with XSL
transformations or with message mapping objects that you graphically define in the Integration Builder.
If you wish to use XSL transformations, proceed as follows:
a. Define (for example, initially as local files) two XSL transformations:
■ One for the mapping of message type CreditAgencyReportQuery in the namespace http://sap.com/xi/FSCM/Global to the inbound interface of the information provider
■ One for the mapping of the output interface of the information provider to the message type CreditAgencyReportResponse in the namespace
http://sap.com/xi/FSCM/Global
Pack both files into an archive file of type ZIP.
b. In the Integration Repository of your software component, create a mapping
object of the Imported Archive type, into which you load the local archive file that you created in step 3a.
c. In the Integration Repository of your software component, create an interface
mapping with the outbound interface CreditAgencyReportQuery_Out in the namespace of http://sap.com/xi/FSCM/Global the target interface that you created in step 2b, and the mapping programs in the imported archive in step 3b.
If you wish to use a Message-Mapping object, proceed as follows:
a. In the Integration Repository of you software component, create two mapping objects of the Message-Mapping type.
■ The outbound message of the first message mapping has the message type CreditAgencyReportQuery in the namespace
http://sap.com/xi/FSCM/Global.
■ The target message is of the external query message type, located in the External Definition that you created in step 2a. The second message mapping has an output message of the external response message type from step 2a and a target message of message type CreditAgencyReportResponse in the namespace of
http://sap.com/xi/FSCM/Global.
Assign the fields that are to be mapped together to each other using drag and drop.
b. In the Integration Repository of your software component, create an interface
mapping with the outbound interface CreditAgencyReportQuery_Out in the namespace of http://sap.com/xi/FSCM/Global, the target interface that you created in step 2b, and the message mappings in the preceding step. 4. In the Integration Builder of your XI server, access the configuration of the Integration Directory and create the following objects in a separate scenario and namespace (the
namespace of your own software component in the previous step):
○ A business service with the inbound interface of step 2b and a communication channel with the following characteristics:
■ Adapter type = HTTP
■ Transport protocol = HTTP 1.0
■ Adapter Engine = Integration Server ■ Addressing type = HTTP destination
■ Content type = application/x-www-form-urlencoded
○ A receiver determination. The sender is your Credit Management system where the request is issued; the interface is CreditAgencyReportQuery_Out in the namespace http://sap.com/xi/FSCM/Global. The recipient is the business service from the previous step.
If you wish to connect more than one information provider, define a business service for each one and specify the conditions for selecting each receiver in the receiver determination (see also step 5).
○ An interface determination in which you determine the receiver interface for the combination of sender, sender interface and receiver. Enter again the interface from step 3c and the interface mapping from step 3d.
○ A receiver agreement in which you determine the communication channel HTTP for the combination of sender, receiver and receiver interface.
5. In SAP Credit Management, implement the business add-in UKM_CREDIT_INFO (see
the Implementation Guide for Credit Management under Credit Risk Monitoring →
Enhancements → BAdI: Evaluate External Credit Information).
The minimum requirement is to implement method FILL_QUERY to be able to address an information provider. In this method, you enter the product identifier that the
information provider needs to identify the required product (for instance, the scope of the information). You may use this identifier in the XI configuration to configure the receiver determination, in other words to derive the correct recipient from the content of the identifier.
In method FILL_QUERY, you can enter the reason for the request (legal requirement in Germany) and the language in which the information is provided. You can also fill other fields of the request, such as the address data of the business partner.
6. The part of the response that is mapped through the XSL transformation of step 3 to interface field CreditRating-Code is stored in the standard delivery as the result of the request.
You can influence this behavior by implementing the method READ_RESPONSE of the Business Add-In UKM_CREDIT_INFO.
...
Result
In the Credit Profile screen of the business partner’s master data transaction, you can now import external credit information by entering the relevant rating procedure, selecting the entry and pressing the Import Data pushbutton.
You can import information on a large number of business partners using the External
Ratings mass activity. From the SAP Easy Access screen choose Accounting → Financial Supply Chain Management → Credit Management → Master Data Mass Changes → External Credit Information.