Procurement on S/4HANA

Contract renewal and approval on SAP S/4HANA

Opens a case 90 days before a purchasing contract expires, shows consumption against target value, and carries the renew, renegotiate or lapse decision through legal and the category lead.

SCREENSDATA HANDLERSS/4HANA · READ IN PLACES01 Expiring contractsS02 Contract reviewS03 Supplier termsS04 Legal reviewS05 ApprovalS06 Trackerdh_purchasing_contractPurchasing contractEKKO · EKPO (BSTYP = 'K' / 'L')dh_purchase_order_linePurchase order lineEKKO · EKPO · EKET · EKBEdh_supplier_masterSupplier masterLFA1 · LFB1 · LFM1 (business partner inS/4)dh_supplier_invoiceSupplier invoiceRBKP · RSEG (supplier invoices)WRITE BACK TO S/4HANAPurchasing contract → BAPI_CONTRACT_CHANGE · BAPI_CONTRACT_CREATEPurchase order line → BAPI_PO_CHANGE · BAPI_PO_CREATE1rows stay in S/4HANA · access rules applied at read time · each write acknowledged and logged
The screens of the app, the data handler behind each, and the S/4HANA object it reads in place. Writes below the line go through released interfaces with an acknowledgement.
4
objects read in place from S/4HANA
catalogue
6
screens on those rows
catalogue
5 days
to production-grade
estimate
2
objects written back
catalogue
0
rows copied to build it
product
What the app reads

The S/4HANA objects behind each handler

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.

ObjectRead fromFields the app usesFreshness
Purchasing contractEKKO · EKPO (BSTYP = 'K' / 'L')EKKO.KDATE (valid to) · EKKO.EBELN (number) · EKKO.LIFNR (vendor) · EKKO.KTWRT (target value)live; change capture where enabled
Purchase order lineEKKO · EKPO · EKET · EKBEEKKO.EBELN (number) · EKPO.EBELP (line) · EKKO.LIFNR (vendor) · EKPO.MATNR (material)live; change capture where enabled
Supplier masterLFA1 · LFB1 · LFM1 (business partner in S/4)LFA1.LIFNR (id) · LFA1.NAME1 (name) · LFA1.LAND1 (country) · LFA1.SPERR (block)live; change capture where enabled
Supplier invoiceRBKP · RSEG (supplier invoices)RBKP.BELNR (number) · RBKP.LIFNR (vendor) · RBKP.RMWWR (amount) · RSEG.EBELN (po)live; change capture where enabled
The trigger

The start criterion in S/4HANA's own fields

In plain words: A purchasing contract whose validity ends within the next 90 days.

The criterion runs in S/4HANA through the data handler, so only the matching rows return. The editor shows the rows it selects, and their count, as it is written.

# start criterion in S/4HANA fields
EKKO.KDATE <= today + 90 and EKKO.KDATE >= today

# the same criterion in canonical fields
{contract.valid_to} <= today + 90 and {contract.valid_to} >= today
What the app writes back

Through released interfaces

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.

ObjectWhat changesInterface
Purchasing contractvalidity and target value extended, or a new contract created with the agreed prices; a lapse recorded with the reasonBAPI_CONTRACT_CHANGE · BAPI_CONTRACT_CREATE
Purchase order lineopen order lines dated beyond expiry moved to the new contract or closedBAPI_PO_CHANGE · BAPI_PO_CREATE1
Acknowledged and logged

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.

Access and prerequisites

What is in place before the first build

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.

  • An SAP user for the connector with read authorisation on the objects the app uses
  • The BAPIs the app writes with, enabled for that user
  • Network path to the application server (PrivateLink or VPN)
  • Change capture switched on for the objects that should refresh within minutes
Register the handlers4 objects from the catalog; each shows its rows at once.
Also on SAP ECC

The same app on SAP ECC

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.

ObjectOn S/4HANAOn SAP ECC
Purchasing contractEKKO · EKPO (BSTYP = 'K' / 'L')same tables
Purchase order lineEKKO · EKPO · EKET · EKBEsame tables
Supplier masterLFA1 · LFB1 · LFM1 (business partner in S/4)LFA1/LFB1/LFM1 vendor master, XK01 via BAPI
Supplier invoiceRBKP · RSEG (supplier invoices)same tables
Nearby

This app on other systems, and other apps on S/4HANA

Contract renewal and approval on

Other apps on S/4HANA

Terms on this page

Target valueThe total value a contract allows call-offs against.
Call-offA purchase order placed against a contract, drawing down its target value.
Read in placeThe rows stay in S/4HANA; the handler sends the filter and the columns and S/4HANA returns the matching rows.
Questions

Does this app copy data out of S/4HANA?

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.

What does S/4HANA need to allow?

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.

Can I run it on SAP ECC as well?

Yes. The screens, criteria and roles stay; the handlers are re-bound to the other system's objects, listed above.

See this app on your data

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.