PA: Integration with Financial

Modules

Contents

Integration Overview
General Ledger
Purchasing
Accounts Payable
Accounts Receivable
Fixed Assets

Integration Overview

This presentation discusses the basic concepts of integrating Oracle Projects (PA) with
five other Oracle Financials modules, namely Oracle General Ledger (GL), Oracle
Purchasing (PO), Oracle Payables (AP), Oracle Receivables (AR) and Oracle Fixed
Assets (FA).
It aims to explain the integration points under the following broad heads:
the flow of data across the integration point;
the set up parameters necessary to enable inter-module integration; and,
the required concurrent manager processes to push or pull data across these
integration points.

Integration With Oracle General Ledger

PA collects detailed project cost and revenue. These costs are distributed to valid
accounts in the chart of accounts defined in the GL. PA uses AutoAccounting and
Flexbuilder features to derive these accounts. Once distributed, PA transactions are then
summarized and transferred into the journal import table. The journal import process
posts these transactions to the general ledger. The tieback costs and revenue process
in PA verifies that these costs and revenues were posted to valid account code
combinations in the general ledger.
Data Flow
Oracle predefines a journal source and several journal categories for this integration.
The journal source is called Projects and the journal categories are as follows:
Labor Cost;
Burden Cost
Total Burdened Cost;
Usage Cost; and,
Revenue.

Integration With Oracle General Ledger

Setup parameters Project Accounting
(N) Setup>System>Implementation Options>Expnd/Costing (Tab Page)

Integration With Oracle General Ledger

Setup parameters Project Accounting
(N) Setup>System>Implementation Options>Billing (Tab Page)

Integration With Oracle General Ledger

Setup parameters General Ledger
(N) Setup>Journal>Sources

Integration With Oracle General Ledger

Setup parameters General Ledger
(N) Setup>Journal>Categories

Integration With Oracle General Ledger

Concurrent Programs
The following concurrent processes must be executed from Projects, for the data to be
pushed into the journal import tables:
PRC: Interface Labor Costs to GL;
PRC: Interface Usage Costs to GL;
PRC: Interface Total Burdened Costs to GL;
Note: All costs should have been distributed before running these programs
PRC: Interface Revenue to GL.
Note: Invoices should have been generated before running this program

Integration With Oracle General Ledger

Once data has been interfaced into the journal import tables, the journal import program
must be submitted from the General Ledger module. This process brings the summary
PA transactions into GL and are ready to be posted.
Once the journals are successfully posted, the Tieback processes have to be submitted
from PA. The tieback process identifies and updates Oracle Projects transactions that
have been interfaced to another application.

To tieback costs and revenue from GL to PA, the following concurrent

processes must run:
PRC: Tieback Labor Costs from GL;
PRC: Tieback Usage Costs from GL;
PRC: Tieback Total Burdened Costs from GL;
PRC: Tieback Revenue from GL;

Integration With Oracle Purchasing

The integration between PA and PO allows us to view committed costs of requisitions
and purchase orders within PA. This is accomplished by entering project related
information into the source requisition or Purchase Order.
Data Flow
Commitments from PO are visible in PA via the Project Status Inquiry (PSI) screen.
There is no intermediary import or interface table between these modules. However, for
project related requisitions and purchase orders, each line item must contain the
following PA information:
project name
task name
expenditure type
expenditure organization
expenditure item date

Integration With Oracle Purchasing

Setup Parameters
There are no specific setups to integrate these two modules with the exception of the
Account Generator. Accounting rules need to be set up before charging Purchase
Requisitions and purchase orders against Projects.
In addition, the following profile options need to be reviewed and set as required:
PA: Allow Override of PA Distribution in AP/PO
PA: Default Expenditure Organization in AP/PO
This parameter allows us to enable or disable a user from over-riding the accounting
flexfield generated by the auto accounting. The parameter can be set at a site level as
well as at a responsibility level.

Integration With Oracle Purchasing

Concurrent Programs
There are no concurrent processes to be run for PO and PA Integration

Integration With Oracle Payables

The integration between PA and AP allows for three types of transactions to flow
between them. These are:
supplier invoices;
expense reports; and,
adjustments.

Integration With Oracle Payables

