Results for “hz_relationship_types”

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

Overview

HZ_RELATIONSHIP_TYPES is a reference (setup) table owned by the AR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It defines the catalog of relationship types that can exist between parties and between other entities modeled in the Oracle Trading Community Architecture (TCA) / Receivables data model. Each row describes a named relationship — for example a parent-to-subsidiary hierarchy, a contact-to-organization association, or a partner-to-account link — and prescribes the directionality, cardinality, and behavioral rules that govern how that relationship is created and maintained.

Although the physical owner is AR, the object is a core TCA reference table consumed across Receivables, Customers, and other modules that build on party and account relationships. Because relationship definitions are configuration data rather than transactional data, the table is relatively static and is normally populated by seeded values and administrative setup rather than end-user entry.

From a Data Vault modeling perspective, the metadata's FK heuristic classifies this object as satellite-leaning. In practical terms it behaves as a descriptive reference set: the relationship type identifier acts as the anchor, while the many descriptive and behavioral attributes attached to each row form the satellite context that qualifies each type.

Key Information Stored

The primary key is the surrogate identifier RELATIONSHIP_TYPE_ID, enforced by HZ_RELATIONSHIP_TYPES_PK. A second unique index, HZ_RELATIONSHIP_TYPES_U1, spans RELATIONSHIP_TYPE_ID together with ZD_EDITION_NAME, marking the business-key candidate and reflecting the editioning mechanism used in 12.2.x.

• RELATIONSHIP_TYPE / FORWARD_REL_CODE / BACKWARD_REL_CODE — the internal name of the type and the labels shown when the relationship is traversed in the forward and backward directions.
• DIRECTION_CODE — indicates whether the type is directed or non-directed.
• SUBJECT_TYPE / OBJECT_TYPE — the entity types occupying the subject and object positions of the relationship; both carry foreign keys to FND_OBJECT_INSTANCE_SETS.
• HIERARCHICAL_FLAG / MULTIPLE_PARENT_ALLOWED — control whether instances form a hierarchy and whether an entity may have more than one parent.
• CREATE_PARTY_FLAG / ALLOW_RELATE_TO_SELF_FLAG — govern whether a related party is auto-created and whether self-relationships are permitted.
• ALLOW_CIRCULAR_RELATIONSHIPS / INCL_UNRELATED_ENTITIES — constrain which entities may participate and prevent or permit loops.
• DO_NOT_ALLOW_CONVERT — restricts conversion of the relationship.
• ROLE — the role associated with the type.
• STATUS — activation state of the definition.
• Standard audit and control columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER, CREATED_BY_MODULE, APPLICATION_ID, ZD_EDITION_NAME.

Common Use Cases and Queries

Typical reporting resolves a relationship instance back to its type definition to obtain readable forward/backward labels and behavioral rules.

• Listing active, hierarchical relationship types: SELECT relationship_type_id, relationship_type, forward_rel_code, backward_rel_code FROM hz_relationship_types WHERE hierarchical_flag = 'Y' AND status = 'A' ORDER BY relationship_type;
• Identifying directed types permitting a single parent: filter on DIRECTION_CODE and MULTIPLE_PARENT_ALLOWED = 'N'.
• Validating configuration before loading relationship data, and driving LOVs and pick lists in concurrent/interface programs.

Related Objects

• FND_OBJECT_INSTANCE_SETS — referenced by SUBJECT_TYPE and OBJECT_TYPE, defining the entity sets for each side of the relationship.
• HZ_GEO_STRUCTURE_LEVELS — references RELATIONSHIP_TYPE_ID, tying geography structure levels to relationship semantics.
• HZ_DSS_CRITERIA — references this table via OWNER_TABLE_ID1 in data-sharing criteria.
• HZ_RELATIONSHIPS — the transactional table holding actual relationship instances defined by these types.