FSCM Credit Management Config Guide ERP 2005

SAP Credit Management Configuration Guide

mySAP ERP 2005


07/01/2006

Copyright © Copyright 2006 SAP AG. 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 AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group 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.

Page 2 of 109


07/01/2006

Icons in Body Text Icon

Meaning Caution Example Note Recommendation Syntax

Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more information, see Help on Help → General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.

Typographic Conventions Type Style

Description

Example text

Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Cross-references to other documentation.

Example text

Emphasized words or phrases in body text, graphic titles, and table titles.

EXAMPLE TEXT

Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example text

Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example text

Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT

Keys on the keyboard, for example, F2 or ENTER.

Page 3 of 109


07/01/2006

Contents SAP Credit Management Configuration Guide.......................................................................... 6 SAP Credit Management (FIN-FSCM-CR) ............................................................................ 7 Documentation Landscape for SAP Applications and Business Scenarios ........................ 11 SAP Notes............................................................................................................................ 12 Further Information .............................................................................................................. 13 Terminology Changes from mySAP ERP 2005 ............................................................... 14 System Connections ............................................................................................................ 15 Process Integration with Logistics and Finance Systems: Overview ............................... 15 Preparation for Using the SAP Business Information Warehouse................................... 16 Setting Up Portal Connection (Optional) .......................................................................... 17 Configuration of the XI Connections ................................................................................ 18 XI Interfaces: Overview................................................................................................. 19 SAP A2A Interface CreditWorthinessQuery_In ........................................................ 21 SAP A2A Interfaces CreditCommitment_In and CreditCommitment_Out ................ 27 SAP A2A Interface CreditPaymentRecord_In........................................................... 33 SAP A2A Interface CreditPaymentBehaviourSummaryNotification_In .................... 37 SAP B2B Interface CreditAgencyReportQuery_Out................................................. 40 SAP A2A Interface CreditWorthinessCriticalPartiesQuery_In .................................. 45 SAP A2A Interface CreditWorthinessChangeInformation_Out................................. 48 SAP Component Interface FICARatingReplicate ..................................................... 51 Connecting External Information Providers .................................................................. 53 Connecting Accounts Receivable Accounting ERP 2005 ............................................ 56 Connecting Accounts Receivable Accounting ERP 2004 ............................................ 57 Connecting Accounts Receivable Accounting 4.70 or 4.6C ......................................... 58 Connecting Contract Accounts Receivable and Payable 6.00 ..................................... 59 Connecting Contract Accounts Receivable and Payable 4.72 ..................................... 61 Connecting Sales and Distribution ERP 2005 .............................................................. 63 Connecting Sales and Distribution ERP 2004 .............................................................. 64 Connecting Sales and Distribution 4.70 or 4.6C .......................................................... 65 Connecting Customer Relationship Management (CRM) ............................................ 66 Data Replication................................................................................................................... 68 Providing Business Partner Data ..................................................................................... 68 Replicating Master Data of Accounts Receivable Accounting (FI-AR) ............................ 69 Replicating Master Data of Contract Accounts Receivable and Payable (FI-CA) ........... 70 Business Customizing.......................................................................................................... 72 Settings in SAP Credit Management (FIN-FSCM-CR) .................................................... 72 Activating the Business Partner Role for Credit Management ..................................... 73 Configuring Business Partner Additional Information................................................... 74

Page 4 of 109


07/01/2006

Defining Authorizations................................................................................................. 76 Define Events and Follow-On Processes ..................................................................... 77 Process Integration with SAP Systems............................................................................ 80 Making Settings in FI-AR ERP 2005 ............................................................................ 81 Making Settings in FI-AR ERP 2004 ............................................................................ 83 Making Settings in FI-AR 4.70 or 4.6C ......................................................................... 85 Making Settings in Contract Accounts Receivable and Payable (FI-CA)..................... 88 Making Settings in SD ERP 2005................................................................................. 91 Making Settings in SD ERP 2004................................................................................. 93 Making Settings in SD 4.70 or 4.6C ............................................................................. 94 Making Settings in CRM ............................................................................................... 96 Setting Up Component-Specific Master Data ...................................................................... 98 Defining Credit Master Data in the Business Partner ...................................................... 98 Workflow Settings .............................................................................................................. 101 Configuring Notifications ................................................................................................ 101 Configuring Approvals for Credit Limit Changes ............................................................ 102 Current Settings ................................................................................................................. 104 Importing Exchange Rates ............................................................................................. 104 Recreating Data (Troubleshooting) ................................................................................ 105 Converting Organizational Changes .............................................................................. 106 Ensuring Data Protection ............................................................................................... 108

Page 5 of 109


07/01/2006

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.

Content The configuration guide describes which structures and activities of the Implementation Guide (IMG) that you have to process to implement the business process.

For information about the individual IMG activities, see the IMG documentation of your SAP system. This configuration guide provides additional contexts and background that may be useful for Customizing.

Target Group ●

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 10].

Feedback on Configuration Guide In order to continually improve the configuration guide, we would appreciate your feedback. If you find errors in the configuration guide, enter a message for the component SAP Credit Management (FIN-FSCM-CR) on SAP Service Marketplace at service.sap.com/message.

Page 6 of 109


07/01/2006

SAP Credit Management (FIN-FSCM-CR) Purpose The creditworthiness and payment behavior of your business partners have an immediate effect on the business results of your company. Efficient receivables and credit management reduces the risk of financial losses and helps you to optimize business relationships with your business partners. SAP Credit Management (FIN-FSCM-CR) supports your company in determining the risk of losses on receivables from your business partners early and in making credit decisions efficiently and partially automated. It also supports you in a heterogeneous and distributed system landscape; by using system-independent XML interfaces, you can also connect external non-SAP systems. With SAP Credit Management (FIN-FSCM-CR) you can operate a centralized credit management. The business systems [External] connected (for example, Sales and Distribution, Logistics Execution, Financial Accounting) report the commitment of a business partner to SAP Credit Management (FIN-FSCM-CR) via XML. These reports are then consolidated into the credit exposure in SAP Credit Management (FIN-FSCM-CR) and checked against the current credit limit for the business partner. In addition to the credit limit check, you can also carry out other checks, such as oldest open item, maximum dunning level, or last payment. SAP Credit Management (FIN-FSCM-CR) is part of the SAP Financial Supply Chain Management (FIN-FSCM) [External] solution.

Implementation Considerations SAP Credit Management (FIN-FSCM-CR) will eventually replace the existing Credit Management (FI-AR-CR). FI-AR-CR is a purely internal FI credit management application, whereas SAP Credit Management (FIN-FSCM-CR) provides you with a comprehensive, integrated, and cross-system form of credit management. We particularly recommend the use of SAP Credit Management (FIN-FSCM-CR) for the following companies: ●

Companies that, due to a heavily distributed system landscape, frequently have problems consolidating information for the credit decisions. In contrast to the Credit Management (FI-AR-CR) component, the component SAP Credit Management (FIN-FSCM-CR) can collect and process information about the credit exposure of a business partner from different SAP and non-SAP systems. The number of financial accounting or SD systems your company uses is not relevant. SAP Credit Management (FIN-FSCM-CR) consolidates the information from these systems into the credit exposure for the respective business partner, and this enables you to monitor the business partner’s credit limit centrally.

●

Companies with a large number of business partners These companies can use SAP Credit Management (FIN-FSCM-CR) to automate a large part of their credit management processes, such as scoring and rating of business partners, proposal of credit limits, notification of credit analysts, monitoring of credit limits.

●

Companies that want to combine internal and external data for a business partner in a separate scoring or rating The integration of external information providers is very important here. You can access this external information automatically through XML interfaces and use it in SAP Credit Management (FIN-FSCM-CR).

Page 7 of 109


07/01/2006

Integration SAP Credit Management (FIN-FSCM-CR) enables your company to operate centralized credit management even in a distributed system landscape while taking account of both internal and external credit information. System-independent XML interfaces enable you to connect internal systems such as SD and Financial Accounting as well as the systems of external credit information providers (external credit information). These systems report credit-relevant data to SAP Credit Management (FIN-FSCM-CR) on request. The data reported is consolidated in SAP Credit Management (FIN-FSCM-CR) and is available for many types of credit checks at customer or customer group level. You can access the analyses and results in SAP NetWeaver Business Intelligence or the Credit Manager Portal. Integration with Other SAP Components SAP Application Components with Release ●

SAP Credit Management 6.0 (Financial Basis 3.00)

●

SAP NetWeaver Application Server 2004s

●

SAP NetWeaver Exchange Infrastructure 7.0

●

Accounts Receivable Accounting (FI-AR) 4.6C; SAP R/3 Plug-In 2004.1; mySAP ERP 2005

●

Industry releases 4.72 and 6.00 of Contract Accounts Receivable and Payable (FI-CA) for the following solutions: ○

mySAP Insurance

○

mySAP Utilities

○

mySAP Telecommunications

○

mySAP Media

○

mySAP Public Sector (Public Sector FI-CA)

○

SAP Contract Accounts Receivable and Payable (FI-CA)

●

Sales and Distribution (SD) 4.6C; SAP R/3 Plug-In 2004.1, mySAP ERP 2005

●

SAP NetWeaver Business Intelligence with Business Content 3.5.2

●

(optional) SAP Customer Relationship Management (CRM) 4.0 with CRM Industry AddOn; 5.00

●

SAP Enterprise Portal 6.0 (optional)

Prerequisites For more information about the SAP components and release versions required, see System and Component Landscape [Extern].

Page 8 of 109


07/01/2006

Features Business Partner – Credit Master Data You manage all credit-relevant master data of a business partner in SAP Credit Management (FIN-FSCM-CR). This data includes the current credit limit, one or more externally determined rating values, the risk class, and an order limit. Each of the master data fields has a change history that gives information about the time of the change, the user, and the old and new value. There is also a note function that the credit analyst can use to enter additional information about the business partner. Alternatively, he or she can use a document storage function to store information such as press articles, correspondence, bank information, and rating information. SAP Credit Management (FIN-FSCM-CR) also enables you to include collateral defined for a business partner in the calculation of the credit exposure, meaning that you can also monitor your own company’s risk. Credit Information and Business Partner Rating The credit analyst can determine and manage both external and internal credit information for a business partner. This information is used mainly as input parameters for the Credit Rules Engine that companies can use to carry out automatic business partner ratings (scoring), making credit decisions, or calculating credit limits. ●

Processing External Credit Information Requesting external credit information is completely integrated in SAP Credit Management (FIN-FSCM-CR) and enables companies to request information electronically using appropriate XML interfaces. Since credit departments often use several external credit information providers, SAP Credit Management (FIN-FSCM-CR) can save the information provided by such an interface separately according to the data provider. The XML interface is designed to allow the user to call up information about both business partners and private customers.

●

Processing Internal Credit Information (Score) The credit analyst can also extract internal data for a business partner from the legacy systems and use the company’s own rating rules to determine a score. You can have these score values determined by the following factors: ○

Master data of the business partner (for example, country of origin of the business partner)

○

Payment behavior (for example, average days in arrears)

○

Dunning history (for example, number of dunning notices in the last 12 months)

○

SAP Dispute Management (for example, the number of dispute cases in the last 12 months)

The external and internal credit information determined is stored in the master data of the business partner. The system monitors the validity of the data determined periodically. The score data can be updated manually or automatically.

Page 9 of 109


07/01/2006

Score and Credit Limit Calculation and Credit Limit Check (Credit Rules Engine) SAP Credit Management (FIN-FSCM-CR) enables you to automate certain processes by applying certain rules. These rules are controlled by the Credit Rules Engine and hence support the subsequent automated business processes. ●

Rating of Business Partners A procedure is assigned to each business partner; each procedure has a formula for calculating the rating value. You can define the formula to meet your own requirements using various data that is available as input parameters for the formula. SAP Credit Management (FIN-FSCM-CR) also has mass processing functions that enable you to recalculate the rating value or change the rating procedure simultaneously for a large number of business partners.

●

Determining Credit Limit You can calculate the credit limit of a business partner automatically. Using SAP Workflow, you can implement an approval procedure where changes to a credit limit can be checked and approved by a superior.

●

Rules for Credit Check You can define rules for determining which credit checks are carried out. Here you can choose whether, in addition to the check for the credit limit utilization, other checks are to be carried out, for example, the maximum age of the oldest open item, or the maximum number of dunning transactions of the business partner. You can also define what consequences a negative check result is to have (for example, block sales order, block customer account, or trigger workflow).

Credit Information and Credit Decisions The credit analyst requires information from different systems to make decisions quickly and efficiently about blocked orders or the amount of the credit limit. SAP Credit Management (FIN-FSCM-CR) supports credit analysts in determining the required customer-related data and analyses in SAP NetWeaver Business Intelligence (SAP NetWeaver BI), and, optionally, in the Credit Manager Portal.

Page 10 of 109


07/01/2006

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

Implementation Guide (IMG)

SAP System

Business Scenario Description, Business Process Description

SAP Solution Manager

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 upgrade guide Technical infrastructure (for example, hardware sizing, platforms, network security)

service.sap.com/ti

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. It lists, for each business scenario, 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.

●

Implementation Guide (IMG) This tool enables you to adapt SAP systems to meet specific customer requirements. The IMG contains the IMG activities for all SAP components with general documentation. The structure is component-oriented, and has no reference to a business scenario. If this reference is required, it is created as follows: By the Configuration Guide, with a textual link to the IMG, and by the content of SAP Solution Manager that links to the IMG 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. Page 11 of 109


07/01/2006

SAP Notes Use Before you start configuring SAP Credit Management, read the following SAP Notes. This in turn contains references to other SAP Notes. Make sure that you have carried out all the necessary installation steps. Central SAP Notes for Installing and Upgrading SAP Credit Management SAP Note

Title of SAP Note

859998

Installation of SAP Credit Management 6.0

859995

Upgrade to SAP Credit Management 6.0

To get a comprehensive and up-to-date overview of the SAP notes for SAP Credit Management, use the note search on SAP Service Marketplace at service.sap.com/notes.

Page 12 of 109


07/01/2006

Further Information Use The following list contains useful information for configuration: Further Information Information

