Search Results scheme_id




Overview
Explore in AI Chat

Overview

APPS.PAY_HK_ASG_SCHEME_NAME_V is a database view owned by the APPS schema in Oracle E-Business Suite, registered under the FND Design Data identifier PAY.PAY_HK_ASG_SCHEME_NAME_V. The view has a status of VALID and falls under the Oracle Internal Use Only designation, meaning Oracle Corporation does not support direct access to application data through this object except from standard Oracle Applications programs. The object is documented as an internal view type.

The nomenclature of the view (PAY_HK...) indicates it is associated with the Hong Kong localization of the Oracle Payroll product family. Its role is to resolve the scheme identifier and scheme name associated with payroll run results, specifically for assignment-level payroll data. This makes it useful in payroll reconciliation, statutory reporting, and integration scenarios where the "scheme_id" value produced during a payroll run must be translated into a recognizable scheme name. The view surfaces the linkage between a payroll run result, the input value that carried the scheme reference, and the resolved scheme identifier and description.

The view is also exposed publicly via the synonym PUBLIC.PAY_HK_ASG_SCHEME_NAME_V, which allows standard application code and localized processes to reference it without qualifying the APPS schema explicitly.

Underlying Base Objects

The ETRM metadata documents APPS.PAY_HK_ASG_SCHEME_NAME_V as referencing four base objects, all resolved through synonyms in the APPS schema:

  • PAY_RUN_RESULTS — the core payroll run result table, holding one row per assignment per payroll run for each defined run result.
  • PAY_RUN_RESULT_VALUES — stores the individual values attributed to a run result, linking results to their input values.
  • PAY_INPUT_VALUES_F — the input value definition table, providing the identity and meaning of each payroll input value.
  • HR_ORGANIZATION_INFORMATION — the organization (business group) information table, typically used to resolve organization-level descriptive flexfield or attribute data, including scheme naming for the Hong Kong localization.

The view therefore operates as a payroll-run-centric construct, joining run result data to its constituent input values and enriching the result with organization-linked scheme information. Because these dependencies are satisfied through APPS synonyms, the view remains insulated from the physical owner of the underlying tables.

Key Columns

The view exposes four documented columns:

  • RUN_RESULT_ID (NUMBER, length 15) — identifies the parent payroll run result row in PAY_RUN_RESULTS. This is the primary grouping key for the assignment-level payroll outcome.
  • INPUT_VALUE_ID (NUMBER) — identifies the specific input value in PAY_INPUT_VALUES_F that contributed to the run result, linking the result to the element input that carried the scheme reference.
  • SCHEME_ID (VARCHAR2, length 60) — the scheme identifier stored as a character value rather than a numeric key. This is the column users most frequently search for, and it represents the localization-specific code used to distinguish one scheme from another.
  • SCHEME_NAME (VARCHAR2, length 150) — the descriptive name of the scheme, resolving the opaque scheme identifier into a human-readable label for reporting.

Common Use Cases and Queries

The most frequent use case is retrieving the scheme name for a known scheme identifier during payroll analysis, or listing all schemes active for a run. A representative query joins the view back to PAY_RUN_RESULTS for assignment context:

  • Scheme resolution: SELECT run_result_id, input_value_id, scheme_id, scheme_name FROM apps.pay_hk_asg_scheme_name_v WHERE scheme_id = :p_scheme_id;
  • Run reconciliation: SELECT v.scheme_id, v.scheme_name, r.assignment_id FROM apps.pay_hk_asg_scheme_name_v v, apps.pay_run_results r WHERE v.run_result_id = r.run_result_id AND r.payroll_run_id = :p_run_id;
  • Reference listing: SELECT DISTINCT scheme_id, scheme_name FROM apps.pay_hk_asg_scheme_name_v ORDER BY scheme_name;

Because the object is flagged Oracle Internal Use Only, production integrations should rely on supported Oracle Payroll interfaces rather than querying the view directly; extracts remain appropriate for diagnostic and reporting purposes only.