In SAP, the main transaction for maintaining a customer’s credit limit depends on the credit-management setup: use UKM_BP for SAP Credit Management in SAP S/4HANA and newer implementations, or FD32 for classic credit management in SAP ERP. These transactions manage credit data; they are not calculators, and the right one depends on which SAP credit-management model your system uses.
Which SAP transaction should you use?
UKM_BP is the primary transaction associated with maintaining business partner credit data in SAP Credit Management. In the relevant business partner roles and credit-management areas, authorized users can review or maintain credit information, including credit limits. The exact screens and fields available depend on the installed SAP product, configuration, and user authorizations.
FD32 is the classic transaction for changing a customer’s credit-management data in SAP ERP. It is commonly used in the classic credit-control-area model, where a customer’s credit limit and related settings are maintained in relation to a credit control area. Some systems may retain this model during upgrades or coexistence with newer functionality.
- Use UKM_BP when the system is configured for SAP Credit Management and credit data is maintained for business partners.
- Use FD32 when the system uses classic SAP ERP credit management and the customer’s data is maintained by credit control area.
- If neither transaction is available, check your system’s product version, configuration, menu or role assignments, and authorization with your SAP administrator.
What a credit limit means in SAP
A credit limit is a configured ceiling used in credit-management checks for a customer or business partner. SAP can compare relevant credit exposure with the maintained limit when processing business documents. Depending on the configured process, a check may take account of items such as open orders, deliveries, and receivables; the exact exposure calculation is system-dependent.
The limit is not necessarily the same as a customer’s total outstanding invoice balance. Exposure can include commitments that have not yet become receivables, and configuration determines which document types and values count. A user should therefore check the credit account’s exposure and the system’s credit-check settings rather than infer available credit from one balance alone.
Classic credit management: FD32
In classic credit management, credit data is generally maintained for a customer in the context of a credit control area. FD32 is the transaction commonly used to display or change that data. The screens can include general credit information as well as data specific to a credit control area; the fields shown depend on the system and the user’s access.
For example, if a customer has a limit of 50,000 in the relevant currency and the configured credit exposure reaches 47,000, only 3,000 remains before the limit is reached, assuming those figures are measured on the same account and under the same exposure rules. That arithmetic does not establish whether a sales order will pass: the check can also depend on risk category, credit horizon, document settings, and other configuration.
Before saving a change in FD32, confirm that the customer and credit control area are correct. A limit entered against the wrong area may not affect the documents or organizational scope the user intended.
SAP Credit Management: UKM_BP
In SAP Credit Management, credit information is associated with a business partner and maintained through credit-management functions. UKM_BP is the transaction commonly used to open the business partner for credit-related maintenance. Depending on the system, users may need to select a relevant business partner role or credit segment to see the appropriate credit data.
Do not assume a credit segment is interchangeable with a classic credit control area. They belong to different credit-management models, and mappings or integration behavior depend on the implementation. A business partner may also have more than one relevant organizational credit context, so confirming the correct segment is important before editing a limit.
UKM_BP is not a universal screen with identical fields in every SAP release. If the expected credit-limit area is missing, the cause may be role selection, configuration, product version, or authorization—not necessarily an incorrect transaction code.
How to identify the right setup
Start by asking whether the system uses classic credit management or SAP Credit Management. Your SAP support team or system documentation can confirm the model and the relevant organizational unit. The transaction code alone cannot determine the correct limit field or scope.
- Check the SAP product and release and whether the system’s credit process is classic or based on SAP Credit Management.
- Identify the customer or business partner number and the relevant credit control area or credit segment.
- Open FD32 for classic maintenance or UKM_BP for the applicable business partner credit maintenance.
- Review the existing limit, currency, credit exposure, and organizational context before changing anything.
- Save only if authorized, then follow your organization’s approval and audit process.
Common access and data problems
If a transaction returns an authorization error, access must be granted through the organization’s SAP security process. Do not try another user’s account or bypass a role restriction. Credit limits can affect order processing and require appropriate approval.
If a limit appears not to affect an order, verify the customer or business partner, the credit control area or segment, and the document’s credit-check behavior. Also check whether exposure has been updated and whether the document is using the expected currency and organizational assignment. In a system with integrations or customized workflows, local support may need to inspect the configuration and application logs.
A frequent misconception is that changing a limit automatically releases every blocked document. A credit check can block a document for reasons beyond the numeric limit, and changing master credit data does not necessarily trigger a new check or release an existing block. Follow the configured recheck and release procedure.
Frequently Asked Questions
What is the T-code for changing a customer credit limit in SAP?
Use FD32 for classic SAP ERP credit management. Use UKM_BP when maintaining credit data through SAP Credit Management. Confirm the model in your system before making a change.
Is FD32 available in SAP S/4HANA?
Availability and use depend on the system’s release and credit-management setup. FD32 is associated with classic credit management; SAP Credit Management commonly uses UKM_BP. Ask your SAP administrator which model is active.
How do I view a credit limit in SAP?
Use the transaction appropriate to the system: FD32 for classic credit management or UKM_BP for SAP Credit Management. Select the correct customer or business partner and relevant credit control area or credit segment.
Why can’t I see the credit limit in UKM_BP?
Possible causes include selecting the wrong business partner role or credit segment, missing authorization, or a different system configuration or release. Your SAP support team can verify the setup.
Does changing the credit limit release a blocked sales order?
Not necessarily. A new credit check may be required, and the block can have other causes. Use the organization’s configured recheck and release process.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this section
- Cash-Out Refinance at U.S. Bank: Estimate the Cash$62,000.00
- VA Cash-Out Refinance Calculator and How It Works$405.53
- Cash-Out Refinance With a Second Lien?$405.53
- Cash-Out Refinance on a Second Home: Rules and Costs$405.53
- Cash-Out Refinance on a Second Home: Costs and Options$405.53
- Cash-Out Refinance Second Home Rates Explained$1,330.60