BPR · BPM · Process documentation · Oracle Cloud ERP · Manufacturing

BPR / BPM Experience

How I document, redesign and govern business processes. One manufacturing case, end to end: evidence classified, current state mapped, gaps registered, rules decided with owners, future state mapped with controls and the documentation handed over as a versioned process library.

Before and afterEvidenceCurrent stateDecisionsFuture stateRecord to reportDocumentation standard
Midwest Engine Works is a made up company. The numbers are illustrative. The method is the one I use on real engagements.

The case

Engine builder and overhauler. Two plants, one repair depot, three legal entities. Live on Oracle Fusion Cloud Financials, Procurement, Inventory, Cost Management, Manufacturing and Order Management. The processes were never documented. The business runs steps outside the system and the ticket backlog grows. The job is to map what the business does, redesign it and govern it.

412
tickets used as evidence
5
process families mapped
6
gaps in the register
6
decisions, each with an owner
4
documentation levels
Working principle. A ticket is a symptom. The map finds the step where the business and the system disagree. The fix is a decision, a configuration change and a control. The decision has an owner and the control appears on the future state map.

Before and after

The whole redesign on one screen. The left column is what the evidence showed. The right column is what the six decisions produce. The two swimlanes below are the same process, procure to pay, before and after.

Before · current state

  • Requests travel by email. The purchase order is keyed after the goods arrive.
  • Receipts are logged on a clipboard when no purchase order exists.
  • Match tolerances sit at zero. Every variance creates a hold with no owner.
  • Holds are chased by email between AP, the buyer and the plant.
  • Accounting and costing run once a month. Errors surface on the last day.
  • Intercompany runs on a spreadsheet. No process map exists.

After · future state

  • Every purchase starts as a requisition in Oracle with approval by amount and cost center.
  • No purchase order, no receipt. Every receipt is against a purchase order line.
  • Tolerances set by the business: 2 percent price, 5 percent quantity.
  • Holds route by rule to a named owner with a three day clock.
  • Accounting and costing run nightly. Exceptions are cleared daily.
  • Intercompany runs as transfer orders. Every process has a versioned map and an owner.
Before
Level 3 · Procure to pay · CURRENT STATE · 412 tickets mapped to steps · red badge = ticket countRequesterBuyerReceiver(plant dock)AP clerkCostaccountantOracle CloudNeed identifiedemails the buyer31Keys purchase orderafter the factGoods arrive at dockPurchase orderexists?Logs receipt ona clipboard58Receipt createdin OracleInvoice keyedthree way matchMatch holdtolerance = 067Emails buyer torelease hold44Create Accountingmonth end only39Accrue at period endnever runs22noyesno accrual, wrong inventory, invoice will fail matchReading the map: five steps carry 261 of 412 tickets. Two of them are not in Oracle at all (email the buyer, clipboard receipt). The accrual step is blocked by the hold step. That loop is the biggest gap in the process.

Figure 1. Before. Procure to pay, current state. Red badges are ticket counts. Five steps carry 261 of 412 tickets and two of them happen outside Oracle.

After
Level 3 · Procure to pay · FUTURE STATE · gold diamonds are controls · each decision has a named ownerRequesterBuyerReceiver(plant dock)AP clerkCostaccountantOracle CloudRequisitionin OracleApproval byamount, cost centerPurchase order fromapproved requisitionNo PO,no receiptReceive againstPO lineAccrue at receiptnightly transferTolerance 2% price5% quantityInvoice matchedholds by rulePrice hold to buyer3 day SLAQuantity hold toreceiver, 3 day SLACreate Accountingnightly, weekly finalSix decisions, six owners: plant manager (no PO no receipt), controller (requisitions, accrue at receipt), procurement director (tolerances), AP manager (hold workflow), cost accountant (nightly accounting).

Figure 2. After. Procure to pay, future state. Gold diamonds are controls. Every decision has a named owner. Every hold has an owner and a clock.

