Search Results br_selected

Overview

AR_BILLS_MAIN is an Oracle Receivables PL/SQL package that supports the Bills Receivable (BR) feature set within Oracle E-Business Suite 12.1.1 and 12.2.2. The package is owned by APPS and classified as an "OTHER" API, meaning it is not a formally published public API but is instead an internal implementation package consumed by the Receivables forms and supporting libraries. Its header comment ($Header: ARBRCOMS.pls 120.3 2005/06/02) and the developer note dated 12-AUG-2000 confirm its origin as part of the original Bills Receivable implementation, and its principal design purpose is to relay server-side package global constants and utility logic to client-side Forms code that cannot reference PL/SQL globals directly.

Accordingly, AR_BILLS_MAIN exposes record types such as FND_API_CONSTANTS_TYPE, FND_MSG_PUB_CONSTANTS_TYPE, and the DISALLOWEDRECTYP/DISALLOWEDTABTYP structures, together with functions that return those constants to the form layer. In practice the package functions as a shared service layer for Bills Receivable transaction handling, item selection and validation, sequence control, and assignment lookups used during bill creation, acceptance, and remittance processing.

Key Procedures and Functions

• LOAD_TABLE — Populates an internal PL/SQL table structure, typically supporting the disallowed-item and lookup tables used by the Bills Receivable forms.
• GET_ALL_ITEMS — Returns the collection of items eligible for a Bills Receivable transaction; this is the routine most commonly searched for by developers investigating item selection behavior.
• GET_ALL_ITEMS_STATUS — Returns the corresponding status of the items retrieved by GET_ALL_ITEMS, enabling the form to enable, disable, or flag selections.
• BR_SEQ_ENTERABLE — Determines whether the bill sequence field should be enterable, based on document sequence setup and transaction context.
• BR_POSTED — Indicates whether a Bills Receivable record has been posted, gating further maintenance actions.
• BR_SELECTED — Indicates whether a bill has been selected within the current processing context.
• FETCH_ASSIGNMENTS — Retrieves assignment rows associated with the bill, used to display and validate assignment information.
• GTRUE / GFALSE — Utility functions returning the canonical Boolean character values used throughout the BR form logic.
• GET_FND_API_CONSTANTS_REC — Returns the FND_API_CONSTANTS_TYPE record so client-side code can compare against FND_API global values.
• GET_FND_MSG_PUB_CONSTANTS_REC — Returns the FND_MSG_PUB_CONSTANTS_TYPE record to relay messaging constants to the form.
• REVISION — Returns the package version or revision identifier.

Tables Accessed

The package reads and writes data through APPS synonyms. Bills Receivable records themselves are held in AR_CONS_INV and AR_CONS_INV_ALL, with AR_PAYMENT_SCHEDULES supplying installment and due-date information. Customer and site context comes from HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES, and HZ_PARTIES. Transaction detail is drawn from RA_CUSTOMER_TRX, RA_CUSTOMER_TRX_LINES, and RA_CUST_TRX_TYPES. Remittance and banking data are sourced from AP_BANK_ACCOUNTS, AR_RECEIPT_METHODS, and AR_BATCHES, while AR_TRANSACTION_HISTORY provides audit history. Document sequence control relies on FND_DOCUMENT_SEQUENCES, and PLITBLM is used for the PL/SQL table backing store.

Usage Notes

AR_BILLS_MAIN is typically invoked from the Bills Receivable forms and their attached libraries rather than from concurrent programs. The constant-relay functions (GET_FND_API_CONSTANTS_REC and GET_FND_MSG_PUB_CONSTANTS_REC) are called during form initialization so that client-side validation and messaging mirror the server-side FND_API and FND_MSG_PUB values. The item-related routines (GET_ALL_ITEMS, GET_ALL_ITEMS_STATUS) are called as the user populates item selections in the transaction window. Custom code should treat the package as an internal, non-public API: signatures may change between point releases, and Oracle does not guarantee backward compatibility. Where customizations require Bills Receivable logic, the supported approach is to call the corresponding public Receivables APIs, such as AR_RECEIPT_API_PUB or the documented Bills Receivable APIs, rather than invoking AR_BILLS_MAIN directly. The package is referenced by two other packages in the E-Business Suite codebase, confirming its role as a shared internal dependency for Bills Receivable processing.