Customer exit and variables

Hello,
Before posting this question I've search on the forum and already found part of my needs, but I still miss the end.
I'd like to create a customer exit to calculate the last day of previous month (this is OK, there are lots of threads regarding this) and another one for last day of previous-previous month (this is OK as well)
I've done the modifications in CMOD, changed the ABAP code and activated it. I've created 2 variables in Query Designer and now I would like to use them in selections. Here I'm stucked because when I try to select any of my 2 variables to restrict dimensions, I don't get them!
I've noticed that I'm only able to create text type variable while I would like to create characteristic value type variable. How can I do to do so?
Thanks for your help,
Benoit

Hi benoit,
Actually you dont know how to create variable.
For Creating variable on any characteristic, Just select that characteristic, Right click on that, select restrict, and there you can see single value, Variable, favourite etc, there in Variable, right click and create variable.
Or refer this link.
http://help.sap.com/saphelp_bw21c/helpdata/en/f1/0a5a2ee09411d2acb90000e829fbfe/frameset.htm
there go to using variable and variables for Characteristic Value.

Similar Messages

How to find out the customer exit and sap exit variables created provider?

Hi all,
How to identify what are all the customer exit and sap exit variables are been created for an info provider. is there any tables which allow us to find out.
thanxs
haritha

Hello haritha,
SAP Exit and Customer Exit variables are created for Characteristics and not for individual InfoProviders.
So whenever the characteristic is used in the InfoProvider, by selection the appropriate variable the exit can be called.
So the same Exit can be in one or more InfoProviders.
Hope it helps.
Thanks,
Chandran

Text Variable(Customer Exit) displays variable name instead of its value.

Hi Gurus,
My requirement is to display the year(from variable) as the field name i.e Year end salary 2009.
I was using the fields name as hardcoded values like 2009 but as per my requirement i need to display it from the variable.
I tried using Text Variable using customer exit, but I'm getting variable name(zvariable) instead of value(2009).
Please help me out, many thanks in advance.
Regards,
Ankur

Hi,
Actually I tried to create a Text Variable with Replacement Path.
But here the problem is that we have a Characteristic Variable (Customer Exit) which is not listing in the selection box of Replacement Path.
Hence we tried to create another Text Variable (Customer Exit) and refering to the same Customer Exit code.
Regards,
Ankur

Customer Exit For Variable

Hi Experts,
Currently i am using SAP BI 7.0, I dont have much ABAP knowledge.
Requirement : I need to create a Customer exit on variable to derive Fiscal period from the date entered manually by user.The date is in mm/dd/yyyy format and i need to derive Fiscal period from it.
Please assist me in doing this.
Best Regards,

Hi,
Assume date entered by the user is captured in user input variable: Variable_Date
Exit Call after User Input
<Declaration>
DATA : l_date1(7) TYPE c,
 l_year(4) TYPE c,
 l_month(2) TYPE c,
 LS_RANGE_IN_LINE LIKE LINE OF I_T_VAR_RANGE,
 d_date type sydatum.
<You need to write code in Step2 as you would be reading data entered by user.>
WHEN 2.
 CLEAR l_s_range.
 READ TABLE I_T_VAR_RANGE WITH KEY VNAM = 'Variable_Date' INTO
 LS_RANGE_IN_LINE.
 d_date = LS_RANGE_IN_LINE-LOW .
 l_year = d_date(4).
 l_month = d_date+4(2).
 CONCATENATE l_year '0' l_month INTO l_date1.
 l_s_range-low = l_date1.
 l_s_range-sign = 'I'.
 l_s_range-opt = 'EQ'.
 APPEND l_s_range TO e_t_range.
Regards
Lavanya

Customer Exit - Fill variable depending on query view name

Hi
We're running BW 7.0
We have a query which is used for broadcasting and as well for user input. That's why we have a variable which is default filled by a customer exit. This variable is the week and is default filled: fist week of year up to actual week.
But now we have for the same query different selection requirenments.
The same query should be send by email with
- first week of year up to actual week
- previous week
Because of dynamic variables the calweek needs to be filled by customer exit and worked until now fine - until a second requirenment was coming (separat broadcast only with previous week).
I don't like the idea to copy the query because of maintenance work.
I'd like to have several views - and depending on the view name etc. I would fill the customer variable. But I don't get the query view name into customer exit - right?
Do you have any other ideas?
How do you handle such requirenments?
Thx
Roger

