SHDB - The Transaction Recorder
Question 14: What is the transaction recorder?
The transaction recorder - BDC recorder - is for recording a series of transactions and their screens. TCODE (transaction code) is SHDB for the transaction recorder. Run SHDB for recording any transaction in SAP R/3 System.
As you know that BDC programming is a kind of tracing all screens and enter data into appropriate place then running the transaction. To do BDC programming either batch input sessions or CALL TRANSACTION you have to know order of all screens, screen names, field names and even you don’t have to miss any screen elements. As you can guess that it is hard to that manually. So SAP provides us an easy method: The Transaction Recorder (BDC Recorder).
SHDB allows a user to record keystrokes and other keyboard actions so that they may be incorporated into a BDC session.
You can use the recording to create:
- Data transfer programs that use batch input or CALL TRANSACTION
- Batch input sessions
- Test data
- Function modules.
The recording can be executed several times. The screens are run in exactly the same way as they were running during recording. You can edit recordings that you have already made using an editor.
- To display the batch input initial screen, choose SAP - Services - Batch Input - Edit
- Chose Recording. The system now displays the initial screen of the batch input recorder.
- Make a recording of the relevant transactions.
- Generate one or several of the objects named above.
There are some special features that you may have to notice:
- F1, F4 and self-programmed F1 - F4 help (PROCESS ON HELP-REQUEST, PROCESS ON VALUE-REQUEST) are not recorded. The same applies to all commands in the System and Help menus.
- Error or warning dialogs are not recorded. This means that only the OK code field and field contents that lead to successful further processing in the current screen.
- COMMIT WORK in a transaction flow indicates the successful end of the transaction as regards batch input. The recording also ends successfully.
- LEAVE TO TRANSACTION in the course of transaction indicates that it is not suitable for batch input. The recording is terminated.
- In Screen Painter screens, movements in the scrollbar are not recorded. Use function keys F21 - F24 for positioning.
- Customized screens may present a problem. If it is possible, only use the non-customized screens to record sessions.
References:
- SAP Library, ABAP Programming (BC-ABA)
Tags: recorder, SHDB, transaction
January 24th, 2007 at 9:19 am
Hi…
I not come to comment,
but I want ask something about SHDB,
When i recording some process at SBWP,
can u give some solution about how to click tab inbox,
because when i try it with SHDB, it’s doing nothing
best regards
Ferry Tjhin
January 24th, 2007 at 11:21 am
Ferry.
The goal of using SHDB is to create BDC programs and sessions. But BDC doesn’t support Enjoy transactions. SBWP is a Enjoy transaction too.
Enjoy transactions use Enjoy SAP Controls like ALV Grid, ALV Tree. If you run BDC in background these Controls would not be able to communicate front-end since they need some files in front-end (client - PC), so BDC fails.
Therefore what can be done? There are two possibilities:
1- ) There might be a alternative, usually older version, transaction. You can use it. For example ME22N is a Enjoy transaction, but ME22 is the older one, does the same thing. So ME22 can be used. As far as I know the older version of SBWP is SO01, but when we run it it goes to same program.
2- ) If it is available, a BAPI can be used. Whatever you want to do, you can search BAPIs and use it instead of BDC technique. I think unfortunately there isn’t any BAPI related to SAP Business Workplace.
I don’t know what you are tryin to do, but the last thing you would write own program by realizing all tables, finding some function modules, ABAP objects, etc..
March 15th, 2007 at 1:22 am
I have made a recording to do reservations using MB21. My problem is how to create test data that allows multiple lines (different material items) for one job to be processed under one reservation document. Any thoughts?
March 19th, 2007 at 8:11 am
Patrick,
If understood your question correctly, you can use flat structure (file), or you can convert a spreadsheet (Excel) file to CSV (comma delimited) file. I mean movement type, G/L Account No, Cost Center, etc. would repeat for each Line Item (Material, Quantity, etc.). You can design and develop your program which processes flat structure file. It seems easy way to do that!
March 22nd, 2007 at 12:43 am
can i know the format of the flat file used for uploading data to the material master-mm01 by using BDC-RECORDING METHOD
March 26th, 2007 at 7:34 am
Kumar,
Since you would write your own BDC program, you don’t need a specific file format. You can use any file, you just neeed to process the file in BDC program.
But if you mean Standard Data Transafer program, you can use transaction SXDB with Data Transfer Object 20 (Material Master) for getting test data file sctructure. It is obvious Standard Data Transfer programs require specific file structure.
May 7th, 2007 at 6:27 am
Is it necessary for test data to be only in flat files? Can we use xml’s as data files for database updation through bdc sessions?
August 5th, 2009 at 12:04 pm
where i need to attach the test data file.
October 23rd, 2009 at 4:44 am
I would like to know under what circumstances does a BDC fail…Could anyone please let me know…
Thanks…
October 23rd, 2009 at 2:18 pm
@Tim
Could you please give more specific info about BDC fail? Have you seen an error in a BDC process?