Results for “rhx_dp_l_org_v”

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

Overview

RHX_DP_L_ORG_V is a reporting view registered in the Oracle E-Business Suite environment under the MRP (Master Scheduling/MRP) product family. The suffix and naming convention indicate it was delivered as part of a retrofit package — the ETRM metadata explicitly describes it as "- Retrofitted" — meaning the object was created or re-created to reconcile custom or previously existing logic with the standard EBS data model during an upgrade or migration effort. The view presents a narrowly scoped list of inventory organizations: its entire body returns organization identifier, code, and name from the ORG_ORGANIZATION_DEFINITIONS table.

Its functional role is that of a lightweight lookup rather than a transactional or analytical view. Rather than exposing organization attributes across all organization classifications, RHX_DP_L_ORG_V surfaces a single, de-duplicated row per organization, which makes it suitable as a driving source for LOV (list of values) queries, parameter prompts in concurrent programs, and integration extracts that must resolve an organization to a human-readable code and name. In the MRP context, such a view is typically consumed by planning, scheduling, and data-pull programs that need to iterate over organizations without repeating the classification filters commonly applied against ORG_ORGANIZATION_DEFINITIONS.

The ETRM metadata records that the view is "Not implemented in this database," which indicates the definition exists in the object registry but is absent from the physical schema of the environment documented. Consequently, references to the view in deployed code should be validated against the target instance before reliance.

Underlying Base Objects

The view is defined over a single base object: ORG_ORGANIZATION_DEFINITIONS (aliased OOD). This is the standard EBS organization definition table that stores organization identifiers, codes, names, and the classification flags (for example, inventory organization, operating unit, and legal entity indicators) that determine which business functions an organization may perform. Because the view applies no classification predicate, every organization defined in the table is a candidate row.

The view text applies a "WHERE 1=1" clause, a common idiom used in generated SQL to provide an unconditional predicate placeholder that simplifies the programmatic appending of additional filter conditions. In practice this clause is a no-op; the result set is the full projection of the three selected columns across ORG_ORGANIZATION_DEFINITIONS. The dependency chain is therefore shallow: a single base table feeds a single view, with no joins, unions, or aggregations documented. The ETRM metadata lists no referenced base objects under the documented view metadata, which is consistent with the view being treated as a retrofit artifact whose dependency on ORG_ORGANIZATION_DEFINITIONS is implicit in the source text.

Key Columns

• ORGANIZATION_ID — The surrogate primary key of the organization. This numeric identifier is the value stored on transactional and planning records throughout EBS and is the join key of choice when associating the view with inventory, item, or MRP data.
• ORGANIZATION_CODE — The short alphanumeric code that uniquely identifies the organization to users. It is typically the value displayed in list-of-values windows and used in interface file specifications.
• ORGANIZATION_NAME — The descriptive name of the organization, suitable for reporting labels, headers, and reconciliation output.

No additional columns, derived expressions, or computed attributes are documented. The view exposes only these three attributes, all sourced directly from ORG_ORGANIZATION_DEFINITIONS without transformation.

Common Use Cases and Queries

Typical usage centers on resolving organization identifiers to codes and names within MRP-related reports and integration programs. A parameter prompt or LOV query might select code and name ordered by code, while an extract program would join on ORGANIZATION_ID. Illustrative statements include:

• SELECT organization_id, organization_code, organization_name FROM rhx_dp_l_org_v ORDER BY organization_code;
• SELECT organization_name FROM rhx_dp_l_org_v WHERE organization_code = :p_org_code;
• SELECT o.organization_code, o.organization_name FROM rhx_dp_l_org_v o WHERE o.organization_id IN (SELECT organization_id FROM mtl_parameters);

When the object is not implemented in the target database, equivalent results can be obtained directly from ORG_ORGANIZATION_DEFINITIONS. The "Roark Tool Room" search term associated with this lookup suggests a practical example scenario: a user resolving a specific inventory organization — such as a tool room operation — to its identifier and code for use in a planning or scheduling query. Because the view applies no classification filter, callers requiring only inventory organizations should add an explicit predicate against organization_id IN (SELECT organization_id FROM mtl_parameters) or an equivalent classification join to avoid returning non-inventory organizations.