Call transaction variant - crmd_order

Hi,
i have created a new transaction variant for cmrd_order. I'm trying to call the new tcode (zcrmd_order) in the abap code by passing the order number using call transaction.
i have used the call transaction ..with bdcdata mode 'E' and im having problems. it works fine ...but now and then it displays the pop up box and couldnt figure out why.
is there a better way of calling this transaction variant.
Thanks,
kris.

Hi Sandra,
i'm using the following statement
Call transaction 'ZCRMD_ORDER' using t_bdcdata options from T_opt .
Some users are getting the pop-up box while for others its working fine. it works fine when the call transaction statement is being called for the first time. But when its called for the second time, this pop-up box appears.
Not sure why this is happening.
I have recorded the screens and passed those to bdcdata tab and didn't use skip first screen.
Let me know where i'm going wrong.
Thanks,
kris.

Similar Messages

Call transaction variant from IW51

hi ,
i have created a transaction variant for va01.
i want to call this transaction only when user creates sales order
from IW51(service notification) .i dont know how to call transaction variant from iw51.
i would appreciate your help on this.
thanks,
yoga

Hi,
You may refer this
Passing Variant's value to a transaction iview
Thanks
Prashant

Transaction variant for Goods Issue going back to MB1A transaction screen

Hello,
I have created a transaction variant ZMB1A for Goods issue.
When the goods issue transaction completed by using ZMB1A system again going back to the initial screen of MB1A. (Since it is the base of MB1A)
Here the issue is everytime user had to enter the ZMB1A transaction. (for example if the user wants to issue material for different plants).
Please suggest any suitable method to avoid the above multiple t code execution.
Regards
Rifaie M

Hi,
In SHD0, do the complete processing of Transaction MB1A during creation of Transaction Variant "ZMB1A" till posting of the Material document.
To create a new T-Code as ZMB1A, go to Transaction SE93 and here enter Transaction Code as ZMB1A and Click Create button. Now enter Short text of Transaction and select option "Transaction with Variant (Variant transaction)" and press enter.
Here enter following;
Transaction MB1A
Transaction variant ZMB1A
Activate "Cross-client"
Select Professional User Transaction
Activate SAP GUI for HTML
Activate SAP GUI for Java
Activate SAP GUI for Windows
Now Click SAVE button.
Now you can start using Transaction ZMB1A which will call Transaction Variant ZMB1A.

Call Transaction CRMD_ORDER

Hi experts,
I made a report displayed in ALV and one of the column was the transaction no.
Now, my user wants it to display the specific line in CRMD_ORDER once it is being double click in the grid filtered by lead. My problem is that the transaction no. under lead unable to display.
Here is my code below.
leadno or transaction no.
*&      Form user_command
FORM user_command USING r_ucomm LIKE sy-ucomm
                        rs_selfield TYPE slis_selfield.
READ TABLE it_data INTO wa_data INDEX rs_selfield-tabindex.
IF SY-SUBRC EQ 0.
CASE r_ucomm.
    WHEN '&IC1'.
       SET PARAMETER ID 'CRM_OBJECT_ID' FIELD wa_data-leadno.
        CALL TRANSACTION 'CRMD_BUS2000120' AND SKIP FIRST SCREEN.
ENDCASE.
ENDIF.
ENDFORM.                    "user_command

hi,
check this.
FORM user_command USING r_ucomm LIKE sy-ucomm
rs_selfield TYPE slis_selfield.
CASE r_ucomm.
WHEN '&IC1'.
READ TABLE it_data INTO wa_data INDEX rs_selfield-tabindex.
SET PARAMETER ID 'CRM_OBJECT_ID' FIELD wa_data-leadno.
CALL TRANSACTION 'CRMD_BUS2000120' AND SKIP FIRST SCREEN.
ENDCASE.
ENDFORM. "user_command

Problems with SKIP FIRST Screen when calling a transaction variant

Hi,
I have a transaction variant of VA02 that suppresses the display of the pricing button on the conditions screen. I have created a variant transaction for called ZA02 which calls this variant of VA02.
In my program I have coded the following :-
      SET PARAMETER ID 'AUN' FIELD VBELN.
      SET PARAMETER ID 'VPO' FIELD POSNR.
      CALL TRANSACTION 'ZA02' AND SKIP FIRST SCREEN.
I would have expected the program to display the second screen of VA02 but it displays the first screen and when I hit return key the second screen is then displayed.
I don't think I need VPO setting but when I code
      SET PARAMETER ID 'AUN' FIELD VBELN.
      SET PARAMETER ID 'VPO' FIELD POSNR.
      CALL TRANSACTION 'VA02' AND SKIP FIRST SCREEN.
