Account Receivables Frequently Asked Questions (FAQ)

Q1. What are the billing cycle requirements for invoice generation?

A: A project must meet the following billing cycle criteria before it can generate an invoice:

a. No pending (unreleased) invoices exist
b. At least one bill cycle past the bill through date (or creation date if no bill through date exists) of the last non crediting invoice
c. At least first bill offset days past the project start date (or project creation date if no start date exists) if you have not yet invoiced a particular project
d. If the billing date is calculated by a client extension, and the client extension returns a null value for the billing date, then the process will not pick up the project


If unreleased invoices exist for a particular project, that project will not be picked up when the Generate Draft Invoices for a Range of Projects process is run. However, if the process is run for a single project, it will ignore the checks listed above.

Q2. What is the difference between running the Generate Draft Invoices process for a single project and running it for a range of projects?

A: When running the Generate Draft Invoices process for a single project, the billing cycle is ignored. Any unreleased draft invoices are deleted and a new draft invoice is created. When running the Generate Draft Invoices for a Range of Projects, the process takes the billing setup into account (i.e., bill offset and cycle days). Therefore, the system looks at the current date, adds cycle days and then determines whether or not the project is ready to bill.

Q3. If adjustments are made to an invoice (i.e., add Bill events, place items on hold), is it necessary to re-generate revenue?

A: Whenever adjustments are made to the expenditure items and/or events included on an invoice, you must submit the appropriate processes to reflect those changes (i.e., recalculate cost, regenerate revenue, regenerate invoices).


Q4. How can I generate a single invoice for a project with multiple agreements?

A: AutoInvoice will break when it meets a grouping rule. AGREEMENT_ID is a mandatory grouping rule. Once AutoInvoice encounters a project/order with a different AGREEMENT_ID, it will create a new invoice. As long as there is more than one AGREEMENT_ID, multiple invoices will be generated. One remedy is to create a single invoice in Receivables for multiple invoices coming from Projects.

Q5. How is the Output Tax Code determined in Oracle Projects?

A. Oracle Projects uses the hierarchy set up in Implementation Options to determine where to look for the Output Tax Code. Sources that can be used include:

Customer Site
Expenditure Type/Event Type / Retention
Client Extension
Oracle Receivables System Options


Q6. Is it possible to sort on the invoice amount column on the Invoice Review form (PAXINRVW) in Release 11.5?

A: A design change was made in Oracle Projects Release 11.5 to have brackets around the negative amounts in the invoice amount column. In order to accommodate the brackets, it was necessary to make the invoice amount column an alphanumeric column. It is not possible to sort numerically on alphanumeric columns; hence, the invoice amount is not available for sorting.

Q7. Why do I receive ORACLE error during DRAFT INVOICE GENERATION, cursor=29 code=-20001:, ORA-20001: Your system parameters are not defined for Oracle errors when running PRC: Generate Draft Invoices (PAIGEN)?

A: This error is received when Order Entry (OE) system parameters have not been setup for the current operating unit. The Receivables tax calculation requires an Inventory Master Organization for the following purposes:

a. Defaulting the tax code from a Product (Inventory Item)
b. Applying tax based on the characteristic/classification of an inventory organization location.
c. Applying exemptions/exceptions (discounted tax rates/special tax rates) based on item & master inventory organization combination.
d. Evaluating Tax Group Conditions based on characteristics of the item being transacted.

Currently, Inventory Master Organization is derived for tax calculation from OE_SYSTEM_PARAMETERS. Therefore, OE_SYSTEM_PARAMETERS must be setup in order to calculate tax based on the functionality mentioned above. These system parameters must be setup even if OE is a shared install. To correct the error, switch to your Order Management Responsibility, navigate to Setup -> Parameters and specify the Item Validation Organization.

Q8. Why do I receive the error message, Some transactions are disabled. Please check AutoAccounting setup, when running PRC: Interface Invoices to Receivables (PATTAR)?

A: In Projects Release 11.5, a rounding account must be created via AutoAccounting to handle rounding issues resulting from Multi-Currency billing. To correct this error, create a rounding account by navigating to Setup -> AutoAccounting:

a. In the Assign AutoAccounting Rules Form, query the Revenue and Invoice Accounts Rule.
b. Enable the rounding account.
c. Define Segment Rule Parings.
d. Save the changes.


Q9. Why is the message, Invalid AR Transaction Type Passed, displayed after running PRC: Interface Invoices to Receivables (PATTAR)?

A: Projects requires the Creation Sign field on the transaction types to be A (for Any Sign). Set the value to A on the Creation Sign field for both PA Invoice and PA Credit Memo transaction types. Additionally, the “Post to GL” box must be enabled.

