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.
Tables are read in place through the SAP connector, using released read interfaces; changed rows arrive through change capture where the basis team allows it. The rows stay in SAP.
| Object | Read from | Fields the app uses | Freshness |
|---|---|---|---|
| Budget line | BPGE · BPJA (budget) · ACDOCP (plan data) | ACDOCP.HSL (plan amount) · BPGE.WTGES (amount) · BPGE.OBJNR (object) · BPJA.GJAHR (year) | live; change capture where enabled |
| Journal line | ACDOCA (universal journal) | ACDOCA.BELNR (document) · ACDOCA.RACCT (account) · ACDOCA.HSL (amount) · ACDOCA.RCNTR (cost center) | live; change capture where enabled |
| Cost center | CSKS · CSKT | CSKS.KOSTL (id) · CSKT.KTEXT (name) · CSKS.VERAK (owner) · CSKS.BUKRS (company) | live; change capture where enabled |
| Employee | PA0001 · PA0002 (SAP HCM) or SuccessFactors | PA0001.PERNR (id) · PA0002.VORNA + NACHN (name) · PA0001.ORGEH (org unit) · PA0001.PLANS (position) | live; change capture where enabled |
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 S/4HANA 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 S/4HANA fields abs(BPGE.WTGES - ACDOCP.HSL) > 0.05 * ACDOCP.HSL and abs(BPGE.WTGES - ACDOCP.HSL) > 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 released BAPIs and IDocs. Each call returns a document number or an error message, and the app records both 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 | BAPI_ACC_PLAN_POST (planning API) |
Each write stores the identifier S/4HANA returns beside the decision, the person and the time, so the log answers who changed what, and the reconciliation shows it arrived.
SAP roles are mapped to Lima access policies once. A buyer who sees purchasing organisation 1000 in SAP sees the same rows in the app.
On SAP ECC the same objects live in the classic tables named beside each row; MATDOC becomes MKPF and MSEG, ACDOCA becomes BKPF and BSEG. The BAPIs are the same.
| Object | On S/4HANA | On SAP ECC |
|---|---|---|
| Budget line | BPGE · BPJA (budget) · ACDOCP (plan data) | BPGE · BPJA · COSP |
| Journal line | ACDOCA (universal journal) | BKPF and BSEG |
| Cost center | CSKS · CSKT | same tables |
| Employee | PA0001 · PA0002 (SAP HCM) or SuccessFactors | same infotypes |
The screens read through handlers that leave the rows in S/4HANA. 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, listed above.
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.
