Solved

Multi Qty CRO Repair line sent for DSO - Repairs, once received with different Condition code doesn't get reserved to the Customer Order.

  • 23 September 2021
  • 4 replies
  • 147 views

Userlevel 4
Badge +9

Hi, in our customer’s TEST environment;

1. Create a CRO line with minimum 2 quantities and release it for disposition shop order. Part should be condition code enabled. CO should be created with CRO at the beginning.

2. Create two DSO lines where one is for internal repair order and other one is for external service order.

3. Complete the internal repair order.

4. Internal repair order is received with condition code ‘USED’ as illustrated below. Serial No = E1.

5. Serial E1 is now reserved in CRO’s customer order.

6. Now process the 2nd DSO line for external repair order.

7. As illustrated below, Serial E2 is received in inventory with condition code OVH.

8. But, customer order failed to reserve the 2nd serial, since it has different condition code.

Check the reserved qty field of the CO. Only a qty of 1 is reserved. 

Is there a fix available for the issue?

icon

Best answer by Devni Panduwawala 23 September 2021, 06:30

View original

This topic has been closed for comments

4 replies

Userlevel 5
Badge +8

Hi Ravindu,

 

Patch 158237 which is available from UPD12 onwards will resolve this issue.

 

Information from RnD

RO design allows only one customer order line per CRO line. You cannot reserve parts with multiple condition codes to a single customer order line. Therefore, the functional enhancement needed for the requested issue.

As a support fix, We will add an information message when user approves the disposition lines when it satisfies all of following conditions:
#  Customer order is partially Reserved with a part having a different condition code.
# Disposition does not create repairs. (Because A warning message is already in place in repair receipt flows)
# Disposition shop order originates from CRO

It is an information message at disposition line approve due to a technical limitation (not a warning message as in the other places)

 

Best regards,

Devni

Badge +1

 The use case for a condition enabled item is to be able to reference one item with multiple condition rates, rather than having multiple .

Badge +1

 The use case for a condition enabled item is to be able to reference one item with multiple condition rates, rather than having multiple .

 

 

 

MyLowesLife  The use case for a condition enabled item is to be able to reference one item with multiple condition rates, rather than having multiple items to manage where the description and cost distinguish one item from another. 

Userlevel 2
Badge +7

@Devni Panduwawala  I also came across this issue during a testing phase with a middle east MRO customer :relaxed: Glad to hear this issue is being resolved by UPD12.