Notification / order

[MTerence]

Hi

My clients requires these things....

1. Notification should not be closed without a order.

2. When u create a notification, order should be created at the back ground....

is there any solutions for this...

I heard there should be some work witht he abapers... thats why

Rgds

Pithan

[paul_meehan]

Hi,

Alternative method would be to assign user status profile to your notifications. Set an initial status value that does not allow notification close. Configure the user status profile so that when a order is assigned the initial status is cleared and another status is set (for example CHKD). The user status configuration should prevent notification close unless the status CHKD is set.

This will be all automated through the status control functionality - See transaction OIBS for setting up the status profile.

In case of notifications that do not need any order the user status CHKD will have to be set manually. Ensure only limited users have relevant authorization for B_USERSTAT to allow making manual status changes. Other users will not be able to change the status manually.

Check SAP Help and this forum for more information on user status functions.

-Paul

[peter_atkin]

Pithan,

I'm assuming you mean TECO the order and not CLSD???

Why not change the process to close the order... You can then opt to close the notification at the same time. This is the normal process...

This way there will be no need for the ABAP development work.

PeteA

[MTerence]

Well Pete and rest

This is problem faced by the client...

Production department raises Notification, around 10 Notifications raised in a week, 3 are closed without orders.

It means there is no cost flow in that...

But in notification they have given breakdown with start and end time....

From the production department, they said its only for 3 hours so, nothing required for a order.

But the internal cost is not there for the order. During the Audit, Maintenance department was punished for not creating a order.

So they require, when they production dep creates a notification, they should not close it, if they close it also, there should be a order created...

They asked me can we do any of the two.. such that we can prevent these kind of problems

[peter_atkin]

Pithan,

Why not write a quick [user-exit|http://pjatkin.users.btopenworld.com/documents/PMCSUserExits.pdf] to check if there is an order assigned when closing a notification (NOCO). If not, then reject NOCO or save.

This could be via user-exits:

IWOC0002 Check whether status change is allowed

QQMA0014 Checks before saving a notification

QQMA0030 Check validity of status change

Or BADI NOTIF_EVENT_SAVE Change When Saving Notification

If you want to automate the creation of the order, then you will need to develop some code probably using QQMA0014 or NOTIF_EVENT_SAVE described above.

PeteA

[former_member192718]

Dear Pithan Pithan,

Some time you have to convince client for such requirement. Not to user exit, notes, BADI etc.

If order is not required for notification then order should not be created. If for any notification cost is going to be incuured during maintenance then only order to be created.

If notification can be closed with observation or without cost it must be closed without order.

Regards,

Kaushal Rai

[Former Member]

Hi Pithan:

I think from Business point of view creating order in the back ground from the notification is something wrong, as in some times after creating the notification you just discover that what you are asking for will be handled by a further PM orders so you just delete the notification....

[virendra_pal]

You could automatically create the notification by creating an order via configuration, however for creating order from notification you may have to carry out development on notification save to call function to create order