Uploading XL file using call Transaction and running in back ground

Hi all,
I am updating the T-code VA01 using call TRansaction method ....
i am uploading the file is XL file for that i m using the FM ALSM_EXCEL_TO_INTERNAL_TABLE.
But if execute my program in the back ground This FM is giving Dump because it can not Execute in Back GRound...
Plz let me know any FM to upload data from Excel file Both from foreground and back ground....
Plz let me know ASAP..
Thanks,
Suresh

HI...,,
When u run any program in Background, it will not have any contacts with the presentation server.... You cannot upload a presentation server file..
But u can use the Application server file...
SO first store this excel file's data in Application server using the transaction CG3Z and then use the Open data set and read dataset to upload the application server file !!!
reward all helpful answers !!
regards,
sai ramesh

Similar Messages

Can we use Call transaction and session method in same program ?

Hi experts,
Is it suggested to use call Transaction and session method in the same Program ?
i have a doubt , why cant we use multiple call transactions in same program instead of session method if we have multiple transaction updations ?

Hi Dengyong Zhang,
we can use the call transation and session method in same program.
However for better performance it's benificial to use call trasaction method of BDC. but if u want to upload very large amount of data then Session method is more preferable to use.
Session method is one of the method of BDC.
U can also use BAPI to upload the data in SAP but it's a different concept than BDC. Performance wise BAPI is more advantageous than BDC.

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.

Uploading xml file using ADF UIX and storing in ordsys.orddoc field

I am using ADF UIX and I am using the messageFileUpload tag to upload an XML file into the database (the file contains special characters like hyphens, apostrophes, $, etc). Once in the database I have a procedure which puts it into a clob field using the dbms_lob package. However, what exactly does ordsys.orddoc do with special characters? If I debug my procedure I see that 1 of 4 hyphens and 3 apostrophes have been turned into a character that looks like a square. Anyone know what is going on?

It should pass binary information only, no conversion at all.
The conversion is likely in messageFileUpload or the dbms_lob package you are using. Or you may need to tell DBMS_LOB the character set the XML file is in?
You may want to upload the file using the interMedia tag library... Using uploadFormData?
http://www.oracle.com/technology/software/products/intermedia/htdocs/descriptions/tag_library.html
http://www.oracle.com/technology/products/intermedia/htdocs/jsptaglib/html/toc.htm
Larry

I want to use both call transaction and session method in the same

Hi,
          1. I want to use call transaction and session method in a single trans..how to do?
          2. I have 1000 records in it 500 records is updated using call transaction remaining 500 i hve to update with session how to do?
          3. Multiple transaction is possible in call transaction how?

I suggest you try fulfilling your requirements yourself and come back with specific problems along the way.

How to upload error records in call transaction method

Hi all,
While uploading data by using call transaction. If any errors occured, how can we process that error records to database.
If all records are processed. How can we display the recent records which where uploaded.
AdvanceThanks for all.

Hi Bharath
You can handle this in many ways. But the easiest option to do is as below,
once the call transaction ends in error, move that particular upload data to a separate internal table. Then finally download all these data to an error file.
Besides this after processing all the records diplay the log for error. So that users can modify the error in the file and can use the same for uploading again. For the data that has been processed successfully you can display the log similarly.
The error as well as sucess messages can be obtained from the messages table.
    CALL TRANSACTION TCODE USING BDCDATA
                     MODE   CTUMODE
                     UPDATE CUPDATE
                     MESSAGES INTO MESSTAB.
Regards
Kathirvel

Bdc(call transaction and session method)

hi experts,
   i want to write for bdc program in which i have used call transaction and session method.please help me.
thank you
with regards,
santosh

Hi,
See the Sample BDc Code for Vendor Master Upload:
Look at the Include BDCRECX1 for Seesion and Call Transaction types:
REPORT zmm_vendor_master_upload
       NO STANDARD PAGE HEADING
       LINE-SIZE 255.
ABAP Name   :   ZMM_VENDOR_MASTER_UPLOAD
Description :   This Program is used to Upload the Vendor Master.
Modification Log:
Date         Programmer          Correction    Description
Standard Include for Selection Screen
INCLUDE bdcrecx1.
Internal Table for Upload Data
DATA: BEGIN OF i_vendor OCCURS 0,
        bukrs(004),             " Company Code
        ekorg(004),             " Purchase Orgn
        ktokk(004),             " Account Group
