Use of CMOD?

What is the need of create project in CMOD? With out creating project if i write code in the include ( user Exit) program then what will happen? Any help will be appreciated.

Hi,
Transaction SMOD --> For searching user-exit,
Transaction CMOD --> For registering a particular user-exit for a work in the program
Without registering the perticular user exit in CMOD, how the SAP come to know that you are going to do some work with the help of that user exit? that why we are registering the user exit in CMOD first.
Hope this helps.

Similar Messages

How to use same CMOD code for 2 Diff. variableS?

Experts,
I have written some code under CMOD. Now, i have another query which i could use the same CODE, but diff. variable
( In the CMOD code, i am passing one User input variable ). For the 2nd query i have to pass different User Input variable.
How OR what should i wright to tell CMOD, that IF its Query # 1 then use ABC variable and if Query # 2 then use XYZ .
thanx

Dear Hon Bon,
Let us have a small example on ur scenario.
Lets take the requirement as to calculate Month from Date. (In both the queries).
Query 1: Input variable for Date is say 'ZDATE1'.
Query 2: Input variable for Date is say 'ZDATE2'.
Now let the CMOD variable be ZVAR_CALMONTH.
when 'ZVAR_CALMONTH'.
    clear: lwa_var_rng,
           lwa_range.
    loop at i_t_var_range into lwa_var_rng where vnam = 'ZDATE1' or vnam = 'ZDATE2'.
      concatenate lwa_var_rng-low+0(4)
                  lwa_var_rng-low+4(2)
             into lwa_range-low.
      lwa_range-sign = 'I'.
      lwa_range-opt = 'EQ'.
      append lwa_range to e_t_range.
      clear lwa_range.
    endloop.
Now when you execute the Query1, the above code will work for 'ZDATE1' variable,
if you execute the Query2, the above code will work for 'ZDATE2' variable.
So, the key point is,
1. You need not worry about which query is getting executed. Whatever the query, the particular user entry variable of that query will be taken care.
2. This method works only if the cmod variable (ZVAR_CALMONTH) is used in both the queries (Ofcourse its ur requirement).
3. If queries have both the user entry variables then the cmod will work differently(it ll get data from both the user variables).
You shall try ur code in the above example by replacing the code and the variable names and try playing around it.
Hope this helps.
Regards,
Guru

Variable based on attributes of another variable (using Exit & CMOD)

Hello,
Another coding question (while I get the previous one to work!)
I have a query with amongst others, 2 variables.
one is a require year variable in the query only ZREQYEAR
another is a module ZMODULE
ZMODULE have two attributes
   Year of start ZYEAR_START
   Year of end ZYEAR_END
I need to write a enhancement in CMOD which does the following.
When the query runs, it asks the user for a year (ZREQYEAR), lets say they those 2010 for this example.
Based on this, the enhancement needs to populate the variable for ZMODULE with entries where
ZMODULE-ZYEAR_START = 2010
OR
ZMODULE-ZYEAREND = 2010
and then display the query for just these modules.
is this possible? if you can think of better way then I am open!
I am very new to CMOD and ABAP so please keep any responses in baby language! THANKS!!

Hi,
You can follow the below given steps,
1) You will have to do all the coding in enhancement RSR00001, for using this enhancement you will have to create a project in CMOD transaction and do the coding in the available EXIT.
2) Inside the EXIT write your code for customer exit variable created on ZMODULE (You will have to create a customer exit variable on ZMODULE infoobject).
3) In the exit use your variable name for doing coding,
When "ZMODULE_VARIABLE".
IF I_STEP = 2.
    Loop at i_t_var_range into wa_var_range where vname = "ZREQYEAR_VARNAME".
    wa_data-sign = 'I'.
    wa_data-option = 'EQ'.
    wa_data-low = wa_var_range-low.
    append wa_data to e_t_data.
    EXIT.
    endloop.
    Endif.
The value of ZREQYEAR is assigned to variable created on module. You can use following document for reference,
[http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662562d]
Regards,
Durgesh.

