Takes a capital request with its business case through plant controller, division and group approval, checks the investment budget, and creates the appropriation in the ERP.
Today a capital request is a slide deck and a spreadsheet emailed up the line, and the plant controller checks the budget in the ERP by hand at each step. The appropriation is created weeks after the approval, and the first purchase requisition waits for it.
A plant engineer or manager writes the request on one screen: description, cost center, amount by year, category and the business case with payback, options considered and attachments. The app reads the investment budget line for the cost center and year and the requests already approved against it, shows the remaining amount, and sets the approval band from the amount. The plant controller, the division lead and the group committee approve their bands in turn, each seeing the same case and the ranking against other open requests. On the final approval the app creates the appropriation request in the ERP through the released interface, releases the budget and gives the number to the requester and procurement.
| Lane | Does |
|---|---|
| Requester | plant engineer or manager: writes the request and the business case |
| Plant controller | checks the budget line, the payback and the classification; approves the first band |
| Division lead | approves the second band and ranks requests across plants |
| Group committee | approves above the division band at its monthly meeting |
Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.
| Screen | What is on it |
|---|---|
| S01 Request | description, cost center, category (replacement, expansion, safety, IT), amount by year, payback, options considered, attachments; submit |
| S02 Budget check | investment budget line for the cost center and year, requests approved to date, this request, remaining amount; over-budget flag with a funding source field |
| S03 Plant controller review | financial check: useful life, depreciation start, asset class, cost center; approve or return with a note |
| S04 Division and group approval | case summary, ranking of open requests by payback and category, budget by division; approve, defer or return; note |
| S05 Appropriation | appropriation request number from the ERP, amount released by year, cost center; link for purchase requisitions |
| S06 Board | requests by status, value and category; approved value against budget by division; days to approve by 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 |
|---|---|---|
| Capital request | capital requests: amount, year, cost center, category, status | S/4HANA · Oracle Fusion · Workday · Snowflake |
| Budget line | investment budget lines by cost center and year with the plan amount | S/4HANA · Oracle Fusion · Workday · Snowflake |
| Cost center | owner, company and validity of the cost center on the request | S/4HANA · Oracle Fusion · Workday · Snowflake |
| Journal line | capital spend posted to date against approved requests | S/4HANA · Oracle Fusion · Workday · Snowflake |
| Object | What changes |
|---|---|
| Capital request | appropriation request created with amount by year, cost center and category; status set as each level approves |
| Budget line | released amount recorded against the investment budget line |
Start: A requester submits S01 with an amount and a business case.
| Step | Moves when |
|---|---|
| Request submitted | amount, cost center and the business case fields for the category present |
| Budget checked | budget line covers the amount, or a funding source is named and the controller agrees |
| Plant controller approved | financial check passed; a request below 100,000 goes straight to the appropriation step |
| Division approved | requests up to 1,000,000; the lead sees the ranking across plants |
| Group approved | requests above 1,000,000 at the monthly committee; deferred requests return to the next meeting |
| Appropriation created | number written to the ERP; budget released; requester and procurement informed |
| Component | Trigger → action → outcome |
|---|---|
| fld_amount | on change → read the budget line and the approved requests for the cost center and year → show the remaining amount and set the approval band |
| btn_submit | on click → check the business case fields for the category (payback for expansion, reference for safety) → route to the plant controller, start the 3-day clock |
| btn_approve | on click → record the approval with the band → move to the next band or to the appropriation step |
| btn_appropriate | on click → call the appropriation request interface with the amount, year and cost center → store the number, release the budget, notify the requester and procurement |
| Step | Time limit and escalation |
|---|---|
| Plant controller | 3 working days, then the finance director is reminded |
| Division | 5 working days, then the division finance lead is copied |
| Group committee | the next monthly meeting, with a reminder 2 working days before to present |
Names, places and figures are illustrative; the pattern is the catalogue's.
Ingrid, a plant engineer in Gothenburg, submitted a request for a 480,000 packaging line upgrade at 15:30 on a Wednesday, with a 2.1-year payback and 2 options considered. The budget check showed 620,000 left on the plant's investment line, the plant controller approved on Thursday morning, and the division lead approved on Monday after reading the second option. The appropriation number appeared in SAP at 09:12, and the buyer raised the first purchase requisition against it before noon. The board showed the CFO 38 open requests and the value approved against budget by division.
The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.
Capital request read from ANLA (asset under construction) · IMPR / IMZO (investment programme) · PRPS; also on SAP ECC.
Open the S/4HANA page →Capital request read from Fixed Assets REST: assets (CIP) · Projects capital projects; also on Oracle E-Business Suite.
Open the Oracle Fusion page →Capital request read from Financial_Management: Get_Projects (capital) · Get_Assets; HCM / finance.
Open the Workday page →Capital request read from CONFORMED.CAPITAL_REQUEST; 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 6 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, Workday, 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.