Search Results update_apl_assignment




Overview
Explore in AI Chat

Overview

HR_PROCESS_ASSIGNMENT_SS is an Oracle EBS PL/SQL package owned by the APPS schema that centralizes the server-side logic used by Oracle Self-Service Human Resources (SSHR) to validate, persist, and update employee assignment records. In the 12.1.1 and 12.2.2 releases the package acts as the transactional bridge between SSHR business process flows (the assignment-related workflow activities initiated from the Employee Self-Service, Manager Self-Service, and HR Professional responsibilities) and the underlying HR foundation tables. Rather than writing directly to PER_ALL_ASSIGNMENTS_F, SSHR pages such as Salary Change, Transfer, Promotion, and Assignment updates route their data through this package, which applies the appropriate HR_API validation logic and preserves the data-integrity rules enforced elsewhere in Oracle HRMS. The package also resolves supporting descriptive attributes — position, organization, location, soft-coding key flexfield segments, vendor and purchase-order references, and probation dates — that the SSHR assignment pages require for display and confirmation before the final save is committed through the HR API transaction framework.

Key Procedures and Functions

  • PROCESS_SAVE — the principal entry point invoked when an SSHR assignment transaction is submitted for saving; coordinates validation and delegates persistence.
  • PROCESS_API — wraps the call to the underlying HR_API layer so that the assignment change is written through supported, validated APIs rather than direct DML.
  • UPDATE_ASSIGNMENT — applies the actual attribute changes to the assignment record.
  • UPDATE_APL_ASSIGNMENT — handles the associated assignment/pay-proposal update path used when a proposal must also be refreshed.
  • GET_ASSIGNMENT — retrieves the current assignment row for the transaction context.
  • GET_ASG_FROM_TT and GET_ASSIGNMENT_FROM_TT — extract assignment identifiers from the SSHR transient table (TT) structures passed in from the calling flow.
  • GET_REC_CNT — returns the number of records in the transient collection, used for loop control.
  • UPDATE_OBJECT_VERSION — increments the object version number, supporting SSHR's optimistic locking and change-detection model.
  • GET_PO_NUMBER, GET_PO_LINE_NUBER (the documented spelling), and GET_VEND_SITE_NAME — resolve purchase-order and supplier-site descriptive fields for assignment-related statutory or contingent-worker information.
  • GET_PROBATION_END_DATE — derives the calculated probation end date from the applicable probation-period rules.

Tables Accessed

The package reads and writes PER_ALL_ASSIGNMENTS_F as its primary datastore, and relies on WF_ITEMS and WF_ACTIVITY_ATTR_VALUES to obtain the workflow item key and activity attributes that identify the SSHR transaction being processed. Supporting descriptive lookups come from HR_ALL_ORGANIZATION_UNITS_TL, HR_ALL_POSITIONS_F_TL, HR_LOCATIONS_ALL, HR_ORGANIZATION_INFORMATION, and PAY_JOB_WC_CODE_USAGES. Key-flexfield and soft-coding resolution use FND_ID_FLEX_SEGMENTS, FND_SEGMENT_ATTRIBUTE_VALUES, and HR_SOFT_CODING_KEYFLEX. Legislative validation leverages PAY_LEGISLATION_RULES, benefits context uses BEN_PGM_F, and API transaction state is tracked in HR_API_TRANSACTION_STEPS and HR_API_TRANSACTION_VALUES.

Usage Notes

HR_PROCESS_ASSIGNMENT_SS is an internal SSHR server-side component and is not intended for direct invocation from custom code; standard usage occurs through SSHR self-service flows. It is referenced by several sibling packages, including HR_PAY_RATE_SS, HR_PAY_RATE_GSP_SS, HR_PROCESS_ASSIGNMENT_STEP_SS, HR_PROCESS_EIT_SS, HR_PROCESS_SIT_SS, and HR_RATE_VALUES_SWI, indicating that rate and EIT/SIT processing flows reuse its save and retrieval routines. Because it calls HR_API and manipulates assignment data, any custom extension should call the supported HR_ASSIGNMENT_API or equivalent rather than this package directly. It participates in the SSHR optimistic-locking model via UPDATE_OBJECT_VERSION, so callers must pass a current object version to avoid concurrent-update errors. During 12.1.1 to 12.2.2 upgrades the package should be treated as delivered Oracle code and recompiled with the standard AD utilities as part of the HRMS patch cycle.