Oracle EBS Discrete Manufacturing Go-Live Checklist

0%

0 of 36 items complete

17 critical items still open - these are the highest-risk gaps.

Download checklist:

Organization and item setup

Inventory organizations created with correct master organization and calendarCRITICALItem master attributes reviewed for each item template, including planning and costing flagsCRITICALUnits of measure and conversions loaded and approvedCategory sets and default categories assigned for inventory, costing and planningSubinventories, locators and nettable settings definedLot and serial control rules agreed per item classCRITICALItem revision control and numbering rules documentedTransaction types and reasons configured, including any custom types

BOM and routing

Departments, resources and resource costs definedCRITICALStandard operations and routings loaded and validatedBills of material loaded with effectivity dates and supply typesCRITICALPhantom assemblies and option classes reviewed with engineeringEngineering change process and approval workflow testedBOM and routing import errors cleared with no unexplained rejectsCRITICALBackflush and pull supply types verified against shop floor practice

WIP and shop floor

WIP parameters, accounting classes and default accounts setCRITICALJob release, issue, move, completion and return flows tested end to endCRITICALScrap, rework and negative issue rules agreedJob closing and variance rules tested with sample jobsCRITICALShop floor status codes and operation hold rules definedBarcode or mobile transaction devices tested if usedMass load and interface programs scheduled and monitored

Costing and finance

Costing method chosen and cost types definedCRITICALStandard costs rolled up and reviewed, or average cost start values loadedCRITICALInventory and WIP accounts mapped to the general ledger and testedVariance accounts and overhead absorption validatedInventory accounting period opened and the close procedure rehearsedCRITICALOpening balances reconciled between subledger and general ledgerCRITICAL

Data, testing and cutover

Opening onhand quantities counted, loaded and reconciledCRITICALOpen jobs, purchase orders and sales orders migrated with an agreed cutoffCRITICALMock conversion run completed with timings and defect logUser acceptance test signed off by plant, planning and financeCRITICALConcurrent managers, transaction manager and cost processors confirmed runningRoles, responsibilities and security reviewed for segregation of dutiesTraining completed and super users assigned per shiftRollback plan and hypercare support schedule publishedCRITICAL

Aim to close every critical item before cutover. Unchecked non-critical items should have an owner and a date in the first weeks of hypercare.

Go-live plan review

Optional: ask an expert to review your Oracle EBS manufacturing cutover plan.

Optional. The tool and every export work without this. No spam.

How to use the checklist

Work through each group with the owner for that area, such as the inventory lead, engineering, the plant and finance. Tick items as they are demonstrated, not as they are promised. Critical items are the ones that, if missed, stop the plant shipping or block the first period close. Export the list to PDF or Excel for the steering committee.

Where go-lives usually fail

Most problems come from item master attributes that differ from the shop floor reality, BOM data that was never reviewed for supply types, and a costing setup nobody rehearsed through period close. Opening balances that do not reconcile between the subledger and the general ledger are the most common finance escalation in the first month.

Item attributes set from templates nobody validated
Backflush and pull supply types not matched to practice
Close not rehearsed before go-live
Opening balances not reconciled

Testing that matters

Run a full job life cycle with real parts: create, release, issue, move, complete, scrap, return and close, then review the accounting entries. Repeat with lot and serial controlled items. Run period close in a test instance and review pending transaction reports. Rehearse the conversion at least twice with timings so the cutover window is realistic.

Hypercare

Plan daily triage in the first two weeks, a monitored list of interface errors and pending transactions, and a rapid path to fix item and BOM data. Keep project resources available through the first period close, because that is when costing and reconciliation issues surface.

Frequently Asked Questions

How long does an Oracle EBS discrete manufacturing go-live take?

It depends on scope, number of organizations and data quality. Projects often run many months, with the cutover itself taking a weekend to a few days. Plan multiple mock conversions rather than relying on a single dry run.

What is the most common cause of a failed WIP close?

Jobs with unprocessed or uncosted transactions, missing accounting class setup, or variance accounts that were never tested. Rehearse job close and period close with real examples before go-live.

Should opening onhand come from a physical count?

Ideally yes, or from a reconciled cutoff count. Loading unverified quantities moves old inaccuracies into the new system and creates large adjustments after the first cycle counts.

Who should sign off the go-live?

Plant operations, planning, purchasing, finance and IT should each sign for their area. Finance sign-off should cover opening balances and the close procedure, because those items are hard to correct later.

If you want help reviewing a plan like this or automating post go-live monitoring of interfaces and pending transactions, we can talk through options with your delivery partner.

Talk to an Expert Explore More Free Tools

Related Tools

Oracle

More Oracle tools

See all