How to determine calling transaction?

Hi
Is there a way to determine the calling transaction? Simple example Transaction A calls Transaction B. From within transaction B, I'd like to know which Transaction called it.
Thanks, Adrian

Hi Adrian,
I think there is now way, because you can call transaction B from transaction A
either with CALL TRANSACTION
or with LEAVE TO TRANSACTION
In the 2nd version the calling transaction has finished!
Regards,
Klaus

Similar Messages

Using Txn SE97 -How to enable called transactions?

Hi Experts,
I suppose you all had worked in the transaction SE97. For any t-code, SE97 gives a list of called transaticons.
Now what i want to know is, how to enable the called transactions given here.
When i tried to change the "Check Indicator" value to YES, its not taking it.
Should i do something else to enable it?
For eg..
i need to call t-code FBL1 (Called t-code) from FBL1 (Calling t-code).
If you give FBL1N as your input in SE97, you will be able to see a list t-codes called by FBL1N with Check Indicators.
Now let me know how to enable this indicator as it is not happening to me.
Thanks & Regards,
Ashwin

If this is specific to a Business Views setting, then there is no SDK for that.
Sincerely,
Ted Ueda

How to use call transaction 'XD03' in alv.

Hi Experts ,
Below i m write code to call transaction xd03 but it not call the transacation.
<Garbled code removed>
Moderator Message: Please continue with your previous thread. Current thread locked.
Edited by: Suhas Saha on Nov 25, 2011 5:04 PM

Uhm
Here it's your calling:
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
 i_callback_program = gv_repid
 i_grid_title = gv_title
 is_layout = gv_layout
 it_fieldcat = gt_fielcat[]
*it_special_groups = gd_tabgroup
* IT_EVENTS = GT_XEVENTS
 i_save = 'X'
* is_variant = z_template
 TABLES
 t_outtab = gt_final
 EXCEPTIONS
 program_error = 1
 OTHERS = 2.
You don't indicate which is the routine for the user_command
You can do it in 2 ways:
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
 i_callback_program = gv_repid
 I_CALLBACK_USER_COMMAND = 'USER_COMMAND' "<.------- FORM the USER_COMMAND
 i_grid_title = gv_title
 is_layout = gv_layout
 it_fieldcat = gt_fielcat[]
*it_special_groups = gd_tabgroup
* IT_EVENTS = GT_XEVENTS
 i_save = 'X'
* is_variant = z_template
 TABLES
 t_outtab = gt_final
 EXCEPTIONS
 program_error = 1
 OTHERS = 2.
Or you indicate in the GT_XEVENTS table
LS_EVENT-NAMES = 'USER_COMMAND'.
LS_EVENT-FORM = 'USER_COMMAND'. "<.------- FORM the USER_COMMAND
APPEND LS_EVENT TO GT_XEVENTS.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
 i_callback_program = gv_repid
 i_grid_title = gv_title
 is_layout = gv_layout
 it_fieldcat = gt_fielcat[]
*it_special_groups = gd_tabgroup
 IT_EVENTS = GT_XEVENTS
 i_save = 'X'
* is_variant = z_template
 TABLES
 t_outtab = gt_final
 EXCEPTIONS
 program_error = 1
 OTHERS = 2.
Max

How to use Call Transaction in AVL ........ for va02

Hi Experts,
I am using CALL TRANSACTION in ALV for VA02, but I want to go on item number. The following form i have used and it is working but I want to go on perticular item number in va02. pl. guide me.
FORM user_command USING r_ucomm LIKE sy-ucomm
 rs_selfield TYPE slis_selfield.
CASE r_ucomm.
 WHEN '&IC1'.
 IF rs_selfield-fieldname = 'VBELN'.
 READ TABLE it_out INTO wa_itab INDEX rs_selfield-tabindex.
 SET PARAMETER ID : 'AUN' FIELD wa_itab-vbeln .
 'APO' FIELD wa_itab-posnr.
 CALL TRANSACTION 'VA02' AND SKIP FIRST SCREEN.
 ENDIF.
ENDCASE.
ENDFORM.
*=====================================
Yusuf

Hi,
use BDC for that....
check out the BDC part of coding for it.
REFRESH itab_bdcdata.
CLEAR itab_bdcdata.
*initial screen
PERFORM bdc_dynpro USING 'SAPMV45A'
 '0102'.
PERFORM bdc_field USING 'BDC_CURSOR'
 'VBAK-VBELN'.
PERFORM bdc_field USING 'BDC_OKCODE'
 '/00'.
PERFORM bdc_field USING 'VBAK-VBELN'
 g_t_atpma4-vbeln.
