Search Results g_package
Overview
HR_ABSUTIL_SS is a server-side PL/SQL utility package in the Oracle E-Business Suite APPS schema that supports the Absence Management (formerly Advanced Benefits absence tracking) and Self-Service absence flows. Its header identifies it as the utilities package for the Oracle HRMS absence management function, and its 20 documented routines are all read-oriented convenience functions plus a small number of transaction-oriented procedures. The package provides the standard "SS" (Self-Service) helper layer that OAF-based and forms-based absence pages call to translate raw HR_API_TRANSACTIONS data into display-ready values such as start dates, end dates, absence types, categories, durations, and approval states. It is not a public business API in the same sense as a date-track or absence business process API; rather it is an internal implementation package owned by APPS and classified as OTHER in the ETRM 12.2.2 repository, referenced by two other packages.
Key Procedures and Functions
The documented procedures divide into distinct groups.
- Date accessors: GETSTARTDATE and GETENDDATE return the effective start and end date of an absence, reading the transaction steps for the transaction and resolving the stored canonical date via FND_DATE. GETABSDURHOURS and GETABSDURDAYS, together with GETABSENCEHOURSDURATION and GETABSENCEDAYSDURATION, expose the calculated duration of an absence in hours or days.
- Classification accessors: GETABSENCETYPE, GETABSENCECATEGORY, and GETABSENCECATEGORYCODE return the absence type and category description/code associated with a transaction, drawing on PER_ABSENCE_ATTENDANCE_TYPES, PER_ABS_ATTENDANCE_TYPES_TL, and FND_LOOKUP_VALUES.
- Status and approval accessors: GETAPPROVALSTATUS, GETAPPROVALSTATUSCODE, GETABSENCESTATUS, GETABSENCESTATUSVALUE, and GETABSENCENOTIFICATIONDETAILS surface the workflow approval state and notification context, using WF_ITEMS, WF_ITEM_ACTIVITY_STATUSES, WF_NOTIFICATIONS, and FND_NEW_MESSAGES.
- Permission predicates: ISUPDATEALLOWED, ISCONFIRMALLOWED, and ISCANCELALLOWED return booleans indicating whether the current absence can be updated, confirmed, or cancelled by the caller.
- Supporting documents: HASSUPPORTINGDOCUMENTS checks FND_ATTACHED_DOCUMENTS for attachments linked to the absence.
- Transaction maintenance: DELETE_TRANSACTION and REMOVE_ABSENCE_TRANSACTION remove absence transactions and their associated HR_API_TRANSACTIONS / HR_API_TRANSACTION_STEPS rows.
Tables Accessed
The package reads and writes HR_API_TRANSACTIONS and HR_API_TRANSACTION_STEPS to obtain the underlying business process context, including the Information1 through Information4 columns from which start and end dates are derived. Descriptive data is drawn from PER_ABSENCE_ATTENDANCE_TYPES and its translation table PER_ABS_ATTENDANCE_TYPES_TL, with lookups resolved through FND_LOOKUP_VALUES. Workflow state is obtained from WF_ITEMS, WF_ITEM_ACTIVITY_STATUSES, and WF_NOTIFICATIONS, and remaining-item messaging from FND_NEW_MESSAGES. Attachments are verified against FND_ATTACHED_DOCUMENTS. All access is via APPS synonyms.
Usage Notes
HR_ABSUTIL_SS is normally invoked indirectly by the Absence Management self-service pages, the absence approval workflow, and any custom concurrent or PL/SQL code that needs to derive display values for an absence without duplicating the standard derivation logic. It is referenced by two other packaged objects, confirming its role as a shared helper rather than an entry-point API. It should not be called as a business process API for creating absences; creation and update are handled by the HR_API and absence business process packages, after which these utilities are used to read back the resulting state. Because it is an internal APPS-owned package, customers should treat the signatures as subject to change between patch levels and avoid direct dependencies where an equivalent public API exists.
-
APPS.HR_COMM_API SQL Statements
12.2.2
-
APPS.HR_COMM_API SQL Statements
12.1.1
-
PACKAGE BODY: APPS.HR_ABSUTIL_SS
12.1.1
-
APPS.VSP_API SQL Statements
12.1.1
-
APPS.OTA_VSP_API SQL Statements
12.2.2
-
PACKAGE BODY: APPS.PY_FR_ADDITIONAL_ELEMENT_RULES
12.2.2
-
PACKAGE BODY: APPS.PY_FR_ADDITIONAL_ELEMENT_RULES
12.1.1
-
APPS.OTA_VSP_API SQL Statements
12.1.1
-
PACKAGE BODY: APPS.HR_ABSUTIL_SS
12.2.2
-
APPS.VSP_API SQL Statements
12.2.2
-
APPS.HR_FCT_BUS SQL Statements
12.2.2
-
APPS.HR_FGT_BUS SQL Statements
12.1.1
-
APPS.IRC_IPC_BUS SQL Statements
12.2.2
-
APPS.HR_SFT_BUS SQL Statements
12.2.2
-
APPS.HR_FGT_BUS SQL Statements
12.2.2
-
APPS.HR_FDG_BUS SQL Statements
12.2.2
-
APPS.HR_WNP_BUS SQL Statements
12.2.2
-
APPS.HR_FSC_BUS SQL Statements
12.2.2
-
APPS.HR_FGI_BUS SQL Statements
12.1.1
-
APPS.HR_FSC_BUS SQL Statements
12.1.1
-
APPS.HR_FDG_BUS SQL Statements
12.1.1
-
APPS.HR_FCN_BUS SQL Statements
12.2.2
-
APPS.HR_HRC_BUS SQL Statements
12.1.1
-
APPS.IRC_IID_BUS SQL Statements
12.1.1
-
APPS.OTA_TAD_API SQL Statements
12.1.1
-
APPS.PQH_GVN_BUS SQL Statements
12.1.1
-
APPS.HR_FGI_BUS SQL Statements
12.2.2
-
APPS.HR_WNP_BUS SQL Statements
12.1.1
-
APPS.HR_FTP_BUS SQL Statements
12.1.1
-
APPS.HR_FIT_BUS SQL Statements
12.1.1
-
APPS.HR_WPT_BUS SQL Statements
12.2.2
-
APPS.HR_WPT_BUS SQL Statements
12.1.1
-
APPS.HR_TPT_BUS SQL Statements
12.1.1
-
APPS.HR_FCT_BUS SQL Statements
12.1.1
-
APPS.HR_TMT_BUS SQL Statements
12.1.1
-
APPS.HR_TMT_BUS SQL Statements
12.2.2
-
APPS.HR_FTT_BUS SQL Statements
12.2.2
-
APPS.PAY_QPU_API SQL Statements
12.1.1
-
APPS.BEN_PSG_BUS SQL Statements
12.2.2
-
APPS.AME_ATL_BUS SQL Statements
12.2.2
-
APPS.PER_COT_BUS SQL Statements
12.1.1
-
APPS.AME_ACL_BUS SQL Statements
12.1.1
-
APPS.GHR_PRE_BUS SQL Statements
12.1.1
-
APPS.HR_OTY_BUS SQL Statements
12.1.1
-
APPS.HR_FIT_BUS SQL Statements
12.2.2
-
APPS.HR_FTT_BUS SQL Statements
12.1.1
-
APPS.HR_FWT_BUS SQL Statements
12.1.1
-
APPS.HR_FWT_BUS SQL Statements
12.2.2
-
APPS.HR_TPT_BUS SQL Statements
12.2.2
-
APPS.HR_FCN_BUS SQL Statements
12.1.1