Address Screen
        anred(015),             " Title
        name1(035),                                         " Name1
        sortl(010),             " Sort Field
        name2(035),                                         " Name2
        name3(035),             " Contact Person1
        name4(035),             " Contact Person 2
        stras(035),             " Street
        pfach(010),             " PO Box
        ort01(035),             " City
        pstlz(010),             " Postal Code
        land1(003),             " Country
        spras(002),             " Language
        telf1(016),             " Telephone No
        telfx(031),             " Fax Number
        lfurl(132),             " URL-Mail Id
Material Group Characteristics
       klart(003),             " Class Type '010'
       class(018),             " Class 'Vendor'
       mname_01(030),          " Characteristic
       mname_02(030),          " Characteristic
       mname_03(030),          " Characteristic
        mwert_01(030),          " Charct.Value
        mwert_02(030),          " Charct.Value
        mwert_03(030),          " Charct.Value
Control Data
        emnfr(010),             " Manufact.Part No
Bank Details
        banks_01(003),          " Country of Bank1
        banks_02(003),          " Country of Bank2
        bankl_01(015),          " Bank Key of 1
        bankl_02(015),          " Bank Key of 2
        bankn_01(018),          " Account No Bank1
        bankn_02(018),          " Account No Bank2
Accounting Info
        akont(010),             " Reconcillation Account
        zuawa(003),             " Sort Key
        fdgrv(010),             " Cash Management Group
Payment Transactions
        zterm(004),             " Payment terms
       reprf(001),             " Check Double Inv.
        zwels(010),             " Payment Method
        hbkid(005),             " House Bank
       xpore(001),             " Individ.Payment
Correspondence
        mahns(001),             " Dunning Level
        xausz(001),             " Account Statement
Withholding Tax Details
        qland(003),             " Withholding Tax Country
        witht_01(002),          " WH tax Type
       wt_withcd(002),        " WH Tax Code
       wt_subjct(001),        " Indicator:WH Tax
Purchasing Data
        waers(005),             " Currency
        zterm1(004),            " Payment Terms
      END OF i_vendor.
Data Variables & Constants
CONSTANTS : c_x     VALUE 'X'. " Flag
Paramters
PARAMETERS: p_file LIKE ibipparms-path. " Filename
At selection-screen on Value Request for file Name
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
Get the F4 Values for the File
CALL FUNCTION 'F4_FILENAME'
    EXPORTING
      program_name = syst-cprog
      dynpro_number = syst-dynnr
    IMPORTING
      file_name     = p_file.
Start of Selection
START-OF-SELECTION.
Open the BDC Session
PERFORM open_group.
Upload the File into internal Table
CALL FUNCTION 'UPLOAD'
    EXPORTING
      filename                = p_file
      filetype                = 'DAT'
    TABLES
      data_tab                = i_vendor
    EXCEPTIONS
      conversion_error        = 1
      invalid_table_width     = 2
      invalid_type            = 3
      no_batch                = 4
      unknown_error           = 5
      gui_refuse_filetransfer = 6
      OTHERS                  = 7.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Upload the Data from Internal Table
