Results for “set_savepoint”
10 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
IRC_UTILITIES_PKG is a shared utility package owned by the APPS schema in Oracle E-Business Suite, classified as an OTHER API within the ETRM repository. It functions as a general-purpose support library for the Oracle iRecruitment (IRC) product family and for other modules that interact closely with recruitment, applicant tracking, and person/party data. The package bundles heterogeneous helper routines that fall into three broad categories: transaction control wrappers intended for Java callers, human resources and party resolution helpers, and user-interface metadata lookups. Because the package is referenced by 162 other packages, it is a heavily depended-upon internal utility rather than a standalone business API. The user search term "get_current_employer" maps directly to the documented procedures GET_CURRENT_EMPLOYER and GET_CURRENT_EMPLOYER_PTY, which are two of the most commonly cited entry points in the package.
Key Procedures and Functions
- SET_SAVEPOINT — a wrapper invoked from Java code that establishes a savepoint to which processing can subsequently roll back.
- ROLLBACK_TO_SAVEPOINT — a companion wrapper, called from Java, that rolls back to the previously established savepoint, typically after an API validation step.
- GET_HOME_PAGE_FUNCTION — returns the function identifier associated with a passed-in responsibility identifier, used to resolve the correct home page for a user session.
- GET_CURRENT_EMPLOYER / GET_CURRENT_EMPLOYER_PTY — resolve the current employer for a person or party respectively; these are the primary routines behind the "get_current_employer" search.
- GET_MAX_QUAL_TYPE / GET_MAX_QUAL_TYPE_PTY — determine the highest qualification type applicable to a person or a party.
- GET_EMP_UPT_FOR_PERSON / GET_EMP_UPT_FOR_PARTY — retrieve employment-related update or effective-date information for a person or party.
- GET_APL_UPT_FOR_PERSON / GET_APL_UPT_FOR_PARTY — retrieve applicant-related update information for a person or party.
- GET_EMP_SPT_FOR_PERSON — retrieves employment support data for a person.
- GET_RECRUITMENT_PERSON_ID — resolves the recruitment-specific person identifier.
- IS_OPEN_PARTY, IS_INTERNAL_PERSON, IS_INTERNAL_EMAIL — boolean-style predicate checks used to classify parties, persons, and email addresses.
- IS_FUNCTION_ALLOWED — evaluates whether a given function is permitted in the current context.
- GET_LAST_QUAL_PTY — returns the most recent qualification for a party.
- REMOVETAGS — strips markup tags from text.
- IRC_APPLICANT_TRACKING — supports applicant tracking processing within iRecruitment.
Tables Accessed
The package reads and writes across HR, FND, and IRC schemas via APPS synonyms. PER_ALL_PEOPLE_F and PER_ADDRESSES supply person and address attributes central to employer and party resolution. HR_ALL_ORGANIZATION_UNITS, HR_ORGANIZATION_INFORMATION, and HR_ALL_POSITIONS_F provide organization and position context. FND_RESPONSIBILITY, FND_FORM_FUNCTIONS, FND_MENU_ENTRIES, and FND_USER support the responsibility and function lookups performed by GET_HOME_PAGE_FUNCTION and IS_FUNCTION_ALLOWED. IRC_ASSIGNMENT_DETAILS_F, IRC_ASSIGNMENT_STATUSES, IRC_DOCUMENTS, and IRC_NOTIFICATION_PREFERENCES back the recruitment-specific routines. GL_DAILY_RATES and FND_DESCR_FLEX_COLUMN_USAGES are referenced for currency and descriptive flexfield metadata.
Usage Notes
IRC_UTILITIES_PKG is generally not called directly by end users. Its savepoint and rollback routines are invoked from Java middle-tier code surrounding validation calls, while the employer, qualification, and party resolution functions are consumed by iRecruitment forms, concurrent programs, and the many dependent packages that reference this utility. Custom extensions in EBS 12.1.1 and 12.2.2 that need to determine a person's or party's current employer, qualification type, or recruitment person identifier can call GET_CURRENT_EMPLOYER, GET_CURRENT_EMPLOYER_PTY, or GET_RECRUITMENT_PERSON_ID rather than re-querying PER and HR tables directly, ensuring consistent behavior with standard iRecruitment processing.