Search Results insert_ic_tran_cmp
Overview
GMI_TRAN_CMP_PVT is a private PL/SQL package body owned by APPS within the Oracle E-Business Suite Process Manufacturing (OPM/GMI) module. Its business purpose is to encapsulate the low-level transactional mechanics for inserting and retrieving records in the IC_TRAN_CMP inventory transaction completion table. This table stores the detailed component-level results of inventory transactions — quantities, units of measure, lot and grade information, posting indicators, and document references — that are generated as material movements are processed through OPM inventory and cost management routines.
Because the package is classified as PVT (private), it is not exposed as a public API for direct customer invocation. It functions as an internal engine called by higher-level GMI packages that need to write or read inventory completion rows without embedding the physical INSERT and SELECT logic inline. The source header indicates continuous maintenance across multiple release updates, including the addition of line_detail_id and the intorder_posted_ind column, reflecting the evolution of the underlying IC_TRAN_CMP structure.
Key Procedures and Functions
- INSERT_IC_TRAN_CMP — Accepts a caller-supplied IC_TRAN_CMP row image and persists it into the IC_TRAN_CMP table. The function first obtains a surrogate key by selecting the next value from the
gem5_trans_id_ssequence, assigns it totrans_id, and then performs the insert, mapping each element of the incoming row to its corresponding column. The generated key is returned to the caller through an OUT NOCOPY row parameter, and the function returns a BOOLEAN success indicator. Documented columns populated include item, line, company, organization, warehouse, lot, location, document identifiers and type, line type, reason code, transaction date and quantity, second quantity and UOM, QC grade, lot status, transaction status and UOM, operation code, GL posting indicator, event identifier, text code, auditing columns,line_detail_id, andintorder_posted_ind. - FETCH_IC_TRAN_CMP — Retrieves IC_TRAN_CMP records, providing the read counterpart to the insert routine. It supplies callers with the persisted completion data, including the
line_detail_idvalue added to satisfy historical bug fix requirements.
Both routines are internal helper functions; their signatures and column lists are tied directly to the IC_TRAN_CMP table definition and should not be treated as a stable public interface.
Tables Accessed
- IC_TRAN_CMP — The primary insert and fetch target. It holds the component-level inventory transaction completion rows produced during OPM material movement processing, and is the repository the package both writes to and reads from.
- GEM5_TRANS_ID_S — The sequence supplying the unique
trans_idsurrogate key for each new IC_TRAN_CMP row. - DUAL — Used solely to select the sequence next value prior to insertion.
All tables are referenced through APPS synonyms under the standard EBS naming convention.
Usage Notes
GMI_TRAN_CMP_PVT is invoked internally rather than directly by end users. It is referenced by one other package in the documented metadata, indicating a narrow, tightly coupled call pattern within the GMI inventory transaction stack. Typical invocation occurs during inventory transaction processing, when a parent package has assembled a completion row and requires the private routine to generate the key and persist the row, or to read it back for downstream posting logic such as GL postings or inter-organization transfers.
Customizations should not call this PVT package directly. Because it is private and its logic tracks the IC_TRAN_CMP schema, any direct dependency risks breakage on patching or upgrade. Custom code requiring this functionality should use the supported public GMI inventory APIs, or, where unavoidable, call this package only with the understanding that the interface is subject to change without notice across 12.1.1 and 12.2.2 releases.
-
APPS.GMI_TRAN_CMP_PVT SQL Statements
12.2.2
-
APPS.GMI_CMP_TRAN_PVT SQL Statements
12.2.2
-
APPS.GMI_TRAN_CMP_PVT SQL Statements
12.1.1
-
APPS.GMI_CMP_TRAN_PVT SQL Statements
12.1.1
-
PACKAGE BODY: APPS.GMI_TRAN_CMP_PVT
12.1.1
-
PACKAGE BODY: APPS.GMI_TRAN_CMP_PVT
12.2.2
-
PACKAGE: APPS.GMI_TRAN_CMP_PVT
12.1.1
-
PACKAGE: APPS.GMI_TRAN_CMP_PVT
12.2.2
-
PACKAGE BODY: APPS.GMI_CMP_TRAN_PVT
12.2.2
-
PACKAGE BODY: APPS.GMI_CMP_TRAN_PVT
12.1.1
-
PACKAGE: APPS.GMI_CMP_TRAN_PVT
12.1.1
-
PACKAGE: APPS.GMI_CMP_TRAN_PVT
12.2.2
-
APPS.GMI_TRAN_CMP_PVT dependencies on IC_TRAN_CMP
12.1.1
-
APPS.GMI_CMP_TRAN_PVT dependencies on IC_TRAN_CMP
12.1.1
-
APPS.GMI_CMP_TRAN_PVT dependencies on IC_TRAN_CMP
12.2.2
-
APPS.GMI_TRAN_CMP_PVT dependencies on IC_TRAN_CMP
12.2.2
-
APPS.GMI_TRAN_CMP_PVT dependencies on IC_TRAN_CMP
12.1.1
-
APPS.GMI_TRAN_CMP_PVT dependencies on IC_TRAN_CMP
12.2.2
-
APPS.GMI_TRAN_CMP_PVT dependencies on FND_MSG_PUB
12.1.1
-
APPS.GMI_TRAN_CMP_PVT dependencies on GMI_TRANS_ENGINE_PUB
12.2.2
-
APPS.GMI_TRAN_CMP_PVT dependencies on GMI_TRANS_ENGINE_PUB
12.1.1
-
APPS.GMI_TRAN_CMP_PVT dependencies on FND_MSG_PUB
12.2.2
-
APPS.GMI_TRAN_CMP_PVT dependencies on GMI_TRAN_CMP_PVT
12.1.1
-
APPS.GMI_CMP_TRAN_PVT dependencies on FND_API
12.1.1
-
APPS.GMI_TRAN_CMP_PVT dependencies on GMI_TRAN_CMP_PVT
12.2.2
-
APPS.GMI_CMP_TRAN_PVT dependencies on FND_API
12.2.2
-
APPS.GMI_CMP_TRAN_PVT dependencies on FND_MSG_PUB
12.2.2
-
APPS.GMI_CMP_TRAN_PVT dependencies on FND_MSG_PUB
12.1.1
-
APPS.GMI_CMP_TRAN_PVT dependencies on IC_TRAN_CMP
12.2.2
-
APPS.GMI_CMP_TRAN_PVT dependencies on IC_TRAN_CMP
12.1.1