Skip to main content

When following the below test plan We are having a error in our background job.
Appreciate any clue why are we getting this error to solve it. 

TEST PLAN:

Create a Shop Order.
1. Duplicate the shop order> Lot size 1> Save.
2. Delete all material lines except the first material line( keep one material line)
3. RMB on SO Header> Release
4. RMB on SO header> Material actions> Issue

5. Shop Order> operations tab> RMB on operation line> Shop order Analysis > Details>
Analysis results window popup> Attributes tab
> nonconformities Column add1
> Non conforming column add 1


> RMB on the line> Complete registered Results> RMB on header> Confirm Registered Results

6. Navigate to Shop floor workbench> Enter as Team (any team in LOV)
> Refresh from button pane> Search for the newly created Shop order> Select the operation line>
Click Approve operation button> Ok
7. Receive Serialized parts window pop up
Tick the following
a. Close Shop order: Checked
b. Backflush: Checked 
c. Background job: Checked
Click OK.

8. Navigate back to shop order> Details tab>
Shop order status : Closed
> Observe Quantity> Completed quantity field  is getting 0 and
State> Products field : No Receive. 
But Shop Order is Closed


Error:
Background job “Receive shop order in background” run in to error
The operation "Issue" is not allowed for Shop Order objects in state "Closed".
ORA-20132: ShopOrd.NOTHANDLED2

Seems like before receiving shop order it is getting closed.
When we run this as online(without ticking Background job in  Receive Serialized parts window pop up) it Perfectly working fine. 

The error is getting popup when we trying to execute it through Background Job only.

This was tested on UPD12 env.

Yes sounds like the logic tries to issue the material (backflush) after closing the order. You may need to raise a support ticket for this. However, since you issued the material in step 4 there should be nothing else to issue I guess?


Yes sounds like the logic tries to issue the material (backflush) after closing the order. You may need to raise a support ticket for this. However, since you issued the material in step 4 there should be nothing else to issue I guess?

Yes Björn Hultgren

This issue rectified as in the latest release(UPD15) as well, Support case has raised and R&D is progressing with a solution


Reply