eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

DBA Data [Home] [Help] [Dependency Information]

TABLE: AR.HZ_RELATIONSHIP_TYPES

Object Details

Object Name:	HZ_RELATIONSHIP_TYPES
Object Type:	TABLE
Owner:	AR
FND Design Data:	AR.HZ_RELATIONSHIP_TYPES
Subobject Name:
Status:	VALID

The HZ_RELATIONSHIP_TYPES table defines the business rules that are associated with a relationship type. A non-directional relationship type consists of a single record with the same forward (FORWARD_REL_CODE) and backward (BACKWARD_REL_CODE) relationship codes. A directional relationship type consists of two records: one for the parent (DIRECTION_CODE is P) and the other for a child (DIRECTION_CODE is C) of that parent. Forward and backward relationship codes are validated against the PARTY_RELATIONS_TYPE lookup type.
.
The primary key for this table is RELATIONSHIP_TYPE_ID.
.
The RELATIONSHIP_TYPE_ID is used as the foreign key to the HZ_CODE_ASSIGNMENTS table, in the OWNER_TABLE_ID column. You can define a relationship type as part of a relationship type group in
the HZ_CODE_ASSIGNMENTS table.

Storage Details

Tablespace:	APPS_TS_SEED
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
HZ_RELATIONSHIP_TYPES_U1	NORMAL	UNIQUE	APPS_TS_SEED	RELATIONSHIP_TYPE_ID
HZ_RELATIONSHIP_TYPES_N1	NORMAL	NONUNIQUE	APPS_TS_SEED	SUBJECT_TYPE
HZ_RELATIONSHIP_TYPES_N2	NORMAL	NONUNIQUE	APPS_TS_SEED	OBJECT_TYPE
HZ_RELATIONSHIP_TYPES_N3	NORMAL	NONUNIQUE	APPS_TS_SEED	FORWARD_REL_CODE SUBJECT_TYPE OBJECT_TYPE
HZ_RELATIONSHIP_TYPES_N4	NORMAL	NONUNIQUE	APPS_TS_SEED	BACKWARD_REL_CODE
HZ_RELATIONSHIP_TYPES_N5	NORMAL	NONUNIQUE	APPS_TS_SEED	RELATIONSHIP_TYPE SUBJECT_TYPE STATUS
HZ_RELATIONSHIP_TYPES_N6	NORMAL	NONUNIQUE	APPS_TS_SEED	ROLE

Columns

Name	Datatype	Length	Mandatory	Comments
RELATIONSHIP_TYPE_ID	NUMBER	(15)	Yes	Relationship type identifier
RELATIONSHIP_TYPE	VARCHAR2	(30)	Yes	The relationship type name. For example, CUSTOMER_SUPPLIER
FORWARD_REL_CODE	VARCHAR2	(30)	Yes	The forward relationship code used to describe relationships. For example, CUSTOMER_OF
BACKWARD_REL_CODE	VARCHAR2	(30)	Yes	The backward relationship code used to describe relationships. For example, SUPPLIER_OF
DIRECTION_CODE	VARCHAR2	(30)	Yes	Validated by DIRECTION_CODE lookup type. P for Parent, C for Child, and N for Not Directional
HIERARCHICAL_FLAG	VARCHAR2	(1)	Yes	Indicates a hierarchical relationship type
CREATE_PARTY_FLAG	VARCHAR2	(1)	Yes	Indicates if a party relationship party will be created
ALLOW_RELATE_TO_SELF_FLAG	VARCHAR2	(1)	Yes	Indicates if a party can be related to itself
SUBJECT_TYPE	VARCHAR2	(30)	Yes	Subject type of the relationship type
OBJECT_TYPE	VARCHAR2	(30)	Yes	Object type of the relationship type
STATUS	VARCHAR2	(1)	Yes	Indicates if the relationship type is inactive or active. I for Inactive, A for Active
CREATED_BY	NUMBER	(15)	Yes	Standard who column - user who created this row (foreign key to FND_USER.USER_ID).
CREATION_DATE	DATE		Yes	Standard who column - date when this row was created.
LAST_UPDATED_BY	NUMBER	(15)	Yes	Standard who column - user who last updated this row (foreign key to FND_USER.USER_ID).
LAST_UPDATE_DATE	DATE		Yes	Standard Who column - date when a user last updated this row.
LAST_UPDATE_LOGIN	NUMBER	(15)		Standard who column - operating system login of user who last updated this row (foreign key to FND_LOGINS.LOGIN_ID).
ALLOW_CIRCULAR_RELATIONSHIPS	VARCHAR2	(1)	Yes	Indicates if circular relationships are allowed using this relationship type.
OBJECT_VERSION_NUMBER	NUMBER			This column is used for locking purposes
CREATED_BY_MODULE	VARCHAR2	(150)		TCA Who column
APPLICATION_ID	NUMBER			TCA Who column
MULTIPLE_PARENT_ALLOWED	VARCHAR2	(1)		Y or N indicates whether multiple parents are allowed under this relationship type or not.
INCL_UNRELATED_ENTITIES	VARCHAR2	(1)		Y or N indicates whether entities not in relationships are included in a hierarchy or not.
ROLE	VARCHAR2	(30)		Unique relationship role lookup code based on relationship type and phrase. In the HZ_RELATIONSHIP_ROLE lookup type meaning is the plural role and description is the singular role.
DO_NOT_ALLOW_CONVERT	VARCHAR2	(1)		Indicates if nonhierarchical relationship type is prevented from conversion to hierarchical. Y for yes, N or null for no

Query Text

Cut, paste (and edit) the following text to query this object:


SELECT RELATIONSHIP_TYPE_ID
,      RELATIONSHIP_TYPE
,      FORWARD_REL_CODE
,      BACKWARD_REL_CODE
,      DIRECTION_CODE
,      HIERARCHICAL_FLAG
,      CREATE_PARTY_FLAG
,      ALLOW_RELATE_TO_SELF_FLAG
,      SUBJECT_TYPE
,      OBJECT_TYPE
,      STATUS
,      CREATED_BY
,      CREATION_DATE
,      LAST_UPDATED_BY
,      LAST_UPDATE_DATE
,      LAST_UPDATE_LOGIN
,      ALLOW_CIRCULAR_RELATIONSHIPS
,      OBJECT_VERSION_NUMBER
,      CREATED_BY_MODULE
,      APPLICATION_ID
,      MULTIPLE_PARENT_ALLOWED
,      INCL_UNRELATED_ENTITIES
,      ROLE
,      DO_NOT_ALLOW_CONVERT
FROM AR.HZ_RELATIONSHIP_TYPES;

Dependencies

[top of page]

AR.HZ_RELATIONSHIP_TYPES does not reference any database object

AR.HZ_RELATIONSHIP_TYPES is referenced by following:

APPS: HZ_RELATIONSHIP_TYPES