Overview of Inter-Project Billing
Overview of Inter-Project Billing
Overview of Inter-Project Billing
DISCLAIMER
This document in any form, software or printed matter, contains proprietary information that is
the exclusive property of Oracle. Your access to and use of this confidential material is subject to
the terms and conditions of your Oracle software license and service agreement, which has been
executed and with which you agree to comply. This document and information contained herein
may not be disclosed, copied, reproduced or distributed to anyone outside Oracle without prior
written consent of Oracle. This document is not part of your license agreement nor can it be
incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.
This document is for informational purposes only and is intended solely to assist you in planning
for the implementation and upgrade of the product features described. It is not a commitment to
deliver any material, code, or functionality, and should not be relied upon in making purchasing
decisions. The development, release, and timing of any features or functionality described in this
document remains at the sole discretion of Oracle.
Due to the nature of the product architecture, it may not be possible to safely include all features
described in this document without risking significant destabilization of the code.
Technical Components 15
Basic Data Model 15
Client Extension & Workflow 15
In above picture an there is a Software Installation Project for a customer where some of the work
such as QA testing and Infrastructure installation is subcontracted to two other projects.
Now while doing infrastructure installation any cost incurred by Infrastructure Project will be billed
to Software Installation Project then further Software Installation project will generate invoice and
deliver it to Customer.
In Oracle E-Business Suite terminologies “Infrastructure Project” becomes provider project where
as “Software Installation Project” becomes receiver project.
Inter-Project functionality can utilize any type of Cross Charges.
1. Intercompany (Projects in different legal entities)
2. Inter-Operating Unit (Projects in same legal entity but different Operating Units)
3. Intera-Operating Unit (Projects belong to different organization but same Operating Unit)
Auto-accounting Setup
To derive accounts for intercompany invoices, Auto-accounting setup is required for function
“Intercompany Invoice Accounts” on provider operating unit.
1. Navigate to Setup > AutoAccounting > Assign Rules
2. Query function “Revenue and Invoice Accounts”
3. Map each rules for all segments for both function transactions
a. Contract Asset Account (Only applicable if you’re on 12.2.7 and above)
b. Contract Liability Account (Only applicable if you’re on 12.2.7 and above)
c. Invoice Write-Off Account
6 WHITE PAPER | Inter-Project Billing | Version [1.03]
Copyright © 2020, Oracle and/or its affiliates | Dropdown Options
d. Realized Gains Account (Optional)
e. Realized Losses Account (Optional)
f. Receivable Account
g. Rounding Account
h. Unbilled Receivable Account
i. Unbilled Retention Account (Only if “Account for Unbilled Retention” flag is enabled in
Implementation Option)
j. Unearned Revenue Account
4. Run Distribution process to calculate cost. In this case User needs to run “PRC: Distribute
Labor Costs”.
Issues
ISSUE STEPS TO CAUSE SOLUTION
REPRODUCE
Payable invoice is not 1. Navigate to Projects Due to lower version 1. Please download and review the
getting created after responsibility of PAXARAPB.pls, if readme for Patch. 26978259:R12.PJB.C
running PRC: Tieback 2. Run request PRC: receiver project is in 2. Apply patch in a test environment.
Invoices from Tieback Invoices from different legal entity
Receivables then AP Invoice was 3. Confirm the file version.
Receivables
not getting interfaced. PAXARAPB.pls 120.10.12020000.16
Run below command to check file
version
strings -a
$PA_TOP/patch/115/sql/PAXARAPB.pls
|grep '$Header'
4. Retest the issue.
5. If the issue is resolved, please migrate
the solution as appropriate to other
environments.
Receivable Invoice is not 1. Navigate to Projects Data is not inserted 1. Please download and review the
created for inter-project responsibility into readme for Patch. 27584203:R12.PJB.C
transactions 2. Run request PRC: ra_interface_lines_all 2. Apply patch in a test environment.
Interface Invoices to table.
3. Confirm the file version.
Receivables
PAXITCAB.pls 120.12.12020000.15
Run below command to check file
version
strings -a $PA_TOP/patch/115/sql/
PAXITCAB.pls |grep '$Header'
4. Retest the issue.
5. If the issue is resolved, please migrate
the solution as appropriate to other
environments.
While interfacing invoice 1. Navigate to Projects Code issue with 1. Please download and review the
to Receivables getting responsibility pattat.lpc and readme for Patch. 18772101:R12.PJB.B
below error. 2. Run request PRC: pattal.lpc 2. Apply patch in a test environment.
Transferring all I for Interface Invoices to 3. Confirm the file version.
project ID. Receivables
pattat.lpc 120.7.12010000.31
AutoAccounting error
code=1 Run below command to check file
version
strings -a $PA_TOP/bin/PATTAR |grep
'$Header'
4. Retest the issue.
5. If the issue is resolved, please migrate
the solution as appropriate to other
environments.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents hereof are subject to change without
notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties
and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed
either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without
our prior written permission.
This device has not been authorized as required by the rules of the Federal Communications Commission. This device is not, and may not be, offered for sale or lease, or sold or
leased, until authorization is obtained.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of
SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered
trademark of The Open Group. 0120
Inter-Project Billing
November 2020
Author: [OPTIONAL]
Contributing Authors: [OPTIONAL]
19 WHITE PAPER | Inter-Project Billing | Version [1.03]
Copyright © 2020, Oracle and/or its affiliates | Dropdown Options