topic Re: transaction analyse in Application Development and Automation Discussions

transaction analyse

ricardo_albertowalter — Thu, 05 Feb 2009 10:28:15 GMT

good morning

someone know a another M.function just like ( EXTENDED_PROGRAM_CHECK ) used in transaction slin to analyse the source code ?

Edited by: Ricardo Alberto Walter on Feb 5, 2009 11:29 AM

Re: transaction analyse

Former Member — Thu, 05 Feb 2009 10:30:05 GMT

Hi,

You can use,

Code Inspector,

SE30 Runtime analysis..

Thanks

Kalyan B

Re: transaction analyse

former_member404244 — Thu, 05 Feb 2009 10:30:05 GMT

HI,

Sorry didn't get ur question..

Regards,

Nagaraj

Re: transaction analyse

Former Member — Thu, 05 Feb 2009 10:34:26 GMT

Hi Richardo ,

You can analyse your prog. in many ways ,

1 . EPC

2 . Code Inspector

3 . Run time analysis

4 . SQL Trace

You can analyse the program using the above aspects .

Much Regards ,

Amuktha .

Re: transaction analyse

Former Member — Thu, 05 Feb 2009 10:35:29 GMT

hi,

hope this is what you were looking for to analyze the code,

SCI_INSPECT_LIST

SCI_ANALYZE_SQL_STMNTS

Re: transaction analyse

ricardo_albertowalter — Thu, 05 Feb 2009 10:49:28 GMT

hum, i dont know about EPC , what is ?

Re: transaction analyse

former_member404244 — Thu, 05 Feb 2009 10:53:12 GMT

Hi,

check the link

http://help.sap.com/saphelp_nw70/helpdata/en/d1/801afd454211d189710000e8322d00/content.htm

Regards,

Nagaraj

Re: transaction analyse

ricardo_albertowalter — Thu, 05 Feb 2009 11:16:29 GMT

Siddharth,

do you know some example to use this functions ?

SCI_INSPECT_LIST

SCI_ANALYZE_SQL_STMNTS

Re: transaction analyse

Former Member — Thu, 05 Feb 2009 11:33:05 GMT

I am exactly not aware of any example used by SAP for calling these function modules.....

just try to check the below code.

data :

t_itab type SCIT_OBJS with header line.

<Check the structure of SCIT_OBJS and fill in t_itab with the values of the objects required from the table TADIR > and then try to call this function module... > I Think this will give you better understanding and also help you to analyse the code......

CALL FUNCTION 'SCI_INSPECT_LIST'

EXPORTING

P_USER = SY-UNAME

p_objects = t_itab

P_NAME =
P_SHOW_RESULTS =
IMPORTING
P_RESULTS =
P_RESULTS_HD =
P_VARIANT =
EXCEPTIONS
NO_OBJECT = 1
OBJS_ALREADY_EXISTS = 2
NO_DEFAULT_CHECKVARIANT = 3
TOO_MANY_OBJECTS = 4
COULD_NOT_READ_VARIANT = 5
OTHERS = 6

IF sy-subrc <> 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

Hope I could clear your point

Regards,

Siddarth

Re: transaction analyse

Former Member — Thu, 05 Feb 2009 11:38:21 GMT

u can use this SAMT transaction to

here u can give many programs at a time to analyze...and u can find syntax errors also..

Thanks

Durga.K