Troubleshooting Unit of Measure Issues with AutoInvoice

Troubleshooting Unit of Measure Issues with AutoInvoice [ID 1132807.1]

   

Troubleshooting Details

1.  Setup and Usage of Unit of Measure in AutoInvoice

The Unit of Measure is a conditionally required field in AutoInvoice.  It is required whenever an inventory item is specified in the import table and optional all other times.

Control over the fields populated is dictated by the Transaction Source setup.  As shown in the screenshot below, transaction source controls if the ID (Column Name = UOM_CODE) or Value (Column Name = UOM_NAME) will be supplied as a column in the interface table. 

Note that UOM is not populated in the following scenarios:

• LINE_TYPE = 'LINE' and you are passing a dummy line for either a tax-only or
  freight-only line
• LINE_TYPE = 'TAX', 'CHARGES', or you are passing freight for a specific line
• Line is for a credit memo

Destination Column: Once imported, the UOM is stored on the invoice in the column RA_CUSTOMER_TRX_LINES_ALL.UOM_CODE

Validation:  UOM must exist in the table MTL_UNITS_OF MEASURE and is mandatory if an inventory item is passed, except for transaction sources of 'OKS_CONTRACTS'

2. Troubleshooting Unit of Measure Errors in AutoInvoice

    a. Common Errors

The most common error reported for Unit of Measure in Autoinvoice are:

·         The supplied unit of measure and the primary unit of measure of your system item must share the same unit of measure class.

·         You must supply unit of measure for transactions with items

These are, in most cases, triggered by improper setup or invalid data being passed to AutoInvoice.  Troubleshoot these as follows.

        i. Evaluate if UOM is required

UOM is only required for inventory items where the transaction source is not 'OKS_CONTRACTS'.  If this applies to your transaction, make certain the UOM is provided.  It is recommended that UOM not be provided except when it has a valid purpose on a transaction line.

Tip:  The item within the Sales Order must be assigned to the proper inventory organization and the UOM must be valid for that organization

        ii. Make certain you have populated the proper column

Responsibility:  Receivables Manager

Navigation:  Setup> Transactions> Transaction Source

Make certain that the column you are populating (UOM_CODE or UOM NAME) is seelcted on the transaction source.

        iii. Verify that the UOM exists in the base tables

The UOM passed must exist in the table MTL_UNITS_OF_MEASURE.  Check to ensure that the value you have passed is also showing in this table.

        iv.  Verify the UOM Class

Make certain the Primary UOM class on the inventory item is consistent with the UOM class you have provided for the organization.

A UOM class represents a common measure for the UOM's within the class.  For example, if the UOM Class is Time one might expect to see values such as Minute, Hour, Day, Week, Month and Year.  If an invoice is passed into AutoInvoice with a UOM of "Each" for an inventory item that is designated with a UOM Class of Time, the error shown below will occur: 

The supplied unit of measure and the primary unit of measure of your system item must share the same unit of measure class.

Release	Error String or Presentation	Cause	Recommended Fix*
11.5 - 12.1	Intercompany transactions are rejected with "The supplied unit of measure and the primary unit of measure of your system item must share the same unit of measure class"	OE: Item Validation Organization is not defined for the operating unit(s) associated with the intercompany transaction.	Set the profile option: OE: Item Validation Organization
11.5	Invoices sourced in OKS Contracts are rejected with: The supplied unit of measure and the primary unit of measure of your system item must share the same unit of measure class	Bug 4724801	Fixed File: raavli.lpc 115.16 is included in 11i.AR.P / 11i.FIN_PF.H AR.L: Patch 5691036 includes raavli.lpc version 115.7.15100.2 AR.M:  <<patch:4733108>> includes raavli.lpc version 115.10.15101.2 AR.N:  Patch 2837106 includes raavli.lpc version 115.13.15103.3 AR.O: Patch 5868909 includes raavli.lpc version 115.15.15104.2

Do not assume that logical UOM relationships have been defined.  For example, if you have "Quarter" on a transaction but have not defined "Quarter" in relationship to the "Time" UOM class then the system will reject the record as it cannot reconcile that a Quarter is representative of 3 months.  You can check this as follows:

Navigation: Inventory--> Setup--> UOM--> Conversions. Click On The Interclass Tab

Select the item from the lov and define how the item converts to other items in the UOM class.

Note: The Primary unit of measure can be different for each organization. Make sure, when troubleshooting this issue, that you review the UOM for the item validation organization associated with the transaction. This may require that you check or set the profile option "OE: Item Validation Organization"

    b. UOM Issues with Projects Integration

If you are passing data from Oracle Projects to Receivables, make certain that you have set the profile option "PA: Receivables Lines UOM".  If this value is not properly set then receivables will not use the same UOM as Projects for invoices generated via AutoInvoice.

     c. UOM Issues with R12 E-Business Tax and Quantity Based Taxes

Several issues have been reported with the Unit of Measure and tax calculations in release 12.  For more on the limitations and troubleshooting of Unit of Measure in context of tax calculations, please refer to Note 1181529.1 How To Setup and Troubleshoot Quantity Based Taxes in R12 E-Business tax (EBTax)

    d. UOM Bugs and Other Common Errors

*Note that the patch recommendation is for the latest released version of the file and not necessarily the version that included the fix.  For example, if version 46 is the fixed file, the recommended patch may contain version 72 of the fixed file.  This fix will include the bug fix referenced here as well as any other bug fix released since the bug was resolved.

3. Still Have Questions?

This article along with Note 1075757.1, Troubleshooting AutoInvoice for Oracle Receivables Release 11.5 Through 12 and the auxiliary notes referenced within attempt to guide you to resolution of most known issues with AutoInvoice and Unit of Measure issues..  To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Receivables Community.

If you find that you require assistance after completing the steps outlined in this note please provide the following information to expedite resolution of your issue:

1) Can you create a manual invoice in AR with this Unit of Measure and Inventory Item?

2) Can you replicate this at will ?

3) Do you have any research findings that would help us in understanding or troubleshooting this issue? If yes what?

4) Did this work before? If so what has changed?

5) If this is AutoInvoice related, provide the AutoInvoice Data Collection Test Diagnostic and Setup diagnostic applicable for your release. Refer to Note 1079666.1 for the latest instructions.