VA02's second screen is displayed
Any help as to how to Skip this first screen with ZA02 would be greatly appreciated
Thanks
Rous

Yes you are right Reg thanks for that.
But it appears that VA02 doesn't require it setting anyway. I changed the PID to APO and indeed I've even commented the line out, but my program goes to the second screen when calling VA02 but stays on the first screen when calling ZA02 .

Call transaction (MF60) with variant

hi
in user will save some variant of the TCODE : MF60, and will put they in job what use SM36 to set job schedule.but the resule message can't be know in BG work.
i want to write a report to run the Transaction (MF60) and to save message with abap application log.
first:
how to find the Transaction contain variant?
second:
if i use abap code: CALL transaction in report,how to set variant to transaction.
three:
i know the command:SUBMIT will call from VARIANT:
but MF60's report is RMPU_SEL_SCREEN,but this report have two transaction: MF60,MF63.
how to set Transaction to this RMPU_SEL_SCREEN.
four:
i know the SM36 will set variant to TCODE,how to open job in ABAP.
thank you very much!

in my company,users will create themselves varaints about MF60.
and they put variants in job schedule (use SM36 ) in bg work at night.
so when these job is over,the last message don't show for they.
they doubt about it and they will spent lot time to get what oneself document for last genearate.
i want to write a report and put this report in job schedule to run MF60.
and get last message for call transaction in abap appliacation log.
next day users just use TCODE SLG1 to view last night run MF60 result.
so first i must get all MF60 of variant what will be run and get message
when this transancations is over.save message in database!
thank you very much for your help!

How to call a variant for a transaction

Is it possible to call a specific variant (say test) for a transaction like MMBE?

Dear Pinkey,
You can use transaction SHD0 (Transaction Variant)
http://help.sap.com/saphelp_webas620/helpdata/en/eb/5fab41d79b11d296190000e82de14a/content.htm
In the SAP Reference IMG, you can create transaction variants. Choose Basis Components -> Application Personalization -> Tailoring of Application Transactions -> Configure Transaction-Related Display Values for Fields (Transaction SHD0). Transaction variants allow you to preset values for fields in a transaction, set field attributes, or hide entire screens.
To execute a transaction variant, you define a variant transaction using the Transaction Maintenance transaction (SE93).
Once you have entered a transaction code and short description, choose transaction type Transaction with variant (Variant transaction).
To define a variant, enter the name of the transaction and the name of the variant. You can then use the new transaction code to start the special variant of the transaction.
Hope this will help.
Regards,
Naveen.

How to deny users to call standard transaction variant

Hello!
We have created a variant transaction (ZME52N) for ME52N, and do not
want give authorization to the transaction ME52N for end users.
We unchecked the authorization check in the SE97 for ZME52N-ME52N pair so the authorization check for ME52N does not take place in the function module AUTHORITY_CHECK_TCODE.
However, we noticed that both calling and called transaction is ME52N in the the function module AUTHORITY_CHECK_TCODE, when we executed the variant transaction ZME52N, and obviously the auth check failed.
Is there a way to lock / disable the ME52N instead of uncheck the authorization ?
Thanks in advance!
Regars,
Daniel

>
Daniel Kaoro Kobashigawa wrote:
> But this is the point. He wants to disable ME52N for everybody and use the ZME52N instead of ME52N.
Well, I read your question different, you state "We have created a variant transaction (ZME52N) for ME52N, and do not want give authorization to the transaction ME52N for end users. " End users for me is non-technical support for SAP. ME52N will not work for user IDs with SAP_ALL and these are not your typical users. If this is your goal then SM01 is what you want.

Transaction variant Tcode called in ZPROGRAM

Hi Folks,
I have created transaction variant for t code MM01.
And created a transaction code for this transaction variant using SE93.
ZMM01_MAT is transaction variant t code.
Now I am trying to call this transaction variant t code(ZMM01_MAT) from other program to fill the next internal material number and pass it to ZMM01_MAT(passing material no from program to screen).
When I select a select views and click on “sales:sale org. data1” view, it is not prompting the screen to enter plant/Sales org/Distribution channel values (it will prompt screen in MM01 and ZMM01_MAT transaction codes).
Below is the coded in ZPROGRAM where ZMM01_MAT is calling
SET PARAMETER ID 'MXX' FIELD 'X'.
SET PARAMETER ID 'MAT' FIELD lv_matnr.
CALL TRANSACTION 'ZMM01_MAT'.
please help us on this.
Sri

Hi,
I don't know if I understand your requirement.
If you want to add new variant TCODe like MIGO_TR and assign Accounting document, I would follow this way:
1. try to add entry to table T158 (in SE16)
2. use related entry (for existing TCode) as a reference for fields entry.
3. save and test if it works
hope it helps.
regards,
wojciech

