Results for “per_bf_gen_data_pump”

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

Overview

APPS.PER_BF_GEN_DATA_PUMP is a PL/SQL package in Oracle E-Business Suite that supports the Oracle Payroll backfeed (Balance Feed) infrastructure. The package name combines the "PER_BF" prefix — denoting the Oracle Human Resources backfeed components — with "GEN_DATA_PUMP," indicating its role as a generic data pump utility. Its purpose is to resolve and supply surrogate primary keys required by the backfeed APIs, particularly for the balance type datapump process associated with PER_BF_BALANCE_TYPES.

The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the defining user. The header carries the source control identifier pebgendp.pkh (version 115.4), reflecting its long-standing presence in the EBS code line. It is available in both the 12.1.1 and 12.2.2 releases.

In practice, the package shields callers from the complexity of deriving internal identifiers from user-facing names. Rather than forcing backfeed logic to join multiple date-tracked and translated tables directly, PER_BF_GEN_DATA_PUMP exposes dedicated lookup functions that accept business-friendly names and business group context and return the internal numeric identifiers the APIs require.

Key Procedures and Functions

The documented interface comprises six functions, each returning a BINARY_INTEGER identifier:

• GET_INPUT_VALUE_ID — Returns the input_value_id for the backfeed APIs. It resolves a reporting name, scoped by business group and effective date, to its corresponding input value. The documentation notes the reporting name can be treated as unique because of a database constraint.
• GET_BALANCE_TYPE_ID — Returns the balance_type_id for the backfeed APIs, resolving a balance type name within a business group and effective date.
• GET_PAYROLL_ID — Returns a Payroll ID, resolved from a payroll name, business group, and effective date.
• GET_PAYROLL_RUN_ID — Returns the identifier for a payroll run, used when backfeed processing must associate data with a specific run.
• GET_ASSIGNMENT_ID — Returns an assignment identifier from the person/assignment data model, supporting backfeed records tied to a worker's assignment.
• GET_PERSONAL_PAYMENT_METHOD_ID — Returns the personal payment method identifier, allowing backfeed APIs to reference a specific payment method.

The header declares PRAGMA RESTRICT_REFERENCES with WNDS (Write No Database State) on the documented functions, confirming they are read-only and perform no DML. This purity guarantee makes them safe to invoke from SQL contexts and within larger backfeed transactions.

Tables Accessed

The package reads from the following tables via APPS synonyms:

• HR_PUMP_BATCH_LINE_USER_KEYS — Stores user-defined keys associated with datapump batch lines, supporting the batched nature of backfeed data loading.
• PAY_ELEMENT_TYPES_F and PAY_INPUT_VALUES_F — Date-tracked tables supplying element type and input value definitions; the latter underpins GET_INPUT_VALUE_ID.
• PER_BF_BALANCE_TYPES — The backfeed balance type definitions that motivate the package's balance type resolution logic.
• PER_ALL_ASSIGNMENTS_F and PER_ALL_PEOPLE_F — Date-tracked person and assignment tables used to resolve assignment identifiers.
• PAY_PERSONAL_PAYMENT_METHODS_F and PAY_ORG_PAYMENT_METHODS_F_TL — Payment method tables, the latter translated, used by the payment method lookup.

All lookups are effective-dated, consistent with the effective-dating conventions of Oracle HRMS and Payroll.

Usage Notes

PER_BF_GEN_DATA_PUMP is an internal utility package, classified as OTHER rather than a public API. It is referenced by four other packages and is not intended for direct customer invocation. It is typically called by backfeed and datapump routines that must translate reporting names into the internal identifiers expected by the PER_BF_BALANCE_TYPES datapump API and related backfeed interfaces.

Because the functions are restricted to WNDS and perform no writes, they can be safely called during concurrent program execution, from PL/SQL batch processes, or within custom extension code that participates in the backfeed workflow. As with all APPS-owned objects, direct modification is not supported; any reliance on these functions should be treated as depending on internal EBS implementation details that may change between releases.