Who this is for
AP, finance and technology teams at universities and colleges that use WebCenter for invoice processing or document management. The starting point is the campus process and its systems of record, whether the finance platform is E-Business Suite, PeopleSoft, Fusion Cloud or another ERP.
Locate the coding and accounting boundaries
Fund, grant, project, department and entity fields may cross several systems. The fact that a value appears on a WebCenter form does not establish where the authoritative validation or accounting takes place.
Document the permitted values, reference-data refresh, validation owner, posting interface and error response. Where encumbrance, matching or indirect-cost treatment is relevant, finance and research-administration teams define the expected behavior. The technical acceptance plan should test those decisions; it should not invent accounting rules.
| Dependency | Question before the change |
|---|---|
| Fund or project coding | Which system validates combinations, and what happens when reference data is unavailable? |
| Grant-related fields | Which owner approves the required fields and rules for the transaction? |
| Matching and encumbrance | What ERP transactions must succeed, and how are exceptions reconciled? |
| Procurement interface | Which system owns the supplier, purchase order, receipt and contract data? |
| Document retrieval | Which identifiers and access rules connect a posted transaction to its supporting record? |
Build the schedule from the institution’s calendar
Fiscal close, academic opening, research activity and audit work may constrain different periods. Confirm those dates with the people who will operate and accept the change. Include procurement lead times, access approvals, representative test data and time to repeat a failed rehearsal.
A summer date is not automatically a safe cutover. Test staffing and finance availability matter as much as infrastructure availability. Agree the go/no-go evidence and the decision owner before reserving the final window.
Validate the ERP connection you will actually use
Separate retained connections from proposed ones. A new ERP instance can change organization identifiers, reference-data endpoints, authentication, certificates, document links and import behavior even when the business process looks familiar.
For each interface, record the source and target, supported API or import mechanism, identifier mapping, retry behavior and reconciliation evidence. Do not assume that an EBS connection can be retargeted unchanged to PeopleSoft, Fusion or a different campus platform.
Make a useful procurement input
Describe the components and customizations that exist, the evidence still needed, and observable acceptance outcomes. For example: an authorized operator codes a permitted distribution, the intended ERP transaction is created once, and the linked document remains retrievable.
That gives procurement a concrete technical scope. It does not establish an award route, procurement duration or supplier eligibility; those decisions belong to the institution.
Put the support dates in context
Oracle’s Fusion Middleware policy lists December 2026 for 12.2.x Premier Support and December 2027 for Extended Support, subject to the policy qualifications. Confirm the exact product, release, patch level and entitlement before using those dates in a plan. Forms Recognition has a separate release and runtime; a WebCenter Content upgrade does not by itself validate the recognition project.
Compare the applicable dates with procurement, implementation, rehearsal and business acceptance. There is no universal project duration or guaranteed cutover window. A hosting move alone does not extend software support.
Compare the changes separately
An upgrade, a hosting move and an ERP integration change solve different problems. Keeping them distinct makes the scope easier to test:
- Upgrade: confirm the supported source and target, review customizations and rehearse the full process.
- Move to OCI: design identity, network, storage, clustering and recovery around the actual workload. Include backups, logs, integrations and administrator access when checking residency.
- Change the AP or ERP connection: agree business identifiers, coding validation, import or posting behavior, error handling and document retrieval.
- Retain a workload: document which repository, records or workflow functions remain and who operates them.
For cutover, first consider completing existing SOA work before the change. If work must continue across the boundary, identify which tasks, unfinished ERP invoices and stored documents require separate treatment. See invoice migration planning.
How ECMWorks helps
An Estate Review maps the products, customizations and interfaces to the business process. The output identifies evidence gaps, applicable options, acceptance tests and proposed owners. Your finance, records, security and procurement teams confirm the requirements and contractual constraints; the engineering plan explains how to test them.
The fictional sample decision pack shows the structure without using customer information. Delivery can then be scoped as an upgrade, migration or support retainer, with access and commercial terms agreed for that engagement.