LOOP AT i_vendor.
    PERFORM bdc_dynpro      USING 'SAPMF02K' '0100'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'RF02K-KTOKK'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM bdc_field       USING 'RF02K-BUKRS'
                                  i_vendor-bukrs.
    PERFORM bdc_field       USING 'RF02K-EKORG'
                                  i_vendor-ekorg.
    PERFORM bdc_field       USING 'RF02K-KTOKK'
                                  i_vendor-ktokk.
    PERFORM bdc_dynpro      USING 'SAPMF02K' '0110'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'LFA1-SPRAS'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=KLAS'.
    PERFORM bdc_field       USING 'LFA1-ANRED'
                                  i_vendor-anred.
    PERFORM bdc_field       USING 'LFA1-NAME1'
                                  i_vendor-name1.
    PERFORM bdc_field       USING 'LFA1-SORTL'
                                  i_vendor-sortl.
    PERFORM bdc_field       USING 'LFA1-NAME2'
                                  i_vendor-name2.
    PERFORM bdc_field       USING 'LFA1-NAME3'
                                  i_vendor-name3.
    PERFORM bdc_field       USING 'LFA1-NAME4'
                                  i_vendor-name4.
    PERFORM bdc_field       USING 'LFA1-STRAS'
                                  i_vendor-stras.
    PERFORM bdc_field       USING 'LFA1-PFACH'
                                  i_vendor-pfach.
    PERFORM bdc_field       USING 'LFA1-ORT01'
                                  i_vendor-ort01.
    PERFORM bdc_field       USING 'LFA1-PSTLZ'
                                  i_vendor-pstlz.
    PERFORM bdc_field       USING 'LFA1-LAND1'
                                  i_vendor-land1.
    PERFORM bdc_field       USING 'LFA1-SPRAS'
                                  i_vendor-spras.
    PERFORM bdc_field       USING 'LFA1-TELF1'
                                  i_vendor-telf1.
    PERFORM bdc_field       USING 'LFA1-TELFX'
                                  i_vendor-telfx.
    PERFORM bdc_field       USING 'LFA1-LFURL'
                                  i_vendor-lfurl.
    PERFORM bdc_dynpro      USING 'SAPLCLCA' '0602'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'RMCLF-KLART'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=ENTE'.
    PERFORM bdc_field       USING 'RMCLF-KLART'
                                  '010'. "i_vendor-klart.
    PERFORM bdc_dynpro      USING 'SAPLCLFM' '0500'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'RMCLF-CLASS(01)'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=AUSW'.
    PERFORM bdc_field       USING 'RMCLF-CLASS(01)'
                                  'Vendor'."i_vendor-class.
    PERFORM bdc_dynpro      USING 'SAPLCTMS' '0109'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'RCTMS-MWERT(03)'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=BACK'.
    PERFORM bdc_field       USING 'RCTMS-MNAME(01)'
                       'MATERIALGROUP'." i_vendor-mname_01.
    PERFORM bdc_field       USING 'RCTMS-MNAME(02)'
                       'MATERIALGROUP'." i_vendor-mname_02.
    PERFORM bdc_field       USING 'RCTMS-MNAME(03)'
                       'MATERIALGROUP'." i_vendor-mname_03.
    PERFORM bdc_field       USING 'RCTMS-MWERT(01)'
                                  i_vendor-mwert_01.
    PERFORM bdc_field       USING 'RCTMS-MWERT(02)'
                                  i_vendor-mwert_02.
    PERFORM bdc_field       USING 'RCTMS-MWERT(03)'
                                  i_vendor-mwert_03.
    PERFORM bdc_dynpro      USING 'SAPLCLFM' '0500'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'RMCLF-CLASS(01)'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=ENDE'.
    PERFORM bdc_dynpro      USING 'SAPMF02K' '0110'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'LFA1-ANRED'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=VW'.
    PERFORM bdc_dynpro      USING 'SAPMF02K' '0120'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'LFA1-EMNFR'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=VW'.
    PERFORM bdc_field       USING 'LFA1-EMNFR'
                                  i_vendor-emnfr.
    PERFORM bdc_dynpro      USING 'SAPMF02K' '0130'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'LFBK-BANKN(02)'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=VW'.
    PERFORM bdc_field       USING 'LFBK-BANKS(01)'
                                  i_vendor-banks_01.
    PERFORM bdc_field       USING 'LFBK-BANKS(02)'
                                  i_vendor-banks_02.
    PERFORM bdc_field       USING 'LFBK-BANKL(01)'
                                  i_vendor-bankl_01.
    PERFORM bdc_field       USING 'LFBK-BANKL(02)'
                                  i_vendor-bankl_02.
    PERFORM bdc_field       USING 'LFBK-BANKN(01)'
                                  i_vendor-bankn_01.
    PERFORM bdc_field       USING 'LFBK-BANKN(02)'
                                  i_vendor-bankn_02.
   PERFORM bdc_dynpro      USING 'SAPMF02K' '0130'.
   PERFORM bdc_field       USING 'BDC_CURSOR'
                                 'LFBK-BANKS(01)'.
   PERFORM bdc_field       USING 'BDC_OKCODE'
                                 '=VW'.
    PERFORM bdc_dynpro      USING 'SAPMF02K' '0210'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'LFB1-FDGRV'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=VW'.
    PERFORM bdc_field       USING 'LFB1-AKONT'
                                  i_vendor-akont.
    PERFORM bdc_field       USING 'LFB1-ZUAWA'
                                  i_vendor-zuawa.
    PERFORM bdc_field       USING 'LFB1-FDGRV'
                                  i_vendor-fdgrv.
    PERFORM bdc_dynpro      USING 'SAPMF02K' '0215'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'LFB1-XPORE'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=VW'.
    PERFORM bdc_field       USING 'LFB1-ZTERM'
                                  i_vendor-zterm.
    PERFORM bdc_field       USING 'LFB1-REPRF'
                                  c_x. "i_vendor-reprf.
    PERFORM bdc_field       USING 'LFB1-ZWELS'
                                  i_vendor-zwels.
    PERFORM bdc_field       USING 'LFB1-HBKID'
                                  i_vendor-hbkid.
    PERFORM bdc_field       USING 'LFB1-XPORE'
                                  c_x. "i_vendor-xpore.
    PERFORM bdc_dynpro      USING 'SAPMF02K' '0220'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'LFB5-MAHNS'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=VW'.
    PERFORM bdc_field       USING 'LFB5-MAHNS'
                                  i_vendor-mahns.
    PERFORM bdc_field       USING 'LFB1-XAUSZ'
                                  i_vendor-xausz.
    PERFORM bdc_dynpro      USING 'SAPMF02K' '0610'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=VW'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'LFBW-WT_SUBJCT(01)'.
    PERFORM bdc_field       USING 'LFB1-QLAND'
                                  i_vendor-qland.
    PERFORM bdc_field       USING 'LFBW-WITHT(01)'
                                  i_vendor-witht_01.
   PERFORM bdc_field       USING 'LFBW-WT_WITHCD(01)'
                                 i_vendor-wt_withcd.
    PERFORM bdc_field       USING 'LFBW-WT_SUBJCT(01)'
                                   c_x.
    PERFORM bdc_dynpro      USING 'SAPMF02K' '0310'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'LFM1-ZTERM'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=VW'.
    PERFORM bdc_field       USING 'LFM1-WAERS'
                                  i_vendor-waers.
    PERFORM bdc_field       USING 'LFM1-ZTERM'
                                  i_vendor-zterm1.
    PERFORM bdc_dynpro      USING 'SAPMF02K' '0320'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'RF02K-LIFNR'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=VW'.
    PERFORM bdc_dynpro      USING 'SAPLSPO1' '0300'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=YES'.
