Search Results get_default_term




Overview
Explore in AI Chat

Overview

AR_BFB_UTILS_PVT is an internal Oracle E-Business Suite PL/SQL utility package owned by the APPS schema. The "PVT" suffix indicates that it is a private package, meaning its procedures and functions are not intended to be called directly by external consumers, forms, or third-party integrations. Instead, it functions as a shared internal library that supports the "Bill for Bill" (BFB) and consolidated billing functionality within Oracle Receivables. The package encapsulates the logic required to determine billing dates, billing cycles, payment terms, and bill levels for consolidated invoicing transactions. In the context of Oracle EBS 12.1.1 and 12.2.2, AR_BFB_UTILS_PVT serves as a foundational layer beneath public APIs such as ARP_BF_BILL and AR_INVOICE_UTILS, providing reusable validation and defaulting routines that those higher-level programs invoke during consolidated billing transaction processing.

Key Procedures and Functions

The documented package exposes thirteen procedures and functions that collectively address billing cycle and payment term defaulting, validation, and record population. The key routines include:

  • GET_BILLING_DATE — Determines the appropriate billing date for a consolidated bill transaction.
  • GET_BILL_PROCESS_DATE — Retrieves the date on which billing processing occurs for the transaction.
  • GET_DUE_DATE — Derives the due date based on payment terms and billing parameters.
  • IS_PAYMENT_TERM_BFB — Validates whether a given payment term is configured for Bill for Bill processing.
  • GET_BILL_LEVEL — Returns the billing level applicable to the transaction, governing consolidation behavior.
  • GET_BILLING_CYCLE — Fetches the billing cycle associated with a customer or site.
  • IS_VALID_BILLING_DATE — Validates whether a proposed billing date conforms to the assigned cycle.
  • GET_CYCLE_TYPE — Returns the type of billing cycle in effect.
  • GET_OPEN_REC — Retrieves open receivable records relevant to the consolidated bill.
  • GET_DEFAULT_TERM — Derives the default payment term for the transaction context.
  • VALIDATE_AND_DEFAULT_TERM — Validates and applies a default payment term when none is supplied.
  • POPULATE — Populates a record or collection structure with the computed billing attributes.

These routines are invoked together to compute the billing attributes required before an invoice is generated under consolidated billing rules.

Tables Accessed

The package reads from and writes to several core Receivables and Trading Community tables via APPS synonyms. Billing cycle configuration is sourced from AR_CONS_BILL_CYCLES_B and AR_CONS_BILL_CYCLE_DATES. Customer and site-level billing attributes are read from HZ_CUSTOMER_PROFILES and HZ_CUST_SITE_USES. Transaction data is accessed through RA_CUSTOMER_TRX, RA_CUSTOMER_TRX_ALL, and RA_CUSTOMER_TRX_LINES. Transaction types are validated against RA_CUST_TRX_TYPES. Payment term logic references RA_TERMS, RA_TERMS_B, and RA_TERMS_LINES. Error handling uses RA_INTERFACE_ERRORS and FND_NEW_MESSAGES, while DUAL and PLITBLM support minor procedural operations. These accesses confirm the package's role in validating and defaulting billing attributes prior to invoice creation.

Usage Notes

AR_BFB_UTILS_PVT is not a public API and should not be invoked directly from custom code, forms, or concurrent programs. Instead, it is referenced internally by ARP_BF_BILL, ARP_TRX_DEFAULTS_3, AR_INVOICE_UTILS, and by itself. Consolidated billing and Bill for Bill processing in Oracle Receivables trigger these routines when invoice records are defaulted and validated. Customizations requiring changes to billing date, cycle, or payment term defaulting for consolidated billing must be implemented through supported public APIs or via personalization, not by modifying or calling this private package. Direct use risks incompatibility during patching or upgrades between 12.1.1 and 12.2.2, since private package signatures may change without notice.