Hi Helder,
I understand your requirement but I don't understand the solution you are using. I think it's a bit tricky.
What I would do is:
Create three variables:
- VAR1: Single value, mandatory, ready for input, customer exit. Used to store "User input date"
- VAR2: Select option, customer exit, not ready for input. Used to store Valid From restriction.
- VAR3: Select option, customer exit, not ready for input. Used to store Valid to restriction.
Then, use this code:
WHEN 'VAR2'.
IF I_STEP = 2.
READ TABLE I_T_VAR_RANGE INTO LOC_VAR_RANGE
with key VNAM = 'VAR1'.
CLEAR L_S_RANGE.
L_S_RANGE-LOW = LOC_VAR_RANGE-LOW.
L_S_RANGE-SIGN = 'I'.
L_S_RANGE-OPT = 'LE'.
APPEND L_S_RANGE TO E_T_RANGE.
ENDIF.
WHEN 'VAR3'.
IF I_STEP = 2.
READ TABLE I_T_VAR_RANGE INTO LOC_VAR_RANGE
with key VNAM = 'VAR1'.
CLEAR L_S_RANGE.
L_S_RANGE-LOW = LOC_VAR_RANGE-LOW.
L_S_RANGE-SIGN = 'I'.
L_S_RANGE-OPT = 'GE'.
APPEND L_S_RANGE TO E_T_RANGE.
ENDIF.
I think this should work, and you'll have three independent variables used for one purpose each.
Hope this helps.
Regards,
Diego

Wrting customer exit in variables

Hi Guys,
I have to change the code in customer exit for variables in reporting.i have to give inputrange in 0calmonth(01/06-07/06)and i have to get the output as 0calday(multiplevalues),can any body help me out.
Thanks
Kiran

Kiran,
   check this... i wrote the code as mentioed in my last post...
data:w_date(8).
CASE I_VNAM.
WHEN '0CALDAY Variable Name'
    if i_step = 1.        clear l_s_range.
      read table I_T_VAR_RANGE where vnam = '0CALMONTH Varibale'.
      l_s_range-low = concatenate i_t_var_range-low+'01'.
      l_s_range-sign = 'I'.
      l_s_range-opt = 'EQ'.
w_date = concatenate i_t_var_range-high '01' into w_date.
call function 'SLS_MISC_GET_LAST_DAY_OF_MONTH'
    exporting
         DAY_IN = w_date
    importing
         LAST_DAY_OF_MONTH = l_s_range-high.
      append l_s_range to e_t_range.
    endif.
endcase.
check this code and let me know...change the Variable Names and keep capital letters.
i'm telling you again... if the 0CALMONTH variable range 200605 to 200608. code will populate the values for 0CALDAY like this...20060501 to 20060831.
all thes best.
Regards,
Nagesh Ganisetti.

Allowing customer exit interval variables to be "Ready for Input"

Hi BI fans,
I am looking to construct a Pie Chart where the default view will show the Year-To-Date data. At present, we are utilizing a customer exit variable (from the 0FISCPER characteristic) to carry out this task.
It is also required, however, to allow the user to manually adjust the start and end date of this period. Is it possible to have a customer exit interval variable which will allow the user to modify the start and end date and thus facilitate specified time periods?
I look forward to hearing from you,

Hi
Use a BI Content variable like 0I_CFYTD - Year to Date For Current Fiscal Yearm, this variable is a interval variable and will default from fiscal period 1 to the current period.
If you edit the variable and set it to ready to input then when you run the report at the variable screen you can change the period on which you want to report.
hope this helps

Difference between customer exit and user exit?

hi experts
difference between customer exit and user exit?

