Search Results ahl_mc_node_pvt




Overview
Explore in AI Chat

Overview

APPS.AHL_DI_ASSO_DOC_GEN_PUB is a public PL/SQL API within the Oracle E-Business Suite Advanced Product Catalog (AHL) schema. Its role is to generate and manage the association between documents and the business entities they describe, a core requirement of the product information management and document control functionality delivered by the AHL modules. In Oracle EBS 12.1.1 and 12.2.2, AHL_DI_ASSO_DOC_GEN_PUB functions as a publication-layer package, meaning it exposes a supported interface intended for invocation by other application modules, wrapper packages, and customer extensions rather than being called directly by end users. The package is classified as a PUB API in the ETRM repository and holds a VALID status, confirming that it compiles cleanly and is supported in the current release. The "_DI_" segment of the name indicates its placement in the document and item integration layer of the AHL architecture, while "_ASSO_DOC_GEN_" reflects its specific responsibility for associating documents with generated content records. The package depends on FND_API, the standard Oracle Application Object Library API package used for message handling and return-status conventions, indicating that it follows Oracle's documented API error-handling and exception-propagation standards.

Key Procedures and Functions

ETRM documents a single public procedure within this package:

  • PROCESS_ASSOCIATION — This is the primary entry point for creating or maintaining a document association. As its name implies, it processes the relationship between a document record and its related title or entity, ensuring that the association metadata is persisted correctly. It is the only documented procedure exposed by this API, which suggests that the package is a focused utility rather than a broad document-management library. Because the ETRM metadata does not enumerate the parameter list, the exact signature is not reproduced here; consumers should obtain the formal parameter list directly from the package specification in the APPS schema. In practice, the procedure follows the FND_API standard return convention, exposing a return status and message fields for error reporting.

Tables Accessed

The package reads and writes the following base tables, all resolved through APPS synonyms:

  • AHL_DOCUMENTS_B — The base table storing the document header records managed through document association.
  • AHL_DOC_REVISIONS_B — The base table storing document revision information, linking each association to a specific version of the document.
  • AHL_DOC_TITLE_ASSOS_B — The association base table that holds the link records between document titles and their related entities. This is the principal target of the PROCESS_ASSOCIATION procedure.
  • AHL_DOC_TITLE_ASSOS_TL — The translation table holding language-specific, descriptive text for the association records.
  • PLITBLM — A standard Oracle Applications internal table used in API processing, typically for identifier and message handling within the FND_API framework.

Usage Notes

AHL_DI_ASSO_DOC_GEN_PUB is referenced by eight other packages, including AHL_MC_NODE_PVT and its wrapper AHL_MC_NODE_PVT_W, AHL_PC_ASSOCIATION_PUB and its private counterpart AHL_PC_ASSOCIATION_PVT, AHL_FMP_MR_DOC_ASSO_PVT, AHL_RM_ASSO_DOCASO_PVT, and the package's own wrapper AHL_DI_ASSO_DOC_GEN_PUB_W. This dependency pattern confirms that the package is invoked programmatically as a subordinate utility by higher-level public and private APIs rather than by users directly. The user query term "ahl_mc_node_pvt" appears in the dependency list, indicating that AHL_MC_NODE_PVT, a private package handling managed-content node processing, calls this package to persist document associations during node operations. Typical invocation therefore occurs from within forms-based product catalog and document validation flows, from concurrent programs that bulk-generate associations, and from custom extensions that require a supported, upgrade-safe interface. Because there is no documented concurrent program name and no direct menu function attached to this package, customizations should call PROCESS_ASSOCIATION directly and respect the FND_API return status.