Takes a manual journal entry with its support documents through checks, review and approval by amount band, and posts it to the ledger on approval.
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 |
|---|---|---|---|
| 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 |
| Budget line | BPGE · BPJA (budget) · ACDOCP (plan data) | BPGE.OBJNR (object) · BPGE.WTGES (amount) · BPJA.GJAHR (year) · ACDOCP.VERSION (version) | 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: A preparer submits S01 with lines that balance to 0 and at least 1 support document.
This app starts from a screen, so the first read happens when the instance opens; the criteria on the arrows use the fields above.
A preparer submits S01 with lines that balance to 0 and at least 1 support document. The instance then reads its rows from S/4HANA through the handlers above.
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 |
|---|---|---|
| Journal line | journal document posted through the ledger interface with lines, text and the support reference; reversal posted in the next period when scheduled | BAPI_ACC_DOCUMENT_POST · BAPI_ACC_DOCUMENT_REV_POST |
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 |
|---|---|---|
| Journal line | ACDOCA (universal journal) | BKPF and BSEG |
| Cost center | CSKS · CSKT | same tables |
| Budget line | BPGE · BPJA (budget) · ACDOCP (plan data) | BPGE · BPJA · COSP |
| 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.