StepBeforeAfter
Create requisitionRequester emails the buyer. Buyer keys the purchase order after the fact. 31 tickets.Requisition in Oracle. Approval rules by amount and cost center. Purchase order from the approved requisition.
Receive goodsReceipt in Oracle only when a purchase order exists. Otherwise a clipboard. 58 tickets.Control: no purchase order, no receipt. Emergency receipts use a blanket purchase agreement per plant.
Match invoiceThree way match with tolerances at zero. Every variance is a hold. 67 tickets.Tolerances set by the procurement director. Floor and ceiling by commodity.
Release holdAP emails the buyer. Buyer emails the plant. Nobody releases. 44 tickets.Price holds to the buyer. Quantity holds to the receiver. Three day SLA. Aging report daily.
Create accountingRun at month end only. 39 tickets.Nightly in draft, weekly in final. Exceptions cleared inside the week.
Accrue receiptsAccrue at period end. The job never runs. 22 tickets.Accrue at receipt. Transfer from Receiving scheduled daily. Reconciliation weekly.

Table 1. Procure to pay, step by step, before and after. Ticket counts are the evidence for each gap.

Step 1 · Collect and classify the evidence

Every ticket was tagged on five dimensions: process, root cause class, business severity, Oracle object and map step. Most of the backlog is a few root causes reported many times. The classes separate people and process gaps from system defects, so each gap gets the right fix type.

412 open tickets by root cause classTraining gap131 (32%)Process gap98 (24%)Configuration defect84 (20%)Data defect52 (13%)Integration defect27 (7%)Enhancement14 (3%)Duplicate6 (1%)Gold bars are people and process, not system. 229 of 412 tickets. Fix the map and the training first, then send the configuration defects to the SI with acceptance criteria.

Figure 3. Tickets by root cause class. More than half are training and process gaps.

Step 2 · Map the process families

Level 2 shows the five families and the Oracle modules under each. This is the table of contents for the process library. Every level 3 swimlane and level 4 work instruction hangs from one of these boxes.

Level 2 · Process families and the Oracle Cloud modules that carry themSource to pay• Procurement• Payables• Receipt AccountingPlan to produce• Manufacturing• Inventory• Cost Management• MES integrationOrder to cash• Order Management• Shipping• ReceivablesService and depot repair• Service Logistics• Maintenance• Installed BaseRecord to reportSubledger Accounting · General Ledger · Intercompany · Close calendar in the Oracle order: AP, Receipt Accounting and Cost, Projects, Assets, AR, SLA, GLEvery family posts through Subledger Accounting. A gap in any family above shows up here. That is why the families are mapped first.

Figure 4. Level 2 process families and the Oracle Cloud modules that carry them.

Step 3 · Map the current state and register the gaps

Procure to pay carried the most tickets, so it went first. The current state swimlane is Figure 1 above. Lanes are roles plus one lane for Oracle Cloud. Ticket counts sit on the steps. Each step with a badge becomes a line in the gap register.

Gap register

StepCurrent stateTicketsGap
Create requisitionRequesters email the buyer. Buyer keys the purchase order. No requisition in Oracle.31No approval trail. Purchase order created after the goods arrive.
Receive goodsDock receives in Oracle only when the purchase order exists. Otherwise the receipt is logged on a clipboard.58Receipt not in Oracle. No accrual. Inventory wrong. Invoice will fail match.
Match invoiceThree way match on. Tolerances at zero. Every price or quantity variance creates a hold.67Tolerances never set by the business. Holds have no owner.
Release holdAP emails the buyer. Buyer emails the plant. Nobody releases.44No workflow. No SLA. Holds age past period end.
Create accountingCreate Accounting run at month end only. Errors found on the last day.39No daily run. Account rules missing for outside processing and for the depot cost center.
Accrue receiptsAccrue at period end selected. Create Uninvoiced Receipt Accruals never runs because Payables cannot close.22Circular block. Payables waits for holds. Accruals wait for Payables.

Step 4 · Decide the rules

Six decisions, one per gap. Each has a business owner and appears on the future state map as a control. The integrator builds to the decision and the acceptance criteria. This table is the change record for the process library.

