Need BAdI or User Exit to disable Save Button in CK11N TCode.

[ricardo_fernndezvzquez3]

Hello SAPients!

I've been looking for a User Exit (apparently there's none) or BAdI (apparently they're not used for that purpose) that allows me to disable the Save Button in the TCode CK11N. Anyone knows?

Or, maybe you can propose something else to achieve this same goal.

Thanks in advance for your kind help.

[RJSA]

Hi Ricardo,

There are Exits/BAdI for this transaction below, but I think you can not disable the "button save".

Maybe there is a way for enhancement, but don't think so...

But I don't understand what the function of the transaction does not have the button save...

What is the reason?

BAdI Definitions:

BADI_MARKING_ADD_PRICES_ML

CK_KALAMATCON2_CI

CO_PROD_COSTING_CK

COPC_CK_MCSO

COPCMESSAGECONTROL

COPCMESSAGECONTROL

COST_ESTIMATE

COST_ESTIMATE

COSTING_COMPONENT

COSTING_COMPONENT

COSTINGRUN_CK

DATA_EXTENSION_CK

DELIVERY_COSTS_ASSIGNMENT_CK

DYNPRO_EXTENSION_CK

ECP_ADD_FUNCTIONS_CK

EXTERNAL_OPERATION_VAL_CK

GUI_ITEMIZATION_CK

GUI_ITEMIZATION_CK

MAT_SELECTION_CK

ORDER_COSTING_CK

QUANTITY_STRUCT_CK

SALES_ORDER_UNITCOSTING_CK

SUBCONTRACTING_VAL_CK

SUR_STOCK_TRANSF_CK

VALUATION_CK

Exits:

COPCP_CC

COPCP001

COPCP002

COPCP003

COPCP004

COPCP005

COPCP006

GRCOST01

KKEK0001

[ricardo_fernndezvzquez3]

Hi Rafael,

Thank you for your reply.

According to the functional people, the reason to disable the Save Button is security, they want that some users be able to save but not others.

Any other idea is greatly appreciated.

Thanks!

[RJSA]

Hi Ricardo,

So, I think the best to be done, is to analyze the possibility to do this with user profile.

I recommend the help of a consultant BASIS.

Best regards,

Rafael Sá

[Former Member]

Hi Ricardo,

You can control the security using two ways.

Option 1:

Inside the "user exit during transaction save" create your own logic and check if the user has any roles / or you can check for allowed user Id and control the transaction flow. Throw a hard error if unauthorized user.

Option 2:-

As Richardo said you can control the buttons using the Security roles. But for this transaction we need to investigate and do the needfull implemantation of user roles/ authorization objects.

Hope this helps.

Thnaks,

'Greetson

[Former Member]

Hi Ricardo.

Rather than trying to stop the use of the save button for certain people, the question should be "why do they have create/change access in the first place"? If someone cannot create or make changes, then the are normally assigned only the disply T-Code (CK13N in this case) via the role that they have been assigned.

Regards,

Brent

Edited by: Brent Garries on Jun 28, 2011 11:07 PM

[RJSA]

Hi Ricardo,

I totally agree with the opinion of Brent. I think you should look again this case with functional consultants.

I don't think this is the solution for you...inhibit the save button...

Best regards,

Rafael Sá

[Former Member]

Hi,

I would recommend going via the functional way. In OKKN create a seperate costing variant and in the Update Tab: uncheck the box: saving allowed. By this the users cannot save but view.

Hope this helps. For others with Authorizations, they can use the costing variant which allows them to save.

Cheers!

- Kedar.