Search Results express_description

Overview

ICX_RELATED_TEMPLATES_V is a VALID database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the ICX product family, which corresponds to Oracle iProcurement. The view is described in the ETRM repository simply as the "Related Templates View," and its functional purpose is to expose the relationships defined between Requisition Express templates (also known as Smart Form or requisition templates) used throughout the iProcurement and Purchasing requisitioning flows.

In iProcurement, administrators can define one or more Express templates using the Self-Service Purchasing setup, each carrying an EXPRESS_NAME as its unique identifier. These templates may be associated with one another through a defined relationship (for example, a template that must be used in conjunction with, or is dependent upon, another template). The ICX_RELATED_TEMPLATES_V view flattens those associations into a single readable result set, pairing each template with its related template and including both the technical names and the user-facing descriptions. This makes the view suitable for reporting, data extraction, and integration scenarios where consumers require a denormalized view of template relationships without having to write the multi-table join themselves. The inclusion of the express_name column (searched as "express_name") is central: it is the key that identifies both the primary and the related template.

Underlying Base Objects

The view is defined over two documented base objects, both exposed through APPS synonyms: PO_RELATED_TEMPLATES and PO_REQEXPRESS_HEADERS. The view text demonstrates that PO_REQEXPRESS_HEADERS is referenced twice—once as PRXT and once as PRXT2—to resolve the descriptions of both the primary template and the related template. PO_RELATED_TEMPLATES supplies the actual relationship records, carrying the EXPRESS_NAME, the RELATED_EXPRESS_NAME, and the RELATIONSHIP_TYPE that link two templates together.

• PO_RELATED_TEMPLATES (PRT) — the driving table holding the pairing of a template with its related template.
• PO_REQEXPRESS_HEADERS (PRXT) — joined on PRT.EXPRESS_NAME = PRXT.EXPRESS_NAME to retrieve the primary template's description.
• PO_REQEXPRESS_HEADERS (PRXT2) — joined on PRT.RELATED_EXPRESS_NAME = PRXT2.EXPRESS_NAME to retrieve the related template's description.

Because the view is owned by APPS, it inherits the standard EBS security model and is typically granted SELECT to reporting and integration responsibilities.

Key Columns

The view exposes five columns as documented in the ETRM metadata:

• EXPRESS_NAME — the identifier of the primary Express template.
• EXPRESS_DESCRIPTION — the descriptive name of the primary template, sourced from PO_REQEXPRESS_HEADERS.
• RELATED_EXPRESS_NAME — the identifier of the template related to the primary one.
• RELATED_EXPRESS_DESCRIPTION — the description of the related template.
• RELATIONSHIP_TYPE — the classification of the association between the two templates, indicating the nature of the relationship as stored in PO_RELATED_TEMPLATES.

Common Use Cases and Queries

Typical uses include auditing template relationships, validating setup during implementations, and feeding downstream reports or interfaces that need to know which templates are linked. A simple query to list all relationships is:

SELECT express_name, express_description, related_express_name, related_express_description, relationship_type FROM apps.icx_related_templates_v;

To isolate the relationships for a specific template, filter on the primary name:

SELECT related_express_name, related_express_description, relationship_type FROM apps.icx_related_templates_v WHERE express_name = :p_express_name;

To examine dependencies from the perspective of a related template, query the reverse direction:

SELECT express_name, express_description, relationship_type FROM apps.icx_related_templates_v WHERE related_express_name = :p_related_express_name;

These queries support setup verification, migration checks, and integration extracts where the express_name is the primary search key.