cancel
Showing results for 
Search instead for 
Did you mean: 

Creating PM Orders and Confirmations Simultaneously

Former Member
0 Kudos

Hi to all experts,

I will be so glad if I can find an answer for my ask.

Is there any possibility on PM Module to create automatically confirmations for orders at the same time when an order is tried to create by someone?

Thanks in advance.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

Maintenance Orders will be created with the operations with Planned hours. Once task is completed, then we can go for either operation wise confirmation or complete confirmation.

Why you want to create the confirmation automatically at the time of order creation? As planned hours & actual hours would not same practically, we can see the variance in terms of duration & cost.

Please state your actual requirement, so that it is possible to suggest some solution.

Regards,

Maheswaran.

Former Member
0 Kudos

Thanks so much for this quick response.

In our case, PM orders will be created in the system after maintenance operations is completed. Planned hours ( or any other data about planning if there is on PM module) will not be used ( or stored) in our processes. They say, they do not need for differences ( or variances ) between planned and actual cases (situations). They only want to track (check or see) in the system ( with helps of created orders and confirmations) if the status of an operation is completed or open.

Former Member
0 Kudos

Hi,

You can use BAPI_ALM_CONF_CREATE to create the confirmation for the Maintenance Order.

Go to T-Code BAPI & check under Plant Maintenance. You can find the required BAPIs.

Enter the operation actual duration / work in planned duration / work column. Based on that, confirmation can be created.

Use this User Exit.

IWO10009 PM Order: Customer Check for 'Save' Event

While saving the order, based on the Maintenance Order status (REL - Released), using above mentioned Functional Module, confimation can be created automatically.

The checks would be,

1. Whether order is having Internal Operation (as only for internal operations, confirmation will be done)

2. Actual duration / work has been entered against each internal operation.

3. Order status is Released.

Regards,

Maheswaran.

Edited by: Maheswaran.K on Apr 22, 2011 10:17 AM

Former Member
0 Kudos

Maheswaran, your answers are so valuable to solve my problem. Thank you very much for your close concern.

My mind is a little confused about using of these BAPI and the user exit that you have offered.

If I do not understand it wrong, you are offering me to use that BAPI in that user exit with a condition of the status of the order.

I understand that, if the status of the order is REL : Released, then the system (in IWO10009 ) should call the BAPI ( BAPI_ALM_CONF_CREATE ) to create the confirmation? But when I check the backside ( codes ) of the order creation program (IW31), I see that the system assigns the " REL : Released" status to the order after that user exit ( IWO10009) with a perform which is named "release_order".

Can having a status as "Created" be enough for an order to use that BAPI in that user exit?

Thank you very much again for your suggestions.

Former Member
0 Kudos

Hi,

Then you have to do in Creation mode itself. Else try for this alternative solution.

1. Create the New Order type which is required to create the Confirmation immediately after Order creation. So that, it will not affect other order types which are following normal process, if any.

2. The reason behind that Released status is that, even Preventive Order can be created immediately by automatic scheduling. But those orders would be confirmed after actual execution. So you can go for one Z-transaction, where user can select the orders which are in released status & with particular order type. So that, other orders will follow normal process.

But that 2nd point is alomst like doing manual activity of doing confirmation. Check with your client & opt for better solution.

Regards,

Maheswaran.

Former Member
0 Kudos

Maheswaran, thank you again for your helps.

The timing (place) of the exit that you have offered looks like so early to use that confirmation creater BAPI.

After adding this BAPI into the include, the system begun not to create any order in IW31.

Needed an exit ( if there is) maybe a few rows after (later) than IWO10009, at least at the time when the system assigns the order number to the order which is tried to create on IW31.

Thank you again.

peter_atkin
Active Contributor
0 Kudos

Have a look at BADI WORKORDER_UPDATE or user-exit PPCO0001 (Application development: PP orders)

PeteA

Former Member
0 Kudos

Thank you Pete for your all quick returnings.

Could it be possible for you to suggest me another exit for the same aim? There is a necessary for exits offered about having "REL : Released" status for the order, to use the BAPI explained above in any of them.

I do not have any result for the BADI that you have offered since I could not have a chance to try it yet.

Thank you very much again.

former_member187991
Active Contributor
0 Kudos

Hi

Can you check the user exit IWO10002 PM maintenance order: Customer check for order release where you can place the BAPI for creating confirmation ( I am not sure ,kindly check and confirm )

Regards

Thyagarajan

peter_atkin
Active Contributor
0 Kudos

Mustafa,

You can either get the status from ABAP memory using standard function modules, or try using the IPHAS field (AFIH)

PeteA

Former Member
0 Kudos

Thanks for the advice.

The program (IW31) does not stop at that user-exit ( IWO10002 ).

peter_atkin
Active Contributor
0 Kudos

It will stop at IWO10002 when the order is released (REL), but I don't think its any use for creating confirmations at this point as the order will still e locked.

PeteA

Former Member
0 Kudos

I would like to thank to all responders in the thread. And thank you so much Pete.

As you have shared, the system does not allow to create confirmations while saving orders because of the locking.

It does not seem possible to create confirmations with helps of any user-exit on IW31.

Thanks again for all answers. I have given your forum points from the top.

Regards,

Mustafa

peter_atkin
Active Contributor
0 Kudos

Mustafa,

Did you find a solution?

PeteA

Former Member
0 Kudos

Pete,

My apologies for not replying sooner.

The problem was solved by my senior colleague whom I fell in love with cause of his skills, abilities that provide us practical solutions for many impossible things.

He has built a relation between PM orders ( fresh created) and a Z-function module ( which is created for the solution and including the BAPI that mentioned above posts) with a similar approach as in workflows.

At every creation of PM orders, this Z-Function module is triggered to run since it supposes these objects (orders) as its trigger events.

Regards.

Mustafa

peter_atkin
Active Contributor
0 Kudos

Thanks Mustafa,

I'm guessing that you used the BADI to kick-off a synchronous workflow task which calls a customer-specific function module.

We've used this method before too.

PeteA

Former Member
0 Kudos

Another late answer from me Pete,

We did not used any BADI for the solution. Only a customer-specific function module ( which contains the BAPI_ALM_CONF_CREATE ) was defined as a receiver function module to be triggered after releasing of the PM Order object ( BUS2007, "RELEASED" ) in the transaction code "SWETYPV" ( EVENT TYPE LINKAGES ).

peter_atkin
Active Contributor
0 Kudos

OK Mustafa, the end result is the same..

Thanks for your feedback

PeteA

Answers (0)