Results for “parent_segment_id”

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

Overview

The GR.GR_DOCUMENT_RTK table is a component of Oracle Process Manufacturing Regulatory Management (GR) in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the Right-to-Know (RTK) detail information that will display or print on a regulatory document generated by the GR module. RTK requirements, imposed by OSHA and analogous state and local jurisdictions, obligate employers to disclose hazardous material information to employees and, where applicable, to the community. In EBS terms, this table holds the per-document, per-location segment detail that drives the physical layout of that disclosure content when a document is rendered.

From a data-modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure is link. This suggests the table is best understood as an associative structure connecting a document definition to a location segment value, rather than as a standalone hub or a descriptive satellite. The composite primary key reinforces that interpretation: each row associates a document with a specific location segment context.

Key Information Stored

The table is documented with nine columns, of which four participate in the business key. The most significant are:

• DOCUMENT_CODE — Identifies the RTK document to which the detail row belongs. This is the principal business-key column for the document side of the association and part of the composite primary key.
• LOCATION_SEGMENT_QUALIFIER — Qualifies the location segment being referenced, indicating which segment of the key flexfield structure the subsequent value applies to.
• LOCATION_SEGMENT_VALUE — The actual value of the qualified location segment, tying the document detail to a specific inventory or organization location.
• PARENT_SEGMENT_ID — Identifies the parent segment in the location hierarchy, supporting hierarchical location representation across the RTK detail records.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO columns that provide audit and concurrency information.

The surrogate-style primary key GR_DOCUMENT_RTK_PK is composite, spanning DOCUMENT_CODE, LOCATION_SEGMENT_QUALIFIER, LOCATION_SEGMENT_VALUE, and PARENT_SEGMENT_ID. Because this unique index is the only documented business-key candidate, the four constituent columns together define row uniqueness; there is no separately documented synthetic sequence column.

Common Use Cases and Queries

Typical usage centers on reconstructing the RTK content and location scope for a document. A common pattern lists all RTK detail rows for a given document code:

• SELECT document_code, location_segment_qualifier, location_segment_value, parent_segment_id FROM gr.gr_document_rtk WHERE document_code = :p_document_code; — retrieves the location segments that a document covers.
• SELECT r.* FROM gr.gr_document_rtk r, gr.gr_document_codes c WHERE r.document_code = c.document_code AND c.document_code = :p_code; — joins to the document header to combine descriptive attributes with RTK detail.
• SELECT r.location_segment_value, r.parent_segment_id FROM gr.gr_document_rtk r WHERE r.location_segment_qualifier = :p_qualifier; — isolates rows for a particular flexfield segment qualifier, useful for segment-level reporting.

Reporting scenarios include validating that every required location has RTK coverage before printing a regulatory document, auditing document-to-location mappings for compliance reviews, and extracting RTK detail into external MSDS or community right-to-know submissions.

Related Objects

The documented foreign keys identify the objects most closely coupled to this table:

• GR.GR_DOCUMENT_CODES — Referenced by GR_DOCUMENT_RTK.DOCUMENT_CODE; holds the document header and code definitions that drive RTK output.
• AR.AR_LOCATION_VALUES — Referenced by the location qualifier and value columns plus PARENT_SEGMENT_ID; the location flexfield value table that anchors each RTK location segment.
• GR.GR_DOCUMENT_RTK_PK — The composite unique index enforcing row identity across the four business-key columns.

Additional GR module document-definition tables follow the same GR_DOCUMENT_* naming convention and typically join on DOCUMENT_CODE. Together these objects form the document-generation layer of Process Manufacturing Regulatory Management, with this table supplying the RTK-specific location detail consumed when a regulatory document is displayed or printed.