Quick Link on SAP Service Marketplace (at service.sap.com) or Location in SAP Solution Manager

SAP Credit Management Application Documentation

helpportal

BI Business Content of SAP Credit Management

helpportal

Documentation for SAP Exchange Infrastructure 7.0 (XI)

Documentation → SAP ERP Central Component → ERP Central Component (Release 6.0) → SAP ERP Central Component → Financials → SAP Financial Supply Chain Management (FIN-FSCM) → SAP Credit Management (FINFSCM-CR) Documentation → SAP ERP Central Component → ERP Central Component (Release 6.0) → SAP NetWeaver Library → SAP NetWeaver by Key Capability → Information Integration by Key Capability → BI Content → Financials → SAP Financial Supply Chain Management → SAP Credit Management (FIN-FSCM-CR)

helpportal Documentation → SAP ERP Central Component → ERP Central Component (Release 6.0) → SAP NetWeaver Library → SAP NetWeaver by Key Capability → Process Integration by Key Capability → SAP Netweaver Exchange Infrastructure

Configuration Guide – SAP XI 7.0


How-to-Guides for SAP Exchange Infrastructure 3.0 (XI): Mapping within XI 3.0

nw04 SAP NetWeaver → SAP NetWeaver 2004 – Release-Specific Information → How-to Guides → Exchange Infrastructure Document from the previous release that is still helpful.

Documentation on Portal Content

http://www.sdn.sap.com/irj/sdn/developer areas/contentportfolio

Business process description: FI-AR: Credit Management [Extern]


SAP Credit Management Security Guide (English Version)

securityguide mySAP ERP 2005 Security Guides → mySAP ERP 2005 Security Guides → SecGuide_CredMan_60_*

Familiarize yourself with the documentation landscape for SAP solutions, business scenarios, and business processes. For information on the type of documentation SAP provides and where the latest versions are published, see Documentation Landscape of SAP Solutions and Business Scenarios [Page 10].

Page 13 of 109


07/01/2006

Terminology Changes from mySAP ERP 2005 With effect from mySAP ERP 2005, the use of the following terms has changed: Old

New

FI summary

Payment behavior summary

Total liability

Credit exposure

Liability

Commitment

Credit query

Credit check

These differences are particularly important if you use applications with different releases.

Page 14 of 109


07/01/2006

System Connections Purpose This section contains information about connecting the systems in a 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

Procedure Perform the steps in these guidelines in the sequence in which they appear.

Process Integration with Logistics and Finance Systems: Overview SAP Credit Management provides direct integration with the SD, FI-AR, and FI-CA processes. This ensures full monitoring of the credit risk from order entry through to bill payment. You have the following integration options for SAP Credit Management 6.0: ●

SD (R/3 4.6C, R/3 Enterprise, mySAP ERP 2004, mySAP ERP 2005) ○

Credit limit check on creating or changing sales orders and deliveries

○

Credit exposure report on saving an order

○

Credit exposure report on saving a delivery

○

Credit exposure report on creating a billing document

Constraints The credit limit check and credit exposure update when you create or change a delivery are only available from mySAP ERP 2005. Service orders are currently not supported. ●

FI-AR (R/3 4.6C, R/3 Enterprise, mySAP ERP 2004, mySAP ERP 2005) ○

Regular credit exposure report for open customer line items

○

Regular update of the payment behavior summary in SAP Credit Management based on payment information

○

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 SAP Library.

Page 15 of 109


●

●

07/01/2006

Industry Release Contract Accounts Receivable and Payable (FI-CA 4.72 and mySAP ERP 2005) ○

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

CRM (4.0, 5,0) ○

Customer credit limit check on creating or changing a CRM sales order (order management)

○

Credit exposure update on saving a CRM sales order (order management)

Constraints 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. The integration of CRM service orders is not yet implemented in the current release.

Preparation for Using the SAP Business Information Warehouse 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.

For more information about SAP NetWeaver Business Intelligence (SAP NetWeaver BI), see SAP Library under SAP NetWeaver Library → SAP NetWeaver by Key Capabilities → Information Integration by Key Capability. ■

For information about configuration, see Business Intelligence.

■

For information about BI Content of SAP Credit Management, see BI Content → Financials → SAP Financial Supply Chain Management → SAP Credit Management (FIN-FSCM-CR).

Page 16 of 109


07/01/2006

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 Data Warehousing → Data Acquisition → Source System → 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 Data Warehousing → Data 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 (FINFSCM-CR) detailed above. 3. In the BI system, activate the Business Content for SAP Credit Management. For more information, see SAP Library for Business Intelligence under Data Warehousing → Data Warehouse Management → Business Content (Versions) → 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 Data Warehousing → Data Acquisition → Source System → 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 Warehouse Management → Scheduler (3.x) → Scheduling InfoPackages.

Setting Up Portal Connection (Optional) Use In SAP Credit Management you can use a wide range of analysis and processing functions in SAP Enterprise Portal. For more information on Business Package for Credit Management 6.01 and SAP Enterprise Portal, see the Internet at

http://www.sdn.sap.com/irj/sdn/developerareas/contentport folio.

Page 17 of 109


07/01/2006

Configuration of the XI Connections Purpose You can connect various components and external systems to SAP Credit Management. Data exchange takes place through XI interfaces.

Prerequisites XI Content has been installed in the XI Repository. You can use the following Releases for the different application components: Component

Release

SAP Credit Management (FIN-FSCM-CR)

FINBASIS 600

Accounts Receivable Accounting (FI-AR)

SAP APPL 6.00 or SAP R/3 Plug-In 2004.1.500 or SAP R/3 Plug-In 2004.1.470 or SAP R/3 Plug-In 2004.1.46C (Corresponding to the release version of the FIAR system connected)

Contract Accounts Receivable and Payable (FI-CA)

FI-CA 6000 or

Sales and Distribution (SD)

SAP APPL 6.00 or

FI-CA 4.72

SAP R/3 Plug-In 2004.1.500 or SAP R/3 Plug-In 2004.1.470 or SAP R/3 Plug-In 2004.1.46C (Corresponding to the release version of the SD system connected) Customer Relationship Management (CRM)

SAP BBPCRM 5.0 or CRMIS 4.00

Process Flow You can connect the following components and external systems using the SAP NetWeaver Exchange Infrastructure (XI): ●

External information providers [Page 53]

●

Accounts Receivable Accounting (FI-AR) ○

Connecting Accounts Receivable Accounting (FI-AR) with Release mySAP ERP 2005 [Page 56]

○

Connecting Accounts Receivable Accounting (FI-AR) with Release mySAP ERP 2004 [Page 56]

○

Connecting Accounts Receivable Accounting (FI-AR) with Release SAP R/3 Enterprise 4.70 or SAP R/3 4.6C [Page 57]

Page 18 of 109


●

●

07/01/2006

Contract Accounts Receivable and Payable (FI-CA) ○

Connecting Contract Accounts Receivable and Payable with Release 6.00 [Page 59]

○

Connecting Contract Accounts Receivable and Payable with Release 4.72 [Page 61]

Sales and Distribution (SD) ○

Connecting Sales and Distribution (SD) with Release mySAP ERP 2005 [Page 63]

○

Connecting Sales and Distribution (SD) with Release mySAP ERP 2004 [Page 63]

○

Connecting Sales and Distribution (SD) with Release SAP R/3 Enterprise 4.70 or SAP R/3 4.6C [Page 65]

For more information on the use of XI interfaces, see XI Interfaces: Overview [Page 19].

XI Interfaces: Overview You can use the following XI interfaces in SAP Credit Management: XI Interface

Description

SAP A2A Interface CreditWorthinessQuery_In [Page 21]

Credit Query

SAP A2A Interfaces CreditCommitment_In und CreditCommitment_Out [Page 26]

Credit exposure update

SAP A2A Interface CreditPaymentRecord_In [Page 32]

Payment behavior summary (reduced scope)

SAP A2A Interface CreditPaymentBehaviourSummaryNotification_In [Page 36]

Payment behavior summary

SAP B2B Interface CreditAgencyReportQuery_Out [Page 40]

External credit information

SAP A2A Interface CreditWorthinessCriticalPartiesQuery_In [Page 44]

Critical business partners

SAP A2A Interface CreditWorthinessChangeInformation_Out [Page 48]

Reporting of events to connected systems

SAP Component Interface FICARatingReplicate [Page 50]

Comparison of FI-CA creditworthiness with score from SAP Credit Management

The following figure gives you an overview of the use of individual XI interfaces for data exchange in SAP Credit Management.

Page 19 of 109


07/01/2006

XI Choreography in SAP Credit Management

Accounts Receivable Accounting

Sales and Distribution or Accounts Rec.

Example: Ext. Telco Inv. System

SAP Credit Management

External Information Provider

CreditCommitment RecordNotification CreditPayment BehaviourSummary Notification CreditWorthiness Query CreditAgency ReportQuery CreditAgency ReportResponse CreditCommitment Query

CreditComitment Response

CreditWorthiness Response

CreditWorthiness ChangeInformation CreditWorthiness CriticalParties Query CreditWorthiness CriticalParties Response

Primary Message Types Secondary Message Types

Page 20 of 109


07/01/2006

SAP A2A Interface CreditWorthinessQuery_In Description The interface CreditWorthinessQuery_In requests information about the creditworthiness of business partners. It uses the following message types: ●

CreditWorthinessQuery: Determines the structure of the creditworthiness query of a business partner.

●

CreditWorthinessResponse: Determines the structure of the response message containing the required details about the creditworthiness (for example, score and credit limit) of a business partner.

The application that wants information on the creditworthiness of a business partner (for example, Accounts Receivable Accounting or Sales and Distribution) sends a query to SAP Credit Management, and SAP Credit Management returns the required information such as the score and recommended credit limit for the business partner. This information influences, for example, the decision in the requesting application as to whether or not to have business dealings with this business partner.

Querying System

SAP Credit Management CreditWorthinessQuery

CreditWorthinessResponse

Message Interfaces CreditWorthinessQuery_In (inbound, synchronous) When an application sends a creditworthiness query, the message interface is the inbound interface to SAP Credit Management. The query is synchronous. The message interface uses the message types CreditWorthinessQuery and CreditWorthinessResponse.

Page 21 of 109


07/01/2006

Message Types CreditWorthinessQuery This message type uses the data type CreditWorthinessQueryMessage that represents a message for querying creditworthiness. CreditWorthinessResponse This message type uses the data type CreditWorthinessMessage that represents a response to the creditworthiness query.

Data Types CreditWorthinessQueryMessage The figure below shows the data type CreditWorthinessQueryMessage that contains an entry of the data type CreditWorthinessQuery.

CreditWorthinessQueryMessage Credit Worthiness QueryMessage

CreditWorthiness Query

CreditWorthinessQuery

CreditSegmentInternalId CheckedAmount CheckingRuleCode CheckingServityCode CreditAgencyReportRetrieval PermissionIndicator DebtorPary CreditorParty SellerParty ProductCategory

Page 22 of 109


07/01/2006

The data type CreditWorthinessQuery contains the following elements: ●

CreditSegmentInternalId – Credit segment in SAP Credit Management GDT: CreditSegmentInternalID

●

CheckedAmount – Amount to be checked (such as the order value) GDT: Amount

●

CheckingRuleCode – Encoded display of the rule to be used to determine the creditworthiness GDT: CreditWorthinessCheckingRuleCode

●

CheckingServityCode – Encoded display of the severity of the check procedure to be used GDT: CreditWorthinessCheckingSeverityCode

●

CreditAgencyReportRetrievalPermissionIndicator – Indicator to show whether or not a business partner has granted permission for credit information to be obtained about him or her GDT: CreditAgencyReportRetrievalPermissionIndicator

●

DebtorParty – Customer whose creditworthiness is to be determined GDT (InternalId): PartyInternalID

●

CreditorParty – Not used in SAP Credit Management

●

SellerParty – Not used in SAP Credit Management

●

ProductCategory – Not used in SAP Credit Management

CreditWorthinessMessage The figure below shows the data type CreditWorthinessMessage that contains an entry of the data type CreditWorthiness.

Page 23 of 109


07/01/2006

CreditWorthinessMessage Credit Worthiness Message

CreditWorthiness

CreditWorthiness

CreditSegmentInternalId Indicator CheckingDescription DebtorPartyBlockedIndicator DebtorPartySpecialAttention RequiredIndicator DebtorPary CreditorParty SellerParty ProductCategory Rating RiskClass CreditLimit CreditExposure

The data type CreditWorthiness contains the following elements: ●


●

Indicator – Specification of whether there is a creditworthiness for the business partner for the query parameters specified GDT: CreditWorthinessIndicator

●

CheckingDescription – Description of the flow of a creditworthiness check GDT: Description

●

DebtorPartyBlockedIndicator – Specification of whether the business partner is blocked in SAP Credit Management GDT: Indicator

Page 24 of 109

SAP Credit Management Configuration Guide ●

07/01/2006

DebtorPartySpecialAttentionRequiredIndicator – Specification of whether the business partner should be subject to special attention GDT: Indicator

●

DebtorParty – Customer whose creditworthiness was determined GDT: PartyInternalID

●


●


●


●

Rating – Score of a business partner determined by SAP Credit Management and valid for a specific period Rating contains the following elements: ○

Code – Coded display of the score value GDT: CreditRatingCode

○

ValidityPeriod – Validity period of the score value GDT: DateTimePeriod

●

RiskClass – Payment default risk determined by SAP Credit Management and valid for a specific period RiskClass contains the following elements: ○

Code – Coded display of the risk class GDT: CreditRiskClassCode

○

ValidityPeriod – Validity period of the risk class GDT: DateTimePeriod

●

CreditLimit – Credit valid for a business partner for a specific period CreditLimit contains the following elements: ○

Amount – Amount of the credit GDT: Amount

○

ValidityPeriod – Validity period of the credit GDT: DateTimePeriod

●

CreditExposure – Current credit exposure of the business partner CreditExposure contains the following element: ○

Amount – Amount of the credit exposure GDT: Amount

Page 25 of 109


07/01/2006

