Map each job to a deliberate target
A WebCenter AP implementation can include capture, recognition, workflow, coding forms and a document repository. The exact products and customizations vary. Begin with the implemented business process rather than assuming every installation includes the same stack.
| Job | Decision for the Fusion program |
|---|---|
| Intake | How supplier email, scanned paper and other channels reach the target |
| Extraction | Which service reads the required fields and how exceptions are reviewed |
| Coding and approval | Where business rules, assignments and authorization are enforced |
| Invoice creation | Which supported import or API fits the transaction and volume |
| Document access | How users retrieve the correct image from the business context |
| Historical records | Where retained documents, holds and audit evidence remain accessible |
Evaluate native imaging against actual invoices
Oracle describes integrated invoice imaging as image intake, recognition, invoice creation and exception review. Check the enabled capability and applicable release in the target tenant. Do not infer that it reproduces every Capture profile, WFR validation rule or custom coding step.
Compare candidate extraction approaches using the same representative documents and expected values. Measure incorrectly accepted values, review effort and exception handling as well as extraction accuracy. WFR configuration and historical corrections are not assumed to transfer to another engine automatically.
Re-establish approval and posting contracts
Document who owns coding, approval and final invoice creation. EBS approval rules and custom SOA processes need a deliberate target mapping; a new ERP does not determine that mapping for you.
Oracle’s Payables REST API exposes invoice operations including attachments. Select an appropriate documented API or import route for the target release and use its validation and error-handling model. Oracle Integration can participate where needed; it is not mandatory for every supported connection.
Prove document and history access
Inventory the relationship between each source document and business record. Decide whether to migrate it into supported Fusion attachments, retain a repository with a designed integration, or use another approved archive arrangement. Do not assume the ERP’s underlying storage service or expose storage credentials directly to users.
Test allowed and denied access, historical retrieval, revisions and applicable records controls. Treat Managed Attachments as an integration capability to assess, not an adapter that automatically carries into Fusion.
Plan the transition and closeout
Assess whether SOA workflow can finish before cutover. If active instances must remain, define their separate treatment; reconcile unfinished ERP invoices independently. Choose staging or combined changes from the dependency and recovery plan, then rehearse the selected approach.
The WebCenter-to-Fusion migration guide covers the wider program. ECMWorks can help define the capability inventory and the evidence required before retiring a source component.