Filters with variables user-exits on queries

Is it possible to define complex selection criteria by using the EXIT_SAPLRRSO_001?. Something similar to what we may do a select for Sap:
Select * from table where ((field1 = value1 and field2 = value2) or (field1 = value3 and field2 = Value4)).
I guess not, it seems that only allows a range for output as a single variable ...
If this is not possible, is there any way to filter the data before the show?. I do not care who is among the infoprovider and Bex, who between Bex and Excel ...
Filters with variables user-exits on queries

The variable can take any combination that can be specified in a select-option. The criteria used to select these values to be populated for the variable can be as complex as any ABAP program. So all combinations in a select statement are allowed.

Similar Messages

Steps for Variable User Exit

Hi All,
I have to do some coding in my variable exit. I have followed the follwing steps to create a project a write the code. Anyone please confirm if my steps are correct or missing anything.
1. Go to CMOD, give project name and Click on create.
2. Enhancements -> give RSR00001. and click on Components.
3. Double click on 'EXIT_SAPLRRS0_001'. This will bring up the functionmodule in which we can find an include.
4. Double click on 'ZXRSRU01' Include.
5. Press Enter for the warning message.
6. It gave me a message saying that 'the Include doesnot exist, Do you want to create it'. Click Yes. This will bring up a blank ABAP editor.
7. Write the required code using CASE Statement.
Am I missing anything here?
I would be grateful if someone can send me any documents relating to the variable User Exits.
Best Rgds,
James.

Hi,
Directly go se38 and execute ZXRSRU01 program. Then write a case statement. below is the sample code to calculate default year month variable.
case v_name.
when 'ZYRMTH'.
    if i_step = 1.
      read table i_t_var_range
      with key vnam = 'ZYRMTH'
           into ld_s_var_range.
      if sy-subrc ne 0.   " no value exists, assigns default
        c_year = sy-datum(4).
        c_month = sy-datum+4(2).
        if c_month = 1.
          c_year = c_year - 1.
          c_month = 12.
        else.
          c_month = c_month - 1.
        endif.
        concatenate c_year c_month into c_monyr.
        l_s_range-low = c_monyr.
        clear e_t_range.
        l_s_range-sign = 'I'.
        l_s_range-opt = 'EQ'.
        append l_s_range to e_t_range.
      endif.
    endif.
endcase.
Regards,
Malli

How can i do a variable User exit that present the values before execute

Hi Gurus,
How can i do a variable User exit that present the values before execute, i need this:
a variable that calculate SYS-DATUM until 30 days before (I got the code) but this variable run automatic because is user exit, i want this variable but first present the values, not execute automatic, this is because the users want the report that automatic present the values , help

Hi,
Refer the below links,
http://documentation.softwareag.com/natural/nat424mf/pdf/ops_mf/conf_usrex.pdf
http://www.erpgenie.com/component/content/article/1097
http://www.apentia-online.at/UP/Apentia/files/Article/SAP_BW_User_Exits_and_BAdIs.pdf
Hope it helps you,
Regards,
Ravindra.

MPS with MCI user exit key

Hi,
What all things to take care for MPS with MCI user exit key??
The requirement is -we need to run MPS for few material s in a plant (distribution). Can we do that by assigning diff MRP controller into those materials for whcih we need to run MPS.
Regards
Dinabandhu

Using the user exit you can write your own way of requirement. Any required combination is possible.

Problem with execute User-exit in BPS

hi all.
I made user-exit for BPS, the function is validate values in master tables.
the user insert datas in layout and the response time is very slow.
We analyzed and the program called the user-exit the same number of times exist in the layout.
there was any way to make the process into data packets and not data by data or to make it faster processing
Thanks
Francisco.

put filters wrapping your user -exit code so that the latter is accessed only for the necessary cases.

Need help with transporting User Exit Variable in CMOD ZXRSRU01

