Manufacturing and quality on S/4HANA

Production schedule change on SAP S/4HANA

Lets a planner move firmed production orders on a live schedule, shows the effect on components and customer dates, collects the signatures and writes the new dates to the ERP.

SCREENSDATA HANDLERSS/4HANA · READ IN PLACES01 Change requestS02 ScheduleS03 EffectsS04 Production checkS05 Sales updateS06 ApprovalS07 Boarddh_production_orderProduction orderAFKO · AFPO · AFVCdh_planned_orderPlanned orderPLAFdh_sales_order_lineSales order lineVBAK · VBAP · VBEPdh_stock_positionStock positionMARD · MCHB · MATDOC_EXTRACTdh_routingRoutingPLKO · PLPO · CRHDWRITE BACK TO S/4HANAProduction order → BAPI_PRODORD_CHANGE · BAPI_PRODORDCONF_CREATE_TTPlanned order → BAPI_PLANNEDORDER_CHANGE · BAPI_PLANNEDORDER_CREATESales order line → BAPI_SALESORDER_CHANGE · BAPI_SALESORDER_CREATEFROMDAT2rows 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
7
screens on those rows
catalogue
7 days
to production-grade
estimate
3
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
Production orderAFKO · AFPO · AFVCAFKO.AUFNR (number) · AFPO.MATNR (material) · AFPO.PSMNG (qty) · AFKO.GSTRP (start)live; change capture where enabled
Planned orderPLAFPLAF.PLNUM (number) · PLAF.MATNR (material) · PLAF.GSMNG (qty) · PLAF.PSTTR (start)live; change capture where enabled
Sales order lineVBAK · VBAP · VBEPVBAK.VBELN (number) · VBAP.POSNR (line) · VBAK.KUNNR (customer) · VBAP.MATNR (material)live; change capture where enabled
Stock positionMARD · MCHB · MATDOC_EXTRACTMARD.MATNR (material) · MARD.WERKS (plant) · MARD.LGORT (sloc) · MARD.LABST (on hand)live; change capture where enabled
RoutingPLKO · PLPO · CRHDPLKO.PLNNR (group) · PLPO.VORNR (operation) · CRHD.ARBPL (work center) · PLPO.VGW01 (setup)live; change capture where enabled
The trigger

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

In plain words: A planner or production lead starts a change on S01 for a work center and a window; a breakdown recorded on the floor screen starts one as well.

This app starts from a screen, so the first read happens when the instance opens; the criteria on the arrows use the fields above.

Start

A planner or production lead starts a change on S01 for a work center and a window; a breakdown recorded on the floor screen starts one as well. The instance then reads its rows from S/4HANA through the handlers above.

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
Production orderstart and finish dates changed through the production order interfaceBAPI_PRODORD_CHANGE · BAPI_PRODORDCONF_CREATE_TT
Planned orderfirmed planned orders rescheduledBAPI_PLANNEDORDER_CHANGE · BAPI_PLANNEDORDER_CREATE
Sales order lineconfirmed dates updated on the affected customer ordersBAPI_SALESORDER_CHANGE · BAPI_SALESORDER_CREATEFROMDAT2
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
Production orderAFKO · AFPO · AFVCsame tables
Planned orderPLAFsame table
Sales order lineVBAK · VBAP · VBEPsame tables
Stock positionMARD · MCHB · MATDOC_EXTRACTMARD · MCHB · MBEW
RoutingPLKO · PLPO · CRHDsame tables
Nearby

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

Production schedule change on

Other apps on S/4HANA

Terms on this page

Firmed orderA production or planned order the planning run leaves in place; a person changes its dates and quantity.
Work centerThe machine or line where an operation runs; the routing states its setup and run time.
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.