Delete button is inactive for Service confirmation

[Former Member]

Hi,

We are in SRM4.0,Classic scenerio

We have a requirement to delete the Service Entry Sheet from EBP in the same way as the goods confirmation can be deleted from EBP .Button 'Delete' should be activated for Service Entry Sheet same as goods confirmation.

How can I activate Delete button for Service entry sheet or else Is that possible to create a button "Delete" for the same functionality

Please give your input on it.

Regards,

Sammeta

Edited by: S Neelima on Feb 16, 2010 8:03 AM

[Former Member]

Hi Neelima,

This is the Standard functionality given by SAP.

Service Confirmations can not be deleted if there is Realease Procedure for the Services defined in the backend system.

The only way to acheive this functioanlity is by developing a custom code and activate the delete Button and give the required Functionality(Enabling Delete Button)

Thanks

Sunil.

[Former Member]

hi,

any inputs???

regards,

sammeta

Edited by: S Neelima on Feb 17, 2010 6:07 AM

[matteo_montalto]

Hi sammeta,

first of all, try to use the SAPgui transaction initially just to identify dynpro used in the process.

Second thing: I didn't understand clearly the scenario; do you want to:

- modify the behaviour of an already present button

OR

- create a new button from scratch.

Case 1: you should first of all identify the screen dynpro in which the button is located. Then by se80 transaction you can look for the underlying logic; if the button is sometimes active and sometimes not, probably in the logic modules you will see that the active indicator is conditioned by some constraints. More difficult to describe it on a post than to see it.

Example: buttons can have some attributes in the GROUPx fields (in which obviously x is a digit, from 1 ascending) and in the logic code we could say that "buttons which belongs to GROUP2 = 'EDI' are only avaiable when in EDIT mode, otherwise they are disabled".

Case 2: same as before, you should identify the dynpro screen in which your new button should be created. Then edit that dynpro and via Graphical Screen Painter (-> Layout) you can define a new custom button. Then you should characterize both button's behaviour (see above) AND opcode associated.

I know these are just 2 cents but the complete procedure could not be synthesized in a simple text guide; moreover, it's just a starting point for your analysis. Lots of debugging could help understanding how buttons works and insert a brand new button in a standard dynpro should be done in a way it should behave like a standard one.

Best regards

[Former Member]

This message was moderated.

[Former Member]

Hi kedar,

We have already applied this OSS note but still we are not able to achive the requirment.

We have raised this issue to SAP, they respond responded that the Delete Button cannot be activated as u201CCancel is possible only if release strategy in backend system is not defined .Hence a workaround solution via a custom transaction is sought to be implemented.u201D

Regards,

Neelima