Runs the monthly variance review on the live ledger: each cost center owner explains the lines above threshold, controllers consolidate, and the CFO sees the top 20.
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.
| Object | Read from | Fields the app uses | Freshness |
|---|---|---|---|
| Budget line | Financial_Management: Get_Budgets · Get_Budget_Amendments | Budget_Line.Amount (plan amount) · Budget_Line.Amount (amount) · Budget.Budget_Structure (object) · Budget.Fiscal_Year (year) | live through the API |
| Journal line | Financial_Management: Get_Journals | Journal.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 |
| Cost center | Financial_Management: Get_Cost_Centers · Get_Organizations | Cost_Center.ID (id) · Cost_Center.Name (name) · Organization.Manager (owner) · Company.ID (company) | live through the API |
| Employee | Human_Resources: Get_Workers · RaaS worker report | Worker.Employee_ID (id) · Worker.Legal_Name (name) · Worker.Supervisory_Organization (org unit) · Worker.Position_ID (position) | live through the API |
In plain words: On working day 3 after a period closes, every cost center line whose actual differs from plan by more than 5 percent and more than 25,000.
The criterion runs in Workday 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 Workday fields abs(Budget_Line.Amount - Budget_Line.Amount) > 0.05 * Budget_Line.Amount and abs(Budget_Line.Amount - Budget_Line.Amount) > 25000 # the same criterion in canonical fields abs({budget.amount} - {budget.plan_amount}) > 0.05 * {budget.plan_amount} and abs({budget.amount} - {budget.plan_amount}) > 25000
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.
| Object | What changes | Interface |
|---|---|---|
| Budget line | revised forecast amount written to the forecast version of the planning system; explanation stored beside the line | Submit_Budget_Amendment |
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.
Security groups are mapped to Lima access policies once. A manager sees their own team in the app, exactly as in 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.
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.
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.
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.