SAP Credit Management Business Partner Setup: UKM000, Risk Class and Credit Limit

In SAP S/4HANA Credit Management, the customer credit record is maintained through the Business Partner. A customer role alone is not enough. The payer needs the SAP Credit Management role and the minimum credit profile and segment data required by the check.

This walkthrough explains the structure and a reliable setup sequence.

Why UKM000 matters

UKM000 is the Business Partner role for SAP Credit Management. It exposes the credit profile and credit segment data needed by FSCM Credit Management.

SAP states that the UKM000 role must be active before credit master data can be processed. Its credit master data documentation identifies risk class, check rule and credit-limit settings as the minimum data for executing a credit check.

If transaction BP reports that the role is unavailable, do not continue by entering data in an unrelated customer view. Fix role availability and system configuration first.

Credit profile versus credit segment data

The credit profile contains information that applies to the business partner across credit segments. The credit segment section contains the account data for a specific segment.

Typical profile-level fields include:

• risk class;
• check rule;
• scoring or limit-calculation rule;
• customer credit group;
• special-attention or global control information.

Typical segment-level fields include:

• credit limit and currency;
• segment-specific block or control data;
• utilization and exposure information;
• analyst responsibility;
• collateral, insurance or check exceptions when used.

Keeping this distinction clear prevents a common mistake: maintaining a global profile but forgetting to create the segment against which the sales document checks.

Maintain the risk class

The risk class represents how the company categorizes the customer's credit risk. It participates in the SD automatic credit-control determination together with the credit account and the document settings.

Use categories that reflect an approved credit policy. Avoid treating risk classes merely as technical keys. Each class should have an owner, documented criteria and a review frequency.

For a controlled test, use a known risk class and confirm that it is transferred to the sales document. If the document shows no risk class, verify that the payer and credit account are correct before changing configuration.

Assign the check rule

The check rule tells SAP which checks to execute for the business partner. A rule contains one or more check steps, such as a static limit check, maximum document value or overdue-item check.

The rule should reflect policy, not convenience. A high-risk customer might require more checks, but the result also depends on the parameters maintained for the relevant credit segment.

SAP's settings for credit check confirms that risk class and check rule belong on the business partner credit profile, while limit data belongs in the segment.

Create the credit segment account

Add the credit segment that is mapped to the credit control area used by the sales transaction. Maintain the credit limit, currency and any relevant control fields.

Then verify that the segment is active for the intended process. The presence of a segment code is not enough if the sales area maps to another segment.

SAP's Manage Credit Accounts app can display profile information, segments, credit limit, exposure and utilization. This makes it a useful validation tool even when the original maintenance was performed in transaction BP.

A controlled setup and test sequence

Use the following order:

• Confirm the general Business Partner and customer roles.
• Add UKM000.
• Maintain the risk class and check rule on the credit profile.
• Add the required credit segment.
• Maintain its credit limit and currency.
• Confirm credit-control-area-to-segment mapping.
• Create a sales order for which the payer is the credit account.
• Review the credit status, exposure update and application log.

Test once below the limit and once above it. This distinguishes master-data failure from correct credit-policy behavior.

Governance and audit trail

Credit limits are financial controls. Restrict who can create, change and release them. SAP provides segment-level authorization through object F_UKM_SGMT and keeps change history for credit master-data fields.

Use an approval process for material limit changes, document temporary overrides and periodically review inactive segments or outdated limits. The technical setup should make the credit policy visible rather than bypass it.

For the full sales-order-to-credit-decision flow, read the [SAP S/4HANA Credit Management process guide](/blog/sap-s4hana-credit-management-process).