Routes every quote whose discount passes the band to the sales manager and then pricing, and returns the approved status and discount to the quote.
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 |
|---|---|---|---|
| Quotation | VBAK · VBAP (VBTYP = 'B') | VBAK.NETWR (value) · KONV/PRCD_ELEMENTS (KSCHL = 'K007') (discount) · VBAK.VBELN (number) · VBAK.KUNNR (customer) | 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 |
| Price condition | A004 · A005 · KONP (condition records) · PRCD_ELEMENTS | A004.MATNR (material) · A005.KUNNR (customer) · KONP.KBETR (amount) · KONP.KONWA (unit) | 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 |
In plain words: A quote saved with a line discount above 15 percent, or a quote value above 250,000.
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 KONV/PRCD_ELEMENTS (KSCHL = 'K007') > 15 or VBAK.NETWR > 250000 # the same criterion in canonical fields {quote.discount} > 15 or {quote.value} > 250000
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 |
|---|---|---|
| Quotation | approval status, approved discount per line and approver note written to the quote; a returned quote goes back to draft with the note | BAPI_QUOTATION_CREATEFROMDATA2 · BAPI_CUSTOMERQUOTATION_CHANGE |
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 |
|---|---|---|
| Quotation | VBAK · VBAP (VBTYP = 'B') | KONV for conditions |
| Customer master | KNA1 · KNB1 · KNVV | same tables |
| Price condition | A004 · A005 · KONP (condition records) · PRCD_ELEMENTS | KONV for conditions |
| Sales order line | VBAK · VBAP · VBEP | same tables |
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.
