Search Results rev_bill_inf_req_check

Overview

PA_BILLING_SETUP_UTILS is a public PL/SQL utility package in the Oracle Projects (PA) application schema, classified under the ETRM as an OTHER API type. It consolidates the shared validation and derivation logic that supports the billing setup configuration workflow in Oracle E-Business Suite 12.1.1 and 12.2.2. The package addresses the configuration decisions that must be made before invoices can be generated: which invoice format applies to a project, whether credit receivers and billing assignments have been defined without duplication, and how sales credit and revenue billing characteristics propagate to billing events.

Rather than exposing a business service of its own, PA_BILLING_SETUP_UTILS acts as the internal engine of the billing setup public and private APIs. Dependencies confirm that APPS.PA_BILLING_SETUP_PUB and APPS.PA_BILLING_SETUP_PVT both reference the package body, and the package itself references FND_API for the standard Oracle Applications error-handling framework, including the expected FND_API.G_RET_STS_SUCCESS/ERROR and G_EXC_* conventions used by the calling APIs. This architecture lets forms and concurrent programs call a single public API while the atomic checks remain centrally maintained and reusable.

Key Procedures and Functions

The ETRM documents eleven procedures and functions:

• VALIDATE_RETN_INV_FORMAT — Validates that the retention invoice format configured is compatible with the project's billing setup.
• DUPLICATE_CREDIT_RECEIVERS — Detects duplicate credit receiver definitions so that a receiver is not credited more than once for the same assignment.
• DUPLICATE_BILLING_ASSIGNMENTS — Identifies duplicate billing assignment rows, preventing overlapping or redundant assignment rules.
• VALIDATE_PERSON_ID_NAME — Confirms that a supplied PERSON_ID and the associated person name are consistent and valid.
• GET_NEXT_BILLING_DATE — Derives the next billing date from the billing schedule and related project parameters.
• REV_BILL_INF_REQ_CHECK — Determines whether revenue billing information is required for the billing configuration being processed.
• BILL_XTENSION_REQ_CHECK — Determines whether billing extension information is required.
• VALIDATE_EMP_NO_TO_ID — Validates an employee number against its employee identifier.
• VALIDATE_EMP_NO_NAME — Validates an employee number against the corresponding employee name.
• CREDIT_REC_REQ_CHECK — Checks whether sales credit receiver information is mandatory for the current billing configuration.
• GET_SALES_CREDIT_FLAG — Retrieves the sales credit flag that governs whether sales credit processing applies.

Tables Accessed

Via APPS synonyms, the package reads and writes the following tables:

• PA_BILLING_ASSIGNMENTS_ALL — Billing assignment definitions; read for duplicate detection and maintained as part of setup.
• PA_CREDIT_RECEIVERS — Credit receiver definitions used in duplicate and requirement checks.
• PA_IMPLEMENTATIONS — Implementation-level options that determine whether revenue billing, billing extensions, and sales credit are required.
• PA_INVOICE_FORMATS — Invoice format definitions, including retention invoice formats validated by VALIDATE_RETN_INV_FORMAT.
• PA_PROJECTS_ALL — Project attributes supplying billing context, dates, and customer information.
• RA_BATCH_SOURCES — Receivables batch source definitions referenced during billing setup validation.

Usage Notes

PA_BILLING_SETUP_UTILS is not intended for direct invocation by end users or by custom code. It is invoked indirectly whenever the Billing Setup user interface or the underlying public API performs setup validation. In the standard flow, a form or concurrent program calls APPS.PA_BILLING_SETUP_PUB, which delegates to PA_BILLING_SETUP_PVT, which in turn calls the utility routines described above. The package references FND_API, so error conditions raised by these checks are surfaced as standard Oracle Applications API exceptions and messages.

Customers and integrators extending billing setup should call PA_BILLING_SETUP_PUB rather than this utility package, since the utility routines assume validated input and internal context. Because the routines are called from within the billing setup transaction, any customization should preserve the duplicate-check and requirement-check behaviour to avoid inconsistent billing assignments or credit receiver data. The package is valid and shipped under the APPS schema in both 12.1.1 and 12.2.2; no separate database object or synonym needs to be created for its use.