Search Results pay_org_payment_methods_tl

Overview

APPS.PAY_OPM_BUS is the business-layer package body for Oracle Payroll's organization payment method entity, known internally as OPM. It encapsulates the server-side validation, security, and legislative logic that governs records in the PAY_ORG_PAYMENT_METHODS_F and PAY_ORG_PAYMENT_METHODS_F_TL tables. The package belongs to the Oracle HRMS/Payroll family of generated business (BUS) packages, which in Oracle EBS 12.1.1 and 12.2.2 are produced by the Oracle Application Object Library (OA Framework) business component generation utilities. The header comment references file pyopmrhi.pkb and revision 120.4, confirming that this is a delivered Oracle-owned object rather than a customer extension.

Users searching for pay_org_payment_methods_tl are directed to this package because the translated (TL) and base (F) tables are the data columns owned and validated by the business layer implemented here. The package is the technical counterpart to the organization payment method form and the underlying entity relationship for payroll payment methods.

Key Procedures and Functions

• SET_SECURITY_GROUP_ID — Resolves the security group identifier for a given organization payment method. It queries PER_BUSINESS_GROUPS joined to PAY_ORG_PAYMENT_METHODS_F using the primary key org_payment_method_id, and raises PAY HR_7220_INVALID_PRIMARY_KEY when the key does not return a row. This enforces row-level security at the business group boundary.
• RETURN_LEGISLATION_CODE — Derives the legislation code applicable to the organization payment method record. The package declares global variables g_legislation_code and g_org_payment_method_id specifically for use by this function, caching the values to avoid repeated legislative lookups.
• INSERT_VALIDATE — Performs pre-insert validation on a new organization payment method definition, checking mandatory attributes and referential consistency before the row is written.
• UPDATE_VALIDATE — Validates changes to an existing organization payment method, ensuring edits do not violate business rules or break relationships with dependent payroll and payment objects.
• DELETE_VALIDATE — Confirms that a deletion request is legal, preventing removal of a payment method still referenced by assignments, payroll actions, or prepayments.

Tables Accessed

The package reads and writes PAY_ORG_PAYMENT_METHODS_F and its translation table PAY_ORG_PAYMENT_METHODS_F_TL as the primary entity. Supporting validation relies on PAY_PAYMENT_TYPES, PAY_PRE_PAYMENTS, and PAY_EXTERNAL_ACCOUNTS to confirm the payment method is consistent with external payment processing. Payroll validation references PAY_ALL_PAYROLLS_F, PAY_PAYROLL_ACTIONS, and PAY_ASSIGNMENT_ACTIONS to detect dependencies that block deletion or modification. Balance-related checks use PAY_BALANCE_TYPES, PAY_DEFINED_BALANCES, and PAY_BALANCE_DIMENSIONS. Legislative rules draw on PAY_LEGISLATION_RULES and PAY_LEGISLATIVE_FIELD_INFO. PER_BUSINESS_GROUPS supplies the security group resolution. ALL_TABLES is referenced indirectly by the generated business logic.

Usage Notes

PAY_OPM_BUS is normally invoked indirectly. The Oracle Payroll organization payment method form calls these validation procedures through the OA Framework business component layer whenever a user creates, updates, or deletes a payment method. Concurrent programs that load or migrate payment method data also route through this package to preserve validation integrity. The ETRM metadata records that the package is referenced by three other packages, indicating layered API dependencies; direct calls are appropriate only in custom code that fully replicates the surrounding validation, security group initialization, and legislation context. Customizations should call the public business procedures (INSERT_VALIDATE, UPDATE_VALIDATE, DELETE_VALIDATE) rather than duplicating table-level inserts, because the generated validation sequence is required for data integrity across the 12.1.1 and 12.2.2 releases.