Finance on Workday

Capital expenditure request on Workday

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.

SCREENSDATA HANDLERSWORKDAY · READ IN PLACES01 RequestS02 Budget checkS03 Plant controller reviewS04 Division and group approvalS05 AppropriationS06 Boarddh_capital_requestCapital requestFinancial_Management: Get_Projects(capital) · Get_Assetsdh_budget_lineBudget lineFinancial_Management: Get_Budgets ·Get_Budget_Amendmentsdh_cost_centerCost centerFinancial_Management: Get_Cost_Centers ·Get_Organizationsdh_journal_lineJournal lineFinancial_Management: Get_JournalsWRITE BACK TO WORKDAYCapital request → Submit_ProjectBudget line → Submit_Budget_Amendmentrows stay in Workday · access rules applied at read time · each write acknowledged and logged
The screens of the app, the data handler behind each, and the Workday object it reads in place. Writes below the line go through released interfaces with an acknowledgement.
4
objects read in place from Workday
catalogue
6
screens on those rows
catalogue
6 days
to production-grade
estimate
2
objects written back
catalogue
0
rows copied to build it
product
What the app reads

The Workday objects behind each handler

Workers, organisations, positions, time off and expense reports are read in place through Workday's SOAP and REST web services and through Reports-as-a-Service for lists. The rows stay in Workday.

ObjectRead fromFields the app usesFreshness
Capital requestFinancial_Management: Get_Projects (capital) · Get_AssetsProject.ID (request) · Project.Name (desc) · Project.Budget (amount) · Project.Fiscal_Year (year)live through the API
Budget lineFinancial_Management: Get_Budgets · Get_Budget_AmendmentsBudget.Budget_Structure (object) · Budget_Line.Amount (amount) · Budget.Fiscal_Year (year) · Budget.Budget_Name (version)live through the API
Cost centerFinancial_Management: Get_Cost_Centers · Get_OrganizationsCost_Center.ID (id) · Cost_Center.Name (name) · Organization.Manager (owner) · Company.ID (company)live through the API
Journal lineFinancial_Management: Get_JournalsJournal.Journal_Number (document) · Journal_Line.Ledger_Account (account) · Journal_Line.Ledger_Debit_Amount − Credit (amount) · Journal_Line.Cost_Center (cost center)live through the API
The trigger

The start criterion in Workday's own fields

In plain words: A requester submits S01 with an amount and a business case.

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 requester submits S01 with an amount and a business case. The instance then reads its rows from Workday through the handlers above.

What the app writes back

Through released interfaces

Writes go through the released web-service operations (for example Submit_Expense_Report, Request_Time_Off, Hire_Employee) under an integration system user with the security groups the operation needs. Each call returns the Workday ID, and the app records it beside the decision.

ObjectWhat changesInterface
Capital requestappropriation request created with amount by year, cost center and category; status set as each level approvesSubmit_Project
Budget linereleased amount recorded against the investment budget lineSubmit_Budget_Amendment
Acknowledged and logged

Each write stores the identifier Workday 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

Security groups are mapped to Lima access policies once. A manager sees their own team in the app, exactly as in Workday.

  • An integration system user with domain security for the objects the app reads and writes
  • A Reports-as-a-Service report for each list the app needs at scale
  • Tenant URL and allowed IP set up
  • Business-process definitions in Workday agreed so approvals raised from the app land in the right step
Register the handlers4 objects from the catalog; each shows its rows at once.
Nearby

This app on other systems, and other apps on Workday

Capital expenditure request on

Other apps on Workday

Terms on this page

Appropriation requestThe ERP record that approves a capital amount and lets purchase requisitions refer to it.
Payback periodThe number of years until the savings or income from an investment equal its cost.
Read in placeThe rows stay in Workday; the handler sends the filter and the columns and Workday returns the matching rows.
Questions

Does this app copy data out of Workday?

The screens read through handlers that leave the rows in Workday. History the app needs at scale is landed in the lake by the Backbone, which is the exception by design.

What does Workday 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 another system as well?

Yes. The screens, criteria and roles stay; the handlers are re-bound to the other system's objects, and the app's other system pages show them.

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.