Transaktion variant not working

Hi experts,
I am facing a problem with a transaction variant.
I am creating a transaction variant in transaction SHD0. But can't get it to work when I afterwards is calling the transaction BBPSC02?
Step By Step:
1. Go into transaction SHD0.
2. In the field transaction code I write BBPSC02.
3. On the 'Tab' Transaction variants I write the name for the variant.
4. Go into the variant a make the field DELIV_DATE for screen 120 invisible.
5. Activate the variant.
6 Call the transaction BBPSC02 in the Gui and the Web. The field DELIV_DATE is NOT invisible??
What am I doing wrong??
Best regards Kim

Hi
you can refer this as Dave check list.
Re: To make the field for Display only on the Shopping Cart Portal
and you can cross verify from step 9.
regards
Muthu

Similar Messages

  • Layout variant not working

    Hi ,
      I have executed a report . I hide one column and saved the layout. The layout name comes on to the selection screen parameter which i have defined on the selection screen.
    PARAMETERS: p_vari LIKE disvariant-variant. " ALV Variant
    i have made the i_save = 'A' and is_default = 'x'. and also used other function modules reg. Variants.
    but if i select the layout variant in the selection screen and execute it is not working . the hidden column also coming on the output.
    But if the select the layout variant on the output of the report from the icon select layout it is working fine. the column which i have hidden is not coming. it is perfect. why it is not working when i select the variant in the selection screen.
    Regards,
    Rose.

    Hi,
    Please try this code
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_vari.
      w_variant-report = sy-repid.
    * Function module to show the variant of a ALV report
      CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
        EXPORTING
          is_variant = w_variant
          i_save     = 'A'
        IMPORTING
          es_variant = w_kvariant
        EXCEPTIONS
          not_found  = 2.
      IF sy-subrc = 2.
        MESSAGE ID sy-msgid TYPE 'S'      NUMBER sy-msgno
                WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      ELSE.
        p_vari = w_kvariant-variant.
      ENDIF.
    END-OF-SELECTION.
    MOVE w_variant TO w_kvariant.
        MOVE p_vari TO w_kvariant-variant.
        MOVE sy-repid TO w_kvariant-report.
    *   Function module to check the variant existence
        CALL FUNCTION 'REUSE_ALV_VARIANT_EXISTENCE'
          EXPORTING
            i_save     = w_save
          CHANGING
            cs_variant = w_kvariant.
        w_variant = w_kvariant.          
    CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
        EXPORTING
          i_callback_program          = sy-repid
          i_callback_pf_status_set    = 'SET_PF_STATUS'
          i_callback_user_command     = 'USER_COMMAND'
          i_callback_html_top_of_page = 'HTML_HEADING'
          i_grid_title                = text-t06
          i_grid_settings             = wa_grid_set
          is_layout                   = wa_layout
          it_fieldcat                 = t_fieldcat
          i_save                      = 'X'
          is_variant                  = w_variant
          is_print                    = wa_print
        TABLES
          t_outtab                    = t_header
        EXCEPTIONS
          program_error               = 1
          OTHERS                      = 2.
      IF sy-subrc <> 0.
        CASE sy-subrc.
          WHEN 1. RAISE program_error.
          WHEN 2. RAISE others.
        ENDCASE.
      ENDIF.
    Regards
    Krishna
    Edited by: Krishna Gowrneni on Apr 17, 2009 5:27 PM

  • Transaction variant not working in quality

    Hi,
    I have created a transaction varient in SHD0 and activated it in develpoment and then
    it is working fine in development system.Then variant transported to quality and there also
    it is activated but somehow it is not working in qulaity sytem.
    I checked in the respctive transaction with following path
    SYSTEM>>>>>STATUS>>>>>SAP REPOSITORY DATA and i can find it is transaction variant name
    below screen program.
    Pl suggest the resolution.
    Regards,
    Rushikesh

    Hi,
    Check the variant is  transported properly in QA. If present then check the transaction for the same.
    If you make this transaction for a table the check the table delivery and maintenance allowed or not. It should be maintenance allowed.
    Thanks
    Subhankar

  • Screen variant not working when assigned to transaction variant in SHd0

    Dear All,
    User requires tax code column for line items in MIRO to be made non-editable. I am using SHD0 transaction for the same. I am able to make the column grey-off by creating screen variant. The program is SAPLMR1M and screen number 6310. When tested individually thru SHD0 the variant is working perfect. But it is not working when assigned to a transaction variant. Any clues on the same would be really helpful.
    Thanks in advance
    Komal

    Hi,
    Try to record again for the whole set of screens instead of doing that for the individual tax screen and only for the tax screen make the required field disable.
    Once done and saved, you can see all the screens variants in the transaction variant.
    Use the Change WITH PROCESSING OPTION.
    Hope this solves your problem
    Regards
    Shiva

  • Screen Variant Not  working

    Hi,
    I have created one screen variant for screen for SAPLBBP_SC_UI_ITS screen 230.
    It's getting called while i checked by debugging .
    But its not working in ITS Template & in transaction also .
    In SAPgui it's not working .
    Is there any more setting for Screen variant apart from just save it & called in screen variant BADI .
    Thanks,
    SS

    Hi
    <u>This BADI as you can see by name is for Screen Variants.
    BBP_SCREENVARIANT in this case.</u>
    <b>Please read the following documentation to get the clear difference</b>
    Transaction Variants and Screen Variants
    Transaction variants can simplify transaction runs as they allow you to:
    Preassign values to fields
    Hide and change the 'ready for input' status of fields
    Hide and change table control column attributes
    Hide menu functions
    Hide entire screens
    In particular, hiding fields in connection with screen compression, and hiding screens, can result in greater clarity and simplicity.
    Transaction variants are made up of a sequence of screen variants. The field values and field attributes for the individual screens found in transaction variants are stored in screen variants. Each of these variants is assigned to a specific transaction, can, however, also contain values for screens in other transactions if this is required by transaction flow. The transaction that the variant is assigned to serves as initial transaction when the variant is called.
    There are both client-specific and cross-client transaction variants. All screen variants are cross-client, but may be assigned to a client-specific transaction variant.
    A namespace exists for cross-client transaction variants and screen variants and both are automatically attached to the Transport Organizer. Client-specific transaction variants must be transported manually.
    In principle, transaction and screen variants can be created for all dialog and reporting transactions. There are, however, certain Restrictions that apply to certain transactions, depending on their internal structure.
    No transaction variants are possible with transactions already containing preset parameters (parameter transactions and variant transactions).
    Screen variants
    Screen variants allow you to simplify screen editing by:
    Inserting default values in fields
    Hiding and changing the ready for input status of fields
    Hiding and changing the attributes of table control columns
    A screen variant contains field values and attributes for exactly one screen.  A screen variant can, howevever, be assigned to multiple transaction variants. Screen variants are always cross-client; they may, however, be assigned to a client-specific transaction. They can also be called at runtime by a program. The different possibilities for calling screen variants guarantee great flexibility of use.
    For more information, see: Calling Screen Variants
    A specific namespace has been designated for screen variants and they are automatically attached to the Change and Transport System.
    Hope this will help.
    Please reward suitable points.
    Regards
    - Atul

  • Transaction variant not working

    Hey,
    I am facing with this peculiar problem of transaction variant. I created a transaction variant as desired by my client for VA01 and activated the same. I checked the status in the transaction VA01 and there it showed that the transaction variant has been successfully applied. But when I check for the fields that I wanted to be made non editable or invisible the same was not reflected in the transaction. Now after trying enough like creating new transaction variants, adding new screen variants to the existing transaction variant, somehow it has started working. But now when I change the transaction variant, even after activating it, the changes in the variant are not reflected in the transaction. Old changes are being reflected. Please advise!
    The reconstruction steps are as follows:
    SHD0 -
    Creation of transaction variant - with processing.
    Activating it.
    Appreciate a quick response. Thanks in advance.
    Note: It might be that I am going wrong somewhere, I would really appreciate if someone could send me a file containing screenshots on how to create and use transaction variants. My email ID is
    [email protected]
    Regards,
    Z

    hi,
    just check out the following pre-requisites if you have followed them or not:
    You can assign various transaction variants to individual sales document types.
    With the help of transaction variants, you create various variants for the same transaction in order to simplify your transaction flows. You can achieve this by:
    Preassigning fields with values
    Fading out and changing input availability for fields
    Fading out entire screens
    In this way, you can provide your users with screens which are defined according to their specific needs per sales document type.
    When a transaction variant is created, several screen variants are created for each individual screen for the transaction chosen for the variant. The system accesses this screen variant when a transaction variant is applied.
    PrerequisitesIn the standard system, transaction variants for Sales (for example, quotation, sales order, credit memo request, group master contract) are defined for all business objects. Assignment of transaction variants for the sales document type is carried out in Customizing for sales document types.
    Activities
    You will find the transaction for creating a transaction variant in Customizing, under General Settings - Field Display Characteristics - Configure application transaction fields. You can find further information on this in the implementation guide.
    Assignment of transaction variants to sales document types can be found in Customizing for Sales, under Sales - Sales Documents - Sales Document Header - Define Sales Document Types in the Variants field.
    In order that a transaction can be called up depending on a sales document type, the system of course needs the information as to which sales document type should be worked with. This choice is however made by the user on the initial screen first.
    This means that the initial screen can not be modified or faded out within a transaction variant. If you wish to miss out or modify the initial screen with the choice of sales document types, you need to create a variant transaction, this means a variant is created for a complete transaction. This transaction will then have ist own name, which has been defined by you.
    regards,
    Siddharth.

  • Bex Query variants not working

    Hello Experts,
    I have a unique problem with one of my queries, the query variants which are created before Nov 1 are not fetching any vaules instead it gives a message MAKE ENTRY IN ALL THE FIELDS......
    the variants which are created in Nov are working fine.....we have not done any upgrade....
    does anyone faced this kind of problem? what needs to done to get back the variant values in the selection screen.
    Any help is highly appreciated.
    Regards

    Was there a change to an InfoObject that is in the InfoProvider that is also one of the query input options?
    e.g. IO ZHARA used to be defeined as a Char with a length of 4, but was changed after Nov 1 to Char, length of 8.
    If you change an IO like this that is in the variant, that will render the variant unusable.
    There is a program that checks for variants that have been broken like this, and another that you enter the query's technical name and it repairs the variant.
    Try a search on SDN for something like "query variant program".  I'll post the program names after I get back in the office tomorrow.

  • Create transaction with variant not working

    Hello!
    Here's my issue -- I have a program that, right now, is more of a shell than anything else.  It is to access the HR Logical Database PNPCE, and to help filter the data I pull back, I created a Selection View with a couple of additional fields.  I put the necessary values in these fields and saved it as a Variant.
    All I want to do is create a transaction to run my program and start it using my Variant to fill in these additional fields.  Using SE93, I can create a plain transaction with no problem.  However, if I click the "Start with variant" drop-down field, I get a response that says screen 1000 (my default Selection Screen) has no variants.
    At first we thought there was some client-side things needing configuration, but if I go create a quick-and-dirty program with a single Selection Screen value (no Selection View) and a Variant, SE93 sees the variant with no problems.  So I'm wondering if maybe it has something to do with the fact that I'm using a Selection View.  Unfortunately, I'm so new to ABAP, I'm completely stuck on how to proceed.
    Any suggestions?  Thank you so much!

    Saquib, thank you SO much!  You're right -- that worked.
    As a relative newbie to SAP R/3 and ABAP, I'm new to little quirks like this.  In other examples, the list (F4) does show the variants.  For some reason, this one didn't.  I entered it anyway, saved, and ran the transaction, and it popped up with the fields populated from the variant.
    Again, kudos and thank you so much.  Points duly awarded.

  • BEx workbook Default variant not working with Broadcaster

    Hi,
    We are broadcasting a BEx workbook, which has more than 1 queries. We have a default variant to populate all the input variables. But while broadcasting, this default variant is not populated sometimes, So the query returns wrong results. It happens randomly. I have checked broadcast logs also nothing unusual found. Can someone throw some light.
    Thanks

    Hi,
    We are broadcasting a BEx workbook, which has more than 1 queries. We have a default variant to populate all the input variables. But while broadcasting, this default variant is not populated sometimes, So the query returns wrong results. It happens randomly. I have checked broadcast logs also nothing unusual found. Can someone throw some light.
    Thanks

  • Current Period" attribute for Variants not working correctly

    Hi Expert,
    Pls i need your advice on the issue screenshot below.
    When creating variants, a dynamic screen selection can be chosen for “Current Period” that will pre-populate begin and end dates. The problem is that, this attribute gives calendar month dates, not our company accounting period dates i.e. 4-4-5.
    Can this be corrected?
    I have an option to create the fiscal year variant to fix the problem but am not sure on how to go about that.
    Pls advice.
    Regards
    Femmy John.

    Hi Marssel,
    Thank you for the quick respond.
    Kindly explain to me the importance of using this field period and execute same setup?
    will this populate our company accounting period dates i.e. 4-4-5.
    I just want to get the fact right before going to the customer.
    Regards
    Femmy John

  • Voice command "Wrong" and "No" (and variants) not working!

    I've read one other thread on this, and I believe it concluded in an exchange at the apple store. Has anyone else experienced this, and resolved it? I can't correct anything, it would be really nice if I could, so I don't have to frantically click end call when it calls someone instead of playing music.
    Am I missing something? Everything else is working perfect.

    Coventry Neil figured it out: Unless there are multiple choices to a voice command's end result, the wrong, no, cancel and variants don't apply. So, if, for instance you say "Dial. Bob." and you have a contact named Barbara that it has confused it for, and Barbara has a Mobile entry AND a Home entry, it will stop and ask for which. At this time, since you were trying for Bob, you can say "no" and it will stop. If, however, Barbara has only ONE entry for Home, it will call Barbara and there is no way to stop it without scrabbling for the Cancel button on your phone.
    Eventually Barbara will become annoyed, you will no longer be friends with Barbara, you can then remove Barbara from your contacts, and then you can call Bob to your heart's content.

  • Layout variant is not working in background in ALV report

    Hi,
    I have one LAV report to send the report output through mail in foreground and backgroud.Final internal table is having 46 fileds to display the output.But here user is saving the layout variant and sending that layout variant output to mail id in excel format with zip file.Its working in foreground.But in background its not working.Even if we select the layout variant,its sending all the 46 fileds to mail.
    here we have used the below FM to update the fieldcat itab.
    CALL FUNCTION 'REUSE_ALV_GRID_LAYOUT_INFO_GET'
        IMPORTING
          et_fieldcat   = it_fieldcat[]
          es_variant    = v_disvariant
        EXCEPTIONS
          no_infos      = 1
          program_error = 2
          OTHERS        = 3.
    In for ground NO_OUT = 'x' for non selected fields and NO_OUT = ' ' for selected fields.
    But in background NO_OUT = ' ' for all the fileds, even if we select the layout variant.
    Please suggest me  with the solution.
    Regards,
    Jayaram

    hi ,
    Do according to this
    SORT t_ekbe by belnr.
      if  t_ekbe[] is not initial  .
          SELECT  MBLNR
            BWART
            SMBLN
            ERFMG   " This is the new added field
            erfme     " This is the new added field
          INTO CORRESPONDING FIELDS OF TABLE t_mseg
        for all entries in t_ekbe
          from mseg
          where mblnr = t_ekbe-belnr
          AND   bwart = '101'.
      endif.
    after this
    loop at t_ekbe .
    loop at t_mseg  where mblnr  = t_ekbe-belnr .
      t_ekbe-ERFMG = t_mseg-ERFMG .
    t_ekbe-erfme =   t_mseg-erfme  .
    modify t_ekbe transporting ERFMG  erfme .
    clear t_mseg .
    endloop.
    clear t_ekbe .
    endloop.
    Regards
    Deepak .

  • Database Variant to Data.vi not working for the Date datatype with LV 8.2?

    I'm moving a large body of LV database code from LV 7.1 to 8.2 and find that the Database Variant to Data.vi is not working correctly when used with the Date datatype. It works fine with 8.0, and the common Variant to Data works also. Am I missing something? Thanks in advance for any assistance. Wes

    Thanks for the prompt reply Crystal,
    The data is stored in an Oracle database using the DATE type. I'm querying many rows along with other columns and converting each of the values as necessary for each column with the 'Database Variant to Data' vi. Only conversion to Timestamp is no longer working as of version 8.2. I recognize that plain Variant to Data works but I have many (100's) of VIs to change if that is the only solution (not the end of the world). Most often the dates are originally generated in the database using PL/SQL procedures calling SYSDATE which look like: 5/1/2006 11:56:26 AM (in TOAD anyway) which I then need to read into LV as type Timestamp.
    Regards, Wes.

  • Two transaction variant do not working for a user

    Hi Gurus
    I have created two Z t code and made transaction variant through T Code SHD0 and assigned these two ZTcode to a user. now when a user is running the Ztcode screen variant is active on only one. when i assign second one to  the user again than screen variant of first ZT code do not work.
    can any one tell me why system is doing so.
    Regards
    Shiv

    Hi, I have the same situation. Can you please help how your case got solved ?
    Basically I have created two transaction variants- one for XD02, the other for XD03. When I am trying to assign a user to both these transaction variants ( using SET PROPOSAL), only one is getting assigned, other is getting deactivated. Please help.

  • Transaction variant to disallow change in FB02 not working for FBL5N / FB09

    Hi SAPtechies,
    I have created a transaction variant to disallow change in all fields other than Text (BSEG-SGTXT), and activated it for standard transaction FB02.
    This works well when FI document is changed via transaction FB02, but fails when the same document is changed via FBL5N / FB09.
    The screen is same for FB02 & FBL5N:
    Program (screen)     SAPMF05L
    Screen number        301
    Program (GUI)        SAPMF05L
    I have already checked for enhancement in PBO INCLUDE MF05LO00, but there was no success.
    Can anyone suggest me another methadology to greyout or make FB02 fields uneditable, with same functionality also working for FBL5N/FB09?

    Hi ,
    I could achieve  a way to disallow editing in FB02 item level fields using substitution & custom exit.
    Additional requirement was that I want to assign authorization for particular users who can change all fields.
    Any suggestions on it?
    Our Basis team has created new role & assigned this role for FB02.
    But this role has got many technical authorization objects.
    Below check is not working:
    AUTHORITY-CHECK OBJECT 'S_TCODE'
               ID 'TCD' FIELD sy-tcode.
    Thanks...Tanaya

Maybe you are looking for