Results for “hierarchy_type”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The FUN_NET_RELATED_CUSTOMERS_V view is a reporting and integration object owned by the APPS schema in Oracle E-Business Suite, residing in the FND – Application Object Library product family. It presents the network of customer accounts that are related to a given party through receivable payment hierarchy relationships. Specifically, the view exposes customer accounts reachable from a parent party by traversing the HZ_HIERARCHY_NODES structure, filtered to relationship types belonging to the PARTY_REL_GRP_AR_PAY_TOP_DOWN and PARTY_REL_GRP_AR_PAY_ANY relationship-type groups. This allows applications and reports to resolve the set of related customers — and, critically, their account numbers and names — without embedding the complex hierarchy traversal logic themselves. It is a read-only presentation layer tailored for consumption in reporting, integration, and downstream processing scenarios where a flattened, denormalized listing of related accounts is required.
Underlying Base Objects
The view is defined over several HZ synonyms. The documented referenced base objects are HZ_CODE_ASSIGNMENTS, HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_RELATE_ALL, HZ_HIERARCHY_NODES, HZ_PARTIES, and HZ_RELATIONSHIP_TYPES. The primary driver in the view text is a join between HZ_HIERARCHY_NODES and HZ_CUST_ACCOUNTS, where a hierarchy node's child party identifier is matched to the customer account's party identifier. Relationship validity is enforced via an EXISTS subquery against HZ_CODE_ASSIGNMENTS joined to HZ_RELATIONSHIP_TYPES, confirming that the relationship type is active and belongs to the AR payment hierarchy group. Effective-dating is applied with SYSDATE BETWEEN HN.EFFECTIVE_START_DATE AND HN.EFFECTIVE_END_DATE, restricting results to currently active hierarchy nodes. The view is a UNION ALL of two branches: one retrieving direct children under a given party (top-down), and one retrieving the accounts beneath the top parent for pay-any hierarchies. Together these branches yield a comprehensive related-customer network.
Key Columns
- PARTY_ID — The parent (subject) party identifier from which the relationship network is evaluated.
- RELATED_PARTY_ID — The party identifier of the related customer account found within the hierarchy.
- RELATED_CUST_ACCOUNT_ID — The customer account identifier of the related party, sourced from
HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID. - CUST_ACCOUNT_NAME — The account name of the related customer.
- CUST_ACCOUNT_NUMBER — The account number of the related customer, derived from
HZ_CUST_ACCOUNTS.ACCOUNT_NUMBER. This is the column users typically search for as "cust_account_number." - HIERARCHY_TYPE — The hierarchy or relationship type under which the related account is connected.
- RELATIONSHIP_TYPE_GROUP_NAME — A literal identifying the governing relationship-type group, either
PARTY_REL_GRP_AR_PAY_TOP_DOWNorPARTY_REL_GRP_AR_PAY_ANY.
Common Use Cases and Queries
The view is commonly used to answer questions such as "which other customer accounts are related to this account number?" and to drive reporting centered on AR payment hierarchies.
To retrieve all related customer accounts for a specific account number:
SELECT related_cust_account_id,
cust_account_number,
cust_account_name,
hierarchy_type,
relationship_type_group_name
FROM apps.fun_net_related_customers_v
WHERE cust_account_number = :p_account_number;
To list all related accounts sharing a common parent party:
SELECT party_id,
related_cust_account_id,
cust_account_number
FROM apps.fun_net_related_customers_v
WHERE party_id = :p_party_id
ORDER BY cust_account_number;
Because the view filters on SYSDATE, only currently effective relationships are returned, making it suitable for point-in-time operational reporting. Users searching for "cust_account_number" should note the related account number column is CUST_ACCOUNT_NUMBER, distinct from the account identifier columns.
-
Lookup Type: HIERARCHY_TYPE 12.2.2
Hierarchy Types for generic hierarchy's
-
Lookup Type: HIERARCHY_TYPE 12.1.1
Hierarchy Types for generic hierarchy's
-
APPS.FUN_NET_RELATED_CUSTOMERS_V·↳ HZ_CODE_ASSIGNMENTS·↳ HZ_CUST_ACCOUNTS·↳ HZ_CUST_ACCT_RELATE_ALL·Explore FND module →
-
This is a denormalized table for Process Hierarchy
-
APPS.FUN_NET_RELATED_CUSTOMERS_V·↳ HZ_CODE_ASSIGNMENTS·↳ HZ_CUST_ACCOUNTS·↳ HZ_CUST_ACCT_RELATE_ALL·Explore FND module →
-
This is denormalized table for process hierarchy in organizations
-
Contains denormalized data for hierarchical relationships.
-
This entity will contain the relationships between tables. The following relationship will be recorded:
-
This entity will contain the relationships between tables. The following relationship will be recorded:
-
Supports UI for HRMS Calendar node types only
APPS.PER_GEN_HIER_NODE_TYPES_V·↳ HR_API·↳ HR_LOOKUPS·↳ PER_GEN_HIER_NODE_TYPES·Explore PER module →
-
Supports UI for HRMS Calendar node types only
APPS.PER_GEN_HIER_NODE_TYPES_V·↳ FND_GLOBAL·↳ HR_API·↳ HR_LOOKUPS·Explore PER module →
-
View for all the process hierarchy descendents in approved and latest hierarchies.
APPS.AMW_ALL_HIER_CHILDREN_V·↳ AMW_APPROVED_HIERARCHIES·↳ AMW_LATEST_HIERARCHIES·↳ AMW_PROCESS·Explore AMW module →
-
Table: PQH_PA_WHATIF_RESULTS 12.1.1
Stores the comparative results of the current and the ?What If? benefits.
-
User profile options
-
View: AS_RPT_MANAGERS_V 12.2.2
This view shows the sales reporting hierarchy information for manager
APPS.AS_RPT_MANAGERS_V·↳ JTF_RS_GROUP_USAGES·↳ JTF_RS_REP_MANAGERS·Explore AS module →
-
APPS.HRIFV_US_FEDREP_GEN_HRCHY·↳ HRI_GEN_HRCHY_SUMMARY·↳ HR_ALL_ORGANIZATION_UNITS_TL·↳ HR_BIS·Explore HRI module →
-
View: FND_PROFILE_OPTIONS_VL 12.1.1
View of FND_PROFILE_OPTIONS and FND_PROFILE_OPTIONS_TL
APPS.FND_PROFILE_OPTIONS_VL·↳ FND_PROFILE_OPTIONS·↳ FND_PROFILE_OPTIONS_TL·Explore FND module →
-
Contains denormalized data for hierarchical relationships.
-
View: JTF_RS_REP_MANAGERS_VL 12.2.2
This view shows the member to manager and admin hierarchy across groups
APPS.JTF_RS_REP_MANAGERS_VL·↳ JTF_RS_REP_MANAGERS·Explore JTF module →
-
View: JTF_RS_REP_MANAGERS_VL 12.1.1
This view shows the member to manager and admin hierarchy across groups
APPS.JTF_RS_REP_MANAGERS_VL·↳ JTF_RS_REP_MANAGERS·Explore JTF module →
-
Denormalized table that stores the reporting hierarchy of group members
-
Denormalized table that stores the reporting hierarchy of group members
-
View: JTF_SEEDED_QUAL_USGS_V 12.2.2
View for territories qualifier form. Summary of qualifier definitions and whether they are enabled or disabled for territory use.
APPS.JTF_SEEDED_QUAL_USGS_V·↳ FND_ACCESS_CONTROL_UTIL·↳ FND_GLOBAL·↳ JTF_QUAL_TYPES·Explore JTF module →
-
Table: PQH_PA_WHATIF_RESULTS 12.2.2
Stores the comparative results of the current and the ?What If? benefits.
-
View: AS_RPT_MANAGERS_V 12.1.1
This view shows the sales reporting hierarchy information for manager
APPS.AS_RPT_MANAGERS_V·↳ JTF_RS_GROUP_USAGES·↳ JTF_RS_REP_MANAGERS·Explore AS module →
-
User profile options
-
APPS.HRIFV_US_FEDREP_GEN_HRCHY·↳ HRI_GEN_HRCHY_SUMMARY·↳ HR_ALL_ORGANIZATION_UNITS_TL·↳ HR_BIS·Explore HRI module →
-
This table stores the value for a metrics being tracked against a marketing entity e.g. the current value for metrics 'ROI' for a specific marketing campaign.
-
View: FND_PROFILE_OPTIONS_VL 12.2.2
View of FND_PROFILE_OPTIONS and FND_PROFILE_OPTIONS_TL
APPS.FND_PROFILE_OPTIONS_VL·↳ FND_PROFILE_OPTIONS·↳ FND_PROFILE_OPTIONS_TL·Explore FND module →
-
View: JTF_SEEDED_QUAL_USGS_V 12.1.1
View for territories qualifier form. Summary of qualifier definitions and whether they are enabled or disabled for territory use.
APPS.JTF_SEEDED_QUAL_USGS_V·↳ FND_ACCESS_CONTROL_UTIL·↳ FND_GLOBAL·↳ JTF_QUAL_TYPES·Explore JTF module →
-
This table stores the value for budget or quota allocation
-
This table stores the historical value for a metrics being tracked against a marketing entity e.g. date and value for metrics 'ROI' for a specific marketing campaign.
-
This table stores the value for budget or quota allocation
-
This table stores the historical value for a metrics being tracked against a marketing entity e.g. date and value for metrics 'ROI' for a specific marketing campaign.
-
Store metric values to allow for forecasting over time by certain dimensions.
-
Store detail allocation value for each node
-
Store detail allocation value for each node
-
This table stores the value for a metrics being tracked against a marketing entity e.g. the current value for metrics 'ROI' for a specific marketing campaign.
-
This table stores the association between a qualifer and the transaction type of a source via JTF_QUAL_TYPE_USGS (stores association between SOURCES/QUALIFER TYPES tables).
-
This table stores the association between a qualifer and the transaction type of a source via JTF_QUAL_TYPE_USGS (stores association between SOURCES/QUALIFER TYPES tables).
-
Store metric values to allow for forecasting over time by certain dimensions.
-
VIEW: HR.HR_DM_HIERARCHIES# 12.2.2