Menu Exit MCP20003 in MC93 and MC94

Former Member · ‎10-12-2007

Hi All,

I am Working With 4.6C , Menu Exits.

As Per My Understanding We Can Add New Menu Options In two places.

1) AREA Menus to the Initial Screen of SAP. (SE43)

2) To Standard Transactions.

Note : Working With AREA MENUs is Clear to me.

Currently I am Working With Menu Exit MCP20003 in Tcode MC94.

I Created the Project and Activated it and provided the text for the Menu Options Cu1,CU2 and Created Transaction Code with +CU1 and +CU2..

But I am Able to see the Menu Options with Newly Provided text in DISPLAY MODE .

Note : One Function Module Exit Also Available, But the Documentation of it Says that We Need to Change the Status CHAK0500 for Module SAPLMCPA.

I tried it and it is Expecting the Access Key . But I don't think so we need to Chane the STATUS by Provindign the Access Key.

Note : I tried with Some other Menu Exits Also , In Some Transactions I am able to See the Options in Enable Mode But the Corresonidng Transaction are not Called and IN SOMe Transaction I can See Only in DISPLAY MODE.

I THINK I AM MISSISSING Some Step Every time .

Can Any ONE Please suggest the Reason for the Same and Also Please Correct me i understood Wrong .

Regds,

Ganapati

Former Member · ‎10-15-2007

Transaction Code - MC93 Create Flexible LIS Planning

Exit Name Description

MCP20001 User exit to read external data for planning table

MCP20003 SOP: create function code for flexible planning

MCP20004 SOP: design header information for flexible planning

MCP20005 User exit for authorization check in planning

MCP20006 Exit for processing header info for download in Excel

MCP20007 User Exit for Customer-Defined F4 - Value Request Control

MCP20008 Order processing treatment from IDocs

MCP20009 Extrapolation of Invoiced Sales for OTB

MCP20010 OTB check in the purchase order

MCP20011 User Exit for Processing Data Records to be Updated

MCP20012 User Exit for Excluding Function Codes

MCP20013 User Exit for Once-Only Change to Planning Table

MCP20014 User Exit for Changing Line Text

MCP20015 User exit to set the field names material/plant PBED

MCP20017 User Exit for Influencing Key Figure Block

MCP20018 User Exit for Enhancing a Level of a Planning Hierarchy

MCP20020 User exit for reading info structure when transferring reqts

MCP20021 User exit for modifying parameter when transferring f.reqts

MCP20022 User Exit for Displaying Forecast Results

MCP20023 User Exit for Checking Duplicate Char. Combinations

MCP20024 User-Exit for Inputing forecast parameters

MCP20025 User Exit for Saving Forecasts

MCP20026 Planning hierarchy tool: Enhancement of characteristics

No of Exits: 23

Transaction Code - MC94 Change Flexible LIS Planning

Exit Name Description

MCP20001 User exit to read external data for planning table

MCP20003 SOP: create function code for flexible planning

MCP20004 SOP: design header information for flexible planning

MCP20005 User exit for authorization check in planning

MCP20006 Exit for processing header info for download in Excel

MCP20007 User Exit for Customer-Defined F4 - Value Request Control

MCP20008 Order processing treatment from IDocs

MCP20009 Extrapolation of Invoiced Sales for OTB

MCP20010 OTB check in the purchase order

MCP20011 User Exit for Processing Data Records to be Updated

MCP20012 User Exit for Excluding Function Codes

MCP20013 User Exit for Once-Only Change to Planning Table

MCP20014 User Exit for Changing Line Text

MCP20015 User exit to set the field names material/plant PBED

MCP20017 User Exit for Influencing Key Figure Block

MCP20018 User Exit for Enhancing a Level of a Planning Hierarchy

MCP20020 User exit for reading info structure when transferring reqts

MCP20021 User exit for modifying parameter when transferring f.reqts

MCP20022 User Exit for Displaying Forecast Results

MCP20023 User Exit for Checking Duplicate Char. Combinations

MCP20024 User-Exit for Inputing forecast parameters

MCP20025 User Exit for Saving Forecasts

MCP20026 Planning hierarchy tool: Enhancement of characteristics

No of Exits: 23

USER EXIT

http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm

http://www.sapgenie.com/abap/code/abap26.htm

http://www.sap-img.com/abap/what-is-user-exits.htm

http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction

http://www.easymarketplace.de/userexit.php

http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm

http://www.sappoint.com/abap/userexit.pdfUser-Exit

http://www.sap-img.com/ab038.htm

http://help.sap.com/saphelp_46c/helpdata/en/64/72369adc56d11195100060b03c6b76/frameset.htm

http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm

http://www.sap-img.com/abap/what-is-user-exits.htm

http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci982756,00.html

Exits are basically the hooks whcih SAP has provided to add your own code. There are two types of Exits:

1. Customer exits: Implemented as Function Modules within z includes. Anybody can change it and no access key is required.

2. User Exit: Implemented as subroutines within includes (any include except y or z includes). You need access for the specific include and then you can any subroutine (user exit) within that Include.

BADIs are the enhanced version of user exits where the same logic is implemented via classes and object (OOP)

Enchancement point is the latest once introduces with ECC6.0 . Not very sure about that but you can change it without any access key.

Please go through the following link which will help you understand the exits in a much better way:

http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm

http://www.sap-img.com/abap/what-is-the-difference-between-smod-and-cmod.htm

http://sap.niraj.tripod.com/id21.html

http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm

http://www.sap-img.com/ab038.htm

User Exits.

-

http://www.erpgenie.com/sap/abap/code/abap26.htm

http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm