The table below outlines all known symptoms and setups that cause this to occur.

Please add a comment to this note if you find additional settings that trigger
this message so that we can include them here.

# Release Cause Fix

Possible mismatch of setup between OM and AR.

In Order Management, the setup is:

Fix Setup:
Responsibility: Order Management
Navigation: Setup > Transaction Types > Define
Responsibility: Order Management
On the Finance Tab : Invoicing Rule and Accounting Rule Defined
Navigation: Setup > Transaction Types > Define
The Order type defined in Order Management has accounting and
On the finance tab check to see if there is an invoicing rule and an accounting
invoicing rules defaulting. This is due to OM Patch 5725539. The patch
rule
11.5 - allows for a defaulting rule on the Order Type.
1 indicated. If accounting rules are not being used and the GL calendar is not
R12
using
type of "month" make sure that the order type does not have invoicing or
In Oracle Receivables, the setup is: accounting rules associated.
Responsibility: Receivables
Navigation: Setup > Transactions > Sources Also, ensure that in RA_INTERFACE_LINES_ALL, you are passing in a
Go To: Accounting Information tab value for
Invoicing Rule and Accounting Rule are set to 'None' TRX_DATE.
Customer is not using rules in AR.

2 11.5 - The period type of the accounting rule does not match the period type of 1. Review the Set of Books
R12 the set of books period type. System Administrator responsibility > Profile > System
Query on %book% and verify the GL Set of Books associated to the
responsibility. Check at all levels: Site, Application, Responsibility, and User

2. Review the calendar associated to the set of books

AR responsibility > Setup > Financials > Books
 Query the set of books and verify the period type.

3. Query the Accounting Rule Used

AR responsibility > Setup > Transactions > Accounting Rule and note the
period used.

The period type for the GL Calendar and the period type for the Accounting
Rule should be the same. If all operating units use the same period type, then
you can change the accounting rule to use the same period type.
When you get both these errors at the same time, please check whether your
GL Period is open in AR for the date seen in the columns GL_DATE,
Common Errors:
SHIP_DATE_ACTUAL and SALES_ORDER_DATE in the table
1) Invalid Warehouse ID (WAREHOUSE_ID)
3 11.5-R12 RA_INTERFACE_LINES_ALL
2) Unable to derive a gl date for your transaction. Please ensure that your
transaction is in a gl period which you have defined
See also Note 201241.1 Troubleshooting AutoInvoice Date Derivation and
How AutoInvoice Derives Dates
4 R11.5 - Item Validation Organization is Not Defined for Operating Unit There is an error in some versions of this setup test. To check if this is a real
R12 issue run the query below:
This may be displayed when running the 'Oracle Receivables AutoInvoice
Setup Test'. (See Note 1079666.1) SELECT a.parameter_value,
b.name
FROM OE_SYS_PARAMETERS_ALL a,
HR_ALL_ORGANIZATION_UNITS b
WHERE b.organization_id = a.parameter_value
AND NVL(a.org_id, -99) = &org_id
AND a.parameter_code = 'MASTER_ORGANIZATION_ID'

In R12, the tables are different for the organization query. If the SQL returned
one row, this proves the organization is defined.

This will be fixed in the AR General Setup and also AR AutoInvoice Setup
 tests with the next upgrade.

If you do not find a value using the query above, correct your setup using
appropriate Order Management responsibility:
Setup>System Parameters>Values
Select the appropriate Operating Unit
For Category select Generic Parameters
Scroll down and check Item Validation Organization and make certain it is
properly set.
1) Set OM:Set Receivables Transaction Date as Current Date for Non
Shippable Lines to Yes.
Profile option 'OM:Set Receivables Transaction Date as Current Date for
5 11.5
Non Shippable Lines' is set to No 2) Update RA_INTERFACE_LINES_ALL table and set the
SALES_ORDER_DATE to the date the record was created in the interface
table
The profile options HR: Security Profile is not set properly. Check to make sure that your OM and AR responsibilities have the same HR
6 11.5-12.x
Different value of HR: Security profile at OM and AR side. security profile settings.
7 12.x When running Autoinvoice Import Program it fails with: To fix the issue and make all valid warehouses available in AR, please
validate the following setups:
Invalid Warehouse ID (WAREHOUSE_ID).
1) Check the Receivables responsibility having the access to warehouse.
This problem exists in all organizations. Warehouse is valid from Order Navigation: Setup >Transactions > Define item
Management responsibility, but it does not appear in Receivables It will show warehouse details having access to the Receivables responsibility.
responsibility.
2) If you do not find a value in previous step, correct your setup using
appropriate Inventory
responsibility:
Navigation: Setup > Organizations > Organization Access.
Associate the warehouse which is missing with the Receivables responsibility.
Save the changes.
Now go back to Receivables responsibility and check if you are able to access
warehouse or not as mentioned in step1.

3) Also check the profile options HR: Security Profile is set properly:
Make sure that your OM and AR responsibilities have the same HR security
profile settings.