SAP Knowledge Base Article - Public

3674047 - Credit Management Blocking Not Working at PGI Level - SAP S/4HANA Cloud Public Edition

Symptom

  • Credit management block is not triggered at the Post Goods Issue (PGI) process step.
  • The system allows users to perform PGI even when credit limits are exceeded for business partners, despite proper credit master data maintenance. 
  • How to configure Credit check at the PGI level.

Environment

SAP S/4HANA Cloud Public Edition

Reproducing the Issue

  1. Create a sales order.

  2. Save and create the delivery.

  3. Perform PGI documents and observe that system is allowing PGI without any credit block.

Cause

The credit check must effectively block the process at the sales order stage or the outbound delivery stage, as this is the last useful point to prevent picking and physical loss of goods. Blocking only Post Goods Issue (PGI) is too late, merely hindering the invoice. The system's standard design ensures that a negative credit check result upon saving the sales order or delivery automatically sets a block on the document and creates a Documented Credit Decision (DCD) for subsequent resolution.

 

Resolution

To do a credit check at the PGI stage a workaround setting should be maintained in the configuration activity Define Automatic Credit Control (SSCUI 101518).

1. Configure Sales Order Check (Credit Group 01)

The objective here is to provide a Warning Message during sales order creation without blocking the order.

  • For the relevant Sales Document Type (e.g., OR) and associated Risk Class:

    • Set the Credit Group to 01.

    • Set SAP Credit Mngt (Check Active) to True (e.g., X).

    • Set Reaction to A. (This raises a Warning Message during order creation).

    • Set Status/Block (Set Block) to Blank. (This ensures the order is not blocked).

2. Configure Delivery Creation Check (Credit Group 02)

The objective here is to apply a soft block to the delivery immediately upon creation, which prevents subsequent picking/packing.

  • For Delivery Type LF:

    • Set the Credit Group to 02.

    • Set SAP Credit Mngt (Check Active) to True (e.g., X).

    • Set Reaction to Blank. (This suppresses the error message during delivery creation).

    • Set Status/Block (Set Block) to True (e.g., X). (This sets the credit block on the delivery and creates a Documented Credit Decision (DCD)).

3. Configure PGI/Subsequent Function Check (Credit Group 03)

The objective here is to apply a hard block—raising an explicit error message when the user attempts picking or Post Goods Issue (PGI).

  • For Delivery Type LF:

    • Set the Credit Group to 03.

    • Set SAP Credit Mngt (Check Active) to True (e.g., X).

    • Set Reaction to B. (This raises an Error Message to the user).

    • Set Status/Block (Set Block) to True (e.g., X).

Important Process Notes

  • PGI Block: The error message from Credit Group 03 will block subsequent functions (Picking/PGI). PGI can only proceed after the Credit Controller releases the related DCD generated in Step 2.

  • Best Practice: Always use Credit Groups 02 and 03 together for delivery-related checks. Using only one group may lead to inconsistent or incomplete credit control.

 

Keywords

Credit block, PGI, Post Goods Issue, credit check not working, SSCUI 101518, credit limit, SAP S/4HANA Cloud Public Edition, define automatic credit control, risk class, credit group, SAP Credit Management, finance, configuration, credit control, sales order, delivery. , KBA , FIN-FSCM-CR-2CL , Credit Management (Public Cloud) , SD-BF-CM-2CL , Credit Management (Public Cloud) , Problem

Product

SAP S/4HANA Cloud Public Edition all versions