SD Program Custom development Enhancement TR · Türkiye

Customer Credit Limit Upload and Cheque-Aware Credit Check

Short answer: A development that updates customer credit limits in bulk from Excel and adds post-dated cheques in the portfolio, a per-customer cheque quota and exceptions by payment terms and material type to the credit check in the sales order. Credit segment limits are updated in S/4HANA, credit control area limits in ECC.

Estimated effort
L · 12–18 working days
System
ECC and S/4HANA
Tables
10
Scope
TR
Built by
NeKuDos Teknoloji
Last updated

Why is the standard not enough?

In S/4HANA the credit limit is kept on the business partner per credit segment and updated one by one; there is no tool to update the yearly limit revision of hundreds of customers from Excel. Standard credit exposure counts open items, orders and deliveries; it does not cover, with one rule set, tracking post-dated cheques common in Turkey within a separate quota or excluding documents with cash-in-advance payment terms or certain material types. The custom development solves both needs in one installation.

Who uses it? Credit and risk management teams, finance managers, sales operations teams and SD/FSCM consultants.

Closest standard alternatives

  • FD32 Change Customer Credit Management. Changes a customer's credit limit one by one in ECC; in S/4HANA it is replaced by business partner credit management and knows no cheque quota.
  • VKM1 Blocked SD Documents. Releases credit-blocked orders; does not explain the block in terms of the cheque quota.

Tables used

The tables the program reads and updates. ECC and S/4HANA differences are marked separately.

TableRoleAccessSystem
UKMBP_CMS_SGMSAP Credit Management: Master Data for Credit AccountLimit and valid-to date per credit segment (S/4HANA, FSCM)Read / writeS/4HANA only
UKMBP_CMSSAP Credit Management: Credit Master Data for PartnerCredit profile and risk class of the business partner (S/4HANA)ReadS/4HANA only
UKM_ITEMCredit Management: Line ItemsOpen orders, deliveries and invoices in the credit exposure (S/4HANA)ReadS/4HANA only
KNKKCustomer Master Credit Management: Control Area DataCustomer limit per credit control area (ECC classic credit management)Read / writeECC only
BSIDCustomer Open ItemsCheques in the portfolio: open items with special G/L indicatorReadECC + S/4
BSEDBill of Exchange Fields Document SegmentCheque maturity, bank and cheque numberReadECC + S/4
VBAKSales Document HeaderOrder type, order value and credit control areaReadECC + S/4
VBKDSales Document: Business DataPayment terms of the orderReadECC + S/4
MARAGeneral Material DataMaterial type exceptionReadECC + S/4
T052Terms of PaymentPayment terms definition (cash in advance, cheque, letter of credit)ReadECC + S/4

S/4HANA notes

  • KNKK → UKMBP_CMS_SGM: In S/4HANA FI-AR-CR credit management is replaced by SAP Credit Management (FIN-FSCM-CR); credit segment data is kept per business partner in UKM tables such as UKMBP_CMS_SGM.
  • BSID → I_OperationalAcctgDocItem: In S/4HANA BSID is no longer filled as a separate index table; reads work through a compatibility view of the same name. For new developments the I_OperationalAcctgDocItem CDS view is recommended.

BAPIs and functions used

  • TEXT_CONVERT_XLS_TO_SAPConvert Excel File to SAP Format. Reads the limit file from Excel
  • BAPI_AR_ACC_GETOPENITEMSCustomer Account Open Items at Key Date. Optionally reads the customer's open items and cheques

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
P_FILELimit fileSingle value—YesC:\kredi\limit_revizyonu_2027.xlsx
P_SGMNTCredit segmentSingle valueUKMBP_CMS_SGM-CREDIT_SGMNTYes1000
P_THRESIncrease percentage that needs approvalSingle value—No25
P_TESTTest runCheckbox—NoX

Input file columns

The columns of the upload template and the SAP fields they are written to. Columns with an asterisk are mandatory.

#ColumnTarget fieldRequired
1Business partnerUKMBP_CMS_SGM-PARTNERYes
2Credit segmentUKMBP_CMS_SGM-CREDIT_SGMNTYes
3New credit limitUKMBP_CMS_SGM-CREDIT_LIMITYes
4Valid toUKMBP_CMS_SGM-LIMIT_VALID_DATENo
5Cheque quotaBy rule Highest post-dated cheque amount accepted for the customerNo
6CommentBy rule Reason for the revisionNo

Sample upload file

1Business partner *Credit segment *New credit limit *Valid toCheque quotaComment
2100020014510002,500,00012/31/20271,500,000Yearly revision
310003002101000800,00006/30/20270Bank guarantee renewed
4100030038810004,000,00012/31/20272,500,000Turnover growth
A view built with fictional sample data; not real system data.