Hello Gurus.,
I changed the existing user exit variable in CMOD ZXRSRU01.,before changing neither it ask for any transport request, nor when I activated the include program .
Well., I tried this........I went to goto-> Object Directory Entry.,
changed the Package and person responsible for and then it asked for transport request...but this dint work...
Now., how can I capture the changes in a transport request, so that, i can move the changes to production system?
is there anyway to solve my problem?
Regards,
PNK

Thanks for ur help VIKRAM...i solved the issue...the changes are captured in someother request, but it was not showing in the Version Management.'
I checked the Lock Overview in the Object DIrectory Entry and found out that it was capturing in different request. I released the request and when I tried to change the code, it asked for new transport request.
It worked..
Thanks for your help..
Regards,
PNK

Variable User Exit

Hi have a user exit variable in a query (It must concatenate two characteristics from the user entry parameters).
WHEN 'NOMSOLI'.   " nombre solicitante tarifa compras
      CLEAR: l_s_var, l_s_var2.
      READ TABLE i_t_var_range WITH KEY vnam = 'OS_SALON'
                                                INTO l_s_var.
      IF ( sy-subrc EQ 0 ).
        LOOP AT i_t_var_range INTO l_s_var2 WHERE vnam = 'OS_EDICI'.
          IF ( sy-subrc EQ 0 ).
            CONCATENATE l_s_var-low '.' l_s_var2-low INTO l_s_range-low.
            l_s_range-sign = 'I'.
            l_s_range-opt   = l_s_var2-opt.
            APPEND l_s_range TO e_t_range.
          ENDIF.
        ENDLOOP.
      ENDIF.
I must to take care the user entry parameters of the query : LE,BT,GE..... <,>, = , ..etc
The final result of the variable shows the follow structure data (because the entry parameters user)::
I   |GE |S028.006
I   |LE |S028.008
but when I execute the query, it shows an error about the interval result.
Some one knows how it works when you have more values entry data?
Because always I create user exit variables like:
I   |EQ |S028.006

Hi MP,
The code seems to be OK as per your current requirement. Please clear below mentioned points are correct as per what i understand.
User Input
1. OS_SALON
2. OS_EDICI
-> First input is going to be single.
-> Second input would always be multiple but single values with various options.
-> you need to concatenate first value with all the second values and the options of just 2nd one.
-> After concatenation, you need to validate the result value with the data in the infoprovider.
-> Validated data then needed in output.
I can suggest you some alternate method if it is same what i understand.
Regards
Raj

Variable User Exits

Previously I have only used CMOD to manipulate variables in queries. However, my current client has BW 3.5 and I have read that the direction now is to use the BADI RSU5_SAPI_BADI.
Can anybody provide an example of a user exit using the BADI? I know enough ABAP to get by in the old user exit but I don't think my knowledge extends this far.
I am on BW 3.5 SP13.
Cheers,

hi,
sample code
INCLUDE ZXRSRU01                                                   *
DATA: L_S_RANGE TYPE RSR_S_RANGESID.
DATA: LOC_VAR_RANGE LIKE RRRANGEEXIT.
CASE I_VNAM.
WHEN 'CUMMONTH'.
    IF I_STEP = 2.                                  "after the popup
      LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGE
              WHERE VNAM = 'MONTH'.
        CLEAR L_S_RANGE.
        L_S_RANGE-LOW      = LOC_VAR_RANGE-LOW(4)."low value, e.g.200001
        L_S_RANGE-LOW+4(2) = '01'.
        L_S_RANGE-HIGH     = LOC_VAR_RANGE-LOW.   "high value = input
        L_S_RANGE-SIGN     = 'I'.
        L_S_RANGE-OPT      = 'BT'.
        APPEND L_S_RANGE TO E_T_RANGE.
        EXIT.
      ENDLOOP.
    ENDIF.
ENDCASE.
sent doc also ...

Convert Variable User Exit to ABAP OO

Hi, I recall an article that demonstrated a better way to implement the Varaible User Exit with ABAP OO, instead of the usual design. The ABAP OO way would eliminate a single variable code error from shutting down all of the others. Can anyone point me to the article?
Thanks

