Diffrent EXITs (enhancements) for same t code (MD02) ????

[Former Member]

Hi,

when im trying to get enhancements for t. code MD02 via. string

search "CALL CUSTOMER" in std. program of MD02 it is giving diffrent

enhancements. however when im looking for same via. package(dev. class)

MD(std. program of MD02 is in this package only) it is giving me

entirely diffrent enhancements. Can anybody explain why??

rgds

sudhanshu

[RaymondGiuseppi]

The transaction MD02 is in development class MD03, when the program SAPMM61X (module pool) belongs to development class MD.

That may be a cause.

Regards

[Former Member]

Hi,

Std. pgm of MD02 (SAPMM61X) exist in MD dev. class. however the EXIT within this lying in MD03 dev. class. Please have a look...that's how i went through this:

1) In pgm SAPMM61X searched for string CALL CUSTOMER which is taking me to FM EXIT_SAPMM61X_001.

2) I put this FM in table MODSAP (field MEMBER) to get corresponding enhancement and it is giving me M61X001.

3) Using this enhancement browse table TADIR (OBJECT: SMOD & OBJ_NAME: M61X001) which is saying that it is in MD03 dev. class.

rgds

sudhanshu

[RaymondGiuseppi]

I did as follow

SE93 MD02 (DevClass MD03 ) 
=> double-click on program SAPMM61X 
=> goto attributes DevClass MD
=> look for CUSTOMER-FUNCTION 
=> gouble-click on exit number 
=> (we are in SE37) attributes tab 
=> DevClass MD03

The usual rule is "look at SMOD for the DevClass of the transaction main program", but here it is DevClass of the transaction.

Regards

[Former Member]

Hi,

Thanks for reply. I understand that program and t code lying in diffrent dev. class. my question is: does it make any diffrence for the existing object because MD02 is nuthin but the t code assocaited with a module pool pgm. Which enhancement will be useful for certain requirement...the one associated with dev. class MD or the one which is thr with MD03.

rgds

sudhanshu

[RaymondGiuseppi]

In this case, i would say the DevClass MD03 is the one to check fist, especially function group XM61 "User Exits PP-MRP Materials Planning".

NB 1 - There are also at least 3 BADI in this class

NB 2 - The dev class can help finding BADI and customer exit, but many transactions or programs call function module belonging to another development class, those can have also exit or BADI, so other sources of information should be looked for (OSS notes, online documentation, debugging the transaction, SE30, sdn, etc.)

Regards

[Former Member]

Hi,

When you got the list of Exits ..you can check that Exit and Click on display button. Then you will get the function module

starts with exit_*.

These procedure for when you get the exits by suing the package name.

regards,

Ajay

[vinod_vemuru2]

Hi,

In addition to the above check below exits also.

EXIT_SAPLMDR2_001

EXIT_SAPLMDR2_002

EXIT_SAPLMDR2_003

EXIT_SAPLMDZU_001

EXIT_SAPLMDZU_002

EXIT_SAPLMDZU_003

Thanks,

Vinod.