on 04-24-2007 10:09 PM
Hi Gurus
Please help me regarding a transaction variant
1. Can I transport a transaction variant and how
2. Can I transport a screen variant seperately within a transaction variant and how?
3. How can I trace a transaction variant
4. While copying a transaction variant for tcde FB50 why I am getting a message that it is client Independent?
If anybody has documentation related to transaction variant please send it to my email address jihsan@hotmail.com
Regards
KTK
Hi
Answers to your questions
1. Can I transport a transaction variant and how
Yes. For details check my document that i have sent to your email.
2. Can I transport a screen variant seperately within a transaction variant and how?
Screen variants are automatically attached to a transport upon saving a screen variant. For more details check my document.
3. How can I trace a transaction variant
check my documet sent.
4. While copying a transaction variant for tcde FB50 why I am getting a message that it is client Independent?
The transaction variant would have been set as cross client.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Musktk,
Could you please send me the documentation to sjosh_dv@yahoo.com
Thanks in Advance
MMvd
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Am also hving the same requirement for FV50. SO,
PLs. culd u send me the same document.
my ID is vtkapoor2000@yahoo.co.in
or I opend a new thread, pls. respond to it. Thread title is
VARIANT TRANSACTION FOR FV50???
thanq.
Message was edited by:
Srikhar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Mus Ktk,
In version 46C (I'm not sure about earlier versions), you can create a transport request in SE38 for the variants of a program. You could then use transaction SCC1 to copy those changes from one client to another.
To create transport:
1) Go to transaction SE38 and enter the program name.
2) Click the radio button next to the "Variants" subobject and click the "Change" button
3) On "ABAP: Variants" screen, select menu path "Utilities -> Transport request"
4) Enter the variant(s) you want to copy into the "Variant name" box.
5) Click the execute button and save the data to a new change request.
To copy to new client:
1) Log on to target client and goto transaction SCC1.
2) Enter the source client and change request number from above.
3) Click the execute button.
<b>**reward points if it helps**</b>
Regards
AK
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
When you want to transprt your changes to the QA or production clients you would need to use transaction STMS.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.