Search Results gr_document_structures




Overview
Explore in AI Chat

Overview

The GR_DOCUMENT_STRUCTURES table is a core data object within the Oracle E-Business Suite (EBS) Process Manufacturing Regulatory Management (GR) module. It serves as a detailed configuration repository that defines the precise layout and content structure for regulatory documents. The table's primary role is to store the granular rules governing how a document will be formatted, displayed, or printed, including the specific ordering of sections, data points, and referenced phrases or labels. It functions as the child entity to document headings, providing the necessary structural details to render a complete, compliant document for regulatory reporting and product labeling.

Key Information Stored

The table stores configuration data that maps document templates to specific content blocks. Its composite primary key, consisting of DOCUMENT_STRUCTURES_SEQNO and DOCUMENT_HEADINGS_SEQNO, uniquely identifies each structural component within a document heading. Key columns include DOCUMENT_HEADINGS_SEQNO, which links the structure to its parent heading in the GR_DOCUMENT_HEADINGS table. The table also holds foreign key references to other master data entities, such as LABEL_CODE (linking to GR_LABELS_B), PHRASE_CODE (linking to GR_PHRASES_B), and PHRASE_GROUP_CODE (linking to GR_PHRASE_GROUP_CODES). These relationships allow the structure to dynamically incorporate standardized regulatory text, hazard labels, and grouped phrases into the final document output.

Common Use Cases and Queries

This table is central to the generation of Safety Data Sheets (SDS), product labels, and other compliance documents. A primary use case is querying the complete structure for a specific document code to drive a report or print engine. For instance, developers or functional consultants may execute queries to validate or audit document configurations. A typical SQL pattern involves joining to related master data tables to retrieve the full descriptive content for a document's structure:

  • SELECT gds.*, gph.phrase_text, glb.label_text FROM gr_document_structures gds LEFT JOIN gr_phrases_b gph ON gds.phrase_code = gph.phrase_code LEFT JOIN gr_labels_b glb ON gds.label_code = glb.label_code WHERE gds.document_headings_seqno = :headings_seqno ORDER BY gds.document_structures_seqno;

This retrieves all structural lines for a document heading in the correct sequence, along with the actual phrase and label text.

Related Objects

The GR_DOCUMENT_STRUCTURES table maintains defined foreign key relationships with several key master data and configuration tables in the GR module, as documented in the ETRM metadata:

  • GR_DOCUMENT_HEADINGS: Linked via GR_DOCUMENT_STRUCTURES.DOCUMENT_HEADINGS_SEQNO. This is the primary parent relationship, where each structure detail must belong to a document heading.
  • GR_LABELS_B: Linked via GR_DOCUMENT_STRUCTURES.LABEL_CODE. This allows the document structure to incorporate predefined regulatory hazard or warning labels.
  • GR_PHRASES_B: Linked via GR_DOCUMENT_STRUCTURES.PHRASE_CODE. This relationship pulls in standardized regulatory phrase text.
  • GR_PHRASE_GROUP_CODES: Linked via GR_DOCUMENT_STRUCTURES.PHRASE_GROUP_CODE. This enables the inclusion of a predefined group of related phrases as a single structural element.

These relationships ensure data integrity and enable the assembly of complex documents from reusable, centrally managed components.