Search Results p_payroll_name

Overview

PYZAMCRP is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the ETRM (E-Business Suite Technical Reference Manual) metadata as an "OTHER" API. Its name follows the Oracle Payroll (PY) naming convention, with the "ZA" segment indicating a South African localization component and the "MCRP" suffix denoting the Manual Credit Transfer Cheque Report. The package addresses a localized South African payroll disbursement requirement: the generation and issuance of manual credit transfer cheques. In many South African payroll environments, employee net pay is settled through electronic credit transfer into a bank account. When that electronic transfer cannot be completed — for example, because of invalid or unverified banking details, a rejected branch code, or a request for a physical instrument — the payroll department must produce a physical cheque to settle the payment manually. The single documented procedure, MANUAL_CT_CHEQUE, encapsulates this logic. The package header carries the version marker pyzamcrp.pkh 120.2 2005/06/28, placing it within the 11i through 12.1.1 lineage and carried forward unchanged into 12.2.2, where it remains present as an APPS-owned object without being registered as a formal public API.

Key Procedures and Functions

ETRM documents exactly one callable program unit in this package:

• MANUAL_CT_CHEQUE — Issues manual credit transfer cheques. This is the sole entry point of the package. It accepts identifying and control information for the payroll run being processed, including the payroll action identifier, the payroll name, the bank clearing (branch) code, and the starting cheque number to be produced. It returns an error code and a corresponding error message through its output parameters, following the standard Oracle Payroll API error-reporting convention used across the PY schema.

The procedure does not expose any overloaded variants, and no additional functions or procedures are declared in the documented header. Because the parameter list is fixed in the package specification, callers must supply all arguments; the error outputs must be checked after every invocation before downstream processing continues.

Tables Accessed

The package operates against the following documented tables (accessed through APPS synonyms), each of which supports a distinct phase of the cheque-issuance process:

• PAY_PAYROLL_ACTIONS — Supplies the payroll action context, confirming the run that produced the payments to be settled.
• PAY_ASSIGNMENT_ACTIONS — Identifies the assignment-level action rows whose results determine which payments require manual cheque issuance.
• PAY_PERSONAL_PAYMENT_METHODS_F — Provides the assignment's configured payment method, distinguishing manual cheque delivery from electronic credit transfer.
• PAY_EXTERNAL_ACCOUNTS — Holds the employee's external bank account details used to validate the payment.
• PAY_ZA_BRANCH_CDV_DETAILS — The South African branch code validation table, against which the supplied branch code is verified.
• PAY_PRE_PAYMENTS — Stores the pre-payment records that the cheque issuance process updates or consumes.

Usage Notes

PYZAMCRP is not a general-purpose public API and is not referenced by any other documented packages (referenced-by count of zero), indicating that it is invoked directly from the South African payroll localization layer. Typical invocation paths are a concurrent program in the South African Payroll responsibility, the corresponding report definition that drives cheque production, or custom localization code supplied during implementation. Callers are expected to submit a valid payroll action for processing, supply a validated bank clearing code, and nominate the first cheque number of the printed range. Because the procedure returns both an error code and an error message, custom code should evaluate the return values immediately after the call and raise or log failures before committing. Given the 2005 vintage of the package header and the "noship" marker in its version string, the logic is stable and has been carried forward without documented functional change into Oracle EBS 12.1.1 and 12.2.2. No online form is documented as calling this package directly; it should be treated as an internal payroll localization component rather than a supported integration interface.