Search Results pay_act

Overview

PAY_CA_T4A_CANCEL_MAG is an Oracle Payroll Canadian legislative reporting package that produces the magnetic media (magtape) file used to transmit T4A cancellation records to the Canada Revenue Agency. T4A slips report pension, retirement, annuity, and other supplementary income amounts, and a cancellation file is required when a previously issued T4A slip must be voided or replaced. The package generates the transmittal, employer, and employee-level records that make up that cancellation submission in a fixed-format layout suitable for magnetic media or electronic filing.

The package is declared with AUTHID CURRENT_USER and resides in the APPS schema. Its cursor logic keys off the Fed Magnetic Reporting organization information context and reads a single completed payroll action identified by the PAY_ACT parameter, using PAY_MAGTAPE_GENERIC.GET_PARAMETER_VALUE to resolve that parameter at runtime. This aligns it with the family of PAY_CA_T4A_* magtape packages and the generic magnetic media generator that together implement Canadian T4/T4A reporting in Oracle EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes thirteen documented procedures and functions. They are grouped by role below; parameter signatures are not restated because the metadata does not define them.

• GET_REPORT_PARAMETERS — Supplies the report parameter values required by the concurrent program invocation, including the payroll action identifying the run.
• RANGE_CURSOR / ACTION_CREATION — Support the standard magnetic media processing model: defining the range of assignment actions to process and creating the action records that the report writer consumes.
• VALIDATE_GRE_DATA — Validates transmitter and employer identification data (GRE, or employer transmitter number) before the file is built, preventing invalid submissions.
• GET_PARAMETER and GET_ARCH_VAL — Retrieve a single runtime parameter value and archive item values respectively, drawing parameters from the payroll action and archived values from the archive schema.
• CONVERT_2_XML — Transforms the assembled record data into XML, supporting electronic filing alternatives to flat magtape output.
• GET_T4A_PP_REGNO — Returns the T4A payer registration number used in the transmittal header.
• T4A_CANCEL_MAG_TRANSMITTER, T4A_CANCEL_EMPLOYER_RECORD, T4A_CANCEL_EMPLOYER_START, T4A_CANCEL_EMPLOYEE_RECORD, END_OF_FILE — The record-writing routines that emit, in order, the transmitter header, employer start and employer detail records, individual employee cancellation records, and the end-of-file trailer that closes the file.

Tables Accessed

The package reads and writes through APPS synonyms. Payroll run and process state come from PAY_PAYROLL_ACTIONS, PAY_ASSIGNMENT_ACTIONS (and PAY_ASSIGNMENT_ACTIONS_S), and PAY_ACTION_INFORMATION; PAY_ACTION_INTERLOCKS support the locked-action relationships used to link original and amending runs, as illustrated in the commented cursor variant that resolves the original T4A payroll action. Employer and transmitter identities are resolved from HR_ORGANIZATION_INFORMATION (Fed Magnetic Reporting context) and HR_ALL_ORGANIZATION_UNITS. Person and assignment data are drawn from PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, PER_ADDRESSES, and HR_ASSIGNMENT_SET_AMENDMENTS. Archived balances and element values are read from FF_ARCHIVE_ITEMS and FF_DATABASE_ITEMS, with DUAL and PLITBLM used for utility and PL/SQL table operations.

Usage Notes

PAY_CA_T4A_CANCEL_MAG is not referenced by any other package in the ETRM inventory; it is an entry point invoked directly, typically from the Canadian T4A magnetic media concurrent program or its associated submission form. It is called after the payroll action to be cancelled or amended has been completed, since the cursor filter requires PPA.ACTION_STATUS = 'C'. The target run is passed through the PAY_ACT parameter, resolved via the generic magtape utility. Because it performs no update of core payroll tables, it is safe to rerun for file regeneration. Custom code should call the documented procedures only through the supported concurrent program interface, as the interface is classified OTHER and not published as a public API.