Q10. When attempting to transfer sales credits to from Projects to Receivables, I receive the following error, APP-11863: Invalid sales_credit_type_id (nil). Why?

A: In order to import Projects invoices with sales credits, the sales credit type must be set to value and not ID in Receivables.

Q11. What is the order for running Projects processes for each transaction classification?


Transaction Import (if applicable)
Distribute Labor Costs
Interface Labor Costs to General ledger
Journal Import (G/L Process)
Tieback Labor Costs from General Ledger

Transaction Import (if applicable)
Distribute Expense Report Costs
Interface Expense Reports to Payables
Invoice Import (A/P Process)
Tieback Expense Reports from Payables

Transaction Import (if applicable)
Distribute Usage Costs
Interface Usage Cost to General Ledger
Journal Import (G/L Process)
Tieback Usage Cost from General Ledger

Interface Supplier Invoices from Payables
Distribute Supplier Invoice Adjustment Costs
Interface Supplier Invoice Adjustment Costs to Payables

Distribute Total Burdened Costs
Interface Total Burdened Costs to General Ledger
Journal Import (G/L Process)
Tieback Total Burdened Cost from General Ledger

Generate Draft Revenue
Interface Revenue to General Ledger
Journal Import (G/L Process)
Tieback Revenue from General Ledger

Generate Draft Invoices
Interface Invoices to Receivables
AutoInvoice (A/R Process)
Tieback Invoices from Receivables


Q12. Why doesn’t the Invoice Review (PAXINRVW) screen display totals?

A: A shift in functionality in 11i.PA.D allowed invoices to be generated in currencies other than the project currency. This shift allows invoices in multiple currencies to be displayed on one screen. To present a total would be incorrect because no conversion to a single currency takes place. This change was introduced with PAXINRVW version 115.104.

From 11i.PJ_PF.J the total functionality is only available for the ‘Project Functional Amount’ column. Please use Folder Tools to show this column.

1. Add the field ‘project functional amount’ from menu Folder

a. Navigate to Menu option FOLDER
b. Choose show field
c. Choose field ‘Project Functional Amount’

2. Click the totals button.

3. Totals will appear in ‘Project Functional Amount’ field.

Q13. When canceling an invoice in the Invoice Review Screen and clicking on the ‘Release Button,’ the pop-up window displays the original invoice date in the ‘Invoice Date Field’ as opposed to the system date. The date can be changed to the system date, but why doesn’t it default to this automatically?

A: The default of the original invoice date in the invoice date field in the Release pop-up window is intended functionality starting with PA family pack 11i.PJ_PF.J. The intended functionality is to display the actual invoice date, and if there is no invoice date entered, the Default is to the system date.

Q14. Is there a way to generate an invoice for each individual task for a percent-complete project?

A: To create separate invoices by task, first create multiple agreements by task and then fund by task level. (Note that this is for a one-customer project only–funding at the task level cannot be done for a multiple-customer project.)


Q15. Why does the PRC: Generate Intercompany Invoice (PAICGEN) process set the PA_DATE to the day the invoice was generated?

A: The PAICGEN process uses the system date for the PA Date from patchset 11i.PJ_PF.I forward, where users have the option of implementing enhanced period processing

Q16. Is there a way to keep the invoice generation process from marking new transactions as unapproved?

A: Beginning with family pack 11i.PJ_PF.L, the functionality has been enhanced to permit invoice regeneration without including new transactions. For family packs prior to 11i.PJ_PF.L, you can use the Automatic Invoice Approve/Release client extension.

Q17. Why are previously-approved invoices set back to unapproved after the invoice generation process is run?

A: Beginning with family pack 11i.PJ_PF.L, there are 2 new concurrent process options: (1) delete unapproved invoices only, and (2) exclude new transactions. For family packs prior to 11i.PJ_PF.L, the intended functionality includes previously-approved invoices getting set to unapproved during the PAIGEN run.

Q18. Why does the PATTAR (PRC: Interface Invoices to Receivables) process reject draft invoices with the rejection reason of ‘No PA Period in Range’ when the invoice date is in a closed PA Period?

A: Based on the enhanced period processing functionality that was introduced in family pack 11i.PJ_PF.I , the PA date and GL date are based on the invoice date. The PA date is set to the invoice date if that date falls in a PA period with a status of Open or Future. If the invoice date falls in a closed PA period, the PA date is set to the start date of the earliest open or future-enterable PA period that follows the invoice date. If there are no Open or Future periods, you will get the error.

Comments are closed.