What is i_step =1 or 2 and what is e_t_range used in Cmod for customer exit

Hi All,
What do we go for I_step =1 or 2. And what is e_t_range is it a table or structure ? Can anyone explain me about it.
What happens if we use i_step = 1 and 2?
Thanks
Pooja

hi Pooja,
I_STEP = 0. This step is not called during report execution but when a report variable is used in other instances such as InfoPackages and authorizations.
I_STEP = 1 - Called prior to processing of variable pop-up and for each u201Ccustomer exitu201D variables. Can be used to fill variable with default values. Function module EXIT_SAPLRRS0_001 is called with I_STEP = 1 in function module RRS_VAR_VALUES_EXIT_BEFORE.
I_STEP = 2 - Called after the processing of the variable pop-up. Only for those variables that are not marked as u201Cready for inputu201D or are set to u201Cmandatory variable entryu201D. . Function module EXIT_SAPLRRS0_001 is called with I_STEP = 2 in function module RRS_VAR_VALUES_EXIT_AFTER
I_STEP = 3 - Called after all variable processing and gets called only once and not per variable. Here you can validate the user entries. Function module EXIT_SAPLRRS0_001 is called with I_STEP = 3 in function module RRS_VAR_VALUES_EXIT_CHECK.
E_T_RANGE: Its an Strcuture to export final values after all the calculations made in the exit.
Let me know if you still need some more explanation.
Regards,
Shiva.

Screen exit for VL01 in ECC 6.0 using badi's

Hi All,
I got a requirement to create a new tab in VL01 transaction where i need to create one field in ECC 6.0.
Can anyone tell me the complete procedure to create a new sub screen and adding it to the existing standard sap screen as a new tab in ECC 6.0 version.
kindly suggest me how to do this using badi's.

Dear Nicole,
a)SE18:
Definition name               ME_PROCESS_PO_CUST
b)SMOD:
Enhancement     MM06E005
EXIT_SAPMM06E_013
-> If you want to use it, use transaction CMOD to create a
project with Enhancement     MM06E005
Best Regards,
Ian Wong

Use of enhancement to add field in screen

please explain me how to add fields in standard transaction screen by using enhancement 6 in version 6.0 ?

