Search Results update_fr_pers_pay_method




Overview
Explore in AI Chat

Overview

APPS.HR_FR_PERS_PAY_METHOD_API is a French localization API within Oracle E-Business Suite Human Resources (Oracle HRMS). Its purpose is to manage the personal payment methods that a French employee or payment recipient may hold on an assignment, including the bank and account details required for disbursement. The package encapsulates the business logic that validates and persists these records directly against the PAY_PERSONAL_PAYMENT_METHODS_F table, shielding callers from the underlying column layout, effective-date handling, and object-version concurrency rules.

The package is classified as an API in the ETRM repository and is owned by the APPS schema. It belongs to the PL/SQL generation associated with the French payroll and payment file processing features (the source header references the peppmfri module), and it exists to provide a supported, version-controlled entry point for creating and amending personal payment method rows rather than allowing direct DML. This is significant because personal payment methods are DateTracked entities: changes take effect on a specified date, produce new effective start and end dates, and increment an object version number used for optimistic locking.

Key Procedures and Functions

  • CREATE_FR_PERS_PAY_METHOD — Creates a new personal payment method record for an assignment effective from a given date. The procedure accepts the assignment, organization payment method, monetary amount, percentage, priority, comments, a descriptive flexfield attribute category followed by attributes 1 through 20, and a comprehensive set of bank and payee details (bank name, bank code, branch code, branch name, account number, account name, third-party payee, transmitter code, deposit type, valid bank branch, payee type, and payee ID). It returns the new personal payment method identifier, the associated external account identifier, the object version number, and the effective start and end dates. This is the procedure most closely associated with the search term p_attribute1, which appears as the first descriptive flexfield segment in the signature.
  • UPDATE_FR_PERS_PAY_METHOD — Amends an existing personal payment method, applying the same DateTrack semantics so that the change is recorded with a new effective period while preserving historical rows. Like the create routine, it exposes the descriptive flexfield attribute list for maintenance of the localization's context-sensitive segments.

The presence of the twenty attribute parameters, coupled with p_attribute_category, indicates that the API surfaces the complete descriptive flexfield structure of the personal payment method entity, allowing French-specific statutory or bank-formatting information to be stored alongside the standard payment fields.

Tables Accessed

The only documented table accessed through APPS synonyms is PAY_PERSONAL_PAYMENT_METHODS_F, the core transactional table for personal payment methods. The API inserts new rows on create and DateTracked rows on update, populating standard columns from the explicit parameters and the descriptive flexfield attribute columns from the p_attribute1 … p_attribute20 arguments. No other packages are recorded as referencing this API, so it functions as a terminal integration point rather than an internal building block.

Usage Notes

Callers are typically Oracle Forms-based HRMS screens that maintain employee bank and payment information, concurrent programs that load or migrate payment methods, and custom PL/SQL integrations that need to register a French personal payment method in a supported manner. Because the package is DateTrack-aware, callers must supply a valid effective date and should respect the returned object version number when performing subsequent updates. Validate mode should be used first in batch or interface code so that errors are surfaced before any database change is committed. Direct DML against PAY_PERSONAL_PAYMENT_METHODS_F should be avoided in favour of this API to preserve flexfield validation, effective dating, and version consistency.