Search Results matured_pend_risk_elimination

Overview

AR_BILLS_MAIN is the PL/SQL package body that powers the Oracle Receivables Bills Receivable (BR) functionality within Oracle E-Business Suite 12.1.1 and 12.2.2. The package encapsulates the server-side logic required to create, load, query, and manage bills receivable records and their associated remittance assignments. Its header comment ($Header: ARBRCOMB.pls 120.10.12010000.3) reflects a shipping release line, and the source has been maintained continuously since 2000, indicating its role as a long-standing foundational component of the Receivables Bills Receivable feature set.

Within the ETRM classification, AR_BILLS_MAIN is categorized as an OTHER API. It is not a bulk business-object API exposed through a formal PL/SQL interface; instead it functions primarily as a server-side supporting package invoked by the Bills Receivable forms, by the underlying application logic, and by other packages. The documented metadata identifies two dependent packages that reference it, confirming its position as a callable utility layer.

Key Procedures and Functions

The documented metadata defines twelve procedures and functions within the package body:

• LOAD_TABLE — Populates an internal/in-memory table structure used by the Bills Receivable form, typically to drive a multi-record block or a list of values.
• GET_ALL_ITEMS — Retrieves the full set of bills receivable items relevant to the current query context.
• GET_ALL_ITEMS_STATUS — Returns the status information associated with the retrieved items.
• BR_SEQ_ENTERABLE — Determines whether the document sequence field is enterable for the bills receivable record.
• BR_POSTED — Establishes whether a bill receivable has been posted.
• BR_SELECTED — Indicates whether a bill receivable has been selected in the current transaction context.
• FETCH_ASSIGNMENTS — Retrieves remittance assignments associated with a bill receivable.
• GTRUE / GFALSE — Helper functions that return the FND_API constants G_TRUE and G_FALSE respectively.
• GET_FND_API_CONSTANTS_REC — Relays FND_API constants to client-side Forms and libraries, which cannot directly reference PL/SQL package global variables.
• GET_FND_MSG_PUB_CONSTANTS_REC — Relays FND_MSG_PUB constants to the client side for the same reason.
• REVISION — Returns the package revision identifier.

Tables Accessed

The package reads and writes against a broad set of Receivables and Trading Community tables accessed through APPS synonyms:

• AR_CONS_INV / AR_CONS_INV_ALL — Consolidated billing invoice tables underpinning bills receivable creation.
• RA_CUSTOMER_TRX / RA_CUSTOMER_TRX_LINES / RA_CUST_TRX_TYPES — Transaction and transaction-type definitions for bills receivable documents.
• AR_PAYMENT_SCHEDULES / AR_RECEIPT_METHODS / AR_BATCHES / AR_TRANSACTION_HISTORY — Core Receivables payment, receipt, batch, and audit history data.
• HZ_CUST_ACCOUNTS / HZ_CUST_SITE_USES / HZ_PARTIES — Customer and party information for the remitting and drawee parties.
• AP_BANK_ACCOUNTS — Bank account data used when validating or selecting remittance bank information.
• FND_DOCUMENT_SEQUENCES — Supports the sequence-enterability check (BR_SEQ_ENTERABLE).
• PLITBLM — The standard Oracle Forms PL/SQL table structure used to pass item lists between server and client.

Usage Notes

AR_BILLS_MAIN is invoked primarily from Oracle Forms-based Bills Receivable windows and from supporting Receivables packages. Its constants-relay functions (GET_FND_API_CONSTANTS_REC, GET_FND_MSG_PUB_CONSTANTS_REC, GTRUE, GFALSE) exist specifically because Forms libraries cannot reference package globals directly. When introducing custom code, developers should treat AR_BILLS_MAIN as a supporting internal package: it is not part of the documented public API surface, and it should be extended only through supported customizations or by calling its documented procedures from custom forms logic. Because the package operates on open Receivables transaction data, it should be invoked within a properly initialized Forms session or a session where FND_PROFILE, FND_API, and FND_MSG_PUB are available, and changes should be tested against both 12.1.1 and 12.2.2 since the source line spans release boundaries.