Symptom
- Sales orders with payment terms set to "CC" (Credit Card) are being placed on credit block despite successful credit card authorization.
- Business Partners without visible Credit Management roles are also experiencing credit blocks.
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
- Create a sales order in SAP S/4HANA Cloud Public Edition using payment terms "CC" (Credit Card).
- Ensure the credit card authorization is successful.
- Observe that the sales order is placed on credit block.
Cause
- Credit check configuration (SSCUI 101518 / OVA8) is active for the sales document type used, with no exclusion logic or requirement routine configured.
- As a result, all sales orders, regardless of payment terms (e.g., credit card), are subject to standard credit check processing.
- Even when Business Partners do not have an assigned Credit Management role (UKM000), they may still have legacy or inherited credit segments that trigger credit control logic
- Additionally, credit card authorization issues (such as an authorization block) can impact the overall status of credit checks, resulting in the order being marked as "credit blocked."
Resolution
- Verify credit check settings
- Review SSCUI 101518 (Define Automatic Credit Control) to confirm that the configuration aligns with intended business behavior.
- Apply supported configuration workarounds
Consider the following supported options to bypass or manage credit checks for certain scenarios:- Assign a dedicated Risk Category (e.g., “ZCC”) for credit card customers, and ensure no logic is maintained for that category in SSCUI 101518.
- Leave the Risk Category field blank in the Business Partner’s credit profile.
- Remove the Credit Management role ( e.g., UKM000) if credit checks are not required for the customer.
- Assign a Credit Check Rule that contains no check logic for exempted scenarios.
- Check for payment card authorization issues
- If the credit block is caused by a payment card issue, ensure that the card authorization is successfully completed and no authorization block remains.
- This can affect the Overall Credit Check Status, even if no formal credit limit check is performed.
- If the credit block is caused by a payment card issue, ensure that the card authorization is successfully completed and no authorization block remains.
Limitations
- Dynamic skipping of credit checks based on payment terms (e.g., “CC”) is not supported in SAP S/4HANA Cloud Public Edition.
- Implementing such logic would require enhancements, which fall under consulting scope as clarified in SAP Note 2706322.
See Also
Keywords
credit block, payment terms CC, credit card authorization, SAP S/4HANA Cloud, credit check configuration, risk category, SSCUI 101518, Credit Management role, authorization block, public cloud limitations, sales order credit block, OR sales document type, UKM_BP, silent credit segment, Define Automatic Credit Control, credit exposure, credit control area config, credit limit = 0, payment card check failure,authorization status impact, credit group, blocked despite CC payment, business partner, credit data, master data check, credit card payment handling , KBA , SD-BF-CM-2CL , Credit Management (Public Cloud) , Problem
SAP Knowledge Base Article - Public