SAP provides standard transactions to enter data into database. But a client may want to maintain some additional information in SAP other than what is provided.
To make provisions for this, additional screens have to be provided and additional fields must be added into appropriate database table.
To pave way for this, SAP has provided the option for screen exits. Usually, SAP provides the following:
An append structure in the database table with the new fields.
A subscreen area into the standard screen u2013 where the programmer can attach his subscreen of his own program with the new fields.
A function group under which the new subscreen has to be created with the new fields.
Function exits to synchronize the PBO and PAI of the standard SAP program with the PBO and PAI of the subscreen u2013 so that data can flow back and forth between the standard SAP program and the program written by the developer for the subscreen. These function modules also exist in the same function group under which the subscreen will have to be developed.
Finally, a linkage has to be done between the subscreen area of standard SAP screen with the custom subscreen constructed by the developer.
Typically, SAP provides an enhancement in which the developer can create an append structure, use the function exits to synchronize the PBO and PAI of the standard SAP program and the custom subscreen program, and make the necessary linking( as mentioned above in step 4. But, again, this is not a hard and fast rule. Linking in some case, is also done by configurations.) SAP also usually provides the name of the function group under which the subscreen has to be developed.
Necessary guidance about implementing a screen exit development is usually available in the Documentation section of the enhancement ( can be availed by transaction SMOD).
Pre-Requisites
The developer to work on screen exit should have essential knowledge on the following:
DDIC concepts, including the knowledge of append structure.
Concept of SAP Enhancements and implementing them using Projects.
Concept of function exits.
Knowledge on Module Pool u2013 including subscreens, Tabstrip controls etc.
Steps
Guidelines
So, a developer can follow the guidelines mentioned below to implement a screen exit to a standard SAP transaction, as and when required:
Find out the Required Enhancements
Go to SMOD. Press F4 in the Enhancement field. In the next popup window, click pushbutton u2018SAP Applicationsu2019. A list will appear that contains information on all the enhancements, categorized under functional areas. Developer must search for the enhancements relevant to his functional area of interest u2013 for e.g., Purchasing, Asset Accounting, etc.
Note down the enhancements. Then, come to the initial screen of SMOD and view the documentation of each enhancement to find out which one is required for your development.
Utilize the Enhancement in a Project
After you have found one, do as directed in the documentation. Generally, the steps are as follows:
Create a project using CMOD including your enhancement.
Create the append structure with new fields.
Go to the desired function group and create a subscreen with the new fields. Write PBO and PAI for the subscreen, if required.
Use the function exits in the enhancement to link the PBO and PAI of the subscreen with that of the main SAP program supporting the SAP transaction.
Maintain necessary linkage between the subscreen area of standard SAP program with the custom subscreen developed along with the custom program name. This can be done in the project (developed by CMOD including the enhancement) or outside as a part of configuration.
Activate the project.
Test to ensure that required functionality are met.
Case Study 1
Add three new custom fields for Asset master and maintain information for them
Requirement
Three fields in the legacy system have to be maintained in Asset master. These fields are:
Original Asset number u2013 20 characters
Location 2 u2013 15 Characters.
Model no u2013 20 characters
Location 2 should start with u2018Lu2019.
Pre-Analysis
Finding out the Enhancement
As described above, the enhancement is determined. It was found, that enhancement AIST0002 will serve the purpose. It contains the following components (can be viewed by transaction SMOD):
Exit Type Description EXIT_SAPL1022_001 Function Exit Check of User-Defined Fields when Using Create and Change BAPI EXIT_SAPLAIST_002 Function Exit Transfer Data for User Subscreens in PBO. EXIT_SAPLAIST_003 Function Exit Transfer of User-Defined Fields to SAP Master Data Transactions CI_ANLU Customizing Include Include structure to add new fields
Studying the Function Exits
The function module level documentation for the function exits are then viewed from transaction SE37. The documentation clearly laid out for the purpose for their use:
EXIT_SAPLAIST_002
Function module Level Documentation
This function module is called by asset master data maintenance at the start of the dialog. (When changing, it is called after reading of the data from the database; when creating it is called after the transfer of the default values from the asset class and reference asset.) The purpose of the function module is to enable this function group to recognize the master data. For interpreting or controlling master data fields that are important for user fields, it is possible to transfer to global variables at this point, so that they can be recognized when the user subscreens are processed.
Import Parameters
Understanding
This function module is called at the PBO to pass the information retrieved from the database to pass them to the custom subscreen and its underlying program. Import parameter : I_ANLU will be populated with the values for user-defined fields which will be passed to the subscreen program. So, there must be some sort of variable assignment from I_ANLU.
EXIT_SAPLAIST_003
Function module Documentation: This function module is called by SAP asset master data maintenance after the screens are processed, but before saving. The purpose of the function module is to transfer fields entered on user sub-screens of SAP asset data maintenance to the database for updating. The export parameter for this function module is:
Understanding
This function module will be used to transfer the user entered data in the subscreen fields to the main SAP program, which will then be saved into the database.
Studying the Documentation of the Enhancement
The enhancement documentation (as is viewed from the initial screen of SMOD] also supports the idea. Moreover, it informs that we need to develop a subscreen under function group XAIS. This is the function group under which the two function exit modules also exist. So, if the custom subscreen refers to the global data of the function group XAIS, then those values will also be available to these function exits as well.
Going to SE80 and viewing the function group XAIS helps us to inform that there are three DDIC tables declared for it:
Deciding the Final course of Action
After making all the investigations, the final course of action was determined.
SrlNo Step Justification
A project has to be created using transaction CMOD where the enhancement AIST0002 will be included.
Customizing include CI_ANLU has to be created with the custom fields demanded When CI_ANLU will be developed, the custom fields will get appended to the database table ANLU. Also, these fields will be used to create screen fields in the new subscreen.
A custom subscreen, say, 9000 will be developed under function group XAIS. The screen group for the screen will be u2018CUSTu2019 (or any name). The three custom fields added to table ANLU (by creating CI_ANLU) will be used to create new fields in the screen.
In the PAI of the subscreen, validation for Location to start with u2018Lu2019 will be added. The subscreen with three new fields has to be developed so that it can be attached to a subscreen area of the asset master screens.
In the custom include of the function exit module u2018EXIT_SAPLAIST_002u2019, the following code will be written:-
ANLU = I_ANLU. I_ANLU is the import parameter of this FM. The value is assigned to the global variable ANLU, referring which the three new subscreen fields are developed. So, data retrieved from database table ANLU will be passed to this FM as I_ANLU by the standard SAP main program. The value will be taken and passed to the global variable of the function group XAIS, so that the three custom fields (referring to ANLU of XAIS) get populated.
In the custom include of the function exit module u2018EXIT_SAPLAIST_003u2019, the following code will be written:-
E_ANLU = ANLU. The changed values in the subscreen fields exist in global variable ANLU for the function group XAIS. This function exit module will pass the data back to the SAP main program as E_ANLU.
Proper linkage/configuration has to be done so that the new subscreens get linked to the appropriate subscreen area of the Asset master screen. This has to be done u2013 otherwise, the new custom subscreen will not be displayed in the Asset master screens.
Development
Creating a Project to include the enhancement
Go to transaction CMOD and create a project.
Enter a description for the project. Then, click on the pushbutton u2018Enhancement Assignmentsu2019 in the Application Toolbar.
Enter the name of the enhancement and Save.
Go to u2018Componentsu2019.
Creating Custom Include for ANLU
The screen shown below will appear, showing all the enhancement components under the assignment AIST0002. Double-click on the name of the Include Structure to create it.
Create the include structure with three new fields, as required. Then, save and activate it.
Develop the subscreen and the program
Go to transaction SE80. For the function group XAIS, create a new subscreen 9000.
Create it as subscreen.
Then, go to the Layout of the screen and create three new fields from Database table ANLU.
Drag the fields in the screen body and place them.
Then, save and activate the screen and come back to screen flow editor.
Create the PAI module to add validation for field u201CLocation 2u201D, as required .
Activate the whole function group and come out.
Write code in the Function Exits to synchronize the programs
Now, code has to be written in the function modules EXIT_SAPLAIST_002 and EXIT_SAPLAIST_003 so that data flows to and fro between the main SAP program and custom subscreen program. For that, go back to transaction CMOD and change the function exits.
Write code in the function module EXIT_SAPLAIST_002 called once at the beginning of the transaction:
Write code in EXIT_SAPLAIST_003 to pass the data from the subscreen to SAP main program.
Then, activate everything u2013 the whole project and come out.
Complete the configuration to link the subscreen
The development portion is complete. Now, linking of the subscreen has to be done with the subscreen area of the main program. In most of the cases, this linking can be done in the enhancement itself. But, here, requirement is a bit different. It is done by configuration using SPRO.
Assets are created under Asset class. And for each asset class, there is a layout assigned to it. For a layout, there are multiple tab pages assigned to it. And, for each tab page, there are multiple screen groups/field groups assigned.
Here, the requirement is to create these three custom fields in the tab page u2018Generalu2019 of asset master screen ( AS01/AS02/AS03/AS91).
Determine the Layout
To achieve this, first of all, we need to find out which layout is assigned to asset class 1000.For that, go to transaction AOLK( information has to be obtained from functional consultant).Select the Asset Class u20181000u2019 and click on folder u2018General Assignment of Layoutu2019.
Here, for Asset class 1000, for all the user groups, tab layout SAP is assigned. Since layout u2018SAPu2019 cannot be changed, it has to be copied and manipulated to include our screen group. Later, the new layout has to be assigned over here.
Create new tab layout
Go to transaction AOLA. Copy the tab layout u2018SAPu2019 to create another layout, say, YSUB.
System will copy all the settings and will inform you about that.
Select your newly created layout and double-click on the folder u2018Tab page titlesu2019.
You want to put your custom fields in the tab page u201CGeneralu201D. So, select this tab page entry and double-click on the folder "Position of Groups".
Here, all the field groups currently residing in the tab-page u201CGeneralu201D are shown. Add an entry for your newly created fields.
Select the group box from the list. An entry will come with u201CUu201D padded with the custom subscreen prepared by you.
Then, save and come out.
Assign the new Layout to Asset Class
Now, go to tcode AOLK and assign tab layout YSUB for asset class 1000.
Save and come out.
Test the Exit
Everything is over. Now, go to transaction code AS01/02/03 or AS91 to deal with an asset of asset class 1000. You will see your new fields added to the screen. Add values to themu2026save. Then, enter into the tcodes again to see whether the values entered by you are being displayed or not.
I hope you read it all
Thanks and Regards
Santosh K.