These r the main differences between user exits and customer exits
1) user exits r subroutines where as customer exits r function modules
2) user exits r not upgraded where as customer exits r will upgrade
3) customer exits r used for creating and additional fields or menu items to stadard tcode where as user exits r used for enabling or disabling the fields on the standrd screen or concatenating the key fields,it is not used adding an additional componenats to stadard tcode
4) customer exits r reusable where as user exits r not reusable.
Also:
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
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
customer exits
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662562d
Menu Exit.
http://www.sappoint.com/abap/spmp.pdf
http://www.sappoint.com/abap/userexit.pdf
http://www.sapdevelopment.co.uk/enhance/mod_sapmenu.htm
http://www.sapdevelopment.co.uk/enhance/enhancehome.htm
1. Previously there were only user-exits.
2. Then came the concept of customer-exits.
3. user exits were nothing but subroutines
FORM/PERFORM
called from standard programs.
4. The FORM defintion was placed inside
an empty include file.
5. So It was called EVERYTIME.
and we need to MODIFY/REPAIR the
standard include .
6. Then it came with concept of customer-exit
7. It consists of calling a FUNCTION MODULE,
which is called only if
the user-exit is ACTIVATED (other wise not called)
In this case, the code in put inside
a pre-defined Z include.
8. Functionality of both is same, howerver
we can note the following important differences
a) Customer exit is called only if activated.
(hence, it does not waste resources)
b) in customer exit, REPAIR does not happen
to the standard include.
Exits are basically the hooks whcih SAP has provided to add your own code.
User Exits: These are provided only SD module .
They are Empty subroutines with naming like USEREXIT_.
We need to have Access key to implement them.
Customer Exits: These are enhancement techniques.
There are defined in SMOD and implemented in CMOD.
Types of Customer exits: Function exit, Screen Exit, Menu exit.
User Exit and Customer Exit are same ,but SAP Exit and Customer exit are different...
Customer Exit,
Enables you to determine values for variables by means of Functional Module exit.The function module used is EXIT_SAPLRRSO_001.
Create a project in CMOD by selecting the SAP Enhancement RSR00001 and assign this to the enhanced proj and activate it.
Customer Exit
SAP creates customer exits for specific programs, screens, and menus within standard applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
If you want to enhance the functionality of your SAP System, you should take advantage of the exits available in standard applications. There are two main reasons why you should use exits rather than modifying SAP software yourself. Add-ons attached to exits have the advantage that:
They do not affect standard SAP source code
When you add new functionality to your SAP System using SAPs exits, you do not alter the source code of standard SAP programs in any way. The code and screens you create are encapsulated as separate objects. These customer objects are linked to standard applications, but exist separately from SAPs standard software package.
They do not affect software updates
When you add new functionality to your SAP System using SAPs exits, your objects (called customer objects) must adhere to strict naming conventions. When it comes time to upgrade a to a new software release, customer objects names ensure that they will not be affected by any changes or new additions to the standard software package.
Customer exits are not available for all programs and screens found in the SAP System. You can only use customer exits if they already exist in the SAP System. You find find more information about locating applications with pre-defined exits in Locating Applications that have Exits
http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
SAP EXIT:this processing type contained in variables that are delivered with SAP BW business content.
http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
User Exits: allow you to add additional functions to the SAP standard.
Programs with user exits contain subroutine calls at certain points in their syntax that are identified by the prefix USEREXIT. The actual user exits are located in an include that has been assigned to a module pool. This is where customers can include any changes (enhancements) that they want to make to the system. These includes are always processed during program flow.
Advantage: In principle, customers can modify anything they want that is found in the include (tables, structures, and so forth).
Disadvantage: SAP cannot check the individual enhancements themselves which often leads to errors
reward points if found useful
regards
palak

Diff b/w "Customer exits" and "User-exit"

Hi,
What is the difference b/w customer exits and user-exit and also please explain me what are the various types of customer and user-exits.
Thanks in advance.
Ramana

Hi,
Types of Exits
There are several different types of customer exits. Each of these exits acts as hooks where you can attach or "hang" your own add-ons.
Menu Exits
Menu exits add items to the pulldown menus in standard SAP applications. You can use these menu items to call up your own screens or to trigger entire add-on applications.
SAP creates menu exits by defining special menu items in the Menu Painter. These special entries have function codes that begin with "+" (a plus sign). You specify the menu items text when activating the item in an add-on project.
Screen Exits
Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screens flow logic.
Function Module Exits
Function module exits add functions to R/3 applications. Function module exits play a role in both menu and screen exits. When you add a new menu item to a standard pulldown menu, you use a function module exit to define the actions that should take place once your menu is activated. Function module exits also control the data flow between standard programs and screen exit fields.
SAP application developers create function module exits by writing calls to customer functions into the source code of standard R/3 programs. These calls have the following syntax: CALL CUSTOMER-FUNCTION 001.
User exits:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/abap/abap-code-samples/userexits%20in%20a%20transaction.doc
In order to find out the user exits for any tcode,
1. get the developement class of the tcode from SE93.
2. Now goto transaction SMOD and press F4,
3. give in the Deve class in the dev class and Press ENTER
this will show u the exits for any tcode.
or execute this report
http://www.erpgenie.com/sap/abap/code/abap26.htm
which gives the list of exits for a tcode
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm
For information on Exits, check these 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
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.ficoexpertonline.com/downloads/User%20ExitsWPedit.doc
http://www.easymarketplace.de/userexit.php
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/content.htm
Check out these links too...
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.planetsap.com/userexit_main_page.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
USER EXITS
https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=312792
https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=1320078
https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=2669896
****Reward points if helpful.
All the best

How to find out query name in customer exit for variables

We use the same customer exit variable in different queries. In the customer exit we want to find out, which query has called the customer exit. With the technical query name we want to read a master data table entry.
e.g. If we come from query ZG1_TEST1 we want to use selection sel1
Query name | selection
ZG1_TEST1 | sel1
ZG1_TEST2 | sel2
How can we find out the query name in the customer exit for variables?
Thanks for your help,
Evi

Hi Evi,
check out the structure I_S_RKB1D in your exit. It contains the query.
Siggi

Difference between user exit/Function exit / Customer exit and BADI

Hi Guys,
I am confused with the types of exits-user exit/Function exit / Customer exit and BADI.
Can you tell me the difference between the different exits/Enhancements?
Classify the following:
what is the one which is shown in SMOD under enhancements? There are 3 sections in that - Function module, Screen and includes.
What is the one which are called using -
Call Customer-Function 001?
Regards,
Guru

hi,
The standard applications do not offer some of the functionality you need. The R/3 enchancement concept allows you to add your own functionality to SAP's standard business applications.
Different types of enhancements
Enhancements using customer exits
Customers' potential requirements which are not included in the standard software are incorporated in the standard as empty modification 'shells'. Customers can then fill these with their own coding. Enhancements can relate to programs, menus and screens. Upward compatibility is assured. In other words, SAP guarantees that the jump from the standard software to the exit and the interface which call the exit will remain valid in future releases.
Enhancements to ABAP/4 Dictionary elements
These are ABAP/4 Dictionary enhancements (creation of table appends), text enhancements (customer-specific key words and documentation for data elements) and field exits (creation of additional coding for data elements).
advantages of enhancements
Do not affect standard SAP source code
Do not affect software upgrades
Customer exit - The R/3 enhancement concept allows you to add your own functionality to SAPs standard business applications without having to modify the original applications. SAP creates customer exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
Various types of customer exits
Menu exits
Screen exits
Function module exits
Keyword exits
Menu exit
Adding items to the pulldown menus in standard R/3 applications .
Screen exit
Adding fields to the screens within R/3 applications. SAP creates screen exits by placing special subscreen areas within a standard R/3 screen and calling a customer subscreen from within the standard dynpro's flow logic.
Function module exit
Adding functionality to R/3 applications. Function module exits play a role in both menu and screen exits.
keyword exit
Add documentation to the data elements of key words defined in the ABAP/4 Dictionary. The system displays this documentation whenever a user presses F1 to get online help for a screen field
Hope this helps, Do reward.

What is the difference between customer exits and user exits?

hello friends,
what is the difference between customer exits and user exits?

Hi
User exit - A user exit is a three character code that instructs the system to access a program during system processing.
SXX: S is for standard exits that are delivered by SAP.   XX represents the 2-digit exit number.
UXX: U is for user exits that are defined by the user. XX represents the 2-digit exit number
Customer exit - The R/3 enhancement concept allows you to add your own functionality to SAPs standard business applications without having to modify the original applications. SAP creates customer exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.     *-- Mani
The following document is about exits in SAP :-
The R/3 enhancement concept allows you to add your own functionality to SAPs standard business applications without having to modify the original applications.
SAP creates user exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
Types of Exits
There are several different types of user exits. Each of these exits acts as hooks where you can attach or "hang" your own add-ons.
Menu Exits
Menu exits add items to the pulldown menus in standard SAP applications. You can use these menu items to call up your own screens or to trigger entire add-on applications.
SAP creates menu exits by defining special menu items in the Menu Painter. These special entries have function codes that begin with "+" (a plus sign). You specify the menu items text when activating the item in an add-on project.
Screen Exits
Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screens flow logic.
Function Module Exits
Function module exits add functions to R/3 applications. Function module exits play a role in both menu and screen exits.
When you add a new menu item to a standard pull down menu, you use a function module exit to define the actions that should take place once your menu is activated.
Function module exits also control the data flow between standard programs and screen exit fields. SAP application developers create function module exits by writing calls to customer functions into the source code of standard R/3 programs.
These calls have the following syntax:
CALL CUSTOMER-FUNCTION 001.
Field Exits
Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field. Example: The data element BBBNR identifies a companys international location number. You might want to set up your R/3 System so that all international location numbers are larger than 100.
The field exit concept lets you create a special function module that contains this logic.
You assign the special function module to the data element BBBNR. You then assign the module to any programs and screens in which users can add new international location numbers. When you activate your field exit, the system automatically triggers your special routine whenever a user enters a company location number.
In 4.6c, you can use "RSMODPRF" program to create field exits.
An example of a user exits :-
MODULE user_exit_0001 INPUT
    CASE okcode.
        WHEN 'BACK OR EXIT'.
            CASE sy-dynnr.
                    WHEN '100'.
                         SET SCREEN 0.
                         LEAVE SCREEN.
                    WHEN '200'.
                         SET SCREEN 100.
                         LEAVE SCREEN.
             ENDCASE.
      ENDCASE.

