Results for “jp_r”

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

Overview

The view PAY_JP_TAX_SWOT_WITHHELD_V is an Oracle Payroll localization object that is delivered exclusively for the Japanese localization of Oracle E-Business Suite. It is documented in ETRM as belonging to the PAY — Payroll product and carries the description "This view is used for Japanese localization only." The view provides a reporting-oriented projection of Japanese withholding tax (Shotokuzei, commonly abbreviated SWOT) data, joining payroll tax accumulation records to person address information so that tax reporting includes a jurisdiction-appropriate town or city value.

In the context of Oracle EBS 12.1.1 and 12.2.2, the view serves as a read-only integration and reporting surface. It is not a transactional entity; no data is stored against it. Rather, it exposes derived tax-withholding rows suitable for extract programs, statutory Japanese tax filings, and downstream data warehouse loads. Because the object is localized, it is absent from non-Japanese installations and would not appear in a standard ETRM listing for a database that has not installed the Japanese localization patch set. The ETRM excerpt explicitly notes "Not implemented in this database," confirming that availability is conditional on localization installation.

Underlying Base Objects

The view text reveals a three-way outer join across two instances of the PER_ADDRESSES table and the Japanese tax view PAY_JP_TAX_SWOT_V. The documented referenced base objects list is empty in ETRM, but the view definition is authoritative:

• PAY_JP_TAX_SWOT_V (PPI) — the driving source of payroll tax withholding rows, supplying business group, tax year, tax organization, effective and earned dates, assignment action, person, period of service, and tax category values.
• PER_ADDRESSES (PADR) — aliased as the residential address, joined with ADDRESS_TYPE = 'JP_R'.
• PER_ADDRESSES (PADC) — aliased as the current address, joined with ADDRESS_TYPE = 'JP_C'.

Both address joins are outer joins (denoted by the (+) operator), keyed on PERSON_ID and bounded by an effective-date range test. The date predicate resolves to the earlier of the person's actual termination date or 1 January of the year following the tax effective date, then confirms that date falls between DATE_FROM and NVL(DATE_TO, 31-DEC-4712). This ensures the address in force for the relevant tax period is selected.

Key Columns

• BUSINESS_GROUP_ID — the HR business group owning the payroll tax record.
• YEAR — the Japanese tax year to which the withholding record applies.
• TAX_ORGANIZATION_ID — the tax reporting organization, typically the municipality or tax office.
• EFFECTIVE_DATE and DATE_EARNED — the effective and earned dates of the tax record.
• ASSIGNMENT_ACTION_ID — links the row to the payroll assignment action that generated it.
• PERSON_ID — the employee or payee.
• PERIOD_OF_SERVICE_ID — the period of service identifier associated with the tax entry.
• TAX_CATEGORY and TAX_YEA_CATEGORY — Japanese tax classification codes.
• TOWN_OR_CITY — derived via DECODE: the residential address town/city is used when a residential row exists; otherwise the current address town/city is returned.

Common Use Cases and Queries

Typical use is extraction of Japanese withholding tax data for statutory reporting, reconciliation of tax by municipality, and feeds into external payroll tax filing systems. A representative query filtering by tax year and person is:

• SELECT person_id, year, tax_organization_id, tax_category, town_or_city FROM pay_jp_tax_swot_withheld_v WHERE year = :p_year AND business_group_id = :p_bg_id;
• SELECT tax_organization_id, COUNT(*), SUM(...) FROM pay_jp_tax_swot_withheld_v GROUP BY tax_organization_id; for municipality-level aggregation.

Analysts searching for "per_addresses" in this context should understand that the address data is consumed internally by the view; joining PER_ADDRESSES again externally may duplicate rows and is generally unnecessary. All access should be treated as read-only and constrained by business group and tax year to preserve performance.