Search Results owner_orgn_code

Overview

The PMITS_ROUTING_MASTER_V view is an Oracle E-Business Suite database object owned by the APPS schema and classified under the PMI – Process Manufacturing Intelligence product family. It exposes a consolidated, security-filtered presentation of Process Manufacturing routing master data drawn from the GMD (Process Manufacturing) tables. In EBS 12.1.1 and 12.2.2 the view serves as the reporting and integration layer through which routing definitions, their class assignments, ownership, status, and effective dating are surfaced to downstream analytics, concurrent programs, and custom extensions.

The view is documented as VALID and is described in ETRM metadata as the GMD Routing Master View. It is commonly referenced in the context of searches for routing class descriptors (for example, the fm_rout_cls code, which corresponds to the FM_ROUT_CLS base table joined within the view). The view is not a base table; it is a denormalized read-only construct intended for query, not for DML.

Underlying Base Objects

The view text joins several Process Manufacturing and EBS foundation objects:

• GMD_ROUTINGS_VL – the primary routing source, supplying routing identifiers, numbers, versions, quantities, status, description, unit of measure, effective dates, owner, and project.
• FND_USER – resolves OWNER_ID to a user name and description.
• FM_ROUT_CLS – provides the routing class description (this is the object referenced by the search term fm_rout_cls).
• SY_ORGN_MST – validates the owning organization code.
• GMD_STATUS – supplies the routing status meaning.
• GEM_LOOKUPS – resolves the INACTIVE_IND flag via the GME_YES_NO lookup type.

Access is further constrained by PMI_SECURITY_PKG.SHOW_RECORD(RV.OWNER_ORGN_CODE), which enforces organization-level security so that users only see routings for organizations they are authorized to view. The ETRM 12.2.2 metadata lists DUAL as a referenced synonym, reflecting the view's evaluation context rather than a data source.

Key Columns

• ROUTING_ID / ROUTING_NO / ROUTING_VERS – primary routing identity, number, and version.
• ROUTING_CLASS / ROUTING_CLASS_DESC – class code and its descriptive text from FM_ROUT_CLS.
• ROUTING_QTY / ITEM_UM – routing quantity and unit of measure.
• ROUTING_STATUS / STATUS – status code and translated meaning.
• ROUTING_DESC – routing description.
• INACTIVE_IND – lookup meaning indicating inactive routing.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE – validity window.
• OWNER_ID / OWNER / OWNER_ORGN_CODE – owning user and organization.
• PROJECT_ID / PROCESS_LOSS – project association and expected process loss.
• DELETE_MARK / TEXT_CODE – soft-delete flag and descriptive text reference.

Common Use Cases and Queries

Typical uses include routing master extracts for BI Publisher reports, integration feeds to MES or planning systems, and ad hoc analysis of routing classes. A representative query filtering by routing class is:

SELECT routing_no, routing_vers, routing_class,
       routing_class_desc, status, owner_orgn_code
FROM   apps.pmits_routing_master_v
WHERE  routing_class = :p_class
  AND  inactive_ind = 'No'
  AND  SYSDATE BETWEEN effective_start_date AND NVL(effective_end_date, SYSDATE);

Because the view enforces PMI security internally, queries automatically respect organizational access without additional WHERE clauses. It should be treated as read-only; DML must target the underlying GMD and FM tables.