Use of documentation flow in data element!!!!

hi experts,
what is the use of documentation flow in data element.
if that field is selected then where will be changes reflected ?
thanks in advance,

Hi,
Changing Data Element documentation (F1 help text)
SAP allows you to modify data element documentation (F1 help text), this could be useful if you want to add/remove information from the F1 help text. E.g. If you are using the field to store info it was not intended for.
Step 1
Using transaction CMOD chose the following menu option
Menu Goto->TExt Enhancements_>data elements->list cust docu.
Enter the data element that you wish to change the documentation text for, then click the change icon(Pencil in 4.6c and tick in 4.6b). You will then be presented with the following screen, which allows you to create new versions of the data element documentation. Simply click on the Change button and enter a name within the customer name range.
Regards

Archiving Document Factory output to CMOD

Hi There, In my Documker 12.3 Factory implememtation I want real time archival to be done on CMOD (Content Manager On Demand).
I am not sure if this is possible and if so how? lots of question is arising.... if the the archival will be synchronous, will there be any data loss,do I need to FTP or what method to apply to move the real time data to CMOD, how the gush of data will be handled, how distributor batch will behave so on so fourth... Any help in this regard will be appreciated.

Hi there,
There are several ways to make this happen, depending on how your CMOD system can accept data. As you may or may not know, the Archiver component is responsible for outputting documents that have completed processing. It can be configured to drop output print files (e.g. PDF, AFP, etc) to a filesystem, or use FTP/sFTP. In addition, it can be configured to drop metadata files that contain information for use by CMOD for indexing the documents on import. This process, like the rest of Factory processing, is asynchronous since the Scheduler's NotifyArchiver thread periodically checks for work and tells the Archiver when work is available. If real-time processing is desired, the Batchings need to be configured for immediate rather than scheduled - however the end result is the same: whenever print files are ready, the Archiver will process them. The Archiver should update the PUBS record indicating if the delivery was successful.
The configuration of these Archiver is a little beyond the scope of this post, but I invite you to review the documentation for the Archiver worker and then reply back if you have further questions. There are advanced configuration and customization possibilities such as integrating directly with CMOD via web service to push documents/index data, but for this sort of integration you'll likely need to involve consulting services.
Best,
Andy

