topic Re: CMOD and SMOD in Application Development and Automation Discussions

CMOD and SMOD

madan_ullasa — Mon, 17 Jul 2006 08:12:01 GMT

hi,

can anyone tell me for what exactly we use CMOD and SMOD transactions.

points assured to all replies .

regards,

Madan...

Re: CMOD and SMOD

Former Member — Mon, 17 Jul 2006 08:13:13 GMT

TC: SMOD is use to find out enhancement / user exit. If you know enhancement/exit name go to transaction SMOD and put enhancement name and you can do you coding.

After completing code in user exit you need to activate it in order to refect in the actual program.

Untill and unless you are not activating enhancement / exit changes will not reflect.

You activate User Exit using TC : CMOD. Goto transaction code CMOD and create new project. Assign Exit to project and activate the project.

For more information check below link...

http://help.sap.com/saphelp_erp2005/helpdata/en/fb/ac5f2d61ae11d295b10000e82de14a/frameset.htm

For more information and sample codes, please check this links.

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

http://www.sap-img.com/abap/field-exits-smod-cmod-questions-and-answers.htm

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

Cheers,

Re: CMOD and SMOD

Former Member — Mon, 17 Jul 2006 08:14:27 GMT

Hello,

CMOD Transaction is used for customer enhancements.

SMOD is used for SAP enhancements.

The SAP enhancements for an enhancement project are grouped together under a project name. An enhancement project always contains at least one SAP enhancement.

SAP enhancements in the same enhancement project are always activated and deactivated jointly.

The SAP enhancements are created by SAP and generally consist of several components (e.g. a screen area and the function exits for data transfer).

The customer chooses the SAP enhancements which he wants to edit, puts the enhancement projects together, edits the components and activates the projects.

Reward if it helps.

Thanks,

krishnakumar

Re: CMOD and SMOD

Former Member — Mon, 17 Jul 2006 08:15:29 GMT

Hi,

Go through the link,

http://help.sap.com/saphelp_47x200/helpdata/en/fb/ac5f2d61ae11d295b10000e82de14a/frameset.htm

Regards,

Azaz Ali.

Re: CMOD and SMOD

Former Member — Mon, 17 Jul 2006 08:17:49 GMT

SMOD is just to see all the enhancements in the sap system.

CMOD is the customer projects where enhancements are implemented. If you want to implement any enhancements then you will create a project and assign the enhancement and do the coding in exits.

To customize an existing SAP application we have been provided the user exits by SAP. These exits are packaged under enhancements. You choose an enhancement according to your requirements e.g. enhancement MM06E005 is used for adding custom field in me21/me21n. SAP has limited no of enhancements for any transactions, you have to choose only from them to cater your requiement you cant create them.

After selecting your enhancements you have to inherit them in your project in CMOD. Thereafter you do coding and other things like making your subscreens or adding fields to standard tables in respective exits.

To see the effect of your whole project you must activate each componnents of your enhancements.

Hope it helps,

Reward points if this reply helps you

Regards

Niraj Kumar

Patni Computers Systems

Re: CMOD and SMOD

Former Member — Mon, 17 Jul 2006 09:10:06 GMT

Hai Madan

Check the following Document

User Exits

Screen exits are exits that allow you to use a reserved part of the screen (A subscreen) to display or input data.

It is determined be SAP where the sub screen will be displayed.

The syntax is: CALL CUSTOMER-SUBSCREEN

The screen exit is not processed untill the corresponding subscreen has been created in an enhancement project,

and the project has been activated.

Note:

Function codes are only processed in the main screens flow logic

You are not allowed to enter a name for the subscreens command field

You are not allowed to define GUI stauses

You are not allowed to enter a value for Next screen

The global data of the program is not available for the subscreen. Data for the subscreen is provided by function modules.

These function modules belongs to the same function group as the subscreen Subscreens are edited with transaction CMOD.

When you activate a project containg subscreens, the calling screen is regenerated and the subscreen is displayed next

time you display the calling screen

The developer must create the subscreen and the corresponding PBO and PAI modules

How to identify screen exits

Look after CALL CUSTOMER-SUBSCREEN in the screenprogram of the screen you want to modify.

Use transaction CMOD menu Utillities -> SAP enhancements to search for screen exits

MENU EXITS

Menu exits allow you to add your own functionallity to menus. Menu exits are implemented by SAP, and are reserved menu

entries in the GUI interface. The developer can add his/her own text and logic for the menu.

Function codes for menu exits all start with "+"

Example

We want to create a new menu item in the Office menu. The text for the menu should be "Run ZTEST", and the menu will

run report ZTEST.

Goto transaction SE43 Area Menu Maintenance

In Area Menu Paramenter type 'S000' (S triple Zero)

Select Change and ignore all the warning screens

Expand the office menu. In the buttom of the office tree you will find a menu named "Customer function"

Double click on the text. In the pop-up screen change the text to "Run ZTEST". Note that the trsnaction code is +C01

Goto transaction SE93 and create transaction +C01 that calls report ZTEST.

Now you will se the menu displayed in the office tree. If you delete transaction +C01 again, the new menu will dissapear.

USER EXITS

User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a functionmodule.

The code for the function module is writeen by the developer. You are not writing the code directly in the function module,

but in the include that is implemented in the function module.

The naming standard of function modules for functionmodule exits is: EXIT_<program name><3 digit suffix>

