Scribd
Upload
225 views2 pages

Open Balance Migration Approach

This document outlines the steps to convert legacy revenue, invoices, costs and balances to Oracle Projects. It involves: 1. Creating summarized legacy payable, revenue and invoice balances in projects through expenditure/revenue batches and events. 2. Running processes to generate draft invoices and revenue, distribute costs, and interface transactions to the general ledger or receivables modules. 3. Optionally deleting converted legacy invoices from receivables to prevent them from becoming open balances, or converting unpaid invoices directly to receivables. 4. Converting advance from customer balances by creating advance invoices in receivables and adjusting applied amounts.

Uploaded by

jo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
225 views2 pages

Open Balance Migration Approach

This document outlines the steps to convert legacy revenue, invoices, costs and balances to Oracle Projects. It involves: 1. Creating summarized legacy payable, revenue and invoice balances in projects through expenditure/revenue batches and events. 2. Running processes to generate draft invoices and revenue, distribute costs, and interface transactions to the general ledger or receivables modules. 3. Optionally deleting converted legacy invoices from receivables to prevent them from becoming open balances, or converting unpaid invoices directly to receivables. 4. Converting advance from customer balances by creating advance invoices in receivables and adjusting applied amounts.

Uploaded by

jo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Convert Legacy Revenue and Invoices to

Oracle Projects
Note: Only Active projects will be considered for migration.

Convert Legacy Cost Balance in Projects

In the approach described below, we will create summarized legacy Payable invoice balance
in project.

 Step: 1(PA): Disable interface cost to GL in Implementation options


 Step: 2(PA): Create Legacy AP invoice balance as expenditure batch in PA for each
projects.
 Step: 3 (PA): Create and Distribute the cost in Projects
 Step: 4 (PA): Create Cost accounting events in Projects
 Step: 5 (PA): Run PRC: Create Accounting. This will set the legacy payable balances
to look like interfaced to GL. If you disabled the GL Transfer option in Step 1, no
journal entries will be created.

Project Billing

Convert Legacy Revenue/COGS Balances:

In the approach described below, we will create summarized legacy revenue as revenue
events and revenue in oracle projects. In order to prevent the balances from becoming open
balances in Receivables, we will need to follow the below process.

 Step: 1 (PA): Disable revenue transfer to General Ledger. Navigate to the


Implementation Options screen and disable the Transfer Revenue to GL flag. This
will prevent your legacy revenue balances from being sent to Oracle General Ledger
since they were already posted in your legacy system.
 Step: 2 (PA): Create legacy revenue balances as Revenue Events (Revenue Amount is
populated).
 Step: 3 (PA): Generate revenue for legacy revenue events. Run the PRC: Generate
Draft Revenue for a Range of Projects process through the last day the period
 Step: 4 (PA): Run the Interface Revenue to General Ledger. This will set the legacy
revenue balances to look like interfaced to GL. If you disabled the GL Transfer
option in Step 1, no journal entries will be created.
 Step: 5 (PA): Turn back on the Transfer Revenue to General Ledger implementation
option. Navigate to the Implementation Options screen and enable the Transfer
Revenue to GL flag.
Covert Legacy Invoice Balances:

In the approach described below, we will create summarized legacy invoices as billing events
and invoices in Oracle Projects. In order to prevent the balances from becoming open AR
balances in Receivables, we will need to delete them in Oracle Receivables.

 Step 01 (PA): Create legacy invoice balances as Billing Events


 Step 02 (PA): Generate draft invoices for legacy invoice balances. Run the PRC:
Generate Draft Invoices for a Range of Projects process. Use the last day of the
respective period as Through Date and Invoice Date.
 Step 03 (PA): Approve and release draft invoices.
 Step 04 (PA): Interface legacy project invoices to Oracle Receivables. Run the PRC:
Submit Streamline Interface process with the XI: Interface Interfaces to Receivables
option.
 Step 05 (AR): Delete the legacy project invoices in Oracle Receivables or Credit memo
will be raised to nullify the account.

Unpaid Legacy AR Invoices

 What we converted above was a summary of billed customer invoices for each project.
Some of them have already been paid, some have not in Receivables. You will need to
convert any unpaid AR invoices as open AR transactions in Oracle Receivables.

Advance from Customer

 Convert the advance from customer GL balances.


 Use the Advance from customer invoice type to create advance in AR.
 Use the adjustment transaction to adjust the applied
 Reverse balance in GL for remaining amount.

Note: Drill down option for converted AP & AR invoices will not be available in Projects.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy