Results for “ship_ind”

50+ results




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

Overview

GMI_AAC_CUST_NUM_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GMI (Process Manufacturing Inventory) product family. Its documented purpose is to present process manufacturing customer information by name and number, joined with ship-to site information, company, and warehouse context. The view carries a status of VALID in both EBS 12.1.1 and 12.2.2, and is available wherever the Process Manufacturing Inventory module is licensed and installed.

The view functions primarily as a reporting and integration convenience layer. Rather than requiring callers to join customer master, warehouse master, and organization master tables individually, GMI_AAC_CUST_NUM_V exposes a flattened result set combining customer identity, ship-to site use identifier, company code, warehouse code, and shipping indicator. This makes it a suitable source for downstream reports, custom concurrent programs, Oracle Reports or BI Publisher data sources, and interface extracts that need a compact customer-by-warehouse picture without embedding the full multi-table join.

Underlying Base Objects

The documented ETRM metadata lists the referenced base objects as IC_WHSE_MST, OP_CUST_MST, and SY_ORGN_MST (all exposed as synonyms in the APPS schema), plus the FND_PROFILE package. The view text confirms the driving tables:

  • OP_CUST_MST — the Process Manufacturing customer master, supplying customer number, customer name, ship-to site use identifier, company code, and the ship indicator.
  • IC_WHSE_MST — the inventory warehouse master, supplying warehouse code and the organization code used in the join.
  • SY_ORGN_MST — the organization master, used to resolve the relationship between warehouse organization and the company code.

The documented join is: SY_ORGN_MST.ORGN_CODE equals IC_WHSE_MST.ORGN_CODE, and SY_ORGN_MST.CO_CODE equals OP_CUST_MST.CO_CODE. This effectively filters and correlates customers to the warehouses belonging to the same company. FND_PROFILE appears in the dependency list as a referenced package, consistent with typical GMI views that consult profile options for organizational or operating-unit context.

Key Columns

  • CUST_NO — the customer number from OP_CUST_MST, the primary business identifier used in order and shipment processing.
  • CUST_NAME — the customer name, providing the human-readable counterpart to the customer number.
  • OF_SHIP_TO_SITE_USE_ID — the ship-to site use identifier, linking the customer record to a specific ship-to location used in order fulfillment.
  • CO_CODE — the company (operating company) code, tying the customer to a legal entity context.
  • WHSE_CODE — the warehouse code from IC_WHSE_MST, indicating the warehouse associated with the resolved organization.
  • SHIP_IND — the ship indicator, the column most directly relevant to searches such as "ship_ind"; it flags shipping eligibility or status for the customer/warehouse combination.

Common Use Cases and Queries

Typical scenarios include building warehouse-specific customer lists for distribution planning, validating which customers are shippable to a given warehouse, and feeding external systems with a normalized customer/warehouse extract. A representative query filtering on the ship indicator is shown below.

  • List all active shipping customers with their warehouse and company:

SELECT cust_no, cust_name, of_ship_to_site_use_id, co_code, whse_code, ship_ind FROM apps.gmi_aac_cust_num_v WHERE ship_ind = 'Y' ORDER BY cust_name;

  • Locate a specific customer across warehouses:

SELECT co_code, whse_code, ship_ind FROM apps.gmi_aac_cust_num_v WHERE cust_no = :p_cust_no;

  • Restrict by warehouse for planning extracts:

SELECT cust_no, cust_name, ship_ind FROM apps.gmi_aac_cust_num_v WHERE whse_code = :p_whse AND co_code = :p_company;

Because the view is read-only and defined over master data, no DML should be issued against it. Queries benefit from indexing on the underlying masters and from binding on CUST_NO, WHSE_CODE, or CO_CODE to limit the join cost. Where performance is critical, callers should also consider the calling user's organization and profile security, since the resolution of warehouse and company context may be influenced by profile settings referenced through FND_PROFILE.