Transaction variant - can all fields be gryed out?

Hi,
I want to build a wraparound for VT02n, I want all the fields to be greyed out except for one field and the save button. Can I do this using trasnaction varinats?
Thanks,
Krishna

We had this requirement in one of my previous project and we were able to create a transaction variant using SHD0 to populate decimal format, logon language and default printer name like LOCL or FRONTEND. Only in case of dates where we needed MM/DD/YYYY we had to change the parameter zcsa/moddatfm (Parameter for Default date format when creating users with transactions SU01).
Creating a transaction variant is pretty easy and you can google it or search in SDN. Basically it is something like this ..
1. executing t-code SHD0,
2. entering SU01 in Transaction code field,
3. entering some transaction variant name say Z_SU01 etc.
4. clicking on create
5. actually creating a test id with the default values you need like putting the user id name and last name and password
6. also hitting enter /continue till you are able to reach/click Default tab
7. here you put values for ex lang - as EN, decimal notation as 1,2345.67, output device as LOCL etc and then when u see screen entries - check mark on W.content for logon language, decimal notation and output device.
8. Save it and then go back ..then again save it
9. Do not forget to activate your transaction variant. To do so click on Standard variant tab -> Standard variant -> you will see activate button.
Next time you create a user id - you will see these default values. Only for dates you need to set the paramter mentioned above from value 1 to 2.
If you still have issue take help from some abapers/developers who are aware of SHDO functionality.

Similar Messages

On saving Transaction Variant for MM02 you cannot exit out

I created a transaction variant for MM02. The first problem that occured was an authorization message when I click saved. It saved the changes but then reported that I was not authorized to access MM02. Which I was not because I had authorization to run the new transaction variant. SAP solved that problem with note 529116. Now I can save and get a correct message: 'Your changes have been saved'.
But now the problem is I cannot exit out of the program because the Back and Exit buttons do not work. Has anyone else encountered this problem after implementing note 529116.

I too facing the similar problem when assigning the screen variant to transaction variant.
screen number where the 'Obj.Status' button is ' 4456
if executing the screen variant alone , it works perfectly,
once i assing to the transaction variant and test, the 'Obj.Status' button is visible.
does anyone got the solution?
Edited by: Thomas Paul jr on Oct 21, 2010 1:59 PM

What is a Transaction Variant?

hello abap gurus,
can u tell me what is a transaction variant and how does it works? i have a requirement that is to run an existing customized report program in the background. that means no user interface. i'm pretty new with abap programming. please help...
thanks,
sid

Use SE75 to create your own custom text ID for SAVE_TEXT object
Finding a user exit when you only have the function module name: Use table MODSAP with member=function module. This will give you the enhancement name that you can enter in SMOD.
To execute on OS command in SAP: Use program RSBDCOS0
Transaction Variants
Use Transaction Variants to make fields Mandatory, Hidden or Display. Also applicable to screens and tabstrips.
You can hide unwanted screens and fields in any of the standard SAP programs without changing any of the standard programs. Additional features such as making the variant as default on the standard SAP transaction code is only available as of 4.6x.
Transaction SHD0 - Create a variant for the required transaction by changing the layout through hiding fields and screens.
Transaction SE93 - Create a variant transaction (e.g. for VA02 = ZVA02).
Next allocate the transaction variant to this variant transaction.
In 4.6c, you can default your transaction variant as the standard variant. (SHD0 - Edit -> Activate/Deactivate as standard variant)
tables: tbtco.
data: jobcnt(1) type n,
      t_sdluname like tbtco-sdluname,
      t_strtdate like tbtco-strtdate,
      t_strttime like tbtco-strttime.
ZXXX is the job name to check for
select * from tbtco where jobname = 'ZXXX'
                      and strtdate = sy-datum
                      and status   = 'R'.
   add 1 to jobcnt = jobcnt.
    if jobcnt = 1.
       t_sdluname = tbtco-sdluname.
       t_strtdate = tbtco-strtdate.
       t_strttime = tbtco-strttime.
    else.
       exit.
    endif.
endselect.
if sy-subrc = 0.
   if jobcnt >= 1.
       message i999(b1) with t_sdluname ' has released job on '
                         t_strtdate t_strttime.
   endif.
endif.
Use Transaction Variants to make fields Mandatory, Hidden or Display. Also applicable to screens and tabstrips.
You can hide unwanted screens and fields in any of the standard SAP programs without changing any of the standard programs. Additional features such as making the variant as default on the standard SAP transaction code is only available as of 4.6x.
Transaction SHD0 - Create a variant for the required transaction by changing the layout through hiding fields and screens.
Transaction SE93 - Create a variant transaction (e.g. for VA02 = ZVA02).
Next allocate the transaction variant to this variant transaction.
In 4.6c, you can default your transaction variant as the standard variant. (SHD0 - Edit -> Activate/Deactivate as standard variant)
Using Transaction variants
Change SAP standard screens by hiding fields, screens, tabstrips, changing field properties, ... read on
Show all users per Application server
Transaction AL08
To log a user off via an ABAP
CALL 'SYST_LOGOFF'.
Advanced SM04 program
The following program displays the Ip address , workstation name , Nt user name etc. Plus you can send instant messages to users just by clicking on the user name. It will show a red band for users who exceeds session limit. ( That you can adjust ). Created this for R/3 4.6C and above. (Submitted by Joy Ramachandran) - Click here to download zuser.txt
Changing the SAP Logo on the top right of the SAPGui
Change file sapalogo.bmp in directory C:\Program Files\SAP\FrontEnd\SAPgui\themes\default (SAP 4.6C)
Changing the Logo on the Right Hand Side ( Courtesy of: http://sapr3.tripod.com/ )
Transaction code - SMW0
X - Binary data for WebRFC application
Hit Enter
Click Execute
Click Settings -> Maintain MIME types
Click the Create button
Fill in :- TYPE : image/gif       EXTENSION : .GIF
Click Save
Click Back to the Binary data for WebRFC
Click Create
Fill in :- Obj. name : ZXXXX.GIF Description : Company Logo
Click Import and specify the filename where your GIF file is located.File type is BIN. Finish press the Transfer button.
If successful, your logo will be shown in the Binary data for WebRFC.
Transaction codeSM30 - Table/View - SSM_CUST
Click Maintain
Click New Entries
Name                     Value to be set
START_IMAGE      ZXXXX.GIF
RESIZE_IMAGE     NO
Logoff and Login again
Automated transports
regards
vinod

How to assign screen variant to transaction variant

Hi ALL
I HAVE CREATED A SCREEN VARIANT HOW TO I ASSIGN IT TO TRANSACTION VARIANT , PLS GUIDE ME ON THIS ITS IMPORTANT

Sunaina,
Transaction Variant:
Transaction variants are client independent. That means that in order to transport them you are creating a workbench request. Client independent means that the moment you save your changes, they will appear in every client on the same box. If for instance you have 3 development clients, by creating a transaction variant you will be able to see it in all 3 clients. You won't need to use transaction SCC1 to transport your changes to the other development clients.
Say for an example you need to deactivate (output only) the pricing date and material pricing group field in VA01/2.
You can use the T.code SHD0, choose your transaction variant here, further choose your screen variant.
Next select your screen variant and in the Menu bar select Variant> change with processing>Make repairs in foreign namespaces only if they are urgent> Continue(Enter)>again 'enter'>Object can only be created in SAP package>continue(enter)> Exit and save >This variant contains other screens, adopt these as well?>enter>enter> scroll down to the entry 'pricing date' or VBKD-PRSDT make the necessary changes and save.
The system will prompt to assign a package and request enter the necessary values.
Crux:- you just make fields as display, or 'supress', knowing your requirements
Transaction Variants to make fields Mandatory, Hidden or Display. Also applicable to screens and tabstrips.
You can hide unwanted screens and fields in any of the standard SAP programs without changing any of the standard programs. Additional features such as making the variant as default on the standard SAP transaction code is only available as of 4.6x.
Transaction SHD0 - Create a variant for the required transaction by changing the layout through hiding fields and screens.
Transaction SE93 - Create a variant transaction (e.g. for VA02 = ZVA02).
o Next allocate the transaction variant to this variant transaction.
In 4.6c, you can default your transaction variant as the standard variant. (SHD0 - Edit -> Activate/Deactivate as standard variant)
One more feature available, instead of creating a new T.Code...you can simply assign the Transaction Variant in the Sales Document Type in T.Code-->VOV8.
Hope this Clarifies your Doubt and Please Reward If Really Helpful
Regds
MM

Transaction variant/Screen variant (SHDO)

Hello guys,
   Actually as far as i know, if we want to put default values for certain field in any transaction, than we can do it by SHDO.Am i right?
   Actually for production order header, i want to maintain certain default values for couple of fields.Through enhancement (PPCO0006) we can do it.But one of my friend told me that its even possible by SHDO.
So could u guys plz help me in doing this?I dont know the procedure.
In CO01 Screen, i want to maintain default values for following fields,
Plant- 1009
Order type- ZPP01.
                             Thanking you guys for all the help you provided.

You can use transaction SHD0 to create transaction variant. The transaction variant can be assigned to user.
Please look into the below process.
Creating the Transaction Variant
Choose Create to create a variant.
The system calls the application transaction that you want to create a variant for. Enter the values you want to use in the in the input fields. Each time an action is completed, a Dialog Box, appears listing the fields of the current screen with their current values. The kind of dialog box called depends on the kind of screen currently being processed (see Requirements).
Here you can determine:
if you want to save the field values you have inserted on the current screen (the "Adopt field values" checkbox)
if you want to hide the entire screen (the "Do not display screen" checkbox). This is only possible if settings are copied to your variant ("Adopt field values")
if field contents are saved (the "With contents" checkbox)
if the ready for input status of specific fields should be revoked (the "Output only" checkbox)
if specific fields should be hidden (the "Invisible" checkbox)
if specific fields should be mandatory the "Mandatory" checkbox)
You may or may not be able to select each of these checkboxes for every field depending on the field's type (--> Requirements).
Screen variants are created automatically for each screen where values have been saved (adopted). Enter screen variant names in the "Name of screen variant" field. These names must be unique. If the system is able to find a unique name for a screen variant it is automatically inserted into this field. The convention reads like so: (< name_of_transaction_variant>_(<client>)_<screen_number>).
Choose the function Continue to proceed. The following pushbuttons are available:
The Cancel function displays the current application transaction screen again. Here you can make changes to your settings.
The Menu functions function displays an additional dialog box wher you can deactivate menu functions.
The GuiXT function allows the user to edit a GuiXT script for the current screen (--> GuiXT).
The Exit and Save function exits and saves the application transaction. A list appears containing all of the screens in the application transaction that you want to save entries for (that is, all screens for which screen variants will be created).
Enter a short text for your transaction variant here.
Display settings can be changed as needed from this list in the future. Settings that require information at application transaction runtime (field values, table control columns) cannot be changed from this list.
Choose "Save". The system saves your transaction variant and the corresponding screen variants. The Workbench Organizer dialog box is displayed for the transaction variant and for each screen variant. Use it to assign each of these objects to a package.
You can also branch to this list using the Change values function during the function selection process.
Apart from this there is alternative to use role/parameter-id's and assign to the user. In this case, whenever the user logins in all the cases same values would be populated on to the CO01 screen. This is easily done by the basis consultant.
Thanks,
Srinivas Karri

About Transaction Variants

Hi friends..
At Application level, i've to customize the screen ( eg. adding/editing the field option in application).
As we know that there r options such as BADIs, Screen-exits.
But i came to know about another options as "Transaction Variant"
Can anyone suggest me regarding this.
Thanks
Suren

Hi,
we can create Transaction Variants Using SHD0 Transaction.
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).
Please check the links.
http://help.sap.com/saphelp_nw04/helpdata/en/7d/f639fb015111d396480000e82de14a/content.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/67/232037ebf1cc09e10000009b38f889/frameset.htm
Reward if useful.

Syst variable for transaction variant?

Hi,
How to identify current transaction code with variant. We can't use sy-tcode as it shows orginal transaction code. Sy-slset is also empty allways?
Thanks
Shekar

hi Reddy ,
check the Documentation of SHD0.Its nothing but modifications of Screen fields.
Regards
Prabhu
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).
Regards
Prabhu
PS : Customer is First Points next

Transaction Variant For Me21.

Can i create a transaction variant for transaction me21.
if yes, please tell me the procedure.
please help.
its urgent.

hi
good
i think you can do it , because Transaction Variants to make fields Mandatory, Hidden or Display. Also applicable to screens and tabstrips.
You can hide unwanted screens and fields in any of the standard SAP programs without changing any of the standard programs. Additional features such as making the variant as default on the standard SAP transaction code is only available as of 4.6x.
In 4.6c, you can default your transaction variant as the standard variant. (SHD0 - Edit -> Activate/Deactivate as standard variant)
thanks
mrutyun^

Transaction Variants and menu function

Hi,
When using transaction variants for cutomization (for screen view layout) am encountering the following:
The customized view is diplayed when the t-code with the transaction variant is entered. However, when using the customization and then we try to go into a different mode through the menu option the screen view will go back to the standard view.
Example: for MM01 a transaction variant ZFG01 was created. When in ZFGO1 (enter the t-code ZFG01)and then you go to the menu-display the screen view is that of MM02 and not the customized view of ZFG02
Any advise on this please.
Thank you
Amalie

Steps :-
Transaction SHD0 - Create a variant for the required transaction bychanging the layout through hiding fields and screens.
Transaction SE93 - Create a variant transaction (e.g. for VA02 you canname it as ZA02). Next allocate the transaction variant to this varianttransaction.
Create and change the Zxxx area menu with the new transaction variant. In this way, the user does have to remembers any extra transaction codes.
In 4.6c, you can default your transaction variant as the standard variant. (SHD0 - Edit -> Activate/Deactivate asstandard variant)
An example for using transaction variant (restricting the field displayfor CO11N - Goods movement) :-
If you want to restrict changes to the fields in Goods movement forone group of users.
1. Create a transaction variant for CO11N
2. Create a new transction code for the transaction variant and assign an authorization object to it
3. Divide the users into this two transaction code. Those who can change the field using CO11N. For those that have limited
field change, give them the authorizationfor ZCO11 (this is a new transaction code you have to create).
<b>Reward if USEFUL :)</b>

Transaction variant misunderstood. I will reward points !!!!!

Hello Gurus, i am trying, for some time now, to create a transaction variant. The goal is to set a field read-only in the "ea13" transaction.
When is use "se93" to create a transaction variant i have to fill in the transaction variant name, but when i do that it says that the transaction variat does not exist, confusing because i want to create a new transaction variant.
When i use "shd0" and fill in the name of my new transaction variant and click create i don`t have any fields, everything is empty. Can anyone give me an exact example or something. I found on the forum a link to a step by step how to, but it didn`t work.
Im working on R/3 Release 4.6C.
Please help, i will reward lots of points !!!

Hi,
Starting Transaction Variants
A transaction can be started with a variant:
Using the Test function from the maintenance transaction
By a program that includes a call to function module RS_HDSYS_CALL_TC_VARIANT
Function module RS_HDSYS_GET_TC_VARIANT checks to see if a transaction variant is active and returns its name and (if possible) its current values (screen variants, inactive functions).
Using its own transaction code as a variant transaction.
When a transaction with variant is called using the Test function, for technical reasons it is started in call mode. Some transactions behave differently in call mode than when called directly.
A variant transaction is started either in call mode or LEAVE TO TRANSACTION, depending to how it is called.
If you call a transaction with variant from a program using the function module RS_HDSYS_CALL_TC_VARIANT, you can use the function module to determine which mode is called (call mode or LEAVE TO TRANSACTION).
Variant Transactions
A transaction with a variant can have its own transaction code, which you can then use to execute the transaction with the appropriate variant.
To create a variant transaction, proceed as follows:
Choose Goto ® Create vari. trans. from the initial transaction variant maintenance screen.
Enter a transaction name and corresponding short text. Transaction type Variant transaction is already set. The following screen already contains default values for the name of the calling transaction, the variant name, and the client-specific or cross-client variant checkbox.
Save your entries.
Example:
Variant ABC has been defined for transaction Z000. We now want to create the variant transaction ZVAR.
Name of the new transaction: ZVAR
Name of the calling transaction: Z000
Name of the variant: ABC
Transaction ZVAR starts transaction Z000 with variant ABC.
If the variant specified for a variant transaction does not exist (in the current client), then the calling transaction will be started without variant.
The Standard Transaction Variant
Standard transaction variants have a special purpose. You can use any transaction variant as a standard variant. Use the Activate and Deactivate functions to use a specific transaction variant as a standard variant or to deactivate it.
If a standard variant is active for a transaction, the system searches for the variant automatically whenever the transaction is started and adopts its values.
If a transaction with an active standard variant is started with another variant, the values of the standard variant are not imported.
If a transaction with an active standard variant is started in batch input mode, the values of the standard variant are not imported either.
Variant Transactions and Parameter Transactions
Variant transactions can be client-specific (this means that their corresponding variants can also be client-specific).
In a variant transaction, several screens can be given pre-assigned values or suppressed. In a parameter transaction this can only be done for the initial screen.
You can suppress as many screens as you like in variant transactions; in parameter transactions you can only suppress the initial screen. If a screen is suppressed in a variant transaction, it is never displayed. An initial screen that has been suppressed in a parameter transaction is only not displayed when the transaction is initially called.
You can use the function Change transaction type during transaction code maintenance to convert a parameter transaction to a variant transaction. The system creates a transaction variant and a screen variant for its initial screen containing the values of the parameter transaction. The system suggests the name CV_P_ for these variants. The default name may be changed. The variant is created for the called transaction. It can be changed in Transaction Variant Maintenance and Screen Variant Maintenance. The transaction variant can be created in the current client or as a cross-client variant.

Transaction variant for VA02 is not working for few fields

Hi All,
I have created a transaction variant for VA02. Made the necessary code changes for populating the variant name in MV45AFZZ. It is working fine for all the screens and all the fields except for second screen of VA02.
First screen - Enter sales order number.
Second screen - Overview screen.
In second screen, I have disabled all the screen fields. When I run the variant, all fields are disabled except sold-to party, ship-to party and create sold to party ICON. All these fields belongs to screen 4701.
In the transaction variant I can see that these fields screen attributes set to output only. I don't see anything different for these fields compared to other fields.
First I thought it is because of mandatory fields. But some other mandatory fields are disabled after my changes. Why is this happening only for these 3 fields (Only for screen 4701 I can say).
Surprisingly, if I do any action like enter/select other tab, these fields are getting disabled.
Your inputs on this are highly appriciated.
Thanks,
Vinod.
Edited by: Vinod Kumar Vemuru on Dec 31, 2009 10:01 AM

Thanks, happy to see the reply.
But I have given the correct names as suggested by you.
I have also created a Transaction ZVA02 as i dont want this variant to be applied on standard VA02.
It is working on first screen but not on subsequent screens. Am i missing something, some link or activation?
Transaction Code VA02                  Change Sales Order
Transaction Variant ZTRN_VA02                       testing
ZTRN_VA02_0102                                        SAPMV45A     102
ZTRN_VA02_4001                                        SAPMV45A     4001
ZTRN_VA02_4021                                        SAPMV45A     4021
ZTRN_VA02_4050                                        SAPMV45A     4050
ZTRN_VA02_4401                                        SAPMV45A     4401
ZTRN_VA02_4701                                        SAPMV45A     4701
ZTRN_VA02_4900                                        SAPMV45A     4900
when I run this the first screen is applied correctly but what happens next.

VA01 Transaction variant Field Modification

Hi All,
I need to deactivate ( make input = 0 ) certain fields in VA01 txn which has a transaction / screen variant. Everything thing works fine but the problem is, the other fields which was deactivated (make input = 0 ) using transaction variant appears in the screen ? Can you people tell how to solve this issue ? The user wants the screen as per the transaction variant. I am using the exit "FORM FORM USEREXIT_FIELD_MODIFICATION ?
Thanks.

The scenario is such that when the sales order is created against the invoice, some fields in VA02 still can be modified. but the user dont want that to be happened beyond the certain date. But it could be mofied with in the certain date. Now the problem is when i modify the screen as per the requirement, the fields which are hided using transaction variant appears in the screen. when i comment my code...
the transaction variant works properly ( i.e the fields got hided ) my code would be like.
Date logic....
IF SCREEN-NAme = VBAK-ZTERM.
input = 0.
modify screen.
endif.

Create transaction variant of mm01 - can't fix material type

Hi,
I am trying to create two transaction variants for MM01 called ZM0R and ZM0F for raw and finished materials respectively.
I have created them and all the fields I want as Required are working.
However, I want the material type to default in as raw for ZMOR and as finished goods for ZMOF. I have ticked "with content" and "required" but it is not working. Whatever material type was last used in MM01 still comes in.
I have also tried creating a copy of MM01 using Se93 to see if I can get it to work this way but when I test it, I get a message Sap Transaction control and can't seem to get past that.
Any ideas?
Thanks

Hi Jurgen,
worked a treat, thanks!. I have another related problem...my backflush field in MRP2 is not appearing. I have checked the field groups and it is there, group 74, for the material type and marked as Optional. Is there somewhere else this can be hidden?

Can anybody tell me how to use SHD0-tRANSACTION VARIANT

hI,
pL.tell me the procedure to use SHD0 for co01 and CO02 T-CODES

Dear Laxmikanth,
Transaction variant or Screen variant does not works out for T
code CO01 or CO02.
As far I know you can restrict only the plant and order type ,I
dont think you can restrict the user's to change or modify the
BOM Components.
Regards
Mangalraj.S

Transaction variant attached to all the transactions

Hello,
I have created a screen variant in transaction SHD0 and attached it to business transaction.
In the field 'Transaction code' at SHD0, I have entered the value CRMD_ORDER_PA,
After doing so, I have discovered that when I entered to create activity using transaction: CRMD_BUS2000126 all the transactions that exist in our system, gets the screen variant I have crate for a certain transaction, although they are attached to different variants.
However, if I enter the business transaction using transaction: CRMD_ORDER, everything work fine- every transaction gets the variant that belongs to it.
Thank you very much.
Ohad.

hi
you are getting this because of the nature of the t code you are using
CRM_ORDER_PA is basically used for designing the activity
,once you have assigned the variant to the transaction and you try open the transaction using this code then what it will do is design all the activities with the same parameters ,thats why you are having all the transactions with the same variant
but on the other hand crm_order is basic t code to create transaction,it works on the concept of one order framework in CRM,using this creating transaction wont place that much effect on the transaction coz it work independent of the transactions,it is used to create Lead ,activity or say opportunity,so it doesn take into account the variant info while creating transaction
try doing this thing using lead transaction you wont see such thing when you will use CRM_ORDER_PA coz hat works only with activity
guess i clear ur doubt
best regards
ashish

Transaction variant - can all fields be gryed out?

Similar Messages

Maybe you are looking for