Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

executing batch input session (SM35) same way as CALL TRANS. RACOMMIT = 'X'

Sandra_Rossi
Active Contributor
0 Likes
2,494

Hello,

one colleague of mine has developped an LSMW which generates a batch input session (SM35). Unfortunately, it doesn't work because several COMMIT WORK occur (it stops at the COMMIT WORK). This is the same behavior as with CALL TRANSACTION.

But with this latter, it's possible to set the option RACOMMIT = 'X' which let the batch input continue even if COMMIT WORK occur.

Do you know a way to do it with SM35, or do you have a custom program or know a standard program which runs the session with CALL TRANSACTION statement?

Thank you all.

sandra

1 ACCEPTED SOLUTION
Read only

ThomasZloch
Active Contributor
0 Likes
1,341

program RSBDCCTU looks promising, you need the queue ID of the session (table APQI).

Can't try it here, so this is at your own risk

Thomas

3 REPLIES 3
Read only

ThomasZloch
Active Contributor
0 Likes
1,342

program RSBDCCTU looks promising, you need the queue ID of the session (table APQI).

Can't try it here, so this is at your own risk

Thomas

Read only

0 Likes
1,341

Thx Thomas, it works very well, preferred solution

What I found about RSBDCCTU (as there is no documentation, it may help people):

1) we have to enter the exact name and ID (just get it from SM35). If we let the ID blank, when we execute, a popup dialog is displayed to show all existing SHDB recordings which satisfy the name. SM35 sessions, unfortunately, are not selected.

2) It does a copy of SM35 data and runs it as a standalone CALL TRANSACTION. It means that it doesn't update the session status and log in SM35.

3) The log is displayed as an ALV

4) It may run in background, the ALV is displayed as a spool

Read only

Sandra_Rossi
Active Contributor
0 Likes
1,341

Workaround:

1) run BDC_RECORD_PLAY function module (usually run with SHDB) to run the batch input session (you have to get the ID and the session name from SM35). A screen is displayed to enter parameters, RACOMMIT especially. It runs in dialog, so there shouldn't be too much work to do, otherwise timeout may occur.

2) add break-point on start of BDC_OBJECT_SELECT function module, start SHDB transaction. On the break-point, change DATATYPE from %BDC to BDC (you may have to repeat each time the break-point is reached). Select your session and execute it. The same dialog (as above) is displayed to choose options.

I let the thread opened for 24 hours if you have other suggestions.

Thx