Search Results poc_ind

Overview

SY_ORGN_MST_VL is a bilingual (VL) view owned by the APPS schema in Oracle E-Business Suite, published under the GMA – Process Manufacturing Systems product family. It exposes process manufacturing organization master data, combining translatable organization attributes with the base organization record. The view presents one row per organization code per language, filtered to the session language through the USERENV('LANG') predicate. In EBS 12.1.1 and 12.2.2 the object retains a VALID status and remains the standard read interface for organization definitions used by Oracle Process Manufacturing (OPM) and adjacent modules.

Because it is a view rather than a table, it functions as a reporting and integration surface. It shields callers from the underlying _B/_TL table split that Oracle uses for multilingual (MLS) columns, and it resolves the language-dependent organization name automatically. The user search term "parent_orgn_code" refers directly to one of the view's exposed columns, indicating interest in organization hierarchy relationships.

Underlying Base Objects

The documented definition references two objects:

• SY_ORGN_MST_B (SYNONYM) — the base table holding non-translatable organization attributes, prefixed alias B in the view text.
• SY_ORGN_MST_TL (SYNONYM) — the translatable table holding the language-specific organization name, prefixed alias T.

These synonyms resolve to the actual GMA tables beneath the APPS schema. The join condition is B.ORGN_CODE = T.ORGN_CODE AND T.LANGUAGE = USERENV('LANG'), so the view returns only the row in the caller's session language, which is the standard MLS pattern. One row is produced per organization code per active language.

Key Columns

All base-table columns are projected unchanged, and the view adds organization name and ORGN_NAME.

• ORGN_CODE — the primary organization identifier within GMA.
• PARENT_ORGN_CODE — the code of the parent organization, defining the organizational hierarchy. This is the column most directly relevant to the user's search.
• ORGN_NAME — the translatable organization name, sourced from SY_ORGN_MST_TL.
• ORGANIZATION_ID / ORGANIZATION_NAME / ORGANIZATION_CODE — links to the HR/Inventory organization structures.
• CO_CODE — the company code associated with the organization.
• PLANT_IND — indicates whether the organization is a plant.
• INVENTORY_ORG_IND, PROCESS_ENABLED_IND, REGULATORY_ORG_IND — classification flags.
• ACTIVE_IND, DELETE_MARK — status and soft-delete indicators.
• MFG_CALENDAR_ID, RESOURCE_WHSE_CODE, TAXLOC_CODE, ADDR_ID — operational references.
• MASTER_ORGANIZATION_ID, TEMPLATE_ORGANIZATION_ID — master/template organization relationships.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 — the standard DFF context and value columns.
• WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include resolving an organization hierarchy from a child to its parent, populating LOVs for organization selection in OPM transactions, and reporting active plants. A simple hierarchy query is:

SELECT orgn_code,
       parent_orgn_code,
       orgn_name,
       active_ind
  FROM apps.sy_orgn_mst_vl
 WHERE parent_orgn_code = :p_parent
   AND active_ind = 'Y';

To list all organizations with their parent names:

SELECT c.orgn_code,
       c.orgn_name AS child_name,
       p.orgn_name AS parent_name
  FROM apps.sy_orgn_mst_vl c,
       apps.sy_orgn_mst_vl p
 WHERE c.parent_orgn_code = p.orgn_code(+);

Because the view already filters by USERENV('LANG'), no additional language predicate is required. For integration, it is safe to select specific columns rather than the full attribute set, improving performance. When RECURSIVE hierarchies are required, a CONNECT BY clause traversing PARENT_ORGN_CODE is the standard approach.