Mapping Objects Interface Mapping UkmCreditQuery_CreditWorthinessQuery This interface mapping connects SD systems with release version 4.6C or 4.70 to the credit check in SAP Credit Management. It is delivered with the XI content of the software component version FINBASIS_300 from support package 06. It maps the interface of the RFC module UKM_CREDIT_QUERY to the interface CreditWorthinessQuery_In. Message Mapping UkmCreditQuery_CreditWorthinessQuery The interface mapping with the same name described above uses this message mapping. The message mapping is also delivered with the XI content of the software component version FINBASIS_300 from support package 06.

Page 26 of 109


07/01/2006

SAP A2A Interfaces CreditCommitment_In and CreditCommitment_Out Description These interfaces provide SAP Credit Management with information about commitments. An application that has information about commitments of business partners sends this information to SAP Credit Management according to the company’s own rules or when requested to do so. The inbound information is collected and consolidated, thus enabling company-wide monitoring of the credit limits. There is a difference between commitment notification and commitment query. With commitment notification, the application sends the information at non-specific intervals to SAP Credit Management. With commitment query, SAP Credit Management actively requests the information from the application concerned.

System with Information about Commitments


CreditCommitmentNotification Commitment Notification

CreditCommitmentQuery Commitment Query

CreditCommitmentResponse

Page 27 of 109


07/01/2006

Message Interfaces CreditCommitmentNotification_In (inbound, asynchronous) When an application sends its information about commitments, the message interface is the inbound interface into SAP Credit Management. The message interface consists of the message type CreditCommitmentNotification. CreditCommitmentQuery_Out (outbound, synchronous) This message interface is used when SAP Credit Management requests information about commitments from the applications connected. Message type CreditCommitmentQuery is used for the query, whereas message type CreditCommitmentResponse represents the notification.

Message Types CreditCommitmentNotification This message type uses the data type CreditCommitmentMessage that represents a message for transferring a business partner’s existing commitments. CreditCommitmentQuery This message type uses the data type CreditCommitmentQueryMessage that represents a message for querying a business partner’s existing commitments. CreditCommitmentResponse This message type uses the data type CreditCommitmentMessage that represents a message for transferring a business partner’s existing payment obligations (commitments).

Data Types CreditCommitmentMessage The figure below shows the data type CreditCommitmentMessage that contains one or more entries of the data type CreditCommitment.

Page 28 of 109


07/01/2006

CreditCommitmentMessage CreditCommitment Message CreditCommitment CreditCommitment

CreditSegmentInternalId TypeCode Amount SecuredAmount UnsecuredAmount ValidityDate AmountBalanceIndicator AmountDifferenceIndicator DebtorParty CreditorParty SellerParty ProductCategory PendingCommitment InvoiceReference OutboundDeliveryReference SalesOrderReference IncomingPaymentReference AccountingDocumentReference PredecessorReference

The data type CreditCommitment contains the following elements: ●


Page 29 of 109


●

07/01/2006

TypeCode – Credit exposure category with the following standard values: ○

100 – Sales value (order value)

○

200 - Receivables

○

300 – Special credit exposure

○

400 – Value of goods supplied

○

500 – Special credit exposure

GDT: CreditCommitmentTypeCode ●

Amount – Amount GDT: Amount

●

SecuredAmount – Hedged amount GDT: Amount

●

UnsecuredAmount – Unhedged amount GDT: Amount

●

ValidityDate – Validity date GDT: Date

●

AmounceBalanceIndicator – Indicates whether it is a balance or a commitment GDT: AmountBalanceIndicator

●

AmountDifferenceIndicator – Indicates whether the amount is a difference amount GDT: AmountDifferenceIndicator

●

DebtorParty – Description of the customer whose payment obligations are reported GDT (InternalId): PartyInternalID

●

CredtorParty – Not used in SAP Credit Management

●


●


●

PendingCommitment – Related information about a payment obligation is grouped together to avoid temporary data inconsistencies when the commitment is updated in SAP Credit Management. The credit exposure is not updated immediately when the first message of a group is received; instead, it is stored in a temporary area until the following message(s) confirm this commitment. PendingCommitment contains the following elements: ○

GroupID – Identifier that links together related CreditCommitment messages

○

GDT:BusinessTransactionDocumentGroupID

○

CompletedIndicator – Indicates whether the business transaction is complete (in other words, whether the last message of the group has been received and the temporary commitment can be deleted).

○

GDT:BusinessTransactionCompletedIndicator

Page 30 of 109


07/01/2006

InvoiceReference – Reference to an outbound invoice document GDT: BusinessTransactionDocumentReference

●

OutboundDeliveryReference – Reference to an outbound delivery document GDT: BusinessTransactionDocumentReference

●

SalesOrderReference – Reference to a sales order GDT: BusinessTransactionDocumentReference

●

IncomingPaymentReference – Reference to an incoming payment GDT: BusinessTransactionDocumentReference

●

AccountingDocumentReference – Reference to an accounting document GDT: BusinessTransactionDocumentReference

●

PredecessorReference – Reference to a preceding document

CreditCommitmentQueryMessage The figure below shows the data type CreditCommitmentQueryMessage that contains one or more entries of the data type CreditCommitmentQuery.

CreditCommitmentQueryMessage CreditCommitment QueryMessage CreditCommitmentQuery CreditCommitment Query

CreditSegmentInternalId ValidityDate DebtorParty CreditorParty SellerParty ProductCategory

The data type CreditCommitmentQuery contains the following elements: ●

CreditSegmentInternalId – Credit segment in SAP Credit Management for which the connected systems send the commitments GDT: CreditSegmentInternalID

Page 31 of 109


07/01/2006

ValidityDate – Validity date GDT: Date

●

DebtorParty – Description of the customer whose payment obligations are to be reported GDT (InternalId): PartyInternalID

●


●


●


Mapping Objects Interface Mapping UkmCommitmentsPush_CreditCommitmentNotification This interface mapping connects Accounts Receivable Accounting systems or SD systems with release version 4.6C or 4.70 to SAP Credit Management. It is delivered with the XI content of the software component version FINBASIS_300 from support package 06. It maps the interface of the RFC module UKM_COMMMITMENTS_PUSH to the interface CreditCommitmentNotification_In. Message Mapping UkmCommitmentsPush_CreditCommitmentNotification The interface mapping with the same name described above uses this message mapping. The message mapping is also delivered with the XI content of the software component version FINBASIS_300 from support package 06.

Page 32 of 109


07/01/2006

SAP A2A Interface CreditPaymentRecord_In Description CreditPaymentRecord transfers payment behavior summaries of business partners bundled.

The interface CreditPaymentRecord_In is replaced by the interface CreditPaymentBehaviourSummaryNotification_In from mySAP ERP 2005; the new interface contains more key figures. However, you can still use the interface CreditPaymentRecord_In after an upgrade to mySAP ERP 2005. For more information about the interface CreditPaymentBehaviourSummaryNotification_In, see SAP A2A Interface CreditPaymentBehaviourSummaryNotification_In [Page 36].

System with Information about Payment Behavior Summaries


CreditPaymentRecord

Message Interfaces CreditPaymentRecordNotification_In (inbound, asynchronous) When an application sends its payment behavior summaries, the message interface is the inbound interface into SAP Credit Management. The message interface consists of the message type CreditPaymentRecordNotification.

Page 33 of 109


07/01/2006

Message Types CreditPaymentRecordNotification This message type consists of the data type CreditPaymentRecordMessage that represents a message for transmitting the payment behavior summaries for business partners.

Data Types CreditPaymentRecordMessage The figure below shows the data type CreditPaymentRecordMessage that contains one or more entries of the data type CreditPaymentRecord.

Page 34 of 109


07/01/2006

CreditPaymentRecordMessage CreditPayment RecordMessage CreditPaymentRecord CreditPayment Record

CreditSegmentInternalId ReferenceDocumentDate DebtorParty CreditorParty SellerParty ProductCategory LastPayment OpenItem Dunning KeyFigures InvoiceReference IncomingPaymentReference DunningReference

The CreditPaymentRecord data type contains the following elements: ●


●

ReferenceDocumentDate – Date of reference document GDT: Date

●

DebtorParty – Description of the customer whose payment behavior summaries are reported GDT (InternalId): PartyInternalID

Page 35 of 109


07/01/2006

●


●


●


●

LastPayment – Payment amount and date of last payment

●

OpenItem – Highest open item amount with due date

●

Dunning – Dunning information (amount, date, number of dunning notices, highest dunning level)

●

KeyFigures – Payment behavior summary without line item reference ○

ReceivablesAmount – Weighted receivables total

○

DaysOfSalesOutstanding – Number of days of overdue items

○

OverdueOpenItemsPercentage

- Proportion of overdue items in the total

●

InvoiceReference – Reference to an invoice document

●

IncomingPaymentReference – Reference to a payment document

●

DunningReference – Reference to a dunning transaction document

Mapping Objects Interface Mapping UkmVectorPush_CreditPaymentRecordNotification This interface mapping connects Accounts Receivable Accounting systems with release version 4.6C or 4.70 to SAP Credit Management. It is delivered with the XI content of the software component version FINBASIS_300 from support package 06. It maps the interface of the RFC module UKM_VECTOR_PUSH to the interface CreditPaymentRecordNotification_In. Message Mapping UkmVectorPush_CreditPaymentRecordNotification The interface mapping with the same name described above uses this message mapping. The message mapping is also delivered with the XI content of the software component version FINBASIS_300 from support package 06.

Page 36 of 109


07/01/2006

SAP A2A Interface CreditPaymentBehaviourSummaryNotification_In Definition CreditPaymentBehaviourSummary transfers information about the payment behavior or business partners.

System with Information about Payment Behavior


CreditPaymentBehaviourSummary

Message Interfaces CreditPaymentBehaviourSummaryNotification_In (inbound, asynchronous) When an application sends its payment behavior summaries, the message interface is the inbound interface into SAP Credit Management. The message interface uses the message types CreditPaymentBehaviourSummaryNotification and CreditPaymentBehaviourSummaryFault.

Message Types CreditPaymentBehaviourSummaryNotification This message type consists of the data type CreditPaymentBehaviourSummaryMessage that represents a message for transmitting the payment behavior summaries for business partners. CreditPaymentBehaviourSummaryFault This message type uses the data type ExchangeFaultData that carries out a standard transfer of exceptions that arise in SAP Credit Management.

Page 37 of 109


07/01/2006

Data Types CreditPaymentBehaviourSummaryMessage The figure below shows the data type CreditPaymentBehaviourSummaryMessage that contains one or more entries of the data type CreditPaymentBehaviourSummary.

CreditPaymentBehaviourSummaryMessage CreditPayment Behaviour Summary Message

CreditPayment Behaviour Summary

CreditPaymentBehaviourSummary

CreditSegmentInternalId DebtorParty CreditorParty SellerParty ProductCategory LastPayment OldestOpenItem MaximumLevelDunnedOpenItem DunningCounterValue CumulatedReceivablesAmount DaysOfSalesOutstandingDuration OverdueOpenItemsPercent LastTwelveMonthsMaximum CreditExposureAmount LesTwelveMonthsMaximum SalesVolumeAmount WithoutDiscountPayments WithDiscountPayments

The CreditPaymentBehaviourSummary data type contains the following elements: ●

CreditSegmentInternalId – Credit segment in SAP Credit Management

Page 38 of 109


07/01/2006

GDT: CreditSegmentInternalID ●

DebtorParty – Description of the customer whose payment behavior summaries are reported GDT: PartyInternalID

●

CreditorParty – The party that owns a receivable from a customer; can be used to derive the credit segment

●

SellerParty – The party that has sold a product to the customer; can be used to derive the credit segment

●

ProductCategory – The product category of the product sold to the customer; can be used to derive the credit segment

●

LastPayment – Payment amount and date of last payment

●

OldestOpenItem – Highest open item amount with due date

●

MaximumLevelDunnedOpenItem – Open item with highest dunning level

●

DunningCounterValue – Number of dunned, outstanding receivables due from the customer GDT: DunningCounterValue

●

CumulatedReceivablesAmount– Cumulative receivables total that can also be subjected to interest with a fictitious interest rate GDT: Amount

●

DaysOfSalesOutstandingDuration – Receivables total measured in days sales of business with the customer GDT: Duration (specification in days)

●

OverdueOpenItemsPercent – Percentage of the amount of all overdue open items of the total amount of all open items of the customer GDT: Percent

●

LastTwelveMonthsMaximumCreditExposureAmount – Highest credit exposure of the customer in the last twelve months GDT: Amount

●

LastTwelveMonthsSalesVolumeAmount – Sales with the customer in the last twelve months GDT: Amount

●

WithoutDiscountPayments – Key figures for payments of the customer where there was a complete or partial loss of cash discount (not taking cash discount can indicate poor liquidity)

●

WithDiscountPayments – Key figures for payments of the customer where maximum cash discount was taken (claiming cash discount can indicate sufficient liquidity)

Mapping Objects No mapping objects exist for the interface.

Page 39 of 109


07/01/2006

SAP B2B Interface CreditAgencyReportQuery_Out Description This interface requests credit information about a business partner from an information provider. An information provider is a company that provides business information about private or business relationships of other parties, in particular with regard to their creditworthiness. Examples are Dun & Bradstreet and SCHUFA. With the information received about the estimated creditworthiness, payment reliability, and other financial information, SAP Credit Management can carry out scoring for the business partner. The interface has two message types: ●

CreditAgencyReportQuery structures the message for requesting credit information

●

CreditAgencyReportResponse structures the response message that contains the required credit information


Information Provider CreditAgencyReportQuery CreditAgencyReportResponse

Message Interfaces CreditAgencyReportQuery_Out (outbound, synchronous) If SAP Credit Management requests external credit information, the message interface is the outbound interface. The query to the external information system takes place synchronously. The message interface consists of the message types CreditAgencyReportQuery and CreditAgencyReportResponse.

Page 40 of 109


07/01/2006

Message Types CreditAgencyReportQuery This message type consists of the data type CreditAgencyReportQueryMessage, which represents a message for requesting external credit information. CreditAgencyReportResponse This message type consists of the data type CreditAgencyReportResponseMessage, which represents a response to the external credit information query.

