Issue with TECO the Emergency Work orders

[Former Member]

Hi Experts,

Configuration settings have been maintained for Notification and Order type combination. Example, N1 to O1, N2 to O2 N3 to O3 and so on.

However, Business have created Order of type O2 with Notification N1 type. And the Order is been released too manually (no jobs).

When Business are trying to do TECO for O2 type, they are unable to proceed.

We tried to replicate the Order - Notification combination, but couldn't due to configuration settings.

we also, tried to create Notification N1 from Order O2, but system created N2 notification by default due to configuration settings again.

Request your help in understanding , how the O2 created with N1 type can be TECOed and Closed in Production system.

Thanks in advance

Surya

[Former Member]

Hi,

Thank you Sebastian.

@Maria - You are right we are trying to create emergency work order through emergency notification and it was successful.

Eg: Business is trying to create Emergency order O1 with emergency order type ORD1 through Emergency notification N1 of type NOT1.

But Here unfortunately, Business has created an order O1 with Non emergency order type ORD2 through Emergency notification N1 of type NOT1.

Now they are unable to close the order O1.

Is there any way to close this kind of order O1 with type ORD2.

Please suggest on the same.

Thanks in Advance

Surya

[rakesh_mane]

Hello,

Please decouple the Emergency notification N1 of type NOT1 from order O1 with Non emergency order type ORD2 .and then try to TECO the Non emergency order type ORD2.

Br

Rakesh

[MTerence]

Hi Surya,

Removing Notification from Work Order

1. Go to Work Order, Click Objects Tab

2. Add the new notification in the objects

3. Select the line item and click (Define Header Notification)

System message will be displayed as the header notification is changed.

4. Save the work order

5. Again go into work order

6. Select the old notification line item and click delete, this will be removed.

Kindly let me know in case if you have any issues.

Regards

Terence

[Former Member]

Hi All,

Thanks for the responses.

We could understand the issue and customizations attached to emergency work orders.

we can create and change only ORD1, ORD2 and ORD3 order types for notifications with type NOT1.

Is there any other way to TECO the orders which are other than ORD1, ORD2 and ORD3 attached to notification type NOT1.

For example: Can ABAP create a little report that is able to override the error messages and TECO the orders?  Is there a way to change the status to TECO by entering the SAP table making the change there?

Thanks in Advance

Surya

[MTerence]

Hi Surya,

Its all possible. Abaper's can debug the client and change the Table entry. But this is highly not recommended.

Earlier i have done couple of Table entry deletion to overcome the error message, after which we will be closing the order immediately.

You can discuss with Abaper, so he can advice, also this depends whether client is aware on this request, may be certain cases they will not approve.

If your client approves, your abaper can work on it. You can do a testing in dev client with similar scenario.

Regards

Terence

[Former Member]

Hi All,

We have reached out to ABAPer for the same. we found that due to some of the customizations in the internal custom program it was giving error.

Example:

we can create and change only ORD1, ORD2 and ORD3 emergency orders order types for notifications with type NOT1, when user ID is maintained in custom table TAB1.

To TECO the orders which are other than ORD1, ORD2 and ORD3 attached to notification type NOT1, the user ID should be removed from custom table TAB1 used to maintain the User ID.

Thanks for the help

Surya

[Former Member]

Hi,

Please find the screen shot for error msg.

Please help us on the same.

Thanks in Advance

Surya

[rakesh_mane]

Hello

It seems you don't have authorization to carry out TECO for work order.

Br

Rakesh

[sebastian_lenartowicz]

Greetings Surya,

The message must be a customised check - please have a look at the user exit IWO10009 PM Order: Customer Check for 'Save' Event and you can drill through to the relevant component, function module and include to look at the ABAP code of the enhancement and infer what is the issue, or speak to your ABAP team or PM Solution Architect.

It's not something we can help you with here at SCN as we do not know your customisations.

[MTerence]

Hi Surya,

As per the screenshot, you are creating emergency work order and trying to release it at a stretch.

I prefer you to save the work order with out releasing (clicking the green flag).

This is an internal restriction provided to users via security access, as you are not allowed to release only to save.

Regards

Terence

[MTerence]

Hi Surya,

Even though you have Notification and Work Order Combination, you will be allowed to change the order type while creating the Order, system will not throw any error.

Also on TECO also i didn't get any error by replicating this.

I request you to check whether there is any custom check or enchancement done on TECO to check the notification and Order Combination.

Post the error message, so we can conclude the result.

Regards

Terence

[Former Member]

Hi Surya,

Could you please let me know what is the error you are getting any message appearing while doing the action?

BR,

Bhanu.