App catalogue Procurement

Purchase requisition approval

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 HANDLERSSOURCE OBJECTS, READ IN PLACES01 My requisitionsscreenS02 ApprovalscreenS03 Buyer checkscreenS04 Budget exceptionscreenS05 Mobile approvalscreendh_prPurchase requisitiondh_budgetBudget linedh_cost_centerCost centerdh_materialMaterial masterdh_contractPurchasing contractS/4HANAEBANS/4HANABPGE · BPJAS/4HANACSKS · CSKTS/4HANAMARA · MARC · MAKTS/4HANAEKKO · EKPOrows stay in the source · access rules apply at read time · writes go through the source's released interface and are confirmed
The screens, the data handlers behind them and the objects each handler reads in place on S/4HANA. Other systems have their own page.
3 days
of configuration to a production-grade version
estimate
6
screens, desktop and mobile
catalogue
5
data handlers, read in place
catalogue
3
systems with a page for this app
catalogue
2
clocks with escalation
catalogue
What it does

Today, and with the app

Today an approver sees a requisition number in an ERP inbox with little context, and checks the budget in a separate report before deciding. Requesters ask the buyer by email where their line is.

The app reads every requisition line whose release is still open, sets the approval band from its value and finds the approvers from the cost center owner and the band. Each approver sees the line with the requester's reason, the cost center's remaining budget after this line, the last price paid for the material and any contract in place, on a screen that works on a phone. A line that takes the cost center over plan goes to the controller as well, and the buyer checks source and price on lines above 10,000. Every approval sets the release code for its level on the line in the ERP, and the requester sees each step on the tracker.

Who takes part

Process app: lanes and boxes first, then screens per box, then roles, then the criteria on each arrow

LaneDoes
Requestercompletes the line and answers questions
Cost center ownerapproves within the band and the budget
Buyerconfirms source, contract and price
Controllerapproves budget overruns and lines above 10,000
Division directorapproves lines above 250,000
Screens

6 screens, composed from the handlers

Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.

ScreenWhat is on it
S01 My requisitionsgrid of the requester's lines with status, current approver, days waiting; open button
S02 Approvalline detail: material, quantity, value, date needed, reason; the cost center's budget with the remaining amount after this line; last price paid; contract in place; approve, return and reject buttons; note
S03 Buyer checksource suggestion from contracts and the last 3 purchase orders, price check, lead time against the date needed; assign contract; forward
S04 Budget exceptionlines that take the cost center over plan with the overrun amount; controller's decision; alternative cost center field
S05 Mobile approvalthe 5 facts an approver needs and 2 buttons; works on a phone
S06 Trackerall open lines by band, age and approver; approvals due today; average time per band
Data handlers

5 objects, read where they live

The first object is the main one; each system page shows the real table or resource behind every handler.

ObjectWhy the app reads itSee it on
Purchase requisitionrequisition lines with value, requester, release state and date neededS/4HANA · Oracle Fusion · Snowflake
Budget linethe cost center's plan and consumed amount for the yearS/4HANA · Oracle Fusion · Snowflake
Cost centerowner and validity of the cost centerS/4HANA · Oracle Fusion · Snowflake
Material masterdescription, type and lead timeS/4HANA · Oracle Fusion · Snowflake
Purchasing contractagreements in place for the material and supplierS/4HANA · Oracle Fusion · Snowflake

Written back

ObjectWhat changes
Purchase requisitionrelease code set for each approval level; rejection recorded with the reason; contract number and price added to the line
The flow

From the trigger to the last write

THE FLOW · PURCHASE REQUISITION APPROVAL1Line detectedrequisition line with anopen release read from theERP; band set from value;first approver set from thecost center owner2Budget checkedremaining budget for thecost center and year readlive; an overrun routes theline to the controller aswell3Approved by bandup to 10,000 the costcenter owner; above 10,000the controller as well;above 250,000 the divisiondirector as well4Buyer checkedbuyer confirms source andprice on lines above 10,000or where a contract exists5Releasedrelease code set on theline in the ERP; requesterinformed; a rejectioncarries the reason
Each step and the criterion that moves it.

Start: A requisition line saved in the ERP whose release is still open.

# start criterion, in canonical fields; each system page shows it in that system's fields
{pr.release} = open

StepMoves when
Line detectedrequisition line with an open release read from the ERP; band set from value; first approver set from the cost center owner
Budget checkedremaining budget for the cost center and year read live; an overrun routes the line to the controller as well
Approved by bandup to 10,000 the cost center owner; above 10,000 the controller as well; above 250,000 the division director as well
Buyer checkedbuyer confirms source and price on lines above 10,000 or where a contract exists
Releasedrelease code set on the line in the ERP; requester informed; a rejection carries the reason
Actions, clocks and measures

What the components do, what the clocks enforce, what the board shows

ComponentTrigger → action → outcome
lbl_budgeton open → read the cost center's budget and its consumed and committed amounts live → show the remaining amount after this line and flag an overrun
btn_approveon click → record the approval at this level → set the ERP release code for the level, move the line to the next band or close it
btn_returnon click → send the line back to the requester with the note → start the 3-day answer clock
btn_assign_contracton click → add the contract number and price to the requisition line through the ERP interface → skip the buyer step at later levels

Clocks

StepTime limit and escalation
Each approval level2 working days, then a reminder; 4 working days, then the approver's manager receives the line
Requester answer3 working days, then the requester's manager is reminded

Measures

lines approved within 2 daysaverage days per bandlines returned for correctionoverruns approved per monthrequisition value by cost center
A day with the app

Illustrative

Names, places and figures are illustrative; the pattern is the catalogue's.

Ana in maintenance at the Monterrey plant saved a requisition for a 38,000 spindle at 15:10 on Tuesday. The app showed the cost center owner the line on his phone at 15:12 with the budget remaining after it and the last price paid for the same part; he approved at 15:30 and the buyer attached the contract at 16:05. The controller saw the budget check passed and released the line at 09:20 on Wednesday; the release code reached the ERP within seconds and the buyer converted the line into an order before 10:00. The tracker showed 214 lines open in the plant, 12 of them beyond 2 days.

illustrative scenario · Purchase requisition approval
On your systems

One page per system

The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.

Other systems connect through the same handlers; see how SmartApps connect.

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.
CommitmentA requisition or order value the budget already counts as spent.
Questions

How long does it take to have this running?

About 30 minutes to a first running screen on your live rows, and 3 working days to the production-grade version described here, most of it spent agreeing screens and criteria with the process owner.

Which system does it run on?

Any of SAP S/4HANA, Oracle Fusion Cloud, Snowflake, with the objects read in place; the pages above show the objects and the write path for each. Two systems at once is one handler per object per system.

Who takes part from outside the company?

Every role in this app is inside the company; an outside role can be added as a lane with a portal screen.

What does the audit record hold?

Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.

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.