E - 20180425 S4TWL - Credit Management
E - 20180425 S4TWL - Credit Management
E - 20180425 S4TWL - Credit Management
Symptom
You are doing a system conversion to SAP S/4HANA and you are using Credit Management (FI-AR-CR) on
SAP ERP. In this scenario, the following SAP S/4HANA Transition Worklist item applies.
Solution
In the following we distinguish between the three possible constellations in your system:
A. You are only using FI-AR-CR Credit Management in your source release
B. You are only using SAP Credit Management (FIN-FSCM-CR) in your source release
C. You are using both Credit Management solutions (FI-AR-CR & FIN-FSCM-CR) in your source release
D. You are not using any of the Credit Management solutions (Then this note is not relevant for you)
(with the prefixes A, B, C, D we mark the explanations as relevant for these scenarios in the following
chapters)
Description:
Credit Management (FI-AR-CR) is not available as part of SAP S/4HANA. The functional equivalent in SAP
S/4HANA is SAP Credit Management (FIN-FSCM-CR).
Risk category -> Risk class maintained for the whole business partner (not per customer & credit
control area), as the probability of a credit default of your customer does depend on the characteristics
of your customer and not your internal organizational structures.
Maintenance of customer master data in business partner transaction
The credit checks carried out for a customer depend on the assigned check rule in the business
partner transaction. They do not depend on the risk class (formerly risk category).
Releasing blocked documents via Case Management (documents the blocking reason)
You are using transaction FD31 or FD32 to maintain credit account master data (this data is stored in
table KNKK & KNKA)
You are using transactions VKM1-4 to process sales documents (e.g. releasing blocked sales orders)
Function module UKM_IS_ACTIVE returns space for flag E_ACTIVE and E_ERP2005
In general: You are using parts of the obsolete transactions and reports listed in chapter "Business
Process related Information".
You are using transaction BP or UKM_BP to maintain credit account master data (this data is stored in
table UKMBP_CMS_SGM & UKMBP_CMS)
You are using transaction UKM_CASE to process sales documents (e.g. releasing blocked sales
orders)
Function module UKM_IS_ACTIVE returns 'X' for parameter E_ACTIVE and E_ERP2005
Business Value:
Higher degree of automation, thanks to automatic calculation of credit scores, risk classes and credit
limits
Credit events help the credit analyst to focus on exceptions during his daily business
Create a relationship from credit analysts to customers
Process of credit limit requests
Documented credit decisions
Higher / lower account relationship of business partners (adds up exposure of lower accounts on
higher accounts)
Less redundant data (reading FI-data via HANA view)
A & C: You need to migrate FI-AR-CR to FIN-FSCM-CR. The migration from one-system landscapes is
supported by tools that SAP provides in the IMG. (see details in chapter "Required and Recommended
Action(s)")
A & B & C: There will be no change to your business processes because of the system conversion.
A & C: However, some transactions become obsolete and are replaced by new transactions.
Examples for replaced For the maintenance of the credit account master data, transaction FD32 is
transactions in SAP S/4HANA replaced by transaction UKM_BP.
Reports not available in SAP RFARI020 - FI-ARI: Extract from credit master data
S/4HANA RFARI030 - FI-ARI: Import credit master data
RFDFILZE - Credit Management: Branch/Head Office Reconciliation
Program
RFDKLI*NACC Reports
RFDKLxx Reports
All IMG activities for SAP Credit Management are listed in Customizing under the following path:
Financial Supply Chain Management>Credit Management.
The credit limit check for sales document types can only be specified as type D in SAP Credit
Management or can be left empty (no credit limit check). The credit limit check types A, B, and C are
no longer available.
The credit check when changing critical fields has been removed from the SD side.
The payment guarantee-related Letter of Credit has been removed from the SD side.
A credit check on the basis of the maximum document value is not supported in SAP S/4HANA 1511
SP00 and SP01.
It is supported as of SAP S/4HANA 1511 FPS2.
B: Migrating Credit Management is not needed. Review of BadIs "UKM_R3_ACTIVATE" and "UKM_FILL" is
advisable. Think of using the default implementation provided by SAP. (FI-data will then be read real-time
with the default implementation of BadI "UKM_R3_ACTIVATE". The implementation of BadI "UKM_FILL" is
then not needed anymore.)
A & C: You need to migrate FI-AR-CR to FIN-FSCM-CR completely. This migration comprises several
elements:
Configuration data
Master data
Credit exposure data
Credit decision data
The migration from one-system landscapes is supported by tools that SAP provides.
You have completed all documents related to payment guarantee Letter of Credit.
You have completed the migration for Accounting.
If you are running on your own code, you have eliminated the usage of SAP objects in your own code.
For details on how to adapt user-defined customer code that relies on the changed objects, see the
following SAP Notes:
2227014 (Financials)
2227014 (SD)
2. Perform the recommended actions in the Task List PDF attached to this Note (only available in English).
This list is only valid for the conversion of one-system landscapes.
C (additionally): Review of BadIs "UKM_R3_ACTIVATE" and "UKM_FILL" is advisable. Think of using the
default implementation provided by SAP.
Software Components
Other Components
Component Description
Attachments
2017-01-20_Task List for the Conversion of Credit Management to SAP S4HANA.pdf.pdf 1015 application/pdf