Oracle Project Public API - Project Billing Events

Package Name: Project Billing Events
Internal Name: PA_EVENT_PUB
Description: This package contains the public AMG APIs which provide an open interface for external systems to insert, update and delete events.
APIs (Functions and Procedures):

Name
Internal Name
Description
Create Billing Event
CREATE_EVENT
This API creates an event or a set of events.
Create Multiple Billing Events – Clear
CLEAR_EVENT
This API clears the globals that were set up during initialization.
Create Multiple Billing Events - Execute Create
EXECUTE_CREATE_EVENT
This API creates an event using the data which is stored in the global tables during the Load phase In order to execute this API the following list of API's should be executed in the order of sequence.
Create Multiple Billing Events – Fetch
FETCH_EVENT
This API gets the return status that was returned during creation of an event and stored in a global PL/SQL table.
Create Multiple Billing Events – Load
LOAD_EVENT
This API loads an event to a PL/SQL record.
Create Multiple Billing Events-Initialize
INIT_EVENT
This API sets the global tables used by the Load Execute Fetch procedures that create a new event or update an existing event.
Delete Billing Event
DELETE_EVENT
This API deletes an event.
Update Billing Event
UPDATE_EVENT
This API updates an event or set of events.
Update Multiple Billing Events-Update
EXECUTE_UPDATE_EVENT
This API updates event data using the information stored in the global tables during the Load phase.
Validate Billing Event Deletion
CHECK_DELETE_EVENT_OK
This API checks whether an event can be deleted.

Project Period Closure

Project Period Closure

The steps to be followed for PA period clsoure,

1. Clear all the transactions from Interface tables
2. Import them
3. Run all the Expenditures (PRC, Interface processes) make sure none of the expenditures are not accounted
4. Run Borrow and Lent process if any, Transfer to GL
5. Run Revenue Process, make sure revenue is generated, accounted
6. Review the revenue draft versions created, make sure all revenue draft versions are released
7. INterface revenue to GL, then later Tie back process
8. Run the Invoicing process
9. Make sure to Approve, release all the Invoices in draft version
10. Interface to AR ( ensure that none of the records are in error)
11. Auto Invoice Import in AR
12. Tieback process in PA
13. Run Exc: Transaction Exception details by GL Period/ PA period , Exc: Transaction Exception summary by GL Period/ PA Period
14. Make sure the report output on step 13 are blank, if yes try to clear all the transactions and re run the reports
15. Now try closing the period

Oracle Project Interfaces

