Search Results validate_desc_flexfield

Overview

AR_BILLS_CREATION_LIB_PVT is a private PL/SQL library package owned by the APPS schema within the Oracle E-Business Suite Receivables (AR) module. Its declared purpose is to support the creation and maintenance of bills receivable (BR), the financial instruments that a customer signs as an acknowledgement of a receivable and that may subsequently be remitted to a bank for financing. The package encapsulates defaulting, assignment, de-assignment, and validation logic that the public Bills Receivable APIs rely upon when they build or modify bill receivable transactions.

The package is declared with AUTHID CURRENT_USER and is classified as a private (PVT) API. This means it is not intended as a supported entry point for external integrations; it is invoked internally by the public APIs and business flows that orchestrate bill receivable creation. The body exposes seven documented program units, all of which are closely tied to the transaction and payment schedule records being manipulated.

Key Procedures and Functions

• Default_Create_BR_Header — Populates default values on a new bill receivable transaction header record (based on ra_customer_trx%ROWTYPE) and the associated GL date during creation.
• Default_Update_BR_Header — Applies defaulting rules to an existing bill receivable transaction header when the record is being updated.
• Default_Create_BR_Assignment — Establishes default values for a bill receivable line assignment, using the transaction line record and the corresponding payment schedule record.
• Default_GL_date — Derives the accounting GL date from an entered date and returns both the dated value and a return status indicator.
• DeAssign_BR — Reverses or removes an existing bill receivable assignment identified by its customer transaction identifier.
• Get_Payment_Schedule_ID — Retrieves the payment schedule identifier associated with a given customer transaction, returning it through an output parameter.
• Validate_Desc_Flexfield — Validates the descriptive flexfield values (attribute category and attributes 1 through 15) against the named descriptive flexfield definition supplied by the caller, and returns the validated values through IN OUT parameters.

The Validate_Desc_Flexfield procedure is the unit most frequently referenced in diagnostic and troubleshooting contexts. It accepts the descriptive flexfield context (attribute category), the fifteen attribute values, and the flexfield name, performing the validation and synchronizing any normalized context values back to the caller.

Tables Accessed

The package operates against core Receivables and Trading Community tables referenced through APPS synonyms:

• RA_CUSTOMER_TRX and RA_CUSTOMER_TRX_LINES — the bill receivable transaction header and line records that are defaulted, validated, and assigned.
• AR_PAYMENT_SCHEDULES — source of payment schedule data and the payment_schedule_id returned by Get_Payment_Schedule_ID.
• RA_CUST_TRX_TYPES — transaction type definitions governing defaulting behavior.
• FND_DESCRIPTIVE_FLEXS — descriptive flexfield metadata used by Validate_Desc_Flexfield.
• HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES, and HZ_ROLE_RESPONSIBILITY — customer account, site, and responsibility context data used during defaulting.
• DUAL — used for single-row lookups and date derivations.

Usage Notes

AR_BILLS_CREATION_LIB_PVT is a private library, so it is not documented for direct customer invocation. It is called by the public Bills Receivable creation and maintenance APIs and by the Receivables forms and concurrent programs that create, assign, or remit bills receivable. Because the package is referenced by five other packages, changes to its signature or behavior can ripple across the bills receivable processing chain.

From a customization perspective, the correct approach is to invoke the public APIs that in turn call this library, rather than calling AR_BILLS_CREATION_LIB_PVT directly. When validating descriptive flexfield values for bills receivable, the Validate_Desc_Flexfield unit mirrors the standard FND flexfield validation performed elsewhere, and defect investigations around flexfield rejections should examine the parameters passed by the calling public API.