Procurement on S/4HANA

Purchase requisition approval on SAP S/4HANA

Routes each requisition line through value-banded approvals with a live budget check and a buyer's source check, and sets the release code back in the ERP.

SCREENSDATA HANDLERSS/4HANA · READ IN PLACES01 My requisitionsS02 ApprovalS03 Buyer checkS04 Budget exceptionS05 Mobile approvalS06 Trackerdh_purchase_requisitionPurchase requisitionEBANdh_budget_lineBudget lineBPGE · BPJA (budget) · ACDOCP (plandata)dh_cost_centerCost centerCSKS · CSKTdh_material_masterMaterial masterMARA · MARC · MAKTdh_purchasing_contractPurchasing contractEKKO · EKPO (BSTYP = 'K' / 'L')WRITE BACK TO S/4HANAPurchase requisition → BAPI_PR_CREATE · BAPI_REQUISITION_RELEASE_GENrows 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.
5
objects read in place from S/4HANA
catalogue
6
screens on those rows
catalogue
3 days
to production-grade
estimate
1
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
Purchase requisitionEBANEBAN.FRGKZ (release) · EBAN.BANFN (number) · EBAN.BNFPO (line) · EBAN.MATNR (material)live; change capture where enabled
Budget lineBPGE · BPJA (budget) · ACDOCP (plan data)BPGE.OBJNR (object) · BPGE.WTGES (amount) · BPJA.GJAHR (year) · ACDOCP.VERSION (version)live; change capture where enabled
Cost centerCSKS · CSKTCSKS.KOSTL (id) · CSKT.KTEXT (name) · CSKS.VERAK (owner) · CSKS.BUKRS (company)live; change capture where enabled
Material masterMARA · MARC · MAKTMARA.MATNR (id) · MAKT.MAKTX (desc) · MARA.MTART (type) · MARC.WERKS (plant)live; change capture where enabled
Purchasing contractEKKO · EKPO (BSTYP = 'K' / 'L')EKKO.EBELN (number) · EKKO.LIFNR (vendor) · EKKO.KDATE (valid to) · EKKO.KTWRT (target value)live; change capture where enabled
The trigger

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

In plain words: A requisition line saved in the ERP whose release is still open.

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
EBAN.FRGKZ = open

# the same criterion in canonical fields
{pr.release} = open
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
Purchase requisitionrelease code set for each approval level; rejection recorded with the reason; contract number and price added to the lineBAPI_PR_CREATE · BAPI_REQUISITION_RELEASE_GEN
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 handlers5 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
Purchase requisitionEBANsame table
Budget lineBPGE · BPJA (budget) · ACDOCP (plan data)BPGE · BPJA · COSP
Cost centerCSKS · CSKTsame tables
Material masterMARA · MARC · MAKTsame tables
Purchasing contractEKKO · EKPO (BSTYP = 'K' / 'L')same tables
Nearby

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

Purchase requisition approval on

Other apps on S/4HANA

Terms on this page

Release codeThe mark on a requisition that says which approval level has agreed to it; the ERP holds one per level.
BandThe value range that sets how many approvals a line needs.
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.