Tx: SHD0

[Former Member]

Experts, can you give me some advice with tx: SHD0.

Do you think is there an inconveinence with the use of this transaction in to many transactions? during upgrades, are the changes made with this transaction deleted?

Best regards,

[Former Member · Accepted solution]

Hi,

I am not dead sure , but I dont think so there is any problems of using SHD0 ,

during upgrade the changes should not be deleted only changes deleted during upgrade which comes from modification.

regards

Deepak

[Former Member]

Hi RBK,

There is no problem with the T-code SHD0 but whenever we use this T-code,it records each and every step that you performed while it is running.

Even if you go back to a screen that is also recorded.

But the problem comes when SAP changes something like the addition of a new field or changing some field or even deleting some field on the screen for which you have done the recording,then since it is not captured while recording, your whole effort goes waste.

That is the reason that people refrain from using it.

I hope I have tried to answer your question to the best of my ability.

Do let me know in case you have any further queries.

Regards,

Puneet Jhari.

[Former Member]

Hi Puneet,

I think you are talking about SHDB, I dont think is there any recording in SHD0 (Transaction and Screen Varints)

regards

Deepak

[Former Member]

Hello,

I do not think there would any prblm....of course you need to take care of performance issue <if you are in implementation project, the outcome can be seen in performance testing>....Ideally I'd suggest SHD0 wud meet your requirement of having different authorizations for different persons....of course you could also achieve this by enhancing a FM<you need to find relevant FM for FPCJ screens>.....but again it needs significant efforts compared to what you do for SHD0.

Hope this clarifies

Rgds

Rajendra

[Former Member]

Hi Deepak, can you give me more information on tx: SHDB

[Former Member]

Hi

basically SHDB is used for recording. A batch input recording is a sequence of transactiothey have run through. A screen (program name, screthe modified fields (field name and value), the use (BDC_OKCODE) and the cursor position (BDC_CURSOR).

From an existing recording you can create a batch input session, a data

transfer program, test data or a function module to transfer the data:

Generating a batch input session directly

The data from the recording is transferred to the batch input

session. You can then process the batch input session for test

purposes using the usual mechanism in Transaction SM35.

Creating a data transfer program

When you create a data transfer program, you can decide whetherfixed data is to be transferred from the recording, or whether variable data should be read from a sequential file.

In the first case, the program must still be modified so that you

can transfer variable data.

Creating test data

To test the batch input program you have created (see above), you

can create a data record in a sequential file. This data record

contains all field contents from the recording that are relevant to

the data transfer.

Creating a function module for data transfer

The function module you have created contains as an interface all

fields from the recording that are relevant to the data transfer.

The function module imports the data transferred using the batch

input mechanism (CALL TRANSACTION USING or generate session). In

this way, you can import data from a different system (Remote

Function Call) and ensure that the data remains consistent.

In SDN , there is lots of useful link regarding SHDB

like:

thanks and regards

Deepak