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.
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.
| Lane | Does |
|---|---|
| Requester | completes the line and answers questions |
| Cost center owner | approves within the band and the budget |
| Buyer | confirms source, contract and price |
| Controller | approves budget overruns and lines above 10,000 |
| Division director | approves lines above 250,000 |
Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.
| Screen | What is on it |
|---|---|
| S01 My requisitions | grid of the requester's lines with status, current approver, days waiting; open button |
| S02 Approval | line 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 check | source suggestion from contracts and the last 3 purchase orders, price check, lead time against the date needed; assign contract; forward |
| S04 Budget exception | lines that take the cost center over plan with the overrun amount; controller's decision; alternative cost center field |
| S05 Mobile approval | the 5 facts an approver needs and 2 buttons; works on a phone |
| S06 Tracker | all open lines by band, age and approver; approvals due today; average time per band |
The first object is the main one; each system page shows the real table or resource behind every handler.
| Object | Why the app reads it | See it on |
|---|---|---|
| Purchase requisition | requisition lines with value, requester, release state and date needed | S/4HANA · Oracle Fusion · Snowflake |
| Budget line | the cost center's plan and consumed amount for the year | S/4HANA · Oracle Fusion · Snowflake |
| Cost center | owner and validity of the cost center | S/4HANA · Oracle Fusion · Snowflake |
| Material master | description, type and lead time | S/4HANA · Oracle Fusion · Snowflake |
| Purchasing contract | agreements in place for the material and supplier | S/4HANA · Oracle Fusion · Snowflake |
| Object | What changes |
|---|---|
| Purchase requisition | release code set for each approval level; rejection recorded with the reason; contract number and price added to the line |
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| Step | Moves when |
|---|---|
| Line detected | requisition line with an open release read from the ERP; band set from value; first approver set from the cost center owner |
| Budget checked | remaining budget for the cost center and year read live; an overrun routes the line to the controller as well |
| Approved by band | up to 10,000 the cost center owner; above 10,000 the controller as well; above 250,000 the division director as well |
| Buyer checked | buyer confirms source and price on lines above 10,000 or where a contract exists |
| Released | release code set on the line in the ERP; requester informed; a rejection carries the reason |
| Component | Trigger → action → outcome |
|---|---|
| lbl_budget | on 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_approve | on 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_return | on click → send the line back to the requester with the note → start the 3-day answer clock |
| btn_assign_contract | on click → add the contract number and price to the requisition line through the ERP interface → skip the buyer step at later levels |
| Step | Time limit and escalation |
|---|---|
| Each approval level | 2 working days, then a reminder; 4 working days, then the approver's manager receives the line |
| Requester answer | 3 working days, then the requester's manager is reminded |
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.
The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.
Purchase requisition read from EBAN; also on SAP ECC.
Open the S/4HANA page →Purchase requisition read from Procurement REST: purchaseRequisitions; also on Oracle E-Business Suite.
Open the Oracle Fusion page →Purchase requisition read from CONFORMED.PURCHASE_REQUISITION; lakehouse.
Open the Snowflake page →Other systems connect through the same handlers; see how SmartApps connect.
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.
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.
Every role in this app is inside the company; an outside role can be added as a lane with a portal screen.
Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.
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.