Credit Management

FI-AR: Credit ManagementPDF download from SAP Help Portal: http://help.sap.com/saphelp_erp60_sp/helpdata/en/be/7187411caa010de10000000a1550b0/content.htm Created on June 12, 2015 The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal. Note This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included. © 2015 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE 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. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices. Table of content PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 1 of 67 Table of content 1 FI-AR: Credit Management 1.1 SAP Credit Management Configuration Guide 1.1.1 SAP Credit Management (FIN-FSCM-CR) 1.1.2 Documentation Landscape for SAP Applications and Business Scenar 1.1.3 SAP Notes 1.1.4 Further Information 1.1.4.1 Terminology Changes from SAP ERP 6.0 1.1.5 System Connections 1.1.5.1 Process Integration with Logistics and Finance Systems: Overview 1.1.5.2 Preparing Use of SAP NetWeaver Business Intelligence 1.1.5.3 Setting Up Portal Connection (Optional) 1.1.5.4 System and Component Landscape 1.1.5.4.1 XI Interfaces: Overview 1.1.5.4.1.1 SAP A2A Interface CreditWorthinessQuery_In 1.1.5.4.1.2 SAP A2A Interfaces CreditCommitment_In and CreditCommitment_Out 1.1.5.4.1.3 SAP A2A Interface CreditPaymentRecord_In 1.1.5.4.1.4 SAP A2A Interface CreditPaymentBehaviourSummaryNotification_In 1.1.5.4.1.5 SAP B2B Interface CreditAgencyReportQuery_Out 1.1.5.4.1.6 SAP A2A Interface CreditManagementAccountByIDQuery_In 1.1.5.4.1.7 SAP A2A Interface CreditManagementAccountChangeNotification_In 1.1.5.4.1.8 SAP A2A Interface CreditWorthinessCriticalPartiesQuery_In 1.1.5.4.1.9 SAP A2A Interface CreditWorthinessChangeInformation_Out 1.1.5.4.1.10 SAP Component Interface FICARatingReplicate 1.1.5.4.2 Connecting External Information Providers 1.1.5.4.3 Connecting Accounts Receivable Accounting ERP 2005 1.1.5.4.4 Connecting Accounts Receivable Accounting ERP 2004 1.1.5.4.5 Connecting Accounts Receivable Accounting 4.70 or 4.6C 1.1.5.4.6 Connecting Contract Accounts Receivable and Payable as of SAP ER 1.1.5.4.7 Connecting Contract Accounts Receivable and Payable 4.72 1.1.5.4.8 Connecting Sales and Distribution ERP 2005 1.1.5.4.9 Connecting Sales and Distribution ERP 2004 1.1.5.4.10 Connecting Sales and Distribution 4.70 or 4.6C 1.1.5.4.11 Connecting Customer Relationship Management (SAP CRM 5.1) 1.1.5.4.12 Connecting Customer Relationship Management (SAP CRM 5.0 and SAP 1.1.6 Data Replication 1.1.6.1 Providing Business Partner Data 1.1.6.2 Replicating Master Data of Accounts Receivable Accounting (FI-AR 1.1.6.3 Replicating Master Data of Contract Accounts Receivable and Paya 1.1.6.4 Replicating SAP CRM Master Data 1.1.7 Business Customizing 1.1.7.1 Settings in SAP Credit Management (FIN-FSCM-CR) 1.1.7.1.1 Activating the Business Partner Role for Credit Management 1.1.7.1.2 Configuring Business Partner Additional Information 1.1.7.1.3 Defining Authorizations 1.1.7.1.4 Define Events and Follow-On Processes 1.1.7.2 Process Integration with SAP Systems 1.1.7.2.1 Making Settings in FI-AR ERP 2005 1.1.7.2.2 Making Settings in FI-AR ERP 2004 1.1.7.2.3 Making Settings in FI-AR 4.70 or 4.6C 1.1.7.2.4 Settings in Contract Accounts Receivable and Payable as of SAP E 1.1.7.2.5 Making Settings in Contract Accounts Receivable and Payable (FI1.1.7.2.6 Making Settings in SD ERP 2005 1.1.7.2.7 Making Settings in SD ERP 2004 1.1.7.2.8 Making Settings in SD 4.70 or 4.6C 1.1.7.2.9 Making Settings in SAP CRM 5.1 1.1.7.2.10 Making Settings in SAP CRM 5.0 and SAP CRM 4.0 Service Industrie 1.1.8 Setting Up Component-Specific Master Data 1.1.8.1 Defining Credit Master Data in the Business Partner 1.1.9 Workflow Settings 1.1.9.1 Configuring Notifications PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 2 of 67 1.1.9.2 Configuring Approvals for Credit Limit Changes 1.1.10 Current Settings 1.1.10.1 Importing Exchange Rates 1.1.10.2 Recreating Data (Troubleshooting) 1.1.10.3 Converting Organizational Changes 1.1.10.4 Ensuring Data Protection PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 3 of 67 you can call up the credit check in SAP Credit Management . Process PUBLIC © 2014 SAP SE or an SAP affiliate company. Accounts Receivable Accounting (FI-AR) regularly provides SAP Credit Management (FIN-FSCM-CR) with the current status of customer open items. When you receive and process new sales orders in the sales and distribution system (SD). check. and evaluate this data in SAP Credit Management . You can then hold back further deliveries to customers via SD so that the customer is forced to pay before he receives any further deliveries. The Sales and Distribution (SD) system and the Accounts Receivable Accounting (FI-AR) system provide the Credit Management system with credit-relevant customer data. Page 4 of 67 .FI-AR Credit Management Purpose You can use this business process to monitor the risk of losses on receivables from your customers and to restrict this loss by means of a credit limit. SAP Credit Management is the leading component. All rights reserved. you then update. In this business process. The system checks whether the order is within the credit limit for the customer and also checks characteristics of the customer’s score. This enables you to recognize very early when a customer is no longer able to pay open invoices due to his weak financial situation. delivery of goods). This information is stored in the credit account of the customer as liability data. the sales order can also be released. 12. and saved there in the status of the sales order. Save blocked sales contract The result of the credit check is negative: The credit limit is exceeded. customer. The sales order is therefore blocked in the system to prevent further processing (for example. This data is then used there for various different steps in the credit check. Release sales order PUBLIC © 2014 SAP SE or an SAP affiliate company. This could be information about dunning transactions. Once you have done this you can process the order further in the system. Update total liability (accounts receivable) Via the XI interface. If the credit limit is increased. he can adjust it manually and increase the credit limit if necessary.) The credit manager analyzes the credit profile of the customer and checks whether the current credit limit corresponds to the default risk. 10. you can carry out this step as a batch run. 3. However. Update FI summary Via the XI interface. the credit manager calls up the list of blocked sales orders and selects the sales order to be checked again. 5. last payment. The credit check takes place in SAP Credit Management : The SD system calls up SAP Credit Management and transfers the required data from the sales order. oldest open items. for example. 7. you could process the sales order further). (Alternatively. Carry out credit check The credit manager repeats the credit check for the sales order selected (see step 7: Carry out credit check). Repeat credit check In SD. SAP Credit Management receives all data required from the SD system. Report open items Accounts Receivable Accounting reports open items to SAP Credit Management per customer. Normally this happens once each day after all incoming and outgoing payments have been processed in Accounts Receivable Accounting. All rights reserved.1. you can also forward data about Days Sales Outstanding (DSO) or average days in arrears. (If the result of the credit check had not been negative. Possible credit checks are: ¡ Statistical check of credit exposure ¡ Dynamic credit limit check with credit horizon ¡ Check for maximum dunning level ¡ Check for maximum document values ¡ Check for age of oldest open item ¡ Check for payment behavior index (as customer enhancement) The results of the check steps carried out are summarized. and that the total liability plus the order value does not exceed the customer’s credit limit. this workflow does not form part of the process variant described. Create FI summary Accounts Receivable can report further credit-relevant data of a customer to SAP Credit Management . The credit checks that are executed depend on the check rules defined in the credit master data record of the customer. the total liability of the customer is updated simultaneously. 8. 9. Carry out credit check Via an interface. 6. Create sales order The SD employee creates a sales order in the SD system either directly or based on a previous offer that the customer has agreed to. SAP Credit Management receives information about the FI summary from Accounts Receivable. If this is not the case. Change credit limit At regular intervals. Call credit check Before a sales order can be processed further. Via customer enhancements and BAdI implementations. 2. 11. forwarded to the SD system. This data is stored in the credit account of the customer as an FI summary and can be viewed there or used for credit checks. and sales organization. but is the prerequisite for a subsequent credit check. Page 5 of 67 . This step runs independently of SAP Credit Management . you must ensure that the customer has a sufficient score. the credit manager checks whether there are blocked orders in SD. 4. SAP Credit Management receives information about the open items for a customer from Accounts Receivable. The order provides check-relevant information later. the credit manager can be informed via workflow when the result of a credit limit check for a customer is negative. order value. by using system-independent XML interfaces. SAP Credit Management receives new information about the customer’s liability that has arisen from the acceptance of the sales order. 17.1. Update total liability (accounts receivable) The reporting of the open items from Accounts Receivable Accounting updates the total liability of the customer. the system creates a message for SAP Credit Management that reduces the total liability of the customer there by the value of the order. 15. This is a risk for the company since costs arise that customers pay later. 19. the relevant open items are created there in the customer account. Update total liability (sales) Via an interface. Report sales order value A sales order that is accepted triggers. SAP Credit Management saves the order value in the line items in the credit account of the customer and updates the total liability. In the SD system. 14. the user can display an overview of the liability categories reported (for example. the total liability is therefore reduced by the value of the order reported. Feedback on Configuration Guide In order to continually improve the configuration guide. 13. the credit manager can block the acceptance of sales orders from customers thus determined as critical if these customers do not reduce their total liability via payment of open invoices.1 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. you can also connect external non-SAP systems. The risk to the company is now reflected in the form of the invoice payable in Financial Accounting. This configuration guide provides additional contexts and background that may be useful for Customizing. Content The configuration guide describes which structures and activities of the Implementation Guide (IMG) that you have to process to implement the business process. In the liability total evaluation. see Documentation Landscape of SAP Solutions and Business Scenarios. Efficient receivables and credit management reduces the risk of financial losses and helps you to optimize business relationships with your business partners. production or deliveries.sap. Report open items At regular intervals. In SAP Credit Management . SAP Credit Management Configuration Guide Purpose This configuration guide applies to the use of SAP Credit Management with the corresponding release of the related SAP application components. 16. It also supports you in a heterogeneous and distributed system landscape. If you find errors in the configuration guide. 1. open orders or open items). PUBLIC © 2014 SAP SE or an SAP affiliate company. 20.If the result of the credit check is positive. the open items in Accounts Receivable Accounting are reported to SAP Credit Management per customer. see the IMG documentation of your SAP system. possibly weeks or months later. and Business Processes The system landscape has already been set up using the Master Guide and other documentation. Update total liability (sales) The transfer of the invoice to Accounts Receivable Accounting completes the processing of the sales order in Logistics. Execute early warning list With an early warning list ( credit exposure list ). At the same time. Business Scenarios. the credit manager can save the sales order. for example. Page 6 of 67 . 18. we would appreciate your feedback. For information about the individual IMG activities. 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. 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. Create open item As a result of the transfer of the billing document to Accounts Receivable Accounting. enter a message for the component SAP Credit Management (FIN-FSCM-CR) on SAP Service Marketplace at service.com/message. All rights reserved. Create billing document The SD employee creates the billing document for the sales order (that has been released) and this is transferred to Accounts Receivable automatically. you can identify customers whose credit exposure is approaching 100%. The order value is therefore reported to SAP Credit Management as a liability. For information on further documentation and where the latest versions are published. the SD system then sends an order confirmation to the customer. 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. 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. 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: Master data of the business partner (for example, country of origin of the business partner) Payment behavior (for example, average days in arrears) Dunning history (for example, number of dunning notices in the last 12 months) SAP Dispute Management (for example, the number of dispute cases in the last 12 months) The external and internal credit information determined is stored in the master data of the business partner. The system monitors the validity of the data determined periodically. The score data can be updated either manually or automatically. PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 7 of 67 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. 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 . Documentation Landscape for SAP Applications and Business Scenarios This documentation gives you an overview of the most important sources of information that you need in connection with SAP applications, business scenarios, and business processes. Make sure that you always use the most up-to-date documents for your implementation. Document Storage Location Document Location Master Guide, Installation Guide, and Upgrade Guide service.sap.com/instguides Implementation Guide (IMG) SAP System Business Scenario Description, Business Process Description SAP Solution Manager SAP Library help.sap.com Comment: Also available under Help → SAP Library in the SAP system SAP Notes service.sap.com/notes to search for notes service.sap.com/instguides listed by installation and upgrade guide Technical infrastructure (for example, hardware sizing, platforms, network security) service.sap.com/ti Description of the Documents ● Master Guide, Installation Guide, and Upgrade Guide These documents describe how you install or upgrade the system landscape required for a business scenario. The central initial access document for every SAP application is the Master Guide. It lists, for each business scenario, the SAP application components and third-party applications required, and refers to their installation and upgrade guides. These guides are Component Installation Guides, Business Scenario Upgrade Guides, and Component Upgrade Guides. ● Implementation Guide (IMG) This tool enables you to adapt SAP systems to meet specific customer requirements. The IMG contains the IMG activities for all SAP components with general documentation. The structure is component-oriented, and has no reference to a business scenario. If this reference is required, it is created as follows: By the Configuration Guide, with a textual link to the IMG, and by the content of SAP Solution Manager that links to the IMG activities for each business scenario and process. ● Business Scenario Description This document describes how a business scenario runs once all components have been installed and configured. For each business process of a business scenario there is a business process description and a component view as graphical representation. This shows the process steps in the respective SAP component. ● SAP Library This documentation describes the different SAP components. 1.1.3 SAP Notes Use PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 8 of 67 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 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. Further Information Use The following list contains useful information for configuration: Further Information Information Quick Link on SAP Service Marketplace (at service.sap.com) or Location in SAP Solution Manager SAP Credit Management Application Documentation helpportal Documentation → SAP ERP Central Component → ERP Central Component (Release 6.0) → SAP ERP Central Component → Financials → SAP Financial Supply Chain Management (FIN-FSCM) → SAP Credit Management (FIN-FSCM-CR) BI Business Content of SAP Credit Management helpportal Documentation → SAP ERP Central Component → ERP Central Component (Release 6.0) → SAP NetWeaver Library → SAP NetWeaver by Key Capability → Information Integration by Key Capability → BI Content → Financials → SAP Financial Supply Chain Management → SAP Credit Management (FIN-FSCM-CR) Documentation for SAP Exchange Infrastructure 7.0 (XI) helpportal Documentation → SAP ERP Central Component → ERP Central Component (Release 6.0) Key Capability → → SAP NetWeaver Library → SAP NetWeaver by Process Integration by Key Capability → SAP Netweaver Exchange Infrastructure Configuration Guide – SAP XI 7.0 How-to-Guides for SAP Exchange Infrastructure 3.0 (XI): Mapping within XI 3.0 SAP Solution Manager nw04 SAP NetWeaver → SAP NetWeaver 2004 – Release-Specific Information → How-to Guides → Exchange Infrastructure Document from the previous release that is still helpful. Documentation on Portal Content Business process description: FI-AR: Credit Management SAP Credit Management Security Guide (English Version) http://www.sdn.sap.com/irj/sdn/developerareas/contentportfolio SAP Solution Manager securityguide mySAP ERP 2005 Security Guides → mySAP ERP 2005 Security Guides → SecGuide_CredMan_60_* Familiarize yourself with the documentation landscape for SAP solutions, business scenarios, and business processes. For information on the type of documentation SAP provides and where the latest versions are published, see Documentation Landscape of SAP Solutions and Business Scenarios. Terminology Changes from SAP ERP 6.0 With effect from SAP ERP 6.0, the use of the following terms has changed: Old New FI summary Payment Behavior Summary Total liability Credit Exposure Credit Exposure Commitment Credit query Credit check PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 9 of 67 An exception is telecommunications in SAP CRM 5. SAP ERP 2005) ○ Regular credit exposure report for open customer line items ○ Regular update of the payment behavior summary in SAP Credit Management based on payment information ○ For a process description of the integration of SAP Credit Management with the SD and FI-AR components. The integration of CRM service orders is not yet implemented in the current release.6C. The following analysis scenarios are provided: ● ● ● ● Credit Profile Credit Risk New Rating and Simulation Analysis Business Partner Rating The settings you have to make to use Business Content for SAP Credit Management are described in this section. This ensures full monitoring of the credit risk from order entry through to bill payment.0 is available with the Industry Add-On for CRM 4.6C. Process Integration with Logistics and Finance Systems: Overview SAP Credit Management provides direct integration with the SD. Page 10 of 67 . SAP CRM 5. This involves. SAP ERP 2004. FI-AR.1. R/3 Enterprise. for example: · Defining logical systems and assigning clients in the Online Transaction Processing System (OLTP) · Determining the systems. 1. PUBLIC © 2014 SAP SE or an SAP affiliate company. and FI-CA processes. ● Industry Release Contract Accounts Receivable and Payable (FI-CA 4. Preparing Use of SAP NetWeaver Business Intelligence Use In SAP Credit Management you can use Business Content to evaluate your credit management data. distribution models and so on. SAP CRM 5.These differences are particularly important if you use applications with different releases.0. SAP ERP 2005) ○ Credit limit check on creating or changing sales orders and deliveries ○ Credit exposure report on saving an order ○ Credit exposure report on saving a delivery ○ Credit exposure report on creating a billing document Constraints The credit limit check and credit exposure update when you create or change a delivery are only available from SAP ERP 2005. Service orders are currently not supported.0. clients.1.1) ○ 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. R/3 Enterprise. SAP ERP 2004. You can currently only connect a CRM system as part of a customer project. ● FI-AR (R/3 4.0 Service Industries Add-On.72 from SAP ERP 2005) ○ Regular credit exposure report for open customer items on a totals item basis ○ Regular update of the payment behavior summary in SAP Credit Management ○ Import of FI-CA creditworthiness to the master data of SAP Credit Management ○ Support of commitment query of SAP Credit Management ○ Support of partner messages of SAP Credit Management ● SAP CRM (4. servers. 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. You have the following integration options for SAP Credit Management 6.0 : ● SD (R/3 4.5 System Connections Purpose This section contains information about connecting the systems in a SAP system landscape. see the documentation for SAP Credit Management in the SAP Library . All rights reserved. 5.sap. PUBLIC © 2014 SAP SE or an SAP affiliate company. 3. For more information. ■ For information about configuration. The data exchange is processed via XML interfaces (XI). Your SAP NetWeaver BI runs in a separate system. 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). Use either the full update or the delta update.com/irj/sdn/developerareas/contentportfolio. and analyze credit information from connected systems and components centrally. System and Component Landscape You can use SAP Credit Management and other integrated components in a single system landscape or a multiple system landscape. Page 11 of 67 . which means that you can connect both SAP and non-SAP systems. For more information. In each OLTP system. 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. For more information on the interfaces used. see SAP Library for Business Intelligence under Data Warehousing → Data Warehouse Management → Scheduler (3. 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. see SAP Library under SAP NetWeaver Library → SAP NetWeaver by Key Capabilities → Information Integration by Key Capability . 2.sdn. Setting Up Portal Connection (Optional) Use In SAP Credit Management you can use a wide range of analysis and processing functions in SAP Enterprise Portal . 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. transfer the DataSources to the active version. see the SAP Library for Business Intelligence under Data Warehousing → Data Acquisition → Source System → Create SAP Source System. For the list of existing DataSources see the BI Content of Credit Management (FIN-FSCM-CR) detailed above. Prerequisites You use SAP NetWeaver BI .01 and SAP Enterprise Portal . This is separate from the OLTP systems in which you run Dispute Case Processing and Process Integration with Accounts Receivable. By planning InfoPackages for the different InfoSources. For more information about scheduling InfoPackages. you can load data into the BI system. activate the Business Content for SAP Credit Management. see the SAP Library for Business Intelligence under Data Warehousing → Data Acquisition → Source System → Connection between Source System and BW. All rights reserved. the BI System.x) → Schedule InfoPackage . Procedure 1. You can collect. see Business Intelligence . see SAP Library for Business Intelligence under Data Warehousing → Data Warehouse Management → Business Content (Versions) → Installing Business Content. ■ For information about BI Content of SAP Credit Management . manage. For more information. this architecture also enables you to distribute and use the credit information effectively in the systems and components connected. In the BI system.For more information about SAP NetWeaver Business Intelligence (SAP NetWeaver BI) . For more information on Business Package for Credit Management 6. see XI Interfaces: Overview. see the Internet at http://www. see BI Content → Financials → SAP Financial Supply Chain Management → SAP Credit Management (FIN-FSCM-CR). 4. Replicate the DataSources from the OLTP system to the BI system. for other components only as customer project SAP Enterprise Portal 6.0.1 Optional Note that the integration for Sales and Distribution (SD) in releases that are earlier than SAP ERP 2005 is subject to a restricted level of functions.0 Mandatory SAP NetWeaver Exchange Infrastructure 3.1 Optional Note that the integration for Accounts Receivable Accounting (FI-AR) in releases that are earlier than SAP ERP 2005 is subject to a restricted level of functions.00 Comments Mandatory (FIN-FSCM-CR) See the precise technical prerequisites described in the following SAP Notes: ● 967611 ● 969190 SAP NetWeaver Application Server 7. For more information. For more information. You can connect either Accounts Receivable Accounting (FI-AR) or Contract Accounts Receivable and Payable (FI-CA) as SAP Financial Accounting system. Plug-In 2004.2 4. see the documentation for Contract Accounts Receivable and Payable under Integration with SAP Credit Management. All rights reserved. see SAP note 1096883.0 Optional External Credit Information External system Optional Financial Accounting External system Optional Sales and Distribution External system Optional PUBLIC © 2014 SAP SE or an SAP affiliate company. SAP NetWeaver Business Intelligence SAP Customer Relationship Management (CRM) BI Business Content 3.72 Optional Note that the integration for Contract Accounts Receivable and Payable (FI-CA) in releases that are earlier than SAP ERP 2005 is subject to a restricted level of functions.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 . Page 12 of 67 .0 Mandatory Accounts Receivable Accounting (FI-AR) 4. Contract Accounts Receivable and Payable (FI-CA) As of Industry Release 4. Application Components and Systems Component/System SAP Credit Management Minimum SAP Release Financial Basis 6.6C. Recommendation: 7.5. see SAP note 1096882. CRM Industry Add-On Edition 2004 Optional Optional. Sales and Distribution (SD) 4.6C. For detailed information about the integration of Contract Accounts Receivable and Payable (FI-CA). Released for mySAP Telecommunications .0 or higher. Plug-In 2004. 5.1 XI Interfaces: Overview You can use the following XI interfaces in SAP Credit Management : XI Interface Description SAP A2A-Interface CreditWorthinessQuery_In Credit query SAP A2A-Interfaces CreditCommitment_In and CreditCommitment_Out Credit exposure update SAP A2A-Interface CreditPaymentRecord_In Payment behavior summary (reduced scope) SAP A2A-Interface CreditPaymentBehaviourSummaryNotification_In Payment behavior summary SAP B2B-Interface CreditAgencyReportQuery_Out External credit information SAP A2A-Interface CreditManagementAccountByIDQuery_In Request for data of the credit account SAP A2A-Interface CreditManagementAccountChangeNotification_In Change to the data of the credit account SAP A2A Interface CreditWorthinessCriticalPartiesQuery_In Critical business partners SAP A2A-Interface CreditWorthinessChangeInformation_Out Reporting of events to connected systems SAP Component-Interface FICARatingReplicate Comparison of FI-CA creditworthiness with score from SAP Credit Management The following figure gives you an overview of the use of individual XI interfaces for data exchange in SAP Credit Management . Page 13 of 67 .4.4.1.1. XI Choreography in SAP Credit Management 1.1 SAP A2A Interface CreditWorthinessQuery_In PUBLIC © 2014 SAP SE or an SAP affiliate company.1.1. All rights reserved.5. the decision in the requesting application as to whether or not to have business dealings with this business partner. synchronous) When an application sends a creditworthiness query. Accounts Receivable Accounting or Sales and Distribution ) sends a query to SAP Credit Management .Description The interface CreditWorthinessQuery_In requests information about the creditworthiness of business partners. The query is synchronous. Message Interfaces CreditWorthinessQuery_In (inbound. PUBLIC © 2014 SAP SE or an SAP affiliate company. The message interface uses the message types CreditWorthinessQuery and CreditWorthinessResponse. Data Types CreditWorthinessQueryMessage The figure below shows the data type CreditWorthinessQueryMessage that contains an entry of the data type CreditWorthinessQuery. All rights reserved. for example. ● CreditWorthinessResponse: Determines the structure of the response message containing the required details about the creditworthiness (for example. This information influences. CreditWorthinessResponse This message type uses the data type CreditWorthinessMessage that represents a response to the creditworthiness query. Message Types CreditWorthinessQuery This message type uses the data type CreditWorthinessQueryMessage that represents a message for querying creditworthiness. and SAP Credit Management returns the required information such as the score and recommended credit limit for the business partner. It uses the following message types: ● CreditWorthinessQuery: Determines the structure of the creditworthiness query of a business partner. The application that wants information on the creditworthiness of a business partner (for example. the message interface is the inbound interface to SAP Credit Management . score and credit limit) of a business partner. Page 14 of 67 . All rights reserved. PUBLIC © 2014 SAP SE or an SAP affiliate company. Page 15 of 67 .The data type CreditWorthinessQuery contains the following elements: ● CreditSegmentInternalId – Credit segment in SAP Credit Management GDT: CreditSegmentInternalID ● CheckedAmount – Amount to be checked (such as the order value) GDT: Amount ● CheckingRuleCode – Encoded display of the rule to be used to determine the creditworthiness GDT: CreditWorthinessCheckingRuleCode ● CheckingServityCode – Encoded display of the severity of the check procedure to be used GDT: CreditWorthinessCheckingSeverityCode ● CreditAgencyReportRetrievalPermissionIndicator – Indicator to show whether or not a business partner has granted permission for credit information to be obtained about him or her GDT: CreditAgencyReportRetrievalPermissionIndicator ● DebtorParty – Customer whose creditworthiness is to be determined GDT (InternalId): PartyInternalID ● CreditorParty – Not used in SAP Credit Management ● SellerParty – Not used in SAP Credit Management ● ProductCategory – Not used in SAP Credit Management CreditWorthinessMessage The figure below shows the data type CreditWorthinessMessage that contains an entry of the data type CreditWorthiness. Page 16 of 67 . All rights reserved.The data type CreditWorthiness contains the following elements: ● CreditSegmentInternalId – Credit segment in SAP Credit Management GDT: CreditSegmentInternalID ● Indicator – Specification of whether there is a creditworthiness for the business partner for the query parameters specified GDT: CreditWorthinessIndicator ● CheckingDescription – Description of the flow of a creditworthiness check GDT: Description ● DebtorPartyBlockedIndicator – Specification of whether the business partner is blocked in SAP Credit Management GDT: Indicator ● DebtorPartySpecialAttentionRequiredIndicator – Specification of whether the business partner should be subject to special attention GDT: Indicator ● DebtorParty – Customer whose creditworthiness was determined GDT: PartyInternalID ● CreditorParty – Not used in SAP Credit Management ● SellerParty – Not used in SAP Credit Management ● ProductCategory – Not used in SAP Credit Management ● Rating – Score of a business partner determined by SAP Credit Management and valid for a specific period Rating contains the following elements: ○ Code – Coded display of the score value GDT: CreditRatingCode ○ ValidityPeriod – Validity period of the score value GDT: DateTimePeriod ● RiskClass – Payment default risk determined by SAP Credit Management and valid for a specific period RiskClass contains the following elements: ○ Code – Coded display of the risk class GDT: CreditRiskClassCode ○ ValidityPeriod – Validity period of the risk class GDT: DateTimePeriod ● CreditLimit – Credit valid for a business partner for a specific period CreditLimit contains the following elements: ○ Amount – Amount of the credit GDT: Amount ○ ValidityPeriod – Validity period of the credit GDT: DateTimePeriod ● CreditExposure – Current credit exposure of the business partner CreditExposurecontains the following element: ○ Amount – Amount of the credit exposure GDT: Amount Mapping Objects PUBLIC © 2014 SAP SE or an SAP affiliate company. asynchronous) When an application sends its information about commitments. The message mapping is also delivered with the XI content of the software component version FINBASIS_300 from support package 06. synchronous) This message interface is used when SAP Credit Management requests information about commitments from the applications connected.6C or 4.Interface Mapping UkmCreditQuery_CreditWorthinessQuery This interface mapping connects SD systems with release version 4. thus enabling company-wide monitoring of the credit limits. With commitment notification. Message Mapping UkmCreditQuery_CreditWorthinessQuery The interface mapping with the same name described above uses this message mapping. Page 17 of 67 . SAP Credit Management actively requests the information from the application concerned. Message type CreditCommitmentQuery is used for the query. It is delivered with the XI content of the software component version FINBASIS_300 from support package 06. Message Interfaces CreditCommitmentNotification_In (inbound. With commitment query. the application sends the information at non-specific intervals to SAP Credit Management .70 to the credit check in SAP Credit Management . An application that has information about commitments of business partners sends this information to SAP Credit Management according to the company’s own rules or when requested to do so. Message Types CreditCommitmentNotification This message type uses the data type CreditCommitmentMessage that represents a message for transferring a business partner’s existing commitments. the message interface is the inbound interface into SAP Credit Management . whereas message type CreditCommitmentResponserepresents the notification. It maps the interface of the RFC module UKM_CREDIT_QUERY to the interface CreditWorthinessQuery_In. All rights reserved. CreditCommitmentQuery_Out (outbound. The message interface consists of the message type CreditCommitmentNotification. There is a difference between commitment notification and commitment query. CreditCommitmentQuery This message type uses the data type CreditCommitmentQueryMessage that represents a message for querying a business partner’s existing PUBLIC © 2014 SAP SE or an SAP affiliate company. SAP A2A Interfaces CreditCommitment_In and CreditCommitment_Out Description These interfaces provide SAP Credit Management with information about commitments. The inbound information is collected and consolidated. CreditCommitmentResponse This message type uses the data type CreditCommitmentMessage that represents a message for transferring a business partner’s existing payment obligations (commitments).commitments. All rights reserved. The data type CreditCommitmentcontains the following elements: · CreditSegmentInternalId – Credit segment in SAP Credit Management GDT: CreditSegmentInternalID · TypeCode – Credit exposure category with the following standard values: ¡ 100 – Sales value (order value) ¡ 200 . Data Types CreditCommitmentMessage The figure below shows the data type CreditCommitmentMessage that contains one or more entries of the data type CreditCommitment. Page 18 of 67 .Receivables ¡ 300 – Special credit exposure ¡ 400 – Value of goods supplied ¡ 500 – Special credit exposure GDT: CreditCommitmentTypeCode · Amount – Amount GDT: Amount · SecuredAmount – Hedged amount GDT: Amount · UnsecuredAmount – Unhedged amount GDT: Amount · ValidityDate – Validity date GDT: Date · AmounceBalanceIndicator – Indicates whether it is a balance or a commitment GDT: AmountBalanceIndicator · AmountDifferenceIndicator – Indicates whether the amount is a difference amount GDT: AmountDifferenceIndicator PUBLIC © 2014 SAP SE or an SAP affiliate company. It maps the interface of the RFC module UKM_COMMMITMENTS_PUSH to the interface CreditCommitmentNotification_In. instead. PendingCommitmentcontains the following elements: ¡ GroupID – Identifier that links together related CreditCommitment messages ¡ GDT:BusinessTransactionDocumentGroupID ¡ CompletedIndicator – Indicates whether the business transaction is complete (in other words. The credit exposure is not updated immediately when the first message of a group is received. The data type CreditCommitmentQuerycontains the following elements: · CreditSegmentInternalId – Credit segment in SAP Credit Management for which the connected systems send the commitments GDT: CreditSegmentInternalID · ValidityDate – Validity date GDT: Date · DebtorParty – Description of the customer whose payment obligations are to be reported GDT (InternalId): PartyInternalID · CreditorParty – Not used in SAP Credit Management · SellerParty – Not used in SAP Credit Management · ProductCategory – Not used in SAP Credit Management Mapping Objects Interface Mapping UkmCommitmentsPush_CreditCommitmentNotification This interface mapping connects Accounts Receivable Accounting systems or SD systems with release version 4. Message Mapping UkmCommitmentsPush_CreditCommitmentNotification PUBLIC © 2014 SAP SE or an SAP affiliate company.· DebtorParty – Description of the customer whose payment obligations are reported GDT (InternalId): PartyInternalID · CredtorParty – Not used in SAP Credit Management · SellerParty – Not used in SAP Credit Management · ProductCategory – Not used in SAP Credit Management · PendingCommitment – Related information about a payment obligation is grouped together to avoid temporary data inconsistencies when the commitment is updated in SAP Credit Management . whether the last message of the group has been received and the temporary commitment can be deleted). Page 19 of 67 . it is stored in a temporary area until the following message(s) confirm this commitment.70 to SAP Credit Management . It is delivered with the XI content of the software component version FINBASIS_300 from support package 06. All rights reserved. ¡ GDT:BusinessTransactionCompletedIndicator · InvoiceReference – Reference to an outbound invoice document GDT: BusinessTransactionDocumentReference · OutboundDeliveryReference – Reference to an outbound delivery document GDT: BusinessTransactionDocumentReference · SalesOrderReference – Reference to a sales order GDT: BusinessTransactionDocumentReference · IncomingPaymentReference – Reference to an incoming payment GDT: BusinessTransactionDocumentReference · AccountingDocumentReference – Reference to an accounting document GDT: BusinessTransactionDocumentReference · PredecessorReference – Reference to a preceding document CreditCommitmentQueryMessage The figure below shows the data type CreditCommitmentQueryMessage that contains one or more entries of the data type CreditCommitmentQuery.6C or 4. SAP A2A Interface CreditPaymentRecord_In Description CreditPaymentRecord transfers payment behavior summaries of business partners bundled. Message Interfaces CreditPaymentRecordNotification_In (inbound. Message Types CreditPaymentRecordNotification This message type consists of the data type CreditPaymentRecordMessage that represents a message for transmitting the payment behavior summaries for business partners. you can still use the interface CreditPaymentRecord_In after an upgrade to mySAP ERP 2005 . Page 20 of 67 . However. For more information about the interface CreditPaymentBehaviourSummaryNotification_In. the new interface contains more key figures. All rights reserved. PUBLIC © 2014 SAP SE or an SAP affiliate company. The interface CreditPaymentRecord_In is replaced by the interface CreditPaymentBehaviourSummaryNotification_In from mySAP ERP 2005 . the message interface is the inbound interface into SAP Credit Management . Data Types CreditPaymentRecordMessage The figure below shows the data type CreditPaymentRecordMessage that contains one or more entries of the data type CreditPaymentRecord. asynchronous) When an application sends its payment behavior summaries. see SAP A2A Interface CreditPaymentBehaviourSummaryNotification_In. The message mapping is also delivered with the XI content of the software component version FINBASIS_300 from support package 06. The message interface consists of the message type CreditPaymentRecordNotification.The interface mapping with the same name described above uses this message mapping. The message mapping is also delivered with the XI content of the software component version FINBASIS_300 from support package 06. number of dunning notices.The CreditPaymentRecord data type contains the following elements: · CreditSegmentInternalId – Credit segment in SAP Credit Management GDT: CreditSegmentInternalID · ReferenceDocumentDate – Date of reference document GDT: Date · DebtorParty – Description of the customer whose payment behavior summaries are reported GDT (InternalId): PartyInternalID · CreditorParty – Not used in SAP Credit Management · SellerParty – Not used in SAP Credit Management · ProductCategory – Not used in SAP Credit Management · LastPayment – Payment amount and date of last payment · OpenItem – Highest open item amount with due date · Dunning – Dunning information (amount.6C or 4. Message Mapping UkmVectorPush_CreditPaymentRecordNotification The interface mapping with the same name described above uses this message mapping. All rights reserved. Page 21 of 67 . It is delivered with the XI content of the software component version FINBASIS_300 from support package 06. date. highest dunning level) · KeyFigures – Payment behavior summary without line item reference ¡ ReceivablesAmount – Weighted receivables total ¡ DaysOfSalesOutstanding – Number of days of overdue items ¡ OverdueOpenItemsPercentage .70 to SAP Credit Management . PUBLIC © 2014 SAP SE or an SAP affiliate company.Proportion of overdue items in the total · InvoiceReference – Reference to an invoice document · IncomingPaymentReference – Reference to a payment document · DunningReference – Reference to a dunning transaction document Mapping Objects Interface Mapping UkmVectorPush_CreditPaymentRecordNotification This interface mapping connects Accounts Receivable Accounting systems with release version 4. It maps the interface of the RFC module UKM_VECTOR_PUSH to the interface CreditPaymentRecordNotification_In. PUBLIC © 2014 SAP SE or an SAP affiliate company. The message interface uses the message types CreditPaymentBehaviourSummaryNotification and CreditPaymentBehaviourSummaryFault. Page 22 of 67 .SAP A2A Interface CreditPaymentBehaviourSummaryNotification_In Definition CreditPaymentBehaviourSummary transfers information about the payment behavior or business partners. Message Interfaces CreditPaymentBehaviourSummaryNotification_In (inbound. the message interface is the inbound interface into SAP Credit Management . asynchronous) When an application sends its payment behavior summaries. Message Types CreditPaymentBehaviourSummaryNotification This message type consists of the data type CreditPaymentBehaviourSummaryMessage that represents a message for transmitting the payment behavior summaries for business partners. Data Types CreditPaymentBehaviourSummaryMessage The figure below shows the data type CreditPaymentBehaviourSummaryMessage that contains one or more entries of the data type CreditPaymentBehaviourSummary. CreditPaymentBehaviourSummaryFault This message type uses the data type ExchangeFaultData that carries out a standard transfer of exceptions that arise in SAP Credit Management . All rights reserved. SAP B2B Interface CreditAgencyReportQuery_Out PUBLIC © 2014 SAP SE or an SAP affiliate company.The CreditPaymentBehaviourSummary data type contains the following elements: · CreditSegmentInternalId – Credit segment in SAP Credit Management GDT: CreditSegmentInternalID · DebtorParty – Description of the customer whose payment behavior summaries are reported GDT: PartyInternalID · CreditorParty – The party that owns a receivable from a customer. outstanding receivables due from the customer GDT: DunningCounterValue · CumulatedReceivablesAmount– Cumulative receivables total that can also be subjected to interest with a fictitious interest rate GDT: Amount · DaysOfSalesOutstandingDuration – Receivables total measured in days sales of business with the customer GDT: Duration (specification in days) · OverdueOpenItemsPercent – Percentage of the amount of all overdue open items of the total amount of all open items of the customer GDT: Percent · LastTwelveMonthsMaximumCreditExposureAmount – Highest credit exposure of the customer in the last twelve months GDT: Amount · LastTwelveMonthsSalesVolumeAmount – Sales with the customer in the last twelve months GDT: Amount · WithoutDiscountPayments – Key figures for payments of the customer where there was a complete or partial loss of cash discount (not taking cash discount can indicate poor liquidity) · WithDiscountPayments – Key figures for payments of the customer where maximum cash discount was taken (claiming cash discount can indicate sufficient liquidity) Mapping Objects No mapping objects exist for the interface. All rights reserved. Page 23 of 67 . can be used to derive the credit segment · ProductCategory – The product category of the product sold to the customer. can be used to derive the credit segment · LastPayment – Payment amount and date of last payment · OldestOpenItem – Highest open item amount with due date · MaximumLevelDunnedOpenItem – Open item with highest dunning level · DunningCounterValue – Number of dunned. can be used to derive the credit segment · SellerParty – The party that has sold a product to the customer. PUBLIC © 2014 SAP SE or an SAP affiliate company.Description This interface requests credit information about a business partner from an information provider. synchronous) If SAP Credit Management requests external credit information. The message interface consists of the message types CreditAgencyReportQuery and CreditAgencyReportResponse. SAP Credit Management can carry out scoring for the business partner. Examples are Dun & Bradstreet and SCHUFA. which represents a response to the external credit information query. Page 24 of 67 . the message interface is the outbound interface. The interface has two message types: · CreditAgencyReportQuerystructures the message for requesting credit information · CreditAgencyReportResponsestructures the response message that contains the required credit information Message Interfaces CreditAgencyReportQuery_Out (outbound. payment reliability. Data Types CreditAgencyReportQuery The figure below shows the data type CreditAgencyReportQueryMessage that contains an entry of the data type MessageHeader and an entry of the data type CreditAgencyReportQuery. CreditAgencyReportResponse This message type consists of the data type CreditAgencyReportResponseMessage. An information provider is a company that provides business information about private or business relationships of other parties. All rights reserved. With the information received about the estimated creditworthiness. The query to the external information system takes place synchronously. and other financial information. in particular with regard to their creditworthiness. Message Types CreditAgencyReportQuery This message type consists of the data type CreditAgencyReportQueryMessage. which represents a message for requesting external credit information. TaxJurisdictionCode. DepartmentName.The data type MessageHeadercontains the following elements: · ID – Unique identifier for the message GDT: MessageID · ReferenceID – Unique identifier for the response message delivered in CreditAgencyReportResponse GDT: MessageID · CreationDateTime – Date and time of creation of the message GDT: DateTime · SenderParty – Sender of the message ( SAP Credit Management system) GDT: BusinessDocumentMessageHeaderParty · RecipientParty – Recipient of message GDT: BusinessDocumentMessageHeaderParty The data type CreditAgencyReportQuerycontains the following elements: · ReasonCode – Reason for the query GDT: CreditAgencyReportQueryReasonCode · DebtorParty – The party (debtor) about whom credit information is to be given DebtorParty contains the following elements: ¡ StandardID – Standardized identifier for the party to be checked GDT: PartyStandardID ¡ CreditAgencyID – Identifier for the party to be checked. assigned by the information provider GDT: PartyPartyID ¡ Address – Address of the party to be checked GDT: Address. Office. if the party to be checked is a natural person GDT: Date · Service– Type and scope of the service required from the information provider Service contains the following elements: ¡ CreditAgencyID – Identifier of the required service assigned by the information provider (according to the service catalog of the information provider) GDT: ProductPartyID ¡ LanguageCode – Language in which the results of the service requested are to be delivered GDT: LanguageCode CreditAgencyReportResponse The figure below shows the data type CreditAgencyReportResponseMessage that contains an entry of the data type MessageHeader and an entry of the data type CreditAgencyReportResponse. TimeZoneDifferenceValue. All rights reserved. PUBLIC © 2014 SAP SE or an SAP affiliate company. Page 25 of 67 . GeoCoordinates are not used ¡ IncorporationDate – Incorporation date of a company. whereby FunctionalTitleName. if the party to be checked is a company GDT: Date ¡ BirthDate – Date of birth of a natural person. PUBLIC © 2014 SAP SE or an SAP affiliate company. ● CreditManagementAccountByIDResponseMessage structures the response message. All rights reserved. Page 26 of 67 . The CreditAgencyReportResponse data type contains the following elements: · CreationLog – A summary of information about the creation of credit information · DebtorParty – Summary of the information about the party about whom credit information is to be given · CreditRating – Rating value for a party determined by the information provider and valid for a specific period · CreditRating – Rating value for a party determined by the information provider and valid for a specific period · Scoring – Result of the rating of a party with regard to its creditworthiness using a scorecard specified by an information provider · CreditLimit – Credit limit valid for a party for a specific period · LegalEvent – A legal event concerning the creditworthiness of a party Mapping Objects No mapping objects exist for the interface. SAP A2A Interface CreditManagementAccountByIDQuery_In Description This interface is used to transfer the data from SAP Credit Management .For the elements of the data type MessageHeader see the data type CreditAgencyReportQuery above. It uses the following message types: ● CreditManagementAccountByIDQueryMessage structures the message for requesting the credit data. Message Types CreditManagementAccountByIDQuery This message type contains the data type CreditManagementAccountByIDQueryMessage that represents a message for requesting credit data. The data type MessageHeader contains the following elements: ● ID – Identifier for the message GDT: MessageID ● ReferenceID – Identifier for the response message delivered in CreditAgencyMonitorResponse GDT: MessageID ● CreationDateTime – Date and time of creation of the message GDT: DateTime ● SenderParty – Sender of the message (querying system) GDT: BusinessDocumentMessageHeaderParty ● RecipientParty – Recipient of message GDT: BusinessDocumentMessageHeaderParty The Selection data type contains the following elements: ● DebtorPartyInternalID – Party (debtor) about whom information is to be given GDT: PartyInternalID ● CreditSegmentInternalId – Credit segment in SAP Credit Management GDT: CreditSegmentInternalID LanguageCode – Language in which the results of the service requested are to be delivered GDT: LanguageCode CreditManagementAccountByIDResponseMessage The data type CreditManagementAccountByIDResonseMessage contains one entry of the data type MessageHeader. Data Types CreditManagementAccountByIDQueryMessage The data type CreditManagementAccountByIDQueryMessage contains one entry of the data type MessageHeader. synchronous) If SAP Credit Management requests credit data. and one entry of the data type Log.Message Interfaces CreditManagementAccountByIDQuery_In (outbound. The message interface consists of the message types CreditManagementAccountByIDQuery and CreditManagementAccountByIDResponse. PUBLIC © 2014 SAP SE or an SAP affiliate company. CreditManagementAccountByIDResponse This message type contains the data type CreditManagementAccountByIDResponseMessage that represents a response to the request for credit data. The response to the query system is synchronous. All rights reserved. one entry of the data type CreditManagementAccount. For the elements of the data type MessageHeader see the data type CreditManagementAccountByIDQueryMessage above. Page 27 of 67 . the message interface is the outbound interface. and a language key. one entry of the data type Selection. Page 28 of 67 . SAP A2A Interface CreditManagementAccountChangeNotification_In Description This interface is used to change specific credit data. PUBLIC © 2014 SAP SE or an SAP affiliate company. ● CommitmentTotal – Credit exposure of the business partner Mapping Objects No mapping objects exist for the interface. All rights reserved.Data type Log: Series of log messages about the processing of the query GDT: Log The CreditManagementAccount data type contains the following elements: ● DebtorPartyInternalID – Identification of the party GDT: PartyInternalID ● CreditSegmentInternalId – Credit segment in SAP Credit Management GDT: CreditSegmentInternalID ● CreditSegmentDescription – Name of the credit segment GDT: MEDIUM_Description ● CreditWorthinessCheckingRuleCode – Rule for scoring GDT: CreditWorthinessCheckingRuleCode ● CreditWorthinessCheckingSchemeCode – Rule for the credit check GDT: CreditWorthinessCheckingSchemeCode ● SpecialAttentionRequiredIndicator – Special attention GDT: Indicator ● BlockedIndicator – Business partner is blocked in SAP Credit Management GDT: Indicator ● BlockingReasonCode – Block reason GDT: CreditBlockingReasonCode ● BlockingReasonCodeDescription – Description of the block GDT: MEDIUM_Description ● CreditRating – Rating value for a party determined by the information provider and valid for a specific period CreditRating is categorized by the data type CreditManagementCreditAccountRating and contains the following elements: ○ Code – Coded display of the score value GDT: CreditRatingCode ○ ValidityPeriod – Validity period of the score value GDT: UPPEROPEN_DatePeriod ● CreditRiskClass – Payment default risk determined by SAP Credit Management and valid for a specific period CreditRiskClass is categorized by the data type CreditManagementAccountCreditRiskClass and contains the following elements: ○ Code – Coded display of the risk class GDT: CreditRiskClassCode ○ ValidityPeriod – Validity period of the risk class GDT: UPPEROPEN_DatePeriod ● CreditLimitAmount – Amount of the credit GDT: Amount ● CreditLimitValidityPeriod – Validity period of the credit GDT: UPPEROPEN_DatePeriod ● CreditExposure – Current utilization of the credit limit of the business partner CreditExposure is categorized by the data type CreditManagementAccountCreditExposure and contains the following elements: ○ Amount – Amount of the utilization GDT: Amount ○ Percent – Utilization in percent GDT: Percent ○ DynamicCheckHorizonEndDate – End date of the credit horizon GDT: Date ● PaymentBehaviourSummary – Payment behavior of the business partner For more information about PaymentBehaviourSummary. see SAP A2A Interface CreditPaymentBehaviourSummaryNotification_In. All rights reserved. Message Types CreditManagementAccountChangeNotification This message type uses the data type CreditManagementAccountChangeNotificationMessage. SAP A2A Interface CreditWorthinessCriticalPartiesQuery_In Description This interface describes business partners that are rated as critical with regard to their creditworthiness.Message Interfaces CreditManagementAccountChangeNotification_In (inbound. The message interface uses of the message type CreditManagementAccountChangeNotification. The interface consists of the following actions: · Sending a query (CreditWorthinessCriticalPartiesQuery) · Receiving a response that contains a list of critical business partners (CreditWorthinessCriticalPartiesResponse) PUBLIC © 2014 SAP SE or an SAP affiliate company. see SAP A2A Interface CreditManagementAccountByIDQuery_In. The CreditManagementAccountChange data type contains the following elements: ● CreditSegmentInternalId – Credit segment in SAP Credit Management GDT: CreditSegmentInternalID ● DebtorInternalID – Customer whose data is to be changed GDT: DebtorInternalID ● BlockedIndicator – Indicates whether the credit account is blocked or not GDT: Indicator ● BlockingReasonCode – Reason for the block in SAP Credit Management GDT: CreditBlockingReasonCode ● SpecialAttentionRequiredIndicator – Indicates whether this credit account requires special attention GDT: Indicator Mapping Objects No mapping objects exist for the interface. Page 29 of 67 . Data Types CreditManagementAccountChangeNotificationMessage The data type CreditManagementAccountChangeNotificationMessage contains one entry of the data type MessageHeader and one entry of the data type CreditManagementAccountChange. asynchronous) If an application wants to change the credit data. the message interface is the inbound interface to SAP Credit Management . For the elements of the data type MessageHeader. synchronous) If an application requests a list of the critical business partners. Message Interfaces CreditWorthinessCriticalPartiesQuery_In (inbound. All rights reserved. sends a query with a number of business partners to SAP Credit Management . SAP Credit Management provides a negative customer list with business partners with negative ratings. for example. for example. the message interface is the inbound interface to SAP Credit Management . which represents a message for querying the quantity of critical business partners. The message interface uses the message types CreditWorthinessCriticalPartiesQuery and CreditWorthinessCriticalPartiesResponse. Message Types CreditWorthinessCriticalPartiesQuery This message type consists of the data type CreditWorthinessCriticalPartiesQueryMessage. The list of critical partners is delivered to the querying system synchronously via the interface. An application. Data Types CreditWorthinessCriticalPartiesQuery The figure below shows the data type CreditWorthinessCriticalPartiesQueryMessage that contains one or more entries of the data type CreditWorthinessCriticalPartiesQuery. CreditWorthinessCriticalPartiesResponse This message type uses the data type CreditWorthinessCriticalPartiesMessage that represents a response to the query regarding the quantity of critical partners. Page 30 of 67 . PUBLIC © 2014 SAP SE or an SAP affiliate company. Contract Accounts Receivable and Payable (FI-CA).These interfaces are motivated by the necessity of providing Financial Accounting with a list of business partners whose score is negative. The data type CreditWorthinessCriticalPartiesResponsecontains the following elements: · CreditSegmentInternalId – Credit segment in SAP Credit Management GDT: CreditSegmentInternalID · DebtorParty – Critical business partner · CreditorParty – Not used in SAP Credit Management · SellerParty – Not used in SAP Credit Management · ProductCategory – Not used in SAP Credit Management Mapping Objects No mapping objects exist for the interface. All rights reserved.The data type CreditWorthinessCriticalPartiesQuerycontains the following elements: · CreditSegmentInternalId – Credit segment in SAP Credit Management GDT: CreditSegmentInternalID · DebtorPartyInterval – Business partner interval to be checked for critical partners · CreditorParty – Not used in SAP Credit Management · SellerParty – Not used in SAP Credit Management · ProductCategory – Not used in SAP Credit Management CreditWorthinessCriticalPartiesResponse The figure below shows the data type CreditWorthinessCriticalPartiesReponseMessage that contains one or more entries of the data type CreditWorthinessCriticalPartiesResponse. PUBLIC © 2014 SAP SE or an SAP affiliate company. Page 31 of 67 . SAP A2A Interface CreditWorthinessChangeInformation_Out Description CreditWorthinessChangeInformation is a message that contains information about changes to the creditworthiness of a business partner. Page 32 of 67 . Data Types CreditWorthinessChangeMessage The figure below shows the data type CreditWorthinessChangeMessage that contains one or more entries of the data type CreditWorthinessChange. Message Types CreditWorthinessChangeInformation This message type uses the data type CreditWorthinessChangeMessage that represents a message with changed information from SAP Credit Management . asynchronous) If an event that is to be published externally is triggered in SAP Credit Management . Message Interfaces CreditWorthinessChangeInformation_Out (outbound. All rights reserved. Once a credit limit or rating check has been performed for a connected system. the current and earlier rating values of a business partner are sent or messages from the creditworthiness check. such as the reason for a negative result. The data type CreditWorthinessChange contains the following elements: ● CreditSegmentInternalId – Credit segment in SAP Credit Management GDT: CreditSegmentInternalID ● ReasonCode – Reason for the change ● CheckingDescription – Description of the flow of a creditworthiness check GDT: Description ● DebtorParty – Description of the customer whose payment behavior summaries are reported GDT (InternalId): PartyInternalID ● CreditorParty – Not used in SAP Credit Management ● SellerParty – Not used in SAP Credit Management ● ProductCategory – Not used in SAP Credit Management ● Rating – Valid score of a business partner determined by SAP Credit Management and valid for a specific period ● RiskClass – The risk of non-payment determined by SAP Credit Management and valid for a specific period. The message interface uses the message type CreditWorthinessChangeInformation. For example. can be connected to closing ● CreditLimit – Credit limit valid for a business partner for a specific period ● CreditExposure – Existing credit exposure of a business partner valid for a specific period ● DebtorPartyBlockedIndicator – Specification of whether the business partner is blocked in SAP Credit Management GDT: Indicator PUBLIC © 2014 SAP SE or an SAP affiliate company. interested applications that are connected to SAP Credit Management are provided with new information. the message interface is the outbound interface. SAP Component Interface FICARatingReplicate Description The asynchronous interfaces FICARatingReplicateQuery and FICARatingReplicateResponse enable you to exchange the following creditworthiness values: · Score from SAP Credit Management · Creditworthiness from Contract Accounts Receivable and Payable (FI-CA creditworthiness) The FI-CA creditworthiness is transferred to SAP Credit Management by means of the interface FICARatingReplicateQuery. the value of the score is then transferred to FI-CA by means of the interface FICARatingReplicateResponse. Page 33 of 67 . see SAP Note 813285. Message Types FICARatingReplicateQuery PUBLIC © 2014 SAP SE or an SAP affiliate company. the message interface is the inbound interface to SAP Credit Management . Use No recipients of events that are sent from SAP Credit Management are delivered with the standard.● BlockingReasonCode – Reason for the block in SAP Credit Management GDT: CreditBlockingReasonCode ● SpecialAttentionIndicator – Specification of whether the business partner should be subject to special attention GDT: Indicator Mapping Objects No mapping objects exist for the interface. asynchronous) If Contract Accounts Receivable and Payable sends the FI-CA creditworthiness. The message interface consists of the message type FICARatingReplicateResponse. There. asynchronous) This message interface is used when SAP Credit Management informs Contract Accounts Receivable and Payable about the score. For an example implementation of a customer-specific module that receives and processes events in an SAP system connected to SAP Credit Management by XI. The message interface consists of the message type FICARatingReplicateQuery. Message Interfaces FICARatingReplicateQuery_In (inbound. FICARatingReplicateResponse_Out (outbound. the calculation of the score can be triggered. All rights reserved. the ‘result’ is taken to mean the key figures that you want to use to calculate your score.com/xi/FSCM/Global PUBLIC © 2014 SAP SE or an SAP affiliate company. Two interface objects of the External Definition type into which you load the interface description for the query and response of the information provider . Data Types FICARatingReplicateQuery The FICARatingReplicateQuery data type contains the following elements: · ProcedureCode – Rating procedure in SAP Credit Management · DebtorParty – Business partner with creditworthiness rating DebtorPartycontains the following elements: ¡ InternalID – Business partner number in Contract Accounts Receivable and Payable ¡ RatingCode – FI-CA creditworthiness value FICARatingReplicateResponse The FICARatingReplicateResponse data type contains the following elements: · DebtorParty – Business partner with creditworthiness rating DebtorPartycontains the following elements: ¡ InternalID – Business partner number in Contract Accounts Receivable and Payable ¡ RatingCode – Value of score in SAP Credit Management Mapping Objects Nointerface mapping is required since the interfaces in Contract Accounts Receivable and Payable use the same data types as the interfaces in SAP Credit Management . For each rating procedure. You must be able to map the fields of the provider’s interface on the XI interface of SAP Credit Management . · You have a description of the information provider's interface in the format of a WSDL-XSD or DTD file. Define (for example. For more information on the XI interfaces. Page 34 of 67 . see SAP B2B Interface CreditAgencyReport. The mapping can either be handled with XSL transformations or with message mapping objects that you graphically define in the Integration Builder. call up the Integration Repository and create the following objects in a separate software component: a. you should make an entry for each product. Prerequisites · You are a customer of the external information provider. If you wish to use different products of an information provider (for instance. Define how the interface of SAP Credit Management is to be mapped with the interface of the information provider. b. proceed as follows: a. FICARatingReplicateResponse This message type consists of the data type FICARatingReplicateResponse that represents a message for transmitting the score of a business partner. information of various scope). To import the information from other systems either manually with an import button or automatically.) Consequently.com/xi/FSCM/Global to the inbound interface of the information provider § One for the mapping of the output interface of the information provider to the message type CreditAgencyReportResponse in the namespace http://sap. In the Integration Builder of your XI server. 2. (The information of an information provider generally contains a large number of fields and key figures. A message interface with the inbound und synchronous attributes and external message type where you reference the external definitions that you have created. 3. Procedure 1. Make an entry for the external information provider in the Implementation Guide of Credit Management under Master Data → Define Rating Procedure . you should define the different forms of results of the query. Connecting External Information Providers Use You can use the credit information received from external information providers for calculating the score. · The external information provider provides an interface for data queries in the Internet. All rights reserved.This message type consists of the data type FICARatingReplicateQuery that represents a message for transmitting the FI-CA creditworthiness of a business partner. you first have to connect and configure the XI landscape of the information providers in question. If you wish to use XSL transformations. initially as local files) two XSL transformations: § One for the mapping of message type CreditAgencyReportQuery in the namespace http://sap. c. You can also fill other fields of the request. e. 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 . connect your FI-AR system to the SAP Credit Management system via XI interfaces. 4. Result In the Credit Profile screen of the business partner’s master data transaction. such as the address data of the business partner. you enter the product identifier that the information provider needs to identify the required product (for instance. the interface is CreditAgencyReportQuery_Out in the namespace http://sap. In the Integration Builder of your XI server. In the Integration Repository of you software component. receiver and receiver interface. For more information. create two mapping objects of the Message-Mappingtype. proceed as follows: § .com/xi/FSCM/Global.com/xi/FSCM/Global.Pack both files into an archive file of type ZIP. you can now import external credit information by entering the relevant rating procedure. and the mapping programs in the imported archive in step 3b. in other words to derive the correct recipient from the content of the identifier.0 § Message protocol = XI 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 scope of the information). All rights reserved. the target interface that you created in step 2b. 6. The recipient is the business service from the previous step. In method FILL_QUERY. Prerequisites You have created the business systems concerned in the System Landscape Directory and are familiar with the configuration environment of the Integration Builder . create a mapping object of the Imported Archive type. In the Integration Repository of your software component. If you wish to connect more than one information provider. selecting the entry and pressing the Import Data pushbutton. You may use this identifier in the XI configuration to configure the receiver determination. create an interface mapping with the outbound interface CreditAgencyReportQuery_Out in the namespace of http://sap. 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. In this method.com/xi/FSCM/Global the target interface that you created in step 2b. Each information requested is subject to costs. see SAP A2A-Interfaces CreditCommitment_In und CreditCommitment_Out and SAP A2A-Interface CreditPaymentRecord_In. b. ¡ A receiver agreement in which you determine the communication channel HTTP for the combination of sender. In SAP Credit Management . Connecting Accounts Receivable Accounting ERP 2005 Use To update items and payment behavior summaries from Accounts Receivable Accounting (FI-AR) with Release mySAP ERP 2005 in SAP Credit Management . You can influence this behavior by implementing the method READ_RESPONSE of the Business Add-In UKM_CREDIT_INFO. 5. § The target message is of the external query message type. located in the External Definition that you created in step 2a. sender interface and receiver. Page 35 of 67 . 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 ). Assign the fields that are to be mapped together to each other using drag and drop. into which you load the local archive file that you created in step 3a. For more information on the relevant XI interfaces. 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. § The outbound message of the first message mapping has the message type CreditAgencyReportQuery in the namespace http://sap. d. ¡ An interface determination in which you determine the receiver interface for the combination of sender. define a business service for each one and specify the conditions for selecting each receiver in the receiver determination (see also step 5). 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. you can enter the reason for the request (legal requirement in Germany) and the language in which the information is provided. Enter again the interface from step 3c and the interface mapping from step 3d.com/xi/FSCM/Global. In the Integration Repository of your software component. see the SAP Library under SAP NetWeaver Library → Key Functional Areas of SAP NetWeaver → Key Functional Areas of PUBLIC © 2014 SAP SE or an SAP affiliate company. If you wish to use a Message-Mapping object. and the message mappings in the preceding step.com/xi/FSCM/Global. In the Integration Repository of your software component. create an interface mapping with the outbound interface CreditAgencyReportQuery_Out in the namespace of http://sap.. The minimum requirement is to implement method FILL_QUERY to be able to address an information provider.. see the SAP Library under SAP NetWeaver Library → Key Functional Areas of SAP NetWeaver → Key Functional Areas of PUBLIC © 2014 SAP SE or an SAP affiliate company. connect your FI-AR system to the XI interfaces of the Credit Management system via RFC adapter. The sender is the FI-AR system and the receiver is the SAP Credit Management system. Connecting Accounts Receivable Accounting ERP 2004 Use To update items and FI summaries from Accounts Receivable Accounting (FI-AR) Release mySAP ERP 2004 in SAP Credit Management . Integrate the sender interface CreditCommitmentNotification_Out from the namespace http://sap. Using this connection.com/xi/FSCM/Global via the receiver communication channel XIChannel.com/xi/FSCM/Global via the receiver communication channel XIChannel.70 or 4.6C Use To update items and FI summaries from Accounts Receivable Accounting (FI-AR) Release SAP R/3 Enterprise 4. Using this connection. Prerequisites You have created the business systems concerned in the System Landscape Directory and are familiar with the configuration environment of the Integration Builder . you can now update FI summaries from Accounts Receivable Accounting to SAP Credit Management . Using this connection.com/xi/FSCM/Global via the receiver communication channel XIChannel. the use of some terms from SAP Credit Management has changed. Note the differences in terminology between applications with different releases – from mySAP ERP 2005. For more information. For more information.70 or SAP R/3 4. Using this connection. 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 on the relevant XI interfaces. you can now update liability information from Accounts Receivable Accounting to SAP Credit Management . see Terminology Changes from mySAP ERP 2005 .Process Integration → SAP NetWeaver Exchange Infrastructure → Design and Configuration Time → Integration Builder and C onfiguration . Integrate the sender interface CreditCommitmentNotification_Out from the namespace http://sap. Integrate the sender interface CreditPaymentRecordNotification_Out from the namespace http://sap. Procedure 1. connect your FIAR system to the SAP Credit Management system via XI interfaces. you can now update payment behavior summaries from Accounts Receivable Accounting to SAP Credit Management .com/xi/PI/FIN/Operational/Global with the receiver interface CreditPaymentRecordNotification_In from the namespace http://sap.6C in SAP Credit Management . For more information on the relevant XI interfaces. see SAP A2A-Interfaces CreditCommitment_In und CreditCommitment_Out and SAP A2A-Interface CreditPaymentRecord_In. For more information. All rights reserved.com/xi/PI/FIN/Operational/Global with the receiver interface CreditCommitmentNotification_In from the namespace http://sap. Procedure 1. For a “How to” guide with screenshots. you can now update commitment information from Accounts Receivable Accounting to SAP Credit Management . 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 C onfiguration . 2. The sender is the FI-AR system and the receiver is the SAP Credit Management system. The sender is the FI-AR system and the receiver is the SAP Credit Management system. see the attachment to SAP Note 794772. Page 36 of 67 .com/xi/PI/FIN/Operational/Global with the receiver interface CreditCommitmentNotification_In from the namespace http://sap. Integrate the sender interface CreditPaymentBehaviourSummaryNotification_Out from the namespace http://sap. see SAP A2A-Interfaces CreditCommitment_In und CreditCommitment_Out and SAP A2A-Interface CreditPaymentRecord_In.com/xi/FSCM/Global via the receiver communication channel XIChannel. Connecting Accounts Receivable Accounting 4. 2.com/xi/PI/FIN/Operational/Global with the receiver interface CreditPaymentBehaviourSummaryNotification_In from the namespace http://sap. The sender is the FI-AR system and the receiver is the SAP Credit Management system. Process Integration → SAP NetWeaver Exchange Infrastructure → Design and Configuration Time → Integration Builder and C onfiguration .com/xi/FICA/Global with the receiver interface CreditCommitmentNotification_In from the namespace http://sap. Prerequisites You have created the business systems concerned in the System Landscape Directory and are familiar with the configuration environment of the Integration Builder . SAP A2A Interface CreditWorthinessQuery_In. 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. The receiver is the SAP Credit Management system. Integrate the sender interface FICARatingReplicateQuery_Out from the namespace http://sap. 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 37 of 67 .com/xi/FSCM/Global with the receiver interface CreditCommitmentQuery_In from the namespace http://sap. Procedure 1. the use of some terms from SAP Credit Management has changed. The sender is the FI-AR system and the receiver is the SAP Credit Management system. SAP IST 6. SAP A2A Interface CreditPaymentBehaviourSummaryNotification_In. 2. you have to integrate your FI-CA system with the XI interfaces of the Credit Management system. you can now update FI summaries from Accounts Receivable Accounting to SAP Credit Management . For more information. 3. you can now update liability information from Accounts Receivable Accounting to SAP Credit Management .com/xi/FICA/Global via the receiver communication channel XIChannel . see Terminology Changes from mySAP ERP 2005 . b. Note the differences in terminology between applications with different releases – from mySAP ERP 2005. for example). Integrate the sender interface FICARatingReplicateResponse_Out from the namespace http://sap. Using this connection.com/xi/FICA/Global with the receiver interface FICARatingReplicateQuery_In from the namespace http://sap. Using this connection you can query credit exposure information from SAP Credit Management in Contract Accounts Receivable and Payable (commitment query). The receiver is the SAP Credit Management system.com/xi/FSCM/Global with the receiver interface CreditPaymentRecordNotification_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel XIChannel. Using this connection you can update payment behavior summaries from Contract Accounts Receivable and Payable in SAP Credit Management . Procedure 1.com/xi/FICA/Global with the receiver interface CreditPaymentBehaviourSummaryNotification_In from the namespace http://sap. PUBLIC © 2014 SAP SE or an SAP affiliate company.com/xi/FSCM/Global via the receiver communication channel XIChannel . All rights reserved. The sender is the FI-CA system. You can access the XI content for Contract Accounts Receivable and Payable as a patch on SAP Service Marketplace under the respective industry solution (for example. The sender is the SAP Credit Management system. Integrate the sender interface CreditPaymentBehaviourSummaryNotification_Out from the namespace http://sap. Using this connection. SAP A2A Interface CreditWorthinessCriticalPartiesQuery_In. 2. The receiver is the SAP Credit Management system. The sender is the FI-AR system and the receiver is the SAP Credit Management system. The receiver is the FI-CA system.com/xi/FSCM/Global via the receiver communication channel XIChannel . 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.com/xi/FSCM/Global via the receiver communication channel XIChannel. Using this connection. For more information about the relevant XI interfaces. Make sure that the XI content of the software components FI-CA and FSCM is installed in the Integration Repository of your XI server.com/xi/FSCM/Global with the receiver interface FICARatingReplicateResponse_In from the namespace http://sap. Connecting Contract Accounts Receivable and Payable as of SAP ERP 6. see SAP A2A Interfaces CreditCommitment_In and CreditCommitment_Out. SAP Component Interface FICARatingReplicate. 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. The sender is the FI-CA system. you can: a.00 with SAP Credit Management . Using this connection you can update credit exposure information from Contract Accounts Receivable and Payable in SAP Credit Management .00). The sender is the FI-CA system. Integrate the sender interface CreditCommitmentNotification_Out from the namespace http://sap. 5.0 Use To integrate Contract Accounts Receivable and Payable (FI-CA) as of Release SAP ERP 6.com/xi/FSCM/Global with the receiver interface CreditCommitmentNotification_In from the namespace http://sap. For more information. and SAP A2A Interface CreditWorthinessChangeInformation_Out.com/xi/FICA/Global via the receiver communication channel XIChannel . Import the FI-CA creditworthiness from Contract Accounts Receivable and Payable to SAP Credit Management . 4.com/xi/FSCM/Global via the receiver communication channel XIChannel . Integrate the sender interface CreditCommitmentQuery_Out from the namespace http://sap. Import the score from SAP Credit Management to Contract Accounts Receivable and Payable . Using this connection you can query liability information from SAP Credit Management in Contract Accounts Receivable and Payable (commitment query). 7. 5. Integrate the sender interface CreditWorthinessQuery_Out from the namespace http://sap. Integrate the sender interface CreditCommitmentQuery_Out from the namespace http://sap. Make sure that the XI content of the software components FI-CA and FSCM is installed in the Integration Repository of your XI server. Integrate the sender interface CreditPaymentRecordNotification_Out from the namespace http://sap. Using this connection you can update FI summaries from Contract Accounts Receivable and Payable in SAP Credit Management . The sender is the FI-CA system. Using this connection. you can: a. Using this connection. 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.72 Use To integrate Release 4. For more information about the relevant XI interfaces. The sender is the SAP Credit Management system. Using this connection you can update liability information from Contract Accounts Receivable and Payable in SAP Credit Management . You can use this connection to transfer information about events from SAP Credit Management to Contract Accounts Receivable and Payable (changes to master data.com/xi/FSCM/Global via the receiver communication channel XIChannel. 3.com/xi/FICA/Global via the receiver communication channel XIChannel. The receiver is the FI-CA system. Integrate the sender interface CreditWorthinessChangeInformation_Out from the namespace http://sap. you can transfer the FI-CA creditworthiness from Contract Accounts Receivable and Payable to SAP Credit Management . Page 38 of 67 .com/xi/FSCM/Global via the receiver communication channel XIChannel. The receiver is the SAP Credit Management system. b. The sender is the FI-CA system. 8.com/xi/FICA/Global with the receiver interface CreditCommitmentNotification_In from the namespace http://sap. Procedure 1.com/xi/FSCM/Global with the receiver interface FICARatingReplicateResponse_In from the namespace http://sap. The sender is the FI-CA system. Using this connection you can query business partners marked for special attention from Contract Accounts Receivable and Payable in SAP Credit Management .The sender is the SAP Credit Management system.com/xi/FICA/Global with the receiver interface CreditPaymentRecordNotification_In from the namespace http://sap. You can access the XI content for Contract Accounts Receivable and Payable as a patch on SAP Service Marketplace under the respective industry solution (for example SAP IS-T 4. 4. The receiver is the FI-CA system. The sender is the FI-CA system. The receiver is the SAP Credit Management system. 6. The receiver is the SAP Credit Management system. The sender is the SAP Credit Management system. Integrate the sender interface CreditCommitmentNotification_Out from the namespace http://sap.com/xi/FICA/Global with the receiver interface CreditWorthinessCriticalPartiesQuery_In from the namespace http://sap. 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 Connecting Contract Accounts Receivable and Payable 4. you have to integrate your FI-CA system with the XI interfaces of the Credit Management system. The receiver is the SAP Credit Management system.com/xi/FICA/Global with the receiver interface FICARatingReplicateQuery_In from the namespace http://sap. 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 C onfiguration .com/xi/FSCM/Global with the receiver interface CreditWorthinessChangeInformation_In from the namespace http://sap.72). The receiver is the SAP Credit Management system.72 of Contract Accounts Receivable and Payable (FI-CA) with SAP Credit Management .com/xi/FSCM/Global via the receiver communication channel XIChannel. Integrate the sender interface FICARatingReplicateResponse_Out from the namespace http://sap. The sender is the FI-CA system. for example). see: ● ● ● ● SAP SAP SAP SAP A2A A2A A2A A2A Interfaces CreditCommitment_In and CreditCommitment_Out Interface CreditPaymentRecord_In Interface CreditWorthinessCriticalPartiesQuery_In Interface 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 example). For more information.com/xi/FICA/Global with the receiver interface CreditWorthinessQuery_Out_In from the namespace http://sap. Integrate the sender interface CreditWorthinessCriticalPartiesQuery_Out from the namespace http://sap.com/xi/FICA/Global via the receiver communication channel XIChannel. Using this connection. 2. Integrate the sender interface FICARatingReplicateQuery_Out from the namespace http://sap. All rights reserved. The receiver is the FI-CA system.com/xi/FSCM/Global with the receiver interface CreditCommitmentQuery_In from the namespace http://sap.com/xi/FICA/Global via the receiver communication channel PUBLIC © 2014 SAP SE or an SAP affiliate company.com/xi/FSCM/Global via the receiver communication channel XIChannel .com/xi/FSCM/Global via the receiver communication channel XIChannel. Integrate the sender interface CreditWorthinessQuery_Out from the namespace http://sap. 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 C onfiguration . Using this connection. 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 C onfiguration . see Terminology Changes from mySAP ERP 2005 . 6. For more information. For more information. Prerequisites You have created the business systems concerned in the System Landscape Directory and are familiar with the configuration environment of the Integration Builder .com/xi/FSCM/Global via the receiver communication channel XIChannel. you can now carry out credit checks from sales orders. The sender is the Sales and Distribution (SD) system and the receiver is the SAP Credit Management system. 7. Using this connection. Connecting Sales and Distribution ERP 2005 Use You connect your SD system(s) with Release mySAP ERP 2005 with SAP Credit Management through XI interfaces to enable the following: ● Performance of credit checks from sales orders ● Update of commitments from orders or from billing documents not yet transferred to accounting For more information on the relevant XI interfaces. Using this connection. Integrate the sender interface CreditWorthinessQuery_Out from the namespace http://sap.com/xi/FICA/Global with the receiver interface CreditWorthinessCriticalPartiesQuery_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel XIChannel. Prerequisites You have created the business systems concerned in the System Landscape Directory and are familiar with the configuration environment of the Integration Builder . see SAP A2A-Interface CreditWorthinessQuery_In and SAP A2A-Interfaces CreditCommitment_In und CreditCommitment_Out. The receiver is the SAP Credit Management system. PUBLIC © 2014 SAP SE or an SAP affiliate company. 2. you can transfer the score from SAP Credit Management to Contract Accounts Receivable and Payable . The sender is the SAP Credit Management system. All rights reserved. Connecting Sales and Distribution ERP 2004 Use You connect your SD system(s) with Release mySAP ERP 2004 with SAP Credit Management through XI interfaces to enable the following: ● Performance of credit checks from sales orders ● Update of liabilities from orders or from billing documents not yet transferred to accounting For more information on the relevant XI interfaces.com/xi/FSCM/Global via the receiver communication channel XIChannel. Integrate the sender interface CreditWorthinessCriticalPartiesQuery_Out from the namespace http://sap. Using this connection you can query business partners marked for special attention from Contract Accounts Receivable and Payable in SAP Credit Management . The sender is the Sales and Distribution (SD) system and the receiver is the SAP Credit Management system. you can now update commitment information from SD (order values and values of blocked billing documents) to SAP Credit Management . For more information.com/xi/PI/FIN/Operational/Global with the receiver interface CreditWorthinessQuery_In from the namespace http://sap.com/xi/FSCM/Global via the receiver communication channel XIChannel. Note the differences in terminology between applications with different releases – from mySAP ERP 2005. the use of some terms from SAP Credit Management has changed. Integrate the sender interface CreditCommitmentNotification_Out from the namespace http://sap.XIChannel. The sender is the FI-CA system.com/xi/FICA/Global with the receiver interface CreditWorthinessQuery_Out_In from the namespace http://sap.com/xi/PI/FIN/Operational/Global with the receiver interface CreditCommitmentNotification_In from the namespace http://sap. see SAP A2A-Interface CreditWorthinessQuery_In and SAP A2A-Interfaces CreditCommitment_In und CreditCommitment_Out. The receiver is the SAP Credit Management system. The sender is the FI-CA system. Using this connection you can query credit information for a business partner from Contract Accounts Receivable and Payable in SAP Credit Management . Procedure 1. Page 39 of 67 . The receiver is the FI-CA system. com/xi/FSCM/Global via the receiver communication channel XIChannel.com/xi/FSCM/Global via the receiver communication channel XIChannel. the use of some terms from SAP Credit Management has changed.6C Use You connect your SD system(s) with Release SAP R/3 Enterprise 4.com/xi/FSCM/Global via the receiver communication channel XIChannel. you can now update liability information from SD (order values and values of blocked billing documents) to SAP Credit Management . For more information. Using this connection.1) Use You connect your CRM system(s) with SAP Credit Management through XI interfaces to enable the following: ● Performance of credit checks from CRM transactions ● Update commitments from CRM transactions or billing documents ● Display of master data from SAP Credit Management in SAP CRM CRM is connected to SAP Credit Management in a customer project solution. For more information.com/xi/FSCM/Global with the receiver interface CreditCommitmentNotification_In from the namespace http://sap. The sender is the Sales and Distribution (SD) system and the receiver is the SAP Credit Management system. you can now carry out credit checks from sales orders. 2. Note the differences in terminology between applications with different releases – from mySAP ERP 2005. Connecting Customer Relationship Management (SAP CRM 5. you can now carry out credit checks from sales orders. For a “How to” guide with screenshots. SAP A2A Interfaces CreditCommitment_In and CreditCommitment_Out.6C with SAP Credit Management via XI 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 more information on the relevant XI interfaces.70 or 4. see Terminology Changes from mySAP ERP 2005 .com/xi/FSCM/Global via the receiver communication channel XIChannel. see the attachment to SAP Note 794772. the use of some terms from SAP Credit Management has changed. see SAP A2A Interface CreditWorthinessQuery_In. The sender is the Sales and Distribution (SD) system and the receiver is the SAP Credit Management system.1 for telecommunications. Using this connection. Integrate the sender interface CreditCommitmentNotification_Out from the namespace http://sap. Integrate the sender interface CreditWorthinessQuery_Out from the namespace http://sap. and SAP A2A Interface CreditManagementAccountByIDQuery_In. Procedure 1. You have implemented SAP Note 768995. Prerequisites You have created the business systems concerned in the System Landscape Directory and are familiar with the configuration environment of the Integration Builder . Page 40 of 67 . see Terminology Changes from mySAP ERP 2005 . 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 C onfiguration . The sender is the Sales and Distribution (SD) system and the receiver is the SAP Credit Management system. Connecting Sales and Distribution 4. Using this connection.com/xi/PI/FIN/Operational/Global with the receiver interface CreditWorthinessQuery_In from the namespace http://sap. PUBLIC © 2014 SAP SE or an SAP affiliate company. The sender is the Sales and Distribution (SD) system and the receiver is the SAP Credit Management system.com/xi/PI/FIN/Operational/Global with the receiver interface CreditCommitmentNotification_In from the namespace http://sap. 2.com/xi/FSCM/Global with the receiver interface CreditWorthinessQuery_In from the namespace http://sap. 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 namespacehttp://sap. 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. An exception is SAP CRM 5. Note the differences in terminology between applications with different releases – from mySAP ERP 2005. For more information. All rights reserved.70 or SAP R/3 4. you can now update liability information from SD (order values and values of blocked billing documents) to SAP Credit Management .Procedure 1. Using this connection. For more information about the relevant XI interfaces. see SAP A2A-Interface CreditWorthinessQuery_In and SAP A2A-Interfaces CreditCommitment_In und CreditCommitment_Out. You can use this connection to display the master data from SAP Credit Management in SAP CRM.com/xi/FSCM/Global via the receiver communication channel XIChannel .com/xi/CRM/Global (CRM Release 5. All rights reserved. 2.com/xi/CRM/Global with the receiver interface CreditManagementAccountByIDQuery_In from the namespace http://sap. 3. 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 C onfiguration . you can now carry out credit checks from CRM transactions. Page 41 of 67 . Integrate the sender interface CreditManagementAccountByIDQuery_Out from the namespace http://sap. For more information about the relevant XI interfaces.com/xi/CRMFSCM/Global (CRM Release 4.com/xi/FSCM/Global via the receiver communication channel XIChannel .0 or have installed CRM 2004 Industry Add-On Edition on your CRM system with Release 4. Using this connection. For more information.com/xi/CRMFSCM/Global (CRM Release 4. Integrate the sender interface CreditWorthinessQuery_Out from the namespace http://sap.0) or http://sap.Prerequisites You are using SAP CRM 5.0) with the receiver interface CreditWorthinessQuery_In from the namespace http://sap. and the receiver is SAP Credit Management . Connecting Customer Relationship Management (SAP CRM 5. Using this connection.com/xi/FSCM/Global via the receiver communication channel XIChannel .com/xi/CRM/Global (CRM-Release 5.0 and SAP CRM 4. Integrate the sender interface CreditWorthinessQuery_Out from the namespace http://sap. see SAP A2A Interface CreditWorthinessQuery_In and SAP A2A Interfaces CreditCommitment_In and CreditCommitment_Out. 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 .1 and a release as of SAP ECC 6. you can now carry out credit checks from CRM transactions. The sender is the CRM system and the receiver is the SAP Credit Management system. Prerequisites You use CRM 5. The sender is SAP CRM. You have created the business systems concerned in the System Landscape Directory and are familiar with the configuration environment of the Integration Builder . you can now update commitment information from CRM transactions to SAP Credit Management .0. The sender is SAP CRM. and the receiver is SAP Credit Management . you can now update commitment information from CRM transactions to SAP Credit Management . 1. Procedure 1.0) or http://sap.0 Service Industries Add-On) Use You connect your CRM system(s) with SAP Credit Management through XI interfaces to enable the following: ● Performance of credit checks from CRM transactions ● Update commitments from CRM transactions or billing documents CRM is connected to SAP Credit Management in a customer project solution.0) with the receiver interface CreditCommitmentNotification_In from the namespace http://sap. Integrate the sender interface CreditCommitmentNotification_Out from the namespace http://sap.1.6 Data Replication Purpose PUBLIC © 2014 SAP SE or an SAP affiliate company.0. You have created the business systems concerned in the System Landscape Directory and are familiar with the configuration environment of the Integration Builder . 2. Using this connection.com/xi/CRM/Global with the receiver interface CreditCommitmentNotification_In from the namespace http://sap. The sender is SAP CRM. Using this connection. and the receiver is SAP Credit Management . Integrate the sender interface CreditCommitmentNotification_Out from the namespace http://sap. Procedure 1.com/xi/CRM/Global with the receiver interface CreditWorthinessQuery_In from the namespace http://sap. The sender is the CRM system and the receiver is the SAP Credit Management system.com/xi/FSCM/Global via the receiver communication channel XIChannel .com/xi/FSCM/Global via the receiver communication channel XIChannel . Copies of the master data of SAP Business Partner are then created in SAP Credit Management . and transaction data. For information about the master data in Contract Accounts Receivable and Payable. Features For information about the master data in Accounts Receivable Accounting. 1. For more information about the distribution of SAP business partners. SAP Credit Management can easily access these tables.1 Providing Business Partner Data Use The master data of SAP Credit Management is an enhancement of SAP Business Partner . Replicating Master Data of Accounts Receivable Accounting (FIAR) Use The master data required for SAP Credit Management is grouped in a separate business partner role based on SAP Business Partner .This section contains information about replicating Customizing.1. The PPO requests are available via the Post Processing Desktop (transaction MDS_PPO2) PUBLIC © 2014 SAP SE or an SAP affiliate company. Cross-Application Components → Master Data Synchronization → Synchronization Control → Synchronization Control → Activate PPO Requests for Platform Objects in Dialog Set the activation indicator for the PPO object BP. ● If you install SAP Credit Management in a system in which no business partner master records exist. for example. You can also use other technoloigy for the master data replication. For information about the master data of Customer Relationship Management . To access the Customizing of Master Data Synchronization . 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. you can use the master data synchronization of the SAP standard delivery. 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. for example. This means that where synchronization attempts fail. All rights reserved. see Replicating Master Data of Contract Accounts Receivable and Payable (FI-CA). see Replicating Master Data of Accounts Receivable Accounting (FI-AR). Cross-Application Components → General Application Functions → Postprocessing Office → Business Processes → Activate Creation of Since the Postprocessing Office (PPO) is connected via the synchronization cockpit for the master data synchronization. The system creates the credit master data as an enhancement of the existing business partner master records. 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. see the Implementation Guide (IMG) for Cross-Application Components under SAP Business Partner → Data Distribution . PPO requests where the errors are logged are written. Procedure If you use the master data synchronization of the SAP standard delivery. Integration ● If you install SAP Credit Management in a system in which business partner master records already exist.6. for example. master data. IMG activities Menu Path Comments Cross-Application Components → Master Data Synchronization → Synchronization Control → Synchronization Control → Synchronization Objects Make sure that the synchronization objects BP and CUSTOMER delivered with the standard exist. activate the the creation of postprocessign orders for the Postprocessing Orders business processes of the software component AP-MD. choose Cross-Application Components → Master Data Synchronization . your own development. see Replicating Master Data of SAP CRM. For the master data replication of customers in business partners. 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). Page 42 of 67 . because automatic replication is not possible Procedure Perform the steps in these guidelines in the sequence in which they appear. a stand-alone system with its own server. perform the following IMG activities. you can also create the SD business partner using a sample customer.1. 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 Synchronization → Customer/Vendor Integration → Business Partner Settings → Settings for Define the number assignment for both direction of the synchronization. XI Content for 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. 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 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 . see Business Partners. In the implementation. For more information about this XI interface.6. PUBLIC © 2014 SAP SE or an SAP affiliate company. To do this. Replicate the business partner data using the XI interface ABABusinessPartner. Define the business partner role categories and customer account groups to be synchronized. Procedure 1.4 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 . implement and activate the BAdI REF_CUSTOMER_XI_GET. 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 CRMOU BUPA 2100000 BUPA_OUTBOUND_BPS_MAP_ROLE_ CM CRMOU BUPA 2200000 BUPA_OUTBOUND_BPS_FILL_ISU CRMIN BUPA 0230000 BUPA_XI_MAP_NUMRANGE 2. Cross-Application Components → Master Data Synchronization → Synchronization Control → Synchronization Control → Activate Synchronization Options Cross-Application Components → Master Data Synchronization → Customer/Vendor Integration → Business Partner Settings → Settings for Activate the master data synchronization for source object BP in target object CUSTOMER and source object CUSTOMER in target object BP. For the replication of business partner master data from SAP Credit Management to FI-CA. that is. 1. 3. the business partner master records are not replicated using CRM Middleware. you have to set the export parameter E_REFERENCE_CUSTOMER to the required SD sample customers. Page 43 of 67 . 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. The business partner master data is distributed using the XI interface ABABusinessPartner.or from the Synchronization Cockpit (transaction MDS_LOAD_COCKPIT). All rights reserved. in the method GET_REF_CUSTOMER. The master data is distributed using CRM Middleware . Settings in Financial Supply Chain Management Activity Comments Master Data → Create Rule for Scoring and Credit Limit Calculation Make sure that one of the rules is selected as the default rule for new customers. 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) 1. This involves.7 Business Customizing Purpose This section contains information about the Customizing settings in each system. For this mapping. Processes → Define Events and Follow-On Processes Define these entries according to the table below.1) ● System with SAP CRM 5. role (UKM000) as well as in the Contract Partner role (MKK).1 for telecommunications. you have to make the following entries in table CRMC_BUT_CALL_FU ( Definition of Function Modules for BP Data Exchange ) in SAP ECC: Note the sequence of the table entries: Entries in table CRMC_BUT_CALL_FU Event Object Position Function Name R3IN BUPA 90005 COM_BUPA_MWX_MAP_UKM R3IN BUPA 100000 COM_BUPA_MWX_MAP_MAIN_CENT RAL 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. Define Events and Follow-On Processes Activity Event Category Follow-On Process Maintain Business Partner (MAIN) Score Invalid (S) Determine Score (EVL_RATING) Maintain Business Partner (MAIN) Score Changed (IC) Determine Risk Class (EVL_RISK_C) So that the system can create the credit segments correctly as part of a subsequent credit check. you must carry out the following IMG activities in SAP ECC.0.0 (mySAP ERP 2005) or SAP ECC 6.1. Business Customizing adjusts the company-neutral delivered functionality to the specific requirements of the company.1 CRM is connected to SAP Credit Management in a customer project solution. Procedure When the business partner is replicated from SAP CRM. You do this in the Implementation Guide for Financial Supply Chain Management by choosing Credit Management → Credit Risk Monitoring .Prerequisites You use the following systems: ● A system with FI-CA ( Telecommunications industry component) and SAP Credit Management (SAP ECC 6. the business partner is created in the Credit Mgt Business Part. Credit Limit Check → Define Check Rules Make sure that one of the check rules is selected as the default rule for new customers. for example: ● Organizational unit Customizing PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 44 of 67 . An exception is SAP CRM 5. Enhancement Package 2005. role (UKM000). The following sections of the configuration guide provide additional information to supplement the documentation in the IMG. ). call view V_TBZJ1C. it controls all credit-relevant ratings and analyses. For information about the Customizing of the individual IMG activities. The Business Partner: Task Menu screen appears. subheader UKM110 is entered. 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 Result In the master data editing for the business partner. The sections explain the relationships and background of business Customizing and should help you to adjust these to benefit your organization in the best possible way. Page 45 of 67 . the tab page Credit Profile and the button Credit Segment Data are displayed. you can now edit the credit master data of your customers. this additional information does not replace the documentation in the IMG. ■ As Subheader ID . b. Choose Business Partner → Control → Applications . ). the business partner role must be active for SAP Credit Management (UKM000 Credit Mgt Business Part. a. Activating the Business Partner Role for Credit Management Use The credit master data of your business partners is the basis of SAP Credit Management . Make sure of the following entries for BP view UKM000: ■ As calling applications.● Master data Customizing ● Process Customizing Procedure Perform the steps in these guidelines in the sequence in which they appear. set the indicator Active . the applications UKM and FS08 are entered. Choose Business Partner → Control → Screen Sequences . c. see the Implementation Guide (IMG) under Financial Supply Chain Management → Credit Management → Credit Risk Monitoring . In order for you to be able to edit the credit master data of your customers. enter BUPT with no other characters in front. On the SAP Easy Access screen. 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. Using transaction SM30. Insert the following new table entry if it does not already exist: ○ Subheader : UKM110 ○ Item : 6 ○ Active: X 3. Procedure 1. b. a. PUBLIC © 2014 SAP SE or an SAP affiliate company. choose SAP Business Partner → Business Partner → Basic Settings → Business Partner Roles → Define BP Roles . Choose Business Partner → Control → Divisibility → BP Views . 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 . You need differentiation categor 9 to enter additional information for each segment. Make sure that the screen sequence BUP001 contains the screen UKM100. If you select the role for Credit Management (UKM000 Credit Mgt Business Part. All rights reserved. 2. On the detail screen for the application UKM. In Customizing for Cross-Application Components . You can restrict the access to credit segment-independent master data of SAP Credit Management (for example. The fields of this authorization object are: ● Credit Segment ● Activity. enter the corresponding entries in view V_TP19 with transaction SM30. and negative credit events in the business partner master record. enter the corresponding entries in view V_TP19 with transaction SM30. If you have created new info types in step 1. define further info types for this info category. 10. In Business Partner Maintenance . 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 . the score) by using the authorization object for business partner roles (B_BUPA_RLT) with the role Business Partner Credit Management (UKM000). The following procedure describes the Customizing activities required in SAP Credit Management and in SAP Business Partner for Financial Services . you can now select collateral with additional info types. define further info types for this info category. 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. check whether the info types delivered for the info category Negative Credit Events are sufficient for your needs. if necessary. You can restrict the access to logs (application logs) of SAP Credit Management using the authorization object S_APPL_LOG. In Business Partner Maintenance . The fields of this authorization object are: PUBLIC © 2014 SAP SE or an SAP affiliate company. check whether the info types delivered for the info category Credit Insurance are sufficient for your needs. if necessary. 6. with the definitions ○ 01 Add or create ○ 02 Change ○ 03 Display ○ 06 Delete ○ 08 Display Change Documents ○ 43 Release The role SAP_FIN_FSCM_CR_USER is delivered with all authorizations to this authorization object. In the IMG activity Define Info Categories (UKM_INFOCAT).1. In Business Partner Maintenance . For the info category Check Exception . make additional entries here based on the existing entries. you can now select credit insurance with additional info types. you can now select negative credit events with additional info types. check exceptions. If you want to deactivate more than three check steps. SAP delivers three info types (see IMG activity Define Info Categories (UKM_INFOCAT)). 9. In the IMG activity Define Info Categories (UKM_INFOCAT). define further info types for this info category.3 Defining Authorizations Use You can control the right of access to SAP Credit Management data by assigning authorizations – separately by credit segment and activity . enter the corresponding entries in view V_TP19 with transaction SM30. For more information. If you have created new info types in step 1. You can now deactivate your own check steps using the check exceptions in the business partner master record. check whether the info types delivered for the info category Collateral are sufficient for your needs.1. 2. In the IMG activity Define Info Categories (UKM_INFOCAT). see the Credit Management System and the Implementation Guide for Credit Management under Credit Risk Monitoring → Enhancements → BAdI: Additional Attributes for the Business Partner. 7. 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. if necessary.Configuring Business Partner Additional Information Use You use credit-specific additional information to define collateral. enter the corresponding entries in view V_TP19 with transaction SM30. 1. then also: Otherwise: SAP Banking → SAP Business Partner for Financial Services → Settings for SM30 with the views V_TP19 and V_TP22 Financial Services → General Settings → Enhancement Options → Additional Information → Configure Information Type 1. 8. 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. 3.7. 4. Procedure Navigation Menu Path in SAP Customizing Implementation Guide (In Credit Management System) Financial Supply Chain Management → Credit Management → Credit Risk Transaction Code UKM_INFOCAT Monitoring → Credit Limit Check → Define Info Categories If you use SAP Banking . 5. then use transaction SM30 to make entries for your check steps in the view V_TP22 based on existing entries. If you have created new info types in step 1. Page 46 of 67 .to the authorization object F_UKM_SGMT. credit insurance. If you have created new info types in step 1. you can now deactivate more than three check steps. In Business Partner Maintenance . All rights reserved. see the documentation for this IMG activity.7. For more information. Page 47 of 67 . 2.1. SUCCESS. Table 1 Assignment Number of Follow-On Process for Table 2 Name of Follow-On Process Follow-On Process 1 Determine Credit Limit of Account EVL_LIMIT 2 Determine Credit Limit of All Accounts of Partner EVL_LIMITS 3 Determine Score EVL_RATING 4 Determine External Rating(s) EVL_EXT_RT 5 Invalidate Credit Limit of Account INV_LIMIT 6 Invalidate Credit Limit of All Accounts of Partner INV_LIMITS 7 Invalidate Score INV_RATING PUBLIC © 2014 SAP SE or an SAP affiliate company. You make these settings in the SAP Credit Management system. whether the follow-on processes assigned to this event are to be triggered or not. the following forms are relevant for object name and subobject: Object Name Subobject Meaning FIN-FSCM-CR BW-SCORING Transfer of score from BW FIN-FSCM-CR COMMITMENT Credit exposure update FIN-FSCM-CR CREDITCHECK Credit check FIN-FSCM-CR-MASS ERROR.1. INFO. with the definitions ○ 03 Display ○ 06 Delete For SAP Credit Management . All rights reserved. can be differentiated by the severity of the error Procedure You can organize the authorizations of your users as follows: Activities Authorization Restrict access to one or more credit segments F_UKM_SGMT with specified credit segment Activity Edit master data F_UKM_SGMT Display master data F_UKM_SGMT 03 Delete master data F_UKM_SGMT 06 Display change documents for master data changes F_UKM_SGMT 08 Release and reject credit limit changes/increases requested (dual control principle) F_UKM_SGMT 43 Edit and display master data of SAP Credit Management B_BUPA_RLT with the business partner role UKM000 Display and/or delete application logs of SAP Credit Management S_APPL_LOG with the object names and subobjects listed above 01 02 03 03 06 Define Events and Follow-On Processes Use Events can be linked with follow-on processes in SAP Credit Management . ERROR_BIG.4 Define Events and Follow-On Processes . The two tables below should be considered as one unit. Procedure 1. ERROR_PROG. WARNING Logs of mass changes. In Customizing for SAP Credit Management choose Credit Risk Monitoring → Processes → 1. ERROR_UPD.● Application Log Object Name ● Application Log Subobject ● Activity. They show which events can trigger follow-on processes. Events that occur in such follow-on processes can also trigger follow-on processes. you can define whether an event is to be considered – that is. STATISTICS. Dependent on the activity performed. Define the events for which the system is to trigger follow-on processes. Page 48 of 67 . All rights reserved.8 Call Business Add-In BADI 9 Set “Special Attention” Indicator SET_FLAG 10 Block Business Partner in Credit Segment SET_BLOCK 11 Perform Credit Check CRD_RECHCK 12 Check Request for Limit Change LIMIT_REQ 13 Start Workflow WF Table 2 Event Value Score Invalid IS Score Changed IC External Rating Invalid ES External Rating Changed EC Credit Limit CL Follow-On Process According to Assignment Number from Table 1 1 2 3 4 5 x x 6 8 9 10 11 12 13 x x x x x x x x x x x x x 7 x x x x x x LC x x Change LR to Credit Limit Requeste d x Credit Refused CF x x x Payment VD Behavior Summary x x x x x x Payment VP Behavior Summary : Payment Data Invalid x x x Payment VX Behavior Summary : Payment Behavior x x x x Invalid Credit Limit Changed x x x x : Dunning Data Invalid Payment VO Behavior Summary : Due Date Invalid Index Invalid Generic Event Occurred GE x x x x x x x x x x x Rule for RC Scoring and Credit Limit x x x x x x x x x x x x x x x Calculatio n Changed Risk XC PUBLIC © 2014 SAP SE or an SAP affiliate company. 0 Service Industries and Making Settings in SAP CRM 5.72 and ERP 6.70 or 4. you must also make settings for all other components that you use for the business processes of SAP Credit Management .1 For information about the Customizing of the individual IMG activities.0. The sections explain the relationships and background of business Customizing and should help you to adjust these to PUBLIC © 2014 SAP SE or an SAP affiliate company. The following sections of the configuration guide provide additional information to supplement the documentation in the IMG. see the Implementation Guide (IMG).70 or SAP R/3 4.70 or SAP R/3 4.6C: Making Settings in FI-AR 4. The following components are affected: ● Accounts Receivable Accounting (FI-AR) ○ Release mySAP ERP 2005 Making Settings in FI-AR ERP 2005 ○ Release mySAP ERP 2004 Making Settings in FI-AR ERP 2004 ○ Release SAP R/3 Enterprise 4.6C ● Industry releases 4.72 and Settings in Contract Accounts Receivable and Payable as of SAP ERP 6.00 of Contract Accounts Receivable and Payable (FI-CA) for the following solutions: ○ mySAP Insurance ○ mySAP Utilities ○ mySAP Telecommunications ○ mySAP Media ○ mySAP Public Sector (Public Sector FI-CA) ○ SAP Contract Accounts Receivable and Payable (FI-CA) See Making Settings in Contract Accounts Receivable and Payable 4.0 and SAP CRM 4. All rights reserved.6C: Making Settings in SD 4.6C ● SAP Customer Relationship Management (CRM) : See Settings in SAP CRM 5.Class Changed Limit UC Utilization Changed Limit x UU x Limit UD Utilization x x x x x x x x x x Utilization Exceeds 100% x x Below 100% Again Payment VC x x x x x x x x x x x x Behavior Summary Changed Check TC Procedure Changed Error CE x x Block Set BL in Credit Managem ent x x Special Attention Indicator Set x x during Credit Exposure or Commitm ent Update SP Process Integration with SAP Systems In addition to the settings in SAP Credit Management . ● Sales and Distribution (SD) ○ Release mySAP ERP 2005 Making Settings in SD ERP 2005 ○ Release mySAP ERP 2004 Making Settings in SD ERP 2004 ○ Release SAP R/3 Enterprise 4. Page 49 of 67 .70 or 4. this additional information does not replace the documentation in the IMG. The payment behavior summary is determined from the modules delivered with the standard. set the indicator Consideration for Credit Limit . You integrate FI-AR and SAP Credit Management by means of implementations of Business Add-Ins (BAdIs) and IMG activities.7. and Replicating Master Data from Accounts Receivable Accounting (FI-AR). 1. you have to make the following settings. If you want to perform this credit check. In the implementation. For more information. 2. you must also integrate your FI-AR system with SAP Credit Management using XI interfaces (see configuration step Connecting Accounts Receivable Accounting ERP 2005). use the implementation of the BAdI BADI_UKM_VECTOR_CALCULATE. You have configured the business partner data for SAP Credit Management . PUBLIC © 2014 SAP SE or an SAP affiliate company. you can perform a credit check after you have entered the amount. To do this. During the update of payment behavior summaries to SAP Credit Management . 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. Implement and activate the Business Add-In UKM_R3_ACTIVATE. Procedure Navigation Menu Path in SAP Customizing Implementation Guide (in FI-AR system) Transaction Code Enterprise Structure → Definition → Financial Accounting → Define Credit Control Area Enterprise Structure → Assignment → Financial Accounting → Assign Company Code to Credit Control Area Financial Supply Chain Management → Credit Management → Integration with Accounts Receivable Accounting and Sales and Distribution → Integration with Accounts Receivable Accounting → Define Credit Segment Financial Supply Chain Management → Credit Management → Integration with Accounts Receivable Accounting and Sales and Distribution → Integration with Accounts Receivable Accounting → Assign Credit Control Area and Credit Segment Financial Supply Chain Management → Credit Management → Integration with Accounts Receivable Accounting and Sales and Distribution → Integration with Accounts Receivable Accounting → Define Reconciliation Accounts without Credit Management Update Financial Accounting → Accounts Receivable and Accounts Payable → Business OBL3 Transactions → Postings with Alternative Reconciliation Account → Other Special General Ledger Transactions → Create List for Special General Ledger Settings for Credit Exposure Update 1. the fields of the outbound XI interface of FI-AR are determined according to the following rules: ○ Business Partner Number = Customer ○ Credit Segment = Segment assigned to the credit control area ○ Credit Exposure Category = 200 You can influence this behavior by implementing the method FILL_FIELDS of the Business Add-In UKM_FILL. You can execute these steps independently of one another and in any order. change the message type of message UKM_PI 139. Page 50 of 67 . 2. For postings in FI-AR. navigate to the details for a special general ledger indicator and.1 Making Settings in FI-AR ERP 2005 Use To update credit exposures and payment behavior summaries from one or more FI-AR systems with release mySAP ERP 2005 in SAP Credit Management . Prerequisites In order to use the update options specified.2. 4. All rights reserved. in the properties. Select the credit-relevance of special general ledger indicators for which you require a credit exposure update (optional). During the update of open items to SAP Credit Management . Additional Settings for Updating Payment Behavior Summaries (in original Credit Management (FI-AR-CR)) 1. see Providing Business Partner Data. In the standard the credit check is not performed. If you want to determine further key figures or use other algorithms. set the export parameters E_ACTIVE_FLAG and E_ERP2005 to X in the method SET_ACTIVE. the fields of the outbound XI interface of FI-AR are determined according to the following rules: ○ Business Partner Number = Customer ○ Credit Segment = Segment assigned to the credit control area 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.1. from the special general ledger list. 3.documentation in the IMG. However. in SAP Credit Management You can influence this behavior by implementing the method FILL_FIELDS of the Business Add-In UKM_FILL. the fields of the outbound XI 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. Select the credit-relevance of special general ledger indicators for which you require a liability update (optional). 2.70 or 4. Additional Settings for Updating FI Summaries (in original Credit Management (FI-AR-CR)) 1. you currently integrate FI-AR and SAP Credit Management via implementations of Business Add-Ins (BAdIs) and via some IMG activities of the PUBLIC © 2014 SAP SE or an SAP affiliate company. During the update of open items to SAP Credit Management . in the properties. with transaction FD32 (Credit Management). 3. To do this.6C in SAP Credit Management . define a credit control area. you have to make the following settings. For more information about how to calculate the key figure DSO ( Days of Sales Outstanding ) in FI-AR and how to transfer it to SAP Credit Management in the FI summary. Note the differences in terminology between applications with different releases – from mySAP ERP 2005. only set the export parameter E_ACTIVE_FLAG to X in the method SET_ACTIVE. In the implementation. In Customizing. The Credit Management (FI-AR-CR) credit control area is merely a tool to enable the update of FI summaries. 3.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.1. You must have defined at least one credit control area. During the update of FI summaries to SAP Credit Management . and assign all company codes from which the FI summary key figures (for example. Implement and activate the Business Add-In UKM_R3_ACTIVATE. you currently integrate FI-AR and SAP Credit Management via implementations of Business Add-Ins (BAdIs) and via some IMG activities of the original Credit Management (FI-AR-CR). if defined and assigned to the company code. see SAP Note 800848.7. For more information. enter a master data record for each customer for which an FI summary is to be updated. go to the details for a special general ledger indicator and. Procedure Navigation Menu Path in SAP Customizing Implementation Guide (In FI-AR System) Transaction Code Enterprise Structure → Definition → Financial Accounting → Define Credit Control Area Enterprise Structure → Assignment → Financial Accounting → Assign Company Code to Credit Control Area Financial Accounting → Accounts Receivable and Accounts Payable → Business Transactions → Postings with Alternative Reconciliation Account → Other Special General Ledger Transactions → Create List for Special General Ledger OBL3 Settings for Liability Update 1.2. that is. the fields of the outbound XI interface of FI-AR are determined according to the following rules: ○ Business Partner Number = Customer ○ Credit Segment = Credit control area.70 or SAP R/3 4. you have to make the following settings. Making Settings in FI-AR 4. However. You can execute these steps independently of one another and in any order. Prerequisites ● In order to use the update options specified. dunning level. you must also integrate your FI-AR system(s) with SAP Credit Management using XI interfaces (see configuration step Connecting Accounts Receivable Accounting ERP 2004). For technical reasons. All rights reserved.1. ● You have configured the business partner data for SAP Credit Management (see Providing Business Partner Data). set the indicator Consideration for Credit Limit . otherwise initial ○ Liability Category : Set on the recipient side.2 Making Settings in FI-AR ERP 2004 Use To update liabilities and some key figures (summarized in an FI summary) from one or more FI-AR systems with release mySAP ERP 2004 to SAP Credit Management . the use of some terms from SAP Credit Management has changed. Page 51 of 67 . from the special general ledger list. oldest open item ) are to be updated to this credit control area. see Terminology Changes from mySAP ERP 2005. 2. you must also integrate your FI-AR system with SAP Credit Management using XI interfaces (see configuration step Connecting Accounts Receivable Accounting 4. the use of some terms from SAP Credit Management has changed. ○ Release SAP R/3 Enterprise 4. For more information. Specify the RFC destination for the RFC adapter of your Exchange Infrastructure. 2. 1430 Function Module UKM_DOCUMENT_PROCESS_0000144 0 6. Document POST 542 Doc.70: in method GET_RFCDEST of BAdI UKM_ITEMS_FILL ○ Release SAP R/3 4. that is. Note the differences in terminology between applications with different releases – from mySAP ERP 2005. Procedure Navigation Menu Path in SAP Customizing Implementation Guide (In FI-AR System) Transaction Code Enterprise Structure → Definition → Financial Accounting → Define Credit Control Area Enterprise Structure → Assignment → Financial Accounting → Assign Company Code to Credit Control Area Financial Accounting → Accounts Receivable and Accounts Payable → Business Transactions → Postings with Alternative Reconciliation Account → Other Special General Ledger Transactions → Create List for Special General Ledger OBL3 Settings for Liability Update 1. All rights reserved. Page 52 of 67 .70 Process Ctry Appl.6C: Method FILL_FIELDS of BAdI UKM_ITEMS_FILL_46C 5. go to the details for a special general ledger indicator and. from the special general ledger list. To do this.6C Process Ctry Appl. To influence the creation of the liabilities to be updated. set the indicator Consideration for Credit Limit . implement the following methods: ○ Release SAP R/3 Enterprise 4. the module UKM_DOCUMENT_PROCESS_00001440 must be called in this module. See SAP Note 694440 and import the transport in the attachment to this note into your system if it does not have the support package version stated in the note. Entries for Release SAP R/3 Enterprise 4. otherwise initial ○ Liability Category : Set on the receiver side. If you already use a customer-specific module for events 1430 or 1440. In transaction SM30. in the properties. Select the credit-relevance of special general ledger indicators for which you require a liability update (optional).6C: in method GET_RFCDEST of BAdI UKM_ITEMS_FILL_46C 4. see Terminology Changes from mySAP ERP 2005. You can execute these steps independently of one another and in any order. During the update of open items to SAP Credit Management . For more information. ● You have configured the business partner data for SAP Credit Management (see Providing Business Partner Data). 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. make the following entries. see SAP Note 694440. Prerequisites ● In order to use the update options specified.original Credit Management (FI-AR-CR). In transaction FIBF.70 or 4. Function Module 1430 UKM_DOCUMENT_PROCESS_0000144 0 1440 UKM_DOCUMENT_PROCESS_0000144 0 Entries for Release SAP R/3 4.70: Method FILL_FIELDS of BAdI UKM_FILL ○ Release SAP R/3 4. make the following new entries in table TRWPR: Transaction Event No. 7.6C). This Note contains up-to-date information. if defined and assigned to the company code. Function Module UKM_DOCUMENT_UPDATE Document PROJECT 094 UKM_DOCUMENT_PROJECT Document RES_CLR 016 UKM_FBRA Document POST 542 UKM_DOCUMENT_UPDATE Document PROJECT 094 UKM_DOCUMENT_PROJECT 3. in SAP Credit Management PUBLIC © 2014 SAP SE or an SAP affiliate company. You have configured the business partner data for SAP Credit Management (see Data Replication). 3.0). proceed as follows: 1. 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 Credit Management (FI-AR-CR) credit control area is merely a tool to enable the update of FI summaries. 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. In the implementation.0. see SAP Note 800848. 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 . 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. define a credit control area. For the creditworthiness from Contract Accounts Receivable and Payable to be included in the SAP Credit Management score. and enter a formula for the rating procedure FICA.6C: Method FILL_VECTOR of BAdI UKM_ITEMS_FILL_46C For more information about how to calculate the key figure DSO ( Days of Sales Outstanding ) in FI-AR and how to transfer it to SAP Credit Management in the FI summary.70: Method FILL_VECTOR of BAdI UKM_FILL ○ Release SAP R/3 4. To do this.0. and enter the rating procedure FICA. Page 53 of 67 .You can influence this behavior by implementing the method FILL_FIELDS of the Business Add-In UKM_FILL. in the method SUPPRESS_CHECK. dunning level. In Customizing.0 Use To integrate your FI-CA system with SAP Credit Management . 2. Procedure Navigation In Customizing for Contract Accounts Receivable and Payable . During the update of FI summaries to SAP Credit Management . you first have to initialize the credit exposure of the business partner. enter a master data record for each customer for which an FI summary is to be updated. 3. the FI-CA creditworthiness is saved as external credit information in the rating procedure FICA. 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 PUBLIC © 2014 SAP SE or an SAP affiliate company. 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. with transaction FD32 (Credit Management). You have to ensure these value areas via an appropriate formula for calculating the score. This rating procedure must be defined in Customizing for SAP Credit Management . oldest open item ) are to be updated to this credit control area. run report RFKK_CR_FILL_DFKKOBL_INITIALLY ( Initialization of Credit Exposure ) for all relevant business partners. In the Implementation Guide for Financial Supply Chain Management choose Credit Management → Credit Risk Monitoring → Master Data → Define Rating Procedure. and assign all company codes from which the FI summary key figures (for example. you have to make the settings described below. 2. Additional Settings for Updating FI Summaries (in original Credit Management (FI-AR-CR)) 1. For more information. The value areas of the FI-CA creditworthiness and the score are restricted to the interval from 0 to 9999. the use of some terms from SAP Credit Management has changed. You must have defined at least one credit control area. For technical reasons. Otherwise it is not possible to update the credit exposure correctly. To do this. Settings in Contract Accounts Receivable and Payable as of SAP ERP 6. whereby 0 is the best score. Note the differences in terminology between applications with different releases – from SAP ERP 6. see Terminology Changes from SAP ERP 6. Implement and activate the BAdI FSBP_BP1012_SUPR_CHK ( Control of Check of Rating Procedure against Customizing ). In Customizing for Financial Supply Chain Management choose Credit Management → Credit Risk Monitoring → Credit Limit Check → Define Formulas . set the export parameter C_SUPPRESS to X for the rating procedure FICA. All rights reserved. If you have already created productive business partners in FI-CA and subsequently activate SAP Credit Management . as a result of a dunning activity in Contract Accounts Receivable and Payable . FKK_SAMPLE_4603. FKK_SAMPLE_4602. you use the data type enhancement concept in XI. 2. Therefore. Proceed as follows: 1. behavior summary can only be updated in one currency. choose Credit Management → Credit Risk Monitoring → Processes → Events and Follow-On Processes . To enhance the XI interface. 4603 XI: Accept CreditChangeInformation See section "Reaction to Master Data Changes in SAP Credit Management “ 4609 XI: Change to Notification for Credit Exposure Update The data is sent using the XI interface CreditCommitmentNotification . You should read the documentation for this Customizing activity. when you maintain the check rules in SAP Credit Management you have to define the system group for the commitment query. you use the data type enhancement concept in XI. when you change the FI-CA creditworthiness. The data is sent using the XI interface CreditWorthinessChangeInformation . To enhance the XI interface. Page 54 of 67 . triggers are updated for changes to the following master data: ● ● ● ● ● Score Risk class Blocked in Credit Management indicator Block reason Special Attention indicator PUBLIC © 2014 SAP SE or an SAP affiliate company. use the element PendingCommitment of the interface SAP A2A Interface CreditCommitment. here you have to calculate the amount in the credit segment currency. 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. since the payment 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 4600 Supplement XI Interface for Payment Behavior Summary The data is sent using the XI interface CreditPaymentBehaviourSummaryNotification . FKK_SAMPLE_4505. To do this. FKK_SAMPLE_4502. FKK_SAMPLE_4504. even if the score has not been replicated from SAP Credit Management . To enhance the XI interface. See the documentation of the sample function modules FKK_SAMPLE_4500. for example. you have to generate a company-wide unique partner message ID in the external system. in Customizing for Financial Supply Chain Management choose Credit Management → Credit Risk Monitoring → Credit Limit Check → Define Check Rules . You also have to transfer the partner message ID to the document interface for posting the FI-CA document. the creditworthiness in Contract Accounts Receivable and Payable and the score in SAP Credit Management are calculated incorrectly. you use the data type enhancement concept in XI. To do this. Note that if you do not follow this procedure. All rights reserved. Settings for Commitment Query To support the commitment query of SAP Credit Management in Contract Accounts Receivable and Payable . In the standard. 4602 XI: Supplement FICARatingReplicateResponse_In The data is sent using the XI interface FICARatingReplicateResponse . you can calculate the SAP Credit Management score immediately.This enables Contract Accounts Receivable and Payable to simulate the score in SAP Credit Management at any time using the current FI-CA creditworthiness. FKK_SAMPLE_4503. You have to report this ID when you update the credit exposure from invoicing in SAP Credit Management . Partner Messages To support the partner messages of SAP Credit Management from an external system. In the Implementation Guide for Financial Supply Chain Management . Set the XI indicator for the relevant event. and FKK_SAMPLE_4609. 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) 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 . FKK_SAMPLE_4501. FKK_SAMPLE_4600. run report RFKK_CR_FILL_DFKKOBL_INITIALLY ( Initialization of Credit Exposure ) for all relevant business partners. 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.00). If you want to make changes to contract accounts. 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). you must make a corresponding enhancement in SAP Credit Management . Procedure Navigation Paths in the Implementation Guide for Contract Accounts Receivable and Payable (FI-CA) In the Implementation Guide for FI-CA. 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. you first have to initialize the credit exposure of the business partner. 4. for example) in Contract Accounts Receivable and Payable based on the replicated master data. for example). that is. the master data from SAP Credit Management is saved to table DFKKCMS ( Credit Management: Master Data Replication ).72 and Connecting Contract Accounts Receivable and Payable 6. 2. 3. the use of some terms from SAP Credit Management has changed. Once the master data has been successfully replicated. From a technical perspective. proceed as follows: 1. see Terminology Changes from mySAP ERP 2005. 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 . For more information. you must enhance the interface. the same XI messages are used as for replicating the creditworthiness: ● Sending of XI messages to SAP Credit Management in which a master data replication is requested (XI message FICARatingReplicateQueryOut ) ● Sending of XI messages with master data information from SAP Credit Management (XI message FICARatingReplicateResponse ) The master data from SAP Credit Management is then replicated in Contract Accounts Receivable and Payable . choose Transaction PUBLIC © 2014 SAP SE or an SAP affiliate company. 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. 2. If the change to the field you requested in SAP Credit Management does not exist as an event (changing the Bankruptcy Proceedings indicator. use the data type enhancement concept in XI. If you have already created productive business partners in FI-CA and then subsequently activate SAP Credit Management . 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. If the field you requested does not exist in the XI interface CreditWorthinessChangeInformation . Page 55 of 67 . Note the differences in terminology between applications with different releases – from mySAP ERP 2005. For performance reasons. You have configured the business partner data for SAP Credit Management (see Data Replication). See the section Define Events and Follow-On Processes . Create the master data as fields in the customer include in table DFKKCMS ( Credit Management: Master Data Replication ). define event 4506 accordingly. Making Settings in Contract Accounts Receivable and Payable (FICA) Use To integrate your FI-CA system with SAP Credit Management . the triggers Score and Risk Class are allocated the status Data Received . You can use the mass activity Prepare Master Data Changes from External System to subsequently process these triggers.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. Supplement the master data at event 4602. To do this. SAP recommends that you do not replicate data from the credit segments. Supply the export structure for the trigger table in event 4603. All rights reserved. Use event 4507 for all changes to other objects (such as the contract). you have to make the settings described below. If you want this update to take place for all other triggers. To do this. 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. you can call this interface in event 4601 (only valid for Release 4. All rights reserved. even if the score has not been replicated from SAP Credit Management . FKK_SAMPLE_4504. here you have to calculate the amount in the credit segment currency.00) 4600 Supplement XI Interface for Payment Behavior Summary Event 4600 is processed for each business partner and credit segment. and enter formula for the rating procedure FICA. you only have to copy the data to the corresponding proxy structure.72). in the method SUPPRESS_CHECK. for example. 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. 3. 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.Integration → Financial Supply Chain Management → Credit Management → Activate Credit Management FQK52 Integration → Financial Supply Chain Management → Credit Management → Maintain Credit Segments FQK51 Integration → Financial Supply Chain Management → Credit Management → Assign Open Items to Credit Segments FQK50 Integration → Financial Supply Chain Management → Credit Management → Define Specifications for Credit Management FQK53 The credit segments that you enter in the activity Maintain Credit Segments have to agree with those of SAP Credit Management . 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. the creditworthiness in Contract Accounts Receivable and Payable and the score in SAP Credit Management will be calculated incorrectly. you can calculate the SAP Credit Management score immediately.00) 4504 Additional Selection for Payment Behavior Summary (from Release 6. FKK_SAMPLE_4501. Otherwise it is not possible to update the credit exposure correctly. whereby 0 is the best score. Settings for Commitment Query To support the commitment query of SAP Credit Management in Contract Accounts Receivable and Payable .00) 4505 Determination of Value for Credit Check (from Release 6. 2. This rating procedure must be defined in Customizing for SAP Credit Management . FKK_SAMPLE_4502. Settings for Scoring in SAP Credit Management In SAP Credit Management . when you change the FI-CA creditworthiness. For the creditworthiness from Contract Accounts Receivable and Payable to be included in the SAP Credit Management score. FKK_SAMPLE_4600. and FKK_SAMPLE_4601. Note that if you do not follow this procedure.00. and enter the rating procedure FICA. in the Implementation Guide for Financial Supply Chain PUBLIC © 2014 SAP SE or an SAP affiliate company. To do this. However. In the implementation. In the Implementation Guide for Financial Supply Chain Management choose Credit Management → Credit Risk Monitoring → Master Data → Define Rating Procedure . FKK_SAMPLE_4505. when you maintain the check rules in SAP Credit Management you have to define the system group for the commitment query. 4601 XI: Asynchronous Outbound Interface for Payment Behavior Summary See the documentation of the sample function modules FKK_SAMPLE_4500. since the payment behavior summary can only be updated in one currency. as a result of a dunning activity in Contract Accounts Receivable and Payable . To do this. if you want to use your own XI interface to also transfer customer-specific fields to SAP Credit Management . set the export parameter C_SUPPRESS to X for the rating procedure FICA. You have to ensure these value areas via an appropriate formula for calculating the score. Implement and activate the BAdI FSBP_BP1012_SUPR_CHK (control of check of rating procedure against Customizing). the enhacement concept of SAP Exchange Infrastructure enables you to enhance the interface with no technical modifications. If the data is sent using the XI interface CreditPaymentBehaviourSummaryNotification. the FI-CA creditworthiness is saved as external credit information in the rating procedure FICA. Page 56 of 67 . Therefore. The value areas of the FI-CA creditworthiness and the score are restricted to the interval from 0 to 9999. proceed as follows: 1. From Release 6. FKK_SAMPLE_4503. In the Implementation Guide for Financial Supply Chain Management choose Credit Management → Credit Risk Monitoring → Credit Limit Check → Define Formulas . SD and SAP Credit Management are integrated by means of implementations of Business Add-Ins (BAdIs) and IMG activities. 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) 1.6 Making Settings in SD ERP 2005 Use The following settings are necessary for calling up the credit check when you create or change an SD order (from one or more SD systems) and to update commitments from SD in SAP Credit Management . you must also integrate your SD system with SAP Credit Management using XI interfaces (see configuration step Connecting Sales and Distribution ERP 2005).1. Prerequisites In order to use the update options specified.Management choose Credit Management → Credit Risk Monitoring → Credit Limit Check → Define Check Rules . set the export parameters E_ACTIVE_FLAG and E_ERP2005 to X in the method SET_ACTIVE. Procedure Navigation Menu Path in SAP Customizing Implementation Guide (in SD system) Transaction Code SAP Customizing Implementation Guide → Enterprise Structure → Definition → Financial Accounting → Define Credit Control Area Financial Supply Chain Management → Credit Management → Integration with Accounts Receivable Accounting and Sales and Distribution → Integration with Sales and Distribution → Define Credit Segment Financial Supply Chain Management → Credit Management → Integration with Accounts Receivable Accounting and Sales and Distribution → Integration with Sales and Distribution → Assign Credit Control Area and Credit Segment Financial Supply Chain Management → Credit Management → Integration with Accounts Receivable Accounting and Sales and Distribution → Integration with Sales and Distribution → Assign Sales Area to Credit Control Area Financial Supply Chain Management → Credit Management → Integration with Accounts Receivable Accounting and Sales and Distribution → Integration with Sales and Distribution → Enter Settings 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 OVAK Accounts Receivable Accounting and Sales and Distribution → Integration 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 1. you have to generate a company-wide unique partner message ID in the external system. You should read the documentation for this IMG activity. Partner Messages To support the partner messages of SAP Credit Management from an external system. use the element PendingCommitment of the interface SAP A2A Interface CreditCommitment. To do this.2. You have to report this ID when you update the credit exposure from invoicing in SAP Credit Management . Implement and activate the Business Add-In UKM_R3_ACTIVATE. PUBLIC © 2014 SAP SE or an SAP affiliate company. Page 57 of 67 .7. All rights reserved. You have configured the business partner data for SAP Credit Management (see Data Replication). Implement the BAdI BADI_SD_CM. The credit check and commitment update are not supported for service orders. You can execute these steps independently of one another and in any order. 2. You also have to transfer the partner message ID to the document interface for posting the FI-CA document. In the implementation. the fields of the outbound XI interface of SD are determined according to the following rules: ○ Business Partner Number = Customer ○ Credit Segment = Company code 2. for technical reasons. 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 For example coding. Therefore. 1. However. see Terminology Changes from mySAP ERP 2005. Prerequisites ● In order to use the update options specified. Page 58 of 67 . SD and Credit Management are currently still integrated via implementations of Business Add-Ins (BAdIs) and via some IMG activities of the original Credit Management (FI-AR-CR). To be able to create liabilities from SD orders. you must a.You can use the following methods: Method Description FSCM_GET_MASTER_DATA Determine master data of partner before credit check. only the existence of the master records is important.7 Making Settings in SD ERP 2004 Use The following settings are required to call up the credit check when you create or change an SD order (from one or more SD systems) and to update commitments from SD in SAP Credit Management . Implement the BAdI BADI_SD_CM. Note the differences in terminology between applications with different releases – from mySAP ERP 2005.2.7. PUBLIC © 2014 SAP SE or an SAP affiliate company. in particular the risk class FSCM_CREDIT_CHECK_ORDER Call credit check from order FSCM_CREDIT_CHECK_DELVRY Call credit check from delivery FSCM_COMMITMENT_UPDATE_ORDER Update new or changed order values FSCM_COMMITMENT_UPDATE_DELVRY Update new or changed delivery values FSCM_COMMITMENT_UPDATE_INVOICE Reduce order values during billing and create open billing values if no immediate transfer to FI FSCM_DISPLAY_CREDIT_MESSAGES Control output of messages for credit check in dialog For example coding.1. see the implementation UKM_BADI_IMP1 (delivered inactive). ● You have configured the business partner data for SAP Credit Management (see Providing Business Partner Data). the customers concerned must have master records in table KNKK. in the original Credit Management (FI-AR-CR). the use of some terms from SAP Credit Management has changed. For more information. Procedure Navigation Menu Path in SAP Customizing Implementation Guide (In SD System) Transaction Code SAP Customizing Implementation Guide → Enterprise Structure → Definition → Financial Accounting → Define Credit Control Area SAP Customizing Implementation Guide → Sales and Distribution → Basic OVAK Functions → Credit Management/Risk Management → Credit Management → Assign Sales Documents and Delivery Documents SAP Menu → Accounting → Financial Accounting → Accounts Receivable → Credit Management → Master Data → Change FD32 1. All rights reserved. In this example implementation. Define at least one credit control area b. see the implementation UKM_BADI_IMP1 (delivered inactive). Create one master data record per customer. The content of the fields is not important. You can execute these steps independently of one another and in any order. that is. you must also integrate your SD system with SAP Credit Management using XI interfaces (see configuration step Connecting Sales and Distribution ERP 2004). In this example implementation. Prerequisites PUBLIC © 2014 SAP SE or an SAP affiliate company. Making Settings in SAP CRM 5.6C Use The following settings are required to call up the credit check when you create or change an SD order (from one or more SD systems) and to update commitments from SD in SAP Credit Management . To be able to create liabilities from SD orders. that is. for technical reasons. Prerequisites ● In order to use the update options specified. Page 59 of 67 . Create one master data record per customer. see Terminology Changes from mySAP ERP 2005.6C).1.1 Use You make the following settings to enable you to: ● Call the credit check when you create or change a CRM transaction (from one or more CRM systems) ● Update the credit exposure from SAP CRM in SAP Credit Management ● Display master data from SAP Credit Management in SAP CRM A CRM system is connected to SAP Credit Management in a customer project solution. Note the differences in terminology between applications with different releases – from mySAP ERP 2005. only the existence of the master records is important.2. All rights reserved. you must a. Procedure Navigation Menu Path in SAP Customizing Implementation Guide (In SD System) Transaction Code SAP Customizing Implementation Guide → Enterprise Structure → Definition → Financial Accounting → Define Credit Control Area SAP Customizing Implementation Guide → Sales and Distribution → Basic Functions → Credit Management/Risk Management → Credit Management → Assign Sales Documents and Delivery Documents OVAK SAP Menu → Accounting → Financial Accounting → Accounts Receivable → Credit Management → Master Data → Change FD32 1. you must also integrate your SD system with SAP Credit Management using XI interfaces (see configuration step Connecting Sales and Distribution 4.7. the use of some terms from SAP Credit Management has changed. Create an enhancement project (transaction CMOD) and assign enhancement UKM_SD to this project.1 for telecommunications. ● You have configured the business partner data for SAP Credit Management (see Providing Business Partner Data). Define at least one credit control area b.8 Making Settings in SD 4. in the original Credit Management (FI-AR-CR). the customers concerned must have master records in table KNKK. For more information. SD and Credit Management are currently still integrated via implementations of Business Add-Ins (BAdIs) and via some IMG activities of the original Credit Management (FI-AR-CR). 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 There is example coding for each function module exit. the fields of the outbound XI interface of SD are determined according to the following rules: ○ Business Partner Number = Customer ○ Credit Segment = Company code 2.70 or 4. You can execute these steps independently of one another and in any order.70 or 4.1. An exception is SAP CRM 5. Therefore. The content of the fields is not important. However. You have configured the business partner data in SAP Credit Management (see Providing Business Partner Data). Note the differences in terminology between applications with different releases – from mySAP ERP 2005. PUBLIC © 2014 SAP SE or an SAP affiliate company. see Terminology Changes from mySAP ERP 2005.1)). 4.0. Basic Functions → Credit Management → Business Partner Rating → Display Credit Master Data from Credit Management System Make the settings in the IMG activities under this node as described in the IMG documentation. 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. see Terminology Changes from mySAP ERP 2005. ● You have configured the business partner data for SAP Credit Management (see Providing Business Partner Data). the use of some terms from SAP Credit Management has changed. ○ CRM 2004 Industry Add-On Edition is installed on the CRM system with Release 4. 2. All rights reserved. To activate the update of commitments to SAP Credit Management . Prerequisites ● One of the following system prerequisites must be fulfilled: ○ The CRM system has Release 5. You can execute these steps independently of one another and in any order. ● In order to use the update options specified. set the Credit Update Active indicator .In order to use the functions specified. you have also integrated your CRM system(s) with SAP Credit Management using XI interfaces (see configuration step Connecting Customer Relationship Management (CRM)). For more information. the use of some terms from SAP Credit Management has changed. using transaction SM30 make two new entries in table SMW3FDCUST.0. If you use this credit group for document types for which a credit exposure update is to take place. 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 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 Also make the following settings: Making Settings in SAP CRM 5. CRM is connected to SAP Credit Management in a customer project solution. Procedure In the CRM system. Note the differences in terminology between applications with different releases – from mySAP ERP 2005. Basic Functions → Credit Management → Credit Check and Credit Exposure Update → Maintain Credit Group Define a new credit group with credit rule 02. Basic Functions → Credit Management → Credit Check and Credit Exposure Update → Activate Credit Check in Transaction. 3. make the following settings in the Implementation Guide for Customer Relationship Management under the following paths: 1. For more information. Page 60 of 67 . 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. you have integrated your CRM system(s) with SAP Credit Management using XI interfaces (see section Connecting Customer Relationship Management (SAP CRM 5.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 .0 and SAP CRM 4. 5. Procedure Perform the steps in these guidelines in the sequence in which they appear. This involves. SAP Customizing Implementation Guide → Customer Relationship Management → Basic Functions → Credit Management → Activate Credit Check in Transaction. or if no OLTP system was used in the business scenario. 3. Defining Credit Master Data in the Business Partner Use In the master data of the business partner you define the following: ● Which rule is used to calculate the score. To activate the update of commitments to SAP Credit Management . using transaction SM30 make two new entries in table SMW3FDCUST. 4. and/or the credit limit manually. make the following settings: 1. 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.Procedure In the CRM system. you can define the score. or if you have not activated credit exposure update from ERP SD. ● 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? PUBLIC © 2014 SAP SE or an SAP affiliate company. Make the settings according to the following table: Detailed Settings Field Name Description User Action and Values BDOC_TYPE BDoc Type CMDOC_NOTIFY FCTXT Context mBDOC notification (additional calls) CNTR Sequence 10 FNAME Service Function CRM_UPLOAD_FSCM_CR_SRV ACTIV Entry Active X Field Name Description User Action and Values BDOC_TYPE BDoc Type CMDOC_NOTIFY FCTXT Context Multiple mBDOC notification (additional CNTR Sequence 10 FNAME Service Function CRM_UPLOAD_FSCM_CR_SRV ACTIV Entry Active X Note and Note calls) Setting Up Component-Specific Master Data Purpose This section contains information about master data that has not been completely replicated. SAP Customizing Implementation Guide → Customer Relationship Management → Basic Functions → Credit Management → Maintain Credit Group Define a new credit group with check rule 02. 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. Page 61 of 67 . the risk class. If you use this credit group for document types that are not replicated in ERP SD. 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. All rights reserved. for example: ● Master data (for example. set the indicator Credit Update Active . and the credit limit? Alternatively. 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. 2. risk class. If required. 9. ● If you want to import external credit information automatically. enter collateral and/or credit insurance with amount and currency. You can use the external credit information as input parameter for scoring. Page 62 of 67 . in change mode choose Delete Data in Segment.1. for example. If required. make sure that you have made the corresponding Customizing settings for the additional information (see Configuring Business Partner Additional Information). You have configured the Customizing of the customer credit groups. name. indicator for special attention? Prerequisites ● ● ● ● ● You have created a general master data record for the business partner (for example. This resubmission date is a selection criterion.● External credit information ● Collateral and credit insurance? ● Negative credit events. credit insurance. if necessary. negative credit events. and different distribution channels therefore apply. for example. in the credit limit utilization list. The field Information Type is a counter that enables you to enter several check exceptions. and the risk classes. or automatically via the follow-on process Set Indicator for Special Attention in Customizing for Events and Follow-On Processes . 6. portrayed your analysts and analyst groups as business partners in the system. You can use the customer credit group as selection criterion in the transactions for mass changes to credit master data. in the data for a credit segment. enter a customer credit group. choose Relationships . make sure that the external information providers are connected via the relevant XI interface (see Connecting External Information Providers). or business partner-specific check exceptions. in the data for a credit segment. in the credit limit utilization list. Procedure Navigation Menu Path Transaction Code SAP Menu → Accounting → Financial Supply Chain Management → Credit Management → Master Data → Business Partner Master Data UKM_BP 1. and set the relevance indicator and a validity interval. You can restrict the relationship to one credit segment or it can be valid for all credit segments. block reasons. 1. for example. if a customer becomes a major customer. enter a business partner relationship of the category Managed in Credit Management By . To have the system calculate the score. category. enter check exceptions with a validity interval. Under certain circumstances. The business partner that you refer to is an analyst or an analyst group. 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. 10. enter external credit information or import it via the XI interface. If you want to use collateral. under the additional information in the general data (valid for all credit segments there) or in the data for a credit segment. You can restrict the relationship to one credit segment or it can be valid for all credit segments. to do this. and an information type for categorization. If required. 7. set the indicator Special Attention . under the additional information in the general data. Call up Business Partner Maintenance in the role Business Partner Credit Management . choose Calculate with Formula . 8. This means that the check can stretch over several hierarchy levels. All rights reserved. choose Relationships . If required. enter a rule for scoring and credit limit calculation and a check rule. 2. enter business partner relationships of the type Higher Level Credit Account of or Lower Level Credit Account of . the check rules. you need to make the following settings: · Configure notifications PUBLIC © 2014 SAP SE or an SAP affiliate company. You can use the analyst or analyst group as selection criterion in the credit limit utilization list. You have. In a credit check with the check steps Statistical Check of Credit Limit Utilization or Dynamic Limit Check with Credit Horizon . This could be the case. A credit check for a blocked credit account (that is. 11. 3. 4. If required. In a credit check for this partner. If required. You have made the Customizing settings for the rule for scoring and credit limit calculation. 5. the block reasons. If required. You can set the indicator manually. 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. You usually use this function to assign a bad score to a partner in such a case. with block reason (optional). before the comparison with the credit limit. This means that you can achieve a temporary relaxation in the checks for a business partner without having to define a new check rule. partner and credit segment) always has a negative result if the block indicator is set.9 Workflow Settings Process To be able to use the various workflows of SAP Credit Management . in the data for a credit segment. If required. enter negative credit events with a validity interval. This indicator is a selection criterion. Before you delete date in the previous credit segment. deletion date. Any block reason appears in the log for the credit check. address). set the block indicator. to do this. In a credit check for a business partner. and the rating procedures. under the additional information in the general data (valid for all credit segments there) or in the data for a credit segment. If required. On the tab page Credit Profile . In the definition of formulas for scoring or the credit limit calculation. set the resubmission date. make sure that the credit exposure is zero! To delete the data in the previous credit segment. If required. you may have to delete the business partner data in the previous segment and recreate it in a different credit segment. higher level credit accounts are also checked. you can use the function NEGATIVE_CHARS to check the existence of negative credit events. under Event Manager → Type Linkages. enter the follow-on process Start Workflow for the required event types. the following settings are defined for the object type CL_UKM_BUSINESS_PARTNER: Detailed Settings Field Name User Action and Values Object Category ABAP class Object Type CL_UKM_BUSINESS_PARTNER Event WF_TRIGGER Receiver Type WS01700047 Receiver Call Function module Receiver Function Module SWW_WI_CREATE_VIA_EVENT_IBF Linkage Activated Active Note Select indicator 3. a workflow item is created. SAP Credit Management supports the following event types: ○ Invalid Score ○ Changed Score ○ Changed Rule for Scoring and Credit Limit Calculation ○ Changed Risk Class ○ Changed Check Rule 2. This processor can approve or reject the required limit. Procedure PUBLIC © 2014 SAP SE or an SAP affiliate company. Make sure that the task is identified as a general task.9. Result When an event with the event type defined above occurs during master data processing. Make sure that. All rights reserved.· Configure approvals for credit limit changes 1. Choose Goto → Basic Data and then Goto → Agent Assignment for Task . changes that are not made manually. Procedure Navigation Menu Path (In SAP Credit Management system) Transaction Code SAP Customizing Implementation Guide → Financial Supply Chain Management → Credit Management → Credit Risk Monitoring → Processes → Define Events and Follow-On Processes SAP Menu → Tools → Business Workflow → Development → Administration → Event Manager → Type Linkage SAP Menu → Tools → Business Workflow → Development → Definition Tools → Workflow Builder → Workflow Builder SWETYPV SWDD 1. you can use workflow functions to have an analyst (recipient) notified of these events. In the IMG activity Define Events and Follow-On Processes . Page 63 of 67 . 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. Call up the Workflow Builder for the multistep task WS01700047 (ID UKM_BUPA).1. define which event types are to be dealt with in which activities.1 Configuring Notifications Use Where changes are made to the credit master data of a business partner. in particular. In the standard configuration of the workflow. This involves. mass change). by more than the percentage rate defined in the rule. If the user has the relevant authorization. he can accept the limit requested (it is included in the credit limit) or reject it. Call up the Workflow Builder for the multistep task WS01700047 (ID UKM_BUPA). Page 64 of 67 . ABAP-based production systems are locked for Customizing. enter the follow-on processes Check Request for Limit Change and Start Workflow for this event type. 1. manually or via an automatic process (for example. each credit limit increase requires approval.1 Importing Exchange Rates Use In SAP Credit Management . Choose Goto → Basic Data and then Goto → Agent Assignment for Task . Make sure that. instead. to change currency exchange rates. that is. define the activities in which event type Credit Limit Change Requested is to be dealt with. In the IMG activity Define Events and Follow-On Processes . There are however. for example.10. All rights reserved. This section also contains information about current settings that must be made in non-ABAP systems.10 Current Settings Purpose This section contains information about settings required during production operation. 1. 3. An empty entry is interpreted as 0%. 2. At the same time. the increased value is not transferred to the field Credit Limit immediately. define a percentage rate for the maximum credit limit increase permitted without approval.1. under Event Manager → Type Linkages the following settings are defined for the object type CL_UKM_ACCOUNT: Detailed Settings Field Name User Action and Values Object Category ABAP class Object Type CL_UKM_ACCOUNT Event WF_TRIGGER Receiver Type WS01700048 Receiver Call Function module Receiver Function Module SWW_WI_CREATE_VIA_EVENT_IBF Linkage Activated Active Comments Select indicator 4. You can make these current settings in the menu in ABAP-based systems. you can monitor a credit limit in credit segment currency regardless of the currency of the commitment report to SAP Credit PUBLIC © 2014 SAP SE or an SAP affiliate company. Procedure Perform the steps in these guidelines in the sequence in which they appear. Result If the credit limit of a credit account is increased. a workflow item is generated that provides information about this request and offers access to the business partner maintenance. For each rule and credit segment . for example: ● Data replication ● Business Customizing As a rule. Make sure that the task is identified as a general task. in this case. it is entered in the field Credit Limit Requested. certain cases in which Customizing settings must be made in production systems.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 → Development → Administration → Event Manager → Type Linkage SWETYPV SAP Menu → Tools → Business Workflow → Development → Definition Tools SWDD → Workflow Builder → Workflow Builder 1.1. delete the credit exposure line items and totals for the business partners and credit segments concerned in SAP Credit Management . You can then reload the credit exposure information from the systems connected to SAP Credit Management . to transfer the exchange rates to the system automatically via a file interface. regardless of the currency in which the commitment was reported to SAP Credit Management . you can always check the credit exposure of a customer in the currency of the credit segment. run the following program. From the SAP Easy Access screen. With this function. Integration The credit exposure transferred is displayed in the master record of the busiiness partner per credit segment. 1. The system can. Procedure 1. Prerequisites ● You have defined the exchange rates and translation factors in the SAP Credit Management system. Set both indicators Delete Totals and Delete Line Items . You can do this either manually or automatically via file interface. All rights reserved. which means that every time you call a report with credit exposure and commitment information. use the following reports: PUBLIC © 2014 SAP SE or an SAP affiliate company. you have defined which exchange rate type is to be used for the currency translation. There you can navigate to the relevant commitments.Management .10. choose Financials → Financial Supply Chain Management → Credit Management → List Displays → Credit Exposure . ● In the SAP Credit Management system. determine the credit exposure dynamically in credit segment currency by translating the commitment reports using exchange rates and translation factors. the translation is run with the current exchange rates. You can recreate the data manually. The translation is not saved in the system.2 Recreating Data (Troubleshooting) Use You recreate transaction data for one or more business partners in one or more credit segments if. see the report documentation. To recreate the credit exposures from an SD system. carry out the following IMG activities: Navigation Menu Path Transaction Code SAP Customizing Implementation Guide → Financial Supply Chain Management → Cash & Liquidity Management → Cash Management → Market Data → Manual Market Data Entry → Enter Exchange Rates S_BCE_68000174 SAP Customizing Implementation Guide → SAP NetWeaver → General Settings → Currencies → Define Translation Factors for Currency Translation Alternatively. Result By entering the exchange rates. or if transaction data has become inconsistent due to incorrect updates. for example. Page 65 of 67 . Navigation Menu Path Transaction Code SAP Menu → Accounting → Financial Supply Chain Management → Cash TBDM and Liquidity Management → Cash Management → Environment → Market Data → File Interface → Import For more information.1. Procedure To enter the exchange rates manually. as described below. 2. or schedule one-time processing in the background. if required. in an implementation of the Business Add-In UKM_FILL). the derivation of one or more credit segments has changed (for example. in the Customizing for the credit segments. For more information. Customizing of a check procedure changed The modified check procedure has an effect on subsequent checks. is currently not supported. Page 66 of 67 . In Customizing. credit rejected for following reasons ) are published according to the PUBLIC © 2014 SAP SE or an SAP affiliate company. Depending on the type of change (formula of score or limit). however. you may have to carry out corrections. Customizing of a rule for scoring and credit limit calculation changed Carry out a mass change. that is. 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 Chain Management → Credit Management → Master Data Mass Changes → Credit Limit UKM_MASS_UPD3 SAP Menu → Accounting → Financial Supply Chain Management → Credit Management → Master Data Mass Changes → Score UKM_MASS_UPD2 SAP Menu → Logistics → Sales and Distribution → Credit Management → Sales Documents → All VKM4 SAP Customizing Implementation Guide → Financial Supply Chain Management → Credit Management → Credit Risk Monitoring → Processes → Define Events and Follow-On Processes The following tables give you an overview of possible changes and the corresponding corrections: Change Measures Required Currency of a credit limit changed The credit limits of all business partners for this credit segment have to be recalculated. the transaction data is recreated from the credit exposure information of SD. you can check all open SD orders again. In SAP Credit Management . 1. for example. If necessary. see the report documentation. This report prepares an update run of report UKM_RVKRED77 to determine suitable selection parameters. 3. To recreate the credit exposures from an FI-AR system from the SAP Easy Access screen. or deleted No correction required. In the Customizing settings for Events and Follow-On Processes. Derivation of one or more credit segments changed (for example. added. selection by check procedure. that is. Rule for score and credit limit change in master record of business partner changed The change to the rule for scoring and credit limit calculation of a business partner is published as an event. Select the open items concerned in both sections of the selection screen and set the indicator Start Recreation . the credit exposure information from FI-AR is added to the transaction data.○ 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. Check rule in master record of business partner changed The change to the check procedure triggers the event with the same name. limit utilized to x%. 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. you can define that the rule for scoring and credit limit calculation is triggered. In SAP Credit Management . All rights reserved. The credit exposure contributions of other partners are always determined dynamically. adjust the formulas for determining the credit limit and carry out the mass change Credit Limit for this credit segment. A new credit check of open SD orders for the partner concerned only. Business partner relationship changed. see Recreating Data (Troubleshooting). The credit exposure of the main credit segment is always determined dynamically at runtime according to the current Customizing. you choose the appropriate report and then select the business partners and/or credit accounts affected via the rule. choose Financial Supply Chain Management → Credit Management → Integration of Credit Management with FI-AR → Asynchronous Credit Exposure Update . Events that occur as a result (for example.3 Converting Organizational Changes Use If you make changes to the SAP Credit Management master data or in Customizing during daily operations. Indicator Additive Contribution to Main Credit Segment changed in Customizing of a credit segment No correction required.10. you can define that a follow-on process Carry Out Credit Check in All Segments is triggered for this event. For more information about the procedure. in implementations of the Business Add-In UKM_FILL) Delete and recreate the transaction data in the credit segments concerned. the system carries out a credit check (with credit exposure change 0) in all segments.1. Run the function. you can have the system recalculate these fields once you have corrected the incorrect formula or input parameters. you have the following options: ○ You can change the risk class and the credit limits manually. ● Ensure data can only be used in SAP Credit Management Data that arises in SAP Credit Management should only be used in SAP Credit Management . ○ Transaction data. is not stored permanently in SAP Credit Management . if you use it ● Correct incorrect data for a business partner Your business partner has the right to have you correct incorrect data. Alternatively. the change document for this change contains the technical user defined in the XIChannel (for example. automatically as the result of a follow-on process during a credit check or an update of the commitment. ● Create own information To provide a business partner with information about the data saved for him in SAP Credit Management . Alternatively. you then have to send the data from the client systems again. Make sure that the rating only takes place if the business partner (natural person) has given his/her consent. Typical requirements are. if the system determined them based on an incorrect formula or on incorrect input parameters. scores. ○ You can delete incorrect commitment and credit exposure data with transaction UKM_COMMITMENTS. for example.Customizing settings. for example. ○ For example. for example. PUBLIC © 2014 SAP SE or an SAP affiliate company. ○ You can change negative credit events and data for collateral and credit insurances manually. you can define a text for external credit information in order to document the use in SAP Credit Management . or credit limits being recalculated unnecessarily or without a legal requirement. Page 67 of 67 . see Defining Authorizations. Depending on the field. ○ By implementing the method READ_RESPONSE of the Business Add-In UKM_CREDIT_INFO appropriately. In a subsequent mass activity. You can document a withdrawal of consent by setting a block reason in the master data. you can have the system recalculate this field once you have corrected the incorrect formula or input parameters. and transaction is supported for all master data fields of SAP Credit Management . ● Consent statement of the business partner for external credit information Inform your business partner specifically if you use a rule that evaluates information from external credit information providers. You can use report UKM_ADD_INFOS_DISPLAY to determine information that is no longer valid and then delete it manually. that is. the history of the credit limit and the score from SAP NetWeaver Business Intelligence . 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. ○ 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. Note the following special case: If the system determines master data. you can restrict the validity period for the scores and credit limits calculated. for example. provide the following data: ○ Overview of the master data in SAP Credit Management with transaction UKM_MASS_DSP2 ○ Overview of the transaction data in SAP Credit Management with transaction UKM_COMMITMENTS ○ If required. that unauthorized access to the data must be prevented and that the functional integration of saved data must be considered. ● Log changed accesses to master data The update of change documents with time. 1. you can. For more information. the system deletes it after clearing. a list of additional information with report UKM_ADD_INFOS_DISPLAY ○ If required. ○ You can and should enter negative credit events and data for collateral and credit insurances with a valid to date. All rights reserved.1. CREDITXIUSER). ● 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. 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. the system no longer considers the events and data but they remain in the system. ○ For each rule for scoring and credit limit calculation.10. ○ You can change a score calculated incorrectly manually if you configure a rule that does not contain a formula for scoring. line items with commitment information. Procedure To implement the data protection guidelines. a credit limit that is no longer valid. 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.4 Ensuring Data Protection Use Data that refers to natural persons is subject to legal data protection requirements that are different in each country. user. Once this date has passed.