Checked Credit Value is wildly used in credit management. Sometimes it could be a little confused as it does not always equal the total credit value of the sales order. The simplest scenario, it's the input amount value when performing a simulation of a credit check for a specific business partner along its credit segment. The log of results of UKM_BP simulation and its credit check displays like below:
The Checked Credit Value is the difference between current commitment and old commitment. For BP credit check simulation, it'll be the input amount value which is the delta of old& new commitments.
It's been collected into message '031' using the message type 'ukm_check'.
And finally, it could be stored as an attribute(UKM_DCD_ATTR-DCD_CHKDRISKAMT) of DCD(Documented Credit Decision) like below if credit check trigger DCD creation or update.
But when comes to DCD, the checked credit value will be dynamic compared with a pure credit check for a Business partner. SAP provides the documentation for Checked Credit Value like below:
In short, there're 3 scenarios for checked credit value at DCD.
The logic of filling the field Checked Credit Value is described in SAP note 2473178 – SAP Credit Management: Checked Credit Value in DCD is not the total value of the sales order:
Besides:
1. the method 'GET_DCD_ATTR_CREDIT_CHECK_LOG' of class 'CL_UKM_LOG_GATE' can be used to fetch this value and convert it into checked credit value at DCD.
2. It's hard to skip credit checks (OVA8 or VOFM->requirements->credit check) by comparing checked credit value and order value from my aspect. Cause OVA8 entry is called ahead of Checked Credit Value been calculated by the system, then we have to calculated by ourselves. Just imagine how many scenarios need to be considered... Maybe it's workable at check steps.
Please correct me if I'm wrong : P
The process of credit check involved checked credit value is directly impacted by individual check step: 010 (Statistical Check of Credit Exposure) which is standard BADI implementation 'UKM_CHECK_010' of BADI: 'UKM_CHECK_STEP'. (As well as UKM_CHECK_030 Dynamic Limit Check with Credit Horizon). Those steps can be triggered during BP simulation but not the DCD creation processing cause different mechanisms.
The Checked Credit Value is the difference between current commitment and old commitment. For BP credit check simulation, it'll be the input amount value which is the delta of old& new commitments.
It's been collected into message '031' using the message type 'ukm_check'.
And finally, it could be stored as an attribute(UKM_DCD_ATTR-DCD_CHKDRISKAMT) of DCD(Documented Credit Decision) like below if credit check trigger DCD creation or update.
But when comes to DCD, the checked credit value will be dynamic compared with a pure credit check for a Business partner. SAP provides the documentation for Checked Credit Value like below:
Checked Credit Value
Specifies the value checked by the system during the latest credit check with regard to the credit risk.
Example
1. A credit analyst enters a new order with a value of EUR 100. Following the related credit check, the system enters the value 100 in this field.
2. As the customer has reduced his order by EUR 10, the credit analyst also makes this change in the system. Following the related credit check, the system enters - 10 (minus 10) in this field.
3. If the credit analyst checks the order again later without making any changes, the system enters the value 0 (zero) in this field.
In short, there're 3 scenarios for checked credit value at DCD.
- Checked Credit Value = Total credit value of the sales order (order creation)
- Checked Credit Value not = Total credit value of the sales order (price relevant order updated like partially confirmed)
- Checked Credit Value = ZERO. (order updated without relevant to price)
The logic of filling the field Checked Credit Value is described in SAP note 2473178 – SAP Credit Management: Checked Credit Value in DCD is not the total value of the sales order:
Besides:
1. the method 'GET_DCD_ATTR_CREDIT_CHECK_LOG' of class 'CL_UKM_LOG_GATE' can be used to fetch this value and convert it into checked credit value at DCD.
2. It's hard to skip credit checks (OVA8 or VOFM->requirements->credit check) by comparing checked credit value and order value from my aspect. Cause OVA8 entry is called ahead of Checked Credit Value been calculated by the system, then we have to calculated by ourselves. Just imagine how many scenarios need to be considered... Maybe it's workable at check steps.
Please correct me if I'm wrong : P
- SAP Managed Tags:
