SAP Customer Exit - Customer Namespace (i.e. /ABC/)

Hi ABAP Experts,
The question I would like to ask is when taking advantage of a SAP customer exit, can you assign the work to a customer namespace (i.e. /ABC/) ?
The problem seems to be that we want the majority of our custom development in our customer reserved namespace i.e. /ABC/.  Yet, to activate a customer exit, the ABAP code follows the old "Z" standard.  For example, customer exit EXIT_RMMR01RS_003 has the include ZXM08U03.  To activate this exit, one would create the include ZSM08U03 and include customer code.  Unfortunately, the include ZSM08U03 can't be assigned to a package with /ABC/.
Any help would be greatly appreciated.
Thanks,
Jay

i dont think so. the reserved name spaces are for specific vendor products, while exits are for all customers.so exits would not be able to use a reserved name space.. but within that exit ZXM08U03 you can create another include using /ABC/ name space

Similar Messages

  • Customer Exit Variable in SAP BI

    Hi to all,
    Please can any body tell me , What is Customer Exit Variable in SAP BI , how to use it , why we use it.
    please also sned any website link , or any PDF or DOC file that have example to explain Customer Exit Variable in SAP BI.
    I shall be thankfull to you for this.
    Regards
    PAVNEET RANA

    Hi,
    Customer Exit Variable in SAP BI : is used to calculata MTD,YTD, and some other calculations.
    You can define variables with Customer Exits and then write code in CMOD. See the Article/Blogs in the same
    https://wiki.sdn.sap.com/wiki/display/profile/Surendra+Reddy
    CHeck the Following Articles.
    Customer Exit Variables in BW/BI Reports
    Using Customer Exit Variables in BW or BI Reports Part - 1
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/business-intelligence/s-u/using%20customer%20exit%20variables%20in%20bw%20or%20bi%20reports%20part%20-%201.pdf
    How to use Customer Exit Variables in BW Reports: Part - 2
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/business-intelligence/g-i/how%20to%20use%20customer%20exit%20variables%20in%20bw%20reports%3a%20part%202.pdf
    Using Customer Exit Variables in BW/BI Reports Part - 3
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/10fc4382-afa6-2c10-1380-fa224fe4324f&overridelayout=true
    Using Customer Exit Variables in BW/BI Reports: Part - 4
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0fefc77-40e3-2c10-8da3-d4bfcb013387?quicklink=index&overridelayout=true 
    Calculating the Ageing of the Materials
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/business-intelligence/a-c/calculating%20the%20ageing%20of%20the%20materials.pdf
    Thanks
    Reddy

  • 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

  • Copying  SAP Exit to Customer Exit

    Dear Experts,
            i need to create Customer exit for Clearing Date, Posting Date and netDuedate. For this i am going to copy the SAP EXIT Variables 0p_keydt, 0p_Keyd2, 0p_keyd3, Bcoz i had created Infoset, sothe technical name get changed, So I cant call SAP Exit variables for this new Info Object.
    What I need is Can U please Explain me how to copy these theree variables in to Customer Exit as i am very new to ABAP. After Copying the Code what i need to change to suits my requirement.
    Please help me in this regard as this is very Urgent.
    I ahve tries in searching the previous thread, i just got the Overview alone.
    Thanks in Advance

    Hi,
    I do not know if we can directly convert a SAP exit to a CMOD exit.
    What I was suggesting was that, create a CMOD exit (custom project) and in the coding part you can copy the code from the existing code and replace the varaible names.
    Check this link for more help on CMOD project creation -
    [http://wiki.sdn.sap.com/wiki/display/ABAP/CustomerExits(CMOD)]
    Hope it helps.
    Regards,
    RahulM

  • "Customer Exit", "SAP Exit"

    Hi,
    In BEx, while creating a new variable, I see the options such as "Customer Exit", "SAP Exit" etc. What is the purpose of these options and what functionality do they provide?
    Reg,
    Sbastian

    Customer exit are used to automaticcaly fill variable value.You can check the code as follows:
    GO to SE37
    Enter EXIT_SAPLRRS0_001
    Double Click ZXRSRU01 .
    Check where your varible's code is embedded. If you don't know where it is, try doucle clicking on the INCLUDEs and your code should start with WHEN <your variable name>.
    Hope it helps.
    Regards

  • How to find CUSTOMER EXIT for a Standard SAP program

    How to find CUSTOMER EXIT for a Standard SAP program

    Hi
    To introduce the techniques of enhancement in standard SAP system. 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.
    They do not affect standard SAP source code.
    When you add new functionality to your SAP System using SAP’s 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 SAP’s standard software package.
    They do not affect software updates.
    When you add new functionality to your SAP System using SAP’s 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.
    Any change made to an SAP object in a customer system is called a modification. Customers usually modify their systems for one of two reasons. Either they make changes to the SAP standard in order to adjust the R/3 System to their specific business needs (actual modifications), or they alter individual SAP objects in order to correct an error (as recommended in an SAP error note).
    You should only modify the SAP standard if the modifications you want to make are absolutely necessary for optimizing work flow in your company. Be aware that good background knowledge of application structure and flow are important prerequisites for deciding what kind of modifications to make and how these modifications should be designed.
    SAP application programmers create SAP enhancements in transaction SMOD using function module exits, menu exits, and screen exits.
    Customers are given a catalog containing an overview of existing SAP enhancements. They can then combine the SAP enhancements they want into an enhancement project using transaction CMOD.
    SAP enhancements are made up of component parts. These components include function module exits, menu exits, and screen exits. A specific component may be used only once in a single SAP enhancement (this guarantees the uniqueness of SAP enhancements).
    Customer enhancement projects consist of SAP enhancements. Each individual SAP enhancement may be used only once in a single customer enhancement program (this guarantees the uniqueness of a customer project).
    SAP application programmers preplan function module exits, menu exits, and screen exits for their applications and combine them to create useful enhancements for the R/3 System.
    Customers create their own enhancement projects for their systems using SAP enhancements. You can customize the individual components of an enhancement project by creating your own include programs (for function module exits), texts (for menu exits), and subscreens (for screen exits).

  • Give me details about  customer exit, sap exit using characterstics variabl

    give me details about  customer exit, sap exit using characterstics variable

    Hi,
    Customer Exit:
    http://help.sap.com/saphelp_nw04/helpdata/en/f1/0a56f5e09411d2acb90000e829fbfe/content.htm
    SAP Exit:
    http://help.sap.com/saphelp_nw04/helpdata/en/f1/0a56f5e09411d2acb90000e829fbfe/frameset.htm
    Characteristic Variables:
    http://help.sap.com/saphelp_nw04/helpdata/en/5c/8db07d555411d189660000e829fbbd/frameset.htm
    SAP and Customer Exit:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662562d
    Some Imp Docs:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/650ee690-0201-0010-4bb7-83c3e2a74039
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/009819ab-c96e-2910-bbb2-c85f7bdec04a
    Assign points if these are helpful.
    Rgs,
    I.R.K

  • SAP BEx Customer Exit

    Hi Gurus,
    I've implemented the code below for my report to display Required Start Date (MM/DD/YYYY) by searching and processing either a single Fiscal Year/Period (PPP/YYYY to PPP/YYYY) input or a range/interval Fiscal Year/Period (PPP/YYY) input. The details are,
    1) Created 1 User Entry Interval Mandatory Variable under Fiscal Year/Period InfoObject (Display) - ZFYP_IN
    2) Created 1 Customer Exit Interval Mandatory Variable under Required Start Date InfoObject (Output) - ZRSD_CX
    *&  Include           ZXRSRU01
    DATA: L_S_RANGE1 TYPE RSR_S_RANGESID,
          L_S_RANGE TYPE RSR_S_RANGESID,
          LOC_VAR_RANGE TYPE RRS0_S_VAR_RANGE,
          ZYEAR TYPE T009B-BDATJ,
          ZMM TYPE T009B-POPER,
          ZMM1 TYPE T009B-POPER,
          ZYEAR1 TYPE T009B-BDATJ,
          ZSTARTDATE TYPE SY-DATUM,
          ZENDDATE TYPE SY-DATUM.
    IF I_STEP = 2.
    CASE I_VNAM.
    **To populate ZCURDAY with current system date**
       WHEN 'ZCURDAY'.
        CLEAR: L_S_RANGE1.
        L_S_RANGE1-LOW    = SY-DATUM.
        L_S_RANGE1-SIGN   = 'I'.
        L_S_RANGE1-OPT    = 'EQ'.
        APPEND L_S_RANGE1 TO E_T_RANGE.
    **To Lookup ZREQSTDAT with 0FISCPER*************
    **This loop will capture the Fiscal Year/Period range input by the user**
       WHEN 'ZRSD_CX'.
        READ TABLE i_t_var_range WITH KEY VNAM = 'ZFYP_IN'
          INTO LOC_VAR_RANGE.
        IF SY-SUBRC = 0.
           CLEAR L_S_RANGE.
    **This 2 call functions are used to convert the Fiscal Year/Period range into**
    **Calendar Day range for use on further lookup in Required Start Date**
           ZYEAR = LOC_VAR_RANGE-LOW(4).
           ZMM = LOC_VAR_RANGE-LOW+4(3).
           CALL FUNCTION 'FIRST_DAY_IN_PERIOD_GET'
             EXPORTING
               I_GJAHR              = ZYEAR
             I_MONMIT             = 00
               I_PERIV              = 'SC'
               I_POPER              = ZMM
             IMPORTING
               E_DATE               = ZSTARTDATE.
           IF ZMM EQ 012.
              ZMM1 = '001'.
              ZYEAR1 = ZYEAR + 1.
           ELSE.
              ZMM1 = ZMM + 1.
              ZYEAR1 = ZYEAR.
           ENDIF.
           CALL FUNCTION 'FIRST_DAY_IN_PERIOD_GET'
             EXPORTING
               I_GJAHR              = ZYEAR1
             I_MONMIT             = 00
               I_PERIV              = 'SC'
               I_POPER              = ZMM1
             IMPORTING
               E_DATE               = ZENDDATE.
           ZENDDATE = ZENDDATE - 1.
    **A third and final function to use the calendar day range provided to lookup on matching**
    **dates in Required Start Date (ZREQSTDAT)*************************************************
           L_S_RANGE-SIGN  = 'I'.
           L_S_RANGE-OPT   = 'BT'.
           L_S_RANGE-LOW   = ZSTARTDATE.
           L_S_RANGE-HIGH  = ZENDDATE.
           APPEND L_S_RANGE TO E_T_RANGE.
        ENDIF.
    ENDCASE.
    ENDIF.
    However, after doing extensive testing I discovered that the code is only able to process 1 period at a time versus an interval of periods as required.
    For example,
    Input Fiscal Year/Period Interval - 001/2011 to 004/2011
    Expected returned dates - 02/27/2010 to 07/02/2010 (4 periods)
    Actual returned dates - 02/27/2010 to 04/02/2010 (only 1 period, the 1st period and not the balance 3 periods)
    Only the first period is returned versus the periods entered. I'm not sure what is missing from the code to process the entered interval.
    Appreciate any help provided.
    Warm regards,
    Eric

    Hi,
    After looking your code, I think the problem is at the below mentioend part.
    WHEN 'ZRSD_CX'.
    READ TABLE i_t_var_range WITH KEY VNAM = 'ZFYP_IN'
    INTO LOC_VAR_RANGE.
    IF SY-SUBRC = 0.
    CLEAR L_S_RANGE.
    **This 2 call functions are used to convert the Fiscal Year/Period range into**
    **Calendar Day range for use on further lookup in Required Start Date**
    ZYEAR = LOC_VAR_RANGE-LOW(4).
    ZMM = LOC_VAR_RANGE-LOW+4(3).
    Here, you should put validation like this.
    If not LOC_VAR_RANGE-LOW is initial.
          If not LOC_VAR_RANGE-HIGH is initial
              ZYEAR = LOC_VAR_RANGE-HIGH(4).
              ZMM = LOC_VAR_RANGE-HIGH+4(3).
             else.
              ZYEAR = LOC_VAR_RANGE-LOW(4).
              ZMM = LOC_VAR_RANGE-LOW+4(3).
    endif.*
    else.
    put a validation to see that some input is given for fiscal year
    endif.
    only after these lines go for your function modules. This way, if your variable has range given, it would calculate till the higher range given for fiscal period.
    Edited by: Rahul K Rai on Jul 15, 2010 11:17 AM
    Edited by: Rahul K Rai on Jul 15, 2010 11:18 AM

  • Puzzled about Customer Exits

    Hi everyone,
    I'm trying to get into the field of customer exit coding to enhance reporting capabilities. Now from what I've learned, the way to go is via one of the SAPLRRS0 exits and do the actual coding in includes like ZXRSRU01, which should be located in the customer namespace (since it's a 'Z', as I understand) and hence be modifiable. Still, if I try to edit the file, SAP asks for a developer key, but I thought this was the whole point about customer exits (and what sets them apart from user exits): Since you're not tampering with the original system, there would be no need for a developer key
    I have also checked in SE03 if the customer namespace is modifiable (from what I can tell it is).

    Hi Tilman Budde ,
    Keys are required at 2 levels .
    1. When you try to modify existing sap object ... This is called as object key.
    2. When you try to modify existing sap object ..This is called as developer access key ..Unless your user id have this (developer key) ..even if you have object key you will not be able to modify abap workbench objects..
    Hope that helps.
    Regards
    Kapadia
    ***Assigning points is the way to say thanks in SDN.***

  • 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 item’s 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 screen’s 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’.
    <b>User exits:</b>
    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

  • What is diff b/w user & customer exit

    Hi
    Good afternoon everybody,
    Plz differentiate user exit and customer exit.
    What is the way to findout user exits and how to modify it.
    Thanks in advance
    Venkat

    Hi Venkat,
    Check the following description
    Customer exits: The R/3 enhancement concept allows you to add your own functionality to SAP’s 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.
    If you want to enhance the functionality of your SAP System, you should take advantage of the exits available in standard R/3 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 SAP’s 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 SAP’s standard software package.
    They do not affect software updates
    When you add new functionality to your SAP System using SAP’s 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.
    In contrast to customer exits, user exits allow developers to access and modify program components and data objects in the standard SAP System.
    User exits: 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.
    I hope this helps.
    Regards,
    Kinshuk

  • Default value of BeX customer Exit variable not Displayed in WeBI??

    Hello Experts,
    We are stuck with a problem where WeBI report is created on top of BeX query and we are not able to see the default value of Bex Customer exit variable in WeBI run. Here is the complete scenario:
    1. One restricted KF is created in BeX, restricted with Customer exit variable on net Due date. And this variable is mandatory, ready for input, and Default value in calculated is user exit as current Week's Monday.
    2. So, by default KF data should be restricted to Monday of current week, if user does not change this value.
    3. Now, WeBI report is created on top of this Bex query, and all is working fine, i.e. we are getting variable as Prompt in WeBI, but Default value is not shown while Running the Webi Report.
    So, need your inputs on the same, if default values from BeX in WeBI is supported or not? If yes, why this is happening, and how to resolve it?
    Please notice, the restrcition is in KF only, it is not a separate restrcition on Net Due date in Filter area or in Defualt area of BeX
    and we are on SAP BW 7.1 and BOXI 3.1 SP4.
    Regards,
    Vipul
    Edited by: VIPUL GOYAL on Nov 23, 2011 9:44 PM

    Hi,
    See 1285993 - Support of Customer Exit Variables from BEx query into WebIntelligence via OLAP universe
    WebI will prompt when executed, but the default values calculated by the user exit  - do not appear.
    Note: If the BEx variable has property 'ready for input' set / enabled, then its WebI prompt shows ok, but no default value appears.
    Cause
    This behaviour expected 'by design' (in the context of the product's current limitations) as explained in the online guide below:
    Please refer to Chapter 7, page 44, document link here: http://help.sap.com/businessobject/product_guides/boexir3/en/xi3_sap_olap_universes_en.pdf
    Characteristic variable > processing type > Customer Exit  is "Supported, without user entry"                                                                               
    -->  This should be understood as meaning "User will not be shown a prompt"
    regards,
    H

  • 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,

  • Calculations on customer exit using input variable

    hi,
    suppose i have a date input variable on my query, and i want to use the input value as an input for a calculation to be done in a different characteristic variable whose value is derived via a customer exit. how could this be done?
    as an example - i have an input date field, and say, the user enters 1/15/2005. the other characteristic variable is, for example, sales for a given date, restricted against a characteristic variable (customer exit) which should restrict the KF to say, the start of the month of the input date up to the input date (in this case, 1/1/2005 - 1/15/2005).
    thanks in advance. =)
    ryan.

    Hi Ryan,
    you have to use parameter I_STEP = 2 in your exit (IF I_STEP = 2. (...))
    This second step is called after the processing of the variable pop-up and only for those variables that are not marked as “ready for input” and are set to “mandatory variable entry”.
    Build your second variable in this way and then you can use this step to see first (pop-up) variable value.
    For details see www.service.sap.com/bw -> SAP BW InfoIndex -> Variables -> How to... Derive a Variable value from another variable 2.x (pdf).
    Hope it helps (and please don't forget to assign some points by clickin'on the yellow star to the contributors that help you !!!)
    Bye,
    Roberto

  • Customer Exit Variable not working in BO-Webi Report

    Hi All,
    I have created a universe based on Bex Query.
    Bex query consists of a customer exit variable on Calendar year/month where in it will populate current calendar year month by default while executing the query. It works fine while executing in SAP BI Bex Analyser.
    I have created a universe based on the query. For Calender year/Month i got L00, L01, LOV values in universe.
    Based on the universe I have created a Webi report. I did not specify calendar year/month as query filters. While directly executing the Webi report, I get the calendar year/month variable screen. But the value for it not populated based on customer Exit code written in BI.
    What has to be done to get the customer exit values in variable screen.
    Thanks for your understanding.
    -- Selva

    Since you have customer exit variable in your bex query, it will be like a global filter in your universe.
    Execute the webi report and check whether you are getting only current month data.
    --- Thanks

Maybe you are looking for