*item overview screen
PERFORM bdc_dynpro USING 'SAPMV45A'
 '4001'.
PERFORM bdc_field USING 'BDC_OKCODE'
 '=POPO'.
PERFORM bdc_field USING 'BDC_CURSOR'
 'RV45A-MABNR(04)'.
*popup screen (move item to top)
PERFORM bdc_dynpro USING 'SAPMV45A'
 '0251'.
PERFORM bdc_field USING 'BDC_CURSOR'
 'RV45A-POSNR'.
PERFORM bdc_field USING 'BDC_OKCODE'
 '=POSI'.
PERFORM bdc_field USING 'RV45A-POSNR'
 g_t_atpma4-posnr.
*item overview screen
PERFORM bdc_dynpro USING 'SAPMV45A'
 '4001'.
PERFORM bdc_field USING 'BDC_OKCODE'
 '/00'.
PERFORM bdc_field USING 'BDC_CURSOR'
 'VBAP-POSNR(01)'.
PERFORM bdc_field USING 'RV45A-VBAP_SELKZ(01)'
 'X'.
*Call transaction VA02
CALL TRANSACTION 'VA02' USING itab_bdcdata
 MODE 'E'
 UPDATE 'A'
 MESSAGES INTO itab_bdcmsg.
Patil

How to use call transaction 'XD03' in abap.

Hi Experts,
I am use call transaction xd03 in programme but when i click on any customer number the transaction xd03 is called and it show only one customer details. i.e 1 st in row . other customer details not show. so please write code to solved my problems

Hi
It's not clear where you set the USER_COMMAND routine and where you set the OK_CODE for doubleclick.
I suppose you set the routine in the importing parameter I_CALLBACK_USER_COMMAND (?) becasue you aren't use the parameter for the event, but for OK_CODE?
Remember the OK_CODE should be upper case:
FORM USER_COMMAND USING R_UCOMM LIKE SY-UCOMM
RS_SELFIELD TYPE SLIS_SELFIELD.
CASE R_UCOMM.
"WHEN 'kunnr'. <--------------- UPPER CASE
WHEN 'KUNNR'.
See my sample:
TYPE-POOLS SLIS.
DATA: BEGIN OF GT_FINAL OCCURS 0,
 KUNNR LIKE KNA1-KUNNR,
 NAME1 LIKE KNA1-NAME1,
 END OF GT_FINAL.
* ALV
DATA: GT_FIELDCAT TYPE SLIS_T_FIELDCAT_ALV,
 GT_LAYOUT TYPE SLIS_LAYOUT_ALV,
 GT_REPID LIKE SY-REPID.
START-OF-SELECTION.
SELECT KUNNR NAME1 INTO TABLE GT_FINAL
 UP TO 20 ROWS
 FROM KNA1.
GT_REPID = SY-REPID.
CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
 EXPORTING
 I_PROGRAM_NAME = GT_REPID
 I_INTERNAL_TABNAME = 'GT_FINAL'
 I_INCLNAME = GT_REPID
 CHANGING
 CT_FIELDCAT = GT_FIELDCAT[].
GT_LAYOUT-F2CODE = 'KUNNR'.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
 EXPORTING
 I_CALLBACK_PROGRAM = GT_REPID
 I_CALLBACK_USER_COMMAND = 'USER_COMMAND'
 IS_LAYOUT = GT_LAYOUT
 IT_FIELDCAT = GT_FIELDCAT
 TABLES
 T_OUTTAB = GT_FINAL.
FORM USER_COMMAND USING R_UCOMM LIKE SY-UCOMM
 RS_SELFIELD TYPE SLIS_SELFIELD.
DATA: GWA_FINAL LIKE GT_FINAL.
CASE R_UCOMM.
 WHEN 'KUNNR'.
 READ TABLE GT_FINAL INTO GWA_FINAL INDEX RS_SELFIELD-TABINDEX.
 IF SY-SUBRC = 0.
 SET PARAMETER ID 'KUN' FIELD GWA_FINAL-KUNNR.
 CALL TRANSACTION 'XD03' AND SKIP FIRST SCREEN.
 ENDIF.
ENDCASE.
ENDFORM.TYPE-POOLS SLIS.
DATA: BEGIN OF GT_FINAL OCCURS 0,
 KUNNR LIKE KNA1-KUNNR,
 NAME1 LIKE KNA1-NAME1,
 END OF GT_FINAL.
* ALV
DATA: GT_FIELDCAT TYPE SLIS_T_FIELDCAT_ALV,
 GT_LAYOUT TYPE SLIS_LAYOUT_ALV,
 GT_REPID LIKE SY-REPID.
