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

Similar Messages

HTC Droid DNA - How to enable Call Forwarding in GSM mode in International Network

Hi,
I have bought HTC Droid DNA (Verizon) from ebay in India and I am able to use any 2G or 3G GSM network as it not locked by Verizon however there is no option to enable CALL Forwarding in phone settings.
Please help me and let me know how to enable call forwarding in HTC Droid DNA in GSM mode,

I don't think you can, call forwarding is enabled by Verizon here in the states. Maybe check with your carrier?

Can any one tell me how to enable call waiting in blackberry z3

I'm not able to find the in de ice setting to enable call waiting, pls suggest how to do it

In the Phone app, swipe down from the top of the screen.
Tap > Call Waiting.
Tap the Call Waiting switch.
http://docs.blackberry.com/en/smartphone_users/deliverables/47561/amc1343098614944.jsp
Click if you want to Thank someone. If Problem is resolved, so that others can make use of it.

How to enable me53n transaction in Portal

Hi,
I would like to know how can we enable me53n transaction in Portal as our company have limited number of SAP licenses but everyone would like to see the PR details.
Almost all our employees have Portal ID's thus we would like to know if the above requirement can be fulfilled.
Best Regards
Faisal Habib

Hi,
   1. Showing me53n Transaction in Portal is possible using Transaction iView as well as IAC iView.
   2. SSO will work only if User Mapping or same user exist in R/3 System. In your case since only limited licences exist, I am not sure whether No. Of Portal Users = No. of R/3 Users.
   3. Or else, If a common R/3 ID is there for Purchase Requisition (PR) purpose you can, use the ID while logging into R/3 system to access the transaction.
Regards
Tushar Shinde.

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 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

How to enable STAT transaction

Hi,
I want to find what transactions a particular user was running for a given period, for that I need to enable transaction "STAT".
What are the steps that I need to follow to enable STAT transaction.
Is there any pre-requisite?
Thanks in advance.
Mahendra

Mahendra,
STAT has been replaced by STAD trasaction.They read from stat files. This file has a fixed size. the system write in it a circular fashion , the oldes data is replaced. System is keeping some history of this in sums by weeks and months, depended on the setting in the system.
note 127642 and 6833 can provide more info
about this
please go to this link for more details
http://help.sap.com/saphelp_nw04/helpdata/en/3d/7b5f3c31727d59e10000000a114084/frameset.htm
Thanks
Pricne Jose

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 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 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

Call transaction error handling

how to maintain the log i.e sucess/failures like below.
Line No. Success/ Failure Document No Error Details
1 S Doc 740000001
2 S Doc 740000002
3 F Co- code does not exist
4 F GL Account does not exist
I'm getting only one last document no: but i need all the documents to be displayed i.e either success/failures.
below is my code.
TYPES: BEGIN OF ty_filedata,
 bukrs TYPE bukrs, "Company code
 blart TYPE blart, "Document type
 bldat TYPE char10, "Document Date
 budat TYPE char10, "Posting date
 xblnr TYPE xblnr, "Reference
 bktxt TYPE bktxt, "Document Header text
 waers TYPE waers, "Currency
 newbs TYPE bschl, "Posting Key for the next line item
 wrbtr TYPE char10, "Amount
 zuonr LIKE bsik-zuonr, "Assignment
 sgtxt TYPE sgtxt, "Text
 newko TYPE hkont, "Account for the next line item
 END OF ty_filedata.
TYPES: BEGIN OF ty_detail_log,
 item_no TYPE i, " Item line no.
 status(1) TYPE c, " Status - success/failure
 doc_no TYPE bkpf-belnr," Document No.
 message TYPE string, " Message
 END OF ty_detail_log.
*& DATA declaration of internal tables
 Internal Table declaration for excel data
DATA: it_itab TYPE STANDARD TABLE OF alsmex_tabline INITIAL SIZE 0,
 Internal Table declaration for upload data
 it_upload TYPE STANDARD TABLE OF ty_filedata INITIAL SIZE 0,
 Internal Table Declaration for BDCDATA
 it_bdcdata TYPE STANDARD TABLE OF bdcdata,
 Internal Table Declaration for BDCMSGCOLL
 it_bdcmsgcoll TYPE STANDARD TABLE OF bdcmsgcoll,
 Internal Table Declaration for FILENMAE
 lf_fname TYPE rlgrap-filename.
 t_err_log TYPE STANDARD TABLE OF ty_err
 INITIAL SIZE 0, " table for validation error log
 t_DETAIL_LOG TYPE STANDARD TABLE OF TY_DETAIL_LOG.
 C_MSGNO TYPE BDC_MNR VALUE '312',
*& DATA declaration of work area
 Work Area declaration for Excel Data
DATA: w_itab TYPE alsmex_tabline,
 Work Area declaration for upload data
 w_upload TYPE ty_filedata,
 Work Area declaration for upload data
 w_upload_n TYPE ty_filedata,
 Work Area declaration for upload data
 w_bdcdata TYPE bdcdata,
 Work Area declaration for upload data
 w_bdcmsgcoll TYPE bdcmsgcoll,
 w_detail_log TYPE ty_detail_log.
*& SELECTION-SCREEN
SELECTION-SCREEN: BEGIN OF BLOCK bk1 WITH FRAME TITLE text-001.
PARAMETERS:p_file TYPE rlgrap-filename. " MODIF ID G1.
SELECTION-SCREEN: END OF BLOCK bk1.
*& AT SELECTION SCREEN
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
 EXPORTING
 dynpro_number = syst-dynnr
 CHANGING
 file_name = p_file
 EXCEPTIONS
 mask_too_long = 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.
