Results for “to_whse”

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

Overview

OP_CUST_MSTI2_VW1 is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, defined within the Process Manufacturing Logistics (GML) product family. As its description states, it is a Customer Master table view — a read-only projection over the GML Customer Master table that exposes the full set of customer attributes required by downstream order processing, pricing, and interface programs. Because it is defined as a simple pass-through view (a straight column projection with a trivial WHERE 1=1 predicate), it presents no transformation logic of its own; its value lies in providing a stable, named access path to customer master data without requiring consumers to reference the synonym or base table directly. The view is documented as VALID in ETRM 12.2.2 and is compatible with EBS 12.1.1 and 12.2.2.

For users searching on "cust_currency," this view is significant because the CUST_CURRENCY column is exposed directly, making the view a convenient source for the default transaction currency defined against each customer record.

Underlying Base Objects

The view is documented as being defined over the following referenced objects:

• OP_CUST_MST (SYNONYM) — the base Customer Master table (via its APPS synonym) that holds the authoritative customer records. The view text confirms a direct SELECT ... FROM OP_CUST_MST with no joins or filters beyond WHERE 1=1.
• FND_PROFILE (PACKAGE) — the standard EBS profile option package. Its inclusion in the dependency list reflects the view's participation in multi-org or profile-driven security patterns typical of GML customer master objects, where org and profile context govern which customer rows are visible.

Because the view performs no data transformation, every column in OP_CUST_MST is carried through unchanged, including the DELETE_MARK and TRANS_CNT audit columns that consumers must filter on in their own queries.

Key Columns

The view exposes approximately 100 columns. The most commonly referenced ones include:

• CUST_ID / CUST_NO — the internal primary key and the user-facing customer number.
• CUST_NAME, PHONE_NO, FAX_NO, TELEX_NO, ALTCUST_NO — descriptive identity and contact data.
• CUST_CURRENCY — the default currency associated with the customer, used to drive pricing, invoicing, and receivables defaults.
• TERMS_CODE, FRTBILL_MTHD, CREDIT_LIMIT — payment terms, freight billing method, and credit exposure limits.
• SLSREP_CODE, COMMISSION_CODE, PRICECUST_ID, CUST_TERRITORY — sales and pricing attributes governing who sells to and prices the customer.
• TAXLOC_CODE, TAXCALC_CODE, CUST_CLASS, CUSTGL_CLASS — tax and accounting classification.
• INACTIVE_IND, BILL_IND, SHIP_IND, BACKORDER_IND — status and behavior flags that must be honored in transactional logic.
• ATTRIBUTE1 through ATTRIBUTE30, ATTRIBUTE_CATEGORY — the standard EBS descriptive flexfield columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns.

Common Use Cases and Queries

Typical uses include customer currency lookups for pricing and order entry interfaces, batch extraction of active customer records into external systems, and reconciliation of credit or terms data. Because the view applies no filtering, all consumer queries must exclude soft-deleted rows.

Retrieving the active customer currency for a given customer:

• SELECT cust_id, cust_no, cust_name, cust_currency FROM apps.op_cust_msti2_vw1 WHERE cust_no = :p_cust_no AND NVL(delete_mark,0) = 0;

Listing active customers by currency for interface processing:

• SELECT cust_no, cust_name, cust_currency, terms_code, credit_limit FROM apps.op_cust_msti2_vw1 WHERE NVL(delete_mark,0) = 0 AND NVL(inactive_ind,'N') = 'N' ORDER BY cust_currency, cust_no;

Joining customer currency into an order staging query:

• SELECT s.order_no, v.cust_no, v.cust_currency FROM xx_order_stg s, apps.op_cust_msti2_vw1 v WHERE s.cust_id = v.cust_id AND NVL(v.delete_mark,0) = 0;

All queries should reference the APPS synonym and observe standard EBS access controls.