Results for “wp_number”

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

Overview

PAY_JP_SI_DISQUALIFIED_V is an APPS-owned database view in the Oracle E-Business Suite Payroll (PAY) product, validated and shipped as part of the Japanese localizations. Its purpose is to supply the data set required by the Japanese statutory report KENPO KONEN HIHOKENSHA SHIKAKU SOUSHITU TODOKE — the notification of loss of qualification for employees' and dependents' welfare pension and health insurance coverage. The view identifies assignments that have been disqualified from a given insurance scheme (health insurance, welfare pension, or welfare pension fund) and reports the effective date of disqualification, the associated organization or office reference, the employee's insurance number, and a reporting output flag.

Because it is a view rather than a concurrent program or table, it does not store data. It derives its rows at query time from payroll element entries and assignment records, resolving the relevant input value identifiers dynamically through HR_JP_ID_PKG for each business group. This makes the view business-group sensitive and therefore usable across multiple Japanese legal entities within a single EBS instance. It is typically consumed by the statutory reporting program or custom extracts that generate the notification form, and by support personnel investigating why a particular assignment does or does not appear on the report.

Underlying Base Objects

The documented base objects referenced by PAY_JP_SI_DISQUALIFIED_V are:

• PAY_ELEMENT_ENTRIES_F — the assignment-level element entry records that anchor each reported row; the view reads PEE.ASSIGNMENT_ID in preference to PA.ASSIGNMENT_ID for performance.
• PAY_ELEMENT_ENTRY_VALUES_F — the individual input values (dates, numbers, flags) held against each element entry.
• PER_ALL_ASSIGNMENTS_F — the assignment and person context, supplying ASSIGNMENT_ID, PERSON_ID, and PERIOD_OF_SERVICE_ID.
• PER_BUSINESS_GROUPS_PERF — used to drive the inline business group driver subquery.
• FND_DATE (package) — converts canonical screen entry values into real dates via CANONICAL_TO_DATE.
• HR_JP_ID_PKG (package) — resolves input value identifiers by business group, using the logical names COM_HI_QUALIFY_INFO, COM_WP_QUALIFY_INFO, COM_WPF_QUALIFY_INFO, and COM_SI_REPORT_INFO.
• PAY_JP_BALANCE_PKG (package) — retrieves numeric and character entry values for the assignment and effective date being reported.

The view text carries explicit ORDERED, NO_MERGE, and INDEX hints, indicating it was tuned for the element entry value access path.

Key Columns

• ASSIGNMENT_ID — the assignment being disqualified.
• PERSON_ID — the person who holds the assignment.
• BUSINESS_GROUP_ID — the legal entity context, used to resolve all input value identifiers.
• PERIOD_OF_SERVICE_ID — the payroll period of service associated with the entry.
• Disqualification date columns — the canonical screen entry value converted by FND_DATE and reduced by one day, giving the effective date of coverage loss for each scheme.
• Organization number columns — the character entry value for the health insurance and welfare pension office numbers, truncated to ten bytes via SUBSTRB.
• Scheme flag — a summed DECODE value (1 for health insurance, 2 for welfare pension, 4 for welfare pension fund) identifying which scheme the row pertains to.
• Output flag — a single-character value retrieved for COM_SI_REPORT_INFO 'OUTPUT_FLAG', controlling whether the row is emitted on the statutory notification.

Common Use Cases and Queries

Typical usage is the generation of the disqualification notification and the reconciliation of that report against payroll entries. A simple diagnostic query returning disqualified assignments for a business group is:

• SELECT assignment_id, person_id, business_group_id, period_of_service_id FROM apps.pay_jp_si_disqualified_v WHERE business_group_id = :p_business_group_id;
• Filtering to assignments with a particular output flag before producing the statutory form.
• Joining the view to PER_ALL_PEOPLE_F on person_id to print employee names and numbers on the notification.
• Comparing the view's disqualification dates with the underlying element entry values to verify that a disqualification was keyed for the correct scheme and effective date.

Because the view resolves input value identifiers at runtime, query performance depends on the element entry value index and on the hint-driven plan; it should not be treated as a historical snapshot, since results reflect current assignment and entry data.