Difference between customer exits and user exits

difference between customer exits and user exits

Hi,
USER EXITS->
1. Introduction:
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>
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
CUSTOMER EXITS-> t-code CMOD.
As of Release 4.6A SAP provides a new enhancement technique, the Business Add-Ins.
Among others, this enhancement technique has the advantage of
being based on a multi-level system landscape (SAP, country versions, IS solutions, partner,
customer, and so on)
instead of a two-level landscape (SAP, customer) as with the customer exits.
You can create definitions and implementations of business add-ins at any level of the system landscape.
To unify enhancements of the SAP Standard you can migrate customer exits to business add-ins.
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/content.htm
In order to find out the user exits for any tcode,
1. get the developement class of the tcode from SE93.
2. Now goto transaction SMOD and press F4,
3. give in the Deve class in the dev class and Press ENTER
this will show u the exits for any tcode.
or execute this report
http://www.erpgenie.com/sap/abap/code/abap26.htm
which gives the list of exits for a tcode
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm
For information on Exits, check these 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
Regards
Kiran Sure

Key Date a Customer Exit and Variant use

Hello,
I have a query and it includes time dependent data. The key date uses a variable that is filled with the current date in a customer exit. Works nicely when the query is executed. However, if I save a variant with various values for variables on the starting/selection screen, the date is saved as a constant date and not dynamic based on the current date so that when the variant is selected to be used on a different day, the key date is the date the variant was saved and not the current date. This can be handled in R/3 ABAP report variants but I've not found a way to do it in BEx. Any help?
Thanks,
Diane

Hi,
If you are running on BI 7.0 you can maintain variants with the below code. make data sy-datum instead of user input.
You can also chect the document. It also contains a method for bw 3.5 variants.
You can schedule this program in a process chain or make variations of this as needed.
[How To Troubleshoot Information Broadcasting (BEx Workbooks)|http://www.sapadvisors.com/resources/HowtoInformationBroadcasting.pdf]
*& Report Z_MASS_VARIANT_MAINTENANCE *
*& Program to mass update BEx Variants within SAP NetWeaver 2004s *
REPORT Z_MASS_VARIANT_MAINTENANCE.
parameter variable like RSRVARIANT-VARI.
parameter vname like RSRVARIANT-VNAM.
parameter sign_01 like RSRVARIANT-SIGN.
parameter opt_01 like RSRVARIANT-OPT.
parameter low_01 like RSRVARIANT-LOW.
parameter high_01 like RSRVARIANT-HIGH.
tables: RSRVARIANT.
select * from RSRVARIANT.
if rsrvariant-VARI = variable AND rsrvariant-vnam = vname.
rsrvariant-SIGN = sign_01.
rsrvariant-OPT = opt_01.
rsrvariant-LOW = low_01.
rsrvariant-HIGH = high_01.
elseif rsrvariant-vnam = vname.
rsrvariant-SIGN = sign_01.
rsrvariant-OPT = opt_01.
rsrvariant-LOW = low_01.
rsrvariant-HIGH = high_01.
endif.
update rsrvariant.
if sy-subrc <> 0. insert rsrvariant. endif.
endselect.
regards,

Customer Exit Prompt Variables in BEx

Hi,
I created a BEx query and in that Query I need to have two prompt variables
1. Flag
2. Fiscal Month Date
Both are customer exit varioables ,so basically the abap code for Flag and Date is, by default the flag will be 0 which means whatever the inpurt Date value is ,the result set will be displayed for that date.
If the flag is changed to 1 by the user and the Date is 3/1/2013 then the result set is today-1 data
If the flag is changed to 2 by the user and the Date is 3/1/2013 then the result set is previous month data... and so on...
Can you please advice as how to create date prompt for this customer exit variable ?When I try to create it is giving me an error
Add a key figure to structure element 'selection 1' in structure 'Key figure'.
Please advice.
Thank you.

Hi,
Add a key figure to structure element 'selection 1' in structure 'Key figure'.
this message just means that you have created a 'new selection' by right clicking on the key figure structure. And you haven't yet included any key figure into this local rkf you are trying to create.Double click on this selection 1.This message will go off once you drag and add a key figure into this selection.
Once this is done , you can rename the 'selection 1' to a relevant description
Hope it helps
Regards,
Rathy

Customer exit and variables

Similar Messages

Maybe you are looking for