DATA: FL_INPUT_OFF.
START-OF-SELECTION.
SELECT KUNNR NAME1 INTO TABLE GT_FINAL
 UP TO 20 ROWS
 FROM KNA1.
GT_REPID = SY-REPID.
CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
 EXPORTING
 I_PROGRAM_NAME = GT_REPID
 I_INTERNAL_TABNAME = 'GT_FINAL'
 I_INCLNAME = GT_REPID
 CHANGING
 CT_FIELDCAT = GT_FIELDCAT[].
GT_LAYOUT-F2CODE = 'KUNNR'.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
 EXPORTING
 I_CALLBACK_PROGRAM = GT_REPID
 I_CALLBACK_USER_COMMAND = 'USER_COMMAND'
 IS_LAYOUT = GT_LAYOUT
 IT_FIELDCAT = GT_FIELDCAT
 TABLES
 T_OUTTAB = GT_FINAL.
FORM USER_COMMAND USING R_UCOMM LIKE SY-UCOMM
 RS_SELFIELD TYPE SLIS_SELFIELD.
DATA: GWA_FINAL LIKE GT_FINAL.
CASE R_UCOMM.
 WHEN 'KUNNR'.
 READ TABLE GT_FINAL INTO GWA_FINAL INDEX RS_SELFIELD-TABINDEX.
 IF SY-SUBRC = 0.
 SET PARAMETER ID 'KUN' FIELD GWA_FINAL-KUNNR.
 CALL TRANSACTION 'XD03' AND SKIP FIRST SCREEN.
 ENDIF.
ENDCASE.
ENDFORM. TYPE-POOLS SLIS.
DATA: BEGIN OF GT_FINAL OCCURS 0,
 KUNNR LIKE KNA1-KUNNR,
 NAME1 LIKE KNA1-NAME1,
 END OF GT_FINAL.
* ALV
DATA: GT_FIELDCAT TYPE SLIS_T_FIELDCAT_ALV,
 GT_LAYOUT TYPE SLIS_LAYOUT_ALV,
 GT_REPID LIKE SY-REPID.
DATA: FL_INPUT_OFF.
START-OF-SELECTION.
SELECT KUNNR NAME1 INTO TABLE GT_FINAL
 UP TO 20 ROWS
 FROM KNA1.
GT_REPID = SY-REPID.
CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
 EXPORTING
 I_PROGRAM_NAME = GT_REPID
 I_INTERNAL_TABNAME = 'GT_FINAL'
 I_INCLNAME = GT_REPID
 CHANGING
 CT_FIELDCAT = GT_FIELDCAT[].
GT_LAYOUT-F2CODE = 'KUNNR'.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
 EXPORTING
 I_CALLBACK_PROGRAM = GT_REPID
 I_CALLBACK_USER_COMMAND = 'USER_COMMAND'
 IS_LAYOUT = GT_LAYOUT
 IT_FIELDCAT = GT_FIELDCAT
 TABLES
 T_OUTTAB = GT_FINAL.
FORM USER_COMMAND USING R_UCOMM LIKE SY-UCOMM
 RS_SELFIELD TYPE SLIS_SELFIELD.
DATA: GWA_FINAL LIKE GT_FINAL.
CASE R_UCOMM.
 WHEN 'KUNNR'.
 READ TABLE GT_FINAL INTO GWA_FINAL INDEX RS_SELFIELD-TABINDEX.
 IF SY-SUBRC = 0.
 SET PARAMETER ID 'KUN' FIELD GWA_FINAL-KUNNR.
 CALL TRANSACTION 'XD03' AND SKIP FIRST SCREEN.
 ENDIF.
ENDCASE.
ENDFORM.
Max

How to use call transaction stmt from webdynpro application

Hi Expers,
Can I use call transaction 'tcode' in my webdynpro application, I have tried in my application but i am getting short dump saying
Error analysis+
An exception occurred that is explained in detail below.The exception, which is assigned to class'CX_SY_SEND_DYNPRO_NO_RECEIVER', was not caught and therefore caused a runtime error. The reason for the exception is: During background processing, the system attempted to send a screen to a user. Current screen: "SAPLMGMM " 0060.
I haven't used any more statements in my application am sure from my application side everything perfect. but I have seen a screen shot
with SAP screen in webbrowser.
Please help me out if you are not clear abt my doubt please ask me for clear idea.
Thanks in advance
Phalani M

Hello,
Since you can't use the call transaction command in web dynpros components, I suggest you to create a report and fill a BDC table on this and use the call transaction in this report.
So, in your web dynpro component you can use a command SUBMIT to create a job in background.
DATA: number TYPE tbtcjob-jobcount,
 name TYPE tbtcjob-jobname VALUE 'JOB_TEST',
 print_parameters TYPE pri_params.
