Identify the attachment implementation
Start from the business page and follow how it opens or stores documents. EBS native attachments, WebCenter Managed Attachments and custom integrations are different implementations. The label on a button does not establish which one is installed.
Oracle’s Managed Attachments configuration guide describes connections between Content Server and business applications. Its Forms, OAF and other configuration paths should be matched to the actual estate.
Document the identity relationship
Capture the business application instance, object type and record keys used to associate documents with transactions. Include custom metadata passed into check-in or scan forms, document identifiers and any downstream consumers of them.
The solution reference describes the relevant configuration tables. Use supported administration and configuration procedures; a generic sample mapping cannot establish the correct keys for an organization’s business objects.
Keep identity mapping separate from authorization. Correctly locating an invoice’s documents does not prove the current user may view or modify all of them.
Inventory the technical boundary
- Application plug-in configuration and the pages or forms enabled for attachments.
- AXF and Content endpoints used by that configuration.
- Authentication, trust and user mapping between the participating systems.
- Content profiles, security groups, accounts and other applicable access controls.
- Browser and document-viewer requirements for the selected releases.
- Custom services, redirects and generated document links.
An upgrade can affect several of these without changing the business keys. Record each dependency and the evidence needed to confirm it works on the target.
Test from the business record
Use approved examples covering the supported object types, multiple application instances where relevant, existing documents and new attachments. Verify that the right documents appear on the right record, that intended actions work, and that another user or record cannot access restricted documents.
Include historical identifiers, revisions, detached documents where supported, and links stored outside the adapter. Test both the repository and the EBS entry point; success in the Content UI alone is insufficient.
The modernization guide compares retaining the integration with changing its repository or architecture. The cloud-storage comparison explains why moving file bytes does not replace record context or access control.