Search Results validate_complete_br




Overview
Explore in AI Chat

Overview

AR_BILLS_MAINTAIN_VAL_PVT is an internal Oracle Receivables validation package that encapsulates the business-rule checks applied to bills receivable (BR) transactions during their lifecycle. In Oracle EBS, a "bill receivable" is a customer transaction that has been remitted to a bank and accepted as a negotiable instrument, progressing through states such as complete, accepted, unpaid, and cancelled. Before any such state transition is committed, Receivables must confirm that dates, references, and relationships are consistent with system parameters and transaction history. This package is the private (PVT classification) home for those validations.

The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user and is intended purely as an internal, subordinate utility rather than a public API. It is invoked by the Receivables transaction maintenance logic and by two other packages documented in the ETRM, which call into these validation routines before performing updates.

Key Procedures and Functions

The package exposes nine documented procedures, all of which are validators (none return a value; failures are raised as exceptions):

  • VALIDATE_COMPLETE_BR — Verifies that a bill receivable may be moved to the completed state, accepting the transaction record and a GL date for evaluation.
  • VALIDATE_ACCEPT_BR — Confirms that a completed bill receivable may be accepted, reconciling the transaction record against transaction history.
  • VALIDATE_CANCEL_BR — Checks whether a bill receivable identified by its transaction ID is eligible for cancellation.
  • VALIDATE_UNPAID_BR — Validates a request to mark a bill receivable as unpaid, using the transaction history record and a reason code.
  • VALIDATE_PAYMENT_SCHEDULE_ID — Confirms that a supplied payment schedule identifier exists and is valid for the intended operation.
  • VALIDATE_REMIT_BATCH_ID — Validates a remittance batch identifier, ensuring that the referenced AR_BATCHES record is legitimate and usable for the remittance. This is the routine surfaced when searching for "validate_remit_batch_id".
  • VALIDATE_ADJ_ACTIVITY_ID — Verifies that a given adjustment activity reference is valid.
  • VALIDATE_ACTION_DATES — Performs date-sequencing checks across the transaction date, GL date, and action, guarding against postings outside permitted accounting periods.
  • VALIDATE_REMITTANCE_DATES — Validates dates associated with a specific remittance, comparing the batch record, transaction history, and transaction number.

Tables Accessed

The validations read from a defined set of Receivables and Trading Community tables through APPS synonyms: AR_BATCHES (remittance batch definition), AR_TRANSACTION_HISTORY and AR_TRANSACTION_HISTORY_ALL (state-change audit trail), RA_CUSTOMER_TRX and RA_CUSTOMER_TRX_LINES (transaction header and lines), AR_PAYMENT_SCHEDULES (installments used in acceptance and cancellation logic), AR_RECEIVABLES_TRX (receivables activities such as adjustments and remittances), AR_SYSTEM_PARAMETERS (profile-like system configuration used for date and status rules), and the HZ_CUST_ACCOUNTS / HZ_CUST_ACCT_RELATE tables (customer account identity and relationships). The package is predominantly read-oriented; state changes are applied by its callers.

Usage Notes

Because the package is classified PVT, Oracle does not document it as a supported integration point, and direct invocation from custom code should be avoided; the supported route is through Receivables forms and the public APIs that call it. In practice it is triggered from the Bills Receivable windows and related concurrent programs whenever a user completes, accepts, marks unpaid, cancels, or remits a bill receivable. The presence of the Remittance Dates and Remit Batch ID validators reflects their use during remittance creation and reconciliation.