How to create process variant for delete index in a process chain

Respected all
I am creating a process chain, but unable to create process variant for the delete index. kindly tell me the
step by step proceure for creating the variant for delete index. also if we use variant which is previously prepared then will it be safe? will it affect the other running process chian.
pls reply
thanks
abhay

Hi,
Please do not use an already created variant for index deletion. It might delete indices of some other cube.
You can follow the following steps -
1. Open the chain in Edit mode and click on "Process Types" button
2. On the Left hand side you will have various process types. Choose "Data Target Administration" and expand it.
3. Choose the first process "Delete Index" (it will be marked with a trash bin sign) and drag it to your chain
4. It will ask you create a variant. Press the create Button
5. In new window enter the Process Variant technical name and description
6. Then in new window choose Object Type = Cube through dropdown and Object name via browsing. After choosing the cube name click on "Transfer Selections"
7. Save and return to your chain
8. It will automatically generate a create index step also after delete index.
9. You need to break the link between create and delete step and insert infopackage in between to get the following steps - delete index --> load cube --> create index.
Please let me know if this is helpful..
Regards
nishant

Similar Messages

  • How to create a variant for  a selection screen  button

    hi ,
          i have  created a selection screen for a normal report .   
    In the selection screen  there is one button after the selct option for company code. when user enters some company code and  presses the button the user i call a able contraol in which user gives some additional values for the comapny code.
    how  do i create variant.  when i create  varaint  for the slection screen  it does  not take into account the  other screen i called .
    so every time user has to click that button and enter some values and execute. please suggest  some way.
    THANKX IN ADAVANCE:)

    Hi,
          Inorder to create a variant for selection screen report, you need to enter valid data on the screen and click on the SAVE button which is available in the Menu.
          And regarding the button you were asking about after select option, it is not created manually it comes automatically,, you can remove this by mentioning no-extension after the select-option. You can get clear information of this if you do F1 help on select-option.
    My advice to you, make effect use of F1 help.
    Edited by: Madhuri on Sep 23, 2008 4:46 PM

  • How to create a variant for a screen (not a selection screen)

    Hi
    I foud a function module RS_CREATE_VARIANT.
    Is this the correct fm for creating screen variant, if yes then pls provide me some help about how to pass values to this fm.
    if not then pls help me to find out new one.
    thnks
    satisfactory answer will be definitely rewarded.
    S@meer

    passing values to RS_CREATE_VARIANT.
    data : LS_VARIANTDESC TYPE VARID.
      DATA : LT_VARIANTTEXT TYPE TABLE OF VARIT ,
             WA_VARIANTTEXT TYPE VARIT.
      DATA : TT_REPORTPARAM TYPE TABLE OF  RSPARAMS,
             WA_REPORTPARAM TYPE RSPARAMS.
    CLEAR LS_VARIANTDESC.
              LS_VARIANTDESC-MANDT   = SY-MANDT.                " gr 46A
              LS_VARIANTDESC-REPORT  = 'ZXXXXX'.
              LS_VARIANTDESC-VARIANT = 'VARIANT'.
              LS_VARIANTDESC-EDAT    = SY-DATUM.
              LS_VARIANTDESC-ETIME   = SY-UZEIT.
              REFRESH LT_VARIANTTEXT.
              CLEAR WA_VARIANTTEXT.
              WA_VARIANTTEXT-MANDT    = SY-MANDT.               " gr 46A
              WA_VARIANTTEXT-LANGU    = SY-LANGU.
              WA_VARIANTTEXT-REPORT   = 'ZXXXXXX'.
              WA_VARIANTTEXT-VARIANT  = 'VARIANT'.
              APPEND WA_VARIANTTEXT TO LT_VARIANTTEXT.
           CALL FUNCTION 'RS_CREATE_VARIANT'
                  EXPORTING
                    CURR_REPORT               = 'ZXXXXX'
                    CURR_VARIANT              = 'VARIANT'
                    VARI_DESC                 = LS_VARIANTDESC
                  TABLES
                    VARI_CONTENTS             = TT_REPORTPARAM
                    VARI_TEXT                 = LT_VARIANTTEXT
                  EXCEPTIONS
                    ILLEGAL_REPORT_OR_VARIANT = 1
                    ILLEGAL_VARIANTNAME       = 2
                    NOT_AUTHORIZED            = 3
                    NOT_EXECUTED              = 4
                    REPORT_NOT_EXISTENT       = 5
                    REPORT_NOT_SUPPLIED       = 6
                    VARIANT_EXISTS            = 7
                    VARIANT_LOCKED            = 8
                    OTHERS                    = 9.
                IF SY-SUBRC EQ 7.
    If variant with same name already exists, change variant
                  CALL FUNCTION 'RS_CHANGE_CREATED_VARIANT'
                    EXPORTING
                      CURR_REPORT               = 'ZXXXXX'
                      CURR_VARIANT              = 'VARIANT'
                      VARI_DESC                 = LS_VARIANTDESC
                    TABLES
                      VARI_CONTENTS             = TT_REPORTPARAM
                    EXCEPTIONS
                      ILLEGAL_REPORT_OR_VARIANT = 1
                      ILLEGAL_VARIANTNAME       = 2
                      NOT_AUTHORIZED            = 3
                      NOT_EXECUTED              = 4
                      REPORT_NOT_EXISTENT       = 5
                      REPORT_NOT_SUPPLIED       = 6
                      VARIANT_DOESNT_EXIST      = 7
                      VARIANT_LOCKED            = 8
                      SELECTIONS_NO_MATCH       = 9
                      OTHERS                    = 10.
                ELSEIF SY-SUBRC NE 0.
                MESSAGE WITH 'Cannot create/change variant for'
                SY-UNAME.
                ENDIF.

  • How to create Transaction Variant for T code F-30

    Hi
    I want to create a Transaction variant for T code F-30, so that user can't change the currency field and put any value in rate. Currency should be always in USD.
    Any input will be heighly appriciated.
    Regards
    Shiv

    Hi,
    In that case you can use transaction SHD0 to create a transaction variant for F-30 with its screen variant for screen# 122. And you also want to creat a so called Variant Transaction Z-something for F-30 using the mentioned transaction variant. You restrict users to use that Z-something. For other unrestricted process, the system will still cal F-30. Here is the documentation:
    http://help.sap.com/erp2005_ehp_03/helpdata/EN/67/232037ebf1cc09e10000009b38f889/content.htm
    Regards

  • How to create a variant for a program without selection screen

    Hi All,
    I've created one program which takes the data from 30 tables and loads into one final table.
    This program is already moved to Production.
    But while creating variant it's not allowing, since the program doesn't have the selection screen.
    Is there anyway where I can create a variant in production without selection screen directly as the program code is already moved to production.
    Thank You,
    Regards,
    Karthik.Ch

    Hi ,
    Are you running this program in a process chain??

  • How to create t-code for a table and how to create transaction variant???

    Hi,
    I have created a custom table zsark.
    Now my requirement is : I have to create a transaction variant zsark_var for sm30 and table zsark. I have to disable the output of the first screen. I have to assign the transaction variant to the transaction code of table zsark.
    Now,
    1.     how to create transaction code to a table. Can any one give me the 
                    staps??
    2.     how to create transaction variant for the above requirement???
    Thanks & Regards,
    Sarkar

    Hi
    1 Goto SE93 transaction
    2 Choose 5th option Transaction with parameters
    3 Give transaction : SM30, Check Skip Initial Screen Press Enter
    4 Goto Bottom left corner, click F4 select viewname, on right hand side give table name
    5 Press one more time F4, choose update , mark it X on right side.
    6 save the transaction.
    Thanks
    sandeep
    reward if helpful

  • How to creat the Varient for 1099MISC With Holding Tax

    How to create the Variant for 1099MISC With Holding Tax ?

    HI,
    please follow the below steps to create variant at report.
    tcode se38
    report RFIDYYWT
    pass all the parameters
    press save icon
    give variant name
    retrive the variant in report
    tcode se38
    report name RFIDYYWT
    press : shift + F5
    or get varinat icon.
    I hope above will resolve your issue.
    Regards
    Madhu M

  • How to create transactoin code for a predefined variant?

    Hi,  I have created one variant for a custom report.How to create transaction code for the report with that variant?

    When you create the transaction in SE93 select the Program and selection screen(Report transaction) type not
    the transaction with variant(Variant transaction)

  • How to create info area for process chains?

    How to create info area for process chains?

    Hi,
    If I understand your question clearly, you want to assign display componets.
    once you have created you chain you assign the components by clicking CTRL+F11
    Regards,
    Namrata

  • How to create an extension for generated type idoc

    Hi all,
    Can u please look into this
    How to create an extension for generated type idoc ?  for example Idoc type BATMAS02

    Enter transaction WE30 (ALE->Extension-> IDOC types->Maintain Idoc type)
    - Type in your name of the extended IDOC type (usually starting with 'Z') and click on the Basic IDoc type, click the create icon.
    - Click on Create new and enter a description and press enter.
    - Click on ZIDOCTYPE01 and then on the Create icon.
    - Enter ZIDOCTYPE as the segment type, click on Segment Editor.
    - Enter a description for your segment type and create.
    - Enter a description for your segment, enter each field required in your IDoc and press enter to validate.
    - Save and generate, press back
    - To release the segment choose Goto, Release from the menu.
    - Check the box on the line of your segment.
    - Save, back and enter.
    - Your Idoc type structure should be displayed with your new segment.
    - Save and back.
    - To release the Idoc type choose Extras, Release type from the menu and Yes.
    ALE FUNCTION MODULE ENHANCEMENTS
    Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application.
    The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
    • For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
    • From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
    • Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
    Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
    All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
    When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
    • Execute transaction CMOD.
    • Enter name of project, say CSTMAST1.
    • Click on Create.
    • Enter a description of the project.
    • Save.
    • Click on SAP Enhancements.
    • Enter VSV00001 for Enhancement.
    • Save.
    Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
    As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
    The two important factors to consider while developing the customer function are:
    1. The point in the ALE function module where the function exit occurs
    2. The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
    Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
    Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
    Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
    Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
    • From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
    • Find Customer Function 001.
    • Double-click on 001.
    • The function EXIT_SAPLVV01_001 will be displayed.
    • Double-click on INCLUDE ZXVSVU01.
    • You will be asked to create a new include object. Proceed as desired.
    • Enter code (as in Listing 1).
    • Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
    Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
    To maintain the contact personâs business address of a customer:
    • Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
    • Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
    With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
    Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
    The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
    Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
    regards,
    srinivas

  • How to create a variant to a maintenance view (trans: SM31)

    Hi gurus.
    I have created a maintenance view (called z_jest). By running it from SM31 there is a variant option. However, I am not able to create the variant which I want to filter a selection upon in this transaction.
    I have even looked into transaction SE54 and created a variant for the maintenance table view there( called z_jestv). Then going back to transaction SM31 and view z_jest, i push 'Variant' radiobutton and type as variant: 'z_jestv', I only get the message: "Variant z_jestv for object z_jest does not exist".
    Can anybody please advice on how to create and/or connect the variant to the maintenance view?
    Regards LL.

    Hi Mahalakshmi
    Thanks for reply.
    When I look into the procedure, there is a prerequisite: "The basis dialog for which the maintenance variant is created already exists."
    I am a little bit unsertain if I miss this 'Basic dialog'. Can you please advice on how to check / create this 'basic dialog' before I go on to create the variant. (I need this 'basic dialog' as input in the procedure you sent.)
    (Note: I have already created a 'maintenance dialog' for the view, but I have a feeling, that is something different...)

  • MMPV - Close period - How to create a variant

    Hello all,
    Transaction MMPV is used to close the MM period and open a new one. Currently, we run this transaction every month MANUALLY.
    We would like to create a variant that will open the new period automatically every month. The only problem is the period / year that changes every month (I do not know how to create a variant with changed values - if it is at all possible).
    How can we create a variant that will run every month to close the MM period ?
    Thanks for your help,
    Isaac

    Hello Isaac
    It is possible......But to make it happen you need to go with date field and not with Period and year.
    Steps -
    1 - Enter field FROM Comp Code and TO Comp Code
    2 - Enter the date (E.g - 05-Mar-2007)
    3 - Save as varient....Give the varient names as required.
    4 - Activate the 4th checkbox (Selection variable) in front of date field
    5 - Click on button 'Selection variable' at the top of screen.
    6 - Click on YELLOW light. This will turn it GREEN. Now you have 1st light as YELLO which was previously yello.
    7 - Click on the down arrow just below the yello light.
    8 - Select the appropriate option and save the varient.
    The day of batch job scheduling depends upon the options you selected in the 8th step.
    I hope it clarifies your dought and will allow you to create the varient as per your requirement.
    Best Regards
    Avinash

  • Find flagged process orders for deletion

    Hi all ,
    How do i find flagged process orders for deletion ?
    i need report or t-code

    Hello,
    Try with t-code COOISPI. In selection,Put material no and system status(sel. at header level) as DLFL
    and also check  "with deeltion flag indicator"
    Check with result and revert.
    Regards,

  • How to Create a Variant BOM

    Hi All,
    Can you please let me know the Process of How to Create a VariantBOM? Preferebly Step-by-Step Process?
    Highly appreciate for your valuable inputs.
    Thanks and Regards,
    Venkat
    Edited by: venkat Korada on Jan 3, 2008 10:14 AM

    Hai Venkat,
    Please go thr. this link.
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
    Reward if helpful.
    Regards
    Pradeep Belur

  • How to Create a Variant in WebDynpro Java apllication

    Hello-
    we have a requirement where we require to create a Variant for some of the Webdynpro application.
    Now that is there any functionality which allows to do so , there are various reports and how will i populate the variant data , does it require backend table and FM for pulling those data..
    How will I save the variant data and access them.
    Regards,
    Raj

    Hi Raj,
             I don't think there is a ready made variant functionality in WD Java like in SAP R/3.  But we can have a work around. As you thought, we have to create a BAPI/RFC and custom table(s) to store the data. So initially, you have to call this RFC and get the data from the tables and then you have to set main RFC/BAPI and   then execute it. Add an additional button to save the variant, onAction of the button update the execute the variant RFC and save the current data in custom table.
    Regards,
    Siva

Maybe you are looking for