Data Types CreditAgencyReportQuery The figure below shows the data type CreditAgencyReportQueryMessage that contains an entry of the data type MessageHeader and an entry of the data type CreditAgencyReportQuery.

CreditAgencyReportQueryMessage CreditAgency ReportQuery Message

MessageHeader MessageHeader ID ReferenceID CreationDateTime SenderParty RecipientParty

CreditAgencyReportQuery CreditAgency ReportQuery ReasonCode DebtorParty Service

Page 41 of 109


07/01/2006

The data type MessageHeader contains the following elements: ●

ID – Unique identifier for the message GDT: MessageID

●

ReferenceID – Unique identifier for the response message delivered in CreditAgencyReportResponse GDT: MessageID

●

CreationDateTime – Date and time of creation of the message GDT: DateTime

●

SenderParty – Sender of the message (SAP Credit Management system) GDT: BusinessDocumentMessageHeaderParty

●

RecipientParty – Recipient of message GDT: BusinessDocumentMessageHeaderParty

The data type CreditAgencyReportQuery contains the following elements: ●

ReasonCode – Reason for the query GDT: CreditAgencyReportQueryReasonCode

●

DebtorParty – The party (debtor) about whom credit information is to be given DebtorParty contains the following elements: ○

StandardID – Standardized identifier for the party to be checked GDT: PartyStandardID

○

CreditAgencyID – Identifier for the party to be checked; assigned by the information provider GDT: PartyPartyID

○

Address – Address of the party to be checked GDT: Address, whereby FunctionalTitleName, DepartmentName, Office, TaxJurisdictionCode, TimeZoneDifferenceValue, GeoCoordinates are not used

○

IncorporationDate – Incorporation date of a company, if the party to be checked is a company GDT: Date

○

BirthDate – Date of birth of a natural person, if the party to be checked is a natural person GDT: Date

●

Service – Type and scope of the service required from the information provider Service contains the following elements: ○

CreditAgencyID – Identifier of the required service assigned by the information provider (according to the service catalog of the information provider) GDT: ProductPartyID

Page 42 of 109

SAP Credit Management Configuration Guide ○

07/01/2006

LanguageCode – Language in which the results of the service requested are to be delivered GDT: LanguageCode

CreditAgencyReportResponse The figure below shows the data type CreditAgencyReportResponseMessage that contains an entry of the data type MessageHeader and an entry of the data type CreditAgencyReportResponse.

CreditAgencyReportResponseMessage CreditAgency ReportResponse Message

MessageHeader MessageHeader ID ReferenceID CreationDateTime SenderParty RecipientParty

CreditAgencyReportResponse CreditAgency ReportResponse CreationLog DebtorParty CreditRating CreditRiskClass Scoring CreditLimit LegalEvent

Page 43 of 109


07/01/2006

For the elements of the data type MessageHeader see the data type CreditAgencyReportQuery above. The CreditAgencyReportResponse data type contains the following elements: ●

CreationLog – A summary of information about the creation of credit information

●

DebtorParty – Summary of the information about the party about whom credit information is to be given

●

CreditRating – Rating value for a party determined by the information provider and valid for a specific period

●

CreditRating – Rating value for a party determined by the information provider and valid for a specific period

●

Scoring – Result of the rating of a party with regard to its creditworthiness using a scorecard specified by an information provider

●

CreditLimit – Credit limit valid for a party for a specific period

●

LegalEvent – A legal event concerning the creditworthiness of a party


Page 44 of 109


07/01/2006

SAP A2A Interface CreditWorthinessCriticalPartiesQuery_In Description This interface describes business partners that are rated as critical with regard to their creditworthiness. The interface consists of the following actions: ●

Sending a query (CreditWorthinessCriticalPartiesQuery)

●

Receiving a response that contains a list of critical business partners (CreditWorthinessCriticalPartiesResponse)

These interfaces are motivated by the necessity of providing Financial Accounting with a list of business partners whose score is negative, for example. An application, Contract Accounts Receivable and Payable (FI-CA), for example, sends a query with a number of business partners to SAP Credit Management. SAP Credit Management provides a negative customer list with business partners with negative ratings.

Querying System


CreditWorthinessCriticalPartiesQuery CreditWorthinessCriticalPartiesResponse

Message Interfaces CreditWorthinessCriticalPartiesQuery_In (inbound, synchronous) If an application requests a list of the critical business partners, the message interface is the inbound interface to SAP Credit Management. The list of critical partners is delivered to the querying system synchronously via the interface. The message interface uses the message types CreditWorthinessCriticalPartiesQuery and CreditWorthinessCriticalPartiesResponse.

Page 45 of 109


07/01/2006

Message Types CreditWorthinessCriticalPartiesQuery This message type consists of the data type CreditWorthinessCriticalPartiesQueryMessage, which represents a message for querying the quantity of critical business partners. CreditWorthinessCriticalPartiesResponse This message type uses the data type CreditWorthinessCriticalPartiesMessage that represents a response to the query regarding the quantity of critical partners.

Data Types CreditWorthinessCriticalPartiesQuery The figure below shows the data type CreditWorthinessCriticalPartiesQueryMessage that contains one or more entries of the data type CreditWorthinessCriticalPartiesQuery.

The data type CreditWorthinessCriticalPartiesQuery contains the following elements: ●


●

DebtorPartyInterval – Business partner interval to be checked for critical partners

●


Page 46 of 109



●


07/01/2006

CreditWorthinessCriticalPartiesResponse The figure below shows the data type CreditWorthinessCriticalPartiesReponseMessage that contains one or more entries of the data type CreditWorthinessCriticalPartiesResponse.

The data type CreditWorthinessCriticalPartiesResponse contains the following elements: ●


●

DebtorParty – Critical business partner

●


●


●



Page 47 of 109


07/01/2006

SAP A2A Interface CreditWorthinessChangeInformation_Out Description CreditWorthinessChangeInformation is a message that contains information about changes to the creditworthiness of a business partner. Once a credit limit or rating check has been performed for a connected system, interested applications (that are connected to SAP Credit Management) are provided with new information. For example, the current and earlier rating values of a business partner are sent or messages from the creditworthiness check, such as the reason for a negative result.


System Connected

CreditWorthinessChangeInformation

Message Interfaces CreditWorthinessChangeInformation_Out (outbound, asynchronous) If an event that is to be published externally is triggered in SAP Credit Management, the message interface is the outbound interface. The message interface uses the message type CreditWorthinessChangeInformation.

Message Types CreditWorthinessChangeInformation This message type uses the data type CreditWorthinessChangeMessage that represents a message with changed information from SAP Credit Management.

Page 48 of 109


07/01/2006

Data Types CreditWorthinessChangeMessage The figure below shows the data type CreditWorthinessChangeMessage that contains one or more entries of the data type CreditWorthinessChange.

The data type CreditWorthinessChange contains the following elements: ●


●

ReasonCode – Reason for a block in SAP Credit Management

●

CheckingDescription – Description of the flow of a creditworthiness check GDT: Description

●

DebtorParty – Description of the customer whose payment behavior summaries are reported GDT (InternalId): PartyInternalID

Page 49 of 109


07/01/2006

●


●


●


●

Rating – Valid score of a business partner determined by SAP Credit Management and valid for a specific period

●

RiskClass – The risk of non-payment determined by SAP Credit Management and valid for a specific period; can be connected to closing

●

CreditLimit – Credit limit valid for a business partner for a specific period

●

CreditExposure – Existing credit exposure of a business partner valid for a specific period


Use No recipients of events that are sent from SAP Credit Management are delivered with the standard. For an example implementation of a customer module that receives and processes events in an SAP system (SAP R/3 4.6C, SAP R/3 Enterprise 4.70, or mySAP ERP 2004) connected to SAP Credit Management via XI, see SAP Note 813285.

Page 50 of 109


07/01/2006

SAP Component Interface FICARatingReplicate Description The asynchronous interfaces FICARatingReplicateQuery and FICARatingReplicateResponse enable you to exchange the following creditworthiness values: ●

Score from SAP Credit Management

●

Creditworthiness from Contract Accounts Receivable and Payable (FI-CA creditworthiness)

The FI-CA creditworthiness is transferred to SAP Credit Management by means of the interface FICARatingReplicateQuery. There, the calculation of the score can be triggered; the value of the score is then transferred to FI-CA by means of the interface FICARatingReplicateResponse.


Contract Accounts Receivable and Payable (FI-CA)

FICARatingReplicateQuery

FICARatingReplicateResponse

Page 51 of 109


07/01/2006

Message Interfaces FICARatingReplicateQuery_In (inbound, asynchronous) If Contract Accounts Receivable and Payable sends the FI-CA creditworthiness, the message interface is the inbound interface to SAP Credit Management. The message interface consists of the message type FICARatingReplicateQuery. FICARatingReplicateResponse_Out (outbound, asynchronous) This message interface is used when SAP Credit Management informs Contract Accounts Receivable and Payable about the score. The message interface consists of the message type FICARatingReplicateResponse.

Message Types FICARatingReplicateQuery This message type consists of the data type FICARatingReplicateQuery that represents a message for transmitting the FI-CA creditworthiness of a business partner. FICARatingReplicateResponse This message type consists of the data type FICARatingReplicateResponse that represents a message for transmitting the score of a business partner.

Data Types FICARatingReplicateQuery The FICARatingReplicateQuery data type contains the following elements: ●

ProcedureCode – Rating procedure in SAP Credit Management

●

DebtorParty – Business partner with creditworthiness rating DebtorParty contains the following elements: ○

InternalID – Business partner number in Contract Accounts Receivable and Payable

○

RatingCode – FI-CA creditworthiness value

FICARatingReplicateResponse The FICARatingReplicateResponse data type contains the following elements: ●

DebtorParty – Business partner with creditworthiness rating DebtorParty contains the following elements: ○

InternalID – Business partner number in Contract Accounts Receivable and Payable

○

RatingCode – Value of score in SAP Credit Management

Mapping Objects No interface mapping is required since the interfaces in Contract Accounts Receivable and Payable use the same data types as the interfaces in SAP Credit Management.

Page 52 of 109


07/01/2006

Connecting External Information Providers Use 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 WSDLXSD 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.

Page 53 of 109


07/01/2006

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

■

Message protocol = XI Payload in HTTP Body

Page 54 of 109


○

■

Adapter Engine = Integration Server

■

Addressing type = HTTP destination

■

Content type = application/x-www-form-urlencoded

07/01/2006

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.

Each information requested is subject to costs.

Page 55 of 109


07/01/2006

Connecting Accounts Receivable Accounting ERP 2005 Use To update items and payment behavior summaries from Accounts Receivable Accounting (FIAR) with Release mySAP ERP 2005 in SAP Credit Management, connect your FI-AR system to the SAP Credit Management system via XI interfaces. For more information on the relevant XI interfaces, see SAP A2A-Interfaces CreditCommitment_In und CreditCommitment_Out [Page 26] and SAP A2A-Interface CreditPaymentRecord_In [Page 32].

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 SAP NetWeaver Library → Key Functional Areas of SAP NetWeaver → Key Functional Areas of Process Integration → SAP NetWeaver Exchange Infrastructure → Design and Configuration Time → Integration Builder and Configuration.

Procedure ...

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 XIChannel. 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 XIChannel. 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.

Page 56 of 109


07/01/2006

Connecting Accounts Receivable Accounting ERP 2004 Use To update items and FI summaries from Accounts Receivable Accounting (FI-AR) Release mySAP ERP 2004 in SAP Credit Management, connect your FI-AR system to the SAP Credit Management system via XI interfaces. For more information on the relevant XI interfaces, see SAP A2A-Interfaces CreditCommitment_In und CreditCommitment_Out [Page 26] and SAP A2A-Interface CreditPaymentRecord_In [Page 32].


Procedure 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 XIChannel. 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 XIChannel. 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.

Note the differences in terminology between applications with different releases – from mySAP ERP 2005, the use of some terms from SAP Credit Management has changed. For more information, see Terminology Changes from mySAP ERP 2005 [Page 14] .

Page 57 of 109


07/01/2006

Connecting Accounts Receivable Accounting 4.70 or 4.6C Use To update items and FI summaries from Accounts Receivable Accounting (FI-AR) Release SAP R/3 Enterprise 4.70 or SAP R/3 4.6C in SAP Credit Management, connect your FI-AR system to the XI interfaces of the Credit Management system via RFC adapter. For more information on the relevant XI interfaces, see SAP A2A-Interfaces CreditCommitment_In und CreditCommitment_Out [Page 26] and SAP A2A-Interface CreditPaymentRecord_In [Page 32]. For a “How to” guide with screenshots, see the attachment to SAP Note 794772.


Procedure 1. Integrate the sender interface UKM_COMMMITMENTS_PUSH from the namespace urn:sap-com:document:sap:rfc:functions using the interface mapping UkmCommitmentsPush_CreditCommitmentNotification from the namespace http://sap.com/xi/FSCM/Global with the receiver interface CreditCommitmentNotification_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel XIChannel. 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.

Page 58 of 109


2.

07/01/2006

Integrate the sender interface UKM_VECTOR_PUSH from the namespace urn:sapcom:document:sap:rfc:functions using the interface mapping UkmVectorPush_CreditPaymentRecordNotification from the namespace http://sap.com/xi/FSCM/Global with the receiver interface CreditPaymentRecordNotification_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel XIChannel. 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.


Connecting Contract Accounts Receivable and Payable 6.00 Use To integrate Release 6.00 of Contract Accounts Receivable and Payable (FI-CA) with SAP Credit Management, you have to integrate your FI-CA system with the XI interfaces of the Credit Management system. For more information on the relevant XI interfaces, see SAP A2A-Interfaces CreditCommitment_In und CreditCommitment_Out [Page 26], SAP A2AInterface CreditWorthinessCriticalPartiesQuery_In [Page 44], and SAP A2A-Interface CreditWorthinessQuery_In [Page 21].

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 SAP NetWeaver Library → Key Functional Areas of SAP NetWeaver → Key Functional Areas of Process Integration → SAP NetWeaver Exchange Infrastructure → Design and Configuration Time → Integration Builder and Configuration. Make sure that the XI content of the software components FI-CA and FSCM is installed in the Integration Repository of your XI server. You can access the XI 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 ...

