Search Results wpf_org_id

Overview

APPS.PAY_JP_ITWB_EMP_SI_V is a seed data view owned by the APPS schema in Oracle E-Business Suite, documented as internal and marked "Oracle Internal Use Only" in ETRM. The view presents a consolidated projection of Japan localization statutory and social insurance reporting attributes held against payroll assignment actions. In practical terms, it exposes, for a given assignment action, the employee's insurance-related organizational identifiers and numbers alongside residency declarations (the NRES_FLAG, NRES_START_DATE and PROJECTED_RES_DATE columns), timing attributes (EFFECTIVE_DATE, ASSIGNMENT_ACTION_ID, ASSIGNMENT_ID) and standard WHO-style audit columns.

The object is registered in FND Design Data as PAY.PAY_JP_ITWB_EMP_SI_V and has a status of VALID. Its intended consumer is the Oracle payroll reporting layer for Japan rather than ad hoc customer reporting; the documented dependency chain confirms it is read by APPS.PAY_JP_ITWB_REPORT_PKG, an internal reporting package. Because the view is flagged as internal, it should be treated as a read-only, non-supported interface and consumed only where required for diagnostic or reconciliation purposes.

Underlying Base Objects

The view type is Internal and it is defined over a small, well-defined set of dependencies:

• APPS.PAY_ACTION_INFORMATION (referenced via a synonym) — the primary transactional source. This table stores assignment action information keyed by ACTION_INFORMATION_ID and ASSIGNMENT_ACTION_ID, with a context discriminator (ACTION_CONTEXT_TYPE) and category (ACTION_INFORMATION_CATEGORY).
• APPS.FND_DATE — the Oracle Applications date conversion package, used to translate stored date values into the view's DATE columns (EFFECTIVE_DATE, NRES_START_DATE, PROJECTED_RES_DATE).
• APPS.FND_NUMBER — the Oracle Applications number conversion package, used to normalize numeric identifiers and amounts exposed by the view.

No base tables beyond PAY_ACTION_INFORMATION are documented as direct dependencies. The view therefore inherits its cardinality and update behaviour entirely from that payroll action information store, filtered and transformed for the Japan social insurance reporting context. Consumers should note that the view is not a physical table and holds no data of its own.

Key Columns

• ROW_ID / OBJECT_VERSION_NUMBER — Row locator and optimistic locking token inherited from the action information record.
• ACTION_INFORMATION_ID, ASSIGNMENT_ACTION_ID, ASSIGNMENT_ID — Payroll action and assignment keys linking the row to a specific assignment action and employee assignment.
• ACTION_CONTEXT_TYPE, ACTION_INFORMATION_CATEGORY, EFFECTIVE_DATE — The context and effective dating of the underlying action information.
• ITAX_ORG_ID / ITAX_TYPE — Income tax related organization and tax type attributes.
• HI_ORG_ID / HI_NUMBER — Health insurance organization and insured number.
• WP_ORG_ID / WP_NUMBER — Welfare pension organization and pension number.
• WPF_ORG_ID / WPF_NUMBER — Welfare pension fund organization and fund number.
• EI_ORG_ID / EI_NUMBER — Employment insurance organization and insured number.
• NRES_FLAG — VARCHAR2(240) indicator of non-resident status used in the Japanese residency declaration process, typically referencing the residence status information supplied to the Japanese authorities.
• NRES_START_DATE, PROJECTED_RES_DATE — Start date of the non-residency declaration and the projected residency (or projected re-entry) date.
• Audit columns — LAST_UPDATE_LOGIN, LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE.

Common Use Cases and Queries

The view is principally consumed by APPS.PAY_JP_ITWB_REPORT_PKG to assemble Japan insurance and residency declarations. A typical investigative query retrieves the insurance numbers and residency flags for a given assignment action:

• Identify assignments flagged as non-resident, showing HI, WP, EI and tax identifiers together with the residency dates, so that statutory declaration reports can be validated.
• Audit the WHO columns to determine when a particular action information record was last changed and by which user.
• Reconcile the view back to PAY_ACTION_INFORMATION on ACTION_INFORMATION_ID to confirm that the derived dates and numbers are being transformed as expected by FND_DATE and FND_NUMBER.

Sample SQL:

SELECT assignment_id, assignment_action_id, effective_date, itax_type, hi_number, wp_number, ei_number, nres_flag, nres_start_date, projected_res_date FROM apps.pay_jp_itwb_emp_si_v WHERE last_update_date >= :p_from_date ORDER BY assignment_id, effective_date;

Because these tables can hold large volumes of historical action information, filters on ASSIGNMENT_ID, ASSIGNMENT_ACTION_ID or EFFECTIVE_DATE should always be applied. Access outside standard Oracle Applications programs is not supported.