Search Results get_source_text2_context

Overview

PAY_FR_RULES is a French localization rules package within the Oracle E-Business Suite Payroll (PAY) module. Declared with AUTHID CURRENT_USER, it exposes a set of public procedures that supply and override payroll element context values during payroll processing. Its central purpose is to derive the source context fields—source text, secondary source text, source identifier, and source number—required by French statutory payroll elements, and to provide supporting hooks for organizational method resolution, multi-tax-unit payment flagging, and retroactive (retro) context overrides. The package originated as a template copy of PYCA_RULE and was progressively extended between 2001 and 2004, with the final change (version 115.6, January 2004) introducing GET_SOURCE_TEXT2_CONTEXT for bug 3360253 and GET_SOURCE_NUMBER_CONTEXT following bug 3305989. It is classified as an OTHER API rather than a public business API, indicating it is intended for internal payroll engine invocation rather than direct customer programming.

Key Procedures and Functions

• get_source_text_context — Derives and returns the primary source text context value for a given assignment action and employee.
• get_source_text2_context — Returns the secondary source text context value. Added in version 115.6 to address bug 3360253; this is the routine most directly associated with the user's search term.
• get_source_context — Supplies the source identifier context value, added in version 115.1.
• get_source_number_context — Supplies the source number context value, added in version 115.6 following bug 3305989.
• get_dynamic_org_meth — Resolves a replacement organization method. It accepts an assignment action, an effective date, and an organization method that has no bank account, returning the substitute organization method identifier. Added in version 115.2.
• get_multi_tax_unit_pay_flag — Returns the multi-tax-unit payment flag for a given business group. Added in version 115.4 under bug 2898674.
• retro_context_override — A retroactive context override hook that accepts an element entry identifier, a context name, and a context value, returning a replacement value. Added in version 115.5.

All out and in-out parameters are declared with NOCOPY, a convention applied consistently from version 115.3 onward to reduce parameter copying overhead.

Tables Accessed

The package reads and writes payroll and HR tables through APPS synonyms. Payroll element context data is sourced from FF_CONTEXTS, PAY_LEGISLATION_CONTEXTS, PAY_INPUT_VALUES_F, PAY_ELEMENT_TYPES_F, PAY_ELEMENT_TYPES_F_TL, PAY_ELEMENT_LINKS_F, PAY_ASSIGNMENT_ACTIONS, PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_ENTRY_VALUES_F, PAY_ENTRY_PROCESS_DETAILS, and PAY_FR_CONTRIBUTION_USAGES, the last being the French-specific contribution usage table. Organizational resolution relies on HR_ALL_ORGANIZATION_UNITS, HR_ALL_ORGANIZATION_UNITS_TL, and HR_ORGANIZATION_INFORMATION. FND_NEW_MESSAGES is referenced, most likely for error or warning message retrieval. These accesses support the derivation of context values, the mapping of contribution usages, and the identification of organization methods without associated bank accounts.

Usage Notes

PAY_FR_RULES is referenced by zero other packages in the documented metadata, confirming that it functions as an entry-point rules package consumed by the payroll engine rather than as a dependency of other PL/SQL units. It is typically invoked during element entry processing, when the payroll run must populate or override element context values for French legislative elements. The context-derivation routines are called as context hooks; retro_context_override is invoked specifically during retroactive processing to substitute context values for previously processed entries. Custom code should not call these procedures directly unless replicating payroll engine behavior, because parameter contracts and context resolution rules are governed by the French localization and may change between patch levels. The 12.1.1 and 12.2.2 releases share the same documented interface, so any customizations should be validated against the specific patch set in use.