Hi @PRODQ,

What’s the current IFS Cloud version and the service update that you are using?

Regards,

Nikila Dissanayake

We are 23.1.10.

Linda

Hi @PRODQ,

I have reviewed the behavior in IFS Cloud 23R1 and the latest 24R1 release, and I observed the same issue across both versions. Specifically, once the PO line is saved, any changes made to the supplier’s purchase part description in the corresponding window are not reflected.

Given this consistent behavior across versions, it seems that this may be more of an enhancement opportunity rather than a bug in the system.

Regards,

Nikila Dissanayake

Hi @PRODQ,

I have reviewed the behavior in IFS Cloud 23R1 and the latest 24R1 release, and I observed the same issue across both versions. Specifically, once the PO line is saved, any changes made to the supplier’s purchase part description in the corresponding window are not reflected.

Given this consistent behavior across versions, it seems that this may be more of an enhancement opportunity rather than a bug in the system.

Regards,

Nikila Dissanayake

Thanks, @Nikila Dis .  Sadly this comes under the heading of yet another “it worked fine in Apps9, why has it changed in Cloud”.  I’ll raise a Support case and see where I get to.

Linda

Hi @PRODQ 

Yes, Please raise a ticket.

Regards,

Nikila Dissanayake

From RND I can confirm that this is the expected behavior considering changes done during the Apps 10 project, where Supplier´s Part No and Supplier´s Part Description are now saved on the PO line, which was not the case earlier. There is a detailed explanation to be found in the LCS solution 287656 as follows:

It can be confirmed that there is a difference between Apps 8 and Apps 10 since design changes were done
during the Apps 10 project to support a number of uses cases where it is necessary that the Supplier´s
Part No is saved on the PO line. In previous releases this was not the case, which is why the system
behaved as you describe where an update in Supplier for Purchase Part would always be reflected in the
PO line. But if you study the solution 264840, this describes a negative effect of the old behaviour
where we could never keep historical data. But the main reason for the design changes was to support
functionality where the Supplier´s Part No is received from the supplier through some kind of integration
or message, and that this information needs to be transferred to the PO line and consequently saved there.
You can also see the effect if you perform the Confirm PO or PO Line with Differences, that it is possible
to enter the Supplier´s Part No and Description there, which was not possible in previous releases.
So this is not a question of contradictory between the releases. The design is different because of deliberate
design decisions done during the Apps 10 project. Since the Part No and description are now saved on the
PO line, the behavior that a change in Supplier for Purchase Part would automatically be reflected in
the PO line no longer exists, since we cannot have both. In the Supply Chain News presentation for
Apps 10 that you can find in sharepoint under Release Documents and Links, there is information mentioned
in slides 330-332 about the new functionality.

Thanks for the update.  We went direct from Apps9 to Cloud so weren’t aware of the change.    

However, operationally, this is a retrograde step as we will now be sending Purchase Orders to suppliers quoting their wrong Part number or Description.

I’ve raised a case - CS0315347 - to pursue a change, Eva.

Linda

I’m not sure if there is any mechanism for changing my “Question” into an “Idea” but at the request of ​@Janani Munasinghe I will raise my suggestion as an idea for R N D to consider

My question regarding 'update function' was to
- introduce a button in the Purchase Order screen - PO header or line - which user clicks and this invokes a 'fetch' of whatever data is in the Supplier for Pur Part/Supplier Part no and Description and performs an "update" (ie overwrite)to the Supplier Part no and Description fields on the PO line/s selected. That way you could have a date/time/user stamp of when the record was changed.

OR

- introduce a button on the Supplier for Purchase Part record that performed the same update/overwrite on any open Purchase Orders - Planned and/or Released and/or Confirmed POs?

In either case have a rule which prevents this from being done where the PO line is identified as having been created off the back of a schedule/import?

Just a thought!

Linda

From: Linda Shaw
Sent: Thursday, November 21, 2024 8:55 AM
To: IFS Support <ifs.support@ifs.com>
Cc: janani.munasinghe@ifs.com
Subject: RE: CS0315347 - Open POs not updating with changes to Supplier for Purchase Part/Supplier Part/Description

Hi Janina

Thanks for the update. Find and replace is an OK-ish workaround. If it worked on PO Lines screen it would be more palatable.

Would R n D consider the option of introducing an ‘update’ function? Users could choose to re-fetch the Supplier Part Number/Description for open order lines – either run off PO lines or off the Supplier for PP record - that was perhaps disabled for those POs which had been created off the back of a schedule/import (which I think were the reason this functionality has been disabled?). Then, at least, there would be an option where required – like for us – as well as giving a formal date/time-stamp for the activity?