cancel
Showing results for 
Search instead for 
Did you mean: 

Permit in PM Order

Former Member
0 Kudos


Hi Gurus

We have controlled the total cost in PM order in order type PM01  by applying the permit method, but now we have found the users can override this control by the method  given below.

IW31 - While creating the order the user enters the component "ABCD" with qty 5 nos. The order value exceeds the amount in permit specified .

The user  then changes the qty to 2 and  now the value  of the order is  within the specified permit limit  and the system allows the user to  release the order. After releasing the order and without saving  the user goes back to the component tab and changes the qty to 5 nos and saves the order.

Even though the order is released , and the qty is changed, the system should check the permit value and should not allow the user to save

the order.

Is there any  method to over come this issue. Pls help

Regards

Vidhyadharan

Accepted Solutions (1)

Accepted Solutions (1)

peter_atkin
Active Contributor
0 Kudos

Vidhyadharan

This scenario applies to labour and purchase changes too.

You would only be able to effectively control this via development.

I've done this a few ways in the past:

  1. Copy the planned costs to the estimated cost field at order RELEASE
  2. Copy the planned costs to a "Z" field on the Enhancement tab at order RELEASE
  3. Check the costs haven't changed between RELEASE and SAVE.

PeteA

Former Member
0 Kudos

Thanks Pete. Will talk to abapers about your idea , and will get back asap

Regards

Vidhyadharan


Answers (1)

Answers (1)

Former Member
0 Kudos

I am looking in other way around.

Its not possible to restrict the users to add any quantity / change the operation details once after release, whether he is doing intentionally or unintentionally.

In that case, you can have control with user status & permit functionality.

Keep 2 user statuses such as "Changes allowed" & "Changes are not allowed".

Keep "Changes Allowed" as Initial Status. Upon release of PM Order, change the status in to "Changes are not allowed" automatically using business transaction set option.

Give the control only to authorized people to set to "Changes allowed" user status. So, once after release, he can't change anything on his own.

But upon approval by changing the user status by authorized person, he can able to change.

You can use IWO10009 PM Order: Customer Check for 'Save' Event to achieve that. Again its a development.

AB
Contributor
0 Kudos
Its not possible to restrict the users to add any quantity / change the operation details once after release, whether he is doing intentionally or unintentionally.


Agreed  - it isn't realised in SAP standard. The building blocks are however there. The operation receives the status Released when the Order is released. It would be possible to influence the screen fields according to the status of the operation - but SAP hasn't chosen to do that.


Behind your comment is a whole discussion about the semantics of Released - what does Released mean and how should the Released status effect the ability to make changes to the order planning. It is a good discussion - but one for another thread.

Former Member
0 Kudos

I don't think so.

Whether Permit has created or not based on the cost, user can play around that by modifying the components / operation details.

That's the reason, I mentioned Intentionally or Unintentionally. So, it may add value if author looks in that perspective as well.

peter_atkin
Active Contributor
0 Kudos

Maheswaran KD

You suggestion using user-statuses/development/authorisations is much more complicated solution than noting the planned costs at RELEASE (user-exit IWO10002), then cross checking the planned costs at SAVE (IWO10009). If they are different, then reject the order SAVE. However, I agree that you may want some form of authorisation check to enable some users to bypass/approve the change.

You could possibly use the permit also, and compare the permit value with the planned costs at SAVE.

PeteA

Former Member
0 Kudos

Pete A,

As I am not ABAP guy, I can't comment on ABAP complication on developing this solution. But this will allow to have control with the possibility of making changes even after release.

peter_atkin
Active Contributor
0 Kudos

Agreed.. This is quite a difficult situation to control.

I've had a couple of clients want similar functionality as the release strategy in MM transactions - i.e. different authorisation levels dependent upon the planned cost level.

But as highlighted by Vidhyadharan, the users can bypass the check by keeping the costs low before release, then raising the costs after release. So we're back at the same point again...

One client then put additional restrictions in place after release if the planned costs were raised by a certain amount. But at what point do you stop the order being progressed..

Some things need to be controlled outside of the order processing. In this case possibly via exception reporting.

PeteA

Former Member
0 Kudos

I am really happy , that my point raised has led to good healthy discussion. Everybody had pitched in with their comments and suggestion.

Thanks once again for all your valuable inputs.

Regards

Vidhyadharan