Results for “data_seeded”

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

Overview

ECX_XREF_STANDARDS_VL is a multilingual (VL) view owned by the APPS schema within the ECX — XML Gateway product. It presents code conversion standard detail, exposing the cross-reference values that the XML Gateway uses to translate internal codes into externally exchanged values (and vice versa) during outbound and inbound message processing. Cross-reference standards define how a value stored in an EBS application maps to a corresponding value in a trading partner's system or a standard vocabulary such as EDI, XML, or a partner-specific identifier set. Because the view joins the base table to its translation table and filters on the session language, it returns the description in the language of the connected user, making it suitable for both runtime lookups and reporting.

The name searched by the user, xref_int_value, is not a standalone object; it is a column exposed by this view. It represents the internal value side of a cross-reference mapping — the code as held inside EBS — whereas xref_std_value holds the external or standard value. This pairing is the essence of the cross-reference function the view documents.

Underlying Base Objects

Per the ETRM metadata, ECX_XREF_STANDARDS_VL is defined over two synonyms: ECX_XREF_STANDARDS_B (the base table holding the non-translatable attributes) and ECX_XREF_STANDARDS_TL (the translation table holding language-specific descriptions). The view joins them on XREF_STANDARD_ID and restricts the translation row to the current session language:

• ECX_XREF_STANDARDS_B — supplies identifiers, codes, seeded flag, and audit columns.
• ECX_XREF_STANDARDS_TL — supplies DESCRIPTION for the row in USERENV('LANG').

The view text selects B.ROWID as ROW_ID and projects the B columns alongside T.DESCRIPTION. Because it is a VL view, it automatically handles language fallback, returning the translation matching the user's language environment. In Oracle EBS 12.1.1 and 12.2.2 the definition is consistent; the differences between releases are in the surrounding XML Gateway setup and table growth, not in this view's structure.

Key Columns

• ROW_ID — the base-table ROWID, useful for direct row addressing.
• XREF_STANDARD_ID — primary identifier of the cross-reference standard row; the join key between the _B and _TL tables.
• XREF_CATEGORY_ID — identifies the category (e.g., a transaction type or document type) to which the standard belongs.
• STANDARD_ID — identifies the standard or trading partner context the mapping applies to.
• XREF_STANDARD_CODE — the code identifying the standard entry.
• XREF_STD_VALUE — the external/standard value to which the internal value converts.
• XREF_INT_VALUE — the internal EBS value that maps to the standard value. This is the column the user searched for.
• DATA_SEEDED — indicates whether the row was delivered as seed data by Oracle (Y) or created by the customer.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.
• DESCRIPTION — language-specific description from the _TL table.

Common Use Cases and Queries

Typical scenarios include validating or explaining a code conversion used in an XML Gateway message, auditing seeded versus customer-defined mappings, and reporting the internal-to-standard pairings for a given category or standard. For example, to locate the internal value associated with a known standard value:

• SELECT xref_standard_id, xref_standard_code, xref_std_value, xref_int_value FROM apps.ecx_xref_standards_vl WHERE xref_std_value = :std_val;

To review all mappings within a category:

• SELECT xref_standard_code, xref_std_value, xref_int_value, description FROM apps.ecx_xref_standards_vl WHERE xref_category_id = :cat_id ORDER BY xref_standard_code;

To distinguish seeded data from user-maintained rows:

• SELECT xref_standard_id, xref_int_value, data_seeded FROM apps.ecx_xref_standards_vl WHERE data_seeded = 'Y';

Queries joining to ECX_XREF_CATEGORIES or ECX_XREF_STANDARDS metadata can expand these results into full conversion documentation, making the view a reliable reference for XML Gateway integration troubleshooting and support reporting.