Search Results report_district_name

Overview

APPS.PAY_JP_SWOT_NUMBERS_V is a supplementary database view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the APPS schema and registered under the FND Design Data identifier PAY.PAY_JP_SWOT_NUMBERS_V. Its documented status is VALID. The object is classified as a supplementary view whose stated purpose is to simplify forms coding within the Japanese localization of Oracle Payroll. Oracle explicitly warns that this view is not recommended for direct querying or data alteration, as its definition may change dramatically across subsequent minor or major releases.

The view presents payroll reporting configuration data specific to Japanese statutory reporting, exposing district-level reporting attributes alongside file-handling flags used for electronic filing (e-filing) of Japan payroll submissions. Because the user query term was "report_district_name," the view's REPORT_DISTRICT_NAME column is the focal attribute, representing the descriptive name of the reporting district associated with a given SWOT number configuration.

Underlying Base Objects

Documented dependency information confirms that PAY_JP_SWOT_NUMBERS_V references the following base objects:

• APPS.PAY_JP_SWOT_NUMBERS (exposed as a SYNONYM)
• PER_JP_ADDRESS_LOOKUPS (exposed as a SYNONYM)

The primary table is PAY_JP_SWOT_NUMBERS, which stores the SWOT number configuration records, including organization, district, reporting district, and file-handling flags. PER_JP_ADDRESS_LOOKUPS supplies the Japanese address lookup values used to resolve district codes into descriptive names such as DISTRICT_NAME and REPORT_DISTRICT_NAME. The view joins these sources to present a denormalized result set that simplifies form field population. No database object in the EBS schema is documented as referencing this view, confirming that it functions purely as a presentation-layer lookup aid rather than a dependency for other objects.

Key Columns

The view exposes sixteen columns. The following are the most operationally significant:

• ROW_ID (VARCHAR2, 18): The unique row identifier used by Oracle Forms for row-level operations.
• ORGANIZATION_ID (NUMBER, 15): The business group or organization context for the configuration record.
• DISTRICT_CODE / DISTRICT_NAME: The code and 240-character descriptive name of the district.
• REPORT_DISTRICT_CODE / REPORT_DISTRICT_NAME (VARCHAR2, 240): The code and descriptive name of the reporting district — the attribute most relevant to the user's search term.
• SWOT_NUMBER (VARCHAR2, 15): The SWOT number associated with the configuration.
• EFILE_EXCLUSIVE_FLAG / IMPORT_EXCLUSIVE_FLAG (VARCHAR2, 30): Flags governing exclusive handling of e-filing output and import processing.
• OUTPUT_FILE_NAME / INPUT_FILE_NAME (VARCHAR2, 80): File names used for export and import of electronic filing data.
• Standard Who columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE provide audit trail information.

Common Use Cases and Queries

This view is typically queried during diagnosis of Japanese payroll e-filing configuration, particularly when validating that district and reporting district names resolve correctly against the address lookup table. A representative query targeting the search term follows:

• SELECT organization_id, district_code, district_name, report_district_code, report_district_name, swot_number FROM apps.pay_jp_swot_numbers_v WHERE report_district_name IS NOT NULL;

Additional scenarios include retrieving e-filing file configuration for a specific organization:

• SELECT swot_number, output_file_name, input_file_name, efile_exclusive_flag FROM apps.pay_jp_swot_numbers_v WHERE organization_id = :org_id;

Because Oracle documents this as a forms-support view, direct queries should be treated as diagnostic only. Any integration or reporting requirement should preferably target the underlying PAY_JP_SWOT_NUMBERS table directly to avoid exposure to definition changes in future EBS releases.