1. Integrate the sender interface CreditCommitmentNotification_Out from the namespace http://sap.com/xi/FICA/Global with the receiver interface CreditCommitmentNotification_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel XIChannel. The sender is the FI-CA system. The receiver is the SAP Credit Management system. Using this connection you can update credit exposure information from Contract Accounts Receivable and Payable in SAP Credit Management.

Page 59 of 109


07/01/2006

2. Integrate the sender interface CreditCommitmentQuery_Out from the namespace http://sap.com/xi/FSCM/Global with the receiver interface CreditCommitmentQuery_In from the namespace http://sap.com/xi/FICA/Global via the receiver communication channel XIChannel. 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. Integrate the sender interface CreditPaymentBehaviourSummaryNotification_Out from the namespace http://sap.com/xi/FICA/Global with the receiver interface CreditPaymentBehaviourSummaryNotification_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel XIChannel. 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. Integrate the sender interface FICARatingReplicateQuery_Out from the namespace http://sap.com/xi/FICA/Global with the receiver interface FICARatingReplicateQuery_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel XIChannel. The sender is the FI-CA system. The receiver is the SAP Credit Management system. Using this connection, you can transfer the FI-CA creditworthiness from Contract Accounts Receivable and Payable to SAP Credit Management. 5. Integrate the sender interface FICARatingReplicateResponse_Out from the namespace http://sap.com/xi/FSCM/Global with the receiver interface FICARatingReplicateResponse_In from the namespace http://sap.com/xi/FICA/Global via the receiver communication channel XIChannel. The sender is the SAP Credit Management system. The receiver is the FI-CA system. Using this connection, you can transfer the score from SAP Credit Management to Contract Accounts Receivable and Payable. 6. Integrate the sender interface CreditWorthinessCriticalPartiesQuery_Out from the namespace http://sap.com/xi/FICA/Global with the receiver interface CreditWorthinessCriticalPartiesQuery_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel XIChannel. 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. 7. Integrate the sender interface CreditWorthinessQuery_Out from the namespace http://sap.com/xi/FICA/Global with the receiver interface CreditWorthinessQuery_Out_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel XIChannel. 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

○

Carry out a credit check for a business partner from Contract Accounts Receivable and Payable in SAP Credit Management

Page 60 of 109


07/01/2006

Connecting Contract Accounts Receivable and Payable 4.72 Use To integrate Release 4.72 of Contract Accounts Receivable and Payable (FI-CA) with SAP Credit Management, you have to integrate your FI-CA system with the XI interfaces of the Credit Management system. For more information about the relevant XI interfaces, see: ●

SAP A2A Interfaces CreditCommitment_In and CreditCommitment_Out [Page 26]

●

SAP A2A Interface CreditPaymentRecord_In [Page 32]

●

SAP A2A Interface CreditWorthinessCriticalPartiesQuery_In [Page 44]

●

SAP A2A Interface CreditWorthinessQuery_In [Page 21]

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 SAP NetWeaver Library → Key Functional Areas of SAP NetWeaver → Key Functional Areas of Process Integration → SAP NetWeaver Exchange Infrastructure → Design and Configuration Time → Integration Builder and Configuration. Make sure that the XI content of the software components FI-CA and FSCM is installed in the Integration Repository of your XI server. You can access the XI content for Contract Accounts Receivable and Payable as a patch on SAP Service Marketplace under the respective industry solution (for example SAP IS-T 4.72).

Procedure ...

1. Integrate the sender interface CreditCommitmentNotification_Out from the namespace http://sap.com/xi/FICA/Global with the receiver interface CreditCommitmentNotification_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel XIChannel. 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 CreditCommitmentQuery_In from the namespace http://sap.com/xi/FICA/Global via the receiver communication channel XIChannel. The sender is the SAP Credit Management system. The receiver is the FI-CA system. Using this connection you can query liability information from SAP Credit Management in Contract Accounts Receivable and Payable (commitment query).

Page 61 of 109


07/01/2006

3. Integrate the sender interface CreditPaymentRecordNotification_Out from the namespace http://sap.com/xi/FICA/Global with the receiver interface CreditPaymentRecordNotification_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel XIChannel. The sender is the FI-CA system. The receiver is the SAP Credit Management system. Using this connection you can update FI summaries from Contract Accounts Receivable and Payable in SAP Credit Management. 4. Integrate the sender interface FICARatingReplicateQuery_Out from the namespace http://sap.com/xi/FICA/Global with the receiver interface FICARatingReplicateQuery_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel XIChannel. The sender is the FI-CA system. The receiver is the SAP Credit Management system. Using this connection, you can transfer the FI-CA creditworthiness from Contract Accounts Receivable and Payable to SAP Credit Management. 5. Integrate the sender interface FICARatingReplicateResponse_Out from the namespace http://sap.com/xi/FSCM/Global with the receiver interface FICARatingReplicateResponse_In from the namespace http://sap.com/xi/FICA/Global via the receiver communication channel XIChannel. The sender is the SAP Credit Management system. The receiver is the FI-CA system. Using this connection, you can transfer the score from SAP Credit Management to Contract Accounts Receivable and Payable. 6. Integrate the sender interface CreditWorthinessCriticalPartiesQuery_Out from the namespace http://sap.com/xi/FICA/Global with the receiver interface CreditWorthinessCriticalPartiesQuery_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel XIChannel. 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. 7. Integrate the sender interface CreditWorthinessQuery_Out from the namespace http://sap.com/xi/FICA/Global with the receiver interface CreditWorthinessQuery_Out_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel XIChannel. 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.


Page 62 of 109


07/01/2006

Connecting Sales and Distribution ERP 2005 Use You connect your SD system(s) with Release mySAP ERP 2005 with SAP Credit Management through XI interfaces to enable the following: ●

Performance of credit checks from sales orders

●

Update of commitments from orders or from billing documents not yet transferred to accounting

For more information on the relevant XI interfaces, see SAP A2A-Interface CreditWorthinessQuery_In [Page 21] and SAP A2A-Interfaces CreditCommitment_In und CreditCommitment_Out [Page 26].


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 XIChannel. 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 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 XIChannel. 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.

Page 63 of 109


07/01/2006

Connecting Sales and Distribution ERP 2004 Use You connect your SD system(s) with Release mySAP ERP 2004 with SAP Credit Management through XI interfaces to enable the following: ●


●

Update of liabilities from orders or from billing documents not yet transferred to accounting

For more information on the relevant XI interfaces, see SAP A2A-Interface CreditWorthinessQuery_In [Page 21] and SAP A2A-Interfaces CreditCommitment_In und CreditCommitment_Out [Page 26].


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 XIChannel. 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 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 XIChannel. 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 liability information from SD (order values and values of blocked billing documents) to SAP Credit Management.


Page 64 of 109


07/01/2006

Connecting Sales and Distribution 4.70 or 4.6C Use You connect your SD system(s) with Release SAP R/3 Enterprise 4.70 or SAP R/3 4.6C with SAP Credit Management via XI interfaces to enable the following: ●


●

Update of liabilities from orders or from billing documents not yet transferred to accounting

For more information on the relevant XI interfaces, see SAP A2A-Interface CreditWorthinessQuery_In [Page 21] and SAP A2A-Interfaces CreditCommitment_In und CreditCommitment_Out [Page 26]. For a “How to” guide with screenshots, see the attachment to SAP Note 794772.

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 SAP NetWeaver Library → Key Functional Areas of SAP NetWeaver → Key Functional Areas of Process Integration → SAP NetWeaver Exchange Infrastructure → Design and Configuration Time → Integration Builder and Configuration. You have implemented SAP Note 768995.

Procedure 1. Integrate the sender interface UKM_CREDIT_QUERY from the namespace urn:sapcom:document:sap:rfc:functions using the interface mapping UkmCreditQuery_CreditWorthinessQuery from the namespace http://sap.com/xi/FSCM/Global with the receiver interface CreditWorthinessQuery_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel XIChannel. 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 interface UKM_COMMMITMENTS_PUSH from the namespace urn:sap-com:document:sap:rfc:functions using the interface mapping UkmCommitmentsPush_CreditCommitmentNotification from the namespace http://sap.com/xi/FSCM/Global with the receiver interface CreditCommitmentNotification_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel XIChannel. 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 liability information from SD (order values and values of blocked billing documents) to SAP Credit Management.

Page 65 of 109


07/01/2006


Connecting Customer Relationship Management (CRM) Use You connect your CRM system(s) with SAP Credit Management through XI interfaces to enable the following: ●

Performance of credit checks from CRM transactions

●

Update commitments from CRM transactions or billing documents

CRM is connected to SAP Credit Management in a customer project solution. For more information on the relevant XI interfaces, see SAP A2A-Interface CreditWorthinessQuery_In [Page 21] and SAP A2A-Interfaces CreditCommitment_In und CreditCommitment_Out [Page 26].

Prerequisites ●

You use CRM 5.0 or have installed CRM 2004 Industry Addon 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.

For more information, see the SAP Library under SAP NetWeaver Library → Key Functional Areas of SAP NetWeaver → Key Functional Areas of Process Integration → SAP NetWeaver Exchange Infrastructure → Design and Configuration Time → Integration Builder 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 XIChannel. 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.

Page 66 of 109


07/01/2006

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 (CRM-Release 5.0) with the receiver interface CreditCommitmentNotification_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel XIChannel. 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.

Page 67 of 109


07/01/2006

Data Replication Purpose This section contains information about replicating Customizing, master data, and transaction data. This involves, for example: ●

Activities to initially transfer data from the Online Transaction Processing System (OLTP) to the Online Analytical Processing System (OLAP)

●

Automatic replication activities

●

Manual replication activities, for example, because automatic replication is not possible


Providing Business Partner Data Use The master data of SAP Credit Management is an enhancement of SAP Business Partner. A master record of SAP Business Partner must exist in the system and client in which SAP Credit Management is run for each business partner that you wish to monitor.

Integration ●

If you install SAP Credit Management in a system in which business partner master records already exist, SAP Credit Management can easily access these tables. 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, for example, 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). Copies of the master data of SAP Business Partner are then 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 about the master data in Accounts Receivable Accounting, see Replicating Master Data of Accounts Receivable Accounting (FI-AR) [Page 69]. For information about the master data in Contract Accounts Receivable and Payable, see Replicating Master Data of Contract Accounts Receivable and Payable (FI-CA) [Page 70].

Page 68 of 109


07/01/2006

Replicating Master Data of Accounts Receivable Accounting (FI-AR) Use The master data required for SAP Credit 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 technoloigy for the master data replication, for example, your own development. SAP Credit 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 IMG activities. To access the Customizing of Master Data Synchronization, choose Cross-Application Components → Master Data Synchronization. IMG activities Menu Path

Comments

Cross-Application Components → Master Data Synchronization → Synchronization Control → Synchronization Control → Synchronization Objects

Make sure that the synchronization objects BP and CUSTOMER delivered with the standard exist.

Cross-Application Components → General Application Functions→ Postprocessing Office → Business Processes → Activate Creation of Postprocessing Orders

Since the Postprocessing Office (PPO) is connected via the synchronization cockpit for the master data synchronization, activate the the creation of postprocessign orders for the business processes of the software component AP-MD.

Cross-Application Components → Master Data Synchronization → Synchronization Control → Synchronization Control → Activate PPO Requests for Platform Objects in Dialog

Set the activation indicator for the PPO object BP. This means that where synchronization attempts fail, PPO requests where the errors are logged are written. The PPO requests are available via the Post Processing Desktop (transaction MDS_PPO2) or from the Synchronization Cockpit (transaction MDS_LOAD_COCKPIT).

Cross-Application Components → Master Data Synchronization → Synchronization Control → Synchronization Control → Activate Synchronization Options

Activate the master data synchronization for source object BP in target object CUSTOMER and source object CUSTOMER in target object BP.

Cross-Application Components → Master Data Synchronization → Customer/Vendor Integration → Business Partner Settings → Settings for Customer Integration → Configure BP Role Category for Direction BP to Customer and Define BP Role for Direction Customer to BP

Define the business partner role categories and customer account groups to be synchronized.

Page 69 of 109


Cross-Application Components → Master Data Synchronization → Customer/Vendor Integration → Business Partner Settings → Settings for Customer Integration → Field Assignment for Customer Integration → Assign Keys → Define Number Assignment for Direction BP to Customer and Define Number Assignment for Direction Customer to BP

07/01/2006

Define the number assignment for both direction of the synchronization.

Replicating Master Data of Contract Accounts Receivable and Payable (FI-CA) Use The master data required for SAP Credit Management is grouped in a separate business partner role based on SAP Business Partner. The business partner master data is distributed using the XI interface ABABusinessPartner. For more information about this XI interface, see XI Content for Business Partners [Extern].

Prerequisites You are using a two-system scenario with the following constellation: ●

System with FI-CA (industry components Utilities and Telecommunications)

●

System with SAP Credit 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):

Page 70 of 109


07/01/2006

Event

Object

Item

Function Name

CRMIN

BUPA

2100000

BUPA_INBOUND_MAP_ROLES_CM

CRMIN

BUPA

2200000

BUPA_INBOUND_MAIN_ISU

CRMOU

BUPA

2100000

BUPA_OUTBOUND_BPS_MAP_ROLE_CM

CRMOU

BUPA

2200000

BUPA_OUTBOUND_BPS_FILL_ISU

CRMIN

BUPA

0230000

BUPA_XI_MAP_NUMRANGE

2. For the replication of business partner master data from SAP Credit Management to FICA, 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. 3. Replicate the business partner data using the XI interface ABABusinessPartner.

Page 71 of 109


07/01/2006

Business Customizing Purpose This section contains information about the Customizing settings in each system. Business Customizing adjusts the company-neutral delivered functionality to the specific requirements of the company. This involves, for example: ●

Organizational unit Customizing

●

Master data Customizing

●

Process Customizing


