Supply chain and planning on S/4HANA

Excess and obsolete inventory review on SAP S/4HANA

Finds stock with cover above a threshold or a long idle time, gives each position to its planner with the options, and posts the decision in the ERP.

SCREENSDATA HANDLERSS/4HANA · READ IN PLACES01 Excess positionsS02 Position detailS03 DispositionS04 Finance reviewS05 Warehouse executionS06 Boarddh_stock_positionStock positionMARD · MCHB · MATDOC_EXTRACTdh_material_masterMaterial masterMARA · MARC · MAKTdh_forecastForecastPBIM · PBED (planned independentrequirements)dh_sales_order_lineSales order lineVBAK · VBAP · VBEPdh_batchBatchMCH1 · MCHA · MCHBdh_journal_lineJournal lineACDOCA (universal journal)WRITE BACK TO S/4HANAStock position → BAPI_GOODSMVT_CREATE (transfer, scrap, block)Material master → BAPI_MATERIAL_SAVEDATAJournal line → BAPI_ACC_DOCUMENT_POST · BAPI_ACC_DOCUMENT_REV_POSTrows 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.
6
objects read in place from S/4HANA
catalogue
6
screens on those rows
catalogue
6 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
Stock positionMARD · MCHB · MATDOC_EXTRACTMARD.LABST (on hand) · MBEW.SALK3 (value) · MARD.LAEDA (last movement) · MARD.MATNR (material)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
ForecastPBIM · PBED (planned independent requirements)PBED.PLNMG (qty) · PBIM.MATNR (material) · PBIM.WERKS (plant) · PBED.PDATU (period)live; change capture where enabled
Sales order lineVBAK · VBAP · VBEPVBAP.KWMENG (qty) · VBAK.VBELN (number) · VBAP.POSNR (line) · VBAK.KUNNR (customer)live; change capture where enabled
BatchMCH1 · MCHA · MCHBMCH1.CHARG (batch) · MCH1.MATNR (material) · MCH1.VFDAT (expiry) · MCH1.HSDAT (produced)live; change capture where enabled
Journal lineACDOCA (universal journal)ACDOCA.BELNR (document) · ACDOCA.RACCT (account) · ACDOCA.HSL (amount) · ACDOCA.RCNTR (cost center)live; change capture where enabled
The trigger

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

In plain words: A stock position worth more than 5,000 whose on-hand quantity covers more than 12 months of forecast and open orders, or whose last movement is older than 180 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
MBEW.SALK3 > 5000 and (MARD.LABST > 12 months of PBED.PLNMG + VBAP.KWMENG or MARD.LAEDA < today - 180)

# the same criterion in canonical fields
{stock.value} > 5000 and ({stock.on_hand} > 12 months of {forecast.qty} + {so.qty} or {stock.last_movement} < today - 180)
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
Stock positiontransfer to another plant or scrap posted as a goods movement; quantity moved to blocked stock while a decision is openBAPI_GOODSMVT_CREATE (transfer, scrap, block)
Material masterplant status set to phase-out so planning stops creating new ordersBAPI_MATERIAL_SAVEDATA
Journal linethe agreed reserve change posted as a journal at month endBAPI_ACC_DOCUMENT_POST · BAPI_ACC_DOCUMENT_REV_POST
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 handlers6 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
Stock positionMARD · MCHB · MATDOC_EXTRACTMARD · MCHB · MBEW
Material masterMARA · MARC · MAKTsame tables
ForecastPBIM · PBED (planned independent requirements)same tables
Sales order lineVBAK · VBAP · VBEPsame tables
BatchMCH1 · MCHA · MCHBsame tables
Journal lineACDOCA (universal journal)BKPF and BSEG
Nearby

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

Excess and obsolete inventory review on

Other apps on S/4HANA

Terms on this page

CoverThe months of demand the on-hand quantity serves: on hand divided by the average monthly forecast and orders.
ReserveThe amount finance sets aside against stock that may sell below its book 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.