2. Table of Content
• Business partner
• Introduction of credit management
• Functional capabilities comparison
• Obsolete Transactions in SAP S4 Hana
• Master data
• Credit Master Data Reports
• Relationship categories
• Documented credit decision
• Reporting
3. Business
Partner
• A business partner is a person , group or organization with which you have a business
relationship.
- Person (can be employee, can be individual person)
- Group (can be group of persons or partners)
- Organization (can be company, department in a company)
• The ECC transaction XD01, XD02, XD03 (Customer: Create, Change, Display) are redirected
to transaction BP
• In SAP S4 Hana, The roles you assign to a business partner reflect the functions it has and
the business transactions in which it is likely to be involved.
• A business partner role can be
- Business partner general data
- Customer
- Vendor
- SAP Credit management & so on.
4. Introducing
SAP S/4 HANA
Credit
Management
• In S/4HANA credit management is a part of FSCM (Financial supply chain
management)
• In SAP S/4HANA, Credit Management (FI-AR-CR) is not available, functional
equivalent is SAP Credit Management (FIN-FSCM-CR)
• Credit management provides functionalities such as internal scoring, categorizing for
existing as well as new customers.
• Credit Management Master Data stored in tables: UKMBP_CMS &
UKMBP_CMS_SGM
• Use of Transaction Code BP or UKM_BP for SAP Credit Management Customer
Master Data. T-code BP, role: SAP Credit Management
5. Functional Capabilities Comparison
Functionality ECC Credit Management FSCM Credit Management
Master Data SAP Customer SAP Business partner
Finance Data FI-AR FI-AR-FI-CA, others
Credit Exposure Monitoring Only at the level of credit control area At segment and main segment level
control area (Overall credit limit)
Distributed system-landscape (multiple
FI, SD and CRM systems)
Scoring & rating for customer Not available Credit Rules Engine
Credit Limit Rules Not available Credit Rules Engine
Relationship Not available Hierarchy relationship
6. Obsolete
Transactions
in SAP S4
Hana
• It is no longer possible to use transactions such as:
Category Obsolete
Transaction replaced by BP – FD01, FD02, FD03, FDOS, FD06, FDO,
FD31, FD32
– VD01, VD02, VD03, VD05, VD06
– XD01, XD02, XD03, XD05, XD06, XD07
Obsolete transaction in accounts
receivable (FI-AR-CR) component
– F.28: Customers: Reset Cred it Lim it
– F.31: Credit Management- Overview
– F.32: Cred it Management - Missing
– Data
– F.33: Credit Management - Brief
– Overview
– F.34: Credit Management- Mass
– Change
Obsolete transaction in sales and
distribution (SD-BF-CM) component
– VKM2 Released SD document
– VKM3 Sales document
– VKM5 Deliveries
7. Master Data
of Credit
management
• Maintenance of credit management data in the business partner
role SAP Credit Management (UKM000).
• To access master data, use Transaction UKM_BP or BP (and then
select the business partner role SAP Credit Management).
• Use partner roles, such as FI Customer, Customers & Credit
Segment
• Risk category -> Risk class maintained for the whole business partner
(not per customer & credit control area)
• UKM_BP_DISPLAY is a transaction code for BP display.
8. General Data
• The master data roles are stored in different types of tables.
• If the master data is not updated properly then the whole credit management is fail to
serve its purpose.
• The General Data relevant for credit management is stored/displayed in the Credit
Profile tabs. The information in tabs other than these two is available to all business
partner roles.
• All of these tabs contains fields that are often relevant for credit management I.e. In
Identification tab contains information about Tax numbers
9. Credit Profile
• The information stored and displayed in the Credit Profile tab is common for all
segments for a business partner.
• Scoring: data is stored in table UKMBP_CMS.
RULES:
- Determines a score is maintained in the rules field.
- We can customize our rules using credit formulas
RISK CLASS
- Risk class and risk category are same
- The customer can divided into various categories I.e. low, medium high risk. each
risk category has defined with certain limits.
- If customer exceed the limit the system automatically changes the risk from low to
high
10. Credit Profile
CHECK RULES
– The system determines the steps which are taken to check the credit of a
customer when a sales order is created.
– The system can be used rules for individuals check steps. Such as
– Highest dunning level
– Age of oldest open items
– Check payment behavior index
– Over due open items
– Open deliveries
– Open invoices
11. Credit Segment
Data
• Credit segment data stored in table UKMBP_VECTOR_IT.
• The tabs are available in credit segment data are credit limit and controls.
• The data stored in these tabs is for a particular credit segment.
12. Credit Limit &
Controls
Credit limit & control data tab store master data relevant for a credit segment data
• The rule uses different formulas for calculating Score and Credit Limit.
• The information icon next to the Calculated Limit amount provides you with the
detailed information about how the limit was calculated
• When you click the information icon next to calculator you can see detailed of
amounts that made the total exposure such as open orders , open items and so
on.
• We can check these amount in an individuals document level
13. Credit Master
Data Reports
• Master data records of business partners store all credit-relevant information for
the business partner.
• Transaction UKM_BP is used for individual customers.
• Transaction UKM_COMMITMENTS used for credit exposure.
• Transaction UKM_BP_DISPLAY is used to monitor several business partners at
a time. This transaction is also a replacement of old transaction FDK43.
• Transactions UKM_BP_PROFILE and UKM_BP_SEGMENT can be used for
credit profile and credit segment data respectively for a business partner.
• Transaction UKM_MALUS_DSP (List of credit limit utilization) gives the credit
limit utilization percentage comparing credit exposure with credit limit.
• This transaction also displays whether the credit limit for a business partner has
been exceeded or not by showing red and green traffic signal icons
• Transaction UKM_MASS_DSP1 is used to display data credit profile level
• Transaction UKM_MASS_DSP2 displays data at credit segment level.
20. Credit check
simulation
• Earlier testing was done by creating order, delivery and billing documents. In
the production client, testing is very difficult
• The credit check simulation is done using Transaction UKM_CHECK_SIMU.
• This can also be done from transaction BP
21. Mass
• The ECC transaction FD37, F.34 credit management mass change are
redirected to transaction UKM_MASS_UPD3
• To update the rules for scoring, credit limit calculation, and check rule, use
Transaction UKM_MASS_UPD4.
• Transaction UKM_MASS_UPD5. For credit management to work effectively
25. Relationship
Categories
• One business partner may be an employee of another business partner.
Similarly, one business customer can have different branches or different
subsidiary companies
• In the relationships functionality, you can link them or maintain the
relationship between them
• Relationship categories in SAP Credit management are:
- Credit management is managed by
- Credit analyst group
BUB1
26. Reports
- Reports are available in S/4 HANA.
• Transaction VKM1
Transaction used to display only sales and distribution documents credit
accounts/credit segment/credit control area that are blocked in credit
management.
• You can select one or more to release or reject them.
• You can also display the individual document.
27. Reports
• Transaction VKM4
Transaction VKM4 displays both blocked as well as released documents
(Order & Delivery level).
• You can block a released document by re-checking it.
28. Sales Order –
Credit Check • During sale order creation as usual we get the credit exceeding
warning