Call the Transaction
    PERFORM bdc_transaction USING 'XK01'.
ENDLOOP.
Close the BDc Session
PERFORM close_group.
Regards,
Anji

Main diff between call transaction and session method

hi frnds.
my friend went for an interview they asked her whts the diff between call tran adn session?
she told more thn one transaction we can call for an session she told itseems. but he told tht by cal tran also u cn call more thn one tran it seems... so please canu help me out regarding this question? how we hve to tell in interview?
in advance thanks....

Hi
Batch Input and CALL TRANSACTION are both data transfer methods. Batch Input usually are used to transfer large amount of data. For example you are implementing a new SAP project, and of course you will need some data transfer from legacy system to SAP system. If there is no standard batch input program, direct input program, you would need to write your own data transfer program and it is going to be batch input program. CALL TRANSACTION methods is real-time method, whenever you run the program CALL TRANSACTION can be triggered. CALL TRANSACTION is used especially for integration actions between two SAP systems or between different modules. Users sometimes wish to do something like that click a button or an item then SAP would inserts or changes data automatically. Here CALL TRANSACTION should be considered. You use CALL TRANSACTION and you do everything automatically, collect necessary data, call transaction and so do database update. If any error occurs, show the user them.
Batch Input
With the Batch Input method, an ABAP program reads the external data that is to be entered in the R/3 System and stores the data in a batch input session. The session records the actions that are required to transfer data into the system using normal SAP transactions.
When the program has generated the session, you can run the session to execute the SAP transactions in it. You can explicitly start and monitor a session with the batch input management function (by choosing System - Services - Batch Input), or have the session run in the background processing session.
It offers management of sessions, support for playing back and correcting sessions that contain errors, and detailed logging. Your program prepares the data and stores it in a batch input session. A session is a collection of transaction data for one or more transactions. Batch input sessions are maintained by the system in the batch input queue. You can process batch input sessions in the background processing system.
Your program must open a session in the queue before transferring data to it, and must close it again afterwards. All of these operations are performed by making function modules calls from the ABAP program.
The most important aspects of the session interface are:
Asynchronous processing
Transfer data for multiple transactions
Synchronous database update. During processing, no transaction is started until the previous transaction has been written to the database.
A batch input processing log is generated for each session
Sessions cannot be generated in parallel. The batch input program must not open a session until it has closed the preceding session.
CALL TRANSACTION
In the second method, your program uses the ABAP statement CALL TRANSACTION USING to run an SAP transaction. External data doesnt have to be deposited in a session for later processing. Instead, the entire batch input process takes place inline in your program. With CALL TRANSACTION USING, the system process the data more quickly than with batch input sessions. Unlike batch input sessions, CALL TRANSACTION USING does not automatically support interactive correction or logging functions.
Your program prepares the data and then calls the corresponding transaction that is then processed immediately.
The most important features of CALL TRANSACTION USING are:
Synchronous processing
Transfer of data from an individual transaction each time the statement CALL TRANSACTION USING is called
You can update the database both synchronously and asynchronously. The program specifies the update type.
Separate LUW (Logical Units of Work) for the transaction. The system executes a database commit immediately before and after the CALL TRANSACTION USING statement.
No batch input processing log

