Professional Documents
Culture Documents
PA Integration With Other Modules v1.0
PA Integration With Other Modules v1.0
PA Integration With Other Modules v1.0
NOTICE
Please contact the appropriate department for validating the version of this document and any changes.
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.
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.
project name
task name
expenditure type
expenditure organization
expenditure item date
Concurrent Programs
There are no concurrent processes to be run for PO and PA Integration
The integration between PA and AP allows for three types of transactions to flow
between them. These are:
supplier invoices;
expense reports; and,
adjustments.
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.
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.
Setup Parameters
Most of the parameters required for running auto invoice is predefined in Oracle. Viz.
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
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.
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