Skip to main content
Solved

Hide Parts in IFS - Based on the Description

  • July 18, 2025
  • 5 replies
  • 88 views
Asela Munasinghe
Superhero (Customer)
Forum|alt.badge.img+23

Dear All 

Hope you are doing great - ready for the weekend. 

Just checking if someone is using a setup in IFS where we can hide some parts according to the part description  [containing part description text **DO NOT USE** for instance] . For instance, we have obsolete parts at N-Sea with the part status obsolete or inactive. But still cannot hide them when creating demands on projects. IFS will of course not let us create demands for such part statuses. But ideally I want to hide those parts when fetched onto a list of values. I tried several configurations like custom fields and saved searches according to the status. But seems hiding them on new demands are not supported. 

Of course I might be able to do this with a customization in IFS. But before that, I am trying to figure out if I have missed a trick. 

Happy Weekend! 

Asela

Best answer by Abdul

Hi ​@Asela Munasinghe,

I will share one of my customers’ experiences. 

The customer has implemented the Purchase Order Authorization functionality, and therefore, PO authorization is mandatory before starting any transactions against any PO. However, the SCM department was able to raise advance manual supplier invoice even before authorization. 

To stop this practice, we modified the View condition directly for the PO Reference LoV (purchase_order_mc_lov) available at the manual supplier invoice level.

Standard Where condition: rowstate != 'Cancelled'

Modified Where condition: rowstate NOT IN ('Cancelled','Planned','Stopped')

After modified Where condition implementation, SCM is not able to select the PO at the manual supplier invoice until not authorized or Released.

Likewise, any new Where condition as per business requirement can enabled for any standard LoV with the help of internal technical resources.

 

Regards

Abdul Rehman

 

https://www.linkedin.com/in/asela61/
Vimukthi Mahakumbura
Grzegorz Byrski

5 replies

PRODQ
Superhero (Customer)
Forum|alt.badge.img+18
  • PRODQ
  • Superhero (Customer)
  • July 18, 2025

Just a thought … Hide for who?  Do you want to hide?  What if someone tries to create a part number you’ve hidden … because it’s hidden?  They’ll get caught in an eternal loop of not being able to save because the part already exists but won’t know why because they can’t see it?

Could you add “Part Status” field to the Project Demand screen and/or conditionally format if obsolete or DNU?

 

Linda

Linda
Asela Munasinghe
Abdul
Superhero (Partner)
Forum|alt.badge.img+20
  • Abdul
  • Superhero (Partner)
  • Answer
  • July 18, 2025

Hi ​@Asela Munasinghe,

I will share one of my customers’ experiences. 

The customer has implemented the Purchase Order Authorization functionality, and therefore, PO authorization is mandatory before starting any transactions against any PO. However, the SCM department was able to raise advance manual supplier invoice even before authorization. 

To stop this practice, we modified the View condition directly for the PO Reference LoV (purchase_order_mc_lov) available at the manual supplier invoice level.

Standard Where condition: rowstate != 'Cancelled'

Modified Where condition: rowstate NOT IN ('Cancelled','Planned','Stopped')

After modified Where condition implementation, SCM is not able to select the PO at the manual supplier invoice until not authorized or Released.

Likewise, any new Where condition as per business requirement can enabled for any standard LoV with the help of internal technical resources.

 

Regards

Abdul Rehman

 

https://www.linkedin.com/in/abdul-rehman-ifscloudexpert/
Vimukthi Mahakumbura
Asela Munasinghe
Asela Munasinghe
Superhero (Customer)
Forum|alt.badge.img+23
  • Asela Munasinghe
  • Author
  • Superhero (Customer)
  • July 19, 2025

Hi ​@PRODQ 

Thanks for the reply. I need to hide like explained below:

When someone tries to create a new demand line and parts with the description **DO NOT USE** shouldn't show up

We've actually tried Part status in new demand creation as a cf, but seems that projection dosen't allow cfs. 

 



Unfortunately conditional formatting isn't enough since we want to actually hide the parts. 

And part no.s wont be a problem here since we would use the system generated new numbers during creation. 

Hi ​@Abdul 

Actually your idea is interesting - to enable a Where condition for the LOV. I will try to test it out. Do you think it might be possible in the above scenario? Thank You very much. 

Thanks,
Asela

https://www.linkedin.com/in/asela61/
Grzegorz Byrski
Abdul
Superhero (Partner)
Forum|alt.badge.img+20
  • Abdul
  • Superhero (Partner)
  • July 19, 2025

Hi ​@Asela Munasinghe,

Yes, it should work. Since the Where condition would exclude all Obsolete parts, and obsolete parts would no longer be available for selection.

 

Regards

Abdul Rehman

https://www.linkedin.com/in/abdul-rehman-ifscloudexpert/
Vimukthi Mahakumbura
Asela Munasinghe
Superhero (Customer)
Forum|alt.badge.img+23
  • Asela Munasinghe
  • Author
  • Superhero (Customer)
  • August 1, 2025

Thanks ​@Abdul , this helps. 

 

https://www.linkedin.com/in/asela61/
Abdul
Terms & ConditionsCookie settingsAccessibility statement