DecisionRuleOwner
1. No purchase order, no receipt.Dock receives only against a purchase order line. Emergency receipts use a blanket purchase agreement per plant.Plant manager
2. Requisition in Oracle for every purchase.Approval rules by amount and by cost center.Controller
3. Match tolerances set by the business.Two percent price, five percent quantity, floor and ceiling by commodity.Procurement director
4. Hold release workflow.Price holds to the buyer. Quantity holds to the receiver. Three day SLA. Aging report on the daily huddle.AP manager
5. Create Accounting nightly in draft, weekly in final.Exceptions cleared inside the week.Cost accountant
6. Accrue at receipt.Transfer Transactions from Receiving scheduled daily. Accrual reconciliation weekly.Controller

Step 5 · Map the future state

The future state swimlane is Figure 2 above. Every decision from step 4 is drawn as a gold control diamond. Every hand off has an owner. Level 4 work instructions are written from this map screen by screen. The training runs on them.

Step 6 · Repeat for the next family: record to report

The same method applied to the second family. Open work orders, missing resource rates and month end only accounting runs were the gaps. The redesign moves that work to nightly jobs, daily exception review and a calendar with one owner per line.

StepBeforeAfter
Close calendarNone. Finance starts the close when the last invoice arrives.A calendar in the Oracle order with an owner per line.
Work order closeWork orders left open for weeks after completion. Scrap not recorded.Complete within two days of last operation. Scrap at the operation. Weekly open work order report.
Resource ratesRates loaded for the assembly plant only.Rates for every plant and work center, reviewed each quarter.
Cost distributionsRun at month end. Errors surface on the last day.Nightly. Exceptions cleared daily by the cost accountant.
IntercompanyMachining sells to assembly on a spreadsheet.Transfer orders in Oracle. Transfer price per item class.
General LedgerNever reached.Closes on day five.
Close calendar · the Oracle subledger order · one owner per line · five business daysDay 1Day 2Day 3Day 4Day 5Payables · AP managerReceipt Accounting and Cost Management · cost accountantAssets · fixed asset accountantReceivables · AR leadSubledger Accounting review · controllerGeneral Ledger · controllerPayables closes first so uninvoiced receipt accruals are right. Every subledger closes before the ledger. Daily Create Accounting all month means day 4 finds nothing new.

Figure 5. The operating calendar that comes out of the record to report redesign. One owner per line.

Deliverables and timeline

Week 2
evidence classified, gap register with owners
Month 1
current state maps and decisions approved
Month 2
future state maps, work instructions, training
Month 3
controls live, KPIs on the dashboard, library handed over
Governance and handover. Maps, transcripts, decisions and defects go into a searchable process library from week one. Every map is versioned with a named owner. A change to a process starts as a gap, becomes a decision and ends as a new map version and a measured result on the PPM dashboard. The integrator and the support provider inherit the library. The client owns it.

Documentation standard

Four levels. One notation per page. BPMN 2.0 for the swimlanes. The same standard on every engagement, so a new reader knows where to look.

LEVEL 1

Value chain

Source, make, deliver, service, finance. One page for the CFO and the plant manager.

LEVEL 2

Process family

Procure to pay, order to cash, record to report, plan to produce, service and depot repair. Oracle modules named on each box.

LEVEL 3

Swimlane

BPMN 2.0 lanes by role plus an Oracle lane. Every decision, exception path, hand off and control drawn. Ticket counts on steps.

LEVEL 4

Work instruction

Screen by screen with the Oracle task name and the data required. The training and the support provider run on these.

Evidence for the current state

  1. The tickets, classified on five dimensions.
  2. Oracle itself: period close exception reports, audit history, setup pages, workflow rules.
  3. Interviews at the desk, watching the work happen.
  4. The spreadsheets beside Oracle. Every spreadsheet is a step the system does not do.
  5. The outgoing integrator's design documents, treated as intent, not fact.

Tools

Lucidchart for BPMN swimlanes with the Lucid MCP, so Claude drafts a map from an interview transcript and a ticket list. A private searchable process library over the engagement files. Oracle exception reports for the truth. Excel for the ticket analysis. A PPM dashboard that tracks each redesign from gap to decision, owner and measured result.

Contact

Business process reengineering, process management and process documentation for Oracle Cloud ERP. Remote, with travel.

chris.clark@clarkfamilyusa.comBack to the portfolio