Results for “service_tax_reporting_year”

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

Overview

PAY_HK_IR56_EMPLOYEE_V is a Hong Kong localisation view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is part of the PAY (Payroll) product module and is designed to consolidate the employee and employer attributes required for Hong Kong Inland Revenue Department (IRD) reporting. Specifically, the view supplies the statutory data elements used when producing IR56 forms — such as IR56B, IR56E, IR56F and IR56G — which employers must file with the IRD to report remuneration paid to employees, the commencement or cessation of employment, and departure from Hong Kong.

The view joins person, assignment, organisation, location, address and spouse detail sources into a single denormalised row per employee/assignment combination. Because the view text uses SELECT DISTINCT, it returns one logically unique row for each person and assignment pairing, filtering out duplicates that would otherwise arise from the underlying joins. This makes it suitable as a direct source for concurrent programs, BI Publisher report data models and custom extracts that must present pre-formatted IR56 employee information.

Underlying Base Objects

The documented base objects referenced by the view sit largely in the HR and PAY core schema surfaces. Person-level attributes are drawn from PER_PEOPLE_F (the effective-dated person record) and enhanced by the HR_PERSON_NAME package and PER_ADDRESSES. Assignment data is sourced from PER_ASSIGNMENTS_F and PER_ASSIGNMENT_EXTRA_INFO, with service history from PER_PERIODS_OF_SERVICE. Employer data is sourced from HR_ORGANIZATION_INFORMATION (organisation flexfield segments carrying the employer return file number and designation), HR_ORGANIZATION_UNITS for the employer name, and HR_LOCATIONS for the employer address. Lookup translation is handled by HR_LOOKUPS; territory names come from FND_TERRITORIES_VL.

Security and generation logic are invoked through the HR_SECURITY, HR_GENERAL, HR_API and FND_NUMBER packages. Spouse information is not held directly in the view but is obtained through the companion view PAY_HK_IR56_SPOUSE_DETAILS_V, and soft-coding flexfield values are resolved via HR_SOFT_CODING_KEYFLEX. Many of these objects are exposed to APPS as synonyms (for example PER_ADDRESSES and HR_ORGANIZATION_INFORMATION), reflecting the standard EBS synonym layer over the HR and PER base tables.

Key Columns

The view exposes a broad set of IR56-specific columns:

• PERSON_ID / ASSIGNMENT_ID — the identifying keys linking to the person and assignment.
• EMPLOYER_RETURN_FILE_NO, DESIGNATION, DESIGNATION_NAME, EMPLOYER_RETURN_LAST_8, EMPLOYER_NAME, EMPLOYER_ADDRESS — employer identification data derived from organisation flexfield segments and the employer location.
• TITLE, FULL_NAME, LAST_NAME, MAIDEN_NAME — the employee name set. Notably, MAIDEN_NAME is populated from PAPF.PREVIOUS_LAST_NAME, mapping the person's previous surname to the IR56 maiden name field.
• EMPLOYEE_TAX_FILE_NO, HK_ID_CARD_NO, PASSPORT_NUMBER, SEX, MARITAL_STATUS — statutory identity attributes; marital status is decoded to 2 for 'M' (married) and 1 otherwise.
• SPOUSE_NAME, SPOUSE_HK_ID_CARD_NO, SPOUSE_PASSPORT_NUMBER — spouse details sourced from the spouse details view.
• Residential address fields — assembled from PER_ADDRESSES using nested DECODE logic against ADDRESS_LINE1/2/3, TOWN_OR_CITY and COUNTRY, with lookup meaning applied.

Common Use Cases and Queries

The primary use case is IR56 form generation. A typical query retrieves the employer, employee and spouse fields for a given person or assignment:

• Extracting a single employee's IR56B data by PERSON_ID or ASSIGNMENT_ID.
• Producing bulk IR56E/F/G extracts for a payroll period or termination date range.
• Feeding BI Publisher or Oracle Reports templates that render the statutory IR56 layout.
• Reconciling maiden name, tax file number and HK ID card values during year-end processing.

A representative query is:

SELECT person_id, assignment_id, full_name, maiden_name,
hk_id_card_no, employee_tax_file_no, employer_return_file_no
FROM apps.pay_hk_ir56_employee_v
WHERE person_id = :p_person_id;

Because the view applies HR_SECURITY and HR_GENERAL logic, query results are subject to the security profile of the connected user, so responsibility and business group context should be considered when using it in custom extracts.