Results for “direction_code”

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

Overview

HZ_RELATIONSHIP_GROUPINGS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Receivables (AR) product family and exposes configuration metadata for relationship groupings used by Oracle Trading Community Architecture (TCA). A relationship grouping binds a set of relationship types into a named category through HZ_CODE_ASSIGNMENTS, so the view effectively answers the question: "which relationship types belong to which grouping, and what are the directional and structural properties of each?"

The view is read-only and is intended for reporting, inquiry, and integration extraction rather than transactional maintenance. Because relationship group definitions drive how parties are linked to one another in TCA, downstream modules such as Receivables, Collections, and iReceivables reference these same groupings when rendering relationship information. The view also normalizes the role code into singular and plural display meanings using AR_LOOKUPS, which makes it convenient for user-facing reports and LOV-style queries.

Underlying Base Objects

The view is defined over three documented base objects:

• HZ_CODE_ASSIGNMENTS (SYNONYM) — aliased as CA. Supplies the grouping code (CLASS_CODE) and the effective date range of the assignment. The join restricts rows to CLASS_CATEGORY = 'RELATIONSHIP_TYPE_GROUP' and OWNER_TABLE_NAME = 'HZ_RELATIONSHIP_TYPES'.
• HZ_RELATIONSHIP_TYPES (SYNONYM) — aliased as RT. Provides the relationship type identity and all behavioral attributes: forward and backward relationship codes, role, direction, hierarchical flag, party-creation flag, self-relationship allowance, subject type, and object type.
• AR_LOOKUPS (VIEW) — aliased as RR. Supplies the human-readable role meanings from lookup type 'HZ_RELATIONSHIP_ROLE' by matching LOOKUP_CODE to RT.ROLE.

The join correlates CA.OWNER_TABLE_ID with RT.RELATIONSHIP_TYPE_ID, and it applies an effective-date filter on the assignment: START_DATE_ACTIVE must be on or before SYSDATE and NVL(END_DATE_ACTIVE, SYSDATE) must be on or after SYSDATE. The relationship type itself must have STATUS = 'A' (active). Consequently the view only returns currently effective, active groupings.

Key Columns

• REL_GROUP_CODE — the relationship grouping code, sourced from CA.CLASS_CODE.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective dates of the grouping assignment.
• RELATIONSHIP_TYPE_ID / RELATIONSHIP_TYPE — surrogate key and name of the relationship type.
• FORWARD_REL_CODE / BACKWARD_REL_CODE — codes describing the relationship in each direction.
• ROLE, ROLE_MEANING_SINGULAR, ROLE_MEANING_PLURAL — the role lookup code and its singular/plural display meanings.
• DIRECTION_CODE — indicates the directional semantics of the relationship type. This is the column most commonly referenced in the user's search, because it determines whether a relationship is treated as directed, non-directed, or otherwise constrained when exposing forward/backward codes.
• HIERARCHICAL_FLAG, CREATE_PARTY_FLAG, ALLOW_RELATE_TO_SELF_FLAG — behavioral controls indicating hierarchy participation, automatic party creation, and whether a party may relate to itself.
• SUBJECT_TYPE / OBJECT_TYPE — the entity types permitted as subject and object of the relationship.

Common Use Cases and Queries

Typical uses include auditing group membership, driving relationship LOVs, and validating directional configuration before data migration. A sample query inspecting direction and hierarchy by group:

• SELECT rel_group_code, relationship_type, forward_rel_code, backward_rel_code, direction_code, hierarchical_flag FROM hz_relationship_groupings_v ORDER BY rel_group_code, relationship_type;
• SELECT rel_group_code, relationship_type, role_meaning_singular FROM hz_relationship_groupings_v WHERE direction_code = :p_direction_code;
• SELECT rel_group_code, COUNT(*) FROM hz_relationship_groupings_v GROUP BY rel_group_code;

Because the view embeds SYSDATE-based filters, results vary over time as assignments expire; reports should therefore be run with awareness of the effective-date logic when historical comparison is required.