Skip to main content
Question

Scrapped Service Objects – One Blocks New Request, One Doesn’t

  • December 5, 2025
  • 0 replies
  • 7 views

Forum|alt.badge.img+4

I'm working with two Service Objects in IFS, and both have an Operational Status of Scrapped. For one of the scrapped objects, IFS correctly prevents me from creating a new Service Request. However, for the other object—also marked Scrapped—I am still able to create a new request.

I would expect the behaviour to be consistent, so I'm trying to understand why one Scrapped object is blocked while the other still allows request creation. Is there another setting or dependency that controls this behaviour?

For service object 012125F15-PL107162560, I’m able to create a new request.

I do note that the operation status doesn’t seem to appear on the Service Object, despite existing on the Part Serial:

 

 

I’m able to create a new request for the above scrapped object.

 

I’m not able to create a request for service object WP3235-45-STKWP-358-34

 

It is not possible to connect the work task to a scrapped object

 

The other difference with these service objects are

012125F15-PL107162560 - came in through migration

WP3235-45-STKWP-358-34 - was not created through migration

 

This feels buggy to me.  Status Scrapped should prevent the creation of a new Request.

I would be grateful for any guidance on this.

 

Thank you,

Ed