Results for “irc_offers_be3”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.IRC_OFFERS_BE3 is a server-side PL/SQL package belonging to the Oracle iRecruitment application family within Oracle E-Business Suite. The object carries the _BE3 suffix, indicating that it is a Business Event or back-end generated package whose members are produced automatically from a declarative object definition rather than being written by hand. The header comment embedded in the source ("Code generated on 30/03/2009") confirms this generated lineage and ties the package to the HR API wrapper framework, as evidenced by the inherited hrapiwfe.pkb version string.

The business function of IRC_OFFERS_BE3 is to expose the transactional operations that act on offer records maintained by iRecruitment. An "offer" in iRecruitment represents the formal employment proposal extended to a candidate; it carries an approval workflow, versioning, and lifecycle states. This package provides the programmatic entry point through which such offer records are manipulated by the application's business logic layer.

Key Procedures and Functions

The ETRM metadata documents a single public procedure:

• DELETE_OFFER_A — the deletion entry point for an offer. The trailing _A denotes the standard Oracle API convention of an "A" (atomic/primary) wrapper procedure that performs the delete operation against a specific offer record. It accepts an object version number, used for optimistic locking so that a stale session cannot remove a record that has been modified since it was queried, and an offer identifier that selects the target row. The procedure is intended to remove the offer and its dependent data in a controlled manner and is the sole documented member of the package.

No additional procedures or functions are recorded for this package in the ETRM 12.2.2 metadata; the implementation is deliberately narrow, consistent with a generated API surface that is invoked only for a specific administrative action.

Tables Accessed

The documented table references are limited, reflecting the generated wrapper's focus on event notification rather than direct manipulation of the iRecruitment base tables:

• PER_WF_EVENTS_S — the Oracle Workflow events subscription table in the HR schema. Access to this table indicates that the delete operation raises or consumes a business event, allowing subscribers to react to the removal of an offer.
• DBMS_LOB — the Oracle-supplied large object package, referenced for handling CLOB or BLOB payloads, typically the event data associated with the workflow event.
• DUAL — the standard single-row pseudo-table, used for simple expression evaluation and consistency checks within the generated code.

Because the metadata records only these references, actual row-level changes to the offer tables are delegated to the underlying iRecruitment API layers that this generated package calls.

Usage Notes

IRC_OFFERS_BE3 is not intended for direct invocation by end users. It is normally called by the iRecruitment forms and business logic when a user cancels or withdraws an offer, and by concurrent programs or custom integrations that need to programmatically terminate an offer record. Callers should supply a current object version number to satisfy the optimistic locking requirement; a mismatch will cause the API to fail rather than silently overwrite concurrent changes.

The package falls under the OTHER API classification in ETRM, meaning it is a generated, framework-owned object rather than a supported public API. Customizations should avoid modifying it, since regenerating the underlying definition would overwrite any changes. Integrations requiring offer deletion should invoke the supported iRecruitment APIs or the documented wrapper rather than bypassing it. Its membership in the HR API wrapper family also means it participates in the standard business event publication mechanism through PER_WF_EVENTS_S, so downstream subscribers configured in Oracle Workflow will be notified when an offer is removed. The package is referenced by one other package, which reflects this layered, generated architecture.