Search Results get_processing_type
Overview
PAY_IN_UTILS is a shared utility package in the Oracle E-Business Suite Payroll (PAY) schema, owned by APPS and shipped under the pyinutil.pkh/pyinutil.pls source files. It functions as a common service layer for payroll-related processing logic, supplying reusable helper routines that other payroll packages, concurrent programs, and forms invoke rather than reimplementing. The package provides services in several distinct areas: action-sequence resolution for assignment processing, diagnostic tracing and location reporting, message construction and raising, date and tax-year derivation, assignment and element-link validation, organizational classification checks, soft coding key flexfield segment retrieval, and miscellaneous value conversions such as number-to-words and HTML string encoding.
Because it is classified as an OTHER (non-API) package, it is not a public integration interface. It is, however, heavily internalized: the ETRM metadata records that PAY_IN_UTILS is referenced by 53 other packages, which reflects its role as a foundational dependency across the payroll product family. Its design intent is defensive simplicity — broad access via PUBLIC declarations, minimal side effects in getter routines, and centralized handling of routine payroll housekeeping tasks.
Key Procedures and Functions
- GET_MAX_ACT_SEQUENCE — Returns the maximum action sequence for a given assignment and process type as of an effective date, used when appending new assignment actions.
- SET_LOCATION — Sets the current processing location based on trace state, message text, and step indicator, supporting diagnostic navigation.
- TRACE — Overloaded trace utility (documented in both procedure and function forms) that emits a message with an associated value for debugging payroll logic.
- NULL_MESSAGE — Handles null-message semantics, allowing callers to suppress or normalize empty message content within the messaging flow.
- GET_PAY_MESSAGE / RAISE_MESSAGE — Retrieve and raise standardized payroll messages, providing consistent error and information delivery.
- GET_USER_TABLE_VALUE / GET_RUN_TYPE_NAME — Lookup helpers for user-defined table values and payroll run type names.
- GET_PERSON_ID / GET_ASSIGNMENT_ID / GET_EFFECTIVE_DATE — Accessor functions that resolve commonly needed context values.
- NEXT_TAX_YEAR — Derives the following tax year for payroll processing.
- VALIDATE_DATES / CHK_ORG_CLASS / CHK_ELEMENT_LINK — Validation routines for date ranges, organization classification, and element link integrity.
- GET_ELEMENT_LINK_ID / GET_EE_VALUE — Resolve element link identifiers and employee-level values.
- GET_SCL_SEGMENT_ON_DATE — Retrieves a soft coding key flexfield segment value effective on a given date.
- NUMBER_TO_WORDS / ENCODE_HTML_STRING — Formatting utilities converting numeric amounts to words and escaping HTML-sensitive content.
Tables Accessed
The package reads and, where applicable, writes the core payroll data model through APPS synonyms:
- Payroll processing: PAY_ACTION_INFORMATION, PAY_ASSIGNMENT_ACTIONS, PAY_ASSIGNMENT_LINK_USAGES_F, PAY_BALANCE_TYPES, PAY_BALANCE_FEEDS_F, PAY_ELEMENT_CLASSIFICATIONS, PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_ENTRY_VALUES_F, PAY_ELEMENT_LINKS_F, PAY_ELEMENT_TEMPLATES, PAY_ELEMENT_TYPES_F, PAY_FORMULA_RESULT_RULES_F, FF_FORMULAS_F — supporting element definition, balance feed, entry value, and formula result lookups.
- HR: HR_ORGANIZATION_INFORMATION and HR_SOFT_CODING_KEYFLEX — supporting organization classification checks and soft coding key flexfield segment retrieval.
Usage Notes
PAY_IN_UTILS is invoked indirectly by the payroll processing engine, by payroll forms, and by other payroll packages during normal concurrent program execution. Direct custom invocation is possible where documented routines suit a requirement — for example, date validation, person or assignment resolution, or message retrieval — but because this is an OTHER-classified package, signatures may change between releases and are not covered by Oracle's public API compatibility guarantees. Custom code should treat it as an internal dependency, favor documented procedures where reused, and re-validate behavior on 12.1.1 versus 12.2.2 upgrades, particularly for trace and messaging routines whose output may influence diagnostics only.
-
PACKAGE: APPS.PAY_IN_UTILS
12.1.1
-
PACKAGE BODY: APPS.HR_PERSON_ABSENCE_API
12.1.1
-
PACKAGE: APPS.PAY_IN_UTILS
12.2.2
-
PACKAGE BODY: APPS.PAY_IN_UTILS
12.1.1
-
PACKAGE: APPS.HR_PERSON_ABSENCE_API
12.2.2
-
PACKAGE BODY: APPS.PAY_IN_UTILS
12.2.2
-
PACKAGE: APPS.HR_PERSON_ABSENCE_API
12.1.1
-
PACKAGE BODY: APPS.HR_PERSON_ABSENCE_API
12.2.2
-
APPS.HR_PERSON_ABSENCE_API dependencies on PAY_ELEMENT_TYPES_F
12.1.1
-
APPS.HR_PERSON_ABSENCE_API dependencies on PAY_ELEMENT_TYPES_F
12.2.2
-
APPS.HR_PERSON_ABSENCE_API dependencies on HR_UTILITY
12.1.1
-
APPS.HR_PERSON_ABSENCE_API dependencies on HR_UTILITY
12.2.2