Results for “transfer_act_id”

50+ results




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

Overview

PAY_GB_RTI_OUTPUT is a United Kingdom–specific Oracle Payroll package that supports Real Time Information (RTI) reporting. Its stated purpose is to fetch archived data produced by RTI processes, convert that data into XML, and merge the result with the associated EText file to generate the final RTI output. The package is defined with AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the invoking user rather than the package owner, which is relevant where APPS-owned code accesses synonyms in a multi-schema EBS environment. The header comment indicates the package was created under version 115.0 in October 2011 and subsequently patched (115.1, 115.2) to correct comparison operators and remove incorrect code. The version stamp 120.2.12020000.1 identifies the file as part of the 12.2 code line, while the same object is present in 12.1.1 instances under the corresponding 12.1 version stamps.

The user search term transfer_act_id reflects a central element of this package. The declared cursors select assignment action identifiers and emit them as EText/XML attributes. In particular, eas_employee selects paa.assignment_action_id from PAY_ASSIGNMENT_ACTIONS and aliases it as TRANSFER_ACT_ID, while eas_asg_actions reads the value of a parameter named TRANSFER_ACT_ID through pay_magtape_generic.get_parameter_value. These constructs bind the generated output to the specific transfer action being reported.

Key Procedures and Functions

The ETRM metadata documents seven callable units. Their purposes are as follows:

  • RANGE_CURSOR — establishes the driving cursor or range over the archived RTI data set that the output process will iterate.
  • ACTION_CREATION — creates or derives the payroll action context needed to associate archived data with the RTI output run.
  • EAS_HEADER_PROC — generates the header portion of the EAS (Employer Annual Summary / alignment) output, including the payroll action reference supplied by the EAS header cursor.
  • EAS_EMPLOYEE_PROC — generates per-employee EAS output, emitting assignment action, assignment, and transfer action identifiers for each employee.
  • NINO_HEADER_PROC — generates the header portion of the National Insurance Number notification output.
  • NINO_EMPLOYEE_PROC — generates per-employee NINO output, again including assignment action and transfer action identifiers.
  • END_OF_FILE — writes the closing or trailer records that terminate each generated output file.

The documented cursors eas_header, eas_employee, eas_asg_actions, nino_header, and nino_employee supply the row sets consumed by these procedures. Parameter lists are not reproduced here, as the available metadata does not document them.

Tables Accessed

The package reads and, in places, writes the following objects through APPS synonyms:

  • PAY_ASSIGNMENT_ACTIONS — the principal source for assignment action and assignment identifiers used as transfer action values.
  • PAY_ASSIGNMENT_ACTIONS_S — the translated or secondary view of assignment actions, used where descriptive or language-dependent context is required.
  • PAY_PAYROLL_ACTIONS — identifies the payroll action that drives the RTI output run.
  • PAY_ACTION_INFORMATION — holds the parameter values, including TRANSFER_ACT_ID and TRANSFER_PAYROLL_ACTION_ID, retrieved via pay_magtape_generic.get_parameter_value.
  • PER_ALL_ASSIGNMENTS_F — supplies assignment-level attributes for the employees included in the output.
  • DUAL — used by single-row cursors that construct literal header and action tags.

Usage Notes

PAY_GB_RTI_OUTPUT is internal payroll infrastructure rather than a public API; the ETRM classification records it as OTHER, and no other packages reference it directly. It is normally invoked from the RTI output concurrent program or from the EText/BI Publisher generation path during a UK RTI submission cycle. Custom code should not call its procedures directly, because they emit file fragments in a defined sequence and depend on parameter values stored in PAY_ACTION_INFORMATION by the preceding RTI archival process. Developers troubleshooting RTI output content, particularly transfer action identifiers appearing incorrectly in EAS or NINO files, should inspect the transfer action and payroll action parameters written to PAY_ACTION_INFORMATION and the corresponding rows in PAY_ASSIGNMENT_ACTIONS.