Application Development 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: 

change standard SAP program or copy and change ?

Former Member
0 Kudos
1,034

Hi,

I am asked to change MIR6(SAPMM08N) program. My question is, should I change it taking access key or copy and perform changes.

What you suggest and why ?

Cheers

Sudhaker

1 ACCEPTED SOLUTION

GauthamV
Active Contributor
0 Kudos
136

hi,

better u go with copy and change instead of waiting for access key which will take time.

10 REPLIES 10

GauthamV
Active Contributor
0 Kudos
137

hi,

better u go with copy and change instead of waiting for access key which will take time.

Former Member
0 Kudos
136

Hi Sudhaker,

There is no need to change the standard program with access key. You should copy the program and perform the changes.

Moreover changes thru access key is not entertained most of the time.

Hope this helps you.

Regards,

Chandra Sekhar

Edited by: Chandrasekhar Gandla on Jun 25, 2008 8:21 AM

Former Member
0 Kudos
136

It is better to copy the std. code and create a custom prog. If u change the std. prog. with access key without the help of modification assistance(Se95) then all the changes can be lost if u upgrade the system. If u take help of modification assistance then after upgrade it shows u the diff, and may be u have to do all the changes semi-automatically.

Regards,

Joy.

former_member181995
Active Contributor
0 Kudos
136

Sudhakar,

for safer side better if you copy and do your changes into zprogram.because might be if you temper SAP program than it would affect some where else too.

Amit.

Former Member
0 Kudos
136

If you want to make small changes you can go for access key.You can also check whether exits are available to suit you job.If you want to make big changes to suit your requirement then copy that program.The below program will help you to find the user exit for the given transaction.

report zuserexit no standard page heading.
tables : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
tables : tstct.
data : jtab like tadir occurs 0 with header line.
data : field1(30).
data : v_devclass like tadir-devclass.
parameters : p_tcode like tstc-tcode obligatory.

select single * from tstc where tcode eq p_tcode.
if sy-subrc eq 0.
select single * from tadir where pgmid = 'R3TR'
and object = 'PROG'
and obj_name = tstc-pgmna.
move : tadir-devclass to v_devclass.
if sy-subrc ne 0.
select single * from trdir where name = tstc-pgmna.
if trdir-subc eq 'F'.
select single * from tfdir where pname = tstc-pgmna.
select single * from enlfdir where funcname =
tfdir-funcname.
select single * from tadir where pgmid = 'R3TR'
and object = 'FUGR'
and obj_name eq enlfdir-area.

move : tadir-devclass to v_devclass.
endif.
endif.
select * from tadir into table jtab
where pgmid = 'R3TR'
and object = 'SMOD'
and devclass = v_devclass.
select single * from tstct where sprsl eq sy-langu and
tcode eq p_tcode.
format color col_positive intensified off.
write:/(19) 'Transaction Code - ',
20(20) p_tcode,
45(50) tstct-ttext.
skip.
if not jtab[] is initial.
write:/(95) sy-uline.
format color col_heading intensified on.
write:/1 sy-vline,
2 'Exit Name',
21 sy-vline ,
22 'Description',
95 sy-vline.
write:/(95) sy-uline.
loop at jtab.
select single * from modsapt
where sprsl = sy-langu and
name = jtab-obj_name.
format color col_normal intensified off.
write:/1 sy-vline,
2 jtab-obj_name hotspot on,
21 sy-vline ,
22 modsapt-modtext,
95 sy-vline.
endloop.
write:/(95) sy-uline.
describe table jtab.
skip.
format color col_total intensified on.
write:/ 'No of Exits:' , sy-tfill.
else.
format color col_negative intensified on.
write:/(95) 'No User Exit exists'.
endif.
else.
format color col_negative intensified on.
write:/(95) 'Transaction Code Does Not Exist'.
endif.

at line-selection.
get cursor field field1.
check field1(4) eq 'JTAB'.
set parameter id 'MON' field sy-lisel+1(10).
call transaction 'SMOD' and skip first screen.

former_member598013
Active Contributor
0 Kudos
136

Hi Sudhakar,

Its better to copy the standard Program and do the necessary changes.. This is a good practice.

Dont go for any access key to change the standard transaction. It may hamper your system

&**************Reward Point if helpful*************&

Former Member
0 Kudos
136

copy and change the new program then configure this to the transaction u r working on

Former Member
0 Kudos
136

hi...

its better to go with copying and making changes to copy..

because... the changes u r doing are custom changes and the changes u do should not alter the functionality of any other object that is linked to the standard program

regards

padma

Former Member
0 Kudos
136

My question is answered

Former Member
0 Kudos
136

Hi friend.

As per my knowledge.

We can't directly modify the program SAPMM08N, which is a standard SAP program.

As per my lessons, We practise the use of very important component of SAP called 'Enhancements'.

I suggest 2 ways of approaching the issue.

1. Use of General Techniques like:

  • SMOD

  • CMOD

transactions.

I haven't gone in depth, but surely you need to explore.

2. Advanced technique.

  • By use of BADI's that is Bussiness Addins.

Standard SAP transactions SE18 & SE19.

Check out and hope things work fine.

Good luck.

Harsh