Search Results ship_to_flag

Overview

The view ASO_PVT_ACCT_RELATE_V is an Oracle E-Business Suite dictionary object owned by the APPS schema and registered as VALID. It belongs to the Order Capture (ASO) product family within the broader Oracle Order Management and Customer Relationship Management (CRM) footprint. In Oracle EBS 12.1.1 and 12.2.2, this view functions as a filtered presentation layer over customer account relationship data. Its specific purpose is to expose only those customer account relationships whose status is Active, as governed by the predicate STATUS = 'A' applied to the underlying base table.

Because it is a view rather than a table, it stores no data of its own. It derives all rows and columns at runtime from its single documented base object. This design allows ASO Order Capture components, concurrent programs, and integrators to query a clean, pre-filtered set of active account relationships without embedding business logic in every calling program. The view is especially relevant to searches involving the column name related_cust_account_id, since that column is directly exposed and forms the join key for relating two customer accounts.

Underlying Base Objects

The ETRM 12.2.2 metadata documents exactly one referenced base object: HZ_CUST_ACCT_RELATE, referenced through a SYNONYM. This table resides in the Oracle Trading Community Architecture (TCA) model and stores the many-to-many relationships that can exist between customer accounts, such as parent-child, bill-to, ship-to, and other hierarchical or functional associations. Each row in HZ_CUST_ACCT_RELATE associates a primary CUST_ACCOUNT_ID with a RELATED_CUST_ACCOUNT_ID and qualifies the linkage with a RELATIONSHIP_TYPE plus bill-to and ship-to indicators.

The view adds a single relational filter, WHERE STATUS = 'A', meaning the well-known STATUS column in the base table is inactivated rows are excluded. The view projects a subset of the table's columns rather than a SELECT *, so consumers receive only the fields needed for relationship resolution: identifiers, relationship type, the two flags, and the operating unit context.

Key Columns

• CUST_ACCOUNT_ID — The primary customer account identifier, the "from" side of the relationship.
• RELATED_CUST_ACCOUNT_ID — The associated customer account identifier, the "to" side of the relationship. This is the column a user searching related_cust_account_id is attempting to resolve, typically to find the parent or counterparty account.
• RELATIONSHIP_TYPE — A lookup code classifying the nature of the linkage between the two accounts.
• BILL_TO_FLAG — Indicates whether the related account may be used as a bill-to destination.
• SHIP_TO_FLAG — Indicates whether the related account may be used as a ship-to destination.
• ORG_ID — The operating unit identifier supporting Multi-Org security and data partitioning.

Common Use Cases and Queries

Typical uses include resolving the counterparty account for a given customer, validating bill-to and ship-to eligibility across a relationship, and driving Order Capture logic that must recognize shared or hierarchical account structures. Because the view itself filters to active relationships, callers need not add a status predicate.

Find all accounts related to a specific customer:

SELECT cust_account_id, related_cust_account_id, relationship_type,
       bill_to_flag, ship_to_flag, org_id
FROM   apps.aso_pvt_acct_relate_v
WHERE  cust_account_id = :p_cust_account_id;

Locate the primary account that a related account belongs to, using the searched column directly:

SELECT cust_account_id, relationship_type, org_id
FROM   apps.aso_pvt_acct_relate_v
WHERE  related_cust_account_id = :p_related_cust_account_id;

Restrict results to a specific operating unit and to bill-to-capable relationships:

SELECT related_cust_account_id
FROM   apps.aso_pvt_acct_relate_v
WHERE  cust_account_id = :p_cust_account_id
AND    org_id = :p_org_id
AND    bill_to_flag = 'Y';

Because the view is defined over a TCA synonym and applies a fixed active-status filter, queries should treat it as read-only and avoid expecting inactivated relationships to appear.