Results for “customer_reciprocal_flag”

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

Overview

OKX_CUST_ACCT_RELATE_ALL_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite Contracts Integration module (OKX). It exposes the relationships that exist between customer accounts in the Oracle Receivables and Oracle Trading Community Architecture (TCA) data model. In EBS 12.1.1 and 12.2.2, this view provides a flattened, denormalized projection of the underlying relationship table, allowing downstream contract integration, order capture, and reporting processes to resolve how one customer account is related to another without querying the base table directly.

The view is registered as VALID in the ETRM metadata and is intended primarily for consumer processes within OKX that need a stable, read-only interface to customer account relationship data. Because it carries the ORG_ID column, it is an operating-unit-scoped (multi-org) view, meaning callers should filter by the appropriate operating unit or rely on the Multi-Org session context where applicable.

Underlying Base Objects

The documented base object referenced by this view is HZ_CUST_ACCT_RELATE_ALL, which the view accesses through a synonym. HZ_CUST_ACCT_RELATE_ALL is the TCA table that stores the many-to-many relationship between customer accounts, including reciprocal relationships and relationship type classification.

The view definition is a straightforward pass-through SELECT from the base table, aliased as CA:

• CA.CUST_ACCOUNT_ID mapped to CUST_ACCOUNT_ID
• CA.RELATED_CUST_ACCOUNT_ID mapped to RELATED_CUST_ACCOUNT_ID
• CA.RELATIONSHIP_TYPE mapped to RELATIONSHIP_TYPE
• CA.CUSTOMER_RECIPROCAL_FLAG mapped to CUSTOMER_RECIPROCAL_FLAG
• CA.STATUS mapped to STATUS
• CA.ORG_ID mapped to ORG_ID

Because no joins or filters are applied, the view preserves the full row population of the base table, including all operating units. The _ALL suffix in both the view and table names signals that records are not filtered by org context at the database level.

Key Columns

• CUST_ACCOUNT_ID — Identifier of the primary customer account in the relationship. Joins to HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID.
• RELATED_CUST_ACCOUNT_ID — Identifier of the customer account on the other side of the relationship. This is the column most commonly searched by users (for example, "related_cust_account_id") when tracing which accounts are linked to a given account.
• RELATIONSHIP_TYPE — Classifies the nature of the linkage between the two accounts, such as parent/child or other configured relationship categories.
• CUSTOMER_RECIPROCAL_FLAG — Indicates whether the relationship is bidirectional, that is, whether the inverse relationship is automatically recorded for the related account.
• STATUS — Lifecycle state of the relationship record, typically active or inactive.
• ORG_ID — Operating unit identifier, enabling multi-org filtering and reporting by business unit.

Common Use Cases and Queries

Typical usage includes resolving account hierarchies for contract integration, validating related-account eligibility during order or agreement processing, and building reports that group related customers for credit or billing purposes.

To find all accounts related to a specific account:

SELECT related_cust_account_id, relationship_type, status
FROM   okx_cust_acct_relate_all_v
WHERE  cust_account_id = :p_cust_account_id
AND    status = 'A';

To resolve the reverse direction, query by the related account identifier:

SELECT cust_account_id, relationship_type
FROM   okx_cust_acct_relate_all_v
WHERE  related_cust_account_id = :p_related_id;

For multi-org reporting, add an org filter to isolate results for a single operating unit and join to HZ_CUST_ACCOUNTS to obtain account names and numbers for presentation.