Settings in SAP Credit Management (FIN-FSCMCR) You make the basic settings for SAP Credit Management (FIN-FSCM-CR) in the system in which you have installed SAP Credit Management. For information about the 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.

Page 72 of 109


07/01/2006

Activating the Business Partner Role for Credit Management Use The credit master data [Extern] of your business partners is the basis of SAP Credit Management; it controls all credit-relevant ratings and analyses. In order for you to be able to edit the credit master data of your customers, the business partner role must be active for SAP Credit Management (UKM000 Credit Mgt Business Part.). Procedure ...

1. On the SAP Easy Access screen, enter BUPT with no other characters in front. The Business Partner: Task Menu screen appears. a. Choose Business Partner → Control → Applications. On the detail screen for the application UKM, set the indicator Active. b. Choose Business Partner → Control → Screen Sequences. Make sure that the screen sequence BUP001 contains the screen UKM100. c. Choose Business Partner → Control → Divisibility → BP Views. Make sure of the following entries for BP view UKM000: ■

As calling applications, the applications UKM and FS08 are entered.

■

As Subheader ID, subheader UKM110 is entered.

2. Using transaction SM30, call view V_TBZJ1C. Insert the following new table entry if it does not already exist: ○

Subheader

○

Item:

○

Active:

:

UKM110

6

X

3. In Customizing for Cross-Application Components, choose SAP Business Partner → Business Partner → Basic Settings → Business Partner Roles → Define BP Roles. a. Insert the following new role category if it does not already exist: ■

Role Category:

■

Title:


■

Name:


■

Differentiation Category:

■

Possible Business Partner Categories: Select all three categories.

UKM000

9

You need differentiation categor 9 to enter additional information for each segment.

Page 73 of 109


07/01/2006

b. Insert the following business partner role if it does not already exist: ■

BP Role:

■

Title:


■

Name:


■

BP Role Category:

■

Standard Assignment BP Role → BP Role Category:

■

BP View:

UKM000

UKM000 X

UKM000

Result In the master data editing for the business partner, you can now edit the credit master data of your customers. If you select the role for Credit Management (UKM000 Credit Mgt Business Part.), the tab page Credit Profile and the button Credit Segment Data are displayed.

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. 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.

Page 74 of 109


07/01/2006

Procedure Navigation Menu Path in SAP Customizing Implementation Guide (In Credit Management System)

Transaction Code

Financial Supply Chain Management → Credit Management → Credit Risk Monitoring → Credit Limit Check → Define Info Categories

UKM_INFOCAT

If you use SAP Banking, then also:

Otherwise:

SAP Banking → SAP Business Partner for Financial Services → Settings for Financial Services → General Settings → Enhancement Options → Additional Information → Configure Information Type

SM30 with the views V_TP19 and V_TP22

