Search Results insert_paevent_table

Overview

EAM_WORKORDERBILLING_PVT is a private PL/SQL package in the Oracle Enterprise Asset Management (EAM) module that supports the billing of maintenance work orders. Its central purpose is to move cost and billing information captured against an EAM work order into the Oracle Receivables (AR) interface tables so that customer charges for performed maintenance work can subsequently be invoiced. The package is classified as a PVT (private) API, meaning it is intended for internal use by other EAM billing components rather than as a supported public integration point. It operates under AUTHID CURRENT_USER, so all unqualified object references resolve to the invoking user's schema and privileges.

In the 12.1.1 and 12.2.2 releases, this package implements the work-order billing flow used when an asset owner or customer is billed for maintenance services. Because the user search term was "work_request," it is worth noting that the package's billing record type explicitly includes a WORK_REQUEST_ID column, tying billed activity back to the originating work request. This makes it relevant when tracing how a work request ultimately produces a receivable.

Key Procedures and Functions

The documented package exposes three procedures:

• INSERT_AR_INTERFACE — Transfers work-order billing records into the Oracle Receivables interface tables. This is the procedure that bridges EAM billing data to AR, preparing invoice lines and related sales credits for import by the standard Receivables AutoInvoice process. Its header comment shows it follows the standard EBS API convention accepting p_api_version, p_init_msg_list, p_commit, and p_validation_level as inputs, and returning x_return_status, x_msg_count, and x_msg_data.
• INSERT_WOB_TABLE — Populates the EAM work-order billing table (EAM_WORK_ORDER_BILLS), persisting the billing detail derived from work-order transactions.
• INSERT_PAEVENT_TABLE — Inserts corresponding records into the Projects Accounting (PA) event structure, associating billing with a project and task where the work is project-related.

The package further declares record types, notably WO_Billing_Rec_Type, which carries organization, customer, bill-to address, WIP entity, operation sequence, inventory item, resource, billed item and UOM, billed quantity, price list header, cost type, list price, cost-plus percentage, billed amount, invoice transaction and line numbers, currency and conversion attributes, project, task, work request, PA event, billing basis, and billing method. A second type, WO_Billing_RA_Rec_Type, carries WIP entity name, invoice number, and line number references.

Tables Accessed

The package reads master and transactional data and writes to the AR interface. Through APPS synonyms it references EAM_WORK_ORDER_BILLS for work-order billing detail; FND_CURRENCIES for currency validation; HR_ORGANIZATION_INFORMATION for organization context; and the HZ customer model (HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_CUSTOMER_PROFILES, HZ_LOCATIONS, HZ_PARTY_SITES) to resolve customer, site, and bill-to information. MTL_UNITS_OF_MEASURE validates billed UOMs. Receivables reference tables RA_BATCH_SOURCES_ALL, RA_TERMS, and RA_TERMS_B supply batch source and payment term defaults, while RA_INTERFACE_LINES_ALL and RA_INTERFACE_SALESCREDITS_ALL receive the generated invoice lines and sales credits for AutoInvoice processing.

Usage Notes

Because EAM_WORKORDERBILLING_PVT is a private package and is referenced by zero other packages in the documented metadata, it is invoked internally by EAM work-order billing logic and underlying EAM concurrent or form-driven processes rather than by external custom code. Billing data flows from completed work orders into the AR interface tables, where the Receivables AutoInvoice concurrent program subsequently creates invoices. Custom integrators seeking a supported entry point should use the public EAM work-order APIs; the PVT package should be treated as internal plumbing. Its behavior depends on correct customer, currency, billing, and project setups being in place before work-order billing is executed.