Hello,
You can use BADI which is a ABAP OO.
[Enhancing DataSources with BAdI RSU5_SAPI_BADI|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3001894b-b1fb-2910-77ba-e80b6f2053b7]
[Implementing a Business Add In (BAdI) in an Enhancement|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0456c54-0901-0010-f0b3-cd765fb99702]
Thanks
Chandran

Formula variable user exit.

Hello experts;
I will provide max points for help with this.
In query designer can I access a key figure from another cube and use it in a formula?
I cannot use multi-cube in this solution so I was looking into creating a formula variable using a user exit to access a key figure stored in a different cube.
Ex:
I have a Tracings cube with customer and material cost information.
I need to calculate the cost per patient for Absorbent material.
I can get the customer cost for Absorbent material but the number of patients is stored in a different cube called Census information.
Since the Census information is not related to a material (only customer) I cannot get the number of patients together with the cost of the absorbent material. I was hoping to access the Census information (number of patients) from the query calculating the cost per patient.
Thanks
Den

I really don't see how you can implement it using exit variable even if you can read data from other cube in exit. If you still want to explore it, refer the following thread - How to read data from an InfoCube in BI 7.0?
Why can't you build a multiprovider - these kind of requirements are precisely the reason why multiprovider is there (when you need information present in multiple infoproviders in the same report)

Selection screen values in global variable user exit

Hi all,
I made a project report global variable of type 3 (User Exit) and I develop the related code in enhancement KKDR0001 component EXIT_SAPLKYP1_003. In this code I need the value of project definition that user entered on selection screen.
Does anybody know how can I get this data?
Thanks!

Hi,
You can do the following for getting project in Earlier screen
Data: l_string(20) type c
Field-symbols: <fs> type any.
l_string = '(Screen)variable name'.
assign l_string to <FS>.
Just try above...

Problem with a user exit PBAS0001

Hi Experts,
We have a new sand box in ecc6. when I go to any sandbox or production in 4.6c system transaction pa40 runs fine.
I slected change of pay in new sandbox ecc6 through pa40, but it is throughing with an error stating
The current ABAP program "SAPFP50M" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLXPAD " in include "ZXPADU02
" in
line 22:
""I0028" and "INNNN" are not mutually convertible. In Unicode programs,"
" "I0028" must have the same structure layout as "INNNN", independent o"
"f the length of a Unicode character."
The above error is found in user exit PBAS0001 with
EXIT_SAPFP50M_001
EXIT_SAPFP50M_002
can anyone let me know how to handle this to correct in new sand box to run as normal.
Thanks
Ravi

Hi Ravi,
After release 5 due to unicode the structure innnn and Pnnnn are not compartiable, hence move statement ll not work.
Use the below methods for conversion. Point if helpful.
MOVE innnn TO gs_0041.
PERFORM MOVE_INNNN_TO_STRU USING INNNN gs_0041.
FORM MOVE_INNNN_TO_STRU USING    P_INNNN
                                  P_GS_0041.
CALL METHOD CL_HR_PNNNN_TYPE_CAST=>PRELP_TO_PNNNN
    EXPORTING
      PRELP = P_INNNN
    IMPORTING
      PNNNN = P_GS_0041.
ENDFORM.                    " MOVE_INNNN_TO_STRU
      MOVE gs_0041 TO innnn.
PERFORM MOVE_STRU_TO_INNNN USING gs_0041 INNNN.
FORM MOVE_INNNN_TO_STRU USING    P_INNNN
                                  P_GS_0041.
CALL METHOD CL_HR_PNNNN_TYPE_CAST=>PRELP_TO_PNNNN
    EXPORTING
      PRELP = P_INNNN
    IMPORTING
      PNNNN = P_GS_0041.
ENDFORM.                    " MOVE_INNNN_TO_STRU
Br/Manas

Variable user exit question

