08-28-2007 1:05 PM
Hi fellows!
Does anyone knows how to assure, in a user-exit for IW22 transaction, that the SAVE function was called?
Can it be made by BADI? Which implementation may I have to use.
Thank you.
08-28-2007 1:15 PM
08-28-2007 1:08 PM
BADI Definition: NOTIF_EVENT_SAVE
Method Name: CHANGE_DATA_AT_SAVE
08-28-2007 1:15 PM
08-28-2007 1:27 PM
Hi.
In MM tcodes ME21/22/23, i have a user-exit for the item validation and another for header validation. That i am used to, but the exit's for PM transactions seems not to work like this.
08-28-2007 1:57 PM
Hi,
Goto Function Group XQQM.All the customer exits including BADI for notifications have been included in that FG.
Goto SPRO ->Plant Maintenance and Customer Service->System Enhancements and Date Transfer..you can find the exits along with documentation
reward if helpful
thanks
08-28-2007 2:51 PM
08-28-2007 2:56 PM
Flavio,
Would still recommend you look at the BADi solution.
All the requried actiivities, items and tasks are populated along with the header.
You can also set up filters to limit your validations to only particular notification types.
08-28-2007 5:10 PM
My version of R/3 is 46D and i am afraid that this BADi isn't available.
But thank you for reply.
08-28-2007 1:31 PM
Hi,
User exits for IW22 are
IWO10026 User check on setting status 'Do not perform'
IWO10027 User exit: Generate user-defined settlement rule
IWOC0001 Create PM/SM notification: Determine reference object
IWOC0002 PM/SM notification: Check whether status change is allowed
IWOC0003 PM/SM authorization check of ref. object and planner group
IWOC0004 Change single-level list editing PM/QM/SM ALV settings
Regards
Sudheer