Rollback a call transaction using CTU_PARAMS

Is there any combination of CTU_PARAMS and ROLLBACK that can be used to rollback a call txn. A BAPI is not available for me to use to perform the function I need.

Hi,
I dont think there would be any combination available for CTU_PARAMS and ROllback.
CTU_PARAMS is available only under the following FM`S :
BDC_RECORD_TRANSACTION
BDC_RUNNING
RS_HDBDC_CALL_TC_BATCH_INPUT
RS_HDBDC_CHANGE_TC_BATCH_INPUT
Rollback can be done using BAPI_TRANSACTION_ROLLBACK.
It would be good if you call the Roll back BAPI explicitly instead of doing rollback along with CTU_PARAMS. Make both of them as independent calls.
Best regards,
Prashant

Similar Messages

Message type in BDCMSGCOLL Structure in Call transaction using BDCDATA

Hi,
We are facing issue while capturing message in BDCMSGCOLL structure in Call transaction using bdcdata. The message which are like
Message 'Message Text' Type 'S' Display LIke 'E' .
This message is captured as Success on the Message structure instead of error & user are asking to update it as Error as it is looking like Error message to the end user.
Please provide resolution to the issue.
Regards,
Kapil

Hi Venkat,
I am not doing any upload, i am just doing a replay of the transaction ME21 & in that there are many error message which encounter while creating a PO but when i have check the logic , they are basically a success message which are display like Error so when i have called ME21 transaction using below statement
call transaction ME21 using BDCDATA
into messages bdcmsgcoll.
I am getting the message as success only since the message are of type success but as they are display like E , so user want that in msgcoll structure these messages must be shown as Error.
Regards,
Kapil.

TRANSACTION을 ROLLBACK SEGMENT에 할당하는 방법(SET TRANSACTION USE)

제품 : ORACLE SERVER
작성날짜 : 2003-04-04
TRANSACTION을 ROLLBACK SEGMENT에 할당하는 방법
==============================================
(SET TRANSACTION USE ROLLBACK SEGMENT)
Purpose
Batch job 등을 사용할 때 특별히 크게 만든 rollback segment를 사용하도록
할 수가 있다. transaction에 특정한 rbs를 지정하는 방법을 알아보자.
Explanation
Oracle은 다음과 같은 규칙에 의해 각 Transaction이 사용하는 Rollback
segment를 결정한다.
1. Active Transaction의 수가 가장 작은 Rollback Segment에 할당한다.
2. 만약 1의 조건에 만족하는 Rollback segment가 하나 이상이면, 가장
마지막에 할당된 rbs 다음의 rbs를 할당한다. 이것은 undo 기능을 더
오래 지속시키도록 해 준다.
그러나, Application이 큰 rollback segment가 필요하다면 위와 같이
자동적인 rollback segment의 할당이 아닌 Manual하게 특정 rollback
segment를 할당 가능하다.
다음의 방법을 사용한다.
1) 큰 rollback segment를 만든다. 큰 rollback segment 를 만들기
위해서는 rbs tablespace에 영역이 충분히 커야 하므로 필요할 경우
tablespace를 확장하는 작업을 한다.
<tablespace 확장>
$ sqlplus system/manager
sql> alter tablespace rbs add datafile '?/rbs1SID.dbf' size 100m;
<rollback segment 생성>
sql> create rollback segment big_rbs storage(initial 10m next 10m)
tablespace rbs;
sql> alter rollback segment big_rbs online;
2) Transaction 를 assign 한다.
<sqlplus>
SQL> set transaction use rollback segment big_rbs;
<pro*c>
exec sql commit work;
exec sql set transaction use rollback segment big_rbs;
<forms>
dbms_transaction.use_rollback_segment('big_rbs');
이와 같이 지정하면 이후에 commit 또는 rollback이 일어날 때까지
한 transaction에만 해당된다.

Call transaction using bdc tab and also skip first screen??

Hi,
Please help.
I want to call transaction PA30 fill it with values which are determined only at runtime and then skip first screen.
The screen doesn't have parameter fields so i cannot use 'set parameter id'.
I also cannot create a transaction with parameters as I only have these at runtime.
Anyone done anything like this???

hi,
you might be populateing the itab bdc_tab with the corresponding values fronm the recording.
while doing the recording go until to the screen wher u want to finsih.
and populate the bdc_tab wit the ok code,screen number and the value.
this will do.
for eg see the code below.
METHOD analyze_log.
DATA : wrk_extid TYPE balhdr-extnumber.
DATA : wrk_date(10) TYPE c.
DATA : it_rspar TYPE TABLE OF rsparams .
DATA : wa_rspar TYPE rsparams.
DATA: it_bdcdata TYPE STANDARD TABLE OF bdcdata,
      wa_bdcdata TYPE bdcdata.
DATA: params TYPE ctu_params.
CONSTANTS : object TYPE balhdr-object VALUE 'ZKIV_LOG'.
IF wa_kopf-vertr_nr IS NOT INITIAL.
    CONCATENATE wa_kopf-vertr_nr '/' wa_kopf-nachtr_nr INTO wrk_extid.
    wrk_date = '01.09.2006'.
    SET PARAMETER ID 'BALOBJ' FIELD object .
    SET PARAMETER ID 'BALEXT' FIELD wrk_extid.
    wa_rspar-selname = 'ALDATE'.
    wa_rspar-sign = 'I'.
    wa_rspar-kind = 'P'.
    wa_rspar-option = 'EQ'.
    wa_rspar-low = wrk_date.
    APPEND wa_rspar TO it_rspar.
ELSE.
    CLEAR wrk_extid.
    SET PARAMETER ID 'BALEXT' FIELD wrk_extid.
ENDIF.
Update BDC tab
--Call SLG1 using BDC--&
params-dismode = 'E'. "Show errors only
CLEAR wa_bdcdata.
wa_bdcdata-program = 'SAPLSLG3'.
wa_bdcdata-dynpro   = '0100'.
wa_bdcdata-dynbegin = 'X'.
APPEND wa_bdcdata TO it_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-fnam = 'BDC_CURSOR'.
wa_bdcdata-fval = 'BALHDR-ALDATE'.
APPEND wa_bdcdata TO it_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-fnam = 'BALHDR-ALDATE'.
wa_bdcdata-fval = wrk_date.
APPEND wa_bdcdata TO it_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-fnam = 'BDC_OKCODE'.
wa_bdcdata-fval = '=SELE'.
APPEND wa_bdcdata TO it_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-program = 'SAPLSLG3'.
wa_bdcdata-dynpro   = '0100'.
wa_bdcdata-dynbegin = 'X'.
APPEND wa_bdcdata TO it_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-fnam = 'BDC_OKCODE'.
wa_bdcdata-fval = '=&F03'.
APPEND wa_bdcdata TO it_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-fnam = 'BDC_SUBSCR'.
wa_bdcdata-fval = 'SAPLSBAL_DISPLAY                        0101SUBSCREEN'.
APPEND wa_bdcdata TO it_bdcdata.
CALL TRANSACTION 'SLG1' USING it_bdcdata OPTIONS FROM params.
--End of BDC--&
ENDMETHOD.
here wat i m doing is that i dont want the subscreen 101 to be displayed..
Message was edited by:
        Sandeep S

SAP MII 14.0 - Calling Transactions using SOAP Runner fails

Hello All,
We are calling transactions in SAP MII 14.0 from external apps using SOAP Runner and we are passing the login info in the payload. But we are getting the following error.
We are passing the following in the payload.
<xmii:LoginName>Username</xmii:LoginName>
<xmii:LoginPassword>Password</xmii:LoginPassword>
We are getting 401 unauthorized as the user name and password is not propagated to the MII.
It works if we supply the info explicitly when we invoke the URL.
Thanks,
Kiran

Hello Rajesh,
I don't think that will be allowed. We usually pass the credentials in the payload and it has always worked for us in MII 12.1. But in MII 14.0 it does not seem to be working.
Thanks,
Kiran

URL format to call transaction using WinGUI

Hello,
We would like to display SAP transactions in the portal, however they are from the SAP APO sytem and require the the WinGUI setting as they contain graphics that the ITS cannot interpret. WinGUI does not use the ITS. An iView or External Service can be created to display the required transactions using the SAPApplication.Transaction but as the screens are made up of several windows we would like them to open up full screen. The standard iView can open in a new screen but the window opens in a different place depending on the user's internet settings. To solve this a java iView could be written to dictate the starting point and size of the window but I am having trouble with the URL of the transaction. Using WebGUI the following format can be used to call a transaction:
<System.Access.ITS.Protocol>://<System.Access.ITS.HostName><System.Access.ITS.Path>/webgui/!?transaction=<SAP_Dynp_AutoStart%><SAP_TCode>%20<SAP_Dynp_Params%>&client=<System.Client>&language=<Request.Language>&accessibility=<User.Accessibility>
Does anyone know the format of the URL to call a transaction using wingui (it doesn't work to substitute wingui for webgui in the format above)?
Thanks for your help,
Katie

HI,
You need to write the codition like below,
If Message = 'Successful'
If Button = 'SUBMIT'
Call Transaction 'ZABC'.
Endif.
Endif.
Regards
Sudheer

CALL transaction using itab aswell as skip the first screen

Hi All,
I am doin BDC for some Ztransaction and i am that transaction using CALL TRANSACTION... but i want to skip the first screen of the Ztransaction as well as pass the Itab .. mode .. update and message table.... how can i do it...
CALL TRANSACTION Z... USING iTAB UPDATE DATE MODE A message bdcmsgcoll AND skip THE FIST SCREEN.. how to acheive it....

PERFORM BDC_DYNPRO      TABLES BDCDATA
                       USING 'SAPLBPT1' '0100'.
*PERFORM BDC_FIELD       TABLES BDCDATA
                       USING 'BDC_CURSOR'
                             'BCONTD-BPCONTACT'.
*PERFORM BDC_FIELD       TABLES BDCDATA
                       USING 'BDC_OKCODE'
                             '/00'.
*PERFORM BDC_FIELD       TABLES BDCDATA
                       USING 'BCONTD-BPCONTACT'
                              V_CONTRACT.
the above code /recording call the first screen 100 which i dont want...
below code / recording is for screen 200 which i want to appear directly when i call the transaction....
skipping the first screen 100..
PERFORM BDC_DYNPRO      TABLES BDCDATA
                        USING 'SAPLBPT1' '0200'.
PERFORM BDC_FIELD       TABLES BDCDATA
                        USING 'BDC_OKCODE'
                              '=SAVE'
PERFORM BDC_FIELD       TABLES BDCDATA
                        USING 'BCONTD-PARTNER'
                               V_GPART.
PERFORM BDC_FIELD       TABLES BDCDATA
                        USING 'BCONTD-ADDINFO'
                               V_ZONE.         "ZONE(S,N,E,E,NE)
PERFORM BDC_FIELD       TABLES BDCDATA
                        USING 'BDC_CURSOR'
                              'EENO_DYNP-ZEILE(01)'.
PERFORM BDC_FIELD       TABLES BDCDATA
                         USING 'EENO_DYNP-ZEILE(01)'
                               V_LOG.                 "MESSAGE
CALL TRANSACTION 'BCT1'    USING BDCDATA
                           MODE MODE UPDATE UPDATE
                           MESSAGES INTO IT_BDCMSGCOLL.

CALL transaction using generic user.

Hi experts,
I have a CALL TRANSACTION, which code is: 'ME54' USING BDC_TAB MODE 'E' UPDATE 'S'.
I have previosly defines the BDC_TAB. Is is a backgroud process executes with an event. The sy-uname there is the same as the user that has lauched the event. I want this to be executed with a generic user, example GENUSER instead of the one that really launches the event.
¿Is this possible?
Thank-you very much,
Artur.

Hi,
The only way I can think of at the moment is to extract your CALL TRANSACTION into a separate self-contained program (which it may already be looking at your post). Then use FM JOB_OPEN, JOB_SUBMIT (changing the parameter AUTHCKNAM to you generic user) and JOB_CLOSE (with STRTIMMED = abap_true).
This obviously gives rise to other problems such as knowing when the job finished etc but this depends on your overall design and if this is important or not.
Looking at your overall process this does not sound like a problem. Simply change the background job step for the event - have it call a new program to perform the JOB* FM steps instead which calls your original program that was registered against the event.
Thanks,
Pete

CAll transaction using Adobe

Hi
My Requirement is call to a transcation ex: VA01 using ADOBE thru webservice(Fn module input-> sales order no).
The transaction shld be called when user hit the SUBMIT button Adobe interactive form.
I can create the button in webdynpro and called the screen using the below method. Its working.
lo_window_manager->create_external_window(
exporting
url = url
receiving
window = lo_window ).
But the requirement is only to call transaction when the user hit the submit button in the Adobe form.
It would be helpful if get an idea regarding the same.
Thanks
Arun

Hi
Thanks for all your replies.
Sanoosh
I tried to code in the function module. when submit the button in Adobe Interactive form is calling the Fn module (webservice).
But I couldnt decalre the wd_comp_controller->wd_get_api( ).
wd_comp_controller is an interface. how to decalre this interface in the function module source code.
Here is the complete code I tried in Function Module.
DATA: url TYPE string,
        host type string,
        port type string.
*Call below method to get host and port
cl_http_server=>if_http_server~get_location(
     IMPORTING host = host
            port = port ).
*create URL
CONCATENATE 'http'
'://' host ':' port
'/sap/bc/gui/sap/its/webgui/?sap-client=&~transaction=' 'VA03'
   INTO url.
*get the window manager as we are opening t code in external window.
DATA lo_window_manager TYPE REF TO if_wd_window_manager.
DATA lo_api_component TYPE REF TO if_wd_component.
DATA lo_window TYPE REF TO if_wd_window.
lo_api_component = wd_comp_controller->wd_get_api( ).
lo_window_manager = lo_api_component->get_window_manager( ).
call the url which we created above
lo_window_manager->create_external_window(
exporting
url = url
receiving
window = lo_window ).
lo_window->open( ).
Thanks & Regards

Problem in call transaction using FD33 t code

Hi all i'm developing a report in that in that i'm calling a tcode FD33.
I want to skip the initial screen.For that i need to pass Customer , Credit control area and status from my program to that tcode.
But my problem is that how to pass the value to check box.
i.m writing the following code
   "Set parameter ID for transaction screen field
        SET PARAMETER ID 'KUN' FIELD W_ALV-KUNNR.
        SET PARAMETER ID 'KKB' FIELD W_ALV-VKORG.
       "Execute transaction FD33, and skip initial data entry screen
        CALL TRANSACTION 'FD33' AND SKIP FIRST SCREEN.
So how to set the value of the STATUS check box.
thanks in advanced.
Dheeraj

use:
data: dynnr(40) value '/210'.    "or number of another dynpro you wish to go
SET PARAMETER ID 'CDY' FIELD dynnr.
A.

RE-FX:call transaction using bdc-tab:No bdc_okcode for swapping table-entry

Hello,
I am trying to call transaction RERAOP (module RE-FX) to make an accounting transaction. There is 1 debit posting and 1 credit posting in a grid. Selecting the debit posting, a details scrren is shown, consisting of 2 registers.
On the first register you have to fill different fields. At this point it isn't possible to select the second register. The second (credit) posting is diplayed when you hit the enter key. After the fields in the details screen of this (credit) postings have been filled, it is possible to swap back to the first (debit) posting with a double-click on the first entry of the postings-table.
Finally I come to the point ...
If I record these steps (batch-input recorder) and generate an report of this code there is no bdc_okcode for the above mentioned swap back to the debit posting. While executing this report I get a lot of error message because the swap back to the debit posting doesn't work (--> because of the missing bdc_okcode) and therefore the batch input tries to fill fields which are not on the active screen (because they are on the 2. register which is not displayed).
Hope that there is someone out there who:
1. Understands my miserable english and
2. has an advice for me.
Thanks in advance!!!
Stephan
Edited by: Stephan Scholze on Apr 22, 2008 1:34 PM
Edited by: Stephan Scholze on Apr 22, 2008 2:24 PM
Edited by: Stephan Scholze on Apr 22, 2008 3:19 PM

Not sure how much I can help as we don't run RE-FX (RERAOP - what's the program name btw?) at any sites I work at, but a couple of general BDC things you might try (based on problems I've had with BDCs to other Tcodes)...
When you are in that transaction normally do a right click to see what function codes are defined as there might be one there that allows you to switch between these debit & credit data entry places (how are they rendered, btw - are they ALV grids or what? If they are table controls then you should be able to position the cursor on row 1 and trigger an F2 double-click)... also look at the PF-STATUS carefully in case (once again) there is a function code that lets you swap from DR to CR & vice versa... and even browse the source code in the user-command for the screen might give a clue as to how to achieve this. Of course it may not be possible if the data entry is control based i.e. the input areas are provided in the SAPGui not the application server (such as the text editor & ALV grids)... in which case you start hunting for BAPIs and function modules and the like, or end up having to pass data into the transaction via something like an "export" and catch it inside a user exit or enhancement via an "import"... all rather messy, but quite possible.
Jonathan

When we use call transaction and session method?

cud anyone tell me the exact difference between session and call transaction ? when we have to use ?

hi,
BATCH INPUT METHOD
Asynchronous processing
Transfer data for multiple transactions.
Synchronous database update.
A batch input process log is generated for each session.
Session cannot be generated in parallel.
CALL TRANSACTION METHOD:
Using CALL TRANSACTION USING statement
Faster processing of data
Synchronous processing
Transfer data for a single transaction.
No batch input processing log is generated.

How to get a message from call transaction in RFC call

Hello :
I would like to ask one favor i make a 2 call transaction in a RFC funtion when i make the first CALL TRANSACTION using te next statement.
    CALL TRANSACTION 'F-43'
      USING bdcdata MESSAGES INTO messtab2 OPTIONS FROM l_fromopt.
I recive the number of the document in the field sy-msgv1 from the message table messtab2 , then i make the second CALL TRANSACTION and i am waiting to get the other number of the document from the table messtab3 using the next statatement.
     CALL TRANSACTION 'FIBLFFP'
        USING bdcdata MESSAGES INTO messtab3 OPTIONS FROM l_fromopt. but now the table messtab3 don't send the number of document , and i need to get the number of this document for making a REFERENCE.
thanks a lot for you help

FORM bdc_transaction USING tcode TYPE tcode.
DATA: l_mstring(480).
DATA: l_subrc TYPE sy-subrc,
        lwa_t100 TYPE t100.
DATA : gv_ctumode TYPE ctu_params-dismode VALUE 'A'.
call transaction using
BREAK-POINT.
REFRESH gt_messtab.
CLEAR gwa_messtab.
gv_ctumode = gc_ctumode.
CALL TRANSACTION tcode USING gi_bdcdata                "#EC CI_CALLTA
                   MODE   gv_ctumode
                   UPDATE gc_cupdate
                   MESSAGES INTO gt_messtab.
l_subrc = sy-subrc.
IF sy-subrc <> 0.
    WRITE: / 'CALL_TRANSACTION',
             tcode,
             'returncode:',
             l_subrc,
             'RECORD:',
             sy-index.
    LOOP AT gt_messtab INTO gwa_messtab.
      CLEAR lwa_t100.
      SELECT SINGLE * FROM t100 INTO lwa_t100 WHERE sprsl = gwa_messtab-msgspra
                                AND            arbgb = gwa_messtab-msgid
                                AND            msgnr = gwa_messtab-msgnr.
      IF sy-subrc = 0.
        l_mstring = lwa_t100-text.
        IF l_mstring CS '&1'.
          REPLACE '&1' WITH gwa_messtab-msgv1 INTO l_mstring.
          REPLACE '&2' WITH gwa_messtab-msgv2 INTO l_mstring.
          REPLACE '&3' WITH gwa_messtab-msgv3 INTO l_mstring.
          REPLACE '&4' WITH gwa_messtab-msgv4 INTO l_mstring.
        ELSE.
          REPLACE '&' WITH gwa_messtab-msgv1 INTO l_mstring.
          REPLACE '&' WITH gwa_messtab-msgv2 INTO l_mstring.
          REPLACE '&' WITH gwa_messtab-msgv3 INTO l_mstring.
          REPLACE '&' WITH gwa_messtab-msgv4 INTO l_mstring.
        ENDIF.
        CALL FUNCTION 'FORMAT_MESSAGE'
          EXPORTING
            id        = gwa_messtab-msgid
            lang      = sy-langu
            no        = gwa_messtab-msgnr
            v1        = gwa_messtab-msgv1
            v2        = gwa_messtab-msgv2
            v3        = gwa_messtab-msgv3
            v4        = gwa_messtab-msgv4
          IMPORTING
            msg       = l_mstring
          EXCEPTIONS
            not_found = 1
            OTHERS    = 2.
        IF sy-subrc <> 0.
          MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                  WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        ENDIF.
        CONDENSE l_mstring.
        IF NOT l_mstring IS INITIAL.
          WRITE: / gwa_messtab-msgtyp, l_mstring(250).
          MESSAGE l_mstring TYPE 'I'.
        ENDIF.
      ELSE.
        WRITE: / gwa_messtab.
      ENDIF.
    ENDLOOP.
    SKIP.
ENDIF.

Commit work statement creating problem in CALL TRANSACTION

Hi Friends,
we are facing a problem where we need to call a standard program from a Zprogram.
we have tried the following ways.
1. Using SUBMIT statement , we are sending the parameters to the standard program, but when the standard program gives a
    dump our program cannot process further records. we are calling the submit statment in a loop. As because the standard
    program is giving dump our program is not able to process the next record in the loop and this should not be the case.
    To avoid this we have used the second method.
2. we used a CALL transaction, we have created a Tcode for the standard program and called this transaction in the calling
    program. We are passing the parameters for the standard program via BDC table. this works fine even when the standard
    program gives a dump but when ever the control   comes across a Commit work statement the the control comes back to our
   calling program with out executing the rest of the   statments after the commit.
now our concern is even though there is an commit work statement , statements after the commit work should also get executed in call transaction. Is thee any way?
Regards,
Sravan

Hi All,
I got the solution
DATA: ctu_parameters TYPE ctu_params.
ctu_parameters-dismode = 'E'.
ctu_parameters-updmode = 'A'.
ctu_parameters-racommit = 'X'. "No abortion by COMMIT WORK
CALL TRANSACTION USING itab_bdcdata OPTIONS FROM ctu_parameters.
the above code will work even if there is an commit work . This might help some others.

Combination of call transaction & session methods

hi,
how to combine call transaction & session methods in a single transaction.
give me the exact steps to proceed with the above.

Hi Saritha,
Your question is not clear to me but I am assuming your queestion like this
"Providing choice for user for using either call transaction & Session method for uploading data"
When you generate the BDC (Batch Data Communication options define the processing mode for a batch input session) program with SHDB, you can remove a lot of unwanted fields by copying this customize abap include program. It allows you to execute the BDC program immediately without filling up those SAP generate fields. To run background, just run it as a background job.
Execute BDC immediately by replacing the include BDCRECX1
Written by : SAP Basis, ABAP Programming and Other IMG Stuff
                 http://www.sap-img.com
***INCLUDE ZBDCRECX1.
When you generate the program using SHDB, you can replace it
with this if you want to execute it immediately without having
to process it using SM35.
During testing you can used the original include.
For example,
include zbdcrecx1.   "After test
include bdcrecx.     "Before test
Declare your internal table as RECORD
for programs doing a data transfer by creating a batch-input session
and
for programs doing a data transfer by CALL TRANSACTION USING
*SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS SESSION RADIOBUTTON GROUP CTU. "create session
SELECTION-SCREEN COMMENT 3(20) TEXT-S07 FOR FIELD SESSION.
selection-screen position 45.
PARAMETERS CTU RADIOBUTTON GROUP CTU DEFAULT 'X'. "call transaction
SELECTION-SCREEN COMMENT 48(20) TEXT-S08 FOR FIELD CTU.
*SELECTION-SCREEN END OF LINE.
PARAMETERS: SESSION NO-DISPLAY,
            CTU     NO-DISPLAY DEFAULT 'X'.
*SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(20) TEXT-S01 FOR FIELD GROUP.
selection-screen position 25.
PARAMETERS GROUP(12).                      "group name of session
SELECTION-SCREEN COMMENT 48(20) TEXT-S05 FOR FIELD CTUMODE.
selection-screen position 70.
PARAMETERS CTUMODE LIKE CTU_PARAMS-DISMODE DEFAULT 'N'.
                                     "A: show all dynpros
                                     "E: show dynpro on error only
                                     "N: do not display dynpro
*SELECTION-SCREEN END OF LINE.
PARAMETERS: GROUP(12) NO-DISPLAY,
            CTUMODE   NO-DISPLAY DEFAULT 'N'.
*SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(20) TEXT-S02 FOR FIELD USER.
selection-screen position 25.
PARAMETERS: USER(12) DEFAULT SY-UNAME.    "user for session in batch
SELECTION-SCREEN COMMENT 48(20) TEXT-S06 FOR FIELD CUPDATE.
selection-screen position 70.
PARAMETERS CUPDATE LIKE CTU_PARAMS-UPDMODE DEFAULT 'L'.
                                     "S: synchronously
                                     "A: asynchronously
                                     "L: local
*SELECTION-SCREEN END OF LINE.
PARAMETERS: USER(12) NO-DISPLAY DEFAULT SY-UNAME,
            CUPDATE LIKE CTU_PARAMS-UPDMODE DEFAULT 'L' NO-DISPLAY.
*SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(20) TEXT-S03 FOR FIELD KEEP.
selection-screen position 25.
PARAMETERS: KEEP AS CHECKBOX.       "' ' = delete session if finished
                                     "'X' = keep   session if finished
SELECTION-SCREEN COMMENT 48(20) TEXT-S09 FOR FIELD E_GROUP.
selection-screen position 70.
parameters E_GROUP(12).             "group name of error-session
*SELECTION-SCREEN END OF LINE.
PARAMETERS: KEEP        NO-DISPLAY,
            E_GROUP(12) NO-DISPLAY.
*SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(20) TEXT-S04 FOR FIELD HOLDDATE.
selection-screen position 25.
PARAMETERS: HOLDDATE LIKE SY-DATUM.
SELECTION-SCREEN COMMENT 51(17) TEXT-S02 FOR FIELD E_USER.
selection-screen position 70.
PARAMETERS: E_USER(12) DEFAULT SY-UNAME.    "user for error-session
*SELECTION-SCREEN END OF LINE.
PARAMETERS: HOLDDATE LIKE SY-DATUM NO-DISPLAY,
           E_USER(12) DEFAULT SY-UNAME NO-DISPLAY.
*SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 51(17) TEXT-S03 FOR FIELD E_KEEP.
selection-screen position 70.
PARAMETERS: E_KEEP AS CHECKBOX.     "' ' = delete session if finished
                                     "'X' = keep   session if finished
*SELECTION-SCREEN END OF LINE.
PARAMETERS: E_KEEP NO-DISPLAY.
*SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 51(17) TEXT-S04 FOR FIELD E_HDATE.
selection-screen position 70.
PARAMETERS: E_HDATE LIKE SY-DATUM.
*SELECTION-SCREEN END OF LINE.
*SELECTION-SCREEN SKIP.
PARAMETERS: E_HDATE LIKE SY-DATUM NO-DISPLAY.
*SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 1(33) TEXT-S10 FOR FIELD NODATA.
PARAMETERS: NODATA DEFAULT '/' LOWER CASE.          "nodata
*SELECTION-SCREEN END OF LINE.
PARAMETERS: NODATA DEFAULT '/' LOWER CASE NO-DISPLAY.
*SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 1(33) FOR FIELD SMALLLOG.
PARAMETERS: SMALLLOG as checkbox. "' ' = log all transactions
                                    "'X' = no transaction logging
*SELECTION-SCREEN END OF LINE.
PARAMETERS: SMALLLOG NO-DISPLAY.
data definition
      Batchinputdata of single transaction
DATA:   BDCDATA LIKE BDCDATA    OCCURS 0 WITH HEADER LINE.
      messages of call transaction
DATA:   MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
      error session opened (' ' or 'X')
DATA:   E_GROUP_OPENED.
      message texts
TABLES: T100.
at selection screen                                                *
AT SELECTION-SCREEN.
group and user must be filled for create session
IF SESSION = 'X' AND
     GROUP = SPACE OR USER = SPACE.
    MESSAGE E613(MS).
ENDIF.
open dataset                                                       *
FORM OPEN_DATASET USING P_DATASET.
OPEN DATASET P_DATASET IN TEXT MODE.
IF SY-SUBRC <> 0.
    WRITE: / TEXT-E00, SY-SUBRC.
    STOP.
ENDIF.
ENDFORM.
close dataset                                                      *
FORM CLOSE_DATASET USING P_DATASET.
CLOSE DATASET P_DATASET.
ENDFORM.
create batchinput session                                          *
(not for call transaction using...)                                *
FORM OPEN_GROUP.
IF SESSION = 'X'.
    SKIP.
    WRITE: /(20) 'Create group'(I01), GROUP.
    SKIP.
open batchinput group
    CALL FUNCTION 'BDC_OPEN_GROUP'
         EXPORTING CLIENT   = SY-MANDT
                    GROUP    = GROUP
                    USER     = USER
                    KEEP     = KEEP
                    HOLDDATE = HOLDDATE.
    WRITE: /(30) 'BDC_OPEN_GROUP'(I02),
            (12) 'returncode:'(I05),
                 SY-SUBRC.
ENDIF.
ENDFORM.
end batchinput session                                             *
(call transaction using...: error session)                         *
FORM CLOSE_GROUP.
IF SESSION = 'X'.
close batchinput group
    CALL FUNCTION 'BDC_CLOSE_GROUP'.
    WRITE: /(30) 'BDC_CLOSE_GROUP'(I04),
            (12) 'returncode:'(I05),
                 SY-SUBRC.
ELSE.
    IF E_GROUP_OPENED = 'X'.
      CALL FUNCTION 'BDC_CLOSE_GROUP'.
      WRITE: /.
      WRITE: /(30) 'Fehlermappe wurde erzeugt'(I06).
    ENDIF.
ENDIF.
ENDFORM.
       Start new transaction according to parameters                 *
FORM BDC_TRANSACTION USING TCODE.
DATA: L_MSTRING(480).
DATA: L_SUBRC LIKE SY-SUBRC.
batch input session
IF SESSION = 'X'.
    CALL FUNCTION 'BDC_INSERT'
         EXPORTING TCODE     = TCODE
         TABLES    DYNPROTAB = BDCDATA.
    IF SMALLLOG <> 'X'.
      WRITE: / 'BDC_INSERT'(I03),
               TCODE,
               'returncode:'(I05),
               SY-SUBRC,
               'RECORD:',
               SY-INDEX.
    ENDIF.
call transaction using
ELSE.
    REFRESH MESSTAB.
    CALL TRANSACTION TCODE USING BDCDATA
                     MODE   CTUMODE
                     UPDATE CUPDATE
                     MESSAGES INTO MESSTAB.
    L_SUBRC = SY-SUBRC.
    IF SMALLLOG <> 'X'.
     WRITE: / 'CALL_TRANSACTION',
              TCODE,
              'returncode:'(I05),
              L_SUBRC,
              'RECORD:',
              SY-INDEX.
      IF SY-SUBRC = 0.
         FORMAT COLOR OFF.
         WRITE:/ 'Successfully Process ', MESSTAB, RECORD.
      ELSE.
         FORMAT COLOR COL_NEGATIVE.
         WRITE:/ 'Failed Process ', MESSTAB, RECORD.
      ENDIF.
      LOOP AT MESSTAB.
        SELECT SINGLE * FROM T100 WHERE SPRSL = MESSTAB-MSGSPRA
                                  AND   ARBGB = MESSTAB-MSGID
                                  AND   MSGNR = MESSTAB-MSGNR.
        IF SY-SUBRC = 0.
          L_MSTRING = T100-TEXT.
          IF L_MSTRING CS '&1'.
            REPLACE '&1' WITH MESSTAB-MSGV1 INTO L_MSTRING.
            REPLACE '&2' WITH MESSTAB-MSGV2 INTO L_MSTRING.
            REPLACE '&3' WITH MESSTAB-MSGV3 INTO L_MSTRING.
            REPLACE '&4' WITH MESSTAB-MSGV4 INTO L_MSTRING.
          ELSE.
            REPLACE '&' WITH MESSTAB-MSGV1 INTO L_MSTRING.
            REPLACE '&' WITH MESSTAB-MSGV2 INTO L_MSTRING.
            REPLACE '&' WITH MESSTAB-MSGV3 INTO L_MSTRING.
            REPLACE '&' WITH MESSTAB-MSGV4 INTO L_MSTRING.
          ENDIF.
          CONDENSE L_MSTRING.
          WRITE: / MESSTAB-MSGTYP, L_MSTRING(250).
        ELSE.
          WRITE: / MESSTAB.
        ENDIF.
      ENDLOOP.
      SKIP.
    ENDIF.
Erzeugen fehlermappe ************************************************
    IF L_SUBRC <> 0 AND E_GROUP <> SPACE.
      IF E_GROUP_OPENED = ' '.
        CALL FUNCTION 'BDC_OPEN_GROUP'
             EXPORTING CLIENT   = SY-MANDT
                        GROUP    = E_GROUP
                        USER     = E_USER
                        KEEP     = E_KEEP
                        HOLDDATE = E_HDATE.
         E_GROUP_OPENED = 'X'.
      ENDIF.
      CALL FUNCTION 'BDC_INSERT'
           EXPORTING TCODE     = TCODE
           TABLES    DYNPROTAB = BDCDATA.
    ENDIF.
ENDIF.
REFRESH BDCDATA.
ENDFORM.
       Start new screen                                              *
FORM BDC_DYNPRO USING PROGRAM DYNPRO.
CLEAR BDCDATA.
BDCDATA-PROGRAM = PROGRAM.
BDCDATA-DYNPRO   = DYNPRO.
BDCDATA-DYNBEGIN = 'X'.
APPEND BDCDATA.
ENDFORM.
       Insert field                                                  *
FORM BDC_FIELD USING FNAM FVAL.
IF FVAL <> NODATA.
    CLEAR BDCDATA.
    BDCDATA-FNAM = FNAM.
    BDCDATA-FVAL = FVAL.
    APPEND BDCDATA.
ENDIF.
ENDFORM.

Rollback a call transaction using CTU_PARAMS

Similar Messages

Maybe you are looking for