Search Results bill_ind




Overview
Explore in AI Chat

Overview

APPS.OP_CUST_MSTI2_VW1 is a reporting and integration view shipped in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments. It is owned by the APPS schema and exposes customer master information stored in the Order Management customer tables. The view text reveals a simple projection with no joins, filters, or aggregations: SELECT ... FROM OP_CUST_MST WHERE 1=1. The WHERE 1=1 clause is a designed placeholder that allows the seeded column list to be repointed at an install-specific source without altering the consuming interface, a pattern frequently used by Oracle for customer-facing APIs and concurrent programs.

The view is commonly categorized alongside the "MSTI" (Master, Interface) family of objects used by Oracle Order Management, Advanced Pricing, and related flows. Its purpose is to present a stable, denormalized customer record — including descriptive, credit, shipping, and flexfield attributes — to reports, interfaces, and conversion programs that must not bind directly to the evolving OP_CUST_MST table structure. Because the view selects every column without qualification, it behaves as a positional interface contract: the column order and names returned to a calling program remain consistent regardless of the underlying table changes.

Underlying Base Objects

The ETRM metadata documents two referenced objects for this view: the OP_CUST_MST synonym and the FND_PROFILE package.

  • OP_CUST_MST (SYNONYM): The immediate underlying source of all data returned by the view. It is the customer master synonym in the APPS schema, which resolves to the actual customer table in the Order Management schema. The view exposes the full OP_CUST_MST column list without transformation.
  • FND_PROFILE (PACKAGE): Although the view text does not directly call FND_PROFILE, the package is listed as a referenced object in ETRM, indicating that the view (or the installer that creates the synonym or wrapper) is evaluated against profile-option context such as org_id or user access profiles. This reinforces its role as a controlled interface to customer data.

Because the filter is 1=1, the view is effectively an unrestricted passthrough. Site-specific deployments may replace the underlying synonym or substitute the source table with an organization-restricted query, but the column list visible to consumers remains intact.

Key Columns

The view exposes over seventy columns. The most operationally significant are described below. Note that the user search term BILL_IND maps directly to a column in this view.

Common Use Cases and Queries

The view is typically consumed by inbound and outbound customer interfaces, conversion routines, and custom reports. Because it is a simple passthrough, it is safe to query without worrying about hidden business logic.

Locating bill-to customers:

  • SELECT cust_id, cust_no, cust_name, bill_ind FROM apps.op_cust_msti2_vw1 WHERE bill_ind = 'Y' AND NVL(inactive_ind,'N') = 'N';
  • SELECT cust_id, cust_no, cust_name, phone_no FROM apps.op_cust_msti2_vw1 WHERE cust_no = :p_cust_no;
  • SELECT cust_id, cust_no, last_update_date, last_updated_by FROM apps.op_cust_msti2_vw1 WHERE last_update_date >= :p_since_date;
  • SELECT c.cust_id, c.cust_name, c.bill_ind FROM apps.op_cust_msti2_vw1 c, apps.op_cust_msti2_vw1 b WHERE c.pricemcust_id = b.cust_id;

In integration scenarios, the view is used as the source for outbound flat files to external order or CRM systems, and for inbound validation lookups during customer conversion. Because it is an unrestricted selection over OP_CUST_MST, applications should still apply INACTIVE_IND and DELETE_MARK filters explicitly, and should treat BILL_IND and SHIP_IND as address-purpose flags rather than as the primary keys for sites.