The call to a functionmodule exit is implemented as: CALL CUSTOMER.-FUNCTION ❤️ digit suffix>

Example:

The program for transaction VA01 Create salesorder is SAPMV45A

If you search for CALL CUSTOMER-FUNCTION i program SAPMV45A you will find ( Among other user exits):

CALL CUSTOMER-FUNCTION '003'

exporting

xvbak = vbak

xvbuk = vbuk

xkomk = tkomk

importing

lvf_subrc = lvf_subrc

tables

xvbfa = xvbfa

xvbap = xvbap

xvbup = xvbup.

The exit calls function module EXIT_SAPMV45A_003

2. How to find user exits

Display the program where you are searching for and exit and search for CALL CUSTOMER-EXIT

If you know the Exit name, go to transaction CMOD. Choose menu Utillities->SAP Enhancements.

Enter the exit name and press enter.

You will now come to a screen that shows the function module exits for the exit.

3. Using Project management of SAP Enhancements

We want to create a project to enahance trasnaction VA01

Go to transaction CMOD

Create a project called ZVA01

Choose the Enhancement assign radio button and press the Change button

In the first column enter V45A0002 Predefine sold-to party in sales document . Note that an enhancement can only

be used i 1 project. If the enhancement is allready in use, and error message will be displayed

Press Save

Press Components. You can now see that enhancement uses user exit EXIT_SAPMV45A_002. Double click on the exit.

Now the function module is displayed. Double click on include ZXVVAU04 in the function module

Insert the following code into the include: E_KUNNR = '2155'.

Activate the include program. Go back to CMOD and activate the project.

Goto transaction VA01 and craete a salesorder. Note that Sold-to-party now automatically is "2155"

Have look at this links

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCCIOFFI/BCCIOFFI.pdf

http://www.sapgenie.com/abap/ole.htm

http://help.sap.com/saphelp_46c/helpdata/en/59/ae3f2e488f11d189490000e829fbbd/frameset.htm

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCCIOFFI/BCCIOFFI.pdf

In ABAP context , interfaces are only of two types.

1) INBOUND interfaces

2)OUTBOUND Interfaces.

INBOUND:(from external system data is fetched as flat files which is moved to SAP database tables).

in this process we get data in the form of flat files(.txt or .xlx). we will read this data from the files using FM like UPLOAD/WS_UPLOAD/GUI_UPLOAD into internal

tables. And using BDC methods or LSMW tool, we will update the database tables with this data.

OUTBOUND:(Data from SAP dtabase is retrieved adn stored as flatfiles on presentaion server or application server)

In this process we retrieve data using select statements from the database tables and will populate the internal tables. based on the requirement, we will use FM like DOWNLOAD/WS_DOWNLAOD/GUI_DOWNLOAD to write data from internal tables to flat files on th presentation server.

*the above mentioned Fm will work for files on presentaion server(local file system) . IF u want to handle files on the application server, use DATASET.

Other technologies that u mentioned like RFC, BAPI, EDI,ALE, IDOCS etc might be used as apart of interface code.

Regards

Sreeni

Re: CMOD and SMOD

Former Member — Mon, 17 Jul 2006 09:15:33 GMT

Hi Madan,

cmod is the transaction for implementing exits

smod is the transaction for searching the exits for our application.

Re: CMOD and SMOD

Former Member — Mon, 17 Jul 2006 09:21:40 GMT

Hi,

CMOD transaction is used to manage Enhancement Projects.

SMOD transaction is used to view the enhancement components which can be added to the project created in CMOD.

Regards,

Shashank

Re: CMOD and SMOD

Former Member — Mon, 17 Jul 2006 09:51:16 GMT

Hi,

Have a look at these good links-

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

Mark useful answers.

Regards,

Tanuja.

Re: CMOD and SMOD

saikat_pal2 — Mon, 17 Jul 2006 10:46:40 GMT

Hi Madan ,

Apart from theory i guess some code would give you the clearity.

Say you would like to check VAT registration field mandatory while creating vendor through MK01.

You can find all the related enhancements using the <b>deveopment class 'FBK'</b>

Now you can find related FM exit 'EXIT_SAPMF02K_001' which clearly saying Vendors: User exit for checks prior to saving .

Now look for 'Customer-function' in the main program 'SAPMF02K'.

call customer-function '001'

exporting

i_lfa1 = lfa1

i_lfb1 = lfb1

i_lfm1 = lfm1

tables

t_lfbk = zlfbk.

Inside the include zxf05u01.

if i_lfa1-stceg = space.

set cursor field 'LFA1-STCEG'.

message s057(f2).

set screen '0120'.

leave screen.

endif.

Hope you would find this helpful though its very simple example.

Re: CMOD and SMOD

Former Member — Mon, 17 Jul 2006 11:01:39 GMT

Hi,

SMOD

This transaction is used to find the enhancements and its components for a given package. Components are nothing but the user exists.

CMOD

This transaction is used to implement the exits found in SMOD.

Regs,

Venkat Ramanan

Re: CMOD and SMOD

Former Member — Mon, 17 Jul 2006 11:08:52 GMT

Hi,

SMOD

This transaction is used to find the enhancements and its components for a given package. Components are nothing but the user exists.

CMOD

This transaction is used to implement the exits found in SMOD.

Regs,

Venkat Ramanan