Search Results delete_billing_assignments

Overview

APPS.PA_BILLING_SETUP_PUB is a public PL/SQL package body in the Oracle Projects (PA) application, responsible for the revenue and billing configuration of a project as defined on the project setup and billing setup forms. The package encapsulates the business logic that governs how a project accrues revenue, generates invoices, and routes invoice distributions to credit receivers and billing assignments. Because it is classified as a PUB (public) API, it constitutes a supported integration point: Oracle EBS development standards permit external callers such as forms, concurrent programs, and custom extensions to invoke its procedures directly, rather than writing to the underlying project setup tables. The header comment attribute dates the original creation to 2001, with later revisions, confirming the package as a long-standing component of the Project Billing module. It sits within the Project Billing family of public APIs and is used to maintain the billing configuration of a project after initial project creation.

Key Procedures and Functions

Seven documented procedures comprise the package interface, and they fall into three functional groups.

• UPDATE_REVENUE_AND_BILLING — Updates the revenue and billing setup attributes of a project. It accepts the billing distribution rule, billing cycle, first bill offset, next billing date, output tax code, billing job group, invoice comment, labor and non-labor billing assignment identifiers, retention invoice format and percentage, and a record version number for optimistic locking. The procedure follows the standard Oracle EBS API parameter convention, including API version, initialization of the message list, commit control, validation-only and validation-level flags, calling module, debug mode, message count limits, and the return status, message count, and message data output parameters.
• CREATE_CREDIT_RECEIVERS, UPDATE_CREDIT_RECEIVERS, DELETE_CREDIT_RECEIVERS — Maintain the credit receiver definitions associated with a project. A credit receiver identifies the party or employee who receives credit for revenue or billing amounts generated by the project. The create procedure establishes new credit receiver records, the update procedure modifies existing credit receivers, and the delete procedure removes them.
• CREATE_BILLING_ASSIGNMENTS, UPDATE_BILLING_ASSIGNMENTS, DELETE_BILLING_ASSIGNMENTS — Maintain billing assignments, which determine how labor and non-labor expenditures are assigned to a billing configuration. The create procedure adds assignment definitions, the update procedure changes existing assignments, and the delete procedure removes assignments that are no longer required.

Tables Accessed

The documented table reference is PA_PROJECTS_ALL, accessed through an APPS synonym. This is the base project table that stores project identifying information and the project-level setup used as the parent context for revenue and billing configuration. The package reads and writes project setup data through the standard Oracle Projects public API layer, and its procedures operate against the project identified by the project parameter passed by the caller. The procedures additionally maintain the child records for credit receivers and billing assignments that are associated with the project. Because the object is a public API, direct DML against the base tables is not the supported access path; the package is the sanctioned interface for maintaining this configuration data.

Usage Notes

PA_BILLING_SETUP_PUB is invoked from the Project Billing setup user interface in Oracle Projects, where it populates and validates the revenue and billing fields presented to the user. Custom integration code may call the procedures to create or maintain project billing configuration programmatically during project creation or maintenance. The API follows the standard Oracle EBS public API contract: callers should first call FND_API.G_TRUE (or FND_MSG_PUB.initialize) for the initialization message list, then process the return status and message stack after each call. Validation-only mode allows a caller to verify input without committing changes. Because the package is referenced by zero other packages, its procedures are not nested dependencies invoked internally by other Oracle Project Billing PL/SQL units; they are intended for external callers, whether forms, concurrent programs, or custom code. Developers should treat the documented procedures as the supported interface and avoid modifying the source package, using API hooks or wrapping custom logic around these entry points instead.