*& START-OF-SELECTION
START-OF-SELECTION.
DATA: lw_itab TYPE alsmex_tabline.
lf_fname = p_file.
CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
 EXPORTING
 filename = lf_fname
 i_begin_col = '1'
 i_begin_row = '6'
 i_end_col = '12'
 i_end_row = '999'
 TABLES
 intern = it_itab[]
 EXCEPTIONS
 inconsistent_parameters = 1
 upload_ole = 2
 OTHERS = 3.
IF sy-subrc <> 0.
*MESSAGE S205(ZF_COMMON_MSGS_FIN1) DISPLAY LIKE C_E.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ELSE.
IF it_itab IS NOT INITIAL.
 SORT it_itab BY row col.
DELETE it_itab WHERE row LT 6.
 LOOP AT it_itab INTO lw_itab.
 w_itab = lw_itab.
 AT NEW row.
 CLEAR: w_upload.
 ENDAT.
 CASE w_itab-col.
 WHEN '0001'.
 w_upload-bukrs = w_itab-value.
 WHEN '0002'.
 w_upload-blart = w_itab-value.
 WHEN '0003'.
 w_upload-bldat = w_itab-value.
 WHEN '0004'.
 w_upload-budat = w_itab-value.
 WHEN '0005'.
 w_upload-xblnr = w_itab-value.
 WHEN '0006'.
 w_upload-bktxt = w_itab-value.
 WHEN '0007'.
 w_upload-waers = w_itab-value.
 WHEN '0008'.
 w_upload-newbs = w_itab-value.
 WHEN '0009'.
 w_upload-wrbtr = w_itab-value.
 WHEN '0010'..
 w_upload-zuonr = w_itab-value.
 WHEN '0011'.
 w_upload-sgtxt = w_itab-value.
 WHEN '0012'.
 w_upload-newko = w_itab-value.
 ENDCASE.
 AT END OF row.
 APPEND w_upload TO it_upload.
 CLEAR: w_upload.
 ENDAT.
 ENDLOOP.
*endif.
ENDIF.
DATA: lw_upload TYPE ty_filedata,
 lv_lines TYPE sy-tabix,
 lv_index TYPE sy-tabix.
DESCRIBE TABLE it_upload LINES lv_lines.
LOOP AT it_upload INTO lw_upload.
 lv_index = sy-tabix.
 w_upload = lw_upload.
 IF NOT w_upload-bukrs IS INITIAL.
 IF lv_index GT 1.
 CALL TRANSACTION 'FB01' USING it_bdcdata
 MODE 'N' UPDATE 'S' MESSAGES INTO it_bdcmsgcoll.
 PERFORM fr_format_message_text.
 REFRESH: it_bdcdata.
 ENDIF.
 PERFORM bdc_dynpro USING 'SAPMF05A' '0100'.
 PERFORM bdc_field USING 'BDC_CURSOR'
 'BKPF-XBLNR'.
 PERFORM bdc_field USING 'BDC_OKCODE'
 '/00'.
 PERFORM bdc_field USING 'BKPF-BLDAT'
 w_upload-bldat.
 PERFORM bdc_field USING 'BKPF-BLART'
 w_upload-blart.
 PERFORM bdc_field USING 'BKPF-BUKRS'
 w_upload-bukrs.
 PERFORM bdc_field USING 'BKPF-BUDAT'
 w_upload-budat.
 PERFORM bdc_field USING 'BKPF-WAERS'
 w_upload-waers.
 PERFORM bdc_field USING 'BKPF-XBLNR'
 w_upload-xblnr.
*perform bdc_field using 'FS006-DOCID'
 PERFORM bdc_field USING 'RF05A-NEWBS'
 w_upload-newbs.
 PERFORM bdc_field USING 'RF05A-NEWKO'
 w_upload-newko.
 ENDIF.
 IF lv_index NE lv_lines.
 lv_index = lv_index + 1.
 READ TABLE it_upload INTO w_upload_n INDEX lv_index.
 PERFORM bdc_dynpro USING 'SAPMF05A' '0300'.
 PERFORM bdc_field USING 'BDC_CURSOR'
 'BSEG-WRBTR'.
 PERFORM bdc_field USING 'BDC_OKCODE'
 '/00'.
 PERFORM bdc_field USING 'BSEG-WRBTR'
 w_upload-wrbtr.
 PERFORM bdc_field USING 'RF05A-NEWBS'
 w_upload_n-newbs.
 PERFORM bdc_field USING 'RF05A-NEWKO'
 w_upload_n-newko.
 ELSE.
 PERFORM bdc_dynpro USING 'SAPMF05A' '0300'.
 PERFORM bdc_field USING 'BDC_CURSOR'
 'BSEG-WRBTR'.
 PERFORM bdc_field USING 'BDC_OKCODE'
 '=BU'.
 PERFORM bdc_field USING 'BSEG-WRBTR'
 w_upload-wrbtr.
 ENDIF.
 PERFORM bdc_dynpro USING 'SAPLKACB' '0002'.
 PERFORM bdc_field USING 'BDC_CURSOR'
 'COBL-ANLN1'.
 PERFORM bdc_field USING 'BDC_OKCODE'
 '=ENTE'.
ENDLOOP.
CALL TRANSACTION 'FB01' USING it_bdcdata
 MODE 'N' UPDATE 'S' MESSAGES INTO it_bdcmsgcoll.
PERFORM fr_format_message_text .
REFRESH: it_bdcdata.
*& Form BDC_DYNPRO
FORM bdc_dynpro USING program dynpro.
CLEAR w_bdcdata.
w_bdcdata-program = program.
w_bdcdata-dynpro = dynpro.
w_bdcdata-dynbegin = 'X'.
APPEND w_bdcdata TO it_bdcdata.
ENDFORM. "BDC_DYNPRO
 Insert field *
FORM bdc_field USING fnam fval.
IF fval <> space.
 CLEAR w_bdcdata.
 w_bdcdata-fnam = fnam.
 w_bdcdata-fval = fval.
 APPEND w_bdcdata TO it_bdcdata.
ENDIF.
ENDFORM. "BDC_FIELD
*& Form fr_format_message_text
FORM fr_format_message_text.
DATA: lf_msg TYPE string.
WRITE:/ sy-uline(125).
FORMAT COLOR 1 INTENSIFIED ON.
WRITE : /1 sy-vline,
 2 text-041 , "'record Number',
 16 sy-vline,
 17 text-042 , " 'success/failure',
 35 sy-vline,
 36 text-043, " 'document no',
 55 sy-vline,
 56 text-044, "'Error details',
 125 sy-vline.
WRITE:/ sy-uline(125).
LOOP AT it_bdcmsgcoll INTO w_bdcmsgcoll.
 CALL FUNCTION 'FORMAT_MESSAGE'
 EXPORTING
 id = w_bdcmsgcoll-msgid
 lang = sy-langu
 no = w_bdcmsgcoll-msgnr
 v1 = w_bdcmsgcoll-msgv1
 v2 = w_bdcmsgcoll-msgv2
 v3 = w_bdcmsgcoll-msgv3
 v4 = w_bdcmsgcoll-msgv4
 IMPORTING
 msg = lf_msg
 EXCEPTIONS
 not_found = 1
 OTHERS = 2.
 IF sy-subrc EQ 0.
 WRITE:/01 sy-vline,
 02 sy-tabix,
 16 sy-vline,
 17 w_bdcmsgcoll-msgtyp,
 35 sy-vline,
 36 w_bdcmsgcoll-msgv1,
 55 sy-vline,
 56 lf_msg,
 125 sy-vline.
 WRITE:/ sy-uline(125).
 ENDIF.
ENDLOOP.
ENDFORM. "fr_format_message_text
Thanks in advance.

Hi Neelima,
Just put the following code within that LOOP...ENDLOOP statement.
LOOP AT it_upload INTO lw_upload.
CALL TRANSACTION 'FB01' USING it_bdcdata
MODE 'N' UPDATE 'S' MESSAGES INTO it_bdcmsgcoll.
PERFORM fr_format_message_text .
REFRESH: it_bdcdata.
ENDLOOP.
Regards,
R.Nagarajan.
We can -

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

What is the diffreence between call transaction and session method

hi gurus
can any one suggest me
what is the difference between call transaction and session methods
in which cases we have to use teh call transaction and
in which cases we have to use session method.
thank you
regards
kals.

CLASSICAL BATCH INPUT (Session Method)
CALL TRANSACTION
BATCH INPUT METHOD:
This method is also called as ‘CLASSICAL METHOD’.
Features:
Asynchronous processing.
Synchronous Processing in database update.
Transfer data for more than one transaction.
Batch input processing log will be generated.
During processing, no transaction is started until the previous transaction has been written to the database.
CALL TRANSACTION METHOD :
This is another method to transfer data from the legacy system.
Features:
Synchronous processing. The system performs a database commit immediately before and after the CALL TRANSACTION USING statement.
Updating the database can be either synchronous or asynchronous. The program specifies the update type.
Transfer data for a single transaction.
Transfers data for a sequence of dialog screens.
No batch input processing log is generated.
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
Among the two methods call transaction is better compared to session bcoz data transfer is faster in it.
Differences between call transaction and session.
Session Method:
1) Data is not updated in the database table until the session is processed.
2) No sy-subrc is returned.
3) Error log is created for error records.
4) Updation is always synchronous.
Call Transaction Method:
1) Immediate updation in the database table.
2) sy-subrc is returned.
3)Error need to be handled explicitly.
4) updation can be synchronous as well as asynchronous.
2) ya u can use using the N mode no screen.
3)u can't handle multiple transaction in call transaction.
4) u can handle multiple transaction in session using the BDC_INSERT fm.
5)When u go to SM35 u can able to see the error records.
Which is best?
That depends on your requirement. Both of them have there advantages.
According to the situation u can choose any one of these.
difference between batch input and call transaction in BDC Session method.
1) synchronous processing.
2) can tranfer large amount of data.
3) processing is slower.
4) error log is created
5) data is not updated until session is processed.
Call transaction.
1) asynchronous processing
2) can transfer small amount of data
3) processing is faster.
4) errors need to be handled explicitly
5) data is updated automatically
For session method,these are the function modules to b used.
BDC_OPEN_GROUP
BDC_INSERT
BDC_CLOSE_GROUP
For call transaction,this is the syntax.
CALL TRANSACTION TCODE USING BDCDATA
MODE A or E or N
UPDATE A or S
MESSAGES INTO MESSTAB.
Take a scenario where we need to post documents in FB01 and the input file has say 2000 records (2000 documents, not line items in FB01 but 2000 records)
In the BDC call transaction method
We call the transaction FB01 2000 times (once for each record posting) and if the processing fails in record no 3 it can be captured and start with reocord 4.
Eg: Loop at itab.
call transaction FB01
capture errors
endloop.
In the session method.
We do not explicity call the transaction 2000 times, but all the records are appeneded into a session and this session is stored. The processinf of the session is done wwhenever the user wants it to be done. Hence the errors cannot be captured in the program itself
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
Batch Input Session method is asynchronous as told by others here. But the advantage of this is that you have all the error messages and the data for each transaction held persistantly. You don't have to code anything for processing them or writing the logs.
But at the same time, the same feature can be disadvantageous if you need to react to an error or if there are too many errors to manually correct in a session. Since the session are created in the program and its execution is done seperately, you loose the trackability of such transactions.
With a call transaction, what was a disadvantage above will become an advantage. Call transaction immediately gives you messages back and you can react to it in your program. But the disadvantage is that, if you have several hundreds of transactions to run, running them from within the program can be resource crunching affair. It will hamper the system performance and you cannot really distribute the load. Of course, you have some mechanisms with which you can overcome this, but you will have to code for it. Also, storing the messages and storing the errored transaction data etc will have to be handled by you in the program. Whereas, in batch input session, your program's job is to just create the session, after that everything is standard SAP system's responsibility.
Ideally, you should do a call transaction if the resources are not a problem and if it fails, put the errored transaction into a session.
You can decide based on the data volume that your BDC is processing. If data volume is high go for session else call transaction will do.The call transaction updates will be instantaneous where as session needs to be processed explictly after creation.
Session Method
1) Session method supports both small amount of data aswell as large amount of data
2) data processing is asynchronus and data updation is synchronus.
3) it process multiple apllication while perfomaning validations.
4) in session method data will be updated in data base only after processing session only.
5) system provide by default logfile for handling error records.
6) it supports both foreground aswell as background process
in bdc we use FM ...
bdc_open_group " for creating Session
bdc_insert " adding transaction and bdcdata table for updating database
bdc_close_group " for closing Session
Call Transaction
1) Call transaction exclusively for small amout of data
2) it supports only one apllication while perfoming validations
3) there is no default logfile, We can explicitly provide logic for creating logfile for handling error records.
we can create logfile by using structure....BDCMSGCOLL
4) it doesn't support background processing.
5) data processing is synchronous and Data updation is Synchronous( default), in
this method also supports daya updation in asynchronus process also.
syntax:
Call transaction <transaction-name> using BDCDATA
mode <A/N/E>
update <L/A/S>
messages into BDCMSGCOLL.
BDC:
Batch Data Communication (BDC) is the process of transferring data from one SAP System to another SAP system or from a non-SAP system to SAP System.
Features :
BDC is an automatic procedure.
This method is used to transfer large amount of data that is available in electronic medium.
BDC can be used primarily when installing the SAP system and when transferring data from a legacy system (external system).
BDC uses normal transaction codes to transfer data.
Types of BDC :
CLASSICAL BATCH INPUT (Session Method)
CALL TRANSACTION
BATCH INPUT METHOD:
This method is also called as ‘CLASSICAL METHOD’.
Features:
Asynchronous processing.
Synchronous Processing in database update.
Transfer data for more than one transaction.
Batch input processing log will be generated.
During processing, no transaction is started until the previous transaction has been written to the database.
CALL TRANSACTION METHOD :
This is another method to transfer data from the legacy system.
Features:
Synchronous processing. The system performs a database commit immediately before and after the CALL TRANSACTION USING statement.
Updating the database can be either synchronous or asynchronous. The program specifies the update type.
Transfer data for a single transaction.
Transfers data for a sequence of dialog screens.
No batch input processing log is generated.
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
call Transaction or session method ?
Check the following links:
http://www.sap-img.com/bdc.htm
See below example code :
Call three FM : BDC_OPEN_GROUP,BDC_INSERT and BDC_CLOSE_GROUP.
Once you execute the program and it creates the session at SM35 Transaction.
Report : ZMPPC011
Type : Data upload
Author : Chetan Shah
Date : 05/05/2005
Transport : DV3K919557
Transaction: ??
Description: This ABAP/4 Program creates new Production Versions
(C223). It accepts tab-delimited spreadsheet input and
creates BDC sessions.
Modification Log
Date Programmer Request # Description
06/10/2005 Chetan Shah DV3K919557 Initial coding
report zmppc011 no standard page heading line-size 120 line-count 55
message-id zz.
pool of form routines
include zmppn001.
Define BDC Table Structure
data: begin of itab_bdc_tab occurs 0.
include structure bdcdata.
data: end of itab_bdc_tab.
Input record layout of Leagcy File
data: begin of itab_xcel occurs 0,
matnr(18) type c,
werks(4) type c,
alnag(2) type c,
verid(4) type c,
text1(40) type c,
bstmi like mkal-bstmi,
bstma like mkal-bstma,
adatu(10) type c,
bdatu(10) type c,
stlal(2) type c,
stlan(1) type c,
serkz(1) type c,
mdv01(8) type c,
elpro(4) type c,
alort(4) type c,
end of itab_xcel.
data: begin of lt_pp04_cache occurs 0,
matnr like itab_xcel-matnr,
werks like itab_xcel-werks,
alnag like itab_xcel-alnag,
plnnr like mapl-plnnr,
arbpl like crhd-arbpl,
ktext like crtx-ktext,
end of lt_pp04_cache.
data: v_ssnnr(4) type n,
v_lines_in_xcel like sy-tabix,
v_ssnname like apqi-groupid,
v_trans_in_ssn type i,
wa_xcel LIKE itab_xcel,
l_tabix like sy-tabix,
v_matnr like rc27m-matnr,
v_plnnr like mapl-plnnr,
v_plnal like mapl-plnal,
v_tcode like sy-tcode value 'C223',
v_plnty like plas-plnty value 'R',
v_objty like crhd-objty value 'A',
v_plpo_steus like plpo-steus value 'PP04',
v_verwe like crhd-verwe value '0007'.
Parameters
selection-screen: skip 3.
selection-screen: begin of block 1 with frame.
parameters: p_name like rlgrap-filename
default 'C:\My Documents\InputFile.txt'
obligatory,
bdc session name prefix
p_bdcpfx(6) default 'ZPVCRT'
obligatory,
number for transction per BDC session
p_trnssn type i
default 2000 obligatory,
retain the BDC session after successfull execution
p_keep like apqi-qerase
default 'X',
user who will be executing BDC session
p_uname like apqi-userid
default sy-uname
obligatory.
selection-screen: end of block 1.
possible entry list (F4 dropdown) for input file name
at selection-screen on value-request for p_name.
*-SELECT FILE FROM USERS LOCAL PC
call function 'WS_FILENAME_GET'
exporting
DEF_FILENAME = ' '
def_path = 'C:\Temp\'
mask = ',.,..'
mode = 'O'
title = 'Select File '(007)
importing
filename = p_name
RC =
exceptions
inv_winsys = 1
no_batch = 2
selection_cancel = 3
selection_error = 4
others = 5.
if sy-subrc 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
begin the show
start-of-selection.
read data from input file
perform transfer_xcel_to_itab.
loop at itab_xcel.
hang on to xcel line num
l_tabix = sy-tabix.
each line in the xcel file marks begining of new prod.version defn
if num-of-trnas-in-session = 0, create new BDC session
if v_trans_in_ssn is initial.
perform bdc_session_open.
endif.
begin new bdc script for rtg create trans
fill in bdc-data for prod.version maintenance screens
perform bdc_build_script.
insert the bdc script as a BDC transaction
perform bdc_submit_transaction.
keep track of how many BDC transactions were inserted in the BDC
session
add 1 to v_trans_in_ssn.
if the user-specified num of trans in BDC session is reached OR
if end of input file is reached, close the BDC session
if v_trans_in_ssn = p_trnssn or
l_tabix = v_lines_in_xcel.
perform bdc_session_close.
clear v_trans_in_ssn.
endif.
endloop.
top-of-page.
call function 'Z_HEADER'
EXPORTING
FLEX_TEXT1 =
FLEX_TEXT2 =
FLEX_TEXT3 =
FORM TRANSFER_XCEL_TO_ITAB *
Transfer Xcel Spreadsheet to SAP Internal Table *
form transfer_xcel_to_itab.
Read the tab-delimited file into itab
call function 'WS_UPLOAD'
exporting
filename = p_name
filetype = 'DAT'
IMPORTING
filelength = flength
tables
data_tab = itab_xcel
exceptions
conversion_error = 1
file_open_error = 2
file_read_error = 3
invalid_table_width = 4
invalid_type = 5
no_batch = 6
unknown_error = 7
others = 8.
if sy-subrc = 0.
sort the data
sort itab_xcel by matnr werks.
clear v_lines_in_xcel.
if no data in the file - error out
describe table itab_xcel lines v_lines_in_xcel.
if v_lines_in_xcel is initial.
write: / 'No data in input file'.
stop.
endif.
else.
if file upload failed - error out
write: / 'Error reading input file'.
stop.
endif.
endform.
FORM BDC_SESSION_OPEN *
Open BDC Session *
form bdc_session_open.
create bdc session name = prefix-from-selectn-screen + nnnn
add 1 to v_ssnnr.
concatenate p_bdcpfx v_ssnnr into v_ssnname.
open new bdc session
call function 'BDC_OPEN_GROUP'
exporting
client = sy-mandt
group = v_ssnname
keep = p_keep
user = p_uname
exceptions
client_invalid = 1
destination_invalid = 2
group_invalid = 3
group_is_locked = 4
holddate_invalid = 5
internal_error = 6
queue_error = 7
running = 8
system_lock_error = 9
user_invalid = 10
others = 11.
endform.
FORM BDC_BUILD_SCRIPT *
Build BDC *
form bdc_build_script.
data: l_arbpl like crhd-arbpl,
l_text1 like mkal-text1,
l_mdv01 like mkal-mdv01,
l_mapl like mapl.
clear bdc-data itab - begin of new bdc transaction
clear itab_bdc_tab.
refresh itab_bdc_tab.
read material cross reference tables to determine sap part#
clear : v_matnr, v_plnnr, v_plnal.
perform read_matnr_cross_ref using itab_xcel-matnr
itab_xcel-werks
changing v_matnr.
determine the version description to use
if itab_xcel-text1 is initial.
l_text1 = itab_xcel-verid.
else.
l_text1 = itab_xcel-text1.
endif.
determine the routing group# and group ctr# to use
perform read_routing .
determine the production line to use
if itab_xcel-mdv01 is initial.
if not provided in the file then:
prod line = work ctr on the last PP04 op of the rtg determined above
perform read_wc_on_last_pp04 using v_plnnr v_plnal
changing l_mdv01.
NOTE: when executing the above form\routine, if v_plnnr is initial
or v_plnal is initial, THEN l_mdv01 will automatically be
returned blank (ie initial)
else.
l_mdv01 = itab_xcel-mdv01.
endif.
build bdc script
perform bdc_build_script_record
fill in initial screen
using: 'X' 'SAPLCMFV' '1000',
' ' 'BDC_OKCODE' '=ENTE',
' ' 'MKAL-WERKS' itab_xcel-werks,
' ' 'MKAL-MATNR' v_matnr,
' ' 'MKAL_ADMIN-DISPO' space,
' ' 'MKAL-PLNNR' space,
' ' 'MKAL_ADMIN-STTAG' space,
' ' 'MKAL-PLNNG' space,
' ' 'MKAL-MDV01' space,
' ' 'MKAL-PLNNM' space,
click create button on initial screen and go to detail screen
'X' 'SAPLCMFV' '1000',
' ' 'BDC_OKCODE' '=CREA',
fill in the detail screen and go back to initial screen
'X' 'SAPLCMFV' '2000',
' ' 'BDC_OKCODE' '=CLOS',
' ' 'MKAL_EXPAND-MATNR' v_matnr,
' ' 'MKAL_EXPAND-VERID' itab_xcel-verid,
' ' 'MKAL_EXPAND-TEXT1' l_text1,
' ' 'MKAL_EXPAND-BSTMI' itab_xcel-bstmi,
' ' 'MKAL_EXPAND-BSTMA' itab_xcel-bstma,
' ' 'MKAL_EXPAND-ADATU' itab_xcel-adatu,
' ' 'MKAL_EXPAND-BDATU' itab_xcel-bdatu,
' ' 'MKAL_EXPAND-PLTYG' v_plnty,
' ' 'MKAL_EXPAND-PLNNG' v_plnnr,
' ' 'MKAL_EXPAND-ALNAG' v_plnal,
' ' 'MKAL_EXPAND-STLAL' itab_xcel-stlal,
' ' 'MKAL_EXPAND-STLAN' itab_xcel-stlan,
' ' 'MKAL_EXPAND-SERKZ' itab_xcel-serkz,
' ' 'MKAL_EXPAND-MDV01' l_mdv01,
' ' 'MKAL_EXPAND-ELPRO' itab_xcel-elpro,
' ' 'MKAL_EXPAND-ALORT' itab_xcel-alort,
save the production version from initial screen
'X' 'SAPLCMFV' '1000',
' ' 'BDC_OKCODE' '=SAVE'.
endform.
FORM BDC_SUBMIT_TRANSACTION *
Submit BDC Session *
form bdc_submit_transaction.
Load BDC script as a trqansction in BDC session
call function 'BDC_INSERT'
exporting
tcode = v_tcode
tables
dynprotab = itab_bdc_tab
exceptions
internal_error = 01
not_open = 02
queue_error = 03
tcode_invalid = 04.
endform.
FORM BDC_BUILD_SCRIPT_RECORD *
form bdc_build_script_record using dynbegin name value.
clear itab_bdc_tab.
if dynbegin = 'X'.
move: name to itab_bdc_tab-program,
value to itab_bdc_tab-dynpro,
'X' to itab_bdc_tab-dynbegin.
else.
move: name to itab_bdc_tab-fnam,
value to itab_bdc_tab-fval.
shift itab_bdc_tab-fval left deleting leading space.
endif.
append itab_bdc_tab.
endform.
FORM BDC_SESSION_CLOSE *
Close BDC Session *
form bdc_session_close.
close the session
call function 'BDC_CLOSE_GROUP'
exceptions
not_open = 1
queue_error = 2
others = 3.
skip 2.
if sy-subrc ne 0.
write: / 'Error Closing BDC Session ' , 'RETURN CODE: ', sy-subrc.
else.
write : / 'Session created:', v_ssnname,
50 '# of transactions:', v_trans_in_ssn.
endif.
endform.
*& Form read_routing_cache
*FORM read_routing_cache USING pi_matnr
pi_werks
pi_alnag
pi_verid
pi_mdv01.
DATA: BEGIN OF lt_plpo OCCURS 0,
vornr LIKE plpo-vornr,
objty LIKE crhd-objty,
objid LIKE crhd-objid,
arbpl LIKE crhd-arbpl,
END OF lt_plpo,
l_mapl_plnnr LIKE mapl-plnnr.
determine the routing group#
CLEAR lt_pp04_cache.
chk if its in the cache first, if not then get it from MAPL table
and put it in the cache
READ TABLE lt_pp04_cache WITH KEY matnr = pi_matnr
werks = pi_werks
alnag = pi_alnag.
IF sy-subrc = 0.
do nothing - lt_pp04_cache header line has rtg#
ELSE.
get the routing group # from MAPL
SELECT plnnr INTO l_mapl_plnnr
FROM mapl UP TO 1 ROWS
WHERE matnr = pi_matnr AND
werks = pi_werks AND
plnty = 'R' AND
plnal = pi_alnag AND
loekz = space.
ENDSELECT.
put it in the cache internal table
IF NOT l_mapl_plnnr IS INITIAL.
lt_pp04_cache-matnr = pi_matnr.
lt_pp04_cache-werks = pi_werks.
lt_pp04_cache-alnag = pi_alnag.
lt_pp04_cache-plnnr = l_mapl_plnnr.
APPEND lt_pp04_cache.
ENDIF.
ENDIF.
if the rtg# was determined AND
the work center was not determined yet AND
work center was really needed for this line in the input file
then
read the work center from last PP04 operation on the routing
update the cache accordingly
IF NOT lt_pp04_cache-plnnr IS INITIAL AND
lt_pp04_cache-arbpl IS INITIAL AND
( pi_verid IS INITIAL OR
pi_mdv01 IS INITIAL ).
read the last PP04 operation
CLEAR lt_plpo.
REFRESH lt_plpo.
SELECT vornr eobjty eobjid e~arbpl
INTO CORRESPONDING FIELDS OF TABLE lt_plpo
FROM plas AS b
INNER JOIN plpo AS c
ON bplnty = cplnty AND
bplnnr = cplnnr AND
bzaehl = czaehl
INNER JOIN crhd AS e
ON carbid = eobjid
WHERE b~plnty = v_plnty AND
b~plnnr = lt_pp04_cache-plnnr AND
b~plnal = lt_pp04_cache-alnag AND
c~loekz = space AND
c~steus = v_plpo_steus AND
e~objty = v_objty AND
e~werks = lt_pp04_cache-werks AND
e~verwe = v_verwe.
SORT lt_plpo BY vornr DESCENDING.
READ TABLE lt_plpo INDEX 1.
IF NOT lt_plpo-arbpl IS INITIAL.
lt_pp04_cache-arbpl = lt_plpo-arbpl.
read work center description
SELECT SINGLE ktext INTO lt_pp04_cache-ktext
FROM crtx WHERE objty = lt_plpo-objty AND
objid = lt_plpo-objid AND
spras = sy-langu.
the following read will get the index of the correct record to be
updated in the cache
READ TABLE lt_pp04_cache
WITH KEY matnr = pi_matnr
werks = pi_werks
alnag = pi_alnag.
MODIFY lt_pp04_cache
INDEX sy-tabix
TRANSPORTING arbpl ktext.
ENDIF.
ENDIF.
*ENDFORM. " read_last_pp04_operation_cache
*& Form read_routing
form read_routing.
data: begin of lt_mapl occurs 0,
plnnr like mapl-plnnr,
plnal like mapl-plnal,
end of lt_mapl,
l_arbpl like crhd-arbpl.
get all the rtg# and grp ctr# from MAPL
select plnnr plnal
into corresponding fields of table lt_mapl
from mapl
where matnr = v_matnr and
werks = itab_xcel-werks and
plnty = v_plnty and "Rate Routing
loekz = space. "with del flag = OFF
sort lt_mapl by plnal.
if not itab_xcel-verid is initial.
if the verid=0001 then use the 1st good rtg-grp# and grp-ctr#
if itab_xcel-verid = '0001'.
read table lt_mapl index 1.
v_plnnr = lt_mapl-plnnr.
v_plnal = lt_mapl-plnal.
else.
if the verid0001 then use the rtg-grp# and grp-ctr# of the routing
whose work center on the last PP04 operation matches the given verid
loop at lt_mapl.
clear l_arbpl.
get the work center from the last PP04 operation
perform read_wc_on_last_pp04 using lt_mapl-plnnr
lt_mapl-plnal
changing l_arbpl.
if itab_xcel-verid = l_arbpl.
v_plnnr = lt_mapl-plnnr.
v_plnal = lt_mapl-plnal.
exit.
endif.
endloop.
endif.
else.
do nothing
endif.
For version IDs that are other then '0000' or 'ZWIP' :--
if itab_xcel-verid NE '0000' and
itab_xcel-verid NE 'ZWIP'.
if routing group# or group counter was not determined, make the
valid-to date 99/99/9999 so that the BDC, on execution, errors out.
if v_plnnr is initial or
v_plnal is initial.
itab_xcel-bdatu = '99/99/9999'.
endif.
endif.
determine the routing group#
CLEAR lt_pp04_cache.
chk if its in the cache first, if not then get it from MAPL table
and put it in the cache
READ TABLE lt_pp04_cache WITH KEY matnr = pi_matnr
werks = pi_werks
alnag = pi_alnag.
IF sy-subrc = 0.
do nothing - lt_pp04_cache header line has rtg#
ELSE.
get the routing group # from MAPL
put it in the cache internal table
IF NOT l_mapl_plnnr IS INITIAL.
lt_pp04_cache-matnr = pi_matnr.
lt_pp04_cache-werks = pi_werks.
lt_pp04_cache-alnag = pi_alnag.
lt_pp04_cache-plnnr = l_mapl_plnnr.
APPEND lt_pp04_cache.
ENDIF.
ENDIF.
if the rtg# was determined AND
the work center was not determined yet AND
work center was really needed for this line in the input file
then
read the work center from last PP04 operation on the routing
update the cache accordingly
IF NOT lt_pp04_cache-plnnr IS INITIAL AND
lt_pp04_cache-arbpl IS INITIAL AND
( pi_verid IS INITIAL OR
pi_mdv01 IS INITIAL ).
read the last PP04 operation
CLEAR lt_plpo.
REFRESH lt_plpo.
SELECT vornr eobjty eobjid e~arbpl
INTO CORRESPONDING FIELDS OF TABLE lt_plpo
FROM plas AS b
INNER JOIN plpo AS c
ON bplnty = cplnty AND
bplnnr = cplnnr AND
bzaehl = czaehl
INNER JOIN crhd AS e
ON carbid = eobjid
WHERE b~plnty = v_plnty AND
b~plnnr = lt_pp04_cache-plnnr AND
b~plnal = lt_pp04_cache-alnag AND
c~loekz = space AND
c~steus = v_plpo_steus AND
e~objty = v_objty AND
e~werks = lt_pp04_cache-werks AND
e~verwe = v_verwe.
SORT lt_plpo BY vornr DESCENDING.
READ TABLE lt_plpo INDEX 1.
IF NOT lt_plpo-arbpl IS INITIAL.
lt_pp04_cache-arbpl = lt_plpo-arbpl.
read work center description
SELECT SINGLE ktext INTO lt_pp04_cache-ktext
FROM crtx WHERE objty = lt_plpo-objty AND
objid = lt_plpo-objid AND
spras = sy-langu.
the following read will get the index of the correct record to be
updated in the cache
READ TABLE lt_pp04_cache
WITH KEY matnr = pi_matnr
werks = pi_werks
alnag = pi_alnag.
MODIFY lt_pp04_cache
INDEX sy-tabix
TRANSPORTING arbpl ktext.
ENDIF.
ENDIF.
endform. " read_last_pp04_operation_cache
*& Form read_wc_on_last_pp04
form read_wc_on_last_pp04 using pi_plnnr
pi_plnal
changing pe_arbpl.
data: begin of lt_plpo occurs 0,
vornr like plpo-vornr,
objty like crhd-objty,
objid like crhd-objid,
arbpl like crhd-arbpl,
end of lt_plpo.
get all the PP04 operations for the given rtg# & grp-ctr#
select vornr eobjty eobjid e~arbpl
into corresponding fields of table lt_plpo
from plas as b
inner join plpo as c
on bplnty = cplnty and
bplnnr = cplnnr and
bzaehl = czaehl
inner join crhd as e
on carbid = eobjid
where b~plnty = v_plnty and "Rate Routing
b~plnnr = pi_plnnr and
b~plnal = pi_plnal and
c~loekz = space and "Oper Del Flag = OFF
c~steus = v_plpo_steus and "PP04
e~objty = v_objty. "WC Obj Type = 'A'
read the last operation
sort lt_plpo by vornr descending.
read table lt_plpo index 1.
pe_arbpl = lt_plpo-arbpl.
endform. " read_wc_on_last_pp04
Goto LSMW-> Select Direct Input method in 1st step. These are the standard programs for data transfer.
Otherwise goto SPRO->SAP Reference IMG-> Under this you'll find standard data transfer programs module wise.
Regards,
Sunil Kumar Mutyala

