Results for “pay_jp_swot_numbers_pk”

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

Overview

HR.PAY_JP_SWOT_NUMBERS is a Japan-specific payroll table in Oracle E-Business Suite (documented here for 12.1.1 and 12.2.2) that stores the Special Withholding Obligation Taxpayer (SWOT) numbers assigned to legal entities and reporting districts. The table is owned by the HR schema and is registered under FND Design Data as PAY.PAY_JP_SWOT_NUMBERS, with a status of VALID. It is a transactional data object, stored in the APPS_TS_TX_DATA tablespace with PCT FREE of 5, and it is surfaced to the applications layer through the APPS synonym PAY_JP_SWOT_NUMBERS and the WHO variant PAY_JP_SWOT_NUMBERS_WHO.

The record set supports Japanese statutory withholding reporting, where each organization that operates in a given tax district must be associated with a valid taxpayer number for electronic filing. The table is geographically constrained to Japan and should not be expected to hold data for other localization regimes. Heuristically, the mined relationship profile classifies this object as standalone, meaning it references no other database object directly. For modeling purposes, it is therefore best treated as a reference or lookup-style entity rather than a Data Vault hub, link, or satellite with outbound relationships. The ETRM documentation explicitly notes that HR.PAY_JP_SWOT_NUMBERS does not reference any database object, so any downstream relationship is conceptual (driven by foreign-key semantics described in column comments) rather than enforced through database constraints.

Key Information Stored

The table is documented with 13 columns. The most operationally significant are the following.

• ORGANIZATION_ID (NUMBER, 15) — the legal entity or organization unit, described in the metadata as a foreign key to HR_ALL_ORGANIZATION_UNITS.
• DISTRICT_CODE (VARCHAR2) — the tax district, described as a foreign key to PER_JP_ADDRESS_LOOKUPS.
• SWOT_NUMBER (VARCHAR2, 15) — the unique identifier of the special withholding obligation taxpayer.
• REPORT_DISTRICT_CODE (VARCHAR2) — the reporting district code used for filing output.
• EFILE_EXCLUSIVE_FLAG — flag controlling e-filing exclusivity for the record.
• OUTPUT_FILE_NAME — name of the e-filing output file generated for the SWOT record.
• IMPORT_EXCLUSIVE_FLAG — flag controlling import exclusivity.
• INPUT_FILE_NAME — name of the input file associated with the import process.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — the standard Who columns used for auditing and concurrency tracking.

The surrogate primary key is PAY_JP_SWOT_NUMBERS_PK, a unique, normal index on (ORGANIZATION_ID, DISTRICT_CODE) stored in APPS_TS_TX_IDX. Because this composite is both the primary key and the only documented unique index, ORGANIZATION_ID plus DISTRICT_CODE is the only business-key candidate in the metadata; SWOT_NUMBER, despite being labeled a unique identifier in its comment, is not enforced by a unique index. Auditing columns such as LAST_UPDATED_BY and CREATED_BY carry foreign-key semantics to FND_USER.USER_ID, and LAST_UPDATE_LOGIN maps to FND_LOGINS.LOGIN_ID.

Common Use Cases and Queries

The primary use case is retrieving the SWOT number for a specific organization and district during Japanese withholding tax reporting and e-filing. A basic lookup uses the full primary key for maximum selectivity:

• SELECT SWOT_NUMBER, REPORT_DISTRICT_CODE FROM HR.PAY_JP_SWOT_NUMBERS WHERE ORGANIZATION_ID = :p_org_id AND DISTRICT_CODE = :p_district_code;
• Enumerating all SWOT numbers registered for an entity: SELECT DISTRICT_CODE, SWOT_NUMBER FROM HR.PAY_JP_SWOT_NUMBERS WHERE ORGANIZATION_ID = :p_org_id ORDER BY DISTRICT_CODE;
• Audit reporting on recently maintained records: SELECT ORGANIZATION_ID, DISTRICT_CODE, SWOT_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY FROM HR.PAY_JP_SWOT_NUMBERS WHERE LAST_UPDATE_DATE >= :p_since;
• Identifying districts that have no taxpayer number: SELECT ORGANIZATION_ID, DISTRICT_CODE FROM HR.PAY_JP_SWOT_NUMBERS WHERE SWOT_NUMBER IS NULL;

Typical consumers are the Japanese payroll statutory reporting and e-filing programs, which read SWOT_NUMBER along with REPORT_DISTRICT_CODE to populate filing headers, and data-migration or reconciliation scripts that compare registered numbers against legal-entity records. Because the table contains Who columns, it is also suitable for lineage and change-tracking extracts in reporting layers.

Related Objects

The following objects are the most significant in relation to HR.PAY_JP_SWOT_NUMBERS, based on the documented dependency and column-comment data.

• HR_ALL_ORGANIZATION_UNITS — the implied parent of ORGANIZATION_ID; join on ORGANIZATION_ID = HR_ALL_ORGANIZATION_UNITS.ORGANIZATION_ID.
• PER_JP_ADDRESS_LOOKUPS — the implied lookup source for DISTRICT_CODE; join on DISTRICT_CODE = PER_JP_ADDRESS_LOOKUPS.DISTRICT_CODE.
• APPS.PAY_JP_SWOT_NUMBERS — the APPS-layer synonym through which transactional code accesses the table.
• APPS.PAY_JP_SWOT_NUMBERS_WHO — the WHO-enabled variant used for audit-context access.
• PUBLIC.PAY_JP_SWOT_NUMBERS — the public synonym exposing the object across schemas.
• FND_USER — the implied parent of LAST_UPDATED_BY and CREATED_BY; join on USER_ID.
• FND_LOGINS — the implied parent of LAST_UPDATE_LOGIN; join on LOGIN_ID.

No other database object is referenced by this table, and no child object references it in the documented relationship model, consistent with its standalone classification.