+3
Hello,
We encounter an error when running the Execute step of the rental transfer between 2 different projects.
At the "Execute" step, an error message appears: "Only Receive into Arrival and Inspect at Arrival are allowed for non-inventory parts."
The item used in the test is an inventory item.
The error doesn't seem to correspond to the situation.
Have you encountered this situation before?
Thanks for your help
HI
+8I’m currently experiencing the same issue in 25R1. Is there any smart person aware of the solution? 😁
+14Hi All,
Based on the information available from our internal sources, the error message "Only Receive into Arrival and Inspect at Arrival are allowed for non-inventory parts" (or similar variations such as "Only Receive into Arrival is allowed for non-inventory parts") represents a standard system validation in IFS that controls how non-inventory parts are processed during arrival and return transactions.
For non-inventory parts, the system restricts the Receive Case to Receive into Arrival (and, where applicable, Inspect at Arrival). This behavior exists because non-inventory parts are not intended to be received into inventory, tracked as stock, or processed through standard inventory inspection.
Also in rental scenarios involving non-inventory parts connected to projects, users may encounter validation messages stating that certain flows (like creating replacement orders) are restricted, as the system often expects "Inventory Order" or "Non-inventory" demand codes rather than "Project Inventory
Key behaviors and rules include:
However, in the reported scenario, the part used in the rental transfer is confirmed to be an inventory part. Therefore, this validation should not normally be triggered as I guess. Can you one of you raise a support ticket with a clear test plan so we can look into this.
Regards,
Nikila Dissanayake
+8Hi All,
Based on the information available from our internal sources, the error message "Only Receive into Arrival and Inspect at Arrival are allowed for non-inventory parts" (or similar variations such as "Only Receive into Arrival is allowed for non-inventory parts") represents a standard system validation in IFS that controls how non-inventory parts are processed during arrival and return transactions.
For non-inventory parts, the system restricts the Receive Case to Receive into Arrival (and, where applicable, Inspect at Arrival). This behavior exists because non-inventory parts are not intended to be received into inventory, tracked as stock, or processed through standard inventory inspection.
Also in rental scenarios involving non-inventory parts connected to projects, users may encounter validation messages stating that certain flows (like creating replacement orders) are restricted, as the system often expects "Inventory Order" or "Non-inventory" demand codes rather than "Project Inventory
Key behaviors and rules include:
However, in the reported scenario, the part used in the rental transfer is confirmed to be an inventory part. Therefore, this validation should not normally be triggered as I guess. Can you one of you raise a support ticket with a clear test plan so we can look into this.
Regards,
Nikila Dissanayake
There was a support ticket created CS0538612, but this one just got closed since the customer is on 24r1 release and that is not supported according the contract….
So i will create a new one for my customer, which is in 25R1. will update the case number when it has been created.
Hi All,
Based on the information available from our internal sources, the error message "Only Receive into Arrival and Inspect at Arrival are allowed for non-inventory parts" (or similar variations such as "Only Receive into Arrival is allowed for non-inventory parts") represents a standard system validation in IFS that controls how non-inventory parts are processed during arrival and return transactions.
For non-inventory parts, the system restricts the Receive Case to Receive into Arrival (and, where applicable, Inspect at Arrival). This behavior exists because non-inventory parts are not intended to be received into inventory, tracked as stock, or processed through standard inventory inspection.
Also in rental scenarios involving non-inventory parts connected to projects, users may encounter validation messages stating that certain flows (like creating replacement orders) are restricted, as the system often expects "Inventory Order" or "Non-inventory" demand codes rather than "Project Inventory
Key behaviors and rules include:
However, in the reported scenario, the part used in the rental transfer is confirmed to be an inventory part. Therefore, this validation should not normally be triggered as I guess. Can you one of you raise a support ticket with a clear test plan so we can look into this.
Regards,
Nikila Dissanayake
There was a support ticket created CS0538612, but this one just got closed since the customer is on 24r1 release and that is not supported according the contract….
So i will create a new one for my customer, which is in 25R1. will update the case number when it has been created.
Hi, to clarify, the support case CS0538612 mentioned above was actually raised by us. As we are currently planning our upgrade to 25R1, we would greatly appreciate if any further insights or updates on this issue and to share them here. Thank you.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