Hi all,
i m looking for a code to make an User exit variable to select the actual month and the previous month , for example in this moment ( september and October )

Hi,
Use Tcode: CMOD, funtion module :EXIT_SAPLRRS0_001 double click on the program ZXRSRU01, start writing ur code. The code which i gave u is for Calculate Month to date, similarly u have change the code as per ur requirement.
Regarding User exits:
http://help.sap.com/saphelp_nw04/helpdata/en/f1/0a56f5e09411d2acb90000e829fbfe/frameset.htm
to calculate "month to date" user input is "Calday" Key Date
sample code:
WHEN 'ZPUTMNTH'.
IF I_STEP = 2. "after the popup
LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGE
WHERE VNAM = 'ZPDATE'.
CLEAR L_S_RANGE.
L_S_RANGE-LOW = LOC_VAR_RANGE-LOW(6). "low value, e.g.YYYYMM (200606) part of key date (20060625)
L_S_RANGE-LOW+6(2) = '01'. low value e..g. YYYYMM01 (20060601)
L_S_RANGE-HIGH = LOC_VAR_RANGE-LOW. "high value = input
L_S_RANGE-SIGN = 'I'.
L_S_RANGE-OPT = 'BT'.
APPEND L_S_RANGE TO E_T_RANGE.
EXIT.
ENDLOOP.
ENDIF.

Help with BDC, user exits and BAPI

Hello all:
1) I posted a question before about BDC documentation and people sent me lot of helpful material. Thanks to all of them. I am very new to ABAP coming from VB background and wondering if someone can tell me how to practice one simple BDC program starting from scratch. What do I first need to do to get started? I have Mini WAS 6.20 test version and like to practice BDC programming.
2) What are user exits and BADI and can anyone provide some documentation and sample code if possible.
Thanks everyone in advance.
--Mithun.

