Results for “pay_hk_asg_scheme_name_v”
24 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The PAY_HK_ASG_SCHEME_NAME_V view is a payroll-legislation view owned by the APPS schema within the Oracle E-Business Suite Payroll (PAY) product. It is a read-only database view with a status of VALID in Oracle EBS 12.1.1 and 12.2.2. Its purpose is to expose the Mandatory Provident Fund (MPF) scheme associated with a payroll run for Hong Kong (HK) legislation. Specifically, the view resolves the scheme identifier recorded as a run result value during payroll processing into a human-readable scheme name, using the organization information held under the HK_MPF_SCHEMES context.
In operational terms, the view bridges processed payroll run results with the descriptive scheme definitions configured for a Hong Kong legal employer. It is not a transactional table; it is a convenience projection intended for reporting, data extraction, and integration, allowing developers and analysts to retrieve the scheme name without manually joining run results, input values, run result values, and organization information.
Underlying Base Objects
The view is defined over four base objects, each referenced through an APPS synonym:
- PAY_RUN_RESULTS — the payroll run result header, providing
RUN_RESULT_ID. - PAY_RUN_RESULT_VALUES — the individual result values captured per run result and input value, supplying
RESULT_VALUE(aliased as the scheme ID). - PAY_INPUT_VALUES_F — the input value definition, providing the input value identifier and used to filter to Hong Kong legislation and the input name
SOURCE. - HR_ORGANIZATION_INFORMATION — the descriptive organization flexfield information, supplying the scheme name from
ORG_INFORMATION2where the context isHK_MPF_SCHEMES.
The join path connects run results to their values via RUN_RESULT_ID, links those values to input value definitions via INPUT_VALUE_ID, and then maps the stored scheme identifier (RESULT_VALUE) to the organization information attribute ORG_INFORMATION20, filtered to the HK_MPF_SCHEMES context. The view therefore depends on correctly configured organization information and input values for Hong Kong payroll.
Key Columns
- RUN_RESULT_ID — the identifier of the payroll run result record; the primary linkage back to the payroll run.
- INPUT_VALUE_ID — the identifier of the input value definition used to capture the scheme selection.
- SCHEME_ID — the result value that stores the MPF scheme identifier selected for the assignment or run.
- SCHEME_NAME — the descriptive name of the scheme, derived from
HR_ORGANIZATION_INFORMATION.ORG_INFORMATION2.
These four columns provide a compact representation of the run result, the selection input, and the resolved scheme name.
Common Use Cases and Queries
Typical uses include payroll audits, MPF reporting for Hong Kong statutory submissions, and reconciliation of scheme selections across payroll runs. A representative query retrieves scheme names for a set of run results:
SELECT run_result_id, input_value_id, scheme_id, scheme_name FROM apps.pay_hk_asg_scheme_name_v WHERE run_result_id = :p_run_result_id;- Joining the view to
PAY_RUN_RESULTSor assignment-level tables to report scheme usage by payroll period, legal employer, or employee. - Feeding MPF scheme data into downstream extracts and interfaces for regulatory reporting.
Because the view filters on LEGISLATION_CODE = 'HK' and NAME = 'SOURCE', results are limited to Hong Kong payroll runs where the scheme selection is captured through the SOURCE input value. Analysts should verify that scheme identifiers are populated in ORG_INFORMATION20 under the HK_MPF_SCHEMES context, as missing configuration will cause the scheme name to resolve as null.
-
APPS.PAY_HK_ASG_SCHEME_NAME_V·↳ HR_ORGANIZATION_INFORMATION·↳ PAY_INPUT_VALUES_F·↳ PAY_RUN_RESULTS·Explore PAY module →
-
APPS.PAY_HK_ASG_SCHEME_NAME_V·↳ HR_ORGANIZATION_INFORMATION·↳ PAY_INPUT_VALUES_F·↳ PAY_RUN_RESULTS·Explore PAY module →
-
12.2.2 DBA Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
eTRM - PAY Tables and Views 12.1.1
Temporary table used to hold invalid location addresses.
-
12.1.1 DBA Data 12.1.1
-
eTRM - PAY Tables and Views 12.2.2
Temporary table used to hold invalid location addresses.
-
eTRM - PAY Tables and Views 12.1.1
Temporary table used to hold invalid location addresses.
-
eTRM - PAY Tables and Views 12.2.2
Temporary table used to hold invalid location addresses.