ConfguideCR2005EHP6_SP10EN.pdf

SAP Credit ManagementConfiguration Guide S AP E n h a n c e m e n t P a c k a g e 6 f o r S AP E R P 6 . 0 SAP Credit Management Configuration Guide November 2011 Copyright © Copyright 2011 SAP AG. All rights reserved. SAP Library document classification: PUBLIC 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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. 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. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, 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 other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company. Page 2 of 95 SAP Credit Management Configuration Guide November 2011 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. 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. <Example text> 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 95 SAP Credit Management Configuration Guide November 2011 Contents Configuration Guide SAP Credit Management ....................................................................... 6 SAP Credit Management (FIN-FSCM-CR) ......................................................................... 7 Documentation Landscape for SAP Applications and Business Scenarios ........................ 10 SAP Notes ....................................................................................................................... 11 Further Information .......................................................................................................... 12 System Connections ........................................................................................................ 13 Process Integration with Logistics and Finance Systems: Overview .............................. 13 Preparing Use of SAP NetWeaver Business Intelligence............................................... 14 Setting Up Portal Connection (Optional) ....................................................................... 16 System and Component Landscape ............................................................................. 16 Service Interfaces: Overview..................................................................................... 19 Connecting External Information Providers................................................................ 25 Connecting Accounts Receivable Accounting from SAP ERP 6.0 .............................. 28 Connecting Accounts Receivable SAP ERP 2004 ..................................................... 29 Connecting Accounts Receivable Accounting 4.70 or 4.6C ........................................ 30 Connecting Contract A/R & A/P from EHP4 for SAP ERP 6.0 .................................... 31 Connecting Contract Accounts Receivable and Payable as of SAP ERP 6.0 ............. 32 Connecting Contract Accounts Receivable and Payable 4.72 .................................... 35 Connecting Sales and Distribution from SAP ERP 6.0 ............................................... 37 Connecting Sales and Distribution SAP ERP 2004 .................................................... 38 Connecting Sales and Distribution 4.70 or 4.6C......................................................... 39 Connecting Customer Relationship Management (as of SAP CRM 2006s) ................ 40 Connecting Customer Relationship Management (SAP CRM 5.0 and SAP CRM 4.0 Service Industries Add-On) ....................................................................................... 41 Data Replication .............................................................................................................. 42 Data Migration .............................................................................................................. 43 Providing Business Partner Data .................................................................................. 43 Replicating Master Data of Accounts Receivable Accounting (FI-AR)............................ 44 Replicating Master Data of Contract Accounts Receivable and Payable (FI-CA) ........... 46 Replicating SAP CRM Master Data............................................................................... 47 Business Customizing...................................................................................................... 49 Settings in SAP Credit Management (FIN-FSCM-CR) ................................................... 49 Activating the Business Partner Role for Credit Management .................................... 49 Configuring Business Partner Additional Information ................................................. 51 Defining Authorizations ............................................................................................. 52 Define Events and Follow-On Processes................................................................... 54 Process Integration with SAP Systems ......................................................................... 57 Page 4 of 95 SAP Credit Management Configuration Guide November 2011 Making Settings in FI-AR from SAP ERP 6.0............................................................. 57 Making Settings in FI-AR SAP ERP 2004 .................................................................. 59 Making Settings in FI-AR 4.70 or 4.6C ...................................................................... 61 Making Settings in FI-CA as of EHP 5 for SAP ERP 6.0 ............................................ 63 Making Settings in FI-CA as of EHP 4 for SAP ERP 6.0 ............................................ 64 Settings in Contract Accounts Receivable and Payable as of SAP ERP 6.0............... 65 Making Settings in Contract Accounts Receivable and Payable (FI-CA) .................... 70 Making Settings in SD from SAP ERP 6.0 ................................................................. 73 Making Settings in SD SAP ERP 2004 ...................................................................... 75 Making Settings in SD 4.70 or 4.6C........................................................................... 76 Making Settings as of SAP CRM 2006s .................................................................... 78 Making Settings in SAP CRM 5.0 and SAP CRM 4.0 Service Industries Add-On CRM ................................................................................................................................. 80 Setting Up Component-Specific Master Data ................................................................... 81 Defining Credit Master Data in the Business Partner ..................................................... 82 Workflow Settings ............................................................................................................ 84 Configuring Notifications ............................................................................................... 85 Configuring Approvals for Credit Limit Changes ............................................................ 86 Current Settings............................................................................................................... 88 Importing Exchange Rates ........................................................................................... 88 Recreating Data (Troubleshooting) ............................................................................... 89 Credit Check if Technical Problems Occur .................................................................... 90 Converting Organizational Changes ............................................................................. 91 Ensuring Data Protection .............................................................................................. 93 Page 5 of 95 SAP Credit Management Configuration Guide November 2011 Configuration Guide SAP Credit Management Purpose This configuration guide applies to the use of SAP Credit Management with the corresponding release of the related SAP application components. Note that you can only use specific functions of the component SAP Credit Management if you have activated the following business functions: FSCM Functions 3 (FIN_FSCM_CCD_3) in the SAP Credit Management system FSCM Functions 2 (FIN_FSCM_CCD_2) in the SAP Credit Management system FSCM Functions (FIN_FSCM_CCD) in the SAP Credit Management system FSCM Integration 2 (FIN_FSCM_CCD_INTEGRATION) in the Accounts Receivable Accounting (FI-AR) system FSCM Integration (FIN_FSCM_INTEGRATION) in the Accounts Receivable Accounting (FI-AR) system For more information about the business functions, see transaction SFW5, which you can access from the first node in Customizing of the respective SAP system. Content The configuration guide describes which Customizing structures and activities you have to process to implement the business process. You can find information on the individual activities in Customizing 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]. Page 6 of 95 SAP Credit Management Configuration Guide November 2011 Feedback on Configuration Guide We would appreciate your feedback with a view to continually improving the usefulness of this configuration guide. If you find errors in the configuration guide, enter a message for the component SAP Credit Management (FIN-FSCM-CR) on SAP Service Marketplace at service.sap.com/message. SAP Credit Management (FIN-FSCM-CR) 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 in some cases 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 centralized credit management. The business systems 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 extensive SAP Financial Supply Chain Management (FIN-FSCM) 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 recommend the use of SAP Credit Management (FIN-FSCM-CR) particularly 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 various SAP and non-SAP systems. The number of financial accounting or SD systems your company uses is not relevant to this. 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. Page 7 of 95 SAP Credit Management Configuration Guide November 2011 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 then use it in SAP Credit Management (FIN-FSCM-CR). 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. Note For more information about the SAP components and release versions required, see System and Component Landscape. 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. Page 8 of 95 SAP Credit Management Configuration Guide November 2011 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, which 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: o Master data of the business partner (for example, country of origin of the business partner) o Payment behavior (for example, average days in arrears) o Dunning history (for example, number of dunning notices in the last 12 months) o 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 either manually or automatically. 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 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. Page 9 of 95 SAP Credit Management Configuration Guide November 2011 Rules for Credit Check You can define rules for determining which credit checks are carried out for an order. 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 in SAP Credit Management (FIN-FSCM-CR) is to have (for example, 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 SAPNetWeaver Business Intelligence (SAP Netweaver BI), and optionally in the Credit Manager Portal. A negative credit decision is saved, together with the data that lead to the decision, by SAP Credit Management (FIN-FSCM-CR) in the form of a documented credit decision. The blocked orders that the credit analyst has to process are available to him in worklist with documented credit decisions. 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 service.sap.com/instguides Guide Customizing SAP System Business Scenario Description, Business SAP Solution Manager Process Description 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 Platforms service.sap.com/platforms Sizing service.sap.com/sizing Security service.sap.com/security Page 10 of 95 SAP Credit Management Configuration Guide November 2011 Description of the Documents Master Guide, Installation Guide, and Upgrade Guide These documents describe how you install or upgrade the system landscape required for a business scenario. The central initial access document for every SAP application is the Master Guide. For each business scenario, it lists the SAP application components and third-party applications required, and refers to their installation and upgrade guides. These guides are Component Installation Guides, Business Scenario Upgrade Guides, and Component Upgrade Guides. Customizing This tool enables you to adapt SAP systems to meet specific customer requirements. Customizing contains the Customizing activities for all SAP components with general documentation. The structure is component-oriented, and has no reference to a business scenario. If this reference is required, it is created as follows: By the configuration documentation, with a textual link to Customizing, and by the content of SAP Solution Manager that links to the Customizing activities for each business scenario and process. Business Scenario Description This document describes how a business scenario runs once all components have been installed and configured. For each business process of a business scenario there is a business process description and a component view as graphical representation. This shows the process steps in the respective SAP component. SAP Library This documentation describes the different SAP components. SAP Notes Use Before you start configuring SAP Credit Management, read the following SAP Notes. These in turn contain 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 859999 Upgrade to SAP Credit Management 6.0 906063 Upgrade to ERP2005 - Activation of SAP Credit Management 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 11 of 95 SAP Credit Management Configuration Guide November 2011 Further Information The following list contains useful information for the configuration: Further Information Information Storage SAP Library for SAP ERP on the SAP Help Portal under SAP Credit http://help.sap.com/erp Management Application In the SAP Libary, choose SAP ERP Central Component Documentation Accounting SAP Financial Supply Chain Management (FIN-FSCM) SAP Credit Management (FIN-FSCM-CR) SAP Library for SAP NetWeaver on the SAP Help Portal under http://help.sap.com/netweaver BI Business Content of SAP Credit In the SAP Library, choose SAP NetWeaver Library SAP Management NetWeaver by Key Capability Information Integration by Key Capability BI Content Financials SAP Financial Supply Chain Management SAP Credit Management (FIN-FSCM-CR) Service interfaces of SAP Library for SAP ERP on the SAP Help Portal under SAP Credit http://help.sap.com/erp Management SAP Library for SAP NetWeaver on the SAP Help Portal under http://help.sap.com/netweaver Documentation for SAP Exchange In the SAP Library, choose SAP NetWeaver Library SAP Infrastructure NetWeaver by Key Capability Process Integration by Key Capability SAP Netweaver Exchange Infrastructure SAP Library for SAP ERP on the SAP Help Portal under http://help.sap.com/erp Documentation on In the SAP Library, choose Portal Content Cross-Application Functions in SAP ERP Roles Business Packages (Portal Content) SAP Credit Management SAP Service Marketplace under http://service.sap.com/securityguide Security Guide (in English) Note Familiarize yourself with the documentation landscape for SAP solutions, business scenarios, and business processes. For more information on the documentation available and where the latest versions are published, see Documentation Landscape of SAP Solutions and Business Scenarios. Page 12 of 95 SAP Credit Management Configuration Guide November 2011 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 Sales and Distribution (SD), Accounts Receivable Accounting (FI-AR) and Contract Accounts Receivable and Payable (FI-CA) processes. This ensures full monitoring of the credit risk from order entry through to invoice payment by the customer. You have the following integration options for SAP Credit Management: SD (R/3 4.6C, R/3 Enterprise, SAP ERP 2004, SAP ERP 6.0 and its enhancement packages) Credit limit check on creating or changing sales documents, deliveries and service orders Credit exposure report on saving a sales document Credit exposure report on saving a delivery Credit exposure report on creating a billing document Constraints The credit limit check and credit exposure update when you create or change a delivery or a service order are only available from SAP ERP 6.0. Page 13 of 95 SAP Credit Management Configuration Guide November 2011 FI-AR (R/3 4.6C, R/3 Enterprise, SAP ERP 2004, SAP ERP 6.0 and its enhancement packages) Regular credit exposure report for open customer line items Regular update of the payment behavior summary in SAP Credit Management based on payment information Note For a process description of the integration of SAP Credit Management with the SD and FI- AR components, see the documentation for SAP Credit Management in the SAP Library. Industry Release of Contract Accounts Receivable and Payable (FI-CA 4.72, SAP ERP 6.0 and its enhancement packages) Regular credit exposure report for open customer items on a totals item basis Regular update of the payment behavior summary in SAP Credit Management Import of FI-CA creditworthiness to the master data of SAP Credit Management Support of commitment query of SAP Credit Management Support of partner messages of SAP Credit Management SAP CRM (4.0 Service Industries Add-On, SAP CRM 5.0, SAP CRM 2006s, SAP CRM 2007) Customer credit limit check on creating or changing a CRM sales order (Order Management) Credit exposure update when saving a CRM sales order (Order Management) Display of master data from SAP Credit Management in SAP CRM 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. An exception exists as of SAP CRM 2006s for telecommunications and utilities. The integration of CRM service orders has not yet been implemented. Preparing Use of SAP NetWeaver Business Intelligence Use In SAP Credit Management you can use Business Content to evaluate your credit management data. The following analysis scenarios are provided: Credit Profile Credit Risk Page 14 of 95 SAP Credit Management Configuration Guide November 2011 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). 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 (FIN- FSCM-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 Warehousing Data Warehouse Management Scheduler (3.x) Schedule InfoPackage. Page 15 of 95 SAP Credit Management Configuration Guide November 2011 Setting Up Portal Connection (Optional) Use In SAP Credit Management you can use a wide range of analysis and processing functions in SAP NetWeaver Portal. For more information about Business Package for Credit Manager (SAP ERP) 1.4, see the SAP Library under Roles Business Packages (Portal Content). System and Component Landscape You can use SAP Credit Management and other integrated components in a single system landscape or a multiple system landscape. You can collect, manage, and analyze credit information from connected systems and components centrally; this architecture also enables you to distribute and use the credit information effectively in the systems and components connected. Example Examples of the cross-system/component information flow are: Credit exposure update from Accounts Receivable Accounting (FI-AR) to SAP Credit Management Credit check in SAP Credit Management on creation of a sales order in Sales and Distribution (SD) Update of the credit exposure in SAP Credit Management based on data from Sales and Distribution (SD) and Accounts Receivable Accounting (FI-AR) The data exchange is processed via XML interfaces, which means that you can connect both SAP and non-SAP systems. For a list of the interfaces used, see Service Interfaces: Overview. The exchange of messages can be made using SAP NetWeaver Process Integration (PI in the following) or – for all synchronous and for certain asynchronous service interfaces – direct using the Web Services Reliable Messaging protocol as point to point connection. This option is available not just in a one system landscape but also if you are using central SAP Credit Management in a multiple system landscape, in which there is a separate system for Contract Accounts Receivable and Payable (FI-CA) or several separate systems for Accounts Receivable Accounting (FI-AR). For additional information which service interfaces allow point to point connection using the Web Services Reliable Messaging (WS-RM) protocol, see also Service Interfaces: Overview. Page 16 of 95 SAP Credit Management Configuration Guide November 2011 Note For more information about Web Services, see: SAP NetWeaver Library under SAP NetWeaver by Key Capability Application Platform by Key Capability ABAP Technology ABAP Workbench (BC-DWB) ABAP Workbench Tools Web Services SAP NetWeaver Knowledge Center on SAP Help Portal under System Administration Technical Operations Manual SAP NetWeaver Technical Operations Manual Administration of SAP NetWeaver IT Scenarios Enabling Enterprise Services Special Administration Tasks Configure Web Service Runtime System and Component Architecture The following figure gives you an overview of the maximum connection options and data flows that the system architecture of SAP Credit Management provides. Financial Accounting (FI-AR / FI-CA) PI or WS-RM SAP NetWeaver Sales and SAP Credit Business Intelligence Distribution Management PI or WS-RM (SD/CRM) Credit Analyses (FIN-FSCM-CR) Other SAP Systems SAP NetWeaver Enterprise Non-SAP System(s) Portal Credit Manager PI Realtime Portal External Credit Information Data Flow (Non-SAP System) System Requirements and Prerequisites The following table provides an overview of all components and systems that you have to or can connect in SAP Credit Management. Note You can connect either Accounts Receivable Accounting (FI-AR) or Contract Accounts Receivable and Payable (FI-CA) as the SAP Financial Accounting components. For detailed information about the integration of Contract Accounts Receivable and Payable, see the documentation for Contract Accounts Receivable and Payable under Integration with SAP Credit Management. Page 17 of 95 SAP Credit Management Configuration Guide November 2011 Application Components and Minimum Release Minimum Component/System SAP Comments Release SAP Credit Management (FIN- Financial Mandatory FSCM-CR) Basis 6.06 SAP NetWeaver Application 7.0 Mandatory Server 7.0 (without WS-RM) SAP NetWeaver Exchange Mandatory Infrastructure 7.0 SP14 (with WS- RM) Optional Caution Accounts Receivable 4.6C; PlugIn Accounting(FI-AR) 2004.1 Note that the integration for Accounts Receivable Accounting(FI-AR) in releases that are earlier than SAP ERP 6.0 is subject to a restricted level of functions. For more information, see SAP Note 1096883. Contract Accounts Receivable and Payable (FI-CA) for the following solutions: SAP for Insurance Optional SAP Utilities As of Caution SAP Industry Telecommunications Release Note that the integration for Contract SAP Media 4.72 Accounts Receivable and Payable (FI-CA) in releases that are earlier than SAP ERP 6.0 is Collection and subject to a restricted level of functions. Disbursement (PSCD) SAP Contract Accounts Receivable and Payable (FI-CA) Page 18 of 95 SAP Credit Management Configuration Guide November 2011 Optional Caution Sales and 4.6C; PlugIn Distribution (SD) 2004.1 Note that the integration for Sales and Distribution (SD) in releases that are earlier than SAP ERP 6.0 is subject to a restricted level of functions. For more information, see SAP Note 1096882. SAP NetWeaver BI Business Business Optional Content 3.5.2 Intelligence SAP Customer 4.0; CRM Optional: for SAP for Telecommunications and SAP for Relationship Industry Utilities released from SAP CRM 2006s, for other AddOn Edition Management (CRM) projects only as a customer project 2004 SAP Enterprise 6.0 Optional Portal External Credit Non-SAP Optional Information system Financial Non-SAP Optional Accounting system Sales and Non-SAP Optional Distribution system Service Interfaces: Overview You can use the following service interfaces in SAP Credit Management: Service Interfaces in the SAP Credit Management System (FIN-FSCM-CR) Service Interface Description FICARatingReplicateQuery_In Compare FI-CA creditworthiness with score from SAP Credit Management FICARatingReplicateResponse_Out Compare FI-CA creditworthiness with score from SAP Credit Management BusinessPartnerIDByElementsQuery_Out Find ID at information provider CreditAgencyMonitorNotification_In Update external credit information CreditAgencyMonitorQuery_Out Request external credit information Page 19 of 95 SAP Credit Management Configuration Guide November 2011 Service Interfaces in the SAP Credit Management System (FIN-FSCM-CR) Service Interface Description CreditAgencyReportQuery_Out Request external credit information CreditCommitmentNotification_In Update credit exposure CreditCommitmentQuery_Out Request credit exposure CreditManagementAccountByIDQuery_In Provide credit master data CreditManagementAccountChange Notification_In Change credit account data CreditPaymentBehaviourSummary Notification_In Update payment behavior summary CreditManagementAccountERPPayment BehaviourSummaryByDebtorPartyQuery Request payment behavior summary Response_Out CreditWorthinessChangeInformation_Out Report events to connected systems CreditWorthinessCriticalPartiesQuery_In Provide critical business partners CreditWorthinessQuery_In Carry out credit check CreditAgencyReportERPDebtRecoveryScore Forward debt recovery score to ByDebtorPartyQuery_In FI-CA; CreditAgencyReportERPDebtRecoveryScore Forward debt recovery score to ByDebtorPartyResponse_Out FI-CA; CreditLimitChangeRequestERPByIDQuery Response_In Read credit limit request CreditLimitChangeRequestERPByIDQuery Read credit limit request Response_Out CreditLimitChangeRequestERPCreateRequest Create credit limit request Confirmation_In synchronously CreditLimitChangeRequestERPCreateRequest Create credit limit request Confirmation_Out synchronously CreditLimitChangeRequestERPUpdateRequest Change credit limit request Confirmation_In synchronously CreditLimitChangeRequestERPUpdateRequest Change credit limit request Confirmation_Out synchronously CreditLimitChangeRequestERPCheckQuery Response_In Change data of a credit limit request Page 20 of 95 SAP Credit Management Configuration Guide November 2011 Service Interfaces in the SAP Credit Management System (FIN-FSCM-CR) Service Interface Description CreditLimitChangeRequestERPCheckQuery Response_Out Change data of a credit limit request CreditLimitChangeRequestERPBasicData ByElementsQueryResponse_In Find credit limit requests Create credit limit request CreditLimitChangeRequestERPCreate asynchronously; Request_In not WS-RM capable Change credit limit request CreditLimitChangeRequestERPChange asynchronously; Request_In not WS-RM capable Delete credit limit request CreditLimitChangeRequestERPCancellation asynchronously; Request_In not WS-RM capable Confirm credit limit request CreditLimitChangeRequestERP asynchronously; Confirmation_Out not WS-RM capable DocumentedCreditDecisionERPBusiness Create or change documented credit Transaction DocumentNotification_In decision The service interfaces given above are located in the following namespaces: http://sap.com/xi/FSCM http://sap.com/xi/FSCM/Global http://sap.com/xi/FSCM/Global2 Service Interfaces in the Accounts Receivable (FI-AR) and Sales and Distribution (SD) System Service Interface Description CreditCommitmentNotification_Out Send credit exposure CreditManagementAccountByIDQuery_Out Request credit master data CreditPaymentBehaviourSummary Notification_Out Send payment behavior summary CreditWorthinessQuery_Out Start credit check DocumentedCreditDecisionERPBusiness Create or change documented credit TransactionDocumentNotification_Out decision Page 21 of 95 SAP Credit Management Configuration Guide November 2011 The above service interfaces are found in the namespace http://sap.com/xi/PI/FIN/Operational/Global. Service Interfaces in the Contract Accounts Receivable and Payable (FI-CA) System Service Interface Description FICARatingReplicateQuery_Out Compare FI-CA creditworthiness with score from SAP Credit Management FICARatingReplicateResponse_In Compare FI-CA creditworthiness with score from SAP Credit Management CreditCommitmentNotification_Out Send credit exposure CreditCommitmentQuery_In Provide credit exposure CreditPaymentBehaviourSummary Notification_Out Send payment behavior summary CreditWorthinessChangeInformation_In Report events to connected systems CreditWorthinessCriticalPartiesQuery_Out Request critical business partners CreditWorthinessQuery_Out Start credit check CreditAgencyReportERPDebtRecoveryScore Request debt recovery score; ByDebtorPartyQuery_Out CreditAgencyReportERPDebtRecoveryScore Provide debt recovery score; ByDebtorPartyResponse_In CreditManagementAccountERPPayment BehaviourSummaryByDebtorPartyQuery Provide payment behavior summary Response_In The service interfaces given above are located in the following namespaces: http://sap.com/xi/FICA/Global http://sap.com/xi/FICA/Global2 http://sap.com/xi/FICA Note For documentation for the individual service interfaces, see the SAP Help Portal under http://help.sap.com/erp. Call up the documentation, and select process component Credit Management. Page 22 of 95 SAP Credit Management Configuration Guide November 2011 The following figures give you an overview of the use of individual service interfaces for data exchange in SAP Credit Management. Choreography in SAP Credit Management (Part 1) Sales or Example: External External Accounts SAP Credit Accounts Telco Billing Information Receivable Management Receivable System Provider CreditCommitment RecordNotification CreditPayment BehaviourSummary Notification CreditWorthiness Query CreditCommitment Query CreditComitment Response CreditWorthiness Response CreditWorthiness ChangeInformation CreditWorthiness CriticalParties Query CreditWorthiness CriticalParties Response Page 23 of 95 SAP Credit Management Configuration Guide November 2011 Choreography in SAP Credit Management (Part 2) Sales or Example: External External Accounts SAP Credit Accounts Telco Billing Information Receivable Management Receivable System Provider CreditManagement AccountByIDQuery CreditManagement AccountByID Response CreditManagement AccountChange Notification BusinessPartnerIDBy ElementsQuery_Sync BusinessPartnerIDBy Elements Response_Sync CreditAgency ReportQuery CreditAgency ReportResponse CreditAgency MonitorQuery CreditAgency MonitorResponse CreditAgencyMonitor Notification Page 24 of 95 SAP Credit Management Configuration Guide November 2011 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 PI landscape of the information providers in question. For additional information about the corresponding service interface CreditAgenyReportQuery_Out, see the documentation of the process component Credit Management under help.sap.com SOA SAP ERP: 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 service interface of SAP Credit Management. You have a description of the information provider's interface in the format of a WSDL- XSD or DTD file. Procedure ... 1. Make an entry for the external information provider in the Implementation Guide of Credit Management under Master Data Define Rating Procedure. If you wish to use different products of an information provider (for instance, information of various scope), you should make an entry for each product. For each rating procedure, you should define the different forms of results of the query. (The information of an information provider generally contains a large number of fields and key figures.) Consequently, the ‘result’ is taken to mean the key figures that you want to use to calculate your score. 2. In the Integration Builder of your PI 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 and synchronous attributes and external message type where you reference the external definitions that you have created. Page 25 of 95 SAP Credit Management Configuration Guide November 2011 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 outbound 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. 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. 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. Page 26 of 95 SAP Credit Management Configuration Guide November 2011 4. In the Integration Builder of your PI 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 = Payload in HTTP Body Adapter Engine = Integration Server Addressing type = HTTP destination Content type = application/x-www-form-urlencoded A receiver determination. The sender is your Credit Management system where the request is issued; the interface is CreditAgencyReportQuery_Out in the namespace http://sap.com/xi/FSCM/Global. The recipient is the business service from the previous step. If you wish to connect more than one information provider, define a business service for each one and specify the conditions for selecting each receiver in the receiver determination (see also step 5). An interface determination in which you determine the receiver interface for the combination of sender, sender interface and receiver. Enter again the interface from step 3c and the interface mapping from step 3d. A receiver agreement in which you determine the communication channel HTTP for the combination of sender, receiver and receiver interface. 5. In SAP Credit Management, implement the business add-in UKM_CREDIT_INFO (see the Implementation Guide for Credit Management under Credit Risk Monitoring Enhancements BAdI: Evaluate External Credit Information). The minimum requirement is to implement method FILL_QUERY to be able to address an information provider. In this method, you enter the product identifier that the information provider needs to identify the required product (for instance, the scope of the information). You may use this identifier in the PI 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. Page 27 of 95 SAP Credit Management Configuration Guide November 2011 7. If you use the provision of external credit monitoring information by the information provider, you can use the following methods in the Business Add-In UKM_CREDIT_INFO. In the method MONITOR_FILL_QUERY, set the scope and type of the external credit monitoring information and the language in which it is to be delivered. You can also fill other fields of the request, such as the date of the change. In the method MONITOR_READ_RESPONSE, you can evaluate the result of the external credit monitoring information. ... Result In the Credit Profile screen of the business partner’s master data transaction, you can 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. Connecting Accounts Receivable Accounting from SAP ERP 6.0 To update items and payment behavior summaries from Accounts Receivable Accounting (FI-AR) with Release SAP ERP 6.0 in SAP Credit Management, connect your FI-AR system to the SAP Credit Management system via service interfaces. For additional information about the following service interfaces, see http://help.sap.com/erp in the documentation for the enterprise services of process component Credit Management: CreditCommitmentNotification_In CreditCommitmentQuery_Out CreditPaymentBehaviourSummaryNotification_In Prerequisites You have created the business systems concerned in the System Landscape Directory and are familiar with the configuration environment of the Integration Builder. For more information, see the SAP Library under 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 also Configuration. Page 28 of 95 SAP Credit Management Configuration Guide November 2011 Procedure If you use a PI server, proceed as follows: 1. Integrate the sender interface CreditCommitmentNotification_Out from the namespace http://sap.com/xi/PI/FIN/Operational/Global with the receiver interface CreditCommitmentNotification_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel. The sender is the FI-AR system and the receiver is the SAP Credit Management system. Using this connection, you can now update commitment information from Accounts Receivable Accounting to SAP Credit Management. 2. Integrate the sender interface CreditPaymentBehaviourSummaryNotification_Out from the namespace http://sap.com/xi/PI/FIN/Operational/Global with the receiver interface CreditPaymentBehaviourSummaryNotification_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel. The sender is the FI-AR system and the receiver is the SAP Credit Management system. Using this connection, you can now update payment behavior summaries from Accounts Receivable Accounting to SAP Credit Management. If you use WS-RM, proceed as follows: 1. Create an endpoint for the receiver interface. 2. Create a logical port for the sender interface with the WSDL file of the endpoint. Connecting Accounts Receivable SAP ERP 2004 Use To update items and FI summaries from Accounts Receivable Accounting (FI-AR) Release SAP ERP 2004 in SAP Credit Management, connect your FI-AR system to the SAP Credit Management system via PI interfaces. For additional information about the corresponding service interfaces CreditCommitmentNotification_In, CreditCommitmentQuery_Out and CreditPaymentRecordNotification_In , see the documentation of the process component Credit Management under help.sap.com SOA SAP ERP. Prerequisites You have created the business systems concerned in the System Landscape Directory and are familiar with the configuration environment of the Integration Builder. For more information, see the SAP Library under 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. Page 29 of 95 SAP Credit Management Configuration Guide November 2011 Procedure If you are using a PI server, proceed as follows: 1. Integrate the sender interface CreditCommitmentNotification_Out from the namespace http://sap.com/xi/PI/FIN/Operational/Global with the receiver interface CreditCommitmentNotification_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel. The sender is the FI-AR system and the receiver is the SAP Credit Management system. Using this connection, you can now update liability information from Accounts Receivable Accounting to SAP Credit Management. 2. Integrate the sender interface CreditPaymentRecordNotification_Out from the namespace http://sap.com/xi/PI/FIN/Operational/Global with the receiver interface CreditPaymentRecordNotification_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel. The sender is the FI-AR system and the receiver is the SAP Credit Management system. Using this connection, you can now update FI summaries from Accounts Receivable Accounting to SAP Credit Management. If you are using WS-RM, proceed as follows: 1. Create an end point for the receiver interface. 2. Create a logical port for the sender interface with the WSDL file of the end point. 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 via RFC adapter to the PI interfaces of the system in which SAP Credit Management runs. For additional information about the corresponding service interfaces CreditCommitmentNotification_In, CreditCommitmentQuery_Out and CreditPaymentRecordNotification_In , see the documentation of the process component Credit Management under help.sap.com SOA SAP ERP. 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. Page 30 of 95 SAP Credit Management Configuration Guide November 2011 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. 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 UKM_VECTOR_PUSH from the namespace urn:sap- com: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. 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 A/R & A/P from EHP4 for SAP ERP 6.0 Connecting Contract Accounts Receivable and Payable for EHP4 1. Carry out the activities that are described under Connecting Contract A/R & A/P (FI-CA) as of SAP ERP 6.0 [page 32]. In addition, carry out the following activities: 2. Integrate the sender interface CreditAgencyReportERPDebtRecoveryScoreByDebtorPartyQuery_Out from the namespace http://sap.com/xi/FICA/Global2 with the receiver interface CreditAgencyReportERPDebtRecoveryScoreByDebtorPartyQuery_In from the namespace http://sap.com/xi/FICA/Global2 via the receiver communication channel. The sender is the FI-CA system. The receiver is the SAP Credit Management system. Using this connection, you can request information about the debt recovery score from Contract Accounts Receivable and Payable via SAP Credit Management. Page 31 of 95 SAP Credit Management Configuration Guide November 2011 3. Integrate the sender interface CreditAgencyReportERPDebtRecoveryScoreByDebtorPartyResponse_Out from the namespace http://sap.com/xi/FSCM/Global2 with the receiver interface CreditAgencyReportERPDebtRecoveryScoreByDebtorPartyResponse_In from the namespace http://sap.com/xi/FICA/Global2 via the receiver communication channel. The sender is the SAP Credit Management system. The receiver is the FI-CA system. Using this connection, you can transfer the externally calculated debt recovery score from SAP Credit Management to Contract Accounts Receivable and Payable. Connecting Contract Accounts Receivable and Payable for EHP5 1. In addition to the activities described above under 'Connecting Contract Accounts Receivable and Payable for EHP4', carry out the following: 2. Integrate the sender interface CreditManagementAccountERPPaymentBehaviourSummaryByDebtorPartyQueryResp onse_Out from the namespace http://sap.com/xi/FSCM/Global2 with the receiver interface CreditManagementAccountERPPaymentBehaviourSummaryByDebtorPartyQueryResp onse_In from the namespace http://sap.com/xi/FICA/Global2 via the receiver communication channel. The sender is the SAP Credit Management system. The receiver is the FI-CA system. Using this connection, SAP Credit Management can request payment behavior summaries in Contract Accounts Receivable and Payable. Note that you have option of setting up a point to point connection using the Web Services Reliable Messaging (WS-RM) protocol for all synchronous and for certain asynchronous service interfaces. Connecting Contract Accounts Receivable and Payable as of SAP ERP 6.0 Use To integrate Contract Accounts Receivable and Payable (FI-CA) from release SAP ERP 6.0 with SAP Credit Management, you have to integrate your FI-CA system with the service interfaces of the system in which SAP Credit Management runs. For additional information about the following service interfaces, see the documentation of the process component Credit Management under help.sap.com SOA SAP ERP: CreditCommitmentNotification_In CreditCommitmentQuery_Out CreditWorthinessCriticalPartiesQuery_In CreditWorthinessQuery_In CreditPaymentBehaviourSummaryNotification_In FICARatingReplicateQuery_In CreditWorthinessChangeInformation_Out Page 32 of 95 SAP Credit Management Configuration Guide November 2011 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 PI content of the software components FI-CA and FSCM is installed in the Integration Repository of your PI server. You can access the PI content for Contract Accounts Receivable and Payable as a patch on SAP Service Marketplace under the respective industry solution (for example SAP IS-T 6.00). Procedure ... 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. 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. 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. 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. 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. The sender is the FI-CA system. The receiver is the SAP Credit Management system. Using this connection, you can: a. Import the FI-CA creditworthiness from Contract Accounts Receivable and Payable to SAP Credit Management. b. Query the current master data from SAP Credit Management to make the relevant master data changes in Contract Accounts Receivable and Payable (to the contract account, for example). Page 33 of 95 SAP Credit Management Configuration Guide November 2011 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. The sender is the SAP Credit Management system. The receiver is the FI-CA system. Using this connection, you can: a. Import the score from SAP Credit Management to Contract Accounts Receivable and Payable. b. Transfer the current master data from SAP Credit Management to make the relevant master data changes in Contract Accounts Receivable and Payable (to the contract account, for example). 6. Integrate the sender interface CreditWorthinessChangeInformation_Out from the namespace http://sap.com/xi/FSCM/Global with the receiver interface CreditWorthinessChangeInformation_In from the namespace http://sap.com/xi/FICA/Global via the receiver communication channel. The sender is the SAP Credit Management system. The receiver is the FI-CA system. You can use this connection to transfer information about events from SAP Credit Management to Contract Accounts Receivable and Payable (changes to master data, for example). 7. 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. The sender is the FI-CA system. The receiver is the SAP Credit Management system. Using this connection you can query business partners marked for special attention from Contract Accounts Receivable and Payable in SAP Credit Management. 8. 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. 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 Note that you have option of setting up a point to point connection using the Web Services Reliable Messaging (WS-RM) protocol for all synchronous and for certain asynchronous service interfaces. Page 34 of 95 SAP Credit Management Configuration Guide November 2011 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 service interfaces of the system in which SAP Credit Management runs. For additional information about the following service interfaces, see the documentation of the process component Credit Management under help.sap.com SOA SAP ERP: CreditCommitmentNotification_In CreditCommitmentQuery_Out CreditPaymentRecordNotification_In CreditWorthinessCriticalPartiesQuery_In CreditWorthinessQuery_In Prerequisites You have created the business systems concerned in the System Landscape Directory and are familiar with the configuration environment of the Integration Builder. For more information, see the SAP Library under 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 PI content of the software components FI-CA and FSCM is installed in the Integration Repository of your PI server. You can access the PI content for Contract Accounts Receivable and Payable as a patch on SAP Service Marketplace under the respective industry solution (for example SAP IS-T 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. 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. 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. 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). Page 35 of 95 SAP Credit Management Configuration Guide November 2011 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. 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. 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. 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. 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. 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. 8. Integrate the sender interface DebtRecoveryScore_Out from the namespace http://sap.com/xi/FICA/Global2 with the receiver interface CreditAgencyReportERPDebtRecoveryScoreByDebtorPartyQuery_In from the namespace http://sap.com/xi/FICA/Global2 via the receiver communication channel. The sender is the FI-CA system. The receiver is the SAP Credit Management system. Using this connection, you can request a Debt Recovery Score [external link]. 9. Integrate the sender interface CreditAgencyReportERPDebtRecoveryScoreByDebtorPartyResponse_Out from the namespace http://sap.com/xi/FSCM/Global2 with the receiver interface CreditAgencyReportERPDebtRecoveryScoreByDebtorPartyResponse_In from the namespace http://sap.com/xi/FICA/Global2 via the receiver communication channel. The sender is the SAP Credit Management system. The receiver is the FI-CA system. Using this connection, you can transfer the debt recovery score from SAP Credit Management to Contract Accounts Receivable and Payable. Page 36 of 95 SAP Credit Management Configuration Guide November 2011 Connecting Sales and Distribution from SAP ERP 6.0 You connect your SD system(s) as of Release SAP ERP 6.0 with SAP Credit Management using service interfaces, to enable the following: Performance of credit checks from sales orders Update of commitments from sales documents, deliveries and from billing documents not yet transferred to accounting From SAP enhancement package 4 for SAP ERP 6.0, the system can create a documented credit decision if there is a credit check with a negative outcome. For additional information about the following service interfaces, see http://help.sap.com/erp in the documentation for the enterprise services of process component Credit Management: CreditWorthinessQuery_In CreditCommitment_In und CreditCommitment_Out DocumentedCreditDecisionERPBusinessTransactionDocumentNotificat ion_In Prerequisites You have created the business systems concerned in the System Landscape Directory and are familiar with the configuration environment of the Integration Builder. For more information, see the SAP Library under 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 also Configuration. Procedure 1. Integrate the sender interface CreditWorthinessQuery_Out from the namespace http://sap.com/xi/PI/FIN/Operational/Global with the receiver interface CreditWorthinessQuery_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel. The sender is the Sales and Distribution (SD) system and the receiver is the SAP Credit Management system. Using this connection, you can now carry out credit checks of sales orders. 2. Integrate the sender interface CreditCommitmentNotification_Out from the namespace http://sap.com/xi/PI/FIN/Operational/Global with the receiver interface CreditCommitmentNotification_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel. The sender is the Sales and Distribution (SD) system and the receiver is the SAP Credit Management system. Using this connection, you can now update commitment information from the sales documents to SAP Credit Management. Page 37 of 95 SAP Credit Management Configuration Guide November 2011 3. From SAP enhancement package 4 for SAP ERP 6.0: Integrate the sender interface DocumentedCreditDecisionERPBusinessTransactionDocumentNotificat ion_Out from the namespace http://sap.com/xi/PI/FIN/Operational/Global with the receiver interface DocumentedCreditDecisionERPBusinessTransactionDocumentNotificat ion_In from the namespace http://sap.com/xi/FSCM/Global2 via the receiver communication channel. The sender is the Sales and Distribution (SD) system and the receiver is the SAP Credit Management system. Using this connection, you can now update data for the documented credit decision to SAP Credit Management. Connecting Sales and Distribution SAP ERP 2004 Use You connect your SD system(s) with Release SAP ERP 2004 with SAP Credit Management through service interfaces to enable the following: Performance of credit checks from sales orders Update of liabilities from orders or from billing documents not yet transferred to accounting For additional information about the corresponding service interfaces CreditWorthinessQuery_In, CreditCommitmentNotification_In and CreditCommitmentQuery_Out, see the documentation of the process component Credit Management under help.sap.com SOA SAP ERP. Prerequisites You have created the business systems concerned in the System Landscape Directory and are familiar with the configuration environment of the Integration Builder. For more information, see the SAP Library under 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/PI/FIN/Operational/Global with the receiver interface CreditWorthinessQuery_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel. The sender is the Sales and Distribution (SD) system and the receiver is the SAP Credit Management system. Using this connection, you can now carry out credit checks from sales orders. Page 38 of 95 SAP Credit Management Configuration Guide November 2011 2. Integrate the sender interface CreditCommitmentNotification_Out from the namespace http://sap.com/xi/PI/FIN/Operational/Global with the receiver interface CreditCommitmentNotification_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel. The sender is the Sales and Distribution (SD) system and the receiver is the SAP Credit Management system. Using this connection, you can now update liability information from SD (order values and values of blocked billing documents) to SAP Credit Management. 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 service interfaces to enable the following: Performance of credit checks from sales orders Update of liabilities from orders or from billing documents not yet transferred to accounting For additional information about the corresponding service interfaces CreditWorthinessQuery_In, CreditCommitmentNotification_In and CreditCommitmentQuery_Out, see the documentation of the process component Credit Management under help.sap.com SOA SAP ERP. 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:sap- com: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. 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. Page 39 of 95 SAP Credit Management Configuration Guide November 2011 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. 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. Connecting Customer Relationship Management (as of SAP CRM 2006s) Use You connect your CRM system(s) with SAP Credit Management through service interfaces to enable the following: Performance of credit checks from CRM transactions Update commitments from CRM transactions or billing documents Display of master data from SAP Credit Management in SAP CRM Request for external information from SAP CRM CRM is connected to SAP Credit Management in a customer project solution. An exception exists from SAP CRM 2006s for telecommunications. An exception also exists as of SAP CRM 2006s for utilities, but only for displaying master data from SAP Credit Management and requesting external information from SAP CRM. For additional information about the following service interfaces, see the documentation of the process component Credit Management under help.sap.com SOA SAP ERP: CreditWorthinessQuery_In CreditCommitmentNotification_In CreditCommitmentQuery_Out CreditManagementAccountByIDQuery_In Prerequisites You are using SAP CRM 2006s or SAP CRM 2007. You have created the business systems concerned in the System Landscape Directory and are familiar with the configuration environment of the Integration Builder. For more information, see the SAP Library under 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. Page 40 of 95 SAP Credit Management Configuration Guide November 2011 Procedure ... 1. Integrate the sender interface CreditWorthinessQuery_Out from the namespace http://sap.com/xi/CRM/Global with the receiver interface CreditWorthinessQuery_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel. The sender is SAP CRM, and the receiver is SAP Credit Management. Using this connection, you can now carry out credit checks from CRM transactions. You also need this connection for requesting external information from SAP CRM. 2. Integrate the sender interface CreditCommitmentNotification_Out from the namespace http://sap.com/xi/CRM/Global with the receiver interface CreditCommitmentNotification_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel. The sender is SAP CRM, and the receiver is SAP Credit Management. Using this connection, you can now update commitment information from CRM transactions to SAP Credit Management. 3. Integrate the sender interface CreditManagementAccountByIDQuery_Out from the namespace http://sap.com/xi/CRM/Global with the receiver interface CreditManagementAccountByIDQuery_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel. The sender is SAP CRM, and the receiver is SAP Credit Management. You can use this connection to display the master data from SAP Credit Management in SAP CRM. Connecting Customer Relationship Management (SAP CRM 5.0 and SAP CRM 4.0 Service Industries Add-On) Use You connect your CRM system(s) with SAP Credit Management through service interfaces to enable the following: Performance of credit checks from CRM transactions Update commitments from CRM transactions or billing documents CRM is connected to SAP Credit Management in a customer project solution. For additional information about the following service interfaces, see the documentation of the process component Credit Management under help.sap.com SOA SAP ERP: CreditWorthinessQuery_In CreditCommitmentNotification_In CreditCommitmentQuery_Out Page 41 of 95 SAP Credit Management Configuration Guide November 2011 Prerequisites You use CRM 5.0 or have installed CRM 2004 Industry Add-On Edition on your CRM system with Release 4.0. You have created the business systems concerned in the System Landscape Directory and are familiar with the configuration environment of the Integration Builder. 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. The sender is the CRM system and the receiver is the SAP Credit Management system. Using this connection, you can now carry out credit checks from CRM transactions. 2. Integrate the sender interface CreditCommitmentNotification_Out from the namespace http://sap.com/xi/CRMFSCM/Global (CRM Release 4.0) or http://sap.com/xi/CRM/Global (CRM-Release 5.0) with the receiver interface CreditCommitmentNotification_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel. The sender is the CRM system and the receiver is the SAP Credit Management system. Using this connection, you can now update commitment information from CRM transactions to SAP Credit Management. 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 Procedure Perform the steps in these guidelines in the sequence in which they appear. Page 42 of 95 SAP Credit Management Configuration Guide November 2011 Data Migration Use When you are using SAP Credit Management for the first time, you have to migrate data, meaning you have to transfer and supplement the master data either from a different SAP system or from a non-SAP system. Procedure 1. Transfer the general business partner data from the previous system to the SAP system in which you are running SAP Credit Management. To do this use the Data Transfer Workbench, which you can find from the SAP Easy Access screen under Tools Data Transfer Workbench. 2. Define a default procedure for the business partners for calculating the score, and also a check rule. From the SAP Easy Access screen choose Accounting Financial Supply Chain Management Credit Management Master Data Mass Changes Rule for Scoring and Credit Limit Calculation and Check Rule. 3. Assign the role SAP Credit Management (UKM000) to the transferred business partners. Use transaction UKM_MASS_UPD5 for this. 4. Recalculate the score. From the SAP Easy Access screen choose Accounting Financial Supply Chain Management Credit Management Master Data Mass Changes Score. 5. Create the credit segments with the appropriate credit limit for the business partners. From the SAP Easy Access screen choose Accounting Financial Supply Chain Management Credit Management Master Data Mass Changes Credit Limit. Result You have transferred the business partner data, and in addition to this created the credit master data that you require for SAP Credit Management. 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. Page 43 of 95 SAP Credit Management Configuration Guide November 2011 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 44]. 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 46]. For information about the master data of Customer Relationship Management, see Replicating Master Data of SAP CRM [page 47]. 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 technology 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. Page 44 of 95 SAP Credit Management Configuration Guide November 2011 Procedure If you use the master data synchronization of the SAP standard delivery, perform the following Customizing activities. To access the Customizing of Master Data Synchronization, choose Cross-Application Components Master Data Synchronization. Customizing Activities Menu Path Comments Cross-Application Components Master Data Make sure that the synchronization objects BP Synchronization Synchronization Control and CUSTOMER delivered with the standard Synchronization Control Synchronization exist. Objects Cross-Application Components General Since the Postprocessing Office (PPO) is Application Functions Postprocessing Office connected via the synchronization cockpit for Business Processes Activate Creation of the master data synchronization, activate the Postprocessing Orders the creation of postprocessign orders for the business processes of the software component AP-MD. Cross-Application Components Master Data Set the activation indicator for the PPO object Synchronization Synchronization Control BP. This means that where synchronization Synchronization Control Activate PPO attempts fail, PPO requests where the errors Requests for Platform Objects in Dialog 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 Activate the master data synchronization for Synchronization Synchronization Control source object BP in target object CUSTOMER Synchronization Control Activate and source object CUSTOMER in target object Synchronization Options BP. Cross-Application Components Master Data Define the business partner role categories and Synchronization Customer/Vendor customer account groups to be synchronized. 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 Cross-Application Components Master Data Define the number assignment for both Synchronization Customer/Vendor direction of the synchronization. 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 Page 45 of 95 SAP Credit Management Configuration Guide November 2011 If you are using a central SAP credit management system for several FI systems, you can map customers with an identical key to several business partners. To do this, you use the connection of the Unified Key Mapping Service to SAPNetWeaver Process Integration (UKMS connection to SAPNetWeaver PI). For more information, see Customizing for SAP Credit Management under Credit Risk Monitoring Business Partner. 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 service interface ABABusinessPartner. For more information about this interface, see XI Content for Business Partners [external link]. 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): Event Object Item Function Name CRMIN BUPA 2100000 BUPA_INBOUND_MAP_ROLES_CM CRMIN BUPA 2200000 BUPA_INBOUND_MAIN_ISU CRMIN BUPA 6666688 UKM_MAP_PROXY_TO_DDIC_CMS_ADD CRMOU BUPA 2100000 BUPA_OUTBOUND_BPS_MAP_ROLE_CM CRMOU BUPA 2200000 BUPA_OUTBOUND_BPS_FILL_ISU CRMIN BUPA 0230000 BUPA_XI_MAP_NUMRANGE Page 46 of 95 SAP Credit Management Configuration Guide November 2011 2. For the replication of business partner master data from SAP Credit Management to FI- CA, you can also create the SD business partner using a sample customer. To do this, implement and activate the BAdI REF_CUSTOMER_XI_GET. In the implementation, in the method GET_REF_CUSTOMER, you have to set the export parameter E_REFERENCE_CUSTOMER to the required SD sample customers. 3. Replicate the business partner data using the service interface ABABusinessPartner. Replicating SAP CRM Master Data Use The master data required for SAP Credit Management is grouped in a separate business partner role based on SAP Business Partner. The master data is distributed using CRM Middleware. Prerequisites You use the following systems: A system with FI-CA (Telecommunications industry component) and SAP Credit Management as of SAP ECC 6.0 System with SAP CRM as of 2006s CRM is connected to SAP Credit Management in a customer project solution. An exception is SAP CRM 2006s for telecommunications and utilities. Procedure When the business partner is replicated from SAP CRM, the business partner is created in the Credit Mgt Business Part. role (UKM000) as well as in the Contract Partner role (MKK). For this mapping, you have to make the following entries in table COM_BUPA_CALL_FU (Definition of Function Modules for BP Data Exchange) in SAP ECC: Note the sequence of the table entries: Entries in Table COM_BUPA_CALL FU Event Object Item Function Name R3IN BUPA 90005 COM_BUPA_MWX_MAP_UKM R3IN BUPA 100000 COM_BUPA_MWX_MAP_MAIN_CENTRAL R3OUT BUPA 150000 COM_BUPA_MWX_BPS_FILL_ISU R3OUT BUPA 200000 COM_BUPA_MWX_BPS_FILL_UKM If you want the system to calculate the score and risk class automatically when it creates the Credit Mgt Business Part. role (UKM000), you must carry out the following Customizing activities in SAP ECC. You do this in the Implementation Guide for Financial Supply Chain Management by choosing Credit Management Credit Risk Monitoring. Page 47 of 95 SAP Credit Management Configuration Guide November 2011 Settings in Customizing of Financial Supply Chain Management Activity Comments Master Data Create Rule for Scoring and Make sure that one of the rules is selected as Credit Limit Calculation the default rule for new customers. Credit Limit Check Define Check Rules Make sure that one of the check rules is selected as the default rule for new customers. Processes Define Events and Follow-On Define these entries according to the table Processes below. Define Events and Follow-On Processes Activity Event Category Follow-On Process Maintain Business Partner Score Invalid (S) Determine Score (MAIN) (EVL_RATING) Maintain Business Partner Score Changed (IC) Determine Risk Class (MAIN) (EVL_RISK_C) So that the system can create the credit segments correctly as part of a subsequent credit check, you must define the following events and follow-on processes: Activity Event Category Follow-On Process Credit Check (REQUEST) Score Invalid (S) Determine Score (EVL_RATING) Credit Check (REQUEST) Score Changed (IC) Determine Credit Limit of All Accounts of Partner (EVL_LIMITS) Credit Check (REQUEST) Score Changed (IC) Determine Risk Class (EVL_RISK_C) Credit Check (REQUEST) Credit Limit Invalid (CL) Determine Credit Limit of Account (EVL_LIMIT) Using role grouping, you can create both roles MKK and UKM000 for the business partner. To fill the mandatory field Rule for Scoring and Credit Limit Calculation automatically, in Customizing (transaction UKM_LIMIT_RULE) select one rule as default. Page 48 of 95 SAP Credit Management Configuration Guide November 2011 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 Procedure Perform the steps in these guidelines in the sequence in which they appear. Settings in SAP Credit Management (FIN-FSCM-CR) You make the basic settings for SAP Credit Management (FIN-FSCM-CR) in the system in which you have installed SAP Credit Management. For information about the Customizing of the individual IMG activities, see the Implementation Guide (IMG) under Financial Supply Chain Management Credit Management Credit Risk Monitoring. The following sections of the configuration guide provide additional information to supplement the documentation in the IMG; this additional information does not replace the documentation in the IMG. The sections explain the relationships and background of business Customizing and should help you to adjust these to benefit your organization in the best possible way. Activating the Business Partner Role for Credit Management Use The credit master data [external link] 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.). Page 49 of 95 SAP Credit Management Configuration Guide November 2011 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 : UKM110 Item: 6 Active: 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: UKM000 Title: SAP Credit Management Name: SAP Credit Management Differentiation Category: 9 Possible Business Partner Categories: Select all three categories. You need differentiation categor 9 to enter additional information for each segment. b. Insert the following business partner role if it does not already exist: BP Role: UKM000 Title: SAP Credit Management Name: SAP Credit Management BP Role Category: UKM000 Standard Assignment BP Role BP Role Category: X BP View: UKM000 Page 50 of 95 SAP Credit Management Configuration Guide November 2011 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. As a prerequisite for this, you have to implement and activate Business Add-In (BAdI) FSBP_BP3100_UPDATE. Use the example coding for this as set out in SAP Note 842975. You can change the attribute selection via the methods FILL_ADD_INFOS and SAVE_ADD_INFOS of the Business Add-In UKM_BP_ADD_FIELDS. For more information, see the Credit Management System and the Implementation Guide for Credit Management under Credit Risk Monitoring Enhancements BAdI: Additional Attributes for the Business Partner. The following procedure describes the Customizing activities required in SAP Credit Management and in SAP Business Partner for Financial Services. Procedure Navigation Menu Path in SAP Customizing Implementation Guide (In Transaction Code Credit Management System) Financial Supply Chain Management Credit Management UKM_INFOCAT Credit Risk Monitoring Credit Limit Check Define Info Categories If you use SAP Banking, then also: Otherwise: SAP Banking SAP Business Partner for Financial Services SM30 with the views V_TP19 Settings for Financial Services General Settings and V_TP22 Enhancement Options Additional Information Configure Information Type 1. In the Customizing activity Define Info Categories (UKM_INFOCAT), check whether the info types delivered for the info category Collateral are sufficient for your needs; if necessary, define further info types for this info category. 2. If you have created new info types in step 1, enter the corresponding entries in view V_TP19 with transaction SM30. In Business Partner Maintenance, you can now select collateral with additional info types. 3. In the Customizing activity Define Info Categories (UKM_INFOCAT), check whether the info types delivered for the info category Negative Credit Events are sufficient for your needs; if necessary, define further info types for this info category. Page 51 of 95 SAP Credit Management Configuration Guide November 2011 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 Customizing activity Define Info Categories (UKM_INFOCAT), check whether the info types delivered for the info category Credit Insurance are sufficient for your needs; if necessary, define further info types for this info category. 6. If you have created new info types in step 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 Customizing 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. In Business Partner Maintenance, you can now deactivate more than three check steps. 9. 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. You can now deactivate your own check steps using the check exceptions in the business partner master record. Defining Authorizations You can control the right of access to SAP Credit Management by assigning authorizations – separately by credit segment and activity - to the authorization object F_UKM_SGMT. This authorization object has the following fields: Credit segment Activity, with the following definitions: o Add or create (01) o Change (02) o Display (03) o Delete (06) o Display change documents (08) o Release (43) The role SAP_FIN_FSCM_CR_USER is delivered with all authorizations for this authorization object. Page 52 of 95 SAP Credit Management Configuration Guide November 2011 You can restrict the access to credit segment-independent master data of SAP Credit Management (for example, the score) by using the authorization object for business partner roles (B_BUPA_RLT) with the role Business Partner Credit Management (UKM000). You can restrict the access to logs (application logs) of SAP Credit Management using the authorization object S_APPL_LOG. This authorization object has the following fields: Application Log: Object Name Application Log: Subobject Activity, with the following definitions: o Display (03) o Delete (06) For SAP Credit Management, the following forms are relevant for object name and subobject: Object Name Subobject Meaning FIN-FSCM-CR BW-SCORING Transfer of score from BW FIN-FSCM-CR COMMITMENT Credit exposure update FIN-FSCM-CR CREDITCHECK Credit check FIN-FSCM-CR MONITOR Update of entries for external credit information FIN-FSCM-CR SEARCH_ID ID search at the information provider FIN-FSCM-CR REPLICATE Replicate the FI-CA creditworthiness FIN-FSCM-CR EVENTING Logs of events ERROR, ERROR_BIG, ERROR_PROG, Logs of mass changes, can be FIN-FSCM- CR-MASS ERROR_UPD, INFO, STATISTICS, differentiated by the severity of the SUCCESS, WARNING error Procedure You can organize the authorizations of your users as follows: Activities Authorization Activity Restrict access to one or more credit F_UKM_SGMT with specified credit segments segment 01 Edit master data F_UKM_SGMT 02 03 Display master data F_UKM_SGMT 03 Delete master data F_UKM_SGMT 06 Page 53 of 95 SAP Credit Management Configuration Guide November 2011 Activities Authorization Activity Display change documents for master data F_UKM_SGMT 08 changes Release and reject credit limit changes/increases requested (dual control F_UKM_SGMT 43 principle) Edit and display master data of SAP Credit B_BUPA_RLT with the BP role UKM000 Management Display and/or delete application logs of S_APPL_LOG with the object names and 03 SAP Credit Management subobjects listed above 06 S_SCMG_CAS and other authorization Display and process documented credit objects of the Case Management decisions component Define Events and Follow-On Processes Events can be linked with follow-on processes in SAP Credit Management. Events that occur in such follow-on processes can also trigger follow-on processes. Depending on the activity performed, you can define whether an event is to be considered – that is, whether the follow- on processes assigned to this event are to be triggered or not. Procedure 1. You make these settings in the SAP Credit Management system. In Customizing for SAP Credit Management,choose Credit Risk Monitoring Processes Define Events and Follow-On Processes . 2. Define the events for which the system is to trigger follow-on processes. For more information, see the documentation for this Customizing activity. The two tables below should be considered as one unit. They show which events can trigger follow-on processes. Table 1 Assignment Number Follow-On Process of Follow-On Name of Follow-On Process Key Process for Table 2 1 Determine Credit Limit of Account EVL_LIMIT Determine Credit Limit of All Accounts of EVL_LIMITS 2 Partner 3 Determine Score EVL_RATING 4 Determine External Rating(s) EVL_EXT_RT Page 54 of 95 SAP Credit Management Configuration Guide November 2011 Table 1 Assignment Number Follow-On Process of Follow-On Name of Follow-On Process Key Process for Table 2 5 Invalidate Credit Limit of Account INV_LIMIT Invalidate Credit Limit of All Accounts of 6 INV_LIMITS Partner 7 Invalidate Score INV_RATING 8 Call Business Add-In BADI 9 Set “Special Attention” Indicator SET_FLAG 10 Block Business Partner in Credit Segment SET_BLOCK 11 Perform credit check CRD_RECHCK 12 Check Request for Limit Change LIMIT_REQ 13 Start workflow WF Process Credit Exposure in Correct 14 RESEQUENCE_ITEM Sequence Create or update documented credit decision 15 DCD_CREATE for account Table 2 Follow-On Process According to Assignment Event Value Number from Table 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Score Invalid IS x x x x Score Changed IC x x x x External Rating Invalid ES x x x x External Rating Changed EC x x x x x Credit Limit Invalid CL x x x x Credit Limit Changed LC x x x x Change to Credit Limit LR x x x Requested Credit Refused CF x x x Page 55 of 95 SAP Credit Management Configuration Guide November 2011 Table 2 Follow-On Process According to Assignment Event Value Number from Table 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Payment Behavior Summary: VD x x x Dunning Data Invalid Payment Behavior Summary: VO x x x Due Date Invalid Payment Behavior Summary: VP x x x Payment Data Invalid Payment Behavior Summary: VX x x x Payment Behavior Index Invalid Generic Event Occurred GE x x x x x x x x x x x x Rule for Scoring and Credit RC x x x x x x x x x Limit Calculation Changed Risk Class Changed XC x x x x x x Limit Utilization Changed UC x x x x Limit Utilization Exceeds 100% UU x x x x x x x Limit Utilization Below 100% UD x x x Again Payment Behavior Summary VC x x x x x x x x x Changed Check Procedure Changed TC x x x Error during Credit Exposure or CE x x Commitment Update Error in Sequence CS x Block Set in Credit Management BL x x x Special Attention Indicator Set SP x x Page 56 of 95 SAP Credit Management Configuration Guide November 2011 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) Industry releases and Enhancement Packages of Contract Accounts Receivable and Payable (FI-CA) for the following solutions: SAP for Insurance SAP Utilities SAP Telecommunications SAP Media Collection and Disbursement (PSCD SAP Contract Accounts Receivable and Payable (FI-CA) Sales and Distribution (SD) SAP Customer Relationship Management (CRM) You can find information on the Customizing activities in your SAP system. The following sections of the configuration guide provide additional information to supplement the Customizing documentation; this additional information does not replace the Customizing documentation. The sections explain the relationships and background of business Customizing and should help you to adjust these to benefit your organization in the best possible way. Making Settings in FI-AR from SAP ERP 6.0 To update credit exposures and payment behavior summaries from one or more FI-AR systems from Release SAP ERP 6.0 in SAP Credit Management, you have to make the following settings. You integrate FI-AR and FI-AR and SAP Credit Management by implementing Business Add-Ins (BAdIs), and also Customizing activities. Prerequisites In order to use the update options specified, you must also integrate your FI-AR system with SAP Credit Management using service interfaces (see configuration step Connecting Accounts Receivable Accounting from SAP ERP 6.0). You can execute these steps independently of each another and in any order. You have configured the business partner data for SAP Credit Management. For more information, see Providing Business Partner Data and Replicating Master Data from Accounts Receivable Accounting (FI-AR). Page 57 of 95 SAP Credit Management Configuration Guide November 2011 Procedure Navigation Transaction Menu Path in SAP Customizing Implementation Guide (in FI-AR system) 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 Financial Accounting Accounts Receivable and Accounts Payable Business Transactions Postings with Alternative Reconciliation Account OBL3 Other Special General Ledger Transactions Create List for Special General Ledger 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 method SET_ACTIVE. 2. The credit exposure update is made bundled using report UKM_TRANSFER_ITEMS. You can implement a direct update from FI-AR to SAP Credit Management by implementing method FI_AR_UPDATE_MODE of BAdI UKM_R3_ACTIVATE. 3. Select the credit-relevance of special general ledger indicators for which you require a credit exposure update (optional). To do this, navigate from the special general ledger list to the details for a special general ledger indicator, and in the properties set the indicator Consideration for Credit Limit. 4. During the update of open items to SAP Credit Management, the fields of the outbound interface of FI-AR are determined according to the following rules: o Business Partner Number = Customer o Credit Segment = Segment assigned to the credit control area o Credit Exposure Category = 200 You can influence this behavior by implementing the method FILL_FIELDS of Business Add-In UKM_FILL. Page 58 of 95 SAP Credit Management Configuration Guide November 2011 5. For postings in FI-AR, you can perform a credit check after you have entered the amount. If you want to perform this credit check, change the message type of message UKM_PI 139. In the standard system the credit check is not made. Additional Settings for Updating Payment Behavior Summaries (in original FI-AR-CR) 1. The payment behavior summary is determined from the modules delivered with the standard system. If you want to determine further key figures or use other algorithms, use the implementation of BAdI BADI_UKM_VECTOR_CALCULATE. 2. During the update of payment behavior summaries to SAP Credit Management, the fields of the outbound interface of FI-AR are determined according to the following rules: o Business Partner Number = Customer o Credit Segment = Segment assigned to the credit control area that is assigned to the company code updated to You can influence this behavior by implementing the method FILL_VECTOR of Business Add-In UKM_FILL. Making Settings in FI-AR SAP 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 Customizing activities of the original Credit Management (FI-AR-CR). Prerequisites In order to use the update options specified, you must also integrate your FI-AR system(s) with SAP Credit Management using service interfaces (see configuration step Connecting Accounts Receivable Accounting SAP ERP 2004 [page 29]). 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 43]). Page 59 of 95 SAP Credit Management Configuration Guide November 2011 Procedure Navigation Menu Path in SAP Customizing Implementation Transaction Code Guide (In FI-AR System) 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 OBL3 Accounts Payable Business Transactions Postings with Alternative Reconciliation Account Other Special General Ledger Transactions Create List for Special General Ledger Settings for Credit Exposure 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 credit exposure 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. 3. During the update of open items to SAP Credit Management, the fields of the outbound interface of FI-AR are determined according to the following rules: Business partner number = Customer Credit segment = 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-AR-CR)) ... 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. Page 60 of 95 SAP Credit Management Configuration Guide November 2011 3. During the update of FI summaries to SAP Credit Management, the fields of the outbound interface of FI-AR are determined according to the following rules: Business partner number = Customer Credit segment = 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 Sales Outstanding) in FI-AR and how to transfer it to SAP Credit Management in the FI summary, see SAP Note 800848. 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 Customizing activities of the original Credit Management (FI-AR-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 service interfaces (see configuration step Connecting Accounts Receivable Accounting 4.70 or 4.6C [page 30]). 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 43]). Procedure Navigation Menu Path in SAP Customizing Implementation Transaction Code Guide (In FI-AR System) 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 OBL3 Accounts Payable Business Transactions Postings with Alternative Reconciliation Account Other Special General Ledger Transactions Create List for Special General Ledger Page 61 of 95 SAP Credit Management Configuration Guide November 2011 Settings for Credit Exposure Update 1. See SAP Notes 694440 and 1228622 and import the transport in the attachment to Note 694440 into your system if it does not have the support package version stated in the note. 2. 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 3. To influence the creation of the liability to be updated, implement the following methods: 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 4. Choose transaction FIBF (table TBE11). Under Settings Identification SAP Applications enter application UKM and set the indicator to active. 5. Using transaction FIBF make the following entry for process 5010 (table TPS31). If an entry already exists, you have to call UKM_EVENT_5010 in this module. Entries for Release SAP R/3 Enterprise 4.6C and 4.70 Process Ctry Appl. Function Module 5010 UKM UKM_EVENT_5010 6. 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, go to the details for a special general ledger indicator and, in the properties, set the indicator Consideration for Credit Limit. 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: Business partner number = Customer 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-AR-CR)) ... 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. Page 62 of 95 SAP Credit Management Configuration Guide November 2011 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: Business Partner Number = Customer 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 Sales Outstanding) in FI-AR and how to transfer it to SAP Credit Management in the FI summary, see SAP Note 800848. Making Settings in FI-CA as of EHP 5 for SAP ERP 6.0 Use To integrate your FI-CA system with SAP Credit Management, you have to make the settings described below. Procedure Perform the activities described in the following texts: Making Settings in Contract Accounts Receivable and Payable as of SAP ERP 6.0 [page 65] Making Settings in FI-CA as of EHP 4 for SAP ERP 6.0 [page 64] Then perform the following activities described below in addition: Settings for Transfer of Key Figures from Contract Accounts Receivable and Payable To be able to transfer key figures for payment behavior from Contract Accounts Receivable and Payable to SAP Credit Management, proceed as follows: 1. Define the key figures for transfer to SAP Credit Management. SAP provides a standard range of key figures. If you want to add to these and determine further key figures, make the necessary settings in Customizing for Contract Accounts Receivable and Payable under Integration Financial Supply Chain Management Credit Management Key Figures Define Key Figures for Transfer to Credit Management. 2. Enter the key figures that you want to transfer to Credit Management in Customizing for Contract Accounts Receivable and Payable under Integration Financial Supply Chain Management Credit Management Key Figures Make Specifications for Key Figures for Credit Management. In this activity, you specify which of the key figures you defined in the previous activity you now want to be transferred to SAP Credit Management. If you want the system to transfer a key figure, set the Active indicator for it. The system does the following only if the indicator is active: it writes triggers for the transfer for the business partner as soon as the partner demonstrates negative payment behavior. Page 63 of 95 SAP Credit Management Configuration Guide November 2011 3. Define the evaluation period for key figures in Customizing for Contract Accounts Receivable and Payable under Integration Financial Supply Chain Management Credit Management Key Figures Specify Evaluation Period for Key Figures. Here you specify the time period for which the system should evaluate a key figure. This value applies for the following standard key figures: COL (collections) DUN (dunning notices) P2P (promises to pay) RET (returns) TIP (installment plans) WRO (write-offs) If you do not make any entries, the system uses the default value of 30 days. Making Settings in FI-CA as of EHP 4 for SAP ERP 6.0 Use To integrate your FI-CA system with SAP Credit Management, you have to make the settings described below. Procedure Perform the activities described in Making Settings in Contract Accounts Receivable and Payable as of SAP ERP 6.0 [page 65]. Then perform the following activities described below in addition: Settings for Request for Debt Recovery Score To request the debt recovery score of a defaulting payer, proceed as follows: 1. Configure Contract Accounts Receivable and Payable for the debt recovery score. To do so, activate the Debt Recovery Score function in Customizing for Contract Accounts Receivable and Payable under Business Transactions Submit to Collection Agency Define Specifications for Debt Recovery Score. 2. The SAP Credit Management system requires a configured interface to an external credit information provider. You enter the key for the rating procedure to be used for the debt recovery score in the Business Add-In (BAdI) UKM_SE_DRS_QUERY_ASYN in the method CONVERT_IBOUND. If you want to use the SAP standard name for the debt recovery score and you create rating procedure DRS (debt recovery score), then you do not need an implementation of this BAdI. Page 64 of 95 SAP Credit Management Configuration Guide November 2011 3. Assign allowed values to the key for the debt recovery score rating procedure in Customizing. In Customizing for Financial Supply Chain Management, choose Credit Management Credit Risk Monitoring Master Data Define Rating Procedure. In the BAdI FSBP_BP1012_SUPR_CHK, if you define the method IF_EX_FSBP_BP1012_SUPR_CHK~SUPPRESS_CHECK as follows, then all values are allowed: * create implementation for Badi FSBP_BP1012_SUPR_CHK method IF_EX_FSBP_BP1012_SUPR_CHK~SUPPRESS_CHECK. if I_rating_method = 'FICA' or i_rating_method = 'DRS'. c_suppress = 'X'. endif. endmethod. 4. Assign the rating procedure for the debt recovery score to a rule for scoring and credit limit calculation. In Customizing for Financial Supply Chain Management, choose Credit Management Credit Risk Monitoring Master Data Create Rule for Scoring and Credit Limit Calculation. Define how the system should derive the external ID of the business partner (ID type). Define the validity period of the rating. 5. In Customizing for the follow-on processes in SAP Credit Management add to the activity DRSREQ Determine Debt Recovery Score and for the event External Score Invalid the new follow-on process EVL_EXT_RT Determine External Score(s). In Customizing for Financial Supply Chain Management, choose Credit Management Credit Risk Monitoring Processes Define Events and Follow-On Processes. Settings in Contract Accounts Receivable and Payable as of SAP ERP 6.0 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 as of SAP ERP 6.0 [page 32]). You have configured the business partner data for SAP Credit Management (see Data Replication [page 42]). If you have already created productive business partners in FI-CA and 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. Page 65 of 95 SAP Credit Management Configuration Guide November 2011 Procedure Navigation In Customizing for Contract Accounts Receivable and Payable, choose Integration Financial Supply Chain Management Credit Management: Activate Credit Management Maintain Credit Segments The credit segments you enter in this activity must correspond to those in SAP Credit Management. Otherwise it is not possible to update the credit exposure correctly. Assign Open Items to Credit Segments Define Specifications for Credit Management Define Origin of Requests for Master Data Changes Define Change Types 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 Customizing for Financial Supply Chain Management choose Credit Management Credit Risk Monitoring Credit Limit Check Define Formulas, and enter a 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 Page 66 of 95 SAP Credit Management Configuration Guide November 2011 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 are 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 4504 Additional Selection for Payment Behavior Summary 4505 Determination of Value for Credit Check 4506 Credit Management: Change to Contract Account Data 4507 Credit Management: Update of Business Objects 4508 Credit Management: Update Trigger Table for BP Change Page 67 of 95 SAP Credit Management Configuration Guide November 2011 4600 Supplement service Interface for Payment The data is sent using the service interface Behavior Summary CreditPaymentBehaviourSummaryNotificatio n. To enhance the service interface, you use the data type enhancement concept in PI. 4602 PI: Supplement The data is sent using the service interface FICARatingReplicateResponse_In FICARatingReplicateResponse. To enhance the service interface, you use the data type enhancement concept in PI. 4603 PI: Accept CreditChangeInformation See section "Reaction to Master Data Changes in SAP Credit Management" 4609 PI: Change to Notification for Credit The data is sent using the service interface Exposure Update CreditCommitmentNotification. To enhance the service interface, you use the data type enhancement concept in PI. See the documentation for the sample function modules FKK_SAMPLE_4500, FKK_SAMPLE_4501, FKK_SAMPLE_4502, FKK_SAMPLE_4503, FKK_SAMPLE_4504, FKK_SAMPLE_4505, FKK_SAMPLE_4506, FKK_SAMPLE_4507, FKK_SAMPLE_4508, FKK_SAMPLE_4600, FKK_SAMPLE_4602, FKK_SAMPLE_4603, and FKK_SAMPLE_4609. 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 Customizing for Financial Supply Chain Management choose Credit Management Credit Risk Monitoring Credit Limit Check Define Check Rules. You should read the documentation for this Customizing 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 element PendingCommitment of interface CreditCommitmentNotification_In. 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 Contract Accounts Receivable and Payable (RFKKBIB0) Page 68 of 95 SAP Credit Management Configuration Guide November 2011 Reaction to Master Data Changes in SAP Credit Management You must first decide which changes to master data in SAP Credit Management should affect the master data in Contract Accounts Receivable and Payable. Proceed as follows: ... 1. In the Implementation Guide for Financial Supply Chain Management, choose Credit Management Credit Risk Monitoring Processes Events and Follow-On Processes. 2. Set the XI indicator for the relevant event. The data is sent using the service interface CreditWorthinessChangeInformation. In the standard system, triggers are updated for changes to the following master data: Score Risk class Blocked in Credit Management indicator Block reason Special Attention indicator If you want to write additional triggers for your own change types (such as a change to the credit limit in SAP Credit Management), proceed as follows: ... 1. If the change to the field you requested in SAP Credit Management does not exist as an event (changing the Bankruptcy Proceedings indicator, for example), you must make a corresponding enhancement in SAP Credit Management. See the section Define Events and Follow-On Processes. 2. If the field you requested does not exist in the service interface CreditWorthinessChangeInformation, you must enhance the interface. To do this, use the data type enhancement concept in the PI. 3. Supply the export structure for the trigger table in event 4603. 4. Enter the new change type in the Implementation Guide for Contract Accounts Receivable and Payable under Integration Financial Supply Chain Management Credit Management Define Change Types. You can use the mass activity Prepare Master Data Changes from External System to subsequently process these triggers. The current master data from SAP Credit Management is replicated in Contract Accounts Receivable and Payable so that it can then be used to determine master data changes in Contract Accounts Receivable and Payable. The data has to be replicated since the mass activity for changing master data in Contract Accounts Receivable and Payable cannot perform a synchronous replication for performance reasons. From a technical perspective, the same messages are used as for replicating the creditworthiness: Sending messages to SAP Credit Management, in which a master data replication is requested (service interface FICARatingReplicateQuery_Out) Sending messages with master data information from SAP Credit Management (service interface FICARatingReplicateResponse_Out) The master data from SAP Credit Management is then replicated in Contract Accounts Receivable and Payable, that is, the master data from SAP Credit Management is saved to table DFKKCMS (Credit Management: Master Data Replication). Page 69 of 95 SAP Credit Management Configuration Guide November 2011 The following master data is replicated in the standard: Score Risk class If you require additional master data from SAP Credit Management to determine master data changes in Contract Accounts Receivable and Payable (such as the credit group), proceed as follows: ... 1. Supplement the master data at event 4602. 2. Create the master data as fields in the customer include in table DFKKCMS (Credit Management: Master Data Replication). For performance reasons, SAP recommends that you do not replicate data from the credit segments. Once the master data has been successfully replicated, the triggers Score and Risk Class are allocated the status Data Received. If you want this update to take place for all other triggers, you must define the event 4508: Blocked in Credit Management indicator Block reason Special Attention indicator Other triggers for your own change types (such as changing the Bankruptcy Proceedings indicator in SAP Credit Management) You can then use the Process Master Data Changes from External Systems transaction to change the business partner master data (contract account, for example) in Contract Accounts Receivable and Payable based on the replicated master data. If you want to make changes to contract accounts, define event 4506 accordingly. Use event 4507 for all changes to other objects (such as the contract). 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 34] and Connecting Contract Accounts Receivable and Payable from SAP ERP 6.00 [page 32]). You have configured the business partner data for SAP Credit Management (see Data Replication [page 42]). Page 70 of 95 SAP Credit Management Configuration Guide November 2011 If you have already created productive business partners in FI-CA and 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 Customizing for Contract Accounts Receivable and Payable (FI-CA) In Customizing for FI-CA, choose Transaction Integration Financial Supply Chain FQK52 Management Credit Management Activate Credit Management Integration Financial Supply Chain FQK51 Management Credit Management Maintain Credit Segments Integration Financial Supply Chain FQK50 Management Credit Management Assign Open Items to Credit Segments Integration Financial Supply Chain FQK53 Management Credit Management Define Specifications for Credit Management The credit segments you enter in the activity Maintain Credit Segments must correspond to those in SAP Credit Management. Otherwise it is not possible to update the credit exposure correctly. 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 Customizing for Financial Supply Chain Management choose Credit Management Credit Risk Monitoring Credit Limit Check Define Formulas, and enter a formula for the rating procedure FICA. Page 71 of 95 SAP Credit Management Configuration Guide November 2011 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 are 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 For amount fields, here you have to calculate the Behavior Summary 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) 4504 Additional Selection for Payment Behavior Summary (from Release 6.00) 4505 Determination of Value for Credit Check (from Release 6.00) 4600 Supplement service Interface Event 4600 is processed for each business partner for Payment Behavior and credit segment. If the data is sent using the Summary service interface CreditPaymentBehaviourSummaryNotifica tion, you only have to copy the data to the corresponding proxy structure. However, if you want to use your own service 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 SAP ERP 6.00, the enhancement concept of SAP Exchange Infrastructure enables you to enhance the interface with no technical modifications. Page 72 of 95 SAP Credit Management Configuration Guide November 2011 4601 PI: 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 Customizing for Financial Supply Chain Management choose Credit Management Credit Risk Monitoring Credit Limit Check Define Check Rules. You should read the documentation for this Customizing 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 element PendingCommitment of interface CreditCommitmentNotification_In. 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 Contract Accounts Receivable and Payable (RFKKBIB0) Making Settings in SD from SAP ERP 6.0 The following settings are necessary for calling up the credit check when you create or change sales documents and deliveries (from one or more SD systems) and to update commitments from SD in SAP Credit Management. SD and SAP Credit Management are integrated by implementing various Business Add-Ins (BAdIs), and also Customizing activities. From SAP enhancement package 4 for SAP ERP 6.0, you can create documented credit decisions for sales documents with a credit block. Note The credit check and commitment update are not supported for service orders. Page 73 of 95 SAP Credit Management Configuration Guide November 2011 Prerequisites In order to use the update options specified, you must also integrate your SD system with SAP Credit Management using service interfaces (see configuration step Connecting Sales and Distribution from SAP ERP 6.0). You can execute these steps independently of each another and in any order. You have configured the business par tner data for SAP Credit Management (see Data Replication). Procedure Navigation Transaction Menu Path in Customizing of SD System 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 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 OVAK with Sales and Distribution Assign Sales Documents and Delivery Documents 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 Page 74 of 95 SAP Credit Management Configuration Guide November 2011 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 method SET_ACTIVE. If you want to use documented credit decisions, implement method DCD_ACTIVE of this BAdI. 2. Implement BAdI BADI_SD_CM. You can use the following methods: Method Description FSCM_GET_MASTER_DATA Determine master data of partner before credit check, in particular the risk category FSCM_CREDIT_CHECK_ORDER Call credit check from order FSCM_CREDIT_CHECK_DELVRY Call credit check from delivery FSCM_COMMITMENT_UPDATE_ORDER Update new or changed order values FSCM_COMMITMENT_UPDATE_DELVRY Update new or changed delivery values FSCM_COMMITMENT_UPDATE_INVOICE Reduce order values during billing and create open billing values if no immediate transfer to FI FSCM_DISPLAY_CREDIT_MESSAGES Control output of messages for credit check in dialog FSCM_CREDIT_CHECK_SM_ORDER Call credit check from service order 3. For sample code, see the implementation UKM_SD_FSCM_INTEGR1 (delivered inactive), that is available also with SAP Note 1130061. Making Settings in SD SAP 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. SD and SAP Credit Management are integrated via implementations of Business Add-Ins (BAdIs) and via some Customizing 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 service interfaces (see configuration step Connecting Sales and Distribution SAP ERP 2004 [page 38]). 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 43]). Page 75 of 95 SAP Credit Management Configuration Guide November 2011 Procedure Navigation Menu Path in SAP Customizing Implementation Transaction Code Guide (In SD System) SAP Customizing Implementation Guide Enterprise Structure Definition Financial Accounting Define Credit Control Area SAP Customizing Implementation Guide Sales and OVAK Distribution Basic Functions Credit Management/Risk Management Credit Management Assign Sales Documents and Delivery Documents SAP Menu Accounting Financial Accounting FD32 Accounts Receivable Credit Management Master Data Change ... 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 Update new or changed order values FSCM_COMMITMENT_UPDATE_INVOICE Reduce order values during billing and create open billing values if no immediate transfer to FI 2. To be able to create credit exposure from open 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 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 with a function module exit and some of the Customizing activities of the original Credit Management (FI-AR- CR). Page 76 of 95 SAP Credit Management Configuration Guide November 2011 Prerequisites In order to use the update options specified, you must also integrate your SD system with SAP Credit Management using service interfaces (see configuration step Connecting Sales and Distribution 4.70 or 4.6C [page 39]). 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 43]). Procedure Navigation Menu Path in SAP Customizing Implementation Transaction Code Guide (In SD System) SAP Customizing Implementation Guide Enterprise Structure Definition Financial Accounting Define Credit Control Area SAP Customizing Implementation Guide Sales and OVAK Distribution Basic Functions Credit Management/Risk Management Credit Management Assign Sales Documents and Delivery Documents SAP Menu Accounting Financial Accounting FD32 Accounts Receivable Credit Management Master Data Change ... 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 EXIT_SAPLUKM_PI_SD_002 Update new or changed order values EXIT_SAPLUKM_PI_SD_003 Reduce order values during billing and create open billing values if no immediate transfer to FI 2. To be able to create credit exposure from open 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 77 of 95 SAP Credit Management Configuration Guide November 2011 Making Settings as of SAP CRM 2006s Use You require settings for the following transactions: The credit check when you create or change a CRM transaction (call up in one or more CRM systems) Update the CRM credit exposure in SAP Credit Management Display of master data of SAP Credit Management in SAP CRM Requesting external credit information through SAP CRM for SAP Credit Management. CRM is connected to SAP Credit Management in a customer project solution. An exception exists as of SAP CRM 2006s for telecommunications. An exception also exists from SAP CRM 2006s for utilities, but only for displaying master data from SAP Credit Management and requesting external information through SAP CRM. Prerequisites In order to use the functions specified, you have integrated your CRM system(s) with SAP Credit Management using service interfaces (see Connecting Customer Relationship Management (as of SAP CRM 2006s) [page 40]). You have configured the business partner data in SAP Credit Management (see Providing Business Partner Data [page 43]). Procedure Display of Master Data of SAP Credit Management in SAP CRM (available for Utilities and Telecommunications In the CRM system, make the required settings: You can find these in Customizing of Customer Relationship Management under Basic Functions Credit Management Business Partner Rating Display Credit Master Data from Credit Management System: ... 1. General Settings 2. Define Texts for Risk Classes and Make Categorization 3. Define Symbols for Categories of Risk Class 4. Define Texts for Displaying Credit Segment 5. Define Texts for Displaying Lock Reason For more information, see the documentation for these Customizing activities. Page 78 of 95 SAP Credit Management Configuration Guide November 2011 Credit Check and Credit Exposure Update (available only for Telecommunications) In the CRM system, make the required settings: Choose the following activities in Customizing of Customer Relationship Management: ... 1. Basic Functions Credit Management Credit Check and Credit Exposure Update Edit Credit Group Define a new credit group with check rule 02. If you use this credit group for document types for which a credit exposure update is to take place, set the Credit Update Active indicator. 2. Basic Functions Credit Management Credit Check and Credit Exposure Update Assign Credit Group to Item Type Assign the new credit group to the item types for which a credit check is to be carried out. 3. Basic Functions Credit Management Credit Check and Credit Exposure Update Activate Credit Check in Transaction, Definition of Transaction Types Assignment of Business Transaction Types Customizing Header Activate the credit check for the transaction types for which a credit check is to be carried out. 4. To activate the update of commitments to SAP Credit Management, using transaction SM30 make two new entries in table SMW3FDCUST. Make the settings according to the following table: Field Name Description User Action and Values BDOC_TYPE BDoc Type CMDOC_NOTIFY FCTXT Context mBDOC notification (additional calls) CNTR Sequence 10 FNAME Service Function CRM_UPLOAD_FSCM_CR_SRV ACTIV Entry Active X Also make the following settings: Field Name Description User Action and Values BDOC_TYPE BDoc Type CMDOC_NOTIFY FCTXT Context Multiple mBDOC notification (additional calls) CNTR Sequence 10 FNAME Service Function CRM_UPLOAD_FSCM_CR_SRV ACTIV Entry Active X Requesting External Credit Information through SAP CRM for SAP Credit Management In the CRM system and ERP system, make the required settings: For additional information, see the documentation in the CRM system for the following Customizing activity: Customer Relationship Management Basic Functions Credit Management Business Partner Rating Display Credit Master Data from Credit Management System Define Profiles for Update of Credit Data. Page 79 of 95 SAP Credit Management Configuration Guide November 2011 Making Settings in SAP CRM 5.0 and SAP CRM 4.0 Service Industries Add-On 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 Add-On 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 service interfaces (see configuration step Connecting Customer Relationship Management (SAP CRM 5.0 and SAP CRM 4.0 Service Industries Add-On) [page 41]). 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 43]). 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 the item types for which a credit check is to be carried out. 3. SAP Customizing 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 check for the transaction types for which a credit check is to be carried out. Page 80 of 95 SAP Credit Management Configuration Guide November 2011 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 Note 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 And Field Name Description User Action and Values Note 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 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. Procedure Perform the steps in these guidelines in the sequence in which they appear. Page 81 of 95 SAP Credit Management Configuration Guide November 2011 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. 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 51]). If you want to import external credit information automatically, make sure that the external information providers are connected via the relevant service interface (see Connecting External Information Providers [page 24]). Page 82 of 95 SAP Credit Management Configuration Guide November 2011 Procedure Navigation Menu Path Transaction Code SAP Menu Accounting Financial Supply UKM_BP Chain Management Credit Management Master Data Business Partner Master Data ... 1. Call up Business Partner Maintenance in the role Business Partner Credit Management. On the Credit Profile tab, 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 service interface. You can use the external credit information as input parameter for scoring. See also: Search for ID of Business Partner at Information Provider [external link] and External Credit Monitoring Information [external link] 6. If required, under the additional information in the general data (valid for all credit segments there) or in the data for a credit segment, enter collateral and/or credit insurance with amount and currency, and set the relevance indicator and a validity interval. In a credit check with the check steps Statistical Check of Credit Limit Utilization or Dynamic Limit Check with Credit Horizon, before the comparison with the credit limit, the credit exposure is reduced by the amount of the collateral and/or credit insurance if the indicator Consider Collateral or the indicator Consider Credit Insurance is set in Customizing, and the current date is in the validity period of the collateral or credit insurance and the relevance indicator is set. 7. If required, under the additional information in the general data (valid for all credit segments there) or in the data for a credit segment, enter check exceptions with a validity interval. The 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. Page 83 of 95 SAP Credit Management Configuration Guide November 2011 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. 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 84] Configure approvals for credit limit changes [page 86] Page 84 of 95 SAP Credit Management Configuration Guide November 2011 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 Transaction Code (In SAP Credit Management system) 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 SWETYPV Development Administration Event Manager Type Linkage SAP Menu Tools Business Workflow SWDD Development Definition Tools Workflow Builder Workflow Builder ... 1. In the IMG activity Define Events and Follow-On Processes, define which event types are to be dealt with in which activities; enter the follow-on process Start Workflow for the required event types. SAP Credit Management supports the following event types: Invalid Score Changed Score Changed Rule for Scoring and Credit Limit Calculation Changed Risk Class Changed Check Rule Page 85 of 95 SAP Credit Management Configuration Guide November 2011 2. Make sure that, under Event Manager Type Linkages, the following settings are defined for the object type CL_UKM_BUSINESS_PARTNER: Detailed Settings Field Name User Action and Values Note Object Category ABAP class Object Type CL_UKM_BUSINESS_PARTNER Event WF_TRIGGER Receiver Type WS01700047 Receiver Call Function module Receiver Function SWW_WI_CREATE_VIA_EVENT_IBF Module Linkage Activated Active Select indicator 3. Call up the Workflow Builder for the multistep task WS01700047 (ID UKM_BUPA). Choose Goto Basic Data and then 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. Procedure Navigation Menu Path 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 SWETYPV Development Administration Event Manager Type Linkage Page 86 of 95 SAP Credit Management Configuration Guide November 2011 SAP Menu Tools Business Workflow SWDD Development Definition Tools Workflow Builder Workflow Builder ... 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 User Action and Values Comments Object Category ABAP class Object Type CL_UKM_ACCOUNT Event WF_TRIGGER Receiver Type WS01700048 Receiver Call Function module Receiver Function SWW_WI_CREATE_VIA_EVENT_IBF Module Linkage Activated Active 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 87 of 95 SAP Credit Management Configuration Guide November 2011 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. Procedure Perform the steps in these guidelines in the sequence in which they appear. 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 S_BCE_68000174 Financial Supply Chain Management Cash & Liquidity Management Cash Management Market Data Manual Market Data Entry Enter Exchange Rates SAP Customizing Implementation Guide SAP NetWeaver General Settings Currencies Define Translation Factors for Currency Translation Page 88 of 95 SAP Credit Management Configuration Guide November 2011 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 TBDM Chain Management Cash and Liquidity Management Cash Management Environment Market Data File Interface Import 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 business 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 89 of 95 SAP Credit Management Configuration Guide November 2011 2. The following reports are available to recreate the credit exposures from an SD system from SAP ERP 6.0: UKM_RFDKLI20 to recreate the credit exposure after organizational changes UKM_RVKRED77 to recreate the credit exposure where you have removed the cause of the error in the case of data inconsistencies UKM_RVKRED88 to simulate report UKM_RVKRED77 without setting blocks on the documents affected. This report prepares an update run of report UKM_RVKRED77 to determine suitable selection parameters, for example. 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 transaction data is recreated from the credit exposure information of FI-AR. Credit Check if Technical Problems Occur Use The system can only make credit checks if the necessary servers are available. Otherwise, it is unable to determine the following credit management account master data that is required for a credit check: Risk class Determining the risk class when creating sales documents is necessary in order to be able to define Customizing of the automatic credit control. Block of the credit management account The check whether the credit management account is blocked is required for all processing, as order and delivery processing is not permitted if there is a block. So that they are not completely blocked if SAP Credit Management or SAP NetWeaver Process Integration are not available, you can also create new sales documents in the event of such technical problems, and perform the credit check later. This function is only available to you if the SD system has at least the status SAP enhancement package 5 for SAP ERP 6.0. Note that with technical problems, you cannot perform the following activities: Change sales documents Create and change deliveries Process service orders Page 90 of 95 SAP Credit Management Configuration Guide November 2011 Activities To connect Sales and Distribution to SAP Credit Management use an implementation of Business Add-In BADI_SD_CM. If a technical problem occurs during the credit check, the system terminates processing and issues error message UKM_PI 008. However, if you want to use the option of creating sales documents despite this, and perform the credit check later, proceed as follows: 1. Configure message UKM_PI 008 as a warning message when technical problems occur. Use transaction OBA5 for this. 2. Create the sales documents as usual. The system creates the documents, but sets and indicator in the document header to the effect that for technical reasons they are blocked. 3. Make a new check of the blocked sales documents once the error has been solved. Use report UKM_RVKRED09_XI for this. This report recognizes from the indicator in the document header which documents are blocked for technical reasons, and releases them following a successful check. For additional information about this report, see the system documentation. Converting Organizational Changes Use If you make changes to the SAP Credit Management master data or in Customizing during daily operations, you may have to carry out corrections. Procedure Navigation Menu Path Transaction Code SAP Customizing Implementation Guide Financial Supply Chain Management Credit Management Credit Risk Monitoring Master Data Define Formulas SAP Menu Accounting Financial Supply UKM_MASS_UPD3 Chain Management Credit Management Master Data Mass Changes Credit Limit SAP Menu Accounting Financial Supply UKM_MASS_UPD2 Chain Management Credit Management Master Data Mass Changes Score SAP Menu Logistics Sales and Transaction VKM4 Distribution Credit Management Sales Documents All (Releases before SAP ERP 6.0) Report UKM_RFDKLI20 (Releases from SAP ERP 6.0) SAP Customizing Implementation Guide Financial Supply Chain Management Credit Management Credit Risk Monitoring Processes Define Events and Follow-On Processes ... Page 91 of 95 SAP Credit Management Configuration Guide November 2011 The following tables give you an overview of possible changes and the corresponding corrections: Change Measures Required Currency of a credit limit The credit limits of all business partners for this credit segment changed 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 No correction required. to Main Credit Segment The credit exposure of the main credit segment is always changed in Customizing of a determined dynamically at runtime according to the current credit segment Customizing. Customizing of a rule for Carry out a mass change. scoring and credit limit Depending on the type of change (formula of score or limit), calculation changed you choose the appropriate report and then select the business partners and/or credit accounts affected via the rule. Customizing of a check The modified check procedure has an effect on subsequent procedure changed 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 Delete and recreate the transaction data in the credit segments changed segments concerned. (for example, in For more information about the procedure, see Recreating implementations of the Data (Troubleshooting) [page 89]. Business Add-In UKM_FILL) Business partner relationship No correction required. changed, added, or deleted The credit exposure contributions of other partners are always determined dynamically. Rule for score and credit limit The change to the rule for scoring and credit limit calculation of change in master record of a business partner is published as an event. business partner changed In the Customizing settings for Events and Follow-On Processes, you can define that the rule for scoring and credit limit calculation is triggered. Check rule in master record of The change to the check procedure triggers the event with the business partner changed 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 92 of 95 SAP Credit Management Configuration Guide November 2011 Ensuring Data Protection Data that refers to natural persons is subject to legal data protection requirements that are different in each country. Typical requirements are, for example, that unauthorized access to the data must be prevented and that the purpose limitation of saved data must be adhered to. Procedure To implement the data protection guidelines, you have the following options in SAP Credit Management: Restrict access to data You can restrict the access to master data and transaction data using the authorizations for the role SAP_FIN_FSCM_CR_USER. For more information, see Defining Authorizations. Log changing accesses to master data The update of change documents with time, user, and transaction is supported for all master data fields of SAP Credit Management. Note the following special case: If the system determines master data, for example, a credit limit that is no longer valid, automatically as the result of a follow-on process during a credit check or an update of the commitment, the change document for this change contains the technical user defined in the communication channel (for example, CREDITXIUSER). Create own information To provide a business partner with information about the data saved for him in SAP Credit Management, compile the following data: Overview of the master data in SAP Credit Management with transaction UKM_MASS_DSP2 Overview of the transaction data in SAP Credit Management with transaction UKM_COMMITMENTS If required, a list of additional information with report UKM_ADD_INFOS_DISPLAY If required, the history of the credit limit and the score from SAP NetWeaver Business Intelligence, if you are using it. From SAP enhancement package 4 for SAP ERP 6.0, you can use a documented credit decision for your own information. This contains a summary of the credit relevant data and a chronology of the changes. If this data proves insufficient, you can either supplement the documented credit decision or use the options already mentioned. Page 93 of 95 SAP Credit Management Configuration Guide November 2011 Correct the incorrect data for a business partner Your business partner has the right to have you correct any incorrect data. Depending on the field, you have the following options: You can change the risk category and the credit limits manually, for example, if the system determined them based on an incorrect formula or on incorrect input parameters. Alternatively, you can have the system recalculate these fields once you have corrected the formula or input parameters concerned. You can manually change a score calculated incorrectly if you use a rule for the scoring and credit limit calculation that does not contain a formula for scoring. Alternatively, you can have the system recalculate this field once you have corrected the formula or input parameters that were incorrect. You can change negative credit events and data for collateral and credit insurances manually. You can delete incorrect commitment and credit exposure data with transaction UKM_COMMITMENTS; you then have to send the data from the client systems again. Delete or initialize data for the business partner You can delete the master data for a business partner manually per credit segment in transaction UKM_BP. For each rule for scoring and credit limit calculation, you can restrict the validity period for the scores and credit limits calculated. In a subsequent mass activity, you can, for example, select (via custom selections) all business partners with a specific rule for scoring and credit calculation and where the score is no longer valid and assign a new rule to them, whereby the formulas in the new rule initialize the score and the credit limit. You should enter negative credit events and data for collateral and credit insurances with a valid to date. Once this date has passed, the system no longer considers the events and data but they remain in the system. You can use report UKM_ADD_INFOS_DISPLAY to determine information that is no longer valid and then delete it manually. Transaction data, that is, line items with commitment information, is not stored permanently in SAP Credit Management; the system deletes it after clearing. You can delete data that you have extracted to SAP Netweaver Business Intelligence for a business partner from the ODS objects 0CDM_DS00 and 0CDM_DS01. The master and transaction data that you use in SAP Credit Management can be archived and deleted using the following archiving objects once the legally required retention time has been reached: o Data for the business partner: archiving object CA_BUPA o Data for the documented credit decision from SAP enhancement package 4 for SAP ERP 6.0: archiving object SCMG Page 94 of 95 SAP Credit Management Configuration Guide November 2011 Purpose limitation Data that arises in SAP Credit Management should only be used in that component. By implementing the method READ_RESPONSE of the Business Add-In UKM_CREDIT_INFO appropriately, you can enter a text for external credit information in order to document the use in SAP Credit Management. For example, you can restrict mass changes by rule for scoring and credit limit calculation or (via custom selections) by the credit group to prevent external information, scores, or credit limits being recalculated unnecessarily or without a legal requirement. Consent statement of the business partner for external credit information Inform your business partner explicitly if you use a rule that evaluates information from external credit information providers. Make sure that the rating only takes place if the business partner (natural person) has consented to this. You can document a withdrawal of consent by setting a block reason in the master data. Page 95 of 95