Variants Missing

Hi
I understand if variants from 3.x are not imported into 7.0 then we can a program RSR_VARIANT_XPRA ........ But please tell me where we would run this program can anyone give me steps...
regards
Naga

Hi
I am new to this....... Can you explain step by step..... i would also like to know what is a Variant?
In SE38> Program: RSR_variant_xpra> Suboject: Variant
Do we need to create a variant... In the selection screen for creating variants it is has options like Infocube,query,variant ...Please explain how to run this program in se38 and please send me some material on using se38 so that i can understand it in  a better way.....
Regards
Naga

Similar Messages

  • Report Layout variant missing in ECC6

    Hi All,
    we are going for upgrade from 4.6 to ECC6. In ECC6 in most of report's  report layout variant are missing in ECC6.But our client want same variant in ECC6 as in 4.6.
    Please sugest how to over come this issue.
    Thanks
    Mohit Khandelwal

    Mohit,
    I think you can try out this...
    Include the variant in a transport request and give the transport req no to the basis guy; and inform him to import the same req no into ECC6 version.
    He can export the transport req no from 4.6 to windows desktop and then he can import the same into ECC 6 system.
    I hope this will solve your issue.
    - Seenu
    Edited by: Sreenivasulu Nallani on Jan 25, 2010 12:24 PM

  • Report variants missing in PC00_M10_REC after upgrade from 4.7 to ECC 6.0

    After Upgrade to ECC 6.0 from 4.7 version, two  variants for  Payroll Reconciliation report  in PC00_M10_REC  are missing.
    These variants were of users who have left the organisation/company.
    Can anyone help me to restore those variants and tell me why those two variants got deleted.
    Thanks in advance
    Rohan Das.

    Try to use program RSTRANSP , this will create transport request for variants. after creating the variant your basis team can move to ECC box
    a®

  • BI Admin Cockpit: Program variant missing in Process chain

    Hi,
    I'm installing BI Admin Cockpit and have troubles with Process chains. I followed the installatin guide and had problems activating process chains: 0TCT_C2_INIT_P01 and 0TCT_MD_C_FULL_P01 because of missing InfoPackages. I solved this by installing an correction as it is described by Note: 1432353. After this I activate these Process chains manually in RSA1 Administration--> BI Content -->Process Chains (all necessary objects). No Problems occured. The Problem is when I'm start these Process chains, I get an error on the last step. There is an Abap Programm with an variant. This variant is missing in the System.
    The Variants are:
    - RSTCC_Dataload (0TCT_C2_INIT_P01)
    - RSTCC_QRuntime (0TCT_MD_C_FULL_P01)
    I tried also to get these Process chains with Dataflow before and after to view if I forgot anything to activate, but there is no programm variant. Can anybody explain, how to get these programm variants?
    Thanks and greetings,
    Sebastian

    Sebastian,
    I faced the same problem. Basically what I found was that variants were not defined. So I manually created the value for variants:
    1. For RSTCC_DATALOAD assign value  TCT_C2_DELTA_P01
    2. For RSTCC_QRUNTIME  assign value   0TCT_C0_DELTA_P01
    Our system info is similar to what you have and I in fact had Basis team patch BI Cont to level 6 but this did not help. If I were to take a guess i would have to say that these variants are missing in the 7.01 BI version, you can either choose to create a OSS message with SAP and wait for them to fix it or you could fix it manually.

  • After unicode conversion Variant missing

    Dear All,
    After unicode conversion in transaction S_ALR_87013611 and
    S_ALR_87013613 variant is missing.
    We checked in table VARIT - "Variant Texts" data is missing.
    Kindly suggest.
    Thanks and regards,
    Joseph

    Hello
    Did you discover the reason for this? We are now facing the same issue and we cannot find the reason.
    I don't think that note 987914 can be the answer.
    Can it be something connected to the procedure for conversion or caused by a wrong-executed step?
    Every suggestion can help,
    Thanks
    Luca

  • After System Refresh Variants missing

    Hi,
    We have used Export / Import method to build QAS system from production
    ABAP export file.
    After System refresh we got the same Production client with all
    configurations, Variants, Object including data.. Which is Perfect.
    But, as per our business we don't want to use the same production
    client number in Quality System., so we done Cliet Copy to copy to
    different client (ex: Client 200) using SAP_ALL profile.
    Question: But after client copy we found that some Data, Objects,
    Variants are missing in the new client (200).
    Ex: In Client 100 (Copy of production client) table T009 is having 10
    entries, but after client copy in client 200 the same table doesn't have any
    entry in that including standard and Z.
    Please help me on this, how do I get clone / copy of 100 client
    (original client)
    Thank You,
    Ramesh

    Hi Ramesh,
    Looks like your client copy didn't bring all the data and Objects, Did you checked logs, Is there any error message ? The client copy completed with all the tables ?
    You can try Remote client copy method .
    You can manually export the variants from the source client to Target client and you need to export the Variants from the table VARID, VARI, VARIT and VARIS.
    You can use the below forum procedure to export and import variants.
    how to export RFC destination to file in order to import it in an other sys
    Since, not only the variants you are missing data and Objects, I would suggest for re-copy the client.
    Regards,
    Arjun

  • ALV layout variant missing in background job.

    hi guys,
    Having problem on getting the default ALV layout variant when run the job in backgorund. Please advise any correction needed in the following code.
    Thanks.
    *&  Include           Z_MM_KBR_AGSUBCONINV_MOD2                        *
    MODULE status_0100 OUTPUT.
      SET PF-STATUS '100'.
      SET TITLEBAR '100'.
    ENDMODULE.                 " STATUS_0100  OUTPUT
    *&      Module  display_data  OUTPUT
          text
    MODULE display_data OUTPUT.
    IF sy-batch IS INITIAL. "Foreground
      IF w_container IS INITIAL.
        IF cl_gui_alv_grid=>offline( ) IS INITIAL.
    *Creating the container
          CREATE OBJECT w_container
            EXPORTING
              container_name              = c_container
            EXCEPTIONS
              cntl_error                  = 1
              cntl_system_error           = 2
              create_error                = 3
              lifetime_error              = 4
              lifetime_dynpro_dynpro_link = 5
              OTHERS                      = 6.
          IF sy-subrc <> 0.
         MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
          ENDIF.
        ENDIF.
    *Creating the ALV GRID
        CREATE OBJECT w_grid
          EXPORTING
            i_parent          = w_container
            i_appl_events     = c_check
          EXCEPTIONS
            error_cntl_create = 1
            error_cntl_init   = 2
            error_cntl_link   = 3
            error_dp_create   = 4
            OTHERS            = 5.
        IF sy-subrc <> 0.
         MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        ENDIF.
        else.
         exit.
        ENDIF.
      ELSE.
    *Creating the ALV GRID
        CREATE OBJECT w_grid
          EXPORTING
            i_parent          = go_dock_container
            i_appl_events     = c_check
          EXCEPTIONS
            error_cntl_create = 1
            error_cntl_init   = 2
            error_cntl_link   = 3
            error_dp_create   = 4
            OTHERS            = 5.
        IF sy-subrc <> 0.
          WRITE:/ 'Error in grid'.
        ENDIF.
         CREATE OBJECT w_grid
          EXPORTING  i_parent = go_dock_container.
      ENDIF.
    *getting the variant option
        wa_variant-report     = sy-repid.
        wa_variant-username   = sy-uname.
        wa_layout-grid_title  = sy-title.
        wa_layout-cwidth_opt  = c_check.
        wa_layout-zebra       = c_check.
        wa_layout-no_f4       = c_check.
        wa_layout-sel_mode    = 'D'.
    *Excluding the unwanted buttons
         PERFORM exclude_toolbar_buttons.
    build field catalog.
        CALL FUNCTION 'LVC_FIELDCATALOG_MERGE'
          EXPORTING
            i_buffer_active        = c_check
            i_structure_name       = c_fcat_str
            i_bypassing_buffer     = c_check
          CHANGING
            ct_fieldcat            = t_fieldcat
          EXCEPTIONS
            inconsistent_interface = 1
            program_error          = 2
            OTHERS                 = 3.
        IF sy-subrc <> 0.
         MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        ENDIF.
        loop at t_fieldcat into w_fieldcat.
         if w_fieldcat-FIELDNAME = 'AGING1'.
          W_FIELDCAT-NO_ZERO = 'X'.
          MODIFY t_fieldcat FROM W_FIELDCAT INDEX SY-TABIX.
         ENDIF.
        endloop.
    Generate sort critria
        PERFORM generate_sort.
    Create object of class lcl_event_receiver.
        CREATE OBJECT w_event.
    Handler for events.
       SET HANDLER w_event->handle_top_of_page       FOR w_grid.
       SET HANDLER w_event->handle_print_top_of_page FOR w_grid.
       SET HANDLER w_event->handle_print_end_of_list FOR w_grid.
        SET HANDLER w_event->handle_hotspot_click     FOR w_grid.
    *Displaying the alv
       IF NOT sy-batch IS INITIAL.
         PERFORM create_snp.
       ENDIF.
    t_data = i_final.
        CALL METHOD w_grid->set_table_for_first_display
          EXPORTING
            i_save                        = 'A'
            is_layout                     = wa_layout
            is_variant                    = wa_variant
          CHANGING
            it_outtab                     = t_data
            it_fieldcatalog               = t_fieldcat
          EXCEPTIONS
            invalid_parameter_combination = 1
            program_error                 = 2
            too_many_lines                = 3
            OTHERS                        = 4.
        IF sy-subrc <> 0.
        ENDIF.
    ENDIF.
    ENDIF.
    ENDMODULE.                 " display_data  OUTPUT
    *&      Module  user_command_0100  INPUT
          text
    MODULE user_command_0100 INPUT.
      DATA: lt_rows TYPE lvc_t_row,
             w_rows TYPE lvc_s_row.
      CASE sy-ucomm.
        WHEN c_back.
          LEAVE TO SCREEN 0.
        WHEN c_exit.
          LEAVE TO SCREEN 0.
        WHEN c_cancel.
          LEAVE TO SCREEN 0.
       WHEN 'BILDET'.
         CALL METHOD w_grid->get_selected_rows
           IMPORTING
             et_index_rows = lt_rows.
         CALL METHOD cl_gui_cfw=>flush.
         IF sy-subrc EQ 0.
           READ TABLE lt_rows INTO w_rows INDEX 1.
           READ TABLE i_vbfa INTO w_vbfa INDEX w_rows-index.
           IF sy-subrc EQ 0.
             CLEAR i_zbw_br_nf4.
             LOOP AT i_zbw_br_nf3 INTO w_zbw_br_nf3 WHERE
                         refkey = w_vbfa-v_vbeln.
               APPEND w_zbw_br_nf3 TO i_zbw_br_nf4.
             ENDLOOP.
    call dialog screen and display new alv control
             CALL SCREEN 101 STARTING AT 10 5.
           ENDIF.
         ENDIF.
         WHEN 'NOTAF'.
         CALL METHOD w_grid->get_selected_rows
           IMPORTING
             et_index_rows = lt_rows.
         CALL METHOD cl_gui_cfw=>flush.
         IF sy-subrc EQ 0.
           READ TABLE lt_rows INTO w_rows INDEX 1.
           READ TABLE i_zbw_br_nf3 INTO w_zbw_br_nf3 INDEX w_rows-index.
           DATA docnum LIKE j_1bdydoc-docnum.
           docnum = w_zbw_br_nf3-docnum.
           SET PARAMETER ID 'JEF' FIELD docnum.
           CALL TRANSACTION 'J1B3N' AND SKIP FIRST SCREEN.
         ENDIF.
      ENDCASE.
      ENDMODULE.                 " user_command_0100  INPUT
    *&      Form  modify_col_name
          text
         -->P_<FCAT>  text
         -->P_TEXT_H01  text
    FORM modify_col_name  USING  pwa_fcat TYPE lvc_s_fcat
                                 value(pw_text) TYPE any.
      pwa_fcat-coltext   = pw_text.
      pwa_fcat-scrtext_l = pw_text.
      pwa_fcat-scrtext_m = pw_text.
      pwa_fcat-scrtext_s = pw_text.
    ENDFORM.                    " modify_col_name
          FORM display_hotspot                                          *
    FORM display_hotspot USING pw_row_id    TYPE lvc_s_row
                               pw_column_id TYPE lvc_s_col.
      FIELD-SYMBOLS <l_data> TYPE zbrforecast.
    READ TABLE t_br_nf_acum ASSIGNING <l_data> INDEX pw_row_id-index.
    CHECK sy-subrc = 0.
    IF pw_column_id = ' '.
    ENDIF.
    ENDFORM.                    "display_hotspot
    *&      Form  generate_sort
          Genereate Sort criteria
    FORM generate_sort.
    Local variables
    DATA: wal_sort TYPE lvc_s_sort,
           wl_pos   TYPE numc2.
    wl_pos = 01.
    sort ORDER
    wal_sort-spos      = wl_pos.
    wal_sort-fieldname = c_aufnr.
    wal_sort-up        = c_check.
    APPEND wal_sort TO t_sort.
    ENDFORM.                    "generate_sort
    *&      Form  f4_variant
          text
         <--PW_VARI  text
    FORM f4_variant CHANGING pw_vari TYPE disvariant-variant.
    wa_variant-report = sy-cprog.
      CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
        EXPORTING
          is_variant    = wa_variant
          i_save        = c_u
        IMPORTING
          es_variant    = wa_variant
        EXCEPTIONS
          not_found     = 1
          program_error = 2
          OTHERS        = 3.
      IF sy-subrc IS INITIAL.
        pw_vari = wa_variant-variant.
      ELSE.
        MESSAGE s208(00) WITH text-t04.
      ENDIF.
    ENDFORM.                    " f4_variant
    *&      Form  validate_layout
    *This subroutine is to validate the layout
    No parameters are passed to this subroutine
    FORM validate_layout.
    IF NOT p_layout IS INITIAL.
      Check Layout
       wa_variant-report   = sy-repid.
       wa_variant-username = sy-uname.
       wa_variant-variant  = p_layout.
       CALL FUNCTION 'LVC_VARIANT_EXISTENCE_CHECK'
         EXPORTING
           i_save     = c_u
         CHANGING
           cs_variant = wa_variant
         EXCEPTIONS
           OTHERS     = 01.
       IF NOT sy-subrc IS INITIAL.
         SET CURSOR FIELD 'P_LAYOUT'.
         MESSAGE s001(00) WITH text-t06 p_layout.
         STOP.
       ENDIF.
    ELSE.
      clear wa_variant.
    ENDIF.
    ENDFORM.                    " validate_layout
    *&      Form  validate_data
          text
    FORM validate_data .
    PERFORM validate_layout.
    ENDFORM.                    " validate_data

    Hi,
    Before the call to method set_table_for_first_display, populate
    wa_variant-report = sy-repid.
    Best regards,
    Prashant

  • Really strange Font behaviour - variants missing

    Hi,
    I'd really appreciate any help.
    I have a MacBook Pro running OSX 10.4.6. I occasionally need to do some work on Quark Xpress.
    One of my documents uses a font called Berling. Under Quark XPress 6.5, I installed the font in the font book and all was well.
    Upgraded to Quark 7 - suddenly same document can't find Berling Bold or Berling Italic.
    Testing to see what the issue is, I took out Quark 7, reinstalled 6.5 and all was fine again.
    Looked in Font Book and it only showed 1 subset of Berling - Berling Roman. When I click on Berling though and select validate, all the subsets show up as working - but they are not visible in the Font Book Application. If I delete Berling and double click the Berling FFil to reinstall, Font Book only shows Roman as the only available variant of Berling. If I install this, Roman is all I can see, unless I click validate - which shows all the variants.
    Quark 7 seems to think Berling Roman is the font and that there are no variations.
    Does anybody have any idea why this would be happening?
    cheers

    The Font Suitcase file contains bitmap (screen resolution) representations of all the associated varieties of that typeface, whereas the Postscript Outline files contain vector data, telling the printer how to output the characters.
    Quark 6.5 can function with only the bitmap representations, as long as you don't try to print the file.
    The bitmap is used to display the characters on screen (screen resolution is very low compared to print resolution). However, when you try to print to a Postscript printer (or make a PDF file), Quark sends the linked Postscript Outline vector data. This allows the output device to use the best possible resolution it can produce.
    It seems that with Quark 7, they've decided to have the program detect the Outline fonts when a document is opened, rather than when you try to print - to prevent people from using typefaces then cannot use for output.
    Postsript fonts are a real pain-in-the-neck, since it's easy to separate the Outline file from the suitcase file. The newer OpenType format looks like it could solve a lot of problems.
    PowerBook G4 1Ghz 15   Mac OS X (10.4.6)  

  • Upgrade 3.0B to NW04s - Existing variant missing in new frontend!

    Hi all
    We have upgraded our system from BW 3.0B to Netweaver 2004s BI with Support Package 12 installed. On the frontend, we are using the new BEx Analyzer with SP14 (rev 797).
    Our existing query variants from 3.0B are no longer visible in the new BEx Analyzer 2004s, while new variants can be saved and used.
    The existing variants are only visible and usable from RSRT or from BEx Analyzer 3.x.
    We have applied:  Note 1003481 - Variant Migration - Migrate all variants
    and ran 'RSR_VARIANT_XPRA', before running 'RSR_MIGRATE_VARIANTS' but to no avail.
    We have looked at Note 1054634 - Query variants are not found or are not listed for selection as well.
    But we have tested with queries with technical names shorter than 25 characters but it is not working as well.
    Looking at:
    https://weblogs.sdn.sap.com/cs/user/view/cs_msg/14320
    Re: BW 3.x and 2004s upgrade
    it seems like an unresolved issue..
    Can anyone help us?

    UPDATE:
    After the RSR_MIGRATE_VARIANTS program was run, the variants were migrated over to the RSRPARAMETRIZA and RSRPARAMETRIZAT tables.
    However, the variants are still not showing up in the new BEx Analyzer frontend. We also noticed the difference between newly created variants in the new BEx Analyzer and the migrated variants:
    Newly created variants - use a !PERS47P* naming convention in the PARAMN field
    Migrated variants - use the variant name itself.
    Newly created variants - CONTENT field which contains XML information
    Migrated variants - CONTENT field XML appear to be incomplete (<> tags not closed etc..)
    Newly created variants - CONTENT field makes reference to generated ID
    Migrated variants - CONTENT field XML tried to store actual variant selection data but is incomplete.
    Has anyone used the migration programs successfully before?
    Thank you

  • Process types(Variants) missing

    hi friends,
    I have created a process chain with 5 process types(All are loading data ). I loaded data whenever necessary. when I monitoring the process chain which was run last, I did not see last two process types(variants) in my log view.this is most urgent task... is any possibility to remove process types in BI 7.0....
    now I am working in BI 7.0,  I could not find why it happened.....
    Guide and help me...
    with hopes,
    Jaya
    Edited by: jaya durai on Jul 21, 2008 5:36 AM

    Once the predecessor process gets finished it triggers the sucessor process ....
    If it has not done till now ... why dont you check the job in SM37 and also see if you have free processes or not
    Cheers!!
    Amit

  • Variants missing error in RSTRANSP

    Hi All,
    I want to transport eight screen variants of the program 'RSUSR070' to another system.
    SAP&_AUTH
    SAP&_BENU
    SAP&_CHANGE
    SAP&_MINI
    SAP&_PROFIL
    SAP&_STANDARD
    SAP&_TRANSAKT
    SAP&_VALUES
    I ran RSTRANSP but it could not find any variants and threw this message
    Now I saved these under new names (e.g. ZSAP_AUTH) so that it can be attached to a TR. Please suggest a way to get the original variants to be attached to the TR.
    Thanks.
    NAIR

    Hello All,
    I have imported the custom variants (ZSAP_STANDARD etc.) to the required system but the transaction and the program still doesn't recognize the custom screen variants. How do I associate the custom ones to these transactions?

  • Internal Order field missing on various entry screens

    Hi,
    In our production client, we don't see internal order field. It was there before. But somehow it just disappeared on screen like FB50, FB60, FB70 etc. I can see the internal order field in other environments. Can you please tell me how I can get the field back?
    Thanks in Advance

    Hi,
    Please check in FB50 the following:
    If you go to configuration (the little chart above the G/L block) -> (Box or button blue and yellow above scroll bar right side.) Then double click on configutation pick button administrator.
    You will see that some fields are flagged as "hidden". (invisible)
    Check if Internal order is hidden. If yes, unflag that selection, activate, save and check the results.
    Unflag also all the fields required.
    Please also review the following Note:
    546889     FAQ: Screen variants in FI Enjoy Transa
    186961     Maintenance of screen variants for Enjoy tr
    180504     Enjoy+screen variant: Missing authorization
    I hope it helps.
    Best Regards,
    Vanessa Barth.

  • Error in ODS Update Rules.

    Hi,
    We have an abap routine in an ODS Update rules to get FISC YEAR (type NUMC 4) with a field FISCPER(numc 7) from a table. This routine worked fine. But now we moved the abap routine to cmod program in r/3, and when I am doing a direct mapping of fiscper to fiscyear,  I am getting this error message 'Fiscal year variant missing for time conversion of characteristic 0FISCYEAR'.  I already did a direct mapping of Fiscal year variant in the update rules.
    Am I missing some thing here?
    Thanks!

    Yes, I am getting fiscvar as V6 from cmod program in r/3, and did a direct mapping in update rules.

  • ME59N batch jobs skipping PRs

    Hello All,
    We have created and schedule a background job in SM36 for program RM06BB30 (ME59N) with a variant of ME59N that selects the requisitions you wish to convert to orders with DAILY run options.
    User can see Jobs in FINISHED status in SM37 but skipping few PRs though the PRs matching the very same Variant. User is inconvenienced by this as slowing down the procurement process for the requisitioners ...
    As an work around , user then runs the same Variant + missing PRs in foreground thus converting it into POs ....
    What could go wrong with SM37 jobs ?
    a) I tested & realised PRs being edited spanning the JOB run duration skipping SENSIBLY --- Perfectly fine
    b) What else could amount to this few PRs skipping with SM37 jobs showing FINISHED green.
    Lights in that directions will be rewarded.
    Regards
    MM

    Hello Jurgen,
         I'm still investigating this issue as constrained by the magnitude / volume of Test data to be replicated to test it in Test environment...
         My client's procurement process is as follows
            a) There is a centrally agreed Contract
            b) User raises PRs manually and ME51N traces if any item referencing the Contract items & adds contract# in the PR line#.
            c) Daily batch jobs Run ME59N to convert PRs into POs (PO grouping criteria Per CCod, Per Plant, Per Contract)
         Ideally Contracts would have been converted directly into Release Orders / Call-Offs as opposed to the process above ...Don't you think step b) is quite unusual...??
         As an work around user then runs ME59N manually punching those PR items on emergency & it converts to PO strangely..
         Please shed lights on this issue of ME59N daily batch jobs skipping some PR items despite they match the variant parameters.
         Hope words are self-explanatory & comprehensive..
    Rgds
    MM

  • Variant price for one feature is missing -error in sales order

    Hello Experts,
    I am working on a SAP implementation project for a premier automobile company...
    I have stuck on one point here in this project SAP is a back end system. So sales order will generated based on the interface feed from a legacy system.
    We have Identified to have two different variant classes in SAP sales order. one will contained all vehicle specification, this will be used by PP for MRP and other variant class will have only optional features and all these features should have variant price in VA00 (maintained as pricing record) in pricing. if any of the feature don't have price then this sales sales order should through an error massage (we will customized this error message as per clients requirement)
    Can any one suggest the relevant sales order user exit or any other method to do this check?
    Thank & Regards,
    Sulabh

    Hi Sulabh,
    In standard procedure any component value of VA00 not picked by the sale order system doe's not show any kind of message.
    Use exit MV45AFZZ - USEREXIT_PRICING_PREPARE_TKOMK.take the help of ABAPer he will write the logic where the VA00
    value missing in sale order system should through the error or warning and message which will illustrate the problem,according
    to that user will check and maintain the price.
    Ram

Maybe you are looking for