Results for “chv_schedulers_all_v”

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

Overview

The CHV_SCHEDULERS_ALL_V view is a reporting object within the Oracle E-Business Suite Supplier Scheduling (CHV) module. It is owned by the APPS schema and holds a status of VALID in both release 12.1.1 and 12.2.2. The view exposes the set of employees who have been designated as schedulers on Approved Supplier List (ASL) attribute records, joining that designation against the current employee directory. In effect, it answers the question of which named individuals within the enterprise are acting as supplier schedulers, and where they are located.

The object is documented as "Retrofitted," indicating that it was carried forward from an earlier EBS data model into the current schema and should be treated as a preserved legacy interface rather than a newly engineered entity. Its principal role is to support lookups and list-of-values presentation — for example, populating the scheduler field on supplier scheduling and ASL enquiry screens — and to serve as a convenient join point for reports and integrations that need to resolve a SCHEDULER_ID into a human-readable name and employee number.

Underlying Base Objects

The view is defined as a DISTINCT projection over two logical sources: PO_ASL_ATTRIBUTES (exposed in APPS as a synonym) and HR_EMPLOYEES_CURRENT_V. The join condition is PAA.SCHEDULER_ID = HRE.EMPLOYEE_ID, meaning scheduler identity on the purchasing side is keyed to the HR employee identifier. Because the HR side is the "current" employees view, the join reflects present employee records rather than historical or terminated assignments.

Documented base objects include the HR_EMPLOYEES_CURRENT_V view together with supporting HR packages and utilities: FND_PROFILE, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY. The presence of HR_SECURITY and HR_GENERAL is significant. These packages enforce Oracle HRMS security, so the rows returned by the view are subject to the Business Group and security profile of the querying user. Consequently, two sessions may legitimately return different result sets. Developers should not assume that CHV_SCHEDULERS_ALL_V behaves like an unrestricted table.

Key Columns

• SCHEDULER_ID — The purchasing-side scheduler identifier. It corresponds to the EMPLOYEE_ID on PO_ASL_ATTRIBUTES and is the column most commonly searched by users.
• FULL_NAME — The formatted full name of the scheduler, resolved through HR_PERSON_NAME from the person record.
• EMPLOYEE_NUM — The employee number assigned in HR, useful for reconciling against payroll or directory listings.
• LOCATION_ID — The location identifier associated with the employee record, allowing schedulers to be grouped by site or geography.

Because the view text applies DISTINCT across all four columns, a scheduler who is referenced on multiple ASL attribute rows appears only once unless location or name values differ.

Common Use Cases and Queries

Typical usage includes validating a scheduler value before assigning it, building LOV queries, and driving reports that list schedulers alongside their assigned suppliers. A straightforward lookup by identifier can be issued as follows:

• SELECT scheduler_id, full_name, employee_num, location_id FROM chv_schedulers_all_v WHERE scheduler_id = :p_scheduler_id;
• SELECT full_name, employee_num FROM chv_schedulers_all_v ORDER BY full_name;

The second query serves as a scheduler search-list. When joining to ASL data, note that PO_ASL_ATTRIBUTES is the driving source and the view already restricts to matching employees, so joining back to the attribute synonym is unnecessary. Users filtering on "scheduler_id" should also remember that the column is an employee identifier, not a supplier or ASL identifier, and that results are constrained by HR security. For cross-module integration, prefer this view over ad hoc joins to HR_EMPLOYEES_CURRENT_V so that security enforcement and name formatting remain consistent with standard EBS behaviour.