Search Results get_rtn_from_tt

Overview

HR_LOA_SS is an Oracle E-Business Suite PL/SQL package owned by the APPS schema, classified under the ETRM as an "OTHER" API type. Despite its _SS suffix, which in EBS conventions often denotes a "single step" or supplementary API wrapper, HR_LOA_SS functions as the core transactional engine behind the Leave of Absence (LOA) self-service flows. It encapsulates the business logic required to create, update, validate, and delete person absence records in Oracle Human Resources, and to manage the underlying HR_API transaction framework that records each change as a discrete, auditable unit.

The package is central to absence and leave processing, bridging the user-facing self-service layer and the base tables that store absence attendance records. It orchestrates transactional integrity through the HR_API and HR_API_TRANSACTIONS infrastructure, ensuring that absence changes are properly staged, validated, and committed, and that group dates and category-specific rules (including GB legislative rules) are honored. The package is marked VALID in ETRM 12.2.2 and references APPS.HR_API, PER_ABSENCE_ATTENDANCES, and WF_ITEMS, and it is itself referenced by HR_ABSUTIL_SS.

Key Procedures and Functions

The documented 21 procedures and functions fall into several functional groups:

• Absence creation and update: CREATE_PERSON_ABSENCE, UPDATE_PERSON_ABSENCE, and DELETE_ABSENCE handle the lifecycle of a person's absence record in PER_ABSENCE_ATTENDANCES.
• Transaction management: CREATE_TRANSACTION, WRITE_TRANSACTION, GET_ABSENCE_TRANSACTION, GET_RETURN_TRANSACTION, GET_UPDATE_TRANSACTION, GET_ABS_FROM_TT, GET_RTN_FROM_TT, and GET_UPD_FROM_TT build and retrieve absence, return, and update transactions, including conversions between transaction tables (TT) and API structures.
• Processing and save: PROCESS_API, VALIDATE_API, PROCESS_SAVE, PROCESS_TXN_SAVE, PROCESS_UPDATE_SAVE, and PROCESS_UPDATE_TXN_SAVE drive the validation and persistence workflow for inserts and updates, both direct and transaction-based.
• Utility and validation: CALCULATE_ABSENCE_DURATION derives absence length; CHK_OVERLAP detects conflicting absence periods; and IS_GB_LEG_AND_CATEGORY_S tests whether the legislation and absence category correspond to the GB (United Kingdom) ruleset.

No parameter signatures are documented in the metadata and are deliberately omitted.

Tables Accessed

The package references the following tables through APPS synonyms:

• PER_ABSENCE_ATTENDANCES and PER_ABSENCE_ATTENDANCE_TYPES: store absence records and their configured absence types.
• PER_ALL_ASSIGNMENTS_F and PER_ALL_PEOPLE_F: provide assignment and person context for validation and duration calculation.
• HR_API_TRANSACTIONS, HR_API_TRANSACTION_STEPS, and HR_API_TRANSACTION_VALUES: implement the HR_API transaction framework used to stage and record changes.
• PAY_ELEMENT_LINKS_F and PAY_INPUT_VALUES_F: link absence processing to payroll elements and their input values.
• FF_FORMULAS_F: supplies Fast Formula definitions used in absence calculations.
• WF_ITEMS and FND_NEW_MESSAGES: support workflow notifications and messaging.
• DUAL and PLITBLM: provide standard SQL and PL/SQL utility support.

Usage Notes

HR_LOA_SS is typically invoked indirectly rather than directly by end users. It is called by the leave of absence self-service flows, by HR_ABSUTIL_SS, and by absence-related concurrent programs and forms that require transactional absence creation or update. In 12.1.1 and 12.2.2 the package executes within the APPS schema using the standard HR_API transaction model, so any custom code should invoke the documented PROCESS_API, VALIDATE_API, and PROCESS_SAVE entry points in that sequence to preserve validation and transaction integrity. Direct DML against PER_ABSENCE_ATTENDANCES should be avoided in favor of these APIs.