calculate-loan

01 Loan payments

Credit Limit Table in SAP: Where to Find It

Guide 01-17609 · Updated · Step by step

SAP does not use one universal “credit limit table” for every system: the relevant table depends on whether credit management is the classic SD/FI-AR setup or SAP Credit Management in S/4HANA. In classic systems, customer credit data is commonly held in KNKK; in S/4HANA, credit account data is generally represented by UKMBP_CMS and related Credit Management objects, so confirm the release and configuration before relying on a table name.

Why There Is More Than One Answer

SAP’s credit management model has changed over time. Classic credit management, often called FI-AR credit management or SD credit management, stores credit-control-area-specific customer data and evaluates sales documents against it. SAP Credit Management, introduced as the strategic model in newer SAP environments and used in S/4HANA, uses business partner records and credit segments rather than relying on the classic customer/credit-control-area arrangement in the same way.

As a result, “the credit limit table” can mean different things: the master record that stores a limit, a table containing credit exposure or open items, a customizing table, or a view/API used by a particular application. A table name found in one system may not be present, populated, or authoritative in another.

Classic SAP: KNKK

For classic credit management, KNKK is the commonly referenced customer credit-management master table. Its records are associated with a customer and a credit control area. The field most often used to identify the credit limit is KLIMK. Other credit-management attributes may be present in the same record, but the exact fields used in a process depend on the SAP release and configuration.

A credit control area is an organizational unit for credit management. A customer can therefore have different credit data—and potentially different limits—in different credit control areas. When looking up a customer, identify the relevant credit control area as well as the customer number; searching only by customer can lead to an incomplete or misleading result.

  • KNKK: classic customer credit data, including the credit limit field commonly identified as KLIMK.
  • KNKA: classic general credit-management data for a customer; it is not a substitute for the credit-control-area-specific record in KNKK.
  • KNB1: customer company-code data, not the general answer for a credit limit.

These names describe common classic-system structures. They should not be treated as a guarantee that a particular system’s applications read or update those tables directly.

S/4HANA: Business Partner and Credit Segments

In SAP S/4HANA Credit Management, credit data is maintained in the business partner framework. UKMBP_CMS is commonly associated with central business-partner credit-management data, while UKMBP_CMS_SGM is commonly associated with credit-segment-specific data. Credit limits are managed by credit segment, so the business partner and the applicable segment both matter.

This is not a simple one-for-one replacement lookup for every classic table. S/4HANA implementations can use compatibility views, application services, or other release-dependent data structures. SAP’s supported applications and released APIs are generally safer ways to read or change business data than direct table updates. Check the relevant S/4HANA release documentation and data dictionary before building a report or integration.

How to Verify the Right Table and Field

Start by establishing which credit-management model the system actually uses. A system’s product name alone may not settle the question: migrations, activated components, and custom development can affect what is in use. Then check the application where an authorized user views the customer or business partner credit data and compare that display with the data dictionary.

  1. Identify the SAP product, release, and active credit-management approach (classic or SAP Credit Management).
  2. Find the customer or business partner key and, where applicable, the credit control area or credit segment.
  3. Use SE11 or the ABAP Data Dictionary to inspect the relevant table or view, including field definitions and key fields.
  4. Use SE16N or an approved reporting tool for a read-only check, subject to your organization’s access controls.
  5. Compare the result with the supported credit-management application; investigate mismatches before using the data operationally.

For a classic lookup, a developer might inspect KNKK using the customer and credit control area, then review KLIMK. For S/4HANA, the equivalent investigation typically starts with the business partner and its credit segment, and confirms the relevant structure in that release. Do not assume the displayed amount’s currency or meaning without checking field documentation and application behavior.

Credit Limit Is Not the Same as Credit Exposure

A stored limit is only one part of a credit decision. Exposure can include open receivables, sales orders, deliveries, billing documents, or other commitments, depending on the configuration and credit-check rules. Therefore, a customer can have a limit in master data while still being blocked because current exposure exceeds the available amount, or because another configured check has failed.

For example, a classic customer might have a limit recorded for one credit control area, while an order is checked under a different area or uses a different exposure calculation. In Credit Management, a business partner might have different limits across credit segments. A report that reads only the limit field cannot establish how much credit is currently available.

Common Lookup and Reporting Problems

  • Wrong model: Looking for KNKK in an S/4HANA Credit Management process can miss the authoritative data model.
  • Missing organizational key: Omitting the credit control area or credit segment can return the wrong record or no record.
  • Confusing limit with exposure: The master limit does not by itself show open commitments or available credit.
  • Currency assumptions: Check the field definition and application display; do not infer currency from a numeric value alone.
  • Direct table changes: Updating database records directly can bypass application checks and create inconsistent data. Use the supported SAP application, interface, or approved business process to maintain credit data.
  • Authorization or buffering issues: A user’s inability to see a record does not prove it is absent; access, filters, and reporting logic can affect results.

If a report must support multiple releases or both credit-management models, avoid hard-coding a single table as the universal source. Document the release scope, organizational keys, currency handling, and whether the report shows a master limit, exposure, or calculated availability.

Frequently Asked Questions

What is the SAP table for a customer credit limit?
In classic SAP credit management, KNKK is the commonly used customer credit-data table, and KLIMK is the commonly referenced credit-limit field. In S/4HANA Credit Management, check business-partner and credit-segment structures such as UKMBP_CMS and UKMBP_CMS_SGM for the relevant release.

What is the credit limit field in KNKK?
KLIMK is commonly identified as the credit limit field in KNKK. Verify its definition and the related key fields in the system’s data dictionary before using it in custom code or reporting.

Does KNKK work in SAP S/4HANA?
It may exist or be relevant in some environments, but it is not a universal source for S/4HANA Credit Management. Determine which model is active and use the structures and supported interfaces documented for that release.

Where is the S/4HANA credit limit stored?
Credit Management data is associated with the business partner and credit segment; UKMBP_CMS and UKMBP_CMS_SGM are commonly referenced structures. Confirm exact usage in the system’s release documentation and data dictionary.

Why does a customer have a credit limit but an order is blocked?
A limit alone does not determine the result. Exposure, the credit control area or segment, configured checks, and document status can affect the order’s credit decision.

Practical Takeaway

Use KNKK/KLIMK as the starting point for a classic credit-management lookup, not as a universal SAP answer. For S/4HANA Credit Management, investigate the business partner’s credit segment and confirm the relevant data model for the installed release. For dependable reports and integrations, prefer supported SAP applications or released interfaces and clearly distinguish the maintained credit limit from exposure and available credit.

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

The whole Loan payments section →