Search Results remap_attachments

Overview

ECX_ATTACHMENT is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It forms part of the E-Business Suite Attachments / e-Commerce XML (ECX) infrastructure that governs how binary and textual attachments are deposited, registered, mapped, and retrieved across the applications. The package provides the programmatic layer through which the ETRM and XML Gateway components reconcile an attachment held in a document repository with the transactional record that owns it. In the EBS architecture, attachments may be stored as files on the application server file system, as BLOB content in the database, or as references to web URLs; ECX_ATTACHMENT abstracts these storage modes so that calling modules need not manage physical storage details. Its status in the documented metadata is VALID, and it is classified under the API category OTHER, indicating that it is an internal supporting utility rather than a public, released business API. The package depends on the WF_EVENT_T workflow event object type and on standard SYS constructs, confirming its role as a bridge between the Workflow event model and the attachment repository.

Key Procedures and Functions

The documented metadata lists fourteen procedures and functions, of which the following are named:

• DEPOSIT_BLOB_ATTACHMENT — Places BLOB-based attachment content into the repository, establishing the stored binary payload.
• FORMULATE_CONTENT_ID — Derives or constructs a content identifier used to uniquely reference an attachment entry.
• REGISTER_ATTACHMENT — Registers an attachment against its owning entity so it becomes visible in the standard Attachments user interface.
• REGISTER_ATTACHMENT_OFFLINE — Performs the registration step for attachments processed in an offline or deferred mode.
• REMOVE_ATTACHMENTMAPS_OFFLINE — Cleans up attachment map records in an offline context, supporting deferred removal.
• MAP_ATTACHMENTS — Creates the association between an attachment and the entity or category to which it belongs.
• REMAP_ATTACHMENTS — Rebuilds or redirects existing attachment mappings, typically after a data migration or reconfiguration.
• RETRIEVE_ATTACHMENT — Fetches an attachment's content and metadata for display or downstream processing.
• RECONFIG_ATTACHMENT — Adjusts attachment configuration, supporting changes to how attachments are stored or referenced.

No parameter signatures are published in the ETRM extract, and none should be assumed; callers should inspect the valid package specification in the database for exact arguments.

Tables Accessed

The package reads and writes several documented tables through APPS synonyms. ECX_ATTACHMENT_MAPS holds the mapping records that bind an attachment to its owning entity and category, and is central to MAP_ATTACHMENTS, REMAP_ATTACHMENTS, and REMOVE_ATTACHMENTMAPS_OFFLINE. ECX_DOCLOGS stores document log entries recording attachment activity. WF_EVENT_T and WF_PARAMETER_LIST_T belong to the Workflow event and parameter infrastructure, used when attachments are raised or handled as workflow business events. PLITBLM is the standard PL/SQL indexed table of long values used for bulk temporary storage. Together these tables allow ECX_ATTACHMENT to persist attachment metadata independently of the physical content store.

Usage Notes

ECX_ATTACHMENT is an internal utility and is not intended for direct invocation by end users. It is referenced by ECX_ERRORLOG, ECX_INBOUND_TRIG, and PO_XML_UTILS_GRP within the APPS schema, and by the package itself, indicating use in the inbound XML/ECX processing path and in purchasing XML utilities. Typical invocation occurs indirectly through XML Gateway inbound transactions, attachment-enabled forms, or concurrent programs that deposit and register content. Custom code should prefer released attachment APIs; where ECX_ATTACHMENT is called directly, developers must supply the correct owning entity and category and must ensure the package remains VALID after patching, since dependency changes in WF_EVENT_T or the ECX tables can invalidate it.