Results for “employer_postal_code”

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

Overview

The PAY_CA_EOY_RL2_TRANS_INFO_V view is an Oracle E-Business Suite (EBS) Payroll (PAY) dictionary object owned by the APPS schema. It exposes the transmitter and employer information associated with Canadian end-of-year (EOY) RL-2 archival records — the Relevé 2 slips used to report employment income, tips, and related amounts to Revenu Québec. The view is a reporting and integration artifact: it flattens the key/value storage pattern of the underlying action information tables into a single denormalized row per archived RL-2 submission, making the data suitable for downstream extraction, magnetically encoded or electronic filing, and audit reporting.

In EBS 12.1.1 and 12.2.2, the view is delivered as VALID in the APPS schema. It is read-only and intended for query access only; the validated RL-2 transmitter and employer attributes are populated by the EOY archival process, which writes completed payroll action records with a report type of RL2 and a report qualifier of CAEOYRL2. The view then joins the transmitter block and the employer block for each such archived action.

Underlying Base Objects

The documented referenced base objects for this view are:

• PAY_ACTION_INFORMATION (SYNONYM) — joined twice, once with the alias TRANS (transmitter data) and once with the alias EMPLR (employer data).
• PAY_PAYROLL_ACTIONS (SYNONYM) — aliased PPA_ARCH, supplying the archival action header.

The join is driven from PPA_ARCH, filtered on REPORT_TYPE = 'RL2', REPORT_QUALIFIER = 'CAEOYRL2', REPORT_CATEGORY = 'ARCHIVE', ACTION_TYPE = 'X', and ACTION_STATUS = 'C'. Both TRANS and EMPLR are linked to PPA_ARCH.PAYROLL_ACTION_ID through ACTION_CONTEXT_ID. The transmitter row is restricted to ACTION_INFORMATION_CATEGORY = 'CAEOY TRANSMITTER INFO' with ACTION_INFORMATION1 = 'RL2'; the employer row is restricted to ACTION_INFORMATION_CATEGORY = 'CAEOY EMPLOYER INFO' with ACTION_INFORMATION1 = 'RL2'. Note that the query joins on PAYROLL_ACTION_ID in the header but projects ACTION_CONTEXT_ID from both child tables; the view exposes the BUSINESS_GROUP_ID from the header.

Key Columns

The view exposes the columns of the two contributing categories under generic ACTION_INFORMATIONn names, with several documented aliases that carry semantic meaning for RL-2 filing. The key columns include:

• BUSINESS_GROUP_ID — the business group that owns the archived RL-2 action, used for security and multi-organization filtering.
• PAYROLL_ACTION_ID — the payroll action identifier that links the transmitter and employer rows to the archived action header.
• TRANSMITTER_NUMBER, TRANSMITTER_NAME, TRANSMITTER_ADDRESS_LINE1, TRANSMITTER_ADDRESS_LINE2, TRANSMITTER_PACKAGE_TYPE, TRANSMITTER_DATA_TYPE, TRANSMITTER_TYPE_INDICATOR, SOURCE_OF_SLIPS — identification and filing attributes of the transmitting party.
• QUEBEC_BUSINESS_NUMBER — the Quebec enterprise number of the employer/transmitter.
• REPORTING_YEAR — the taxation year covered by the RL-2 submission.

The remaining ACTION_INFORMATIONn columns (2 through 27) map to positional slots in PAY_ACTION_INFORMATION, including transmitter and employer address, contact, and postal information. Notably, employer_postal_code is not exposed as a named column; it is stored positionally and must be resolved from the CAEOY EMPLOYER INFO category rows, typically by inspecting the corresponding ACTION_INFORMATIONn slot.

Common Use Cases and Queries

Typical scenarios include validating archived RL-2 transmitter and employer blocks before electronic filing, reconciling Revenu Québec submissions for a reporting year, and extracting employer postal and address data for remittance correspondence.

SELECT business_group_id,
       payroll_action_id,
       reporting_year,
       transmitter_number,
       transmitter_name,
       quebec_business_number
  FROM apps.pay_ca_eoy_rl2_trans_info_v
 WHERE reporting_year = :p_year;

To locate an employer postal code, query the CAEOY EMPLOYER INFO category directly, since the view surfaces employer data positionally:

SELECT action_context_id, action_information_category, action_information1
  FROM apps.pay_action_information
 WHERE action_context_id = :p_payroll_action_id
   AND action_information_category = 'CAEOY EMPLOYER INFO';

Because the view returns one row per archived RL-2 action, it is well suited to set-based extraction into a staging table for transmission file generation and archival audit trails.