Search Results pa_multi_currency_billing




Overview
Explore in AI Chat

Overview

PA_MULTI_CURRENCY_BILLING is a core Oracle Projects package body owned by the APPS schema that supports Multi-Currency Billing (MCB) in Oracle E-Business Suite Releases 12.1.1 and 12.2.2. Multi-Currency Billing enables an operating unit or project to invoice a customer in a currency different from the project's functional or funding currency, and to bill across operating units. The package encapsulates the setup validation, currency determination, and amount conversion logic required by the billing engine to generate invoices under these conditions.

The package is classified as OTHER within the ETRM taxonomy and exposes 21 documented procedures and functions. It delegates cross-functional business rules to companion packages, most notably PA_MULTI_CURRENCY, PA_MCB_REVENUE_PKG, PA_CURRENCY, GL_CURRENCY_API, and the FND API and profile utilities, while concentrating MCB-specific checks and cache management in this body.

Key Procedures and Functions

Tables Accessed

The package reads setup and transactional data through APPS synonyms. Setup data is drawn from PA_IMPLEMENTATIONS_ALL and PA_IMPLEMENTATIONS, PA_PROJECTS_ALL and PA_PROJECTS, PA_PROJECT_TYPES, PA_AGREEMENTS, PA_BILLING_ASSIGNMENTS, PA_PROJECT_CUSTOMERS, PA_PROJECT_FUNDINGS, and PA_SUMMARY_PROJECT_FUNDINGS. Currency reference data comes from FND_CURRENCIES via GL_CURRENCY_API. Rate override tables consulted include PA_STD_BILL_RATE_SCHEDULES, PA_STD_BILL_RATE_SCHEDULES_ALL, PA_EMP_BILL_RATE_OVERRIDES, PA_JOB_BILL_RATE_OVERRIDES, and PA_NL_BILL_RATE_OVERRIDES. Transactional billing data is read from PA_EVENTS, PA_EXPENDITURE_ITEMS_ALL, and PA_DRAFT_INVOICES_ALL. DUAL supports standalone arithmetic and validation queries.

Usage Notes

PA_MULTI_CURRENCY_BILLING is primarily invoked by the Oracle Projects billing engine during invoice generation rather than directly by end users; it is referenced by 23 other database objects and does not itself reference higher-level modules. It executes within the context of the Generate Draft Invoices concurrent program and related billing workflows, and forms such as project and operating unit setup screens rely on its flag and setup validation routines to enforce MCB configuration rules. Custom extensions should call the public APIs rather than manipulating the underlying tables, observing the FND_MSG_PUB error-stack convention. Because the package is documented as VALID in both 12.1.1 and 12.2.2, its interface is stable across those releases.