Data Flow
Supplier invoices are sent from AP to PA. Each invoice must contain project related
information for this interface, as follows:
project number
task number
expenditure type
expenditure organization
expenditure item date
quantity, if setup option Cost Rate Required is set to Yes.

Expense reports entered into PA for project related expenditures are sent to AP via the
AP interface tables. AP creates invoices from these expense reports using the Invoice
Import feature, approves and pays the invoices and transfers these accounting
transactions directly to GL.

Integration With Oracle Payables

Data Flow (Cont.)
The tieback process is then invoked in PA to ensure that AP transactions have
been successfully interfaced. The tieback process is run after AP Invoice
Import has run.

Integration With Oracle Payables

Setup Parameters

The following profile options need to be reviewed and set as required :

PA: Summarize Expense Report lines

PA: Default Expenditure Organization in AP/PO

When Importing from Payables, the Invoice Import Source should be = Oracle
Projects

Concurrent Programs
The following concurrent manager processes must be invoked to enable the interface
between AP and PA.

PA: Interface Supplier Invoices from Payables

PA: Interface Expense report from Payables

PA: Distribute Expense Report Costs

PA: Interface Expense Reports to Payables

PA: Tieback Expense Reports from Payables

Integration With Oracle Payables

For adjustments made to Supplier Invoices in Oracle Projects, the following

processes must be invoked:
PA: Distribute Supplier Invoice Adjustment Costs
PA: Interface Supplier Invoice Adjustment Costs to Payables

Integration With Oracle Receivables

PA integrates into AR by generating draft invoices and sending them to AR for printing
and tracking customer payments.
Data Flow
PA loads the invoices into AR via ARs Auto Invoice feature. Project information is stored
in the invoice via the Line Transaction flexfield.
Setup Parameters
Most of the parameters required for running auto invoice is predefined in Oracle. Viz.
Line Transaction Flexfield
Line Ordering Rules (PA Line Order)
Grouping Rules (PA Grouping Rule)
Invoice Source (PA Invoices)

Integration With Oracle Receivables

Setup Parameters
(N) Setup>Financials>Flexfields>Descriptive>Segments Query for Line Transaction Flexfield

Integration With Oracle Receivables

Setup Parameters
(N) Setup>Transactions>Auto Invoice>Line Ordering Rules

Integration With Oracle Receivables

Setup Parameters
(N) Setup>Transactions>Auto Invoice>Grouping Rules

Integration With Oracle Receivables

Concurrent Programs
The following concurrent process must be executed for the data to be pushed into AR:
PRC: Generate Draft Revenue
PRC: Generate Draft Invoices
PRC: Interface Invoices to Receivables

Once data has been interfaced into AR, the Autoinvoice program must be run in AR:
(N) Interfaces > AutoInvoice > AutoInvoice Master Program - with Invoice Source of PA
INVOICES.
Once data has been interfaced to AR, you tieback interfaced invoices into PA by running
the following concurrent manager process:
PRC: Tieback Invoices from Receivables

Integration With Fixed Assets

PA collects project related expenditures for capital projects. Using AutoAccounting and
Account generator features, these costs are assigned to a Construction In Process (CIP)
account. When the asset is ready to be placed in service, it is interfaced to FA.

Data Flow
When expenditures for capital projects are collected PA, they are classified as
capitilazable or non - capitalizable. These costs are then interfaced from PA to FA via the
FA Mass Additions Table from where they are posted to the FA Assets Table. They are
then posted to the GL via the GL interface table, at which point the CIP account is
relieved and costs transferred to the asset account.

Integration With Fixed Assets

Setup Parameters
PA needs the following FA implementation features in place before data from PA can be
interfaced to FA.
Corporate book
Category flexfield
Location flexfield
Asset key flexfield

Concurrent Programs
The following concurrent programs are invoked to interface data from PA to FA
PRC: Generate Asset lines for a single project
PRC: Generate Asset lines for a range of projects
PRC: Interface Assets to Oracle Assets

Integration With Fixed Assets

Concurrent Programs (Cont.)
From FA, we have to review the mass additions and update the status of the lines from
New, Merged or Cost Adjustment to Post.
The Post Mass Additions Program has to be run after reviewing the lines.
After successful posting of the Asset lines, the following program has to be run from PA:
PRC: Tieback Asset Lines from Oracle Assets