BI CMOD Performance

Dear Friends,
I have a performance related question.
We need to develop a report in which Sum of top 5 materials based on delivery quantity has to be displayed monthwise.
Eg: If in January Materials M1 M2 M5 M6 M7 are top 5 in delivery quantity, then the sum of their delivery quantity.
If in Feb Materials M2 M3 M5 M8 M9 are top 5 in delivery quantity, then the sum of their delivery quantity.
and so on till December.
I thought of using condition TOP N on delivery quantity in Bex query. (Pls correct me if i am wrong)
Problem: Top N will work only for one month in a single query. It cant work for different month (different top 5 materials)
Solution Proposed:
1. Make 12 different queries, one for each month (using Top N) and put each result in a workbook.
2. 12 different CMOD variables and cmod code picksup top 5 materials for each month and put in each variables of respective months. Restrict using these cmod variables for respective columns.
So I wanted your valuable suggestions which of the above method will be of good performance (considering maintenance, etc factors) and the reason also.
Approximate number of records 1 lakh per year.
Kindly give ur suggestions.
Thanks,
Guru

Hi
I think I hv answered this in some other thread. Pl close this thread.
Cheers
Umesh

User Exit Variable for Bex in CMOD (ABAP Code)

Hi Experts
My requirment is to develop a Restricted Keyfigure...
The restriction is based on 0Calmonth (Calendar Year/Month)
The sales from beginning of calendar year up to last "closed" month in a Calendar.
Ex: in June i want to see 01.01.2009 to 31.05.2009 data.
    in October i want to see 01.01.2009 to 30.09.2009 data.
