Search Results gr_properties_pk

Overview

The GR_PROPERTIES_B table is a core data entity within the Process Manufacturing Regulatory Management (GR) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It functions as the master definition table for property codes, which are standardized attributes used to characterize and classify regulatory labels. A single label can be associated with multiple property codes, enabling a flexible and detailed structure for capturing diverse regulatory information. The table's primary role is to serve as the central reference point for all property definitions, ensuring data integrity and consistency across the regulatory management system.

Key Information Stored

While the provided metadata does not list specific column names beyond the primary key, the table's structure is designed to define the essential characteristics of a property. The primary column is PROPERTY_ID, a unique system-generated identifier that serves as the primary key for the table. This ID is referenced by all related entities. Based on its described purpose, the table likely contains columns for the property code itself (a unique identifier or short name) and an indicator or flag that defines the property's type or behavior (e.g., mandatory, optional, data type). The "_B" suffix indicates it is the base table, which typically holds the core transactional columns, while translatable descriptive information is stored in a separate "_TL" (Translation) table.

Common Use Cases and Queries

This table is central to queries that list, report on, or validate the properties available for defining regulatory labels. Common use cases include administrative setup and maintenance of the property master list, and generating reports of all properties used within the system. A typical query would join the base table with its translation table to retrieve user-friendly names in a specific language. For example, to retrieve a list of all active property codes and their descriptions, a developer might use a SQL pattern similar to the following:

• SELECT b.PROPERTY_CODE, tl.DESCRIPTION FROM GR.GR_PROPERTIES_B b, GR.GR_PROPERTIES_TL tl WHERE b.PROPERTY_ID = tl.PROPERTY_ID AND tl.LANGUAGE = USERENV('LANG');

Another critical use case involves data validation, where the PROPERTY_ID from this table is used to ensure that entries in related tables like GR_LABEL_PROPERTIES reference a valid, predefined property.

Related Objects

The GR_PROPERTIES_B table is at the center of a key data model, with several important objects referencing its primary key. The documented foreign key relationships are as follows:

• GR_LABEL_PROPERTIES: Links properties to specific labels via the GR_LABEL_PROPERTIES.PROPERTY_ID column. This is the primary transactional relationship that applies property definitions to actual regulatory labels.
• GR_PROPERTIES_TL: Stores the translated descriptions and names for each property, joined on GR_PROPERTIES_TL.PROPERTY_ID. This supports multilingual implementations.
• GR_PROPERTY_VALUES_TL: References the property master to provide translated values for properties that have predefined lists of allowed values, joined on GR_PROPERTY_VALUES_TL.PROPERTY_ID.

All joins to these related tables are performed using the GR_PROPERTIES_B.PROPERTY_ID column, which is the primary key for the GR_PROPERTIES_PK constraint.