PA Event Upload – Oracle EBS SQL Report

Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™.

Overview

PA Event Upload =================== This upload can be used to create new Project Billing and Revenue Events against the Projects belonging to the Operating Units accessible to the current responsibility.

If the Operating Unit parameter is specified, then the upload will be restricted to Projects within the specified Operating Unit only.

Run this report in Excel in seconds: download Blitz Report™ free (your first 30 reports are free) or try it in the online demo.

Report Parameters

Product Source, Operating Unit, Default Event Date, Validate DFF Attributes

Oracle EBS Tables Used

mtl_parameters, mtl_system_items_vl, pa_proj_elements, pa_events, pa_projects, pa_tasks, hr_all_organization_units_vl, pa_all_organizations, pa_event_types, pa_agreements, pa_customers_v, pa_conversion_types_v, mo_glob_org_access_tmp, dual

Report Categories

Enginatics, Upload

GL Account Analysis, GL Account Analysis (Drilldown) (with inventory and WIP), GL Account Distribution Analysis, AP Invoices and Lines, ONT Order Upload, PO Headers and Lines, AP Invoice Upload

Running This SQL Without Blitz Report

The SQL source can be run in any SQL client. Some Oracle EBS SQL reports in this library use functions from the utility package xxen_util – install it first. Blitz Report™ adds parameters, Excel output with pivots, scheduling and security on top.

Download & Import Options

Resource Link
Excel Example Output Example
Blitz Report™ XML Import PA_Event_Upload.xml
SQL Source PA Event Upload.sql
Full Report on Enginatics www.enginatics.com/reports/pa-event-upload/

Case Study & Technical Analysis: PA Event Upload

Executive Summary

This upload creates new Project Billing and Revenue Events against the projects of the operating units that the current responsibility can access. Project accountants and billing teams use it to load milestone, billing and revenue events in bulk, so that the events carry the billing amounts, currencies, exchange rates, holds and references that drive project billing and revenue recognition. The download shows existing events, and the file is worked in Excel through Blitz Report™.

Business Challenge

The Solution

Technical Architecture (High Level)

Primary Tables

Logical Relationships

  1. Each event is joined to its project, and the project’s operating unit is checked against the accessible operating units.
  2. The event’s task is outer-joined, because an event can be recorded at project level.
  3. The expenditure organization of the event is matched to an expenditure organization in the operating unit, and its name is taken from the organization view.
  4. The agreement and customer are outer-joined, so events without an agreement are still listed.
  5. The projected, project and funding rate types are outer-joined to the conversion types to give readable names.
  6. Deliverable and action names are read from the project element table with the object type of each.

Parameters & Filtering

Performance & Optimization

FAQ

Q: Which projects can receive events in this upload? A: Only projects in the operating units that the current responsibility can access, and, when the Operating Unit parameter is entered, only projects in that unit.

Q: Can an event be created without a task? A: Yes, the task join is an outer join, so an event can be recorded against the project alone.

Q: Which currencies and rates does an event carry? A: An event carries the transaction currency and bill and revenue amounts, and the functional, project and funding currency rates with their rate types and rate dates.

© Enginatics GmbH