Connecting shipment with package parts

Hi @caveman022 ,

In the problematic customer order line, has the shipment successfully connected when it was initially released?

Can you explain the trigger that lead to the error message? What details were you trying to edit (ex: quantity or part no)? 

Elaborating the scenario further along with a screenshot of the error message will be helpful to identify the issue.

Regards,
Kethaka

Hi @caveman022 ,

As my colleague has said, with more detail of the flow implemented in the customer order line, it would be a more clear picture of the problem.

But just with the information provided I can only suppose that the supply code for your package part components is Internal Purchase Direct. So then, if the components have already been supplied, then internal customer order line is already in Delivered status and cannot accept any more changes.

Regards,

Pilar

I am having exactly the same issue where new package part lines cannot be added to a customer order that has been released. In this case the Released line on the order is a configured sales part with supply code  ‘Shop Order’ and the cancelled line is a package part with three configured components,  all of which have supply code of ‘Shop order’. The shipment that just contains the one line of sales part is at preliminary status. When I try and add a new line to the order that is a package part with three configured components (same part as the cancelled line) I get this error message.  There are no Internal Purchase Direct Supply lines on this order (or on any customer order in the application as internal supply is not used anywhere by this customer)

Hi @AntJeremF ,

Then, if that’s the case, better to create a Support ticket in Service Center with all the details so it can be investigated from Support.

Regards,

Pilar

A support case has been raised with IFS to investigate this issue.

Case ID: CS0309564

Hi @AntJeremF ,

Fine, then my colleague from Support will investigate and try to provide solution for this.

Regards,

Pilar

Hi ​@caveman022 / ​@AntJeremF ,

Above issue has been corrected in the latest APP10 update. UPD26 via Bug ID 169408.

Thanks,

Sayuri.