Skip to main content

Hi All,

 

Please let me know why the UOM from source is not fetched to the part lines in the incoming dispatch advice. This is for App10. 

The UOM is fetching to part lines from source in App9.

 

Test

  • Go to Incoming Dispatch Advice window
  • From available source line select one of line that has the source UOM
  • RMB and click connect part lines
  • Then move to the Part Line tab, selected Part has been assigned to the incoming dispatch advice, but source UOM is missing

 

Thanks.

Hi @Dilrukshi 

I’ve tested it in IFS Apps 10. Same issue.

Hi @Link, thanks for the feedback, did you find a reason for this?

Hi @Dilrukshi 

I have not had the opportunity to analyze it until now.

And in IFS Apps9 it works?

Hi @Link , yes is works in APP9

Hi @Dilrukshi 

as I understand it correctly the value (Source UoM) from Part Lines doesn’t come from the tab Available Source Lines but from another object. This is my assumption.

How do you generate an Incoming Dispatch Advice? 

Hi @Link , it was created from an inter-site purchase order.

It seems the source UoM is only fetched for automatic flows like inter-site and inbound messages.

But the system will not fetch it when connecting the part lines manually.

So I would recommend to create a task to RnD to rectify this.

 

Hi Rigslrosh,

Thanks for your feedback.

Let me check with RnD as well.

It seems the source UoM is only fetched for automatic flows like inter-site and inbound messages.

But the system will not fetch it when connecting the part lines manually.

So I would recommend to create a task to RnD to rectify this.

 

Exactly, I’ve also noticed this.

As per the investigation in different UPDs of APP9 and APP10 environments, it can be concluded that; although the UoM was previously fetched to part line tab (in App9), the source UoM from available part lines to part lines tab is not fetching after App10 and this is the standard system behavior.

Reply


Terms & ConditionsCookie settings