SolMan 4.0 CHaRM / CRMD_ORDER: Authorize Change Request by CALL TRANSACTION

After creating a Change Request I need to execute the action "Authorize" by some kind of CALL TRANSACTION but until now I have not found a solution for this. There are a few forum questions similar to this one but all I've seen are still not answered.
The problem is caused by the Toolbar Control in screen "Edit: Normal Correction nnn": the dropdown and select actions are not recorded by the Batch Input Recorder and are not executed, the following function code "SAVE" therefore does not work as needed (thus creating the CRM service process and Task List).
To find out what the event handling really does in order to make SAVE work is handicapted by this: I have not been successful in debugging the execution of the event handler.
Before I start to search for more details (which might turn out as a very time consuming advanture) I would like to ask for some help of you. If you have any idea on how to solve the problem, sharing your expertise would be appreciated. Thank you.

No further interest in this topic

Call SAP Transaction Variant from Iview

Hello,
I know we can pass parameters into a SAP transaction via the 'Application Parameters', but this does not always work especially for complicated selection screen options.
Can the actual transaction variant ID be passed instead?
Regards
Mr.T

Hi,
You may refer this
Passing Variant's value to a transaction iview
Thanks
Prashant

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.

How to create Transaction Variant

Hi all,
I have a requirement like this
I need to create a transaction variant for the table CEPCT, for the transaction SE16 and want to disable or invisible CREATE and CHANGE options in that
Can any one help me out in this requirement
Regards
Srinivas

Hi,
Recording a Transaction Variant
Transactions variant are recorded through transaction SHD0.
   1. Enter the transaction code you want to record u2013 here BP, and press enter
   2. Enter a name for your transaction variant u2013 here Z_BP_NO_PERSON. Please notice that the naming convention for transaction variant requires that it starts with Z or Y.
   3. Push Create
You have now called transaction BP in recording mode.
   1. When you push the exit button you will get the following popup
   2. Enter a name for the screen variant u2013 e.g. Z_BP_NO_PERSON,
   3. Press the deactivate menu function, and you get the following popup.
In this Popup you can deactivate menu functions.
   1. Open the Menu Bar à Business Partner à Create
Position the cursor on u201CSCREEN_1000_CRE_PERS Personu201D
   2. And push the deactivate button.
   3. Push enter
   4. And u201CExit and Saveu201D
   5..Save the Transaction Variant.
Thanks,
NNR.

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

Call transaction CJIC using bdcdata and skip first screen

I want to call transaction CJIC and skip first screen. I have set parameters for fields for which I need to pass data. But one field namely display variant has no parameter id. How can I pass value to it and also skip first screen?
I have tried passing its value in bdcdata and also passing ONLI. But it does not run in mode "N". What can be the solution?

Hi frnd,
fortunately transaction CJIC is selection-screen of an executable program RKPEP012.......so u don hav to use call transaction and instead u can use SUBMIT statement................
submit RKPEP012 WITH SELECTION-TABLE rspar
Effect
If you specify this addition, parameters and selection criteria on the selection screen are supplied from an internal table rspar. You must specify an internal table with the row type RSPARAMS for rspar. The structured data type RSPARAMS is defined in the ABAP Dictionary and has the following components, all of which are data type CHAR:
SELNAME (length 8),
KIND (length 1),
SIGN (length 1),
OPTION (length 2),
LOW (length 45),
HIGH (length 45).
To supply parameters and selection criteria for the selection screen with specific values, the lines in the internal table rspar must contain the following values:
SELNAME must contain the name of a parameter or selection criterion for the selection screen in block capitals
KIND must contain the type of selection screen component (P for parameters, S for selection criteria)
SIGN, OPTION, LOW, and HIGH must contain the values specified for the selection table columns that have the same names as the selection criteria; in the case of parameters, the value must be specified in LOW and all other components are ignored.
If the name of a selection criterion is repeated in rspar, this defines a selection table containing several lines and passes it on to the selection criterion. If parameter names occur several times, the last value is passed on to the parameter.
The contents of the parameters or selection tables for the current program can be entered in the table by the function module RS_REFRESH_FROM_SELECTOPTIONS.
Notes
In contrast to selection tables, the data types of the components LOW and HIGH in table rspar are always of type CHAR and are converted to the type of the parameter or selection criterion during transfer, if necessary.
When entering values, you must ensure that these are entered in the internal format of the ABAP values, and not in the output format of the screen display.
Revert back for queries.
Cheers,
Will.

Call transaction variant - crmd_order

Similar Messages

Maybe you are looking for