1. In the IMG 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. In Business Partner Maintenance, you can now select collateral with additional info types. 3. In the IMG activity Define Info Categories (UKM_INFOCAT), check whether the info types delivered for the info category Negative Credit Events 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 1, enter the corresponding entries in view V_TP19 with transaction SM30. In Business Partner Maintenance, you can now select negative credit events with additional info types. 5. In the IMG 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 1, enter the corresponding entries in view V_TP19 with transaction SM30. In Business Partner Maintenance, you can now select credit insurance with additional info types. 7. For the info category Check Exception, SAP delivers three info types (see IMG activity Define Info Categories (UKM_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 1, enter the corresponding entries in view V_TP19 with transaction SM30. 9. In Business Partner Maintenance, you can now deactivate more than three check steps. 10. If you have defined your own check steps (using customer-specific implementations of the Business Add-In 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.

Page 75 of 109


07/01/2006

You can now deactivate your own check steps using the check exceptions in the business partner master record.

Defining Authorizations Use You can control the right of access to SAP Credit Management data by assigning authorizations – separately by credit segment and activity - to the authorization object F_UKM_SGMT. The fields of this authorization object are: ●

Credit Segment

●

Activity, with the definitions ○

01 Add or create

○

02 Change

○

03 Display

○

06 Delete

○

08 Display Change Documents

○

43 Release

The role SAP_FIN_FSCM_CR_USER is delivered with all authorizations to 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. The fields of this authorization object are: ●

Application Log Object Name

●

Application Log Subobject

●

Activity, with the definitions ○

03 Display

○

06 Delete

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-MASS

ERROR, ERROR_BIG, ERROR_PROG, ERROR_UPD, INFO, STATISTICS, SUCCESS, WARNING

Logs of mass changes, can be differentiated by the severity of the error

Page 76 of 109


07/01/2006

Procedure ...

You can organize the authorizations of your users as follows: Activities

Authorization

Restrict access to one or more credit segments

F_UKM_SGMT with specified credit segment

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 data changes

F_UKM_SGMT

08

Release and reject credit limit changes/increases requested (dual control principle)

F_UKM_SGMT

43

Edit and display master data of SAP Credit Management

B_BUPA_RLT with the business partner role UKM000

Display and/or delete application logs of SAP Credit Management

S_APPL_LOG with the object names and subobjects listed above

03 06

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. Dependent on the activity performed, you can define whether an event is to be considered – that is, whether the followon 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 IMG activity. The two tables below should be considered as one unit. They show which events can trigger follow-on processes.

Page 77 of 109


07/01/2006

Table 1 Assignment Number of Follow-On Process for Table 2

Name of Follow-On Process

Follow-On Process

1

Determine Credit Limit of Account

EVL_LIMIT

2

Determine Credit Limit of All Accounts of Partner

EVL_LIMITS

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 Partner

INV_LIMITS

7

Invalidate Score

INV_RATING

8

Call Business Add-In

BADI

9

Set “Special Attention” Indicator

SET_FLAG

10

Block Business Partner in Credit Segment

SET_BLOCK

11

Perform Credit Check

CRD_RECHCK

12

Check Request for Limit Change

LIMIT_REQ

13

Start Workflow

WF

Table 2 Event

Value

Follow-On Process According to Assignment Number from Table 1 1

Score Invalid

IS

Score Changed

IC

External Rating Invalid

ES

External Rating Changed

EC

Credit Limit Invalid

CL

Credit Limit Changed

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

Change to Credit Limit Requested

LR

x

Credit Refused

CF

x

x

x

Payment Behavior Summary: Dunning Data Invalid

VD

x

x

x

Payment Behavior Summary: Due Date Invalid

VO

x

x

x

Payment Behavior Summary: Payment Data Invalid

VP

x

x

x

Payment Behavior Summary: Payment Behavior Index Invalid

VX

x

x

x

Generic Event Occurred

GE

x

x

x

x

x

x

x

x

x

Rule for Scoring and Credit Limit Calculation Changed

RC

x

x

x

x

x

x

x

x

Page 78 of 109

x x

x x

x

x

x

x x


07/01/2006

Risk Class Changed

XC

x

Limit Utilization Changed

UC

x

Limit Utilization Exceeds 100%

UU

x

Limit Utilization Below 100% Again

UD

x

Payment Behavior Summary Changed

VC

x

Check Procedure Changed

x

x

x

x

x

x x

x

x

x

x

x

x

x

x x

x

x

x

TC

x

x

x

Error during Credit Exposure or Commitment Update

CE

x

x

Block Set in Credit Management

BL

x

x

Special Attention Indicator Set

SP

x

x

Page 79 of 109

x

x

x

x

x


07/01/2006

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) ○

Release mySAP ERP 2005 Making Settings in FI-AR ERP 2005 [Page 81]

○

Release mySAP ERP 2004 Making Settings in FI-AR ERP 2004 [Page 82]

○

Release SAP R/3 Enterprise 4.70 oder SAP R/3 4.6C: Making Settings in FI-AR 4.70 or 4.6C [Page 84]

●

Industry releases 4.72 and 6.00 of Contract Accounts Receivable and Payable (FI-CA) for the following solutions: ○

mySAP Insurance

○

mySAP Utilities

○

mySAP Telecommunications

○

mySAP Media

○

mySAP Public Sector (Public Sector FI-CA)

○

SAP Contract Accounts Receivable and Payable (FI-CA)

See Making Settings in Contract Accounts Receivable and Payable (FI-CA) [Page 87]. ●

Sales and Distribution (SD) ○

Release mySAP ERP 2005 Making Settings in SD ERP 2005 [Page 91]

○

Release mySAP ERP 2004 Making Settings in SD ERP 2004 [Page 93]

○

Release SAP R/3 Enterprise 4.70 oder SAP R/3 4.6C: Making Settings in SD 4.70 or 4.6C [Page 94]

●

SAP Customer Relationship Management (CRM) Making Settings in CRM [Page 95]

For information about the Customizing of the individual IMG activities, see the Implementation Guide (IMG). 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.

Page 80 of 109


07/01/2006

Making Settings in FI-AR ERP 2005 Use To update credit exposures and payment behavior summaries from one or more FI-AR systems with release mySAP ERP 2005 in SAP Credit Management, you have to make the following settings. You integrate FI-AR and SAP Credit Management by means of implementations of Business Add-Ins (BAdIs) and IMG activities.

Prerequisites In order to use the update options specified, you must also integrate your FI-AR system with SAP Credit Management using XI interfaces (see configuration step Connecting Accounts Receivable Accounting ERP 2005 [Page 56]). You can execute these steps independently of one another and in any order. You have configured the business partner data for SAP Credit Management. For more information, see Providing Business Partner Data [Page 68], and Replicating Master Data from Accounts Receivable Accounting (FI-AR) [Page 69].

Procedure Navigation Menu Path in SAP Customizing Implementation Guide (in FI-AR system)

Transaction Code

Enterprise Structure → Definition → Financial Accounting → Define Credit Control Area Enterprise Structure → Assignment → Financial Accounting → Assign Company Code to Credit Control Area Financial Supply Chain Management → Credit Management → Integration with Accounts Receivable Accounting and Sales and Distribution → Integration with Accounts Receivable Accounting→ Define Credit Segment Financial Supply Chain Management → Credit Management → Integration with Accounts Receivable Accounting and Sales and Distribution → Integration with Accounts Receivable Accounting → Assign Credit Control Area and Credit Segment Financial Supply Chain Management → Credit Management → Integration with Accounts Receivable Accounting and Sales and Distribution → Integration with Accounts Receivable Accounting→ Define Reconciliation Accounts without Credit Management Update

Page 81 of 109

SAP Credit Management Configuration Guide Financial Accounting → Accounts Receivable and Accounts Payable → Business Transactions → Postings with Alternative Reconciliation Account → Other Special General Ledger Transactions → Create List for Special General Ledger

07/01/2006

OBL3

Settings for Credit Exposure Update 1. Implement and activate the Business Add-In UKM_R3_ACTIVATE. In the implementation, set the export parameters E_ACTIVE_FLAG and E_ERP2005 to X in the method SET_ACTIVE. 2. Select the credit-relevance of special general ledger indicators for which you require a credit exposure update (optional). To do this, from the special general ledger list, navigate 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 XI interface of FI-AR are determined according to the following rules: ○

Business Partner Number = Customer

○

Credit Segment = Segment assigned to the credit control area

○

Credit Exposure Category = 200

You can influence this behavior by implementing the method FILL_FIELDS of the Business Add-In 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 the credit check is not performed. Additional Settings for Updating Payment Behavior Summaries (in original Credit Management (FI-AR-CR)) ...

1. The payment behavior summary is determined from the modules delivered with the standard. If you want to determine further key figures or use other algorithms, use the implementation of the BAdI BADI_UKM_VECTOR_CALCULATE. 2. During the update of payment behavior summaries to SAP Credit Management, the fields of the outbound XI interface of FI-AR are determined according to the following rules: ○


○

Credit Segment = Segment assigned to the credit control area assigned to the company code updated to

You can influence this behavior by implementing the method FILL_VECTOR of the Business Add-In UKM_FILL.

Page 82 of 109


07/01/2006

Making Settings in FI-AR ERP 2004 Use To update liabilities and some key figures (summarized in an FI summary) from one or more FI-AR systems with release mySAP ERP 2004 to SAP Credit Management, you have to make the following settings. However, you currently integrate FI-AR and SAP Credit Management via implementations of Business Add-Ins (BAdIs) and via some IMG activities of the original Credit Management (FIAR-CR).

Prerequisites ●

In order to use the update options specified, you must also integrate your FI-AR system(s) with SAP Credit Management using XI interfaces (see configuration step Connecting Accounts Receivable Accounting ERP 2004 [Page 56]). You can execute these steps independently of one another and in any order.

●

You have configured the business partner data for SAP Credit Management (see Providing Business Partner Data [Page 68]).

Note the differences in terminology between applications with different releases – from mySAP ERP 2005, the use of some terms from SAP Credit Management has changed. For more information, see Terminology Changes from mySAP ERP 2005 [Page 14].

Procedure Navigation Menu Path in SAP Customizing Implementation Guide (In FI-AR System)

Transaction Code

Enterprise Structure → Definition → Financial Accounting → Define Credit Control Area Enterprise Structure → Assignment → Financial Accounting → Assign Company Code to Credit Control Area Financial Accounting → Accounts Receivable and Accounts Payable → Business Transactions → Postings with Alternative Reconciliation Account → Other Special General Ledger Transactions → Create List for Special General Ledger

OBL3

Settings for Liability Update 1. Implement and activate the Business Add-In UKM_R3_ACTIVATE. In the implementation, only set the export parameter E_ACTIVE_FLAG to X in the method SET_ACTIVE. 2. Select the credit-relevance of special general ledger indicators for which you require a liability update (optional). To do this, from the special general ledger list, go to the details for a special general ledger indicator and, in the properties, set the indicator Consideration for Credit Limit.

Page 83 of 109


07/01/2006

3. During the update of open items to SAP Credit Management, the fields of the outbound XI interface of FI-AR are determined according to the following rules: ○


○

Credit Segment = Credit control area, if defined and assigned to the company code, otherwise initial

○

Liability Category: Set on the recipient side, that is, in SAP Credit Management

You can influence this behavior by implementing the method FILL_FIELDS of the Business Add-In UKM_FILL. Additional Settings for Updating FI Summaries (in original Credit Management (FI-ARCR)) ...

1. In Customizing, define a credit control area, and assign all company codes from which the FI summary key figures (for example, dunning level, oldest open item) are to be updated to this credit control area.

The Credit Management (FI-AR-CR) credit control area is merely a tool to enable the update of FI summaries. 2. For technical reasons, with transaction FD32 (Credit Management), enter a master data record for each customer for which an FI summary is to be updated. You must have defined at least one credit control area. 3. During the update of FI summaries to SAP Credit Management, the fields of the outbound XI interface of FI-AR are determined according to the following rules: ○


○

Credit Segment = Credit control area assigned to the company code updated to

You can influence this behavior by implementing the method FILL_VECTOR of the Business Add-In UKM_FILL. For more information about how to calculate the key figure DSO (Days of Sales Outstanding) in FI-AR and how to transfer it to SAP Credit Management in the FI summary, see SAP Note 800848.

Page 84 of 109


07/01/2006

Making Settings in FI-AR 4.70 or 4.6C Use To update liabilities and some key figures (summarized in an FI summary) from one or more FI-AR systems with release SAP R/3 Enterprise 4.70 or SAP R/3 4.6C in SAP Credit Management, you have to make the following settings. However, you currently integrate FI-AR and SAP Credit Management via implementations of Business Add-Ins (BAdIs) and via some IMG activities of the original Credit Management (FIAR-CR). For more information, see SAP Note 694440. This Note contains up-to-date information.

Prerequisites ●

In order to use the update options specified, you must also integrate your FI-AR system with SAP Credit Management using XI interfaces (see configuration step Connecting Accounts Receivable Accounting 4.70 or 4.6C [Page 57]). You can execute these steps independently of one another and in any order.

●



Procedure Navigation Menu Path in SAP Customizing Implementation Guide (In FI-AR System)

Transaction Code

Enterprise Structure → Definition → Financial Accounting → Define Credit Control Area Enterprise Structure → Assignment → Financial Accounting → Assign Company Code to Credit Control Area Financial Accounting → Accounts Receivable and Accounts Payable → Business Transactions → Postings with Alternative Reconciliation Account → Other Special General Ledger Transactions → Create List for Special General Ledger

Page 85 of 109

OBL3


07/01/2006

Settings for Liability Update 1. See SAP Note 694440 and import the transport in the attachment to this note into your system if it does not have the support package version stated in the note. 2. In transaction SM30, make the following new entries in table TRWPR: Transaction

Event

No.

Doc.

Function Module

Document

POST

542

UKM_DOCUMENT_UPDATE

Document

PROJECT

094

UKM_DOCUMENT_PROJECT

Document

RES_CLR

016

UKM_FBRA

Document

POST

542

UKM_DOCUMENT_UPDATE

Document

PROJECT

094

UKM_DOCUMENT_PROJECT

3. Specify the RFC destination for the RFC adapter of your Exchange Infrastructure. ○

Release SAP R/3 Enterprise 4.70: in method GET_RFCDEST of BAdI UKM_ITEMS_FILL

○

Release SAP R/3 4.6C: in method GET_RFCDEST of BAdI UKM_ITEMS_FILL_46C

4. To influence the creation of the liabilities to be updated, implement the following methods:

5.

○

Release SAP R/3 Enterprise 4.70: Method FILL_FIELDS of BAdI UKM_FILL

○

Release SAP R/3 4.6C: Method FILL_FIELDS of BAdI UKM_ITEMS_FILL_46C

In transaction FIBF, make the following entries. If you already use a customer-specific module for events 1430 or 1440, the module UKM_DOCUMENT_PROCESS_00001440 must be called in this module.

Entries for Release SAP R/3 Enterprise 4.70 Process

Ctr y

Appl.

Function Module

1430

UKM_DOCUMENT_PROCESS_00001440

1440

UKM_DOCUMENT_PROCESS_00001440

Entries for Release SAP R/3 4.6C Process 1430

Ctr y

Appl.

Function Module UKM_DOCUMENT_PROCESS_00001440

6. Select the credit-relevance of special general ledger indicators for which you require a liability update (optional). To do this, from the special general ledger list, go to the details for a special general ledger indicator and, in the properties, set the indicator Consideration for Credit Limit.

Page 86 of 109


07/01/2006

7. During the update of open items to SAP Credit Management, the fields of the RFC interface of FI-AR are determined according to the following rules: ○


○

Credit Segment = Credit control area, if defined and assigned to the company code, otherwise initial

○

Liability Category: Set on the receiver side, that is, in SAP Credit Management

You can influence this behavior by implementing the method FILL_FIELDS of the Business Add-In UKM_FILL. Additional Settings for Updating FI Summaries (in original Credit Management (FI-ARCR)) ...

1. In Customizing, define a credit control area, and assign all company codes from which the FI summary key figures (for example, dunning level, oldest open item) are to be updated to this credit control area.

The Credit Management (FI-AR-CR) credit control area is merely a tool to enable the update of FI summaries. 2. For technical reasons, with transaction FD32 (Credit Management), enter a master data record for each customer for which an FI summary is to be updated. You must have defined at least one credit control area. 3. During the update of FI summaries to SAP Credit Management, the fields of the RFC interface of FI-AR are determined according to the following rules: ○


○

Credit Segment = Credit control area assigned to the company code updated to

You can influence this behavior by implementing the following methods: ○

Release SAP R/3 Enterprise 4.70: Method FILL_VECTOR of BAdI UKM_FILL

○

Release SAP R/3 4.6C: Method FILL_VECTOR of BAdI UKM_ITEMS_FILL_46C

For more information about how to calculate the key figure DSO (Days of Sales Outstanding) in FI-AR and how to transfer it to SAP Credit Management in the FI summary, see SAP Note 800848.

Page 87 of 109


07/01/2006

Making Settings in Contract Accounts Receivable and Payable (FI-CA) Use To integrate your FI-CA system with SAP Credit Management, you have to make the settings described below.

Prerequisites You have integrated your FI-CA system with SAP Credit Management using SAP NetWeaver Exchange Infrastructure (see Connecting Contract Accounts Receivable and Payable 4.72 [Page 61] and Connecting Contract Accounts Receivable and Payable 6.00 [Page 59]). You have configured the business partner data for SAP Credit Management (see Data Replication [Page 67]). If you have already created productive business partners in FI-CA and then subsequently activate SAP Credit Management, you first have to initialize the credit exposure of the business partner. To do this, run report RFKK_CR_FILL_DFKKOBL_INITIALLY (Initialization of Credit Exposure) for all relevant business partners.


Procedure Navigation Paths in the Implementation Guide for Contract Accounts Receivable and Payable (FICA) In the Implementation Guide for FI-CA, choose

Transaction

Integration → Financial Supply Chain Management → Credit Management → Activate Credit Management

FQK52

Integration → Financial Supply Chain Management → Credit Management → Maintain Credit Segments

FQK51

Integration → Financial Supply Chain Management → Credit Management → Assign Open Items to Credit Segments

FQK50

Integration → Financial Supply Chain Management → Credit Management → Define Specifications for Credit Management

FQK53

The credit segments that you enter in the activity Maintain Credit Segments have to agree with those of SAP Credit Management. Otherwise it is not possible to update the credit exposure correctly.

Page 88 of 109


07/01/2006

Settings for Scoring in SAP Credit Management In SAP Credit Management, the FI-CA creditworthiness is saved as external credit information in the rating procedure FICA. This rating procedure must be defined in Customizing for SAP Credit Management. For the creditworthiness from Contract Accounts Receivable and Payable to be included in the SAP Credit Management score, you have to define a formula for the rule for determining the score that accesses the rating procedure FICA via the function rating in the formula editor. To do this, proceed as follows: ...

1. In the Implementation Guide for Financial Supply Chain Management choose Credit Management → Credit Risk Monitoring → Master Data → Define Rating Procedure, and enter the rating procedure FICA. 2. Implement and activate the BAdI FSBP_BP1012_SUPR_CHK (control of check of rating procedure against Customizing). In the implementation, in the method SUPPRESS_CHECK, set the export parameter C_SUPPRESS to X for the rating procedure FICA. 3. In the Implementation Guide for Financial Supply Chain Management choose Credit Management → Credit Risk Monitoring → Credit Limit Check → Define Formulas, and enter formula for the rating procedure FICA. The value areas of the FI-CA creditworthiness and the score are restricted to the interval from 0 to 9999, whereby 0 is the best score. You have to ensure these value areas via an appropriate formula for calculating the score. Note also that the formula for scoring in SAP Credit Management must only contain the FI-CA creditworthiness as additive argument in the following form: Score = FI-CA creditworthiness + further items from SAP Credit Management This enables Contract Accounts Receivable and Payable to simulate the score in SAP Credit Management at any time using the current FI-CA creditworthiness, even if the score has not been replicated from SAP Credit Management. Therefore, when you change the FI-CA creditworthiness, for example, as a result of a dunning activity in Contract Accounts Receivable and Payable, you can calculate the SAP Credit Management score immediately.

Note that if you do not follow this procedure, the creditworthiness in Contract Accounts Receivable and Payable and the score in SAP Credit Management will be calculated incorrectly. Enhancements in Events for Contract Accounts Receivable and Payable In the following events you can influence the program logic in Contract Accounts Receivable and Payable: Event

Name

Note

4500

Supplement Payment Behavior Summary

For amount fields, here you have to calculate the amount in the credit segment currency, since the payment behavior summary can only be updated in one currency.

4501

Filter Open Items for Credit Exposure Determination

4502

Determination of Credit Exposure Category

4503

Only Relevant Business Partners for Credit Exposure Update (from Release 6.00)

Page 89 of 109


4504

Additional Selection for Payment Behavior Summary (from Release 6.00)

4505

Determination of Value for Credit Check (from Release 6.00)

4600

Supplement XI Interface for Payment Behavior Summary

07/01/2006

Event 4600 is processed for each business partner and credit segment. If the data is sent using the XI interface CreditPaymentBehaviour SummaryNotification, you only have to copy the data to the corresponding proxy structure. However, if you want to use your own XI interface to also transfer customer-specific fields to SAP Credit Management, you can call this interface in event 4601 (only valid for Release 4.72). From Release 6.00, the enhacement concept of SAP Exchange Infrastructure enables you to enhance the interface with no technical modifications.

4601

XI: Asynchronous Outbound Interface for Payment Behavior Summary

See the documentation of the sample function modules FKK_SAMPLE_4500, FKK_SAMPLE_4501, FKK_SAMPLE_4502, FKK_SAMPLE_4503, FKK_SAMPLE_4504, FKK_SAMPLE_4505, FKK_SAMPLE_4600, and FKK_SAMPLE_4601. Settings for Commitment Query To support the commitment query of SAP Credit Management in Contract Accounts Receivable and Payable, when you maintain the check rules in SAP Credit Management you have to define the system group for the commitment query. To do this, in the Implementation Guide for Financial Supply Chain Management choose Credit Management → Credit Risk Monitoring → Credit Limit Check → Define Check Rules. You should read the documentation for this IMG activity. Partner Messages To support the partner messages of SAP Credit Management from an external system, you have to generate a company-wide unique partner message ID in the external system. You have to report this ID when you update the credit exposure from invoicing in SAP Credit Management. To do this, use the element PendingCommitment of the interface SAP A2A Interface CreditCommitment [Page 26]. You also have to transfer the partner message ID to the document interface for posting the FI-CA document. The following document interfaces support the transfer of the partner message ID: ●

BAPIs for posting an FI-CA document

●

IDoc interface BillLineItemInterface

●

Program for transferring documents in (RFKKBIB0)

Page 90 of 109


07/01/2006

Making Settings in SD ERP 2005 Use The following settings are necessary for calling up the credit check when you create or change an SD order (from one or more SD systems) and to update commitments from SD in SAP Credit Management. SD and SAP Credit Management are integrated by means of implementations of Business Add-Ins (BAdIs) and IMG activities. The credit check and commitment update are 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 XI interfaces (see configuration step Connecting Sales and Distribution ERP 2005 [Page 63]). You can execute these steps independently of one another and in any order. You have configured the business partner data for SAP Credit Management (see Data Replication [Page 67]).

Procedure Navigation Menu Path in SAP Customizing Implementation Guide (in SD system)

Transaction Code

SAP Customizing Implementation Guide → Enterprise Structure → Definition → Financial Accounting → Define Credit Control Area Financial Supply Chain Management → Credit Management → Integration with Accounts Receivable Accounting and Sales and Distribution → Integration with Sales and Distribution → Define Credit Segment Financial Supply Chain Management → Credit Management → Integration with Accounts Receivable Accounting and Sales and Distribution → Integration with Sales and Distribution → Assign Credit Control Area and Credit Segment Financial Supply Chain Management → Credit Management → Integration with Accounts Receivable Accounting and Sales and Distribution → Integration with Sales and Distribution → Assign Sales Area to Credit Control Area Financial Supply Chain Management → Credit Management → Integration with Accounts Receivable Accounting and Sales and Distribution → Integration with Sales and Distribution → Enter Settings

Page 91 of 109


07/01/2006

Financial Supply Chain Management → Credit Management → Integration with Accounts Receivable Accounting and Sales and Distribution → Integration with Sales and Distribution → Define Active Receivable per Item Category Financial Supply Chain Management → Credit Management → Integration with Accounts Receivable Accounting and Sales and Distribution → Integration with Sales and Distribution → Define Credit Groups Financial Supply Chain Management → Credit Management → Integration with Accounts Receivable Accounting and Sales and Distribution → Integration with Sales and Distribution → Assign Sales Documents and Delivery Documents

OVAK

Financial Supply Chain Management → Credit Management → Integration with Accounts Receivable Accounting and Sales and Distribution → Integration with Sales and Distribution → Define Automatic Credit Control Financial Accounting → Accounts Receivable and Accounts Payable → Credit Management → Credit Control Account → Define Risk Categories ...

1. Implement and activate the Business Add-In UKM_R3_ACTIVATE. In the implementation, set the export parameters E_ACTIVE_FLAG and E_ERP2005 to X in the method SET_ACTIVE. 2. Implement the 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 class

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

For example coding, see the implementation UKM_BADI_IMP1 (delivered inactive).

Page 92 of 109


07/01/2006

Making Settings in SD ERP 2004 Use The following settings are required to call up the credit check when you create or change an SD order (from one or more SD systems) and to update commitments from SD in SAP Credit Management. However, SD and Credit Management are currently still integrated via implementations of Business Add-Ins (BAdIs) and via some IMG activities of the original Credit Management (FI-AR-CR).

Prerequisites ●

In order to use the update options specified, you must also integrate your SD system with SAP Credit Management using XI interfaces (see configuration step Connecting Sales and Distribution ERP 2004 [Page 63]). You can execute these steps independently of one another and in any order.

●



Procedure Navigation Menu Path in SAP Customizing Implementation Guide (In SD System)

Transaction Code

SAP Customizing Implementation Guide → Enterprise Structure → Definition → Financial Accounting → Define Credit Control Area SAP Customizing Implementation Guide → Sales and Distribution → Basic Functions → Credit Management/Risk Management → Credit Management → Assign Sales Documents and Delivery Documents

OVAK

SAP Menu → Accounting → Financial Accounting → Accounts Receivable → Credit Management → Master Data → Change

FD32

...

Page 93 of 109


07/01/2006

1. Implement the BAdI BADI_SD_CM. You can use the following methods: Method

Description

FSCM_CREDIT_CHECK_ORDER

Call credit check

FSCM_COMMITMENT_UPDATE_ORDER


FSCM_COMMITMENT_UPDATE_INVOICE


For example coding, see the implementation UKM_BADI_IMP1 (delivered inactive). In this example implementation, the fields of the outbound XI interface of SD are determined according to the following rules: ○


○

Credit Segment = Company code

2. To be able to create liabilities from SD orders, for technical reasons, the customers concerned must have master records in table KNKK, that is, in the original Credit Management (FI-AR-CR). Therefore, you must a. Define at least one credit control area b. Create one master data record per customer. The content of the fields is not important; only the existence of the master records is important.

Making Settings in SD 4.70 or 4.6C Use The following settings are required to call up the credit check when you create or change an SD order (from one or more SD systems) and to update commitments from SD in SAP Credit Management. However, SD and Credit Management are currently still integrated via implementations of Business Add-Ins (BAdIs) and via some IMG activities of the original Credit Management (FI-AR-CR).

Prerequisites ●

In order to use the update options specified, you must also integrate your SD system with SAP Credit Management using XI interfaces (see configuration step Connecting Sales and Distribution 4.70 or 4.6C [Page 65]). You can execute these steps independently of one another and in any order.

●



Page 94 of 109


07/01/2006

Procedure Navigation Menu Path in SAP Customizing Implementation Guide (In SD System)

Transaction Code

SAP Customizing Implementation Guide → Enterprise Structure → Definition → Financial Accounting → Define Credit Control Area SAP Customizing Implementation Guide → Sales and Distribution → Basic Functions → Credit Management/Risk Management → Credit Management → Assign Sales Documents and Delivery Documents

OVAK

SAP Menu → Accounting → Financial Accounting → Accounts Receivable → Credit Management → Master Data → Change

FD32

...

1. Create an enhancement project (transaction CMOD) and assign enhancement UKM_SD to this project. You can use the following function module exits: Function Module

Description

EXIT_SAPLUKM_PI_SD_001

Call credit check





There is example coding for each function module exit. In this example implementation, the fields of the outbound XI interface of SD are determined according to the following rules: ○


○

Credit Segment = Company code

2. To be able to create liabilities from SD orders, for technical reasons, the customers concerned must have master records in table KNKK, that is, in the original Credit Management (FI-AR-CR). Therefore, you must a. Define at least one credit control area b. Create one master data record per customer. The content of the fields is not important; only the existence of the master records is important.

Page 95 of 109


07/01/2006

Making Settings in CRM Use The following settings are required to call up the credit check when you create or change a CRM transaction (from one or more CRM systems) and to update credit exposures from CRM in SAP Credit Management.

CRM is connected to SAP Credit Management in a customer project solution.

Prerequisites ●

One of the following system prerequisites must be fulfilled: ○

The CRM system has Release 5.0.

○

CRM 2004 Industry Addon Edition is installed on the CRM system with Release 4.0.

●

In order to use the update options specified, you have also integrated your CRM system(s) with SAP Credit Management using XI interfaces (see configuration step Connecting Customer Relationship Management (CRM) [Page 66]). You can execute these steps independently of one another and in any order.

●



Procedure In the CRM system, make the following settings: 1. SAP Customizing Implementation Guide → Customer Relationship Management → Basic Functions → Credit Management → Maintain Credit Group Define a new credit group with check rule 02. If you use this credit group for document types that are not replicated in ERP SD, or if you have not activated credit exposure update from ERP SD, set the indicator Credit Update Active. 2. SAP Customizing Implementation Guide → Customer Relationship Management → Basic Functions → Credit Management → Assign Credit Group to Item Type Assign the new credit group to those item types for which a credit check is to be carried out. 3. SAP Implementation Guide → Customer Relationship Management → Basic Functions → Credit Management → Activate Credit Check in Transaction, Definition of Transaction Types → Assignment of Business Transaction Types → Customizing Header Activate the credit checks for those transaction types for which a credit check is to be carried out.

Page 96 of 109


07/01/2006

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: Detailed Settings 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

Field Name

Description


BDOC_TYPE

BDoc Type

CMDOC_NOTIFY

FCTXT

Context

multiple mBDOC notification (additional calls)

CNTR

Sequence

10

FNAME

Service Function

CRM_UPLOAD_FSCM_CR_SRV

ACTIV

Entry Active

X

Comment

And

Page 97 of 109

Comment


07/01/2006

Setting Up Component-Specific Master Data Purpose This section contains information about master data that has not been completely replicated. This involves, for example: ●

Master data (for example, plant data in SAP APO) that was downloaded from the Online Transaction Processing System (OLTP), but must be enhanced

●

Master data that must be newly created (for example, product catalog in SAP CRM, transportation relationships in SAP APO) Master data must be newly created if the data was not downloaded from the OLTP system during replication, or if no OLTP system was used in the business scenario.


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: ●

Which customer credit group does the business partner belong to?

●

Which analyst or analyst group is the business partner assigned to?

●

Should credit checks also be carried out for additional business partners that are related to him?

●

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.

Page 98 of 109


07/01/2006

●

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 74]).