Hai Mithun Dha
Go through the following Documentation & Example Code
Just check these links.
Diff. between LSMW & BDC?
BDC SESSION
CALL TRANSACTION
CALL DIALOG
What is BDC or batch input
The Batch Input is a SAP technic that allows automating the input in transactions. It lies on a BDC (Batch Data Commands) scenario.
BDC functions:
E BDC_OPEN_GROUP : Opens a session group
E BDC_CLOSE_GROUP : Closes a session
E BDC_INSERT : Insert a BDC scenario in the session
E The ABAP statement "CALL TRANSACTION" is also called to run directly a transaction from its BDC table.
It runs the program RSBDCSUB in order to launch automatically the session. The session management is done through the transaction code SM35.
The object itself is maintanable through the transaction SE24.
BDC methods:
Method
Description
Parameters
OPEN_SESSION
Opens a session
SUBRC (Return Code ? 0 OK)
SESSIONNAME (Session to be created)
CLOSE_SESSION
Closes a session
None
RESET_BDCDATA
Resets the BDC Internal Table...
None. Normally, for internal purposec
BDC_DYNPRO
Handles a new screen
PROGNAME (Name of the program)
DYNPRONR (Screen Number)
BDC_FIELD
Puts a value on the screen
FIELDNAME (Name of the field)
FIELDVALUE (Value to be passed)
CONSTRUCTOR
Constructor - Initializes NO_DATA
NODATA (No data character). The constructor is called automatically when the object is created.
RUN_SESSION
Launches a session with RSBDCBTC
None
CALL_TRANSACTION
Calls a transaction with the current BDC Data
MODE (Display Mode)
UPDATE (Update Mode)
TCODE (Transaction to be called)
BDC_INSERT
Inserts the BDC scenario in the session
TCODE (Transaction to be called)
BDC techniques used in programs:
1) Building a BDC table and calling a transaction,
2) Building a session and a set of BDC scenarios and keeping the session available in SM35,
3) Building a session and lauching the transaction right after closing the session.
BDC using Call Transaction
BDC using Call transaction involves calling an SAP transaction in back ground from within the ABAP
program. The process involves building an Internal BDC table containing the screen information needed to
execute the required transaction and then passing this to the Call transaction command (See code example).
The full procedure for creating a BDC program is as follows:
What is the difference between batch input and call transaction in BDC?
Session method.
1) synchronous processing.
2) can tranfer large amount of data.
3) processing is slower.
4) error log is created
5) data is not updated until session is processed.
Call transaction.
1) asynchronous processing
2) can transfer small amount of data
3) processing is faster.
4) errors need to be handled explicitly
5) data is updated automatically
BATINPUT/DIRECT INPUT
A: Batch-inputs can not be used to fill the "delivery due list" screen because it is not a dynpro. This is a standard SAP report. A SAP report (check with "System -> Status") may be called using SUBMIT sentence with the appropriate options . It is preferred to call a report than create a Batch-input program.
GO THROUGH THIS LINK
http://www.guidancetech.com/people/holland/sap/abap/zzsni001.htm
check with this code
include bdcrecx1.
tables : mara.
data : begin of it_mara occurs 0,
matnr like mara-matnr,
mbrsh like mara-mbrsh,
mtart like mara-mtart,
maktx like makt-maktx,
meins like mara-meins,
end of it_mara.
start-of-selection.
perform upload_data.
perform open_group.
loop at it_mara.
perform bdc_dynpro using 'SAPLMGMM' '0060'.
perform bdc_field using 'BDC_CURSOR'
'RMMG1-MATNR'.
perform bdc_field using 'BDC_OKCODE'
'/00'.
perform bdc_field using 'RMMG1-MATNR'
it_mara-matnr.
perform bdc_field using 'RMMG1-MBRSH'
it_mara-mbrsh.
perform bdc_field using 'RMMG1-MTART'
it_mara-mtart.
perform bdc_dynpro using 'SAPLMGMM' '0070'.
perform bdc_field using 'BDC_CURSOR'
'MSICHTAUSW-DYTXT(02)'.
perform bdc_field using 'BDC_OKCODE'
'=ENTR'.
perform bdc_field using 'MSICHTAUSW-KZSEL(01)'
'X'.
perform bdc_field using 'MSICHTAUSW-KZSEL(02)'
'X'.
perform bdc_dynpro using 'SAPLMGMM' '4004'.
perform bdc_field using 'BDC_OKCODE'
'=BU'.
perform bdc_field using 'MAKT-MAKTX'
it_mara-maktx.
perform bdc_field using 'BDC_CURSOR'
'MARA-MEINS'.
perform bdc_field using 'MARA-MEINS'
it_mara-meins.
perform bdc_field using 'MARA-MTPOS_MARA'
'NORM'.
perform bdc_transaction using 'MM01'.
endloop.
perform close_group.
*& Form upload_data
text
--> p1 text
<-- p2 text
FORM upload_data .
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
FILENAME = 'c:\mat_bdc.txt'
FILETYPE = 'ASC'
TABLES
DATA_TAB = it_mara.
IF SY-SUBRC = 0.
SORT IT_MARA BY MATNR.
ENDIF.
ENDFORM. " upload_data
flat file structure is
PRANIT_011 CCOUP This is Testing material kg
PRANIT_012 CCOUP This is Testing material kg
PRANIT_013 CCOUP This is Testing material kg
PRANIT_014 CCOUP This is Testing material kg
PRANIT_015 CCOUP This is Testing material kg
when your selecting views
this particular material will belongs to Po/Sales or some other areas .
when you select basic 1 --it gives description
select basic 2 -- it gives tax ,amount, base unit of measurement
BDC TO BAPI
The steps to be followed are :
1. Find out the relevant BAPI (BAPI_SALESORDER_CHANGE for VA02).
[for VA01 use BAPI_SALESORDER_CREATEFROMDAT2]
2. Create a Z program and call the BAPi (same as a Funtion module call).
2. Now, if you see this BAPi, it has
-> Importing structures.
eg: SALESDOCUMENT: this will take the Sales order header data as input.
-> Tables parameters:
eg: ORDER_ITEM_IN: this will take the line item data as input.
Note :
Only specify fields that should be changed
Select these fields by entering an X in the checkboxes
Enter a U in the UPDATEFLAG field
Always specify key fields when changing the data, including in the checkboxes
The configuration is an exception here. If this needs to be changed, you need to complete it again fully.
Maintain quantities and dates in the schedule line data
Possible UPDATEFLAGS:
U = change
D = delete
I = add
Example
1. Delete the whole order
2. Delete order items
3. Change the order
4. Change the configuration
Notes
1. Minimum entry:
You must enter the order number in the SALESDOCUMENT structure.
You must always enter key fields for changes.
You must always specify the update indicator in the ORDER_HEADER_INX.
2. Commit control:
The BAPI does not run a database Commit, which means that the application must trigger the Commit so that the changes are read to the database. To do this, use the BAPI_TRANSACTION_COMMIT BAPI.
For further details... refer to the Function Module documentation for the BAPi.
For User Exits
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 <3 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
Creation of Field Exits
Step by step procedure for creating Field Exits
There are eight steps to creating a field exit:
Step 1: Determine Data Element
Step 2: Go To Field Exit Transaction
Step 3: Create Field Exit
Step 4: Create Function Module
Step 5: Code Function Module
Step 6: Activate Function Module
Step 7: Assign Program/Screen
Step 8: Activate Field Exit
Step 1: Determine Data Element
- Before you can begin adding the functionality for a field exit, you must know the corresponding data element.
- An easy way to determine the data element associated to a particular screen field is to:
Go the appropriate screen.
Position the cursor in the appropriate field.
Press eF1f for field-level help.
Click on the eTechnical infof pushbutton (or press eF9f) on the help dialog box.
On this Technical Information dialog box, the data element will be specified if the field is 'painted' from the ABAP/4 Dictionary.
Step 2: Go To Field Exit Transaction
- The transaction to create field exits is CMOD.
- You can use the menu path Tools -> ABAP/4 Workbench -> Utilities -> Enhancements -> Project management.
- From the initial screen of transaction CMOD, choose the Text enhancements -> Field exits menu path.
- After choosing this menu path, you will be taken to the field exits screen. From here, you can create a field exit.
NOTE : Even though you use transaction CMOD to maintain field exits, you do not need to create a project to activate field exits.
Step 3: Create Field Exit
- From the field exit screen of transaction CMOD, choose the Field exit -> Create menu path.
- After choosing this menu path, a dialog box will prompt you for the appropriate data element .
- Enter the data element name and click the eContinuef pushbutton.
- Now, you will be able to create the function module associated to the data elementfs field exit.
Step 4: Create Function Module
- You will automatically be taken to the Function Library (SE37) after entering a data element name and clicking the eContinuef pushbutton.
- In the eFunction modulef field, a function module name will be defaulted by the system based on the data element specified. This name will have the following convention:
FIELD_EXIT_<data element>
- You can add an identifier (an underscore followed by a single character ).
- The first function module for a data elementfs field exit must be created without an identifier.
- To create the function module, click on the eCreatef pushbutton, choose menu path Function module -> Create, or press eF5f.
- After choosing to create the function module, you will get the warning: "Function module name is reserved for SAP". This message is just a warning so a developer does not accidentally create a function module in the field exit name range. By pressing eEnterf, you will be able to go ahead and create the function module.
- Before coding the function module, you will have to specify the function modules attributes -- function group, application, and short text.
Step 5: Code Function Module
- From the function modulefs attributes screen, click on the eSource codef pushbutton or choose the Goto -> Function module menu path to the code of the function module.
- Here you will add your desired functionality for the field exit.
- Remember that field exitfs function module will have two parameters -- one importing parameter called "INPUT" and one exporting parameter called "OUTPUT". These parameters will be set up automatically by the system.
- You must remember to assign a value to the OUTPUT field. Even if the value does not change, it must be moved from the INPUT field to the OUTPUT field.
Step 6: Activate Function Module
- After coding the function module, you must remember to activate it.
- Use the Function module -> Activate menu path to activate the function module.
- At this point, you can return to the field exit transaction.
- You should be able to 'green arrow' back to this transaction.
- When you return to the field exit transaction, you will see an entry for the newly created field exit.
- At this point, the field exit is global. That is, it applies to all screens that use a particular data element. On any screen that uses the data element, the corresponding field exit function module will be triggered, once it is active.
- Also, the field exit will not be triggered yet because it is inactive.
Step 7: Assign Program/Screen
- This step is only needed if you want to make a field exit local.
- To make a field exit local, select the field exit and click on the eAssign prog./screenf pushbutton.
- In the dialog box , indicate the appropriate program name and screen number.
This information indicates that the field exit is local to the specified screen in the specified program.
- In the dialog box, you determine which function module gets executed for the field exit by specifying the identifier in the eFld. Exitf field.
- If this field is left blank, the function module triggered will be 'FIELD_EXIT_<data element>'.
- If a single-character identifier is entered into the field, the function module triggered will be 'FIELD_EXIT_<data element>_<identifier>'.
Step 8: Activate Field Exit
- The field exit must be active for it to be triggered by the system.
- Activate the field exit by choosing the Field exit -> Activate menu path.
- After assigning the field exit to a change request, its status will change to eActivef and it will be triggered automatically on the appropriate screen(s).
NOTE : In order to activate the field exit the profile parameter abap/fieldexit = YES must be set on all application servers
Thanks & regards
Sreenivasulu P

