READ PROGRAM SAPMSYST

[Former Member]

i am trying to read the source code of a program SAPMSYST.

But it says that the source code is protected.

is there exists some way that i can read the source code.

but making some changes in debugging.

say:

comparing in debugging mode a zprogram and this program,

which statement raise the error msg that source code is protected

and i can get into the source code of this prog.

moreover, in SE80, i can see the sceen. gui_status ,

but there are no pbo or pai modules.

Please suggest how to get into it,.

[ThomasZloch]

This code is protected by SAP on some deeper level that we ABAP developers have no access to.

That's alright with me, because it probably contains logic that is highly relevant to system security and stability.

Hands off!

Thomas

[Former Member]

i understand what u say,

but still i want to get into the program.

there has to be some way out.

In childhood we have been taught, nothing is impossible.

moreover, this security check  is still coded in ABAp,

so an abap developer can get into it with pretty sound knowledge.

[ThomasZloch]

I bet this check is not on ABAP level, rather inside the SAP kernel (coded in C, I believe).

I had this "nothing is (technically) impossible" attitude as well, many years ago. However, many other factors are relevant and must be weighed, and not everything that can be done should be done, in my opinion.

Don't forget, this is an official SAP site, I would not continue to ask for hacks like these here.

Thomas

[Former Member]

thomas,

i am not asking to guide me how to hack sap system,

what i am wondering  i just placing the break-point somewhere in the coded and wanted to see how this code actually works.

please don't get me wrong.

Thomas Zloch wrote:
I bet this check is not on ABAP level, rather inside the SAP kernel (coded in C, I believe).

may be this has been coded in C, but there has be some difference, when we try to display Z Program and This SAPMSYST Program.

if we in debugging alter these changes , then may the Kernal level code will not get fired, and hopefully i will be able to see the source code.

[FredericGirod]

This kind of program is too critical for SAP to let people see the code, modify the code ...

I read the only solution is to make a Transport order and, at when SAP import, it uncompress the data, at this moment you could see the code ..

regards

Fred

[Former Member]

 I read the only solution is to make a Transport order and, at when SAP import, it uncompress the data, at this moment you could see the code ..

thanks fredric, u are the first person, who actually suggested something to work some way around.

i m glad .

please shed some light on what u have said:

how the transport order is created ,

and how it uncompresses data.

[FredericGirod]

You go in SE01, create a transport order, enter manually the key  R3TR PROG SAPMSYST, save, release the OT.

and open your debug in the STMS when you ask SAP to make an import ... 

I never do it, so I can't give you more input.

just a detail, you could crash your SAP system if you made a mistake into this program

[Former Member]

 and open your debug in the STMS when you ask SAP to make an import ...  

That means i have to open debug in our prod system, and in STMS_IMPORT Transaction.

am i right.

indeed this  will crash our sap system, if i make unnecessary changes, but rather i am thinking about only placing the break-point somewhere in the code and see how actually the program works.

can u please tell in which transaction exactly i should open debug mode and eventually how i can see the code.?

[Former Member]

Hi Abhishek,

To be very honest, i have a question to ask.

If something is restricted, there should be a very strong reason behind it and the error clearly says that its been blocked by SAP itself.

So trying to change anything in this might cause a disaster to your SAP System.

If this is for gaining the information, i read few blogs saying that this program is protected when writing the ABAP Code with some String and this can be removed only during the transportation as Frederic had mentioned above by removing the String during the transport.

Check Database View D010SINF SQLX field.

It is similar to how the codes are hidden. I would strongly recommend not to do this or even try this as it is protected by SAP and not any single Technical or Functional Person.

Still if you want to try, it would be better trying it in your IDES system at Home

Regards,

AyyamPerumal

[Former Member]

i am not going to change anything.

as i mentioned earlier i am gonna break-point somehwere in code, to see how it works in debug mode.

Check Database View D010SINF SQLX field.

means if i remove SQLX flag from this table REPOSRC.

then i'll be able to see the code.(i wonder).

 If this is for gaining the information, i read few blogs saying that this program is protected when writing the ABAP Code with some String and this can be removed only during the transportation as Frederic had mentioned above by removing the String during the transport.

please please can u tell how can i remove this flag during transportation.

are u taking about transporting this prog from dev to Quality Sys.

what diff does it will make??

And why is that so, i cant change the flag to initial from Debug in this table.???

[Former Member]

there are many programs which have D010SINF SQLX field as 'X'.

but their source code can still be viewed.

therefore i guess this is not the flag which is protecting source code.

Can u figure out some another way to do this??

And how can it ve viewed during transportation. please elaborate as i am not getting this.