SAP-crack the client's lock through debugging to modify system data

Original article: SAP-break through the client's lock through debugging to modify system data

Generally, the SAP production machine is set as unchangeable. However, sometimes some custom tables or data tables that do not affect the logic of the system can be directly modified on the Production Machine Client. OK. Let's try it in debug mode and modify the material group.

1. modify the tcode: omsf of the material group in normal mode. The message "customer XXXX cannot be modified" is displayed, and you can only select to enter in display mode. This is because the client is locked and cannot be modified.

2. Return to the main interface, set the debugging status, and then enter tcode: omsf.CodeAfter debugging, such as adding a breakpoint of the message command

Press F8 to run the prompt message that cannot be modified, and return to the debugging code. The Code stops at line 302 message i430 ..., this line is the code of the pop-up information. check whether there is an if judgment in the 297 line. Intuition tells me that this is the key point. The vim_client_state variable may be used to check whether the status can be modified.
.

Set this line to a breakpoint.ProgramAgain, execute the program with omsf, F8 runs until 297 rows, and change vim_client_state to 0.
(This is different from vim_loked). After F8, the prompt box is skipped and the modification interface is successfully displayed.

At this time, we can modify it as we like. When we save it, the breakpoint will also be in line 297, and vim_client_state will be modified as well, so we can save it successfully.