Results for “remove_attachmentmaps_offline”

8 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

ECX_ATTACHMENT is a public PL/SQL package body owned by APPS and classified under the ETRM taxonomy as OTHER. It provides the attachment-handling infrastructure for Oracle E-Business Suite's e-commerce and Workflow notification framework, enabling documents, files, and BLOB content to be deposited, registered, mapped, and retrieved against business entities. The package is a foundational utility for features that attach supporting content to a transactional record — for example, a purchase order attachment, an expense receipt, or an approval notification attachment routed through Oracle Workflow. The header stamp ($Header: ECXATCHB.pls 120.2 2006/05/24) indicates a mature, stable shipping module that has been carried forward into EBS 12.1.1 and 12.2.2 without structural change. Internally it defines private constants for an embedded program name, tag, key, entity, a sequence seed (88) and interval (10), plus delimiter constants (!, :, @) and a record type that decomposes a content identifier, file identifier, and data type. These internals support parsing of the composite attachment reference strings exchanged between runtime and offline (BES) execution modes.

Key Procedures and Functions

  • DEPOSIT_BLOB_ATTACHMENT — Stores a BLOB payload against a main document identifier, capturing file name, content type, expiration date, language, character set, and file format, and returning a generated file identifier.
  • FORMULATE_CONTENT_ID — Builds the composite content identifier string used to reference an attachment across the ECX framework.
  • REGISTER_ATTACHMENT — Creates the attachment registration and its association with the target entity in the online runtime.
  • REGISTER_ATTACHMENT_OFFLINE — Performs the equivalent registration when the calling context is offline (BES), buffering reference maps in memory for later reconciliation.
  • REMOVE_ATTACHMENTMAPS_OFFLINE — Cleans up attachment reference maps accumulated during offline processing.
  • MAP_ATTACHMENTS — Establishes the mapping between attachment content and the entities to which it applies.
  • REMAP_ATTACHMENTS — Reassigns existing attachment mappings when the underlying entity or document identifier changes.
  • RETRIEVE_ATTACHMENT — Reads attachment content and metadata back for display or downstream processing.
  • RECONFIG_ATTACHMENT — Adjusts attachment configuration or representation, typically after a copy, upgrade, or environment change.
  • get_attachment_records (private) — Parses a delimited attachment string into a table of cid/fid/dataType records for internal consumption.

Tables Accessed

  • ECX_ATTACHMENT_MAPS — The principal persistence store for the relationships this package creates, updates, and removes.
  • ECX_DOCLOGS — Maintains the document log used to track deposited attachment content and file identifiers.
  • WF_EVENT_T — Workflow event table, enabling attachment changes to raise and consume business events in the Workflow engine.
  • WF_PARAMETER_LIST_T — Supplies parameter lists when attachments are passed to Workflow processes.
  • PLITBLM — The PL/SQL index-by table memory structure used for in-memory handling of attachment record collections.

Usage Notes

ECX_ATTACHMENT is not intended for end-user invocation. It is called programmatically by forms and concurrent programs that manage attachments, by Oracle Workflow notification handlers (hence the WF_EVENT_T dependency), and by three other APPS packages that reference it. Customizations should call the public procedures only, supplying a valid main document identifier and file metadata; the offline variants are reserved for deferred (BES) execution where connectivity to the database is intermittent and reference maps must be reconciled later. Because registration writes to ECX_ATTACHMENT_MAPS and ECX_DOCLOGS, callers must ensure the surrounding transaction commits consistently with the attachment operation, and should avoid direct DML on these tables in favor of the package APIs.