Search Results gr_xml_properties_map_u1

Overview

GR.GR_XML_PROPERTIES_MAP is a configuration mapping table in the Oracle E-Business Suite GR (Process Manufacturing/Regulatory) schema. Its documented purpose is to serve as a "GR XML mapping table" — it associates internal field name codes and property identifiers with the XML element names used when GR data is rendered into or parsed from XML payloads. Because EBS regulatory and process manufacturing flows exchange data with external systems (labels, hazard communication, MSDS sheets, and interface files) via XML, this table provides the lookup layer that translates a stored property into its corresponding XML tag.

The table is owned by the GR schema, carries FND Design Data reference GR.GR_XML_PROPERTIES_MAP, has status VALID, and is stored in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10. Its unique index GR_XML_PROPERTIES_MAP_U1 resides in APPS_TS_TX_IDX. No foreign keys are documented, and the table neither references nor is referenced by other database objects at the schema level. Under a heuristic Data Vault classification, this object is best modeled as a standalone reference or lookup satellite — it holds descriptive mapping attributes keyed by a composite business key and shows no hub/link relationship structure, so no dimensional hub is implied by the documented metadata.

Key Information Stored

The documented physical schema for 12.2.2 contains only three columns, all of which are significant:

• FIELD_NAME_CODE (VARCHAR2) — the internal field name code that is mapped to an XML element. This is the first component of the composite business key.
• PROPERTY_ID (VARCHAR2) — the property identifier mapped to the element. This is the second component of the composite business key.
• XML_ELEMENT (VARCHAR2(40)) — the XML element name used in the generated or consumed payload.

The heuristic primary key is GR_XML_PROPERTIES_MAP_PK on the composite (FIELD_NAME_CODE, PROPERTY_ID). The unique index GR_XML_PROPERTIES_MAP_U1, also on (FIELD_NAME_CODE, PROPERTY_ID), enforces the same business-key candidate independently and is the object named in the user's search. There is no separate surrogate numeric key documented; the business key itself governs uniqueness, which is why field code plus property ID must be supplied together for any lookup.

Common Use Cases and Queries

The most frequent use is resolving which XML element corresponds to a given field/property pair during integration troubleshooting or XML template validation. A direct lookup returns the mapping:

• SELECT FIELD_NAME_CODE, PROPERTY_ID, XML_ELEMENT FROM GR.GR_XML_PROPERTIES_MAP WHERE FIELD_NAME_CODE = :field AND PROPERTY_ID = :prop;
• Reverse lookup to find all properties rendered into a particular element: SELECT * FROM GR.GR_XML_PROPERTIES_MAP WHERE XML_ELEMENT = :element;
• Inventory of the full mapping set for interface documentation or gap analysis using the documented query text.
• Detecting duplicate or orphaned element assignments by grouping on XML_ELEMENT.

Because the column set is small and the table is configuration-oriented rather than high-volume transactional, queries are typically low-cost and can safely join to GR property or field definition tables on the shared code columns.

Related Objects

The documented metadata shows GR.GR_XML_PROPERTIES_MAP as standalone: it references no database object, and the only recorded dependency is the APPS synonym GR_XML_PROPERTIES_MAP, which is the name applications code should use. In practice, related objects include the GR field definition and property definition tables whose code values supply FIELD_NAME_CODE and PROPERTY_ID, the XML generation/conversion programs that read XML_ELEMENT when producing payloads, and the GR regulatory reporting APIs that consume those payloads. Because no foreign keys are enforced, referential integrity between this table and those definition tables is maintained by application logic rather than by the database, so join columns should be validated against the actual code tables during analysis rather than assumed.