Result list columns

#ColumnSource
1Business partnerUKMBP_CMS_SGM-PARTNER
2Credit segmentUKMBP_CMS_SGM-CREDIT_SGMNT
3Old limitCalculated UKMBP_CMS_SGM-CREDIT_LIMIT before the update (KNKK-KLIMK in ECC)
4New limitCalculated Limit from the file
5Change %Calculated (new − old) / old × 100
6Cheques in portfolioCalculated Sum of not-yet-due BSID items with the cheque indicators from setup
7Cheque quotaCalculated Quota from the file
8StatusCalculated Ready, updated, approval needed or error
9MessageCalculated Check or update message

Sample result list

Business partnerCredit segmentOld limitNew limitChange %Cheques in portfolioCheque quotaStatusMessage
100020014510002,000,0002,500,000251,320,0001,500,000Ready
100030021010001,000,000800,000-2000ReadyNo cheques accepted
100030038810002,500,0004,000,000602,140,0002,500,000Approval neededIncrease threshold exceeded
100030099910000500,000000ErrorBusiness partner has no credit profile in this segment
A view built with fictional sample data; not real system data.

How does the program work?

  1. Limit upload: the Excel file holds business partner, credit segment, new limit, valid-to date, cheque quota and a comment. In S/4HANA the business partner and segment are checked in UKMBP_CMS_SGM; the limit and valid-to date are updated through the FSCM credit management API (CL_UKM_BUPA_FACTORY and CL_UKM_ACCOUNT), so the standard change documents are created. In ECC with classic credit management the KNKK limit is changed with CREDITLIMIT_CHANGE.
  2. The test run shows old and new limit, the change in percent and rows above the approval threshold set during setup; the live run writes the results to the application log.
  3. Cheque risk: the customer’s post-dated cheques in the portfolio are read from open items by the special G/L indicators set during setup (BSID-UMSKZ); cheque maturity and bank come from BSED. In S/4HANA BSID is read as a compatibility view on ACDOCA and BSEG.
  4. Adding to exposure: in S/4HANA the cheque risk is added to the credit exposure formula with the UKM_EV_FORMULA BAdI; in ECC classic credit control the user exit in LVKMPFZ1 is used. The cheque quota is checked separately: if the order’s payment terms are flagged as payment by cheque, cheques in the portfolio plus this order’s value are compared with the quota.
  5. Document-based exceptions: for cash-in-advance or letter-of-credit payment terms (VBKD-ZTERM), material types chosen during setup such as samples, scrap or internal use (MARA-MTART) and certain order types, the credit check is skipped or only gives a warning through the UKM_R3_ACTIVATE BAdI.
  6. The result shows up in the order as the standard credit block; the block is released with VKM1, and the rule that caused the block is written to the order text and the log.

Performance notes

Do not calculate cheque risk by scanning all open items on every order save; do a narrow read by customer and special G/L indicator and buffer it within the same LUW. In the mass limit upload, update business partners in packages and issue COMMIT WORK after each package.

Features

  • Export to Excel
  • Test mode (check without posting) Old and new limit, change and threshold check are visible before the update.
  • Line-by-line result and error log Limit changes and the rule that blocked an order are written to the log.
  • Download failed lines as a separate file

Authorization objects

  • F_UKM_SGMTChanging limits in a credit segment (S/4HANA, FSCM)
  • F_KNKK_BEDChanging customer limits in a credit control area (ECC)
  • S_APPL_LOGDisplaying the application log

Frequently asked questions

Cheques are already open items; why are they counted separately?

Standard exposure counts the open items on the receivables account, but in many setups received cheques are tracked separately with a special G/L indicator and do not enter the exposure. The development adds not-yet-due cheques to the exposure by the rule chosen during setup and also checks a per-customer cheque quota.

Are limit increases updated without approval?

An increase threshold is set during installation. Rows above it are flagged 'approval needed' in the test run, and only for these rows an authorized user has to run a separate approval step; the other rows are updated directly.

What changes when moving from ECC to S/4HANA?

In ECC classic credit management works with KNKK and user exits; in S/4HANA credit management runs through FSCM on the business partner and credit segment. The rule set and the Excel format stay the same; only the place where the limit is written and the point where exposure is extended change.

Related reports

SD Report Custom ALV report

Credit-Blocked Sales Orders by Value and Age Report

A custom ALV report that groups credit-blocked sales orders per credit account and shows the blocked order value, the age of the oldest block, the …

VBUK · VBAK · VBAP · VBUP

Let us build this program for your system

Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.

Related report: Customer Credit Limit Upload and Cheque-Aware Credit Check