INCIAR - Create Intercompany AR Invoices Fails With Error "QP API returnStatus=E" For RMA Flow With ATO Items (Doc ID 1129980.1)

Last updated on MAY 12, 2016

Applies to:

Oracle Inventory Management - Version: 11.5.10.2 and later   [Release: 11.5.10 and later ]
Information in this document applies to any platform.
Executable:INCIAR - Create Intercompany AR Invoices

Symptoms

Create Intercompany AR Invoices concurrent program (INCIAR) fails for RMA receipt transactions performed for configured items. The following errors are seen in the request log:
[
calling QP API...
returned from QP API...
QP API returnStatus=E

Return Warning from inarcil.

Warning: Cannot create invoice line
...
[...] INV_INTERCOMPANY_INVOICING: MTL_QP_PRICE.Populate_Results: Status_Code=IPL Status_Text=Item <item number> and uom <UOM code> not on pricelist
[...] INV_INTERCOMPANY_INVOICING: MTL_QP_PRICE.get_transfer_price: EXCEP G_EXC_ERROR
...
]

The following profiles are set to Yes at site level:
INV:Advanced Pricing for Intercompany Invoice (eg Advanced pricing is enabled)
INV: Use Model & Options for Configuration Pricing
The problem occurs with the RMA receipt but not with the related shipment / sales order issue. Adding the configured item to the price list will solve the issue. However, the expectation is that this should work without adding configured items to price list(s). It works fine with the same items when processing the sales order issue transactions. So it should work when returning items as well.

Steps to Reproduce

  1. Create a sales order having ATO Model whose shipping organization is not under the operating unit that is selling the order (trade order).
  2. Ship the order.
  3. Run the Create Intercompany AR Invoices concurrent program, see no error is raised.
  4. Run the Autoinvoice Master Program, see an invoice gets created as expected.
  5. Create a return (RMA) order referencing the order you shipped from previous steps.
  6. Perform the receiving.
  7. Run the Create Intercompany AR Invoices concurrent program, see it fails with the reported error.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms