Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

copy transaction problem

Former Member
0 Likes
777

dear my friends

i want to ask about is it possible to copy standard sap transaction completely like ( Fbl5n or va01 or iw51 ) some thing like this sap transactions to a customized z one and modify it instead of use (user exit ,enhancements , BADI and also BTE ) and

other tool . because i want to left the standard program away from my modification and is it will be completely copied or it will raise problem .

thank you

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
729

Hi.

It is not generally a good idea to clone standard SAP transactions. The reasons for this are that as you apply patches or upgrade your system, any program changes made by SAP to the object(s) you cloned never get the changes applied to them and this could be a major thing if new functionality has been added. Also, a transaction is not a single program. It probably calls other programs, function modules, etc and if you have to clone these then you really run the risk of problems with missing patches and updates. Finally, main programs for SAP Transactions apply to many transactions and quite often there is coding that checks what T-Code was used and different functionallity is then executed. Yor 'Z' t-code would not be in those checks so things may not work properly.

In some cases, you may have to clone but be sure to exhaust all other alternatives (exits, enhancements etc) before you do.

Hope this answers your question.

Brent

3 REPLIES 3
Read only

ThomasZloch
Active Contributor
0 Likes
729

This is done very often, however I strongly suggest not to do it. You will lose connection to future SAP fixes to the standard transaction, and every upgrade might produce major headaches, even more if only parts of the code are being copied to Z-includes. There is problems as well with technical customizing tables that expect the original transaction name.

Don't do it, use any means of SAP provided enhancement techniques as much as possible. I even favor a small modification over copying an entire transaction.

Thomas

Read only

Former Member
0 Likes
730

Hi.

It is not generally a good idea to clone standard SAP transactions. The reasons for this are that as you apply patches or upgrade your system, any program changes made by SAP to the object(s) you cloned never get the changes applied to them and this could be a major thing if new functionality has been added. Also, a transaction is not a single program. It probably calls other programs, function modules, etc and if you have to clone these then you really run the risk of problems with missing patches and updates. Finally, main programs for SAP Transactions apply to many transactions and quite often there is coding that checks what T-Code was used and different functionallity is then executed. Yor 'Z' t-code would not be in those checks so things may not work properly.

In some cases, you may have to clone but be sure to exhaust all other alternatives (exits, enhancements etc) before you do.

Hope this answers your question.

Brent

Read only

0 Likes
729

Seems we typed at the same time to say the same things, I hope the message sinks in

Thomas