Results for “gr_physical_property_xml”

28 results




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

Overview

GR_PHYSICAL_PROPERTY_XML is a VALID database view owned by the APPS schema within the Oracle E-Business Suite, belonging to the GR product family — Process Manufacturing Regulatory Management. Its documented purpose is to present an inventory item together with its associated physical property details, expressed in a form oriented to XML generation and regulatory reporting. The view consolidates the physical, chemical, and safety-related attributes maintained against an item so that they can be emitted as structured XML content — for example, material safety data sheets, hazard communication documents, and regulatory submissions.

The name reflects the design intent: the view pivots regulated physical property values into discrete, named columns whose names correspond to XML element identifiers such as FLASHPOINT1, BOILINGPOINT1, CARGENGENICITY, and LOWERFLAMELIMIT. Rather than returning a long, narrow set of property rows, the view returns one row per organization/item combination with the properties spread across columns, which is convenient for XML publisher templates and integration payloads.

Because it is a view rather than a table, GR_PHYSICAL_PROPERTY_XML holds no data of its own; it is a read-only aggregation over the regulatory management tables in the APPS schema. Its status of VALID confirms it is compiled and available for query in both the 12.1.1 and 12.2.2 releases as documented in ETRM.

Underlying Base Objects

The view is defined over four documented base objects, all referenced through public synonyms in the APPS schema:

  • GR_INV_ITEM_PROPERTIES — the association between an inventory item (organization and item) and its physical properties; supplies ORGNID, ITEMID, and the property values themselves.
  • GR_PROPERTIES_B — the property definition table, providing PROPERTY_TYPE_INDICATOR (for example, 'A' for alpha values and 'N' for numeric values) and the property's unit-of-measure relationships.
  • GR_PROPERTY_VALUES_TL — the translated value table, supplying the meaning/description of a property value, including units of measure such as temperature and method used.
  • GR_XML_PROPERTIES_MAP — the mapping table whose XML_ELEMENT column drives the DECODE logic, translating each stored property into its corresponding XML element name.

The relationships are typical of a star-style consolidation, with GR_INV_ITEM_PROPERTIES at the center and the remaining three objects joined to resolve the element name, data type, and displayed value or unit.

Key Columns

The view exposes an identifier pair and a series of pivoted property columns. Key columns include:

  • ORGNID — the organization identifier from GR_INV_ITEM_PROPERTIES.
  • ITEMID — the inventory item identifier; ORGNID and ITEMID together define the item.
  • CONSUMERUSE, PRODUCTUSE, TRADESECRETNUMBER, CARCENGENICITY, COLOR — alpha-valued descriptive and safety attributes.
  • AUTOIGNITIONTEMP1, AUTOIGNITIONTEMP1UNIT, FLASHPOINT1, FLASHPOINT2, FLASHPOINT1TEMPUNIT, FLASHPOINT1METHODUSED, BOILINGPOINT1, BOILINGPOINT2, BOILINGPOINT1TEMPERATUREUNIT, LOWERFLAMELIMIT, and UPPERFLAMELIMIT — numeric and unit values covering flammability and thermal properties.

Each column is populated by MAX(DECODE(...)) over the mapped XML element, with numeric properties cast through TO_CHAR and alpha properties read from ALPHA_VALUE; unit and method columns resolve to G.MEANING from the translated value table.

Common Use Cases and Queries

The primary use case is generating item-level physical property XML for regulatory and safety documentation. A simple retrieval for one item is:

  • SELECT ORGNID, ITEMID, FLASHPOINT1, BOILINGPOINT1, LOWERFLAMELIMIT, UPPERFLAMELIMIT, CARCENGENICITY FROM APPS.GR_PHYSICAL_PROPERTY_XML WHERE ORGANIZATION_ID = :org AND INVENTORY_ITEM_ID = :item;

Integration scenarios typically select the full column list for a set of items to feed an XML publisher template or an outbound interface, filtering by organization to bound the result set. Reporting scenarios may aggregate across items within an organization to review completeness of property capture, or join the view back to item master tables for descriptions and categories. Because the view is read-only and consolidates four objects, queries should always include ORGANIZATION_ID and INVENTORY_ITEM_ID predicates where possible to avoid full scans of the underlying regulatory property tables.