I have a client who is utilizing intersite functionality to direct ship material to an external customer on behalf on another site. Everything is flowing normally, except when the PO lines have a receive case of “Receive into Arrival, Inspect at Arrival”. At this point, they do not want to use an alternate receive case.
The Direct Delivery is being processed by the intersite flow. The PO lines are updating to “Closed” status but the Receipt Lines are in “To Be inspected”. In order to complete the Register Inspection Results the PO Lines have to be manually reopened.
I would not expect the PO Line to close without the Register Inspection Results completed. Is this the expected behavior?
The client is on 22R1.8
Page 1 / 1
Hi,
Sorry but I need additional clarification here. If the flow is a Direct Delivery, the internal PO is not really receiving anything physically. Then, what kind of inspection would be required if the parts were directly delivered to the customer?
Could you please provide the Supply Chain Order Analysis and clarify this?
Regards,
Pilar
Hi,
Very similar case here. But “To be Inspected” status is set by mistake. User filled and saved “Qty to Inspect”. Now he wants to undo this. 0 value doesn’t want to save, same as approving inspection Any ideas?
BR, Lukasz
Hi @IC-LukaszP ,
I have tried to find a similar example in an App9 Core environment, as your screenshot is from that version, with the same Demand Code. Then, I tried to follow up your steps, but in my case there is no error being raised when approving inspection results or when trying to change the Qty to Inspect value to 0.
I also tried the same in IFS Cloud 22R1, but in my case an error is raised when trying to change the Qty to Inspect to any value in the Receipt:
I recommend you to report this issue in a Support case, so this can be investigated further.
Regards,
Pilar
Hi @Pilar Franco ,
Thanks for checking this on APP9 environment. Meanwhile, I also checked, and confirmed on some different APP9. It is possible to fill qty to inspect = 1, save and then fill = 0 and save. No limitations.
So this error message from the screenshot might originate in some customization or custom event. Anyway, thanks for your feedback.
