Search Results gr_item_doc_statuses




Overview
Explore in AI Chat

Overview

The GR_ITEM_DOC_STATUSES table is a core data object within Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2, specifically for the Process Manufacturing Regulatory Management (GR) module. Its primary role is to serve as a master status tracking entity for documents associated with items. The table maintains a single, current status record per unique combination of an item and a regulatory document type, effectively acting as a control point that summarizes the latest approval or change state for critical item documentation. This status is essential for enforcing compliance workflows, determining item availability for specific processes, and providing a consolidated view of an item's regulatory documentation health.

Key Information Stored

The table's structure is defined by its composite primary key, which consists of the ITEM_CODE and DOCUMENT_CODE columns. The ITEM_CODE links to the item master (GR_ITEM_GENERAL), while the DOCUMENT_CODE links to the definition of valid document types (GR_DOCUMENT_CODES). The most critical data point stored is the Item Document Status itself, which indicates the current lifecycle state (e.g., Draft, Pending Approval, Approved, Rejected) for that specific item-document pair. A pivotal supporting column is the LAST_CHANGE_DATE, which records the timestamp of the most recent status update, enabling audit trails and change tracking. The table is intentionally narrow, focusing on the current status snapshot rather than the detailed transactional history, which is typically managed in related detail tables.

Common Use Cases and Queries

A primary use case is generating compliance reports to identify items with incomplete or non-compliant documentation. For instance, a query might join GR_ITEM_DOC_STATUSES with GR_ITEM_GENERAL and GR_DOCUMENT_CODES to list all active items where a mandatory document (like a Safety Data Sheet) does not have an 'APPROVED' status. Another common operational query retrieves the status of all documents for a specific item to provide a complete compliance dashboard during item review or process order creation. The table is also central to programmatic logic within the GR module; APIs and forms frequently query this table to validate if an item's documentation is in a state that permits certain manufacturing or logistical transactions. A typical SQL pattern involves filtering on STATUS and joining to item master tables for descriptive information.

Related Objects

The GR_ITEM_DOC_STATUSES table is centrally positioned within the Regulatory Management schema, with defined relationships to several key tables:

  • Referenced by Foreign Keys (This table references):
    • GR_ITEM_GENERAL via ITEM_CODE: This is the master table for regulated items.
    • GR_DOCUMENT_CODES via DOCUMENT_CODE: This table defines the valid types of regulatory documents.
  • Referenced by Foreign Keys (Other tables reference this):
    • GR_ITEM_DOCUMENT_DTLS references via (ITEM_CODE, DOCUMENT_CODE): This detail table holds the version history, attachments, and specific data for each item-document combination, relying on the status table for the current state.

The primary key constraint GR_ITEM_DOC_STATUSES_PK on (ITEM_CODE, DOCUMENT_CODE) enforces the one-current-status rule and is the anchor for these relationships.