Help With an User Exit

Hi Everyone,
I need help to build a user exit.
I need to get a quarter period, but i only have the 0FISCPER3 and 0FISCYEAR.
I tought in use 0FISCPER3 in some addition.
Can anyone help me or give some exemple of time user exits?
Thanks

Use a routine for 0CALQTR, pass Fiscal year Period to the Func. Module below:
FUNCTION Z_FISCPER_TO_QTR.
""Local Interface:
*" IMPORTING
*"     REFERENCE(I_PERIV) TYPE PERIV DEFAULT 'K4'
*"     REFERENCE(I_FISCPER) TYPE WDY_NUMC_7
*" EXPORTING
*"     REFERENCE(ES_CALQUARTER) TYPE /BI0/OICALQUARTER
*" EXCEPTIONS
*"      INVALID
DATA: ld_gjahr      LIKE t009b-bdatj,
        ld_poper      LIKE t009b-poper,
        ld_date       LIKE sy-datum,
        ld_year(4)    TYPE n,
        ld_month(2)   TYPE n,
        ld_quarter(1) TYPE n.
ld_gjahr = i_fiscper(4).
ld_poper = i_fiscper+4.
CALL FUNCTION 'FIRST_DAY_IN_PERIOD_GET'
    EXPORTING
      i_gjahr              = ld_gjahr
    I_MONMIT             = 00
      i_periv              = i_periv
      i_poper              = ld_poper
   IMPORTING
     e_date               = ld_date
   EXCEPTIONS
     input_false          = 1
     t009_notfound        = 2
     t009b_notfound       = 3
     OTHERS               = 4.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4
            RAISING invalid.
ENDIF.
ld_year = ld_date.
ld_month = ld_date+4(2).
CASE ld_month.
    WHEN 1 OR 2 OR 3.
      ld_quarter = 1.
    WHEN 4 OR 5 OR 6.
      ld_quarter = 2.
    WHEN 7 OR 8 OR 9.
      ld_quarter = 3.
    WHEN 10 OR 11 OR 12.
      ld_quarter = 4.
ENDCASE.
CONCATENATE ld_year ld_quarter INTO ES_CALQUARTER.
ENDFUNCTION.

Filters with variables user-exits on queries

Similar Messages

Maybe you are looking for