Search Results igs_as_doc_details_s

Overview

The APPS.IGS_AS_DOC_DETAILS_PKG package body is a core component of the Oracle E-Business Suite Student System (the IGS schema family), specifically within the Academic Support / Advanced Studies document-tracking functional area. Its principal business role is to manage the detail records associated with academic documents — the individual line items, requirements, or delivery attributes attached to a parent document order. In EBS Release 12.1.1 and 12.2.2 the package holds VALID status in the APPS schema and is classified as an OTHER API, meaning it is primarily a table-handling package rather than a published public interface.

Functionally, the package encapsulates the data-manipulation logic for the IGS_AS_DOC_DETAILS entity. It applies the standard Oracle EBS API conventions — initialization via FND_API, message handling through FND_MSG_PUB and FND_MESSAGE, and environment context from FND_GLOBAL — so that callers receive structured success/error responses rather than raw SQL exceptions.

Key Procedures and Functions

The documented package exposes ten procedures and functions, which follow the conventional Oracle EBS table-handler pattern:

• INSERT_ROW — Inserts a new document-detail record into the base table, applying defaulting and validation logic.
• LOCK_ROW — Obtains a row-level lock on an existing document detail, typically used ahead of an update to enforce concurrency control.
• UPDATE_ROW — Modifies an existing document-detail record after validation.
• ADD_ROW — A higher-level wrapper that combines insert/lock/update behaviour, allowing a caller to add or amend a row through a single entry point.
• DELETE_ROW — Removes a document-detail record, subject to any dependent-data checks.
• GET_PK_FOR_VALIDATION — Resolves the primary key for a detail record so that it can be validated against the parent entity.
• GET_FK_IGS_AS_DOC_DLVY_TYP — Retrieves the foreign-key value relating the detail to the document delivery type.
• GET_FK_IGS_CA_INST — Retrieves the foreign key linking the detail to the institution (IGS_CA_INST) record.
• GET_FK_IGS_AS_ORDER_HDR — Resolves the foreign key that ties the detail line to its parent order header.
• BEFORE_DML — A trigger-style procedure invoked before insert/update/delete operations to enforce attribute-level validation and audit stamping.

Tables Accessed

Through APPS synonyms, the package reads and writes the following documented tables:

• IGS_AS_DOC_DETAILS — the primary base table holding document-detail records; the INSERT/UPDATE/DELETE procedures operate here.
• IGS_AS_DOC_DETAILS_S — the sequence (or secondary) object associated with the base table, used for key generation and lookups.
• IGS_AS_DOC_DLVY_TYP — lookup for document delivery types referenced by detail rows.
• IGS_AS_ORDER_HDR — the parent document order header to which details belong.
• IGS_AS_DOCPROC_STUP, IGS_AS_DUP_DOCS, and IGS_AS_DUP_DOCS_PKG — supporting document-processing setup and duplicate-handling logic.
• HZ_PARTIES — the trading-community party (student/applicant) associated with the document.
• DUAL — used for single-row utility queries.

Related APIs referenced include IGS_AS_DOCUMENTS_API, IGS_AS_ORDER_HDR_PKG, IGS_AS_PROD_DOC, IGS_AS_NOTIFY_STUDENT, IGS_AS_SS_DOC_REQUEST, and IGS_CA_INST_PKG, confirming the package participates in the wider document-lifecycle workflow.

Usage Notes

Because this is an OTHER-classified API, it is not intended as a public integration point. It is invoked internally by higher-level packages and by the Student System forms and concurrent programs that maintain academic document orders. Five other packages reference it, while the metadata records no database object referencing it externally — the expected pattern for a leaf-level table handler.

Customisations should call the procedures through the FND_API message stack rather than issuing direct DML on IGS_AS_DOC_DETAILS, so that BEFORE_DML validation, foreign-key checks against delivery type, institution, and order header, and standard error handling are honoured. The presence of both IGS_AS_DOC_DETAILS_PKG and IGS_AS_DOC_DETAILS_S in the reference list explains why the object is frequently located via searches for the sequence or the package together.