Question

customer RMA in register arrivals : inventory part does not exist error


Userlevel 3
Badge +10
  • Hero (Customer)
  • 51 replies

Hi

We are upgrading from 22R2 to 23R2 and are currently testing the changes as they affect us.

In 22R2 we do our customer returns successfully from the RMA screens but in 23R2 this has moved to the ‘register arrivals’ screen.  Typically for us an RMA will be for 1 item among the many delivered, not the whole order, and the item being returned will be on a project activity.

If we use ‘receive with serial/lots’, then it works ok.  However, if we use ‘receive parts against order deliveries’ (which is preferable for these partial returns) we get an ‘inventory part does not exist’ error.  On investigation, it appears to be checking for the returned part in activity 0 rather than the activity it is actually being returned to.

17:14:32 TRACE - DATABASE {"origin":"DB","indentation":"19","time":"224614507","category":"FRAMEWORK","level":"DEBUG","type":"Key values","text":"Site: GB01, Part No: ESR-48/56B F, Configuration ID: *, Location No: PICK, Lot/Batch No: *, Serial No: VW131021032W0, Rev No: 1, W/D/R No: *, Activity Sequence: 0, Handling Unit ID: 2005"}

17:14:32 TRACE - DATABASE {"origin":"DB","indentation":"20","time":"224614507","category":"CALLSTACK","level":"DEBUG","type":"","text":"__anonymous_block at line 5 RECEIVE_PARTS_AGAINST_ORDER_DELIVERIES_SVC.DO_CREATE_RECEIPT at line 1378 RECEIVE_PARTS_AGAINST_ORDER_DELIVERIES_SVC.CREATE_RECEIPT___ at line 4959 RECEIVE_PARTS_AGAINST_ORDER_DELIVERIES_SVC.PACK_AND_SEND_MESSAGE_ARRIVAL___ at line 5818 RECEIVE_ORDER_API.PACKED_ARRIVAL at line 6164 RECEIVE_ORDER_API.PACKED_ARRIVAL___ at line 2397 RECEIVE_ORDER_API.INCREASE_QTY_AT_LOCATIONS___ at line 1196 RECEIVE_ORDER_API.INCREASE_QTY_AT_LOCATION at line 468 RECEIPT_INV_LOCATION_API.NEW at line 2140 RECEIPT_INV_LOCATION_API.NEW___ at line 1946 RECEIPT_INV_LOCATION_API.CHECK_INSERT___ at line 4739 RECEIPT_INV_LOCATION_API.CHECK_INSERT___.CORE at line 4721 RECEIPT_INV_LOCATION_API.CHECK_INSERT___.BASE at line 4710 RECEIPT_INV_LOCATION_API.CHECK_COMMON___ at line 1842 INVENTORY_PART_IN_STOCK_API.EXIST at line 1461 INVENTORY_PART_IN_STOCK_API.RAISE_RECORD_NOT_EXIST___ at line 2845 ERROR_SYS.FND_RECORD_NOT_EXIST at line 364 ERROR_SYS.RAISE_APPLICATION_ERROR___ at line 129 ERROR_SYS.RAISE_APPLICATION_ERROR___.FORMAT_CALL_STACK___ at line 123 "}

 

Has anyone else seen this, is it a bug or are we missing something about the new way the RMAs are being received?

Thanks,

mmck


8 replies

Userlevel 5
Badge +9

Hi @MMcK ,

  I tested your flow and it is working fine. Please elaborate more about your test plan, then we can have a closer look again.

regards,

Piyal

Userlevel 7
Badge +17

@Piyal Perera I think this issue is also reported in below post. It must be a bug when Receiving Parts against Order Delivery

 

Userlevel 3
Badge +10

Hi, yes, it’s specifically when Receiving Parts against Order Delivery where they were despatched from a project activity, in 23R2.

Userlevel 5
Badge +9

Hi @Marcel.Ausan  @MMcK ,

   Thanks I feel have more info now and will have a look and let you know the outcome.

regards,

Piyal

Userlevel 5
Badge +9

Hi @MMcK 

   I checked 23R2 and Master version. 3 serial part, project connected 3 CO lines, delivered. Created RMA. - receive parts against order deliveries- delete 2 serials from the assitant. And returned 1 serial part.

The flow completed without any error. Do I miss something here?

regards,

Piyal

Userlevel 3
Badge +10

Hi @Piyal Perera 

Many thanks for looking into this.  We typically do not actually delete the other serial lines but leave them blank, but I have now tried both ways and it’s made no difference, I still get the ‘inventory part not in stock’ error.

 

Do you see the same trace message in the debug log window?  This shows activity seq 0 when the item should be returned into, in our case, activity seq 100002568.

For reference, our versions are these:

I hope this helps in reproducing the error.

It does seem to have been reported by @Hashane Bolonne as well

Thanks again,

mmck

 

Userlevel 5
Badge +9

Hi @MMcK 

  I searched any bug correction in this area, but my search results not given any related issue. Please check OESHIP transaction related to your serial part. When creating OERETURN transaction it refers the corresponding issued transaction.

regards,

Piyal

Userlevel 3
Badge +10

Hi @Piyal Perera 

Thanks again for your assistance on this.

How do I check the OERETURN transaction when the return has failed, it doesn’t show up in the part serial history?

Best regards,

mmck

 

Reply