Results for “trans_cnt”

50+ results




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

Overview

The view APPS.OP_CUST_ASC_VW1 is a customer association view owned by the APPS schema and delivered as part of the GML – Process Manufacturing Logistics product family. Its purpose is to expose relationships between a primary customer record and one or more associated customers, presenting a denormalized result set suitable for reporting, validation, and integration. The view joins the customer master table (OP_CUST_MST) with the customer association table (OP_CUST_ASC), returning association metadata alongside descriptive attributes of the associated customer such as customer number and customer name. In EBS 12.1.1 and 12.2.2 environments, the object maintains a status of VALID, indicating that it compiles correctly against the referenced base objects. Because the view resolves the association join and filters out logically deleted master records at the database level, it simplifies consumer queries and reduces the risk of reporting orphaned or inactive customer associations. The user search term assoccust_id corresponds directly to a core column of this view, confirming that the object is typically accessed to resolve the associated customer identifier into a recognizable customer number or name.

Underlying Base Objects

The documented metadata identifies OP_CUST_ASC and OP_CUST_MST as synonyms referenced by the view, along with the FND_PROFILE package. Functionally, the view is defined over the base tables behind those synonyms: OP_CUST_ASC (the customer association table) and OP_CUST_MST (the customer master table). The view text confirms an inner join in which ASSOCCUST_ID from the association table is equated to CUST_ID in the customer master, and a filter restricts results to rows where DELETE_MARK = 0. The presence of the FND_PROFILE package among referenced objects is consistent with EBS conventions in which profile option values, such as organization or operating unit context, influence which customer records are visible or valid within the process manufacturing logistics model. Because the object is a view rather than a table or synonym, it holds no data of its own and reflects changes made to the underlying association and master records in real time.

Key Columns

  • CUST_ID — Identifier of the owning (primary) customer on the association record.
  • ASSOC_TYPE — Code describing the nature of the relationship between the primary customer and the associated customer.
  • ASSOCCUST_ID — Identifier of the associated customer, joined to OP_CUST_MST.CUST_ID; this is the column matched by the search term assoccust_id.
  • ASSOCCUST_NO — Customer number of the associated customer, sourced from C.CUST_NO.
  • ASSOCCUST_NAME — Customer name of the associated customer, sourced from C.CUST_NAME.
  • DELETE_MARK — Logical deletion indicator; records with a non-zero value are excluded by the view's filter.
  • TRANS_CNT — Transaction count associated with the association record.
  • TEXT_CODE — Reference or descriptive text code attached to the association.

Common Use Cases and Queries

This view is commonly used to retrieve the human-readable identity of associated customers for a given primary customer, to validate association integrity, and to drive downstream integrations that require resolved customer numbers rather than internal identifiers. A typical lookup by associated customer uses the following form:

SELECT cust_id, assoc_type, assoccust_id, assoccust_no, assoccust_name
FROM   apps.op_cust_asc_vw1
WHERE  assoccust_id = :p_assoccust_id;

Retrieving all associations for a primary customer follows the same pattern against CUST_ID, optionally constrained by ASSOC_TYPE. Because the view already filters DELETE_MARK = 0 on the master record, consumers need not add that predicate themselves, though it may be reapplied defensively in integration code. Join conditions to other customer-facing views should use CUST_ID or ASSOCCUST_ID as appropriate, and outputs should be treated as sensitive since the object exposes customer master data governed by Oracle's proprietary and confidential information notices.