Search Results validate_gl_date

Overview

AR_BILLS_CREATION_VAL_PVT is a private validation package in the Oracle Receivables (AR) module of Oracle E-Business Suite. It is owned by the APPS schema and declared with AUTHID CURRENT_USER, meaning its procedures execute with the privileges of the calling user rather than the definer. As its name implies, the package supports the Bills Receivable creation flow, providing the centralized validation logic invoked when a transaction is created or updated as a Bills Receivable (BR). The package encapsulates checks against GL dates, transaction headers, transaction lines, assignments, and BR status, allowing the surrounding Bills Receivable APIs and forms to enforce business rules before committing data. It is classified as a PVT (private) interface in ETRM, so it is not intended for direct customer invocation; it is consumed internally by the Bills Receivable formation logic and is referenced by four other packages.

Key Procedures and Functions

The package exposes nine documented procedures and functions:

• VALIDATE_GL_DATE — Validates the accounting (GL) date supplied for the Bills Receivable transaction, ensuring it falls within an open accounting period and conforms to AR date-validation rules. This is the object most directly associated with the search term "validate_gl_date".
• VALIDATE_CREATE_BR_HEADER — Performs header-level validations required when a new Bills Receivable transaction header is being created.
• VALIDATE_UPDATE_BR_HEADER — Performs the equivalent validations when an existing BR transaction header is being updated.
• VALIDATE_BR_ASSIGNMENT — Validates the assignment of a Bills Receivable to a transaction line and payment schedule, checking the linkage between line and BR records.
• VALIDATE_CUSTOMER_TRX_ID — Confirms that a given customer transaction identifier is valid and usable in the BR context.
• VALIDATE_CUSTOMER_TRX_LINE_ID — Confirms that a given customer transaction line identifier is valid.
• VALIDATE_BR_STATUS — Checks the current status of a Bills Receivable transaction to ensure it permits the requested operation.
• IS_TRANSACTION_BR — A Boolean function that determines whether a given transaction type is a Bills Receivable type.
• VALIDATE_ASSIGNMENT_STATUS — Validates the assignment status for a transaction, keyed by customer transaction and transaction number.

Parameter lists are intentionally not reproduced here; the purposes above reflect the documented signatures.

Tables Accessed

The package references the following tables through APPS synonyms:

• RA_CUSTOMER_TRX and RA_CUSTOMER_TRX_LINES — transaction header and line data used for header, line, and assignment validation.
• AR_PAYMENT_SCHEDULES — payment schedule records linked to BR assignments.
• AR_TRANSACTION_HISTORY — status and history checks for BR transactions.
• RA_CUST_TRX_TYPES — used by IS_TRANSACTION_BR to identify Bills Receivable transaction types.
• RA_BATCHES and RA_BATCH_SOURCES — batch context for BR creation.
• CE_BANK_ACCOUNTS, HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, and HZ_CUST_SITE_USES — customer, site, and bank account validation supporting the BR assignment and header checks.

Usage Notes

Because AR_BILLS_CREATION_VAL_PVT is a private package, it is not called directly from custom code or from the standard Receivables forms. Instead, it is invoked internally by the Bills Receivable creation and update logic, and its validations surface to users as errors or warnings within the Receivables transaction and BR forms and through the corresponding concurrent programs. Developers investigating GL date errors in a Bills Receivable context should trace calls into VALIDATE_GL_DATE to understand the date and period checks applied. Customizations that bypass the standard BR APIs and attempt direct inserts into RA_CUSTOMER_TRX or RA_CUSTOMER_TRX_LINES will not automatically run these validations, which is a common source of inconsistent data; the recommended approach is to use the supported Bills Receivable APIs so that this package and its sibling validation routines execute as designed.