Search Results check_run_result_usage




Overview
Explore in AI Chat

Overview

PAY_BALANCE_FEEDS_F_PKG is the PL/SQL package body that implements the application logic behind the Oracle E-Business Suite balance feed definition entity, stored in the PAY_BALANCE_FEEDS_F table. A balance feed defines the relationship between a source (such as an element input value, element run result value, or another balance) and a target balance belonging to an element or element classification. This package encapsulates the create, read, update, delete, and validation operations required to maintain those definitions. In a 12.1.1 or 12.2.2 environment, it is the server-side counterpart to the Balance Feeds form in Oracle Payroll and is the programmatic control point ensuring that every balance feed row written to the database is internally consistent and compatible with the element and balance structures it references.

As the package body sits in the APPS schema and is classified under the ETRM metadata as API type OTHER, it is treated as an internal, form-driven package rather than a formally published public API. This distinction matters: the set of procedures it exposes is designed to serve the maintainable views (PAY_BALANCE_FEEDS_F and PAY_BALANCE_FEEDS_S) and the Oracle Forms that manipulate them, rather than to provide a stable interface for third-party integrations.

Key Procedures and Functions

The package body exposes nine documented procedures and functions that together implement the full lifecycle of a balance feed record.

  • INSERT_ROW — Validates and inserts a new balance feed definition into PAY_BALANCE_FEEDS_F. It is the entry point for creating a feed that links a source and a target balance.
  • LOCK_ROW — Acquires a row-level lock on an existing balance feed record, providing the concurrency control required when a user edits a feed in the form or when multiple transactions target the same definition.
  • UPDATE_ROW — Applies modifications to an existing balance feed row after validation of the changed attributes such as the source type, target balance, and associated element or classification.
  • DELETE_ROW — Removes a balance feed definition, first checking whether the record may be safely deleted without leaving orphaned or inconsistent balance feed data behind.
  • CHECK_RUN_RESULT_USAGE — Determines whether a given run result value is already in use by a balance feed. This guards against duplicate or conflicting feed definitions that would otherwise distort balance accumulation.

These procedures internalize the validation rules enforced by HR_BALANCE_FEEDS and HR_API, calling these dependent packages to apply Oracle Payroll business rules, and FND_MESSAGE to surface error text to the calling form.

Tables Accessed

The package reads and writes the following documented tables, resolved through APPS synonyms.

  • PAY_BALANCE_FEEDS_F — The primary base table holding the business definition of each balance feed. It is the principal insert, update, delete, and lock target.
  • PAY_BALANCE_FEEDS_S — The translated/seed-side table that stores language-dependent descriptive attributes associated with a feed.
  • PAY_ELEMENT_CLASSIFICATIONS — Read to validate target balances defined at the element classification level.
  • PAY_ELEMENT_TYPES_F — Read to confirm that referenced elements exist and are valid for the effective date range.
  • PAY_INPUT_VALUES_F — Read to resolve element input values used as balance feed sources.
  • PAY_RUN_RESULT_VALUES — Read (and checked via CHECK_RUN_RESULT_USAGE) to identify run result values that serve as balance feed sources and to prevent their conflicting reuse.

Usage Notes

PAY_BALANCE_FEEDS_F_PKG is invoked primarily through the Oracle Payroll Balance Feeds maintenance form, which calls INSERT_ROW, UPDATE_ROW, DELETE_ROW, and LOCK_ROW as the user commits changes. The CHECK_RUN_RESULT_USAGE routine is exercised during validation of source definitions before a feed is persisted. The package is referenced by fifteen other database objects within the APPS schema, but is not itself referenced by external or outbound interfaces, reinforcing its role as a form-support package rather than a public API. Because it is marked as an internal API, custom code should not call it directly; integrators seeking to create balance feeds programmatically should use the supported HR_BALANCE_FEEDS interface, which this package in turn relies upon. The dependency on HR_API and HR_BALANCE_FEEDS means the package participates fully in Oracle Payroll datetrack and business-rule validation, so direct table manipulation bypassing it risks invalid balance feed data.