Search Results delete_br_trxn_extension

Overview

AR_BILLS_CREATION_PUB is a public PL/SQL API package owned by the APPS schema that supports the Oracle Receivables "Bills Receivable" (BR) functionality in Oracle E-Business Suite 12.1.1 and 12.2.2. Bills Receivable allow an organization to draw a negotiable instrument against a customer's outstanding transactions, track that instrument through its lifecycle (remittance, discounting, factoring, protest, and settlement), and manage its accounting impact. This package exposes the transactional entry points through which callers create, modify, lock, and delete bill headers and their associated assignments, and through which revision records and transaction extension rows are maintained. The package is classified as a public (PUB) API, meaning it is intended to be called from outside the Receivables product — including from Oracle forms, concurrent programs, and customer-written extensions.

Key Procedures and Functions

The package defines twelve documented procedures that fall into four logical groups.

• Header operations: CREATE_BR_HEADER, UPDATE_BR_HEADER, DELETE_BR_HEADER, and LOCK_BR_HEADER manage the bill header record itself — the instrument that identifies the bill, its customer, currency, amount, and status. LOCK_BR_HEADER provides the concurrency guard that prevents conflicting updates to the same header.
• Assignment operations: CREATE_BR_ASSIGNMENT, UPDATE_BR_ASSIGNMENT, DELETE_BR_ASSIGNMENT, and LOCK_BR_ASSIGNMENT manage the linkage between a bill and the transactions it draws against, since a single bill header may be assigned to one or more receivables transactions.
• Revision: REVISION handles revision tracking against the bill, capturing changes made over its lifecycle.
• Transaction extension operations: CREATE_BR_TRXN_EXTENSION, UPDATE_BR_TRXN_EXTENSION, and DELETE_BR_TRXN_EXTENSION maintain rows in the transaction extension structure that carries additional bill-related attributes associated with the underlying transactions.

The procedures follow standard Oracle EBS API conventions, returning status and error information through the FND_API error-handling framework rather than raising unhandled exceptions to the caller.

Tables Accessed

Through APPS synonyms, the package operates on the core Receivables tables. AR_PAYMENT_SCHEDULES and RA_CUSTOMER_TRX / RA_CUSTOMER_TRX_LINES supply the transaction and installment data against which bills are drawn and assigned. AR_RECEIPT_METHODS provides the receipt method validation used when a bill is associated with remittance or collection handling. AR_TRANSACTION_HISTORY records the audit trail of transaction-level changes made as bills are created, revised, or removed. The package also depends on the IBY_TRXN_EXTENSIONS_V view and the FND_API package for its extension and error-handling logic.

Usage Notes

AR_BILLS_CREATION_PUB is a lower-level public API rather than an end-user entry point. It is referenced by the package AR_BILLS_CREATION_LIB_PVT, which holds the private implementation logic, and is called by ARP_PROGRAM_GENERATE_BR, the concurrent program that generates bills receivable in bulk. It is also referenced by AR_BILLS_MAINTAIN_PUB, which provides the maintenance-side API used by the Bills Receivable windows in the Receivables forms. Custom code should invoke this package only when standard functionality is insufficient, and should follow the documented API pattern: obtain a lock via the appropriate LOCK procedure, perform the create/update/delete operation, check the returned status, and handle errors through FND_API. Because the procedures rely on the internal validation rules enforced by the Bills Receivable framework, callers must supply properly validated bill and transaction identifiers; bypassing those validations can leave the payment schedules and transaction history inconsistent.