Name
Internal Name
Description
PRC: Interface Assets to Oracle Assets
PAXCPCAL
The Interface Assets process sends valid asset lines to Oracle Assets to become fixed assets. The process creates one mass addition line in Oracle Assets for each asset line in Oracle Projects, assigning the asset information you entered for the CIP asset to the mass addition line in Oracle Assets. Interface the costs to General Ledger before you run the Interface Assets process.
PRC: Interface Cross Charge Distributions to General Ledger
PACCGLTR
The process identifies the cross charged transactions that fit the parameters you specify and then interfaces the cross charged distributions to General Ledger
PRC: Interface Expense Reports from Payables
PAAPIMP
This process gets expense report information from Payables. This process creates pre- approved expense report batches from expense report information entered in Self-Service Expenses or in the invoices window (in payables).
PRC: Interface Expense Reports to Payables
PATTER
The Interface Expense Reports to Payables process collects all eligible expense reports, including adjustments, in Oracle Projects and interfaces them to the Oracle Payables interface tables.
PRC: Interface Intercompany Invoices to Receivables
PATTAR-IC
This process collects all eligible intercompany invoices in Oracle Projects and interfaces them to the Oracle Receivables interface tables.
PRC: Interface Invoices to Receivables
PATTAR
This process collects all eligible draft invoices in Oracle Projects and interfaces them to the Oracle Receivables interface tables. The process also maintains the project balances of unbilled receivable and unearned revenue and creates accounting transactions for these amounts.
PRC: Interface Labor Costs to General Ledger
PAGGLT
This process collects all eligible labor costs in Oracle Projects and interfaces them to the Oracle General Ledger interface tables. The interface process also determines the liability account for the labor costs.
PRC: Interface Revenue to General Ledger
PATTGL
This process collects all eligible revenue in Oracle Projects and interfaces it to the Oracle General Ledger interface tables. This process also maintains project balances for unbilled receivables and unearned revenue and creates accounting transactions for these amounts.
PRC: Interface Supplier Costs
PAAPIMP_SI
The PRC: Interface Supplier Invoices from Payables process retrieves the following items and interface them to Oracle Projects: All eligible posted, project related supplier invoices from Oracle Payables, Tax lines for project related intercompany invoices. The process first populates the Transaction Import Interface table, creating a cost distributed expenditure item and cost distribution line for each invoice distribution line, and expenditure for each invoice.
PRC: Interface Supplier Invoice Adjustment Costs to Payables
PAVTVC
This process collects all eligible supplier invoice adjustment costs in Oracle Projects and interfaces them to Oracle Payables. The process determines the liability account for the supplier invoice costs.
PRC: Interface Total Burdened Cost to GL
PACTFTBC
This process collects all eligible total burdened distribution lines in Oracle Projects and interfaces them to Oracle General Ledger.
PRC: Interface Usage and Miscellaneous Costs to General Ledger
PASGLT
This process collects all eligible cost distribution lines of the following transactions in Oracle Projects and interfaces them to the Oracle General Ledger interface tables: usage costs, miscellaneous transaction costs, burden transaction costs, and Inventory and WIP transactions not already costed or accounted. The interface process also determines the liability account for these costs.
PRC: Transaction Import
PAXTRTRX
Transaction Import is an open interface that enables you to load transactions from external cost collection systems into Oracle Projects. Transaction Import creates pre-approved expenditure items from transaction data entered in external cost collection systems.

Oracle Project Tables

Table Name
Description
PA_PROJECTS_ALL
 Information about projects
PA_AGREEMENTS_ALL
 Customer contracts that serve as the basis for work authorization
PA_BILL_RATES_ALL 
Information about bill rates and markups of standard bill rate schedules
PA_BILLING_ASSIGNMENTS_ALL 
Assignments of billing extensions to a project type, project, or task
PA_COST_DISTRIBUTION_LINES_ALL
 Information about expenditure item cost distribution
PA_CUST_REV_DIST_LINES_ALL 
Information about expenditure item revenue distribution
PA_DRAFT_INVOICE_DETAILS_ALL
 Intercompany invoice details for cross charged transactions
PA_DRAFT_INVOICES_ALL 
Information about draft invoices generated for projects
PA_DRAFT_REVENUES_ALL
 Information about draft revenue generated for projects
PA_EXPENDITURE_COST_RATES_ALL 
Cost rates for non-labor expenditure types
PA_EXPENDITURE_GROUPS_ALL
 Groups of pre-approved expenditures
PA_EXPENDITURE_ITEMS_ALL 
The smallest units of expenditure charged to projects and tasks
PA_EXPENDITURES_ALL 
Groups of expenditure items incurred by employees or organizations for an expenditure period
PA_PERIODS_ALL 
Implementation-defined periods against which project performance is measured
PA_PROJECT_ASSET_LINES_ALL 
Summarized project CIP costs
PA_PROJECT_ASSETS_ALL
 Assets defined for capital projects
PA_EXPENDITURE_TYPES 
Implementation-defined classifications of expenditures charged to projects and tasks
PA_EXPENDITURE_CATEGORIES 
Implementation-defined groupings of expenditure types by type of cost
PA_CLASS_CATEGORIES
 Implementation-defined categories for classifying projects
PA_CLASS_CODES 
Implementation-defined values within class categories that can be used to classify projects
PA_PROJECT_CLASSES 
Class codes of class categories that are used to classify projects
PA_BUDGET_VERSIONS 
Versions of project budgets
PA_BUDGET_LINES 
Detail lines

Change of Person Types

To change Person Type of the existing employee.

Navigation : People > Enter and Maintain > Others > Person Type Usage
Select the required person type to be changed.

Note: The person type change is limited to any of the user person types corresponding to the system person type effective on the date of change.

User Person Types are defined, as part of setup activity : Other Definitions > Person Types