Results for “sport_indicator”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
HZ_PERSON_INTEREST is a Receivables (AR) module table in the Oracle E-Business Suite 12.1.1 and 12.2.2 data model. It stores information about a person's personal interests — for example sporting activities, hobbies, or extracurricular pursuits recorded against a party — and is a child of the Trading Community Architecture (TCA) party model. The table is owned by the AR schema and holds 25 documented columns in the ETRM 12.2.2 physical schema. Its status is VALID.
From a dimensional modeling perspective, the mined relationship structure suggests a hub-leaning classification. The table carries its own surrogate identifier and a foreign key to HZ_PARTIES, which is characteristic of a hub entity in a Data Vault style model; the descriptive attributes on the row (level of interest, participation, comments) behave like satellite attributes attached to that hub.
Key Information Stored
The primary key is HZ_PERSON_INTEREST_PK, defined on PERSON_INTEREST_ID, which is also the sole unique index documented (HZ_PERSON_INTEREST_U1). This surrogate key uniquely identifies each interest record and is the join anchor for dependent tables.
- PERSON_INTEREST_ID — surrogate primary key; the business-key candidate confirmed by the unique index.
- PARTY_ID — foreign key to HZ_PARTIES; associates the interest with a specific person or party.
- INTEREST_TYPE_CODE and SUB_INTEREST_TYPE_CODE — lookups classifying the interest into a category and subcategory.
- INTEREST_NAME — the descriptive name of the interest.
- LEVEL_OF_INTEREST and LEVEL_OF_PARTICIPATION — qualitative measures of how strongly the person is engaged.
- SPORT_INDICATOR — flag distinguishing sporting interests from other types.
- TEAM and SINCE — the associated team and the date from which the interest has been held.
- COMMENTS — free-text notes.
- STATUS — lifecycle state of the record.
- Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — plus the concurrent-program columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) and APPLICATION_ID, OBJECT_VERSION_NUMBER, and CREATED_BY_MODULE.
Common Use Cases and Queries
Typical scenarios include customer profiling, marketing segmentation, and enrichment of party records for higher-education or membership applications, where extracurricular interests feed admissions and alumni reporting. A common query pattern joins the interest table to HZ_PARTIES to retrieve interests for a named party:
- SELECT pi.interest_name, pi.interest_type_code, pi.level_of_interest FROM hz_person_interest pi, hz_parties p WHERE pi.party_id = p.party_id AND p.party_name = :name;
- Reporting by category: grouping records by INTEREST_TYPE_CODE and SUB_INTEREST_TYPE_CODE to profile a population.
- Extract/reconciliation involving the IGS tables that reference this entity, joining on PERSON_INTEREST_ID or DUP_PERSON_INTEREST_ID.
Related Objects
- HZ_PARTIES — parent party entity, joined on HZ_PERSON_INTEREST.PARTY_ID = HZ_PARTIES.PARTY_ID.
- IGS_AD_HZ_EXTRACURR_ACT — references this table via PERSON_INTEREST_ID.
- IGS_AD_EXCURR_INT_ALL — references this table via DUP_PERSON_INTEREST_ID.
The TCA public APIs that maintain party information are the supported means of creating and updating these records, with the table itself serving as the persistent store beneath them.
-
Information about a person's personal interests
-
Information about a person's personal interests
-
View: AST_PERSON_INTEREST_V 12.2.2
APPS.AST_PERSON_INTEREST_V·↳ AR_LOOKUPS·↳ HZ_PERSON_INTEREST·Explore AST module →
-
This table contains person's extracurricular activities details to be imported.
-
View of HZ_PERSON_INTEREST. This view is used to get person interests
APPS.CSC_HZ_PERSON_INTEREST_V·↳ AR_LOOKUPS·↳ HZ_PERSON_INTEREST·Explore CSC module →
-
View: IGS_AD_EXCURR_INT 12.1.1
APPS.IGS_AD_EXCURR_INT·↳ IGS_AD_EXCURR_INT_ALL·Explore IGS module →
-
View of HZ_PERSON_INTEREST. This view is used to get person interests
APPS.CSC_HZ_PERSON_INTEREST_V·↳ AR_LOOKUPS·↳ HZ_PERSON_INTEREST·Explore CSC module →
-
View: AST_PERSON_INTEREST_V 12.1.1
APPS.AST_PERSON_INTEREST_V·↳ AR_LOOKUPS·↳ HZ_PERSON_INTEREST·Explore AST module →
-
View: IGS_AD_EXTRACURR_ACT_V 12.1.1
APPS.IGS_AD_EXTRACURR_ACT_V·↳ FND_LOOKUP_VALUES·↳ HZ_PERSON_INTEREST·↳ IGS_AD_HZ_EXTRACURR_ACT·Explore IGS module →
-
VIEW: AR.HZ_PERSON_INTEREST# 12.2.2
-
View: IGS_AD_EXCURR_INT 12.2.2
Not implemented in this database·Explore IGS module →
-
VIEW: AR.HZ_PERSON_INTEREST# 12.2.2
-
VIEW: APPS.IGS_AD_EXCURR_INT 12.1.1
-
VIEW: APPS.IGS_AD_EXCURR_INT 12.1.1
-
TABLE: AR.HZ_PERSON_INTEREST 12.2.2
-
TABLE: AR.HZ_PERSON_INTEREST 12.1.1
-
View: IGS_AD_EXTRACURR_ACT_V 12.2.2
Not implemented in this database·Explore IGS module →
-
eTRM - CSC Tables and Views 12.1.1
Translation table to Store Drilldown details for a profile variable. This stores the column and table names for the drilldown form. Also stores the object_code, which provides the form_function to drilldown
-
eTRM - CSC Tables and Views 12.2.2
Translation table to Store Drilldown details for a profile variable. This stores the column and table names for the drilldown form. Also stores the object_code, which provides the form_function to drilldown
-
eTRM - AST Tables and Views 12.2.2
All available web searches
-
eTRM - AST Tables and Views 12.1.1
All available web searches