Search Results gml_reqimport_grp




Overview
Explore in AI Chat

Overview

GML_REQIMPORT_GRP is a public PL/SQL group API package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Process Manufacturing (OPM, formerly GML) family of modules and provides the group-level validation entry point used by Process Requisitions during requisition import processing. The package carries the AUTHID CURRENT_USER declaration, meaning its SQL statements execute with the privileges of the invoking user rather than the definer, a common pattern for APIs that must respect the caller's security context and synonym resolution.

The package is identified in its header as type "Group," which in the Oracle EBS API design convention signals a wrapper that orchestrates one or more underlying entity-level or validation APIs rather than performing isolated row-level DML itself. Its stated purpose is to contain the group API for Requisition Import validations for Process Requisitions. The header revision is 115.1, dated August 2003, and the package was authored by Preetam Bamb, indicating that the interface has remained stable across the 11i to R12.1.1 and R12.2.2 upgrade paths.

Key Procedures and Functions

The package exposes a single documented procedure:

  • VALIDATE_REQUISITION_GRP — The group validation routine for requisition import. It validates a set of Process Requisition interface records before they are processed into Oracle Purchasing requisitions. The procedure follows the standard Oracle EBS API parameter conventions: it accepts an API version, an initialization flag controlling whether the message list is cleared, a validation level (defaulting to full validation), a commit flag, and a request identifier. It returns the standard trio of API outputs: return status, message count, and message data.

The package also declares a private global, G_PKG_NAME, set to 'GML_ReqImport_GRP', used for error message and debugging context, and a global G_OPM_INSTALLED flag used to detect whether OPM components are installed in the current environment. This installation check allows the group validation to be skipped or altered gracefully in instances where process manufacturing is not licensed or not installed.

Tables Accessed

The documented tables referenced through APPS synonyms reflect both the OPM item master and the standard Oracle inventory and purchasing interface structures:

  • IC_ITEM_MST — the OPM item master, used to validate that items referenced on the requisition interface lines exist and are valid process manufacturing items.
  • MTL_SYSTEM_ITEMS — the Oracle Inventory item definition, used to confirm the item is defined and transactable in the target inventory organization.
  • MTL_UNITS_OF_MEASURE — validates that the unit of measure on each interface line is a valid, enabled UOM.
  • PO_REQUISITIONS_INTERFACE — the requisition import open interface table that holds the incoming rows being validated prior to import.
  • PO_INTERFACE_ERRORS — the standard error repository where validation failures are recorded so users can review and correct rejected interface rows.
  • QC_GRAD_MST — the OPM quality grade master, used when quality grade information is supplied on process requisition lines.

Usage Notes

GML_REQIMPORT_GRP is normally invoked indirectly rather than by end users. It is called as part of the Process Requisitions import flow, typically from the requisition import concurrent program or from a forms-based "Validate" action in the Process Requisitions window, after records have been loaded into PO_REQUISITIONS_INTERFACE. Customers extending requisition import can call VALIDATE_REQUISITION_GRP directly from custom PL/SQL, passing a request identifier that scopes the set of interface rows to validate.

Because the group API follows FND_API conventions, callers should check x_return_status for FND_API.G_RET_STS_SUCCESS and inspect x_msg_count and x_msg_data when errors are returned. The p_commit flag should generally be passed as FALSE during validation so that the caller retains transaction control. The package is not referenced by any other documented package, so it sits at the top of its own call hierarchy and is safe to invoke standalone. Note that the header copyright dates to 1998 and the last revision to 2003; the package is a legacy OPM interface but remains valid and callable in R12.1.1 and R12.2.2.