CALL TRANSACTION AND SKIP FIRST SCREEN to specified tab in TCODE 'IW32'

Hi,
I am using CALL TRANSACTION AND SKIP FIRST SCREEN in ALV Grid Report to call IW32 tcode and it goes to tcode skipping the first screen. But it goes to the default header tab in the tab control. Whereas I wish to go to the specified tab 'OPERATIONS'.
Can any one help me, as to how to resolve this issue ?
Thanks in advance.

Sridher,
I have the similar requirement. but in my case its COSTS tab. Could you please provide the code you have used for this to work?
I used standard "call transaction with mode 'E' ". This seems to be working but I am not pleased by my effort. Is there any proper way that you might have followed ?
Greatly appreciated your help.
Regards,
Reddy

Error in CALL TRANSACTION and SESSION Method

I have 8 records (1,2,3,4,5,6,7,8) to update into SAP database using CALL TRANSACTION and SESSION Method. If there is a error in 6th record. What happens in both call transaction and session method.
Please let me know which records will process and what about the error record. How to process only the error record if all other records have updated into database.

Hi Patil_sumeet,
if your code for this is not protected secret of some federal agency, you may read [How to post code in SCN, and some things NOT to do...|How to post code in SCN, and some things NOT to do...; and then post relevant lines here.
According to the facts presented until know it may have been better to ask Radio Eriwan
Regards
Clemens

How to create bdc for fbs1 using both call transaction and session

Hi Friends,
i have one problem with tcode FBS1, i need to create a bdc program for both call transaction and session method using subroutine.
first call transaction needs to execute if there is an error sesion has to execute. if u have code please forward.
thanks in advance.
chandramouli pothugunta

where as in call transaction we can do error handling explictly.those errors are stored in one file .this file will send to the error log(session method),i.e session log.
in the above case we use both call transaction n session method at time in one program.sample code is below ,go through it .
data : begin of itxk01 occurs 0,
end of itxk01.
data : bdcdata like itbdcdata occurs 0 with header line.
data : itbdcmsgcoll like itbdcmsgcoll occurs 0 with header line,
itxk01 like itxk01-dup occurs 0 with header line.
call gui-upload.
loop at itxk01.
refresh itxk01.
perform bdc-dynpr0 using 'prg' 'scr'
perform bdc-dynfld using fnam fval
call transaction 'xk01' using bdcdata mode 'a' update 's' messages into itbdcmsgcoll.
if sy-subrc ne 0.
append itxk01 into itxk01-dup.
endif.
endloop.
if not itxk01-dup[] is initial.
refresh itck01.
call bdc_open_group
itxk01 = itxk01-dup.
loop at itxk01.
refresh itxk01.
perform bdc-dynpr0 using 'prg' 'scr'
perform bdc-dynfld using fnam fval
call bdc-insert.
endloop.
call bdc-close-group.
form bdc-dynpr0 using pr sc
endform .
form bdc-field using fnam faval
endform.
this will help u.
reward points for me
kiran

How to call a SM35 transaction and run in BDC report.

Hi Experts,
I knew that how to call a transaction but here, I've to call the SM35 transaction ,which have my BRS BDC recording, to run my session.
Pls help me how to call the transaction and run/process the first session tab in the table control of SM35 window.
thanks & regards
sankar.

Hi,
Look up this example..here v have recorded one transaction & running it throough BDC report programming.
report ZBDC_16JUL2008
       no standard page heading line-size 255.
include bdcrecx1.
DATA : BEGIN OF it_tab OCCURS 0,
         LIFNR(016),
         BUKRS(004),
         KTOKK(004),
         NAME1(035),
         SORTL(010),
         STRAS(035),
         PFACH(010),
         ORT01(035),
         LAND1(003),
         REGIO(003),
         SPRAS(002),
         TELF1(016),
         AKONT(010),
         FDGRV(010),
       END OF it_tab.
start-of-selection.
CALL FUNCTION 'UPLOAD'
EXPORTING
CODEPAGE                      = ' '
   FILENAME                      = 'D:\'
   FILETYPE                      = 'ASC'
ITEM                          = ' '
FILEMASK_MASK                 = ' '
FILEMASK_TEXT                 = ' '
FILETYPE_NO_CHANGE            = ' '
FILEMASK_ALL                  = ' '
FILETYPE_NO_SHOW              = ' '
LINE_EXIT                     = ' '
USER_FORM                     = ' '
USER_PROG                     = ' '
SILENT                        = 'S'
IMPORTING
FILESIZE                      =
CANCEL                        =
ACT_FILENAME                  =
ACT_FILETYPE                  =
TABLES
    data_tab                      = it_tab
EXCEPTIONS
   CONVERSION_ERROR              = 1
   INVALID_TABLE_WIDTH           = 2
   INVALID_TYPE                  = 3
   NO_BATCH                      = 4
   UNKNOWN_ERROR                 = 5
   GUI_REFUSE_FILETRANSFER       = 6
   OTHERS                        = 7
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
perform open_group.
LOOP at it_tab.
perform bdc_dynpro      using 'SAPMF02K' '0105'.
perform bdc_field       using 'BDC_CURSOR'
                              'RF02K-KTOKK'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'RF02K-LIFNR'
                              it_tab-LIFNR.
perform bdc_field       using 'RF02K-BUKRS'
                              it_tab-BUKRS.
perform bdc_field       using 'RF02K-KTOKK'
                              it_tab-KTOKK.
perform bdc_dynpro      using 'SAPMF02K' '0110'.
perform bdc_field       using 'BDC_CURSOR'
                              'LFA1-TELF1'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'LFA1-NAME1'
                              it_tab-NAME1.
perform bdc_field       using 'LFA1-SORTL'
                              it_tab-SORTL.
perform bdc_field       using 'LFA1-STRAS'
                              it_tab-STRAS.
perform bdc_field       using 'LFA1-PFACH'
                              it_tab-PFACH.
perform bdc_field       using 'LFA1-ORT01'
                              it_tab-ORT01.
perform bdc_field       using 'LFA1-LAND1'
                              it_tab-LAND1.
perform bdc_field       using 'LFA1-REGIO'
                              it_tab-REGIO.
perform bdc_field       using 'LFA1-SPRAS'
                              it_tab-SPRAS.
perform bdc_field       using 'LFA1-TELF1'
                              it_tab-TELF1.
perform bdc_dynpro      using 'SAPMF02K' '0120'.
perform bdc_field       using 'BDC_CURSOR'
                              'LFA1-VBUND'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_dynpro      using 'SAPMF02K' '0130'.
perform bdc_field       using 'BDC_CURSOR'
                              'LFBK-BANKS(01)'.
perform bdc_field       using 'BDC_OKCODE'
                              '=ENTR'.
perform bdc_dynpro      using 'SAPMF02K' '0210'.
perform bdc_field       using 'BDC_CURSOR'
                              'LFB1-FDGRV'.
perform bdc_field       using 'BDC_OKCODE'
                              '=UPDA'.
perform bdc_field       using 'LFB1-AKONT'
                              it_tab-AKONT.
perform bdc_transaction using 'FK01'.
ENDLOOP.
perform close_group.

Doubt in uploading using call transaction method

hi all
i am uploading f-29 in call transaction method .. i have a problem in currency field, the currency field is not picking up it shows a error that input field is longer than screen field .. i have declared currency field as type BSEG-WRBTR(same as screen field ...how to go about
thanks
lokesh

Hi,
When you use the database value directly in your BDC, you will have this issue. It is always advisable to use character fields when doing BDC. so change it to charecter field and try it..
Regards
Sudheer

Type of error in the log file while using using call transaction mode u2018Eu2019

Hi Gurus,
Please Answer for this qusetion urgently
what type of error exactly you will be seeing in the log file while using call transaction mode u2018Eu2019?
Thanks/
Radha.

Hi,
Can you be clear.
In call transaction , no error logs are created, you have to handle the errors explicitly using the structure BDCMSGCOLL.
Whenever you use E mode then if the transaction encounters any of the errors i.e. data type mismatching or invalid values etc, it will stop at that screen.
You can handle the errors in call transaction in the following method.
create a table using the structure BDCMSGCOLL.
then
loop at ......
      CALL TRANSACTION 'XK01' USING I_BDCDATA MODE 'N' UPDATE 'S' MESSAGES INTO I_MESGTAB.
endloop.
SORT I_MESGTAB BY MSGID MSGV1 ASCENDING.
DELETE ADJACENT DUPLICATES FROM I_MESGTAB.
LOOP AT I_MESGTAB.
    CALL FUNCTION 'FORMAT_MESSAGE'
      EXPORTING
        ID   = I_MESGTAB-MSGID
        LANG = I_MESGTAB-MSGSPRA
        NO   = I_MESGTAB-MSGNR
        V1   = I_MESGTAB-MSGV1
        V2   = I_MESGTAB-MSGV2
        V3   = I_MESGTAB-MSGV3
        V4   = I_MESGTAB-MSGV4
      IMPORTING
        MSG = MESG1.
    IF I_MESGTAB-MSGTYP = 'S' .
      WA_SUCCMESG-MESG = MESG1.
      APPEND WA_SUCCMESG TO I_SUCCMESG.
else     IF I_MESGTAB-MSGTYP = 'E' .
      WA_ERRMESG-MESG = MESG1.
      APPEND WA_ERRMESG TO I_ERRMESG.
    ENDIF.
ENDLOOP.
Hope this is clear.
Thanks and Regards.

While uploading data into the r/3 using call transaction or session method

hi experts
while uploading data into the r/3 using call transaction or session method error occured in the middle of the processing then how these methods behaves it transfers next records or not?

hai
Session method: The records are not added to the database until the session is processed. sy-subrc is not returned. Error logs are created for error records. Updation in database table is always Synchronous.
Call Transaction method: The records are immediately added to the database table. sy-subrc is returned to 0 if successful. Error logs are not created and hence the errors need to be handled explicitly. Updation in database table is either Synchronous or Asynchronous.
While to transfer the data from the through if any errors occurs until the errors are the complete the data is not transfer to the SAP system.
the system compulsory shows the errors. that errors are stored into the error logs (Transaction is SM35).
so the session method should not return any value.
In call transaction method data is directly pass to the SAP system.
So its compulsory return the value.
Because of the call transaction is the function.
A function should return the value mandatory
In session method errors stroed in SYSTEM GENRATED ERROR LOG.
IN CALL TRANSACTION TO CAPTURE THE ERRORS WE SHOULD PERFORM THE FOLLOWING.
FIRST ME MUST DECLARE AN INTERNAL TABLE WITH THE STRUCTURE OF BDCMSGCOLL TABLE.
THEN WHILE WRITING THE CALL TRANSACTION STATEMENT WE SHOULD PUT THE 'E' MODE FOR CAPTURING ALL THE ERRORS.
THEN FINALLY THE CAPTURED ERRORS MUST TO SENT TO THE INTERNAL TABLE WHICH WE DECLARED IN THE BEGINNING WITH BDCMSGCOLL BY USING THE FUNCTION MODULE "FORMAT_MESSAGE"
AND THUS THE ERROR MESSAGES WILL BE SENT TO THE INTERNAL TABLE WHICH WE DECLARED AT THE BEGINNING.

Uploading XL file using call Transaction and running in back ground

Similar Messages

Maybe you are looking for