Takes a request for a higher credit limit from the seller through the credit analyst to the approver, updates the credit profile and releases the orders the new limit covers.
Tables are read in place through the SAP connector, using released read interfaces; changed rows arrive through change capture where the basis team allows it. The rows stay in SAP.
| Object | Read from | Fields the app uses | Freshness |
|---|---|---|---|
| Credit profile | UKMBP_CMS_SGM (FSCM credit) · KNKK | UKMBP_CMS_SGM.PARTNER (customer) · UKMBP_CMS_SGM.CREDIT_LIMIT (limit) · UKM_TOTALS.TOTAL_EXPOSURE (exposure) · UKMBP_CMS.RISK_CLASS (risk class) | live; change capture where enabled |
| Customer master | KNA1 · KNB1 · KNVV | KNA1.KUNNR (id) · KNA1.NAME1 (name) · KNA1.LAND1 (country) · KNVV.VKORG (sales org) | live; change capture where enabled |
| Sales order line | VBAK · VBAP · VBEP | VBAK.VBELN (number) · VBAP.POSNR (line) · VBAK.KUNNR (customer) · VBAP.MATNR (material) | live; change capture where enabled |
| Quotation | VBAK · VBAP (VBTYP = 'B') | VBAK.VBELN (number) · VBAK.KUNNR (customer) · VBAK.NETWR (value) · VBAK.BNDDT (valid to) | live; change capture where enabled |
In plain words: A seller submits S01 for a customer, usually from a blocked order or ahead of a large quote.
This app starts from a screen, so the first read happens when the instance opens; the criteria on the arrows use the fields above.
A seller submits S01 for a customer, usually from a blocked order or ahead of a large quote. The instance then reads its rows from S/4HANA through the handlers above.
Writes go through released BAPIs and IDocs. Each call returns a document number or an error message, and the app records both beside the decision.
| Object | What changes | Interface |
|---|---|---|
| Credit profile | new limit and valid-to date written to the credit profile; risk class updated when changed | UKM_DB_UKMBP_CMS_SGM_UPDATE via released FM · BAPI_CREDIT_LIMIT_CHANGE (ECC) |
| Sales order line | credit block released on the orders the new limit covers | BAPI_SALESORDER_CHANGE · BAPI_SALESORDER_CREATEFROMDAT2 |
Each write stores the identifier S/4HANA returns beside the decision, the person and the time, so the log answers who changed what, and the reconciliation shows it arrived.
SAP roles are mapped to Lima access policies once. A buyer who sees purchasing organisation 1000 in SAP sees the same rows in the app.
On SAP ECC the same objects live in the classic tables named beside each row; MATDOC becomes MKPF and MSEG, ACDOCA becomes BKPF and BSEG. The BAPIs are the same.
| Object | On S/4HANA | On SAP ECC |
|---|---|---|
| Credit profile | UKMBP_CMS_SGM (FSCM credit) · KNKK | KNKK.KLIMK |
| Customer master | KNA1 · KNB1 · KNVV | same tables |
| Sales order line | VBAK · VBAP · VBEP | same tables |
| Quotation | VBAK · VBAP (VBTYP = 'B') | KONV for conditions |
The screens read through handlers that leave the rows in S/4HANA. History the app needs at scale is landed in the lake by the Backbone, which is the exception by design.
The prerequisites above: an integration identity with read rights on the objects listed and write rights on the interfaces named, connectivity, and the scopes agreed with the process owner.
Yes. The screens, criteria and roles stay; the handlers are re-bound to the other system's objects, listed above.
Bring the process and the systems it touches. In the first session we register the data handlers, draw the levels or the lanes and run the first screen on your live rows.