Call Transaction VT02

Hello Guys,
Need some help in SAP 3.1, I am trying to perform a call transaction VT02 (change shipment) to empty the shipping units and later delete the same. I did code according the recordings but it seems to fail in sync mode due to pop_up_confirm message during deletion..can you please let me know how I can resolve the issue ?
Code -->
REFRESH BDCDATA.
PERFORM BDC_DYNPRO USING 'SAPMV56A' '0011'.
PERFORM BDC_FIELD USING 'BDC_OKCODE' 'TKAL'.
PERFORM BDC_FIELD USING 'BDC_CURSOR' 'VTTK-TKNUM'.
PERFORM BDC_FIELD USING 'VTTK-TKNUM' ITAB-TKNUM.
perform bdc_dynpro      using 'SAPMV56A' '0020'.
perform bdc_field       using 'BDC_OKCODE' 'VSEB'.
perform bdc_field       using 'BDC_CURSOR' 'VTTK-TDLNR'.
PERFORM BDC_DYNPRO USING 'SAPLV51A' '2001'.
PERFORM BDC_FIELD USING 'BDC_OKCODE' 'UVLG'.
PERFORM BDC_FIELD USING 'BDC_CURSOR' 'V51VE-SELKZ(01)'.
PERFORM BDC_FIELD USING 'V51VE-SELKZ(01)' 'X'.
*logic to mark all the units+packs
PERFORM BDC_DYNPRO USING 'SAPLV51A' '2500'.
PERFORM BDC_FIELD USING 'BDC_OKCODE' 'VSEE'.
PERFORM BDC_FIELD USING 'BDC_CURSOR' 'V51V4-SELKZ(01)'.
DO x times
    PERFORM BDC_FIELD USING 'V51V4-SELKZ(06)' 'X'.
    PERFORM BDC_FIELD USING 'V51V4-SELKZ(07)' 'X'.
