AP Invoice Interface Issues

AP Invoices Doc Created by –Priya NV-Version 1.0

 Recurring Issues related to AP Invoices in WP
1. Intercompany AP Invoice Interface issues
2. Standard AP Invoice creation issues after GSG Inter-Project Simplification

Intercompany AP Invoice Interface

Process Once the Intercompany AR invoice is created and interfaced successfully to Receivables, the
tieback process will be kicked off in the Provider OU
The intercompany invoices are automatically copied into the interface table of the receiver
operating unit’s Payables. Intercompany invoices interfaced to Payables are identified with the
following attributes:
• Source. All intercompany invoices have a source of Projects Intercompany Invoices.
• Supplier. The supplier is identified by the provider operating unit’s internal billing
implementation options.
• Supplier Site. The supplier site is based on how the provider operating unit defines the receiver
controls for the receiver operating unit.
• Invoice Amount. The Payables invoice amount is the amount of the related Receivables invoice,
including taxes. The interface process populates the project–related attributes for intercompany
Payables invoice distributions, as indicated below:
• Project Number. The number of the cross charged project indicated in the invoice line.
• Task Number. The number of the task specified in the Intercompany Tax Receiving Task field on
the cross charged project.
• Expenditure Item Date. The invoice date of the intercompany Receivables invoice.
• Expenditure Type. The expenditure type specified by the receiver operating unit in the Receiver
Controls tab.
• Expenditure Organization. The expenditure organization specified by the receiver operating
unit in the Receiver Controls tab.
 
In addition, the interface process matches the tax code from each invoice line of the Receivables
invoice to the appropriate Oracle Payables tax code. This process indicates that the Payables
invoice distributions do not include tax amounts, so that the Payables Open Interface process
creates the invoice distributions for the entire invoice by grouping the tax lines based on the
following attributes:
 
• Tax code

• Project information (project, task, expenditure item date, expenditure type, expenditure
organization)

AP Invoices Doc Created by –Priya NV-Version 1.0

Issue1 Payables Open Interface Import is run from the Receiver AP to import the Intercompany AP
invoice. The process may fail importing invoice with below error” Acct date not in  open pd”
If the AP Periods are not in Open status as of the GL date while running the import program , the
Reason
program rejects the invoice

Use the below query to find the rejection reasons.

Solution Rerun the Import Program with an Open GL date and ensure the invoice is imported successfully

Issue2 Payables Open interface import may fail importing invoice with below error” PA flexbuild Failed”
The PA flexbuild failed error is due to one of the validation on the Projects data is violated.
Reason

Solution Error Message Rejection Reason Solution

PA Flexbuild Failed Expenditure Option 1: Change the expenditure item date

Organization date is
prior to expenditure Or Option 2: change the start date of the organization
item date Run the open interface import

PA Flexbuild Failed Supplier and supplier Supplier site needs to be created and the supplier and
site linked to the site details for the error invoice to be updated in AP
invoice doesn’t exist in open interface lines and run the import
the Payables look up
set , hence
intercompany segment
for code combination
is not created

PA Flexbuild Failed Project status is closed Reopen the project and rerun the open interface import

AP Invoices Doc Created by –Priya NV-Version 1.0

 Issues during Creation of AP Invoice after Inter Project Simplification

Process Expenditure types which are enabled for Intercompany during Inter Project Functionality
implementation.

INTERCOMPANY EXP TYPES:

1. 9110 - IT Services Costs
2. 9911 - Global Charges
3. 9912 - Marketing Intangibles
4. 9913 - Global Charges True Up
5. 9915 - GBS Charges
6. 9916 Project Delivery SW Rec
7. 9917 Treasury Cost Recoveries
8. 9919 - BSC Charges
9. 9920 - Office Cost Rcy(Global)
10. 9973 Services Bus Mgmt Costs
11. 9974 Services Region OH Costs
12. 9975 Bus Line OH Recharge

Issue 1 After the implementation of Inter-Projects, a new restriction has been developed for the above
mentioned intercompany expenditure type versus Internal Suppliers.
If an AP invoice is using an Internal Supplier which is part of the IC AP Look up set, then the
expenditure type used should be one among the above 12 Expenditure Types. If not, the system
will throw an error during the distribution account generation.

Error 1)System cannot generation distributions because tax calculation has failed due to
following error Entity :InterCompany Error Occurred in pa_flexbuild

Solution Use the correct Internal Supplier which is part of look up set when Inter-Co Expenditure Type is
used.

AP Invoices Doc Created by –Priya NV-Version 1.0

Issue 2 After the implementation of Inter-Projects, a new restriction has been developed for the above
mentioned intercompany expenditure type versus Internal Suppliers.
If cross-charged AP Invoice is created, the segments are derived based on the Expenditure
Organization .
But if a cross-charged AP invoice uses an Intercompany expenditure type, then the invoice
becomes an Interco invoice and, the segments are derived based on the Project Owning
Organization.

Error 1)System cannot generation distributions because tax calculation has failed due to
following error Entity :Segment Error Occurred in pa_flexbuild

Solution Use a different Expenditure Type other than Intercompany Expenditure type

AP Invoices Doc Created by –Priya NV-Version 1.0