We have already come across LSMW for mass changes to SAP data. Let us not assume that LSMW is the only tool that can be used to update data in SAP. SAP provides quite a few numbers of tools, each with its unique features, to allow mass update of data. In the current article, I talk about the Transaction Recorder tool which can be accessed through the transaction SHDB. Like LSMW, SHDB is also used to record certain user actions in the SAP GUI for a particular transaction.

These actions are used to create a recording that can be processed at a later time to upload data. Through SHDB it is also quite easy to generate an ABAP report from the recording and modify the generated code to read an input file with a list of records and upload the data through the program. In this article, I demonstrate the entire sequence of actions through a recording to reset the password of a user through SU01.

We start the transaction SHDB and click the button for a new recording. We give an appropriate name for the recording and input the transaction (SU01 in this case) which we are trying to record.

Capture.1461

On clicking the check button we are taken to the normal SU01 screen where we reset the password of any user id already created in the system (USER01)

Capture.1462

On saving the new password and clicking the back button, we are returned SHDB where we can check the steps in the recording.

Capture.1463

To test the recording we change the user id to "USER02" and save the recordings. Now we can process the recordings from SHDB.

Capture.1464

On successful processing for the recording, we get a screen showing that the password for the USER02 was indeed changed.

Capture.1464

Although its technically feasible to manually change the data in the recording and process them through SHDB, the generally accepted approach is to generate a program for the recording and update a list of records through ABAP code. SHDB's main screen has options to generate a program from recording.

Capture.1466

Capture.1467

Capture.1468

On clicking the check button, we are taken to the normal SU01 screen where we set the password of any user_id already created in the system(USER01)Capture.1469

On saving the new password and clicking the back button, we are returned SHDB where we can process the recording.

Capture.1470

To test the recording we change the user to "USER02" and save the recording. Now we can process the recording from SHDB

Capture.1471

On successful processing for the recording, we get a screen showing that the password for USER 02 was indeed changed.

Capture.1473

Although it's technically feasible to manually change the data in the recording and process them through SHDB, the generally accepted approach is to generate a program for the recording and update a list of records through ABAP code. SHDB's main screen has options to generate a program from recording.

Capture.1474

On selecting this option, SHDB prompts us for the attribute details for this skeleton code to read data records from a file into an internal table, and loop over each record to update data into SAP.

Capture.1475

As you can see from the above example, like LSMW, SHDB provides us with another alternate method of upload of data into an SAP system. Which method you finally chose depends a lot on whether you are more comfortable in writing code or creating at the LSMW script.

For In-depth knowledge on SAP Security click on: