Results for “pay_jp_emp_v”

26 results




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

Overview

PAY_JP_EMP_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite. It is registered under the PAY (Payroll) product family and is documented as a localization-specific object used exclusively by the Japanese Tax Entry form. The view is not a general-purpose HR or payroll entity; its sole documented purpose is to supply the Japanese localization's tax entry process with a flattened, session-filtered result set of employee assignment and person data. It is valid in both 12.1.1 and 12.2.2, and the ETRM metadata classifies it as a VIEW with the description "This view is used for Japanese Tax Entry form. This view is used for Japanese localization only."

Because the view joins person, assignment, and person-type data and applies a date-effective filter driven by the current FND session, it behaves more like a controlled data access layer than a simple denormalized table. Any consumer querying the view automatically inherits the effective-date context of the active session.

Underlying Base Objects

The documented view text selects from three core objects plus the FND session data, with the person type supplied by a fourth reference:

The ETRM metadata additionally lists HR_GENERAL and HR_SECURITY packages as referenced base objects. HR_SECURITY is the standard row-level security package applied to PER_ALL_PEOPLE_F access, meaning the view's results are filtered by the querying user's security profile. HR_GENERAL supplies general HR utility logic.

Key Columns

  • ROW_ID — the ROWID of the underlying PER_ASSIGNMENTS_F2 row, used as a unique identifier by the form.
  • ASSIGNMENT_ID / ASSIGNMENT_NUMBER / PAYROLL_ID — assignment identifiers and the associated payroll.
  • PERSON_ID / EMPLOYEE_NUMBER / APPLICANT_NUMBER — person-level keys and unique national identifiers.
  • FULL_NAME, GLOBAL_NAME, LOCAL_NAME — the person's display name, the global (Romanized) name, and the localized (Japanese script) name. The LOCAL_NAME column is the field matched by the user's search and is central to Japanese tax reporting, where the local-script name is required.
  • SYSTEM_PERSON_TYPE — the system person type (e.g., Employee, Applicant).
  • CURRENT_APPLICANT_FLAG, CURRENT_EMPLOYEE_FLAG, CURRENT_EMP_OR_APL_FLAG — status flags indicating the person's present classification.
  • DATE_OF_BIRTH and AGE — the date of birth and the derived age, computed as TRUNC(MONTHS_BETWEEN(FND.EFFECTIVE_DATE, PP.DATE_OF_BIRTH)/12). Age is calculated as of the session effective date.
  • BUSINESS_GROUP_ID, PRIMARY_FLAG, ASSIGNMENT_TYPE — the business group, primary-assignment indicator, and assignment type.

Common Use Cases and Queries

The primary use case is the Japanese Tax Entry form, which reads assignment and person data for the currently logged-in session's effective date. The view is generally not intended for ad hoc reporting, but it can be queried in a session context to retrieve local and global names, age, and payroll assignment details.

To list employees with their Japanese local name for a given assignment:

SELECT person_id,
       employee_number,
       local_name,
       global_name,
       age,
       assignment_number,
       payroll_id
FROM   apps.pay_jp_emp_v
WHERE  assignment_type = 'E'
ORDER  BY employee_number;

To locate a person by local name:

SELECT person_id, employee_number, local_name, global_name, age
FROM   apps.pay_jp_emp_v
WHERE  local_name LIKE '%TANAKA%';

Because the view derives its effective date from FND_SESSIONS and applies HR_SECURITY, results depend on the active session and the querying user's security profile. Any query executed outside a valid EBS session context may return no rows or incomplete data. This makes the view unsuitable for direct external reporting without session emulation, and it should be accessed through the supported Japanese localization flow rather than treated as a general HR data source.