CALL FUNCTION 'JOB_OPEN'
EXPORTING
 jobname = name
IMPORTING
 jobcount = number
EXCEPTIONS
 cant_create_job = 1
 invalid_job_data = 2
 jobname_missing = 3
 OTHERS = 4.
IF sy-subrc = 0.
SUBMIT submitable TO SAP-SPOOL
 SPOOL PARAMETERS print_parameters
 WITHOUT SPOOL DYNPRO
 VIA JOB name NUMBER number
 AND RETURN.
IF sy-subrc = 0.
 CALL FUNCTION 'JOB_CLOSE'
 EXPORTING
 jobcount = number
 jobname = name
 strtimmed = 'X'
 EXCEPTIONS
 cant_start_immediate = 1
 invalid_startdate = 2
 jobname_missing = 3
 job_close_failed = 4
 job_nosteps = 5
 job_notex = 6
 lock_failed = 7
 OTHERS = 8.
 IF sy-subrc <> 0.
 ENDIF.
ENDIF.
ENDIF.
Regards.

How to Debug Call transaction ?

Hi ,
I want to debug a BDC program . In the debug I want to change the MODE value to 'A '. Currently it is hard coded . Statement in the code looks like this
CALL TRANSACTION 'VL01N' USING bdcdata
                                MODE 'N'
                                UPDATE 'S'
                                MESSAGES INTO messtab.
I dont have the option to modify or copy the code.
Please let me know is theer a way to do it ? Thank you very much in advance.
Thanks & regards
Nanaiah

HI,
Put a Break point in the Call transcation and change the mode value to 'A' during the Debugging or change the mode value to 'A' for the testing part or do the below declaration
DATA opt TYPE ctu_params.
opt-dismode = 'E'.
opt-defsize = 'X'.
In that give the dismode = 'A'.
CALL TRANSACTION 'VL01N' USING bdcdata_tab OPTIONS FROM opt
UPDATE 'S'
MESSAGES INTO messtab.
While doing that take care u r not saving any data .
With Regards,
Sumodh.P
Edited by: Sumodh P on May 11, 2010 11:09 AM

How i can call transaction into conteiner

hi,
i hope you can help me,
i want call one transaction into the conteiner.
i try everyting but dont working
REPORT Z_IGOR_TESTE2.
DATA: G_CUSTOM_CONTAINER TYPE REF TO CL_GUI_CUSTOM_CONTAINER.
CLASS create_report DEFINITION
CLASS create_report DEFINITION INHERITING FROM cl_gui_alv_grid.
PUBLIC SECTION.
METHODS:
call_transactio.
ENDCLASS. "create_report DEFINITION
CLASS create_report IMPLEMENTATION
CLASS create_report IMPLEMENTATION .
METHOD call_transactio.
call transaction 'SM30'.
ENDMETHOD. "
ENDCLASS. "create_report IMPLEMENTATION
START-OF-SELECTION.
call screen 100.
*& Module STATUS_0100 OUTPUT
text
module STATUS_0100 output.
SET PF-STATUS 'xxxxxxxx'.
SET TITLEBAR 'xxx'.
data: initial type c,
sm30 type string VALUE 'SM30',
teste TYPE REF TO create_report.
if initial NE 'X'.
CREATE OBJECT G_CUSTOM_CONTAINER
EXPORTING CONTAINER_NAME = 'CC'.
CREATE OBJECT teste
EXPORTING I_PARENT = G_CUSTOM_CONTAINER.
*SET HANDLER: create_report2=>call_transaction FOR create_report.
CALL METHOD teste->call_transactio.
INITIAL = 'X'.
endif.
endmodule.

The main issue is that you can have only one main dynpro (I don't talk about its possible subscreens) and any number of docking containers (outside the dynpro). But these docking containers must be created from the PBO of the main dynpro.
If it's for SM30, I think it is possible only by a modification of the standard. Note that SM30 already handles docking containers, as you can see when you call a view cluster (SM34, docking container at the left of the dynpro).

How to find CALL TRANSACTION templete

Hello Experts
I'd like to Call Transaction SE11 in Batch Input Program.
Is there any way to find pre-defined templete of
CALL TRANSACTION 'SE11'
like finding Function module or Method

HI,
You can directly call se11 transaction in the program.
you can also enter the table name in the se11 screen thru BDC and skip the first screen.
Regards,
Anil.

How to determine the transaction type?

Hello,
I have a requirement to disable the user when the role string field on the usr form is empty. I set up a post update entity adapter to do that and it works fine.
When I want to enable the user using the Enable button, the above post update entity adapter detects that the role string field is empty and the user is Active, it disables the user right back.
So, I need to set up a pre-update entity adapter that can detect the type of transaction. If the transaction is to Enable the Xellerate User, then I will update the role string to a dummy value (as long as it's not empty) so that the Disable adapter doesn't get fired.
Is this possible to do? Where can I find the transaction type information for a given Object?
Thanks
Khanh

Thanks
This is the information that i got :
java version "1.4.2_07"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_07
Java HotSpot(TM) Client VM (build 1.4.2_07-b05, mixed mode)
from this i could make out that the jvm is client version,, but how do i determine which vendor has provided the jvm .

Call transaction in web by WebDynpro

Good day!
How i can call transaction with parameters from my web dynpro?
I need from my WebDynpro program run for ex:
http://yourabaphost.domain.com:port/sap/bc/gui/sap/its/webgui?~transaction=iw32
Regards.
Points guaranteed.

Hi.
Oh now i see .. you could use this URL as source in an WebDynpro IFrame. Worked without problems here.
But keep in mind that the WebDynpro IFrame is obselete.
Or open a new window with this URL ?
Cheers,
Sascha
Message was edited by:
Sascha Dingeldey

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.

Regarding BDC and Call transaction Method

hi gurus,
can anyone tell the difference how many records Call transaction and Session
Method can upload in case of single transaction and what is the time taken by each.its urgent pls.
thanks and regards.

Rajesh,
u can do as many as ,
coming to speed means it depends on server,
if ur using session then u can calculate time ,
with in one time h many records system will upload the records by seeing in sm35
(first see h many records systems uploads, see the number and put the time , after one min again see the records h many it is ,) u can calculate by this.
remember this speed will changes depends on server,
so if u have n number of records better to do upload in weekends.
2) if u r using call transaction method means , normally we use error file where ever record occurs that record is in error file, i think we cant analyze h many records it will be with in a time r .
we can also check by going respective tables , just put the time and do refreshing the table after one minute , n this way u can analyze .
Thanks

Call transaction PFCG

HI
I am folowing this help
http://help.sap.com/saphelp_nw04/helpdata/en/c4/51104159ecef23e10000000a155106/content.htm
In the Note (tip)
its given that
call transaction PFCG on your SAP Web AS host
my question is
How I can call transaction PFCG on your SAP Web AS host
what is SAP Web host here, how can I log on to that
any TC or any URL ?
thanks
manian
Edited by: manian on May 5, 2008 11:29 AM

Hi
/people/michael.nicholls/blog/2008/03/03/assign-portal-role-while-editting-it
Please go through the above blog
Regards
Abhishek Mahajan
This might help
**Please reward points if helpful**

How to skip first screen while calling transaction

Hi all,
I am using interactive alv.
if i select one line and press details
that must go to another screen.
In that i must skip first screen and directly go to the details of that first screen.
suppose i am using the code as follows
call transaction mm01 and skip first screen
this is giving me error.
how to solve the problem.
thanks and regards,
giri.

hi giri,
For ur requirement, u can use SKIP FIRST SCREEN addition for CALL TRANSACTION Command.
Before this, u have to use SET PARAMETER ID Command to pass the required values for transaction.
Example, In transaction VA01, we have to set parameter AUN to pass the sale order number to the transaction.

AT LINE-SELECTION .
SET PARAMETER ID 'AUN' FIELD w_vbeln.
CALL TRANSACTION 'VA01' AND SKIP FIRST SCREEN .
where w_vbeln contains the sale ordre number. Now VA01 runs for this sale order number..... And AUN is the PARAMETER to be set before calling VA01 TCODE.
similarly, check the PARAMETER associated with MM01 Tcode and initialize that parameter and call the code in the similar way.
To check parameter Id of MM01,
1) Enter MM01 Transaction
2) Press F1 on Material Field
3) Select Technical Info
4) u can find Parameter ID associated with this field.
check these links for full details.
call transaction...
http://help.sap.com/saphelp_47x200/helpdata/en/78/21761c51ce11d189570000e829fbbd/frameset.htm
at line selection,
http://help.sap.com/saphelp_47x200/helpdata/en/9f/dba2c435c111d1829f0000e829fbfe/frameset.htm
get/set parameter:
http://help.sap.com/saphelp_nw04/helpdata/en/5b/7bc3775d1111d295ad0000e82de14a/frameset.htm
Reward me if useful........
Harimanjesh AN

How to determine calling transaction?

Similar Messages

Maybe you are looking for