Skip to main content

Hello everyone, (Sorry for poor quality img)

I´ve run into some issues concering the receiving of serialized parts in the component repair order (CRO) flow. The problem has started to become more frequent and I would like to find the root cause of this issue.

 

Summary of problem: The repair technician wants to close the repair shop order. First, the time of the operation is reported then the reception of the parts should be done.

The problem is that an error message appears which signals that we should use the same availability control ID or W/D/R number in the existing stock.

We don´t assign different W/D/R numbers currently, and Control ID’s are not common practice in that area of operations. Therefore, the issue is interesting to say the least.

 

Our setup:

We are currently not tracing finished/semi-finished products. Although, the products that are received through the CRO - process has a serial number.

 

Current workaround is to change the Control ID in the “Receive Parameter”, which enables us to close everything. This solution does not feel viable in the long term. Whereas it should not be necessary to do so to begin with.

 

Have any of you encountered similar problems?

 

Best Regards

 

 

The reason for this error to appear seems nothing connected to CRO. But the key violation in part in stock record. What happens here is, by entering a different availability control ID, you are trying to insert a new record to the part in stock table with same keys. Therefore, the general error message of change W/D/R number displayed to the user. This is because  W/D/R number is a key in that table and changing it can possibly create a new record with the new availability control ID.

Having a new W/D/R number has no effects in the functional flows as long as you are ok to proceed with that value.

Hope this clarifies the behavior.

Hi Pushpa,

Thank you for your reply and clarification!

 

Although, the problem occurs mainly when receiving goods when the CRO is finished, the repair shop order that is. 

The inventory part in stock does indicate that the specific product is still in inventory. Hence, the error message indicates that we should use a separate W/D/R No.

 

We are not normally using W/D/R No as a standard practice.

 

It might be in process of the CRO that is the problem, is there any material that I could check?

Reply


Terms & ConditionsCookie settings