●

If you want to import external credit information automatically, make sure that the external information providers are connected via the relevant XI interface (see Connecting External Information Providers [Page 53]).

Procedure Navigation Menu Path

Transaction Code

SAP Menu → Accounting → Financial Supply Chain Management → Credit Management → Master Data → Business Partner Master Data

UKM_BP

...

1. Call up Business Partner Maintenance in the role Business Partner Credit Management. On the tab page Credit Profile, 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 category Managed in Credit Management By; 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. 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 XI 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.

Page 99 of 109


07/01/2006

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 field Information Type 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 function NEGATIVE_CHARS 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 indicator Special Attention. 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.

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.

Page 100 of 109


07/01/2006

Workflow Settings Process To be able to use the various workflows of SAP Credit Management, you need to make the following settings: ●

Configure notifications [Page 101]

●

Configure approvals for credit limit changes [Page 102]

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 SAP Credit Management system)

Transaction Code

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 → Administration → Event Manager → Type Linkage

SWETYPV

SAP Menu → Tools → Business Workflow → Development → Definition Tools → Workflow Builder → Workflow Builder

SWDD

...

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

2. Make sure that, under Event Manager → Type Linkages, the following settings are defined for the object type CL_UKM_BUSINESS_PARTNER:

Page 101 of 109


07/01/2006

Detailed Settings Field Name


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

Note

Select indicator

3. Call up the Workflow Builder for the multistep task WS01700047 (ID UKM_BUPA). Choose Goto → Basic Data and then Goto → Agent Assignment for Task. Make sure that the task is identified as a general task.

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.

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.


Transaction Code

SAP Customizing Implementation Guide → Financial Supply Chain Management → Credit Management → Credit Risk Monitoring → Master Data → Define Rules 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 → Administration → Event Manager → Type Linkage

SWETYPV

SAP Menu → Tools → Business Workflow → Development → Definition Tools → Workflow Builder → Workflow Builder

SWDD

...

Page 102 of 109


07/01/2006

1. For each rule and 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 IMG 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. 3. Make sure that, under Event Manager → Type Linkages the following settings are defined for the object type CL_UKM_ACCOUNT: Detailed Settings Field Name


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

4. Call up the Workflow Builder for the multistep task WS01700047 (ID UKM_BUPA). Choose Goto → Basic Data and then Goto → Agent Assignment for Task. Make sure that the task is identified as a general task.

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 field Credit Limit immediately; instead, it is entered in the field Credit Limit Requested. 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.

Page 103 of 109


07/01/2006

Current Settings Purpose This section contains information about settings required during production operation. 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 production systems, 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.


Importing Exchange Rates Use In SAP Credit Management, you can monitor a credit limit in credit segment currency regardless of the currency of the commitment report to SAP Credit Management. The system can, if required, determine the credit exposure dynamically in credit segment currency by translating the commitment reports using exchange rates and translation factors.

Prerequisites ●

You have defined the exchange rates and translation factors in the SAP Credit Management system. You can do this either manually or automatically via file interface.

●

In the SAP Credit Management system, in the Customizing for the credit segments, you have defined which exchange rate type is to be used for the currency translation.

Procedure To enter the exchange rates manually, carry out the following IMG activities: Navigation Menu Path

Transaction Code

SAP Customizing Implementation Guide → Financial Supply Chain Management → Cash & Liquidity Management → Cash Management → Market Data → Manual Market Data Entry → Enter Exchange Rates

S_BCE_68000174

SAP Customizing Implementation Guide → SAP NetWeaver → General Settings → Currencies → Define Translation Factors for Currency Translation

Page 104 of 109


07/01/2006

Alternatively, to transfer the exchange rates to the system automatically via a file interface, run the following program. Navigation Menu Path

Transaction Code

SAP Menu → Accounting → Financial Supply Chain Management → Cash and Liquidity Management → Cash Management → Environment → Market Data → File Interface → Import

TBDM

For more information, see the report documentation.

Result By entering the exchange rates, you can always check the credit exposure of a customer in the currency of the credit segment, regardless of the currency in which the commitment was reported to SAP Credit Management.

The translation is not saved in the system, which means that every time you call a report with credit exposure and commitment information, the translation is run with the current exchange rates.

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 busiiness partner per credit segment. There you can navigate to the relevant commitments.

Procedure ...

1. 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.

Page 105 of 109


07/01/2006

2. To recreate the credit exposures from an SD system, use the following reports: ○

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.

In SAP Credit Management, the transaction data is recreated from the credit exposure information of SD.

For more information, see the report documentation. 3. To recreate the credit exposures from an FI-AR system from the SAP Easy Access screen, choose Financial Supply Chain Management → Credit Management → 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 credit exposure information from FI-AR is added to the transaction data.

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.


Transaction Code

SAP Customizing Implementation Guide Financial Supply Chain Management → Credit Management → Credit Risk Monitoring → Master Data → Define Formulas SAP Menu → Accounting → Financial Supply Chain Management → Credit Management → Master Data Mass Changes → Credit Limit

UKM_MASS_UPD3

SAP Menu → Accounting → Financial Supply Chain Management → Credit Management → Master Data Mass Changes → Score

UKM_MASS_UPD2

SAP Menu → Logistics → Sales and Distribution → Credit Management → Sales Documents →All

VKM4

SAP Customizing Implementation Guide → Financial Supply Chain Management → Credit Management → Credit Risk Monitoring → Processes → Define Events and Follow-On Processes ...

Page 106 of 109


07/01/2006

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 segment have to be recalculated. If necessary, adjust the formulas 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 currency 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.

Customizing of a rule for scoring and credit limit calculation changed

Carry out a mass change.

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 currently not supported; however, you can check all open SD orders again.

Derivation of one or more credit segments changed

Delete and recreate the transaction data in the credit segments concerned.

(for example, in implementations of the Business Add-In UKM_FILL)

For more information about the procedure, see Recreating Data (Troubleshooting) [Page 105].

Business partner relationship changed, added, or deleted

No correction required.

Rule for score and credit limit change in master record of business partner changed

The change to the rule for scoring and credit limit calculation of a business partner is published as an event.

Check rule in master record of business partner changed

The credit exposure of the main credit segment is always determined dynamically at runtime according to the current Customizing.

Depending on the type of change (formula of score or limit), you choose the appropriate report and then select the business partners and/or credit accounts affected via the rule.

The credit exposure contributions of other partners are always determined dynamically.

In the Customizing settings for Events and Follow-On Processes, you can define that the rule for scoring and credit limit calculation is triggered. 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 Customizing settings.

Page 107 of 109


07/01/2006

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 functional integration of saved data must be considered.

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 76].

●

Log changed 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 update of the commitment, the change document for this change contains the technical user defined in the XIChannel (for example, CREDITXIUSER).

●

Create own information To provide a business partner with information about the data saved for him in SAP Credit Management, provide 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 use it

Correct incorrect data for a business partner Your business partner has the right to have you correct incorrect data. Depending on the field, you have the following options: ○

You can change the risk class 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 incorrect formula or input parameters.

○

You can change a score calculated incorrectly manually if you configure a rule that does not contain a formula for scoring. Alternatively, you can have the system recalculate this field once you have corrected the incorrect formula or input parameters.

○

You can change negative credit events and data for collateral and credit insurances manually.

Page 108 of 109

SAP Credit Management Configuration Guide ○

●

●

07/01/2006

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 can and 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.

Ensure data can only be used in SAP Credit Management Data that arises in SAP Credit Management should only be used in SAP Credit Management.

●

○

By implementing the method READ_RESPONSE of the Business Add-In UKM_CREDIT_INFO appropriately, you can define 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 specifically 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 given his/her consent. You can document a withdrawal of consent by setting a block reason in the master data.

Page 109 of 109

FSCM Credit Management Config Guide ERP 2005

Recommend Documents