An "smart" concept learned by SAP"

I learned how to read internal tables today. In the SQL Server 2005 Manager, we can see the spfli flight schedule, which contains a large string of data. The first column contains the information about the client. Because I log on to client 001, but the table does not have 001 data, I cannot see any records in SE16.

So I made a little bit of effort to directly update the 000 data in the SQL Server 2005 Manager, and changed the 000 data to 001, in this way, data can be found in SE16 in SAP, but it cannot be found in SAP when writing ABAP queries. The syntax is absolutely no problem, but no matter what method is used, the data cannot be displayed! I almost had to crash. I found no relevant information on QQ and Baidu.

Later, I thought about how to dirty the data. Then, the system was updated and used ddic to log on to the 000 client system, create a user, and grant the highest permissions to sap_all. Log on to se38, and queryProgramThe data is displayed ~

I think the tables in each client in the database are associated with each other, and changes in the database without permission will certainly break some rules. However, I was surprised to find that the programs in different clients seem to be public ~