Search Results iby_bill_pkg




Overview
Explore in AI Chat

Overview

IBY_BILL_PKG is a valid PL/SQL package owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It resides within the Oracle Payments (IBY) product family, which is responsible for payment processing, funds capture, and payment instrument handling across the E-Business Suite. The package serves as an internal bill-handling utility that supports the creation and modification of "tangible" records — the payment instrument entities that Oracle Payments tracks when processing disbursements and receipts.

In the Oracle Payments data model, the IBY_TANGIBLE entity represents the physical or logical instrument associated with a payment transaction, such as a check, a payment card, or an electronic funds transfer artifact. IBY_BILL_PKG encapsulates the low-level logic used to persist and update these records, and it is positioned as a building block consumed by higher-level payment transaction packages rather than as a user-facing API. The ETRM metadata classifies the package as an "OTHER" API classification, confirming that it is an internal implementation package rather than a published public API.

Key Procedures and Functions

Two documented program units are exposed by IBY_BILL_PKG:

  • CREATEBILL — Inserts a new bill (tangible) record into the Oracle Payments data store. This procedure is responsible for establishing the initial row in IBY_TANGIBLE and its related sequence-driven key assignment, based on the documented references to IBY_TANGIBLE and IBY_TANGIBLE_S.
  • MODBILL — Modifies an existing bill record. This procedure updates attributes of a previously created tangible, supporting changes such as status transitions, reference updates, or instrument detail corrections during the payment lifecycle.

The documented procedure list is limited to these two units; the metadata does not expose parameter signatures, and none should be assumed. Both procedures are intended for internal invocation by peer packages within the IBY schema.

Tables Accessed

The package references the following tables through APPS synonyms:

  • IBY_TANGIBLE — The primary base table storing payment instrument (tangible) records. Both CREATEBILL and MODBILL operate against this table for insert and update operations.
  • IBY_TANGIBLE_S — The sequence table associated with IBY_TANGIBLE, used to generate the primary key values required when creating new tangible rows.
  • DUAL — The standard Oracle single-row utility table, typically used for sequence-value selection or trivial seed queries within the package code.

Additionally, the documented dependency list shows that the package body references APPS.IBY_TANGIBLE and SYS.STANDARD, confirming reliance on Oracle's built-in STANDARD package for PL/SQL language constructs.

Usage Notes

IBY_BILL_PKG is referenced by six other packages: IBY_FIPAYMENTS_PKG, IBY_FNDCPT_TRXN_PUB, IBY_OFFLINEDB_PKG, IBY_TRANSACTIONCC_PKG, IBY_TRANSACTIONEFT_PKG, and IBY_TRANSACTIONSET_PKG. This dependency pattern demonstrates that the package is invoked indirectly through Oracle Payments' credit card, EFT, funds capture, offline database, and transaction-set processing flows. It is not typically called directly from Oracle Forms or from standard concurrent programs.

Customizations and extensions should avoid direct calls to IBY_BILL_PKG, since it is an internal package with no documented public contract. Integrations requiring payment instrument creation or update should use the supported Oracle Payments public APIs, such as IBY_FNDCPT_TRXN_PUB, which internally composes IBY_BILL_PKG operations. Because the package exists in both 12.1.1 and 12.2.2 with a VALID status, its behavior is consistent across those releases, but customers should treat it as subject to change by Oracle patches without notice.