When user execute the report
    in Jan 2010 i want to see 0 as there is no closed month in that particular year.
    in Fed 2010 i want to see 01.01.2010 to 31.01.2010 data.
For that purpose i need to create a User Exit variable in CMOD...
I am struggling to get an idea on how to write a code to meet the requirment
Please help me with code that i can use in cmod
Thanks in advance

Hi,
Use the following code :
when' variable name ' .
DATA : year(4) type n,
month2(2) type n,
date_in type sy-datum,
date_op type sy-datum.
IF I_STEP = 1.
CLEAR L_S_RANGE.
L_S_RANGE-SIGN = 'I'.
L_S_RANGE-OPT = 'BT'.
month2 = sy-datum+4(2).
if month2 = '01'.
concatenate sy-datum+0(4) '01' '01' into l_s_range-low.
l_s_range-high = sy-datum.
else.
month2 = month2 - 1.
clear : date_in, date_op.
concatenate sy-datum+0(4) month2 '01' into date_in.
CALL FUNCTION 'SLS_MISC_GET_LAST_DAY_OF_MONTH'
EXPORTING
    DAY_IN                  = date_in
IMPORTING
   LAST_DAY_OF_MONTH       = date_op
EXCEPTIONS
   DAY_IN_NOT_VALID        = 1
   OTHERS                  = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
concatenate sy-datum+0(4) '01' '01' into l_s_range-low.
l_s_range-high = date_op.
endif.
APPEND L_S_RANGE TO E_T_RANGE.
ENDIF.
I dint know what output do you want if the current month is jan.
I have put it as 1st jan till current date.
Modify it if you need.
Regards,
Mansi

Differences between SMOD & CMOD

Dear All,
Experts can you clear some doubts which have on the above functionalities I know that CMOD can be used to define an project and handle the required enhancements and in SMOD you can select the available User Exits and chart down your required enhancements, now coming to LIS structures enhancements can be done by both using SMOD & CMOD my question is when do this have to be used in regard to LIS Structures, If I enhance the communication structures in LIS I guess I can only use the SMOD where as if enhance the extract structure i can still use CMOD, when is the best option to use out of CMOD & SMOD can experts throw light on this or point out some white papers on the same.
Thanks & Warm Regards,
Fayak.

Hi Fayak,
cmod and smod doesn't apply only for the bw datasource enhancements. They are neccessary for all enhancements you do in a R/3 system. As you already mentioned, you can use smod for maintaining one special enhancement. But this enhancement will not work unless you assigned it to a project and activated the project. This is what you do in cmod. You create a project and assign enhancements to the project. You can have lots of enhancements in one project. But without activating the project, these enhancements will not work.
Hope this helps
regards
Siggi

Why we use customet exit variables?

hi friends,
why we use customer exit variables. can u give me some examples at what scenerio we use
default/user entry, formula, text, hierchies and hierchies. ( with processing type is customer exit)
can i get atleast 1 scenerio for 5 types variables?
Thanking u
suneel.

