Search Results g_attach_entity_name

Overview

The APPS.OKC_CONTRACT_DOCS_GRP package body is a group (GRP) layer API within the Oracle E-Business Suite Contracts (OKC) module, responsible for managing the lifecycle of documents and attachments associated with contract records. It mediates between the Oracle Contracts application and the common Oracle Attachment infrastructure (FND_DOCUMENTS, FND_ATTACHED_DOCUMENTS), providing a controlled, business-rule-aware mechanism for inserting, updating, deleting, versioning, and copying contract-related documents. It also manages quality assurance status and the designation of primary terms documents. The package follows the standard EBS API conventions — reference to G_RET_STS_SUCCESS, G_RET_STS_ERROR, and G_FND_APP, error token handling, and category constants such as G_CONTRACT_DOC_CATEGORY and G_SUPPORTING_DOC_CATEGORY — indicating that it participates in the multi-layer (API/GRP) architecture used across OKC. It supports Oracle EBS 12.1.1 and 12.2.2, and is referenced by seven other packages, making it a shared dependency for contract documentation processing.

Key Procedures and Functions

• INSERT_CONTRACT_DOC — Creates a new contract document record, associating a document with a contract and its appropriate document category.
• UPDATE_CONTRACT_DOC — Modifies attributes of an existing contract document.
• DELETE_CONTRACT_DOC — Removes a contract document association.
• VERSION_ATTACHMENTS — Creates a new version of existing attachments, supporting the versioning model inherent to Oracle Attachments.
• DELETE_DOC_ATTACHMENTS — Deletes the attachments tied to a document.
• DELETE_VER_ATTACHMENTS — Deletes attachments associated with a specific document version.
• COPY_ATTACHMENTS — Copies attachments from one context to another; referenced by the G_COPY_ALL_DOCS constant.
• QA_DOC — Performs or records quality assurance of a contract document, using status constants (G_QA_STS_SUCCESS, G_QA_STS_ERROR, G_QA_STS_WARNING).
• IS_PRIMARY_TERMS_DOC_MERGEABLE — Determines whether a primary terms document is eligible to be merged.
• GET_PRIMARY_TERMS_DOC_FILE_ID — Retrieves the file identifier for a primary terms document.
• HAS_PRIMARY_CONTRACT_DOC — Returns whether a contract has a designated primary document.
• CLEAR_PRIMARY_DOC_FLAG — Clears the primary document indicator on a contract document.

Tables Accessed

The package operates primarily against the Oracle Attachments and Contracts tables through APPS synonyms. FND_DOCUMENTS and FND_DOCUMENTS_TL hold document definitions and translated names; FND_ATTACHED_DOCUMENTS and FND_ATTACHED_DOCUMENTS_S store the attachment-instance links; FND_DOCUMENT_CATEGORIES supplies the category definitions referenced by the category constants. OKC_CONTRACT_DOCS and OKC_BUS_DOC_TYPES_B hold contract-specific document and business document type data, while OKC_DOC_QA_LISTS supports the QA procedures. FND_NEW_MESSAGES supports messaging, and DUAL and PLITBLM are used for utility/PL/SQL table operations.

Usage Notes

OKC_CONTRACT_DOCS_GRP is typically invoked indirectly by higher-level OKC APIs and by Oracle Contracts forms rather than directly by end users. A user searching for insert_contract_doc will most likely be tracing how contract documents are created when a contract is authored, copied, or versioned. Because the GRP layer wraps the underlying DML, customizations should call this package rather than inserting into OKC_CONTRACT_DOCS or FND attachment tables directly, preserving the primary-document, category, and QA logic. The procedures may also be reached from concurrent programs or workflow activities that generate, copy, or validate contract deliverables.