Results for “orgn_code”

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

Overview

BIS_PROCESS_MFG_ORGS_V is an Oracle E-Business Suite view owned by the APPS schema and registered as a VALID database object under the BIS – Applications BIS product family. In EBS 12.1.1 and 12.2.2, this view serves as a security-filtered lookup that exposes manufacturing organization definitions for reporting, list-of-values, and integration purposes. Rather than querying the organization master table directly, consuming forms, reports, and interfaces query this view so that the built-in process-manufacturing security rule is applied transparently at the row level.

The view is defined with a WHERE clause invoking PMI_SECURITY_PKG.SHOW_RECORD(ORGN_CODE) = 'TRUE'. This means any consumer—whether a concurrent program, an OAF page, or a custom SQL report—automatically receives only the organizations the current responsibility/user is authorized to see, based on the process-manufacturing security profile. The view is therefore best understood as a security-wrapped projection of the organization master, not as a transactional data source.

Underlying Base Objects

The documented base object is SY_ORGN_MST, the organization master table from which all columns are projected. The ETRM documentation for 12.2.2 states that no other referenced base objects are recorded, so the view is a single-table projection with one dependent function call. Every column in the view maps directly to a column of SY_ORGN_MST except for the final element, which is defined as TO_NUMBER(NULL)—a deliberate placeholder aliased as RESPONSIBILITY_ID that yields a null value.

Because the security predicate is embedded inside the view definition, the effective result set is a conjunction of the base table contents and the boolean outcome of PMI_SECURITY_PKG.SHOW_RECORD. Any change to security profile assignments in the process-manufacturing module immediately alters the rows returned, with no change required to consuming code.

Key Columns

• ID – Aliased from ORGN_CODE; carries the organization code and is typically used as the identifier in value sets and record lookups.
• VALUE – Aliased from ORGN_NAME; the human-readable organization name displayed in lists of values.
• CO_CODE – Company code associated with the organization, supporting multi-company filtering.
• ORGN_CODE – The raw organization code, retained for joins back to organization-related tables.
• ORGN_NAME – The organization name, corresponding directly to the orgn_name token users commonly search for.
• PLANT_IND – Plant indicator flag distinguishing plant-level organizations from other organization types.
• RESPONSIBILITY_ID – Populated as TO_NUMBER(NULL); always null and present only for interface compatibility with dependent value sets or reports.

Common Use Cases and Queries

A frequent requirement is populating a value set or parameter list of authorized process-manufacturing organizations. The following query returns only those organizations visible under the current security profile:

SELECT id,
       value,
       orgn_code,
       orgn_name,
       plant_ind
  FROM apps.bis_process_mfg_orgs_v
 ORDER BY orgn_name;

Because orgn_name is exposed directly, reporting layers routinely join the view to inventory or manufacturing tables on ORGN_CODE to resolve a friendly organization name:

SELECT v.orgn_name,
       m.inventory_item_id,
       m.organization_id
  FROM apps.bis_process_mfg_orgs_v v,
       apps.mtl_parameters m
 WHERE v.plant_ind = 'Y'
   AND m.organization_id = v.id;

Integration extract programs can use the view to build an allow-list of manufacturing organizations without re-implementing security logic. It is important to note that the embedded PMI_SECURITY_PKG.SHOW_RECORD call executes per row, so queries against large result sets should be filtered and indexed appropriately, and the always-null RESPONSIBILITY_ID column should not be relied upon for restricting output—security is already enforced by the view definition.