Hi Suneel
Check info about Exits,
Replacement Path
You use the Replacement Path processing type to specify the value that automatically replaces the variable when you execute the query or Web application
check this link explains step by step
http://www.sd-solutions.com/documents/SDS_BW_Replacement%20Path%20Variables.html
Customer Exit:
If you need to use a processing type other than manual entry/default value, replacement path, SAP exit, or authorization, then a customer exit gives you the option of setting up a processing type for variables, tailor-made to your specific needs.
The customer exit is designed as an enhancement that you can configure with customer-specific logic
SAP Exit:
SAP exits are delivered content variables. Before creating any custom variable exit, its advisable to check if there are any SAP exits delivered to do the same functionality.
Check these links for SAP and Customer Exits,
To see SAP Exits -> Use Tcode SMOD
To See Customer Exits -> Use Tcode CMOD
There are projects to which Exits are assigned. Selects the relevant projects.
What is User Exit:
http://www.sap-img.com/abap/what-is-user-exits.htm
How to find then:
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
All Exits List:
http://www.easymarketplace.de/userexit.php
Thanks,
Sudhakar.

Problem with the CMOD

Hi,
We newly upgraded the system to BI 7.0 version. We have created a new Project in CMOD. The code is for customizing the SAP defined standard message. The problem is that, when we execute the query in the front end the control is not coming to the ABAP code in the CMOD project (we used a Break point in the CMOD). Help us to proceed further.
Thanks
SMS.

Hi,
Do you have any customer exit variable in your query? Did that variable name is used in CMOD includes? If not, then control won't come inside CMOD at all.
Please go through this link, will explain about customer exit & I_STEP usage in detail.
http://help.sap.com/saphelp_nw70/helpdata/EN/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
And you can get lot of customer exit info in SDN itself.
Regards,
Arun Thangaraj.

Performance wise: CMOD or dividing the queries.

Dear Friends,
I have a performance related question.
We need to develop a report in which Sum of top 5 materials based on delivery quantity has to be displayed monthwise.
Eg: If in January Materials M1 M2 M5 M6 M7 are top 5 in delivery quantity, then the sum of their delivery quantity.
If in Feb Materials M2 M3 M5 M8 M9 are top 5 in delivery quantity, then the sum of their delivery quantity.
and so on till December.
I thought of using condition TOP N on delivery quantity in Bex query. (Pls correct me if i am wrong)
Problem: Top N will work only for one month in a single query. It cant work for different month (different top 5 materials)
Solution Proposed:
1. Make 12 different queries, one for each month (using Top N) and put each result in a workbook.
2. 12 different cmod variables and cmod code picksup top 5 materials for each month and put in each variables of respective months. Restrict using these cmod variables for respective columns.
So I wanted your valuable suggestions which of the above method will be of good performance (considering maintenance, etc factors) and the reason also.
Approximate number of records 1 lakh per year.
Kindly give ur suggestions.
Thanks,
Guru
Edited by: hi2guru on Nov 17, 2010 5:21 AM
Edited by: hi2guru on Nov 17, 2010 5:55 AM

Hi
Interesting situation !!!
I think writing 12 queries is not a good idea. For a simple reason that you will have either run a Query at a time (with a different input for each of this) .. isnt it ?
Creating variables for each of the month would be a good idea. You could generate value of 11 months based on a single input from the user. Moreover, the user can give any input ...say for eg the input is 11.2010 then through the customer exit you could find values for the past 11 months. Similarly even if the user changes the input value (say to 08.2010) the system can easily calculate the previous 11 months thus giving you the desired output.
Cheers
Umesh

Data source enhancement using BADI

Hi,
We had a 2LIS_* extractor which is enhanced with ZZ fields.
I look for the sode in CMOD which i couldn't able to find any
My assumption is the data source is enhanced using BADI.....As i am not familiar with BADI's how can i create for my data source enhancement code in BADI
Thanks

Hi ,
Not sure on your question.
Is the Enhancement already done and you want to check whether it is done in BADI/CMOD.
Or
You want to populate the Data using BADI/CMOD.
In any case you can use CMOD or BADI to populate the data ,the recomendded is BADI which can be created in SE24..you can google for some Docs on its creation and steps to be followed.
And if tis CMOD you have to create a project and then write the code and for that also there are DOcs avaliable.
Rgds
SVU

Use of CMOD?

Similar Messages

Maybe you are looking for