Field details for SY02000 table 1

[Luvsql]

I've installed the SDK for release 7.5, but it does not list the System tables, especially the SY02000 table. I need to create a report for security setup, but cannot determine what each ResType is and what the ResID corresponds to.

Anyone have an SDK for the system tables?

 

[winthropdc]

There is a reason that the SY_Security_Normal_MSTR (SY02000) table is not included in the SDK.... Because it IS a security table.

However, given that you want a security report, I would suggest using Advanced Security to print the report for you.

David Musgrave
Senior Development Consultant
MBS Services - Asia Pacific

 

[jazgeek]

too bad system setup password is in plain text though

-----------
and they wonder why they call it Great Pains!

jaz

 

[Luvsql]

The advanced security reports are also over 90 pages long per class and use temp tables. I only want a simplied security report per user class. SDK's should incorporate ALL tables within an application. We should be able to import/integrate into or out of any table. The only table that contains secure information is the SY01400 table, but that password is encrypted, so what's the big deal with the SY02000 table. It doesn't contain the User, just what User Class can access.

 

[winthropdc]

Luvsql
The Advanced Security report will be a lot shorter if you ask it to Only Print Non-Default security. This way it will only show you the security records for resources which have changed from default. Select the class before printing to get the report on the class.

The class security is in the SY_Class_Normal_SETP (SY40300) and SY_Class_Main_SETP (SY40400) tables.

The deal with providing to much information on the security tables is that a user who can get access to SQL can modify the table to give themselves access to areas that they should not have access to. The structure of the Class and User security tables are almost identical so information on one will help understanding the other.


Jaz
I made sure that for v8.0 the SY_System_Password_MSTR table has access denied by default meaning that it cannot be accessed by the report writer without changing permissions first. Also it is not stored in plain text, if you look at the table in SQL it is encrypted, it is just that the Report Writer decrypts the field by default.


David Musgrave
Senior Development Consultant
MBS Services - Asia Pacific

Microsoft Business Solutions

http://www.microsoft.com/BusinessSolutions

Any views contained within are my personal views and
not necessarily Microsoft Business Solutions policy.