Search Results document_text_id




Overview
Explore in AI Chat

Overview

The GR_DOCUMENT_DETAILS table is a core data object within Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Process Manufacturing Regulatory Management (GR) module. Its primary function is to store the discrete text phrases that constitute the content of regulatory or compliance documents. The table acts as the detailed repository for the narrative and data-driven text lines that will be assembled, displayed, and ultimately printed on formal documents managed by the system. Its role is integral to the document generation workflow, separating content storage from document formatting and control logic.

Key Information Stored

The table stores each line of text associated with a document. While the full column list is not provided in the excerpt, the documented primary and foreign keys reveal its critical structure. The primary key is a composite of TEXT_LINE_NUMBER and DOCUMENT_TEXT_ID. This design indicates that for each unique document text identifier (DOCUMENT_TEXT_ID), the table can store multiple lines, ordered sequentially by TEXT_LINE_NUMBER. The DOCUMENT_TEXT_ID column is the foreign key linking the detail lines to their parent document header or control record. Other columns, implied by the description "Contains each phrase as it will display or print," would typically store the actual text content, potentially formatting codes, and indicators for page breaks or sections.

Common Use Cases and Queries

This table is central to any process requiring the generation, review, or audit of regulatory documents. Common use cases include the batch printing of safety data sheets (SDS), product specification sheets, or compliance certificates. A frequent reporting need is to extract the full text of a specific document for verification or archival purposes. A typical query would join GR_DOCUMENT_DETAILS to its parent table to retrieve an ordered set of lines.

  • Retrieving a Complete Document: SELECT d.text_line_number, d.text_phrase FROM gr_document_details d, gr_document_print p WHERE d.document_text_id = p.document_text_id AND p.document_number = '&DOC_NUM' ORDER BY d.text_line_number;
  • Document Content Validation: Queries are often used to find documents containing specific keywords or phrases within their detailed lines for compliance audits.

Related Objects

Based on the provided foreign key metadata, GR_DOCUMENT_DETAILS has a direct and essential relationship with the GR_DOCUMENT_PRINT table. The join is established via the DOCUMENT_TEXT_ID column. GR_DOCUMENT_PRINT likely serves as the controlling header or print queue record for a document, while GR_DOCUMENT_DETAILS holds its constituent text lines. This relationship is enforced by the foreign key constraint from GR_DOCUMENT_DETAILS.DOCUMENT_TEXT_ID to GR_DOCUMENT_PRINT. Other related objects may include views that consolidate document headers with their detail text for reporting, and APIs within the GR module for document generation and maintenance that manipulate data in this table.