Search Results update_contract_a

Overview

The APPS.HR_CONTRACT_BK2 package body is an Oracle HRMS API hook artifact generated by the Oracle HRMS API Hook Pre-processor. It resides in the APPS schema and belongs to the family of business process hook packages (suffix "BK") that wrap the standard HRMS contract APIs. Its principal role is to expose pre-processing logic ("_A" suffix denotes the "before" or validation phase) and post-processing logic ("_B" suffix denotes the "after" or processing phase) that executes around the core contract maintenance operation performed by the underlying HR_CONTRACT_API.

In Oracle EBS 12.1.1 and 12.2.2, the HR contract entity (PER_CONTRACTS_F / PER_CONTRACTS) stores terms and conditions governing an assignment, including contract type, status, duration, parties, and descriptive flexfield attributes. The HR_CONTRACT_BK2 package provides the extension point through which Oracle's delivered contract validation and any customer-defined business rules can be injected into the update lifecycle. The generated header comment (hrctcapi.pkb 115.18, generated 2009/03/30) confirms it is a mechanism-generated companion to the shipped contract API rather than hand-coded application logic.

Key Procedures and Functions

The package body documents two procedures, both participation points in the contract update flow:

• UPDATE_CONTRACT_A — The "A" (before/validation) hook for updating a contract. It receives a comprehensive set of IN parameters mirroring the contract attributes to be changed, including the primary key context (contract identifier, effective dates, business group, object version number, person identifier), descriptive fields (reference, type, status, status reason, document status and change date, description, duration and duration units, contractual job title, parties, start/end reasons), extension-related fields (number of extensions, extension reason, extension period and units), and a full set of descriptive flexfield columns (twenty CTR information segments, the information category, and attribute category with attributes 1 through 20 and beyond). Because it is a validation-phase hook, its intended purpose is to inspect and, if required, reject or default incoming contract data before the base API commits the change. The user's search term, update_contract_a, corresponds directly to this procedure.
• UPDATE_CONTRACT_B — The "B" (after/processing) hook for the same update operation, invoked subsequent to the core change so that downstream side effects, derived data, or post-update business logic can be applied once the contract record has been modified.

Parameter lists are declared by the API hook pre-processor and should not be modified; the profile-driven hook framework maps them to the base API call.

Tables Accessed

The ETRM metadata does not surface an explicit list of base tables referenced through APPS synonyms. Functionally, the package operates against the HR contract data model, and any reads or writes are mediated through the base HR_CONTRACT_API it wraps rather than performed directly. The PER_CONTRACTS family (date-tracked and non-dated contract tables) and the associated descriptive flexfield structures are the logical targets. Because the documented procedures are hooks, direct DML within HR_CONTRACT_BK2 is not expected; the parameters carry the contract payload to and from the base API.

Usage Notes

• Invocation path: The package is not called directly by end users. It is invoked automatically by the HRMS API Hook framework when the base contract update API is executed, provided the corresponding hook is enabled.
• Forms and concurrent programs: Standard EBS contract maintenance UI (e.g., the Contract Management / People forms that call HR_CONTRACT_API.UPDATE_CONTRACT) and any concurrent or custom processes invoking the same API will trigger these hooks.
• Customization guidance: Customers implement site-specific validation or post-processing by wrapping or replacing the generated body; because it is a generated hook, customizations must be re-applied after patches or upgrades.
• Referenced by: Per ETRM, this package is referenced by one other package, consistent with the layered hook architecture used throughout the HRMS API stack.
• Version scope: Behavior is consistent across 12.1.1 and 12.2.2, though the online patching model of 12.2.2 requires additional care to ensure customized hook logic is preserved through editioning and patch cycles.