Results for “chv_planners_all_v”

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

Overview

CHV_PLANNERS_ALL_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, documented as part of the CHV – Supplier Scheduling product family (Release 12.1.1 / 12.2.2) and flagged in ETRM as retrofitted. Its purpose is to expose planner identities—the individuals responsible for planning items and supplier schedules—by joining material planning data in MTL_PLANNERS with current employee records in HR_EMPLOYEES_CURRENT_V. The view therefore acts as a reconciliation layer between the Materials Management/Planning tables and the HRMS employee model, delivering a single, human-readable planner roster with names, employee numbers, location identifiers, and planner codes.

The object is frequently surfaced in searches for "mtl_planners" because it is the principal enriched projection of the MTL_PLANNERS table, which is the underlying source for planner codes in Oracle Planning. Rather than querying the raw table—where only numeric identifiers appear—consumers use CHV_PLANNERS_ALL_V to translate those identifiers into meaningful personnel data suitable for reports, concurrent programs, and supplier scheduling workflows.

Underlying Base Objects

ETRM lists the following referenced base objects: FND_PROFILE (PACKAGE), HR_EMPLOYEES_CURRENT_V (VIEW), HR_GENERAL (PACKAGE), HR_PERSON_NAME (PACKAGE), HR_SECURITY (PACKAGE), and MTL_PLANNERS (SYNONYM). The view text is a direct two-object join:

• MTL_PLANNERS (SYNONYM) — the planning source record supplying PLANNER_CODE and EMPLOYEE_ID, aliased as PLANNER_ID in the output.
• HR_EMPLOYEES_CURRENT_V (VIEW) — the HRMS current-employee view supplying FULL_NAME (via HR_PERSON_NAME logic), EMPLOYEE_NUM, LOCATION_ID, and EMPLOYEE_ID.
• HR_SECURITY, HR_GENERAL, HR_PERSON_NAME, FND_PROFILE — packages invoked beneath HR_EMPLOYEES_CURRENT_V to enforce HR security profiles, resolve person names, and derive current assignments.

The join predicate is MTP.EMPLOYEE_ID = HRE.EMPLOYEE_ID. Because HR_EMPLOYEES_CURRENT_V applies Row-Level Security, results are restricted to employees visible under the querying user's HR security profile. MTL_PLANNERS is a synonym pointing to the APPS-owned base table in the planning schema lineage.

Key Columns

• PLANNER_ID — the employee identifier from MTL_PLANNERS (published as MTP.EMPLOYEE_ID); the primary join key to HR.
• PLANNER_CODE — the short planner code stored in MTL_PLANNERS and referenced throughout planning and supplier scheduling setups.
• FULL_NAME — the formatted person name from HR_PERSON_NAME, enabling reporting without numeric joins.
• EMPLOYEE_NUM — the HR employee number for cross-referencing to HRMS and payroll reporting.
• LOCATION_ID — the employee's location identifier, useful for site-level filtering.

Common Use Cases and Queries

Typical uses include LOV validation, supplier scheduling reports, and mapping planner codes to names for planning dashboards. Example queries:

• List all visible planners: SELECT planner_code, full_name, employee_num, location_id FROM apps.chv_planners_all_v ORDER BY full_name;
• Resolve a single planner: SELECT full_name FROM apps.chv_planners_all_v WHERE planner_code = :code;
• Filter by location: SELECT full_name FROM apps.chv_planners_all_v WHERE location_id = :org_location_id;

Because HR security is enforced, the same query may return different rows for different users, a behavior to anticipate in reports and interface extracts.