Enddo.
*logic to mark all the units+packs
PERFORM BDC_DYNPRO USING 'SAPLV51A' '2500'.
PERFORM BDC_FIELD USING 'BDC_OKCODE' 'VELO'.
PERFORM BDC_FIELD USING 'BDC_CURSOR' 'V51V4-SELKZ(01)'.
DO x times
     PERFORM BDC_FIELD USING 'V51V4-SELKZ(05)' 'X'.
Enddo.
PERFORM BDC_DYNPRO USING 'SAPLSP01' '0100'.
PERFORM BDC_FIELD USING 'BDC_OKCODE' 'YES'.
PERFORM BDC_DYNPRO USING 'SAPLV51A' '2500'.
PERFORM BDC_FIELD USING 'BDC_OKCODE' 'ENT1'.
PERFORM BDC_FIELD USING 'BDC_CURSOR' 'V51V4-TMENG(02)'.
PERFORM BDC_DYNPRO USING 'SAPLV51A' '2500'.
PERFORM BDC_FIELD USING 'BDC_OKCODE' 'BACK'.
PERFORM BDC_FIELD USING 'BDC_CURSOR' 'V51V4-TMENG(02)'.
PERFORM BDC_DYNPRO USING 'SAPLV51A' '2001'.
PERFORM BDC_FIELD USING 'BDC_OKCODE' 'SICH'.
PERFORM BDC_FIELD USING 'BDC_CURSOR' 'V51VE-EXIDV(01)'.
CALL TRANSACTION 'VT02' USING BDCDATA
                          MODE 'A'
                          UPDATE'S'.
--Any hints !!

hi
good
yes both of them retrun,
CALL TRANSACTION->
On the face of it, you would think that the Call Transaction has succeeded if "Sy-Subrc = 0" after the call. In an ALE environment this is only half the story, because when the import parameter Input_Method takes on the value "A" or "E", the inbound function module must call the transaction using mode = "A" or "E" ("show all screens" or "show the screens starting with the one where the error occurred"). In this case, the user sees the screens and can cancel the transaction using OK-code "/n", which also leads to "Sy-Subrc = 0" after the call! Hence the only reliable way to tell whether the Call Transaction succeeded or not is to check the message ID (Sy-Msgid) and number (Sy-Msgno). Beware that some transactions have more than one "success" message.
thanks
mrutyun^

Using Txn SE97 -How to enable called transactions?

Similar Messages

Maybe you are looking for