Search Results per_people_f_pk

Overview

PAY_HK_MPF_REMITTANCE_V is an Oracle EBS Hong Kong localisation view owned by the APPS schema and delivered as part of the PAY (Payroll) product. Its purpose is to consolidate the Mandatory Provident Fund (MPF) remittance information that a Hong Kong payroll run produces, flattening the payroll action, assignment action, run result, and person/assignment context into a single queryable row per assessed contribution line. MPF is the statutory pension scheme for Hong Kong, and the payroll solution captures employer and employee contributions as element input values and run result values; this view pivots those values into named columns so that remittance reports, extracts, and downstream integrations can consume them without hard-coding PAY_RUN_RESULT_VALUES lookups.

Because it joins across the core payroll action and run result model, the view is primarily used for post-run reporting and for feeding remittance files to trustees. It is not a transactional entity; it exposes no DML and reflects whatever the latest completed payroll run has written.

Underlying Base Objects

ETRM metadata for 12.2.2 records the following referenced base objects: PAY_PAYROLL_ACTIONS, PAY_ASSIGNMENT_ACTIONS, PAY_RUN_RESULTS, PAY_RUN_RESULT_VALUES, PAY_INPUT_VALUES_F, PAY_ELEMENT_TYPES_F, PER_PEOPLE_F, PER_ASSIGNMENTS_F, and PER_PERIODS_OF_SERVICE, together with the packages and utilities FND_DATE, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY. PER_ASSIGNMENTS_F and PER_PEOPLE_F are resolved as views over the HR base tables, while the payroll objects are synonyms to their PAY counterparts.

The view joins PER_PEOPLE_F (PPF) to PER_ASSIGNMENTS_F (PAF) on the person/assignment relationship, constrained by effective dating. PAF is linked to PAY_ASSIGNMENT_ACTIONS (PAA) and PAY_PAYROLL_ACTIONS (PPA) so that only actions whose payroll effective date falls inside the assignment and person effective ranges are returned. PAA is joined to PAY_RUN_RESULTS (PRR), which in turn links to PAY_RUN_RESULT_VALUES (PRRV) and, through the element type, to PAY_ELEMENT_TYPES_F (PETF). PAY_INPUT_VALUES_F (PIVF) supplies the input value names used to pivot run result values into labelled output columns. PER_PERIODS_OF_SERVICE (PPS) contributes the period of service start and termination dates. A prominent feature of the implementation is the USE_NL hint and a set of INDEX hints, including INDEX(PPF PER_PEOPLE_F_PK) — the index reference the user searched for — which drives nested-loop access through the person primary key to keep the query plan efficient.

Key Columns

PERSON_ID / ASSIGNMENT_ID — keys to the person and assignment being assessed.
PAYROLL_ACTION_ID / ASSIGNMENT_ACTION_ID / TAX_UNIT_ID — identify the payroll run, the per-assignment action, and the tax unit context.
EFFECTIVE_DATE — the payroll action effective date used for effective-dated joins.
ELEMENT_TYPE_ID / ELEMENT_NAME — the MPF element being processed.
RUN_RESULT_ID — the underlying run result row.
FULL_NAME — last name concatenated with first name via DECODE.
PERIOD_OF_SERVICE_ID / DATE_START / ACTUAL_TERMINATION_DATE — service period context.
VALUE — numeric contribution amount from the input value named 'PAY VALUE'.
SCHEME_ID — numeric scheme identifier from the 'SOURCE' input value.
MEMBERSHIP_NUMBER — trustee membership identifier.
PERIOD_START_DATE / PERIOD_END_DATE — contribution period boundaries converted by FND_DATE.CANONICAL_TO_DATE.
ASSESSED_RI — the assessed relevant income, numeric.

Common Use Cases and Queries

Typical scenarios include producing the monthly MPF remittance schedule, reconciling assessed relevant income against contributions, and extracting membership numbers for trustee files. A representative query:

SELECT person_id, full_name, membership_number, scheme_id, value, assessed_ri, period_start_date, period_end_date FROM apps.pay_hk_mpf_remittance_v WHERE payroll_action_id = :p_action_id ORDER BY full_name;

For period reporting, filter on period_start_date and period_end_date, or join the view to PAY_PAYROLL_ACTIONS to restrict to a single payroll run. Because the view is APPS-owned and contains no security predicates beyond those inherited from the resolved objects, HR_SECURITY-based access rules should be applied by the calling report or a secured wrapper view.

View: PAY_HK_MPF_REMITTANCE_V 12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:PAY.PAY_HK_MPF_REMITTANCE_V, object_name:PAY_HK_MPF_REMITTANCE_V, status:VALID, product: PAY - Payroll , description: Hong Kong localisation view. , implementation_dba_data: APPS.PAY_HK_MPF_REMITTANCE_V ,
View: PAY_HK_MPF_REMITTANCE_V 12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:PAY.PAY_HK_MPF_REMITTANCE_V, object_name:PAY_HK_MPF_REMITTANCE_V, status:VALID, product: PAY - Payroll , description: Hong Kong localisation view. , implementation_dba_data: APPS.PAY_HK_MPF_REMITTANCE_V ,
View: PAY_JP_PRE_TAX_V 12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:PAY.PAY_JP_PRE_TAX_V, object_name:PAY_JP_PRE_TAX_V, status:VALID, product: PAY - Payroll , description: This view is used by PAYJPPTX form and Japanese legislative reports. , implementation_dba_data: APPS.PAY_JP_PRE_TAX_V ,
View: PAY_JP_UI_V 12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:PAY.PAY_JP_UI_V, object_name:PAY_JP_UI_V, status:VALID, product: PAY - Payroll , description: This view is used by Japanese statutory report of Unemployment Insurance Check List(PAYJPRUI) , implementation_dba_data: APPS.PAY_JP_UI_V ,
View: PAY_JP_UI_V 12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:PAY.PAY_JP_UI_V, object_name:PAY_JP_UI_V, status:VALID, product: PAY - Payroll , description: This view is used by Japanese statutory report of Unemployment Insurance Check List(PAYJPRUI) , implementation_dba_data: APPS.PAY_JP_UI_V ,