Professional Documents
Culture Documents
Note:
To use SHDB and LSMW transactions it is better the SAP screen to be in format Default size.
In this situation the recording will have exactly the same number of lines like in screen.
Page: 1 of 9
File: 130467193.doc
To start a new recording, enter a recording name (up to 10 letters) in the field labeled "Recording," and the Transaction Code MM01. Click either the "Start Recording" button or the green check mark at the bottom of the screen.
Page: 2 of 9
File: 130467193.doc
Page: 3 of 9
File: 130467193.doc
Hiatus
Screen
Hiatus
Screen
Page: 4 of 9
File: 130467193.doc
Hiatus
Screen
Detail Screen
Page: 5 of 9
File: 130467193.doc
Hiatus
Screen
Screen
Page: 6 of 9
File: 130467193.doc
Record a session with You will be asked for a session name and the the name of the transaction to transaction SHDB record.The you can enter the data into the transaction as usual.
Activating the recording session First screen of MB1C Detail Screen End the recording
Detail Screen There is something to say on detail screen processing, ie. screens with table Processing: There are controls.If you enter many lines or try to extend a list, where you do not know mostly menu functions before, how many lines the list contains, you will not know, where to place the that allow exact item cursor. Therefore most transactions provide a menu option, that positions the list positioning in a calculable manner. If you choose a new item, most transaction will either pop up a detail screen or will position the list, so that the next free line is always line 2. From the recorded The SHDB transaction creates an ABAP from the recording. When you run this session, you can ABAP, it will generate a BTCI group file, with exactly the same data as in the generate an ABAP recording. Replace the include with modified FORM routines to allow CALL TRANSACTION It will use a set of predefined FORM routines, which are stored in an include file. If we modified this FORM routines a little bit, we can make the ABAP run with a CALL TRANSACTION, which is much more suitable for our development and testing purposes. If you replace the standard include BDCRECXX with this one zz_bdcrecxx.txt , you can replay the recording online. Try it out, to check if the recording worked the way you expected it. It is often a good idea to deactivate the
Page: 7 of 9 File: 130467193.doc
Page: 8 of 9
File: 130467193.doc
Steps: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19.
Execute transaction SHDB in QAS(where data is) Make recording and save, return to SHDB front screen Press 'Overview', then select the created recording(double click) Go into change mode(press Change-Display icon) Now go into editing mode(press editing icon or F6) Select Export from the Recording menu Enter file name and path to store temporary file Press the Transfer button Breathe... Execute transaction SHDB in DEV client Make new recording and save it, but dont worry about what it does as data will be over written (just create one for SE38 or something). Return to SHDB front screen Press 'Overview', then select the created recording(double click) Go into change mode(press Change-Display icon) Now go into editing mode(press editing icon or F6) Select Import from the Recording menu Enter file name and path of temporary file created before Press the Transfer button Hit save and you can now use this recording to generate your program as usual (SHDB->Overview-> Program).
Page: 9 of 9
File: 130467193.doc