Results for “data_position_indicator”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The GR.GR_DOCUMENT_STRUCTURES table is a core configuration object within the Process Manufacturing Regulatory Management (GR) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It defines the detailed breakdown of how a regulatory document will display or print, governing the ordering, formatting, and content selection of every heading, label, phrase, and ingredient-related section that appears on the rendered output. Before structure details can be created, the parent record in the Document Code entity must exist, along with a row defining date format and the detailed ingredient, toxic, and exposure information.

Under a heuristic Data Vault classification, this object is best modeled as a link entity. Its composite primary key combines a document structure sequence with a heading sequence, and its foreign keys resolve to multiple reference entities (labels, phrases, phrase groups, headings). This pattern is characteristic of an associative table joining independent business concepts rather than a hub (which would carry a single natural key) or a satellite (which would store descriptive attributes attached to a parent hub).

Key Information Stored

The table holds 45 documented columns. The most operationally significant are listed below.

• DOCUMENT_STRUCTURES_SEQNO — Surrogate identifier and part of the composite primary key GR_DOCUMENT_STRUCTURES_PK.
• DOCUMENT_HEADINGS_SEQNO — The second component of the composite primary key; identifies the document heading to which the structure row belongs and provides the FK to GR_DOCUMENT_HEADINGS.
• LABEL_CODE — Foreign key to GR_LABELS_B; selects the label rendered for the section.
• PHRASE_GROUP_CODE — Foreign key to GR_PHRASE_GROUP_CODES; groups reusable regulatory phrases.
• PHRASE_CODE — Foreign key to GR_PHRASES_B; identifies the specific phrase text.
• PRINT_FONT — Font specification applied when the structure is printed.
• DATA_POSITION_INDICATOR — Controls where the associated data is positioned on the document.
• DISPLAY_ORDER — Determines sequence in which the section appears on output.
• DOCUMENT_DESCRIPTION — Descriptive text for the structure entry.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit/WHO columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 — Descriptive flexfield segments available for customer-specific extensions.

The surrogate key is the composite DOCUMENT_STRUCTURES_SEQNO / DOCUMENT_HEADINGS_SEQNO; the metadata exposes no independent unique business-key candidate beyond this PK.

Common Use Cases and Queries

Regulatory authors use this table to audit how a document is assembled, verify that all heading sections resolve to valid labels and phrases, and confirm display ordering. The document_structures_seqno search term is typically resolved through a localized query.

• Retrieve all structure rows for a heading, ordered by display position:

  SELECT document_structures_seqno, label_code, phrase_code, print_font, display_order FROM gr.gr_document_structures WHERE document_headings_seqno = :heading_seq ORDER BY display_order;

• Detect orphaned or incomplete structures by left-joining the reference tables:

  SELECT s.document_structures_seqno, l.label_code, p.phrase_code FROM gr.gr_document_structures s LEFT JOIN gr.gr_labels_b l ON s.label_code = l.label_code LEFT JOIN gr.gr_phrases_b p ON s.phrase_code = p.phrase_code WHERE l.label_code IS NULL OR p.phrase_code IS NULL;

• Report on last modification activity using LAST_UPDATED_BY and LAST_UPDATE_DATE.

Related Objects

The following objects are directly referenced by or logically bound to this table:

• GR_DOCUMENT_HEADINGS — joined on DOCUMENT_HEADINGS_SEQNO; provides the parent heading context.
• GR_LABELS_B — joined on LABEL_CODE; supplies label definitions.
• GR_PHRASE_GROUP_CODES — joined on PHRASE_GROUP_CODE; provides phrase grouping.
• GR_PHRASES_B — joined on PHRASE_CODE; supplies the regulatory phrase text.
• The Document Code entity — the prerequisite parent that must contain date format and ingredient, toxic, and exposure detail rows before a structure row is created.