Skip to Content

Restrict Work Order Creation to specific FLOCs

Hi,

I'd like to know if there is a way to restrict creation of notifications and/or work orders to specific FLOCs.

Our situation is that we don't necessarily want to allow people to create WO against higher levels of FLOCs.

And some FLOCs don't have equipments underneath them because there is just nothing to follow there (ex. meeting rooms)

So in order to make sure Work Orders aren't created against FLOCs that do have equipments under them we'd like to have some sort of rule that prevents the creation of Work Order against such FLOCs.

We would also use this rule to spot objects that have been created and do not have an ABC indicator assigned so we can assign one. But only on those where it is allowed to create a work order.

Feel free to ask questions, I know it might be difficult to understand the context.

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Posted on Jul 22, 2020 at 06:41 PM

    Hi, Pascal,

    you can accomplish this with the use of user statuses on the functional locations, linked to the limitation of business transactions. So 100 % customising.

    kind regards,

    Dirk

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 23, 2020 at 06:40 AM

    Pascal,

    As points out by Dirk above, you can resolve the higer-level FLoc issue with a user-status which forbids "Enter PM processing data" in transaction OIBS or SPRO.

    You can set the ABC indicator as mandatory through customising. Have a look at IMG element "Define Field Selection for Order Header Data (PM)" (OIAZ or SPRO) and set the ABC field as required in the Location/Account Assignment Data section.

    However, this only works if you enter the Location tab. So the only other option is to develop a solution, probably via user-exit IWO10009 (SMOD) or BADI WORKORDER_UPDATE (SE18).

    .

    PeteA

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.