Call transaction Vs BAPI

why we go for BAPI instead of call transaction ?

Hi,
BAPI is a higher end usage for tranfering the data from SAP to non-SAP and vice-versa. for ex: if we are using VB application,where in that we want to connect to SAP and retireve the data,and then change and update the data in SAP for that purpose we can use that.Apart from that, we can also use it for
Uploading/Downloading the data from SAP to Non-SAP like call transaction, provided we have an existing BAPI for that.BAPI function modules will also do all the checks required for data integrity like Transactions for call transaction.
There is one more advantage using BAPI instead of call transaction. When we go for upgradation, there might be pozzibility to change the screen elements for transactions depending on the requirement. In that case,our call transaction pgm may or may not work (depending on the screen changes they have made). Unless and until we prepare new call transaction we cant use the old call transaction pgm. But in BAPI, SAP promises that they are going to keep the old BAPI and for new functionality they will provide an upgraded BAPI. Until we write a new BAPI pgm, we can use the exisitng BAPI pgm.
********please reward points if the information is helpful to you**********

Similar Messages

Can i use call transaction in BAPI

Can I use call transaction in a BAPI and create master record.

There is no reason AS LONG AS this BAPI will not accessed from an external system. BAPIs are intended to accessed by external systems... otherwise, creating a Func Module is just fine.
I would be cautious with using BDCs. SAP continually changes screens with each upgrade. When you use BDCs, you are TOTALLY dependent on those screen fields. And when an upgrade changes a screen, you have extra work to do to fix your BDC in the new version.
By using a BAPI or a Func Mod, your impact from an upgrade is greatly reduced.
Remember to reward points accordingly.
Message was edited by: John Jakabcsin
Message was edited by: John Jakabcsin

Call bdc or call transaction in bapi

Hi,
i create MAM sales order using bapi BAPI_ADMGMTSO_CREATEFROMDATA .
But i want create genral business partner using t-code bug1 for that i use bdc.
how i should call that bdc in above bapi.
Please anybody suggest solution for this?

Hi,
I don't find BAPI_ADMGMTSO_CREATEFROMDATA, but what you can do is create a customize ZBAPI_ADMGMTSO_CREATEFROMDATA and made a call function to BAPI_ADMGMTSO_CREATEFROMDATA and after commit you put your bdc code.

Unlocking Call Transaction

I am doing a call transaction (no bapi for modifying vendors in 4.6C) and I keep getting an error that I have the vendor locked when I try to do the next transaction (I am doing purchasing vendors and then financial vendors). I added a 'commit work and wait' statement but it doesn't seem to always help. Any suggestions?
Thanks,
Lisa

Hello Lisa,
I think that is the wrong forum for your question. Post it in the ABAP Programming Forum (ABAP Development) and you would have more response.
Regards
Gregor
Message was edited by: Mark Finnern
Hi Gregor,
I moved the post and thanks for keeping an eye on things like that, Mark.

Call Transaction (BAPI) in ABAP Web Dynpro

I'm developing a ABAP WD application which make use of a RFC BAPI. The BAPI will then use call transaction to perform certain operation on R3.
<b>CALL TRANSACTION 'IQS12' USING bdcdata MODE 'P'
MESSAGES INTO itab.</b>
It works fine when I tested it using TCode SE37. When the call transaction fails all error message is trapped inside the internal table.
However when I run it using ABAP WD, it does not return the internal table but an error page on the portal. The error message was displayed on the portal page. I would like to handle the error message by my own. Is there any way doing this?
Appreciate if anyone can sort this out for me. Thanks in advance.
Ricky

Hi,
It's okie now. I have found out that this is a known issue and there's a SAP notes (935725) for that.
According to the notes, call transaction with message type E will fail if the BAPI is executed through http.
Thanks for replying. Appreciate that.
Ricky

How bapi different from session and call transaction?

how bapi different from session and call transaction?
thanks in advance.

For one, Batch Data Communication (BDC) is older. Business Application Programming Interface (BAPI) came later, about 10 years ago (you can see this already from the name, which contains marketese like "business" ).
More important though, they are different technologies. With BDC you build the "batch input transaction" yourself, with an ABAP program which creates the "batch input session" ("Batch-Input-Mappe" in german). You then take that session, like an object, and "run" it on a system (most of the time, this is done on a local system by the administrators, after it has been tested for correctness).
With BAPI, a system (local or remote) exposes its interface to you through some kind of Remote Function Call (RFC). Practically, it tells you: "What do you want to do? Insert that data into Materials Management? Here is the function and the the parameters you have to use for each record". You only work with the Interface - the exposed function. How this function works does not have to interest you. You don't have sessions to "run", you fire your function calls filled with data, one after another and you're done.
BAPI can be run remotely. With BDC, you probably have to call the administrators of the remote system and send them the session you created for them to run. With BDC you go through the whole transaction in one BDC session, with BAPI you may need more than one "BAPI calls" to do this.
With BAPI you don't fill obcure field names with values, you just fill the parameters. You can use a BAPI from inside your ABAP program to let a "business object" do some clearly defined work for you, then you can continue with your code doing other things. You don't do this with BDC. With BDC you write a dedicated program that creates the "session", which is then executed separately.
Batch Data Communication (BDC) is the oldest batch interfacing technique that SAP provided since the early versions of R/3. BDC is not a
typical integration tool, in the sense that, it can be only be used for uploading data into R/3 and so it is not bi-directional.
BDC works on the principle of simulating user input for transactional screen, via an ABAP program. Typically the input comes in the form of a flat file. The ABAP program reads this file and formats the input data screen by screen into an internal table (BDCDATA). The transaction is then started using this internal table as the input and executed in the background.
In Call Transaction, the transactions are triggered at the time of processing itself and so the ABAP program must do the error handling.
It can also be used for real-time interfaces and custom error handling & logging features. Whereas in Batch Input Sessions, the ABAP
program creates a session with all the transactional data, and this session can be viewed, scheduled and processed (using Transaction SM35) at a later time. The latter technique has a built-in error processing mechanism too.
Batch Input (BI) programs still use the classical BDC approach but doesnt require an ABAP program to be written to format the
BDCDATA. The user has to format the data using predefined structures and store it in a flat file. The BI program then reads this and
invokes the transaction mentioned in the header record of the file.
Direct Input (DI) programs work exactly similar to BI programs. But the only difference is, instead of processing screens they validate
fields and directly load the data into tables using standard function modules. For this reason, DI programs are much faster (RMDATIND - Material Master DI program works at least 5 times faster) than the BDC counterpart and so ideally suited for loading large volume data. DI programs are
not available for all application areas.
Business Add-In (BADI) are a new SAP enhancement technique based on ABAP Objects.
They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.
As with customer exits two different views are available:
In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object.
In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if one is available.
In contrast to customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions), but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created at each level within such a system infrastructure.

Changing Service Entry Sheet - Call Transaction / BAPI / etc

Dear all,
I need to create a program in order to change data in service entry sheets services or/and delete services. I wanted to use a BAPI but I can not find one for changing data (only for creating). Trying to use call transaction for transaction ML81N has been nearly impossible due to positioning issues. (It is an Enjoy transaction and acts differently when in batch input mode). The old transaction ML81 also has this positioning problem.
Has anybody ever done this and has any tips?
Regards

Hi,
The below BAPI's are avilable for transaction ML81N
BAPI_ENTRYSHEET_CHECK Check Service Entry Sheet
BAPI_ENTRYSHEET_CREATE Create Entry Sheet
BAPI_ENTRYSHEET_DELETE Delete Entry Sheet
BAPI_ENTRYSHEET_GETDETAIL Display Detailed Data on Entry Sheet
BAPI_ENTRYSHEET_GETLIST List Entry Sheets
BAPI_ENTRYSHEET_GETRELINFO Detailed Release Information Relating to Entry Sheet
BAPI_ENTRYSHEET_RELEASE Release Entry Sheet
BAPI_ENTRYSHEET_RESET_RELEASE Cancel Release of Entry Sheets
Regards
Sudheer

ORDER05 (call transaction) or SALESORDER_CREATEFROMDAT2 (using BAPI)

Hello all,
Should we use ORDER05 or SALESORDER_CREATEFROMDAT2 to place sales orders in SAP?
I know ORDERS05 is using call transaction to create it an the other one is using a BAPI.
One was released for version 46C and the other one from 620
It seems as we need to use the second one but I'm not sure the functionality or what is the purpose for this last message type.
My disconcert is just because I was expecting ORDERS06 for new versions...
Thanks in advance.
Jorge Rosa.
Edited by: Jorge Rosa on Feb 8, 2012 2:46 PM

Hello Jorge,
May be thread in the SD foruns would help you more than database:
http://forums.sdn.sap.com/forum.jspa?forumID=246&start=0
http://forums.sdn.sap.com/forum.jspa?forumID=328&start=0
Regards,
Eduardo Rezende

D/W BAPI and sesssion ,call transaction

Hi ,
can any one help me in finding difference from BAPI and call transaction ,session method .
If you can provide any URL that can be vary useful .
Thank u,
Mahendra.

Hi Mahendra,
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
BAPI stands for Business API(Application Program Interface).
Please check these links which will give you step by step for learning BAPI.
http://www.erpgenie.com/sap/abap/bapi/example.htm
http://www.sap-img.com/bapi.htm
http://help.sap.com/saphelp_nw04/helpdata/en/e0/9eb2370f9cbe68e10000009b38f8cf/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/43/b46c1e53c111d395fa00a0c94260a5/content.htm
http://www.sappoint.com/abap/bapiintro.pdf#search=%22BAPI(SAP)%22
http://www.erpgenie.com/sap/abap/bapi/index.htm
http://www.erpgenie.com/sap/abap/bapi/conventions.htm
http://www.erpgenie.com/sapgenie/docs/BAPI%20Programming.doc
http://64.233.167.104/custom?q=cache:eyMZ5qPOH-0J:www.erpgenie.com/sapgenie/docs/BAPI%2520Intro.doc+bapi&hl=en&ct=clnk&cd=6&ie=UTF-8&client=pub-2723892367221695
http://64.233.167.104/custom?q=cache:c7cwsXMxq-UJ:www.sapdevelopment.co.uk/java/jco/bapi_jco.pdf+bapi&hl=en&ct=clnk&cd=1&ie=UTF-8&client=pub-6389415953938571
http://www.sapgenie.com/abap/bapi/example.htm
http://www.sappoint.com/abap/bapiintro.pdf
http://www.sappoint.com/abap/bapiprg.pdf
http://www.sappoint.com/abap/bapiactx.pdf
http://www.sappoint.com/abap/bapilst.pdf
http://www.sappoint.com/abap/bapiexer.pdf
http://service.sap.com/ale
http://service.sap.com/bapi
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf
http://www.planetsap.com/Bapi_main_page.htm
http://www.topxml.com/sap/sap_idoc_xml.asp
http://www.sapdevelopment.co.uk/
http://www.sapdevelopment.co.uk/java/jco/bapi_jco.pdf
List of all BAPIs
http://www.planetsap.com/LIST_ALL_BAPIs.htm

Improve performance of bdc call transaction

Hi all,
I am performing a batch update of tax codes in a BDC call transaction program. This particular code takes about 3 minutes to process 2,600 entries. I have tried almost everything but is there a way to improve / make it run faster?
I have a feeling it has something to do with the form "do_transaction", but I really don't know anymore.
Thank you in advance.
Attached is the code:
*& Report ZFI_CHANGEWTAX
*& Description: Change Doctors Withholding Tax Code (EI)
*& Using BDC Call Transaction Method
*& Created by : mpena
*& Created on : 07/15/2009
*& Modification History
*& Seq Changed on
*&       Changed by
*& 001   07/15/2009
*&        mpena         Initial Development
*& 002   07/20/2009
*&        mpena         Logic modification
*&                      Testing
*& 003   07/20/2009
*&        mpena         Call function parameter modification
*& 004   07/22/2009
*&        mpena         Report generation
*&                      Performance improvements
REPORT zfi_changewtax
       NO STANDARD PAGE HEADING
       MESSAGE-ID zfk02msg.
TYPES: BEGIN OF t_tax,
       lifnr LIKE lfa1-lifnr,                "account number
       wt_withcd LIKE lfbw-wt_withcd,        "current tax code
       wt_withcd_new LIKE lfbw-wt_withcd,    "new tax code (left blank at default)
       END OF t_tax.
DATA: wa_tax TYPE t_tax,
       i_tax TYPE STANDARD TABLE OF t_tax,
       it_bdcdata TYPE bdcdata OCCURS 0 WITH HEADER LINE,
       lin TYPE i.
-------Selection Screen Design -
SELECTION-SCREEN:
SKIP 1,
BEGIN OF BLOCK blk1 WITH FRAME TITLE aaa.
PARAMETERS: p_ktokk LIKE lfa1-ktokk DEFAULT 'DOCT' OBLIGATORY,
            p_bukrs LIKE lfbw-bukrs DEFAULT 'SL' OBLIGATORY,
            p_wtax LIKE lfbw-wt_withcd OBLIGATORY.
SELECTION-SCREEN END OF BLOCK blk1.
INITIALIZATION.
aaa = 'Change Tax Code to specified value'.
TOP-OF-PAGE.
WRITE:
/ 'Update of taxes successful on:', sy-datum, sy-uzeit,
/ 'Generated by:', sy-uname,
/ 'Company Code:', p_bukrs, 'Vendor Group:', p_ktokk.
SKIP 1.
ULINE.
WRITE:
/ 'Account Number', 20 'Old Withholding Tax Code', 50 'New Withholding Tax Code'.
ULINE.
START-OF-SELECTION.
SELECT lfa1~lifnr
         lfbw~wt_withcd
INTO TABLE i_tax
FROM lfa1 INNER JOIN lfbw
    ON lfa1lifnr = lfbwlifnr
    WHERE lfbw~bukrs EQ p_bukrs
    AND lfbw~witht EQ 'EI'.
IF sy-subrc EQ 0.
    DESCRIBE TABLE i_tax LINES lin.
ENDIF.
Update i_tax with new value of wt_witchd, then display for comparison.
After write: if old and new tax are the same, tax update was not successful for that specific account
or inputted tax type is the same as the old one.
LOOP AT i_tax INTO wa_tax.
    wa_tax-wt_withcd_new = p_wtax.
    MODIFY i_tax FROM wa_tax.
    WRITE:
    / wa_tax-lifnr,
    20 wa_tax-wt_withcd,
    50 wa_tax-wt_withcd_new.
    CLEAR wa_tax.
ENDLOOP.
PERFORM do_transaction USING p_bukrs p_wtax.
*&      Form do_transaction
     Extracted from ZFKO2 recording accessible in shdb.
FORM do_transaction USING v_bukrs v_wtax.
MESSAGE i000 WITH lin.
LOOP AT i_tax INTO wa_tax.
    REFRESH it_bdcdata.
    PERFORM bdc_dynpro      USING 'SAPMF02K' '0106'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'RF02K-D0610'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM bdc_field       USING 'RF02K-LIFNR'
                                  wa_tax-lifnr.
    PERFORM bdc_field       USING 'RF02K-BUKRS'
                                  v_bukrs.
    PERFORM bdc_field       USING 'RF02K-D0610'
                                  'X'.
    PERFORM bdc_dynpro      USING 'SAPMF02K' '0610'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'LFBW-WT_WITHCD(01)'.
    PERFORM bdc_field       USING 'LFB1-QLAND'
                                  'PH'.
    PERFORM bdc_field       USING 'LFBW-WT_WITHCD(01)'
                                  v_wtax.
    PERFORM bdc_dynpro      USING 'SAPMF02K' '0610'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=UPDA'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'LFB1-QLAND'.
    PERFORM bdc_field       USING 'LFB1-QLAND'
                                  'PH'.
    CALL TRANSACTION 'FK02' USING it_bdcdata
                            MODE   'N'
                            UPDATE 'A'.
ENDLOOP.
MESSAGE i001.
ENDFORM.                    "do_transaction
       form for bdc dynpro
FORM bdc_dynpro USING program
                      dynpro.
it_bdcdata-program = program.
it_bdcdata-dynpro = dynpro.
it_bdcdata-dynbegin = 'X'.
APPEND it_bdcdata.
CLEAR it_bdcdata.
ENDFORM.                    "bdc_dynpro
       form for bdc field
FORM bdc_field USING fnam
                      fval.
it_bdcdata-fnam = fnam.
it_bdcdata-fval = fval.
APPEND it_bdcdata.
CLEAR it_bdcdata.
ENDFORM.                    "bdc_field

You might want to try using a BAPI instead of a call transaction.   I believe "BAPI_VENDOR_SAVECHARVALREPLICA" will work for you. Calling a BAPI is just like calling a function module.   After you call the bapi remember to commit it with the function module "BAPI_TRANSACTION_COMMIT".

I want in LSMW SAME CODING. THIS IS USING BDC CALL TRANSACTION

REPORT ZXX_BDC_PRA NO STANDARD PAGE HEADING LINE-COUNT 20
                                            LINE-SIZE 150 .
Program Name :ZXX_BDC_PRA                             *
Object Id     :                                        *
Develper Name : praveen                                *
Start Date    : 25.06.07                               *
Description   : uploading flat file to sap system      *
*--structure for Data Uploading.
DATA: BEGIN OF IT_STR ,
        VKORG LIKE RF02D-VKORG,
        VTWEG LIKE RF02D-VTWEG,
        SPART LIKE RF02D-SPART,
        KTOKD LIKE RF02D-KTOKD,
        NAME1 LIKE KNA1-NAME1,
        SORTL LIKE KNA1-SORTL,
        ORT01 LIKE KNA1-ORT01,
        PSTLZ     LIKE KNA1-PSTLZ,
        LAND1 LIKE KNA1-LAND1,
        SPRAS LIKE KNA1-SPRAS,
        END OF IT_STR.
*--Internal Table for Data Uploading.
DATA: ITAB LIKE IT_STR OCCURS 0.
*--Internal Table to sucessfull Records.
DATA:   ITAB1 LIKE IT_STR OCCURS 0.
*--Internal Table to Store Error Records.
DATA:    ITAB2 LIKE STANDARD TABLE OF IT_STR WITH HEADER LINE.
*--Internal Table for Storing the BDC data.
DATA: BDCDATA LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
*--Internal Table for storing the messages.
DATA:   MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
DATA:   COUNT TYPE I VALUE 1,
        S VALUE 0, E VALUE 0.
Selection screen *
SELECTION-SCREEN BEGIN OF BLOCK b1
                 WITH FRAME TITLE TEXT-001.
PARAMETERS: P_FILE TYPE IBIPPARMS-PATH.
SELECTION-SCREEN END OF BLOCK B1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
*functionality to use drill down list
CALL FUNCTION 'F4_FILENAME'
    EXPORTING
      PROGRAM_NAME = SYST-CPROG
      DYNPRO_NUMBER = SYST-DYNNR
    IMPORTING
      FILE_NAME     = P_FILE.
Start-of-selection *
START-OF-SELECTION.
DATA FILENAME TYPE STRING.
FILENAME = P_FILE.
*-- Form to upload flatfile data into the internal table.
CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      FILENAME                = FILENAME
      FILETYPE                = 'ASC'
      HAS_FIELD_SEPARATOR     = 'X'
    TABLES
      DATA_TAB                = ITAB
    EXCEPTIONS
      FILE_OPEN_ERROR         = 1
      FILE_READ_ERROR         = 2
      NO_BATCH                = 3
      GUI_REFUSE_FILETRANSFER = 4
      INVALID_TYPE            = 5
      NO_AUTHORITY            = 6
      UNKNOWN_ERROR           = 7
      BAD_DATA_FORMAT         = 8
      HEADER_NOT_ALLOWED      = 9
      SEPARATOR_NOT_ALLOWED   = 10
      HEADER_TOO_LONG         = 11
      UNKNOWN_DP_ERROR        = 12
      ACCESS_DENIED           = 13
      DP_OUT_OF_MEMORY        = 14
      DISK_FULL               = 15
      DP_TIMEOUT              = 16
      OTHERS                  = 17.
*--Generating the BDC table for the fields of the internal table.
LOOP AT ITAB INTO IT_STR.
    PERFORM BDC_DYNPRO      USING 'SAPMF02D' '0107'.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                  'RF02D-KTOKD'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM BDC_FIELD       USING 'RF02D-VKORG'
                                  IT_STR-VKORG.
    PERFORM BDC_FIELD       USING 'RF02D-VTWEG'
                                   IT_STR-VTWEG.
    PERFORM BDC_FIELD       USING 'RF02D-SPART'
                                  IT_STR-SPART.
    PERFORM BDC_FIELD       USING 'RF02D-KTOKD'
                                    IT_STR-KTOKD.
    PERFORM BDC_DYNPRO      USING 'SAPMF02D' '0110'.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                  'KNA1-SPRAS'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM BDC_FIELD       USING 'KNA1-NAME1'
                                IT_STR-NAME1.
    PERFORM BDC_FIELD       USING 'KNA1-SORTL'
                                    IT_STR-SORTL.
    PERFORM BDC_FIELD       USING 'KNA1-ORT01'
                                    IT_STR-ORT01.
    PERFORM BDC_FIELD       USING 'KNA1-PSTLZ'
                                  IT_STR-PSTLZ.
    PERFORM BDC_FIELD       USING 'KNA1-LAND1'
                                  IT_STR-LAND1.
    PERFORM BDC_FIELD       USING 'KNA1-SPRAS'
                                    IT_STR-SPRAS.
    PERFORM BDC_DYNPRO      USING 'SAPMF02D' '0120'.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                  'KNA1-TXJCD'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM BDC_DYNPRO      USING 'SAPMF02D' '0125'.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                  'KNA1-NIELS'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM BDC_DYNPRO      USING 'SAPMF02D' '0360'.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                  'KNVK-NAMEV(01)'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                  '=ENTR'.
    PERFORM BDC_DYNPRO      USING 'SAPMF02D' '0310'.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                  'KNVV-BEGRU'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM BDC_DYNPRO      USING 'SAPMF02D' '0324'.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                  'KNVP-PARVW(01)'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                  '=ENTR'.
*--Calling the transaction 'Vd01'.
    CALL TRANSACTION 'VD01' USING BDCDATA MODE 'N' UPDATE 'S'
    MESSAGES INTO MESSTAB.
    PERFORM MESSAGES.
    REFRESH : BDCDATA, MESSTAB.
ENDLOOP.
END-OF-SELECTION.
*--Populating the Success records internal table.
IF ITAB1[] IS NOT INITIAL.
format color 5.
    WRITE: /'SUCCESSFUL RECORDS'.
    format color off.
    LOOP AT ITAB1 INTO IT_STR.
      WRITE:/ IT_STR-VKORG,IT_STR-VTWEG,
              IT_STR-SPART,IT_STR-KTOKD,
              IT_STR-NAME1,IT_STR-SORTL,
              IT_STR-ORT01,
              IT_STR-PSTLZ,
              IT_STR-LAND1,
              IT_STR-SPRAS.
      S = S + 1.
    ENDLOOP.
REFRESH : ITAB1.
    WRITE:/ 'TOTAL RECORDS',S.
ENDIF.
*--Populating the error records internal table.
IF ITAB2[] IS NOT INITIAL.
FORMAT COLOR 3.
    WRITE :/ 'ERRORS RECORDS ARE'.
FORMAT COLOR OFF.
    LOOP AT ITAB2.
      WRITE:/ ITAB2-VKORG,
              ITAB2-VTWEG,
              ITAB2-SPART,ITAB2-KTOKD,
              ITAB2-NAME1,ITAB2-SORTL,
              ITAB2-ORT01,
              ITAB2-PSTLZ,
              ITAB2-LAND1,
              ITAB2-SPRAS.
        E = E + 1.
    ENDLOOP.
REFRESH : ITAB2.
    WRITE: / 'TOTAL RECORDS',E.
REFRESH : ITAB2.
ENDIF.
End of Selection *
END-OF-SELECTION.
TOP-OF-PAGE *
TOP-OF-PAGE.
WRITE:/ SY-ULINE.
WRITE:/10 'REPORT ID',21 SY-REPID,35 'USERNAME',46 SY-UNAME,
60 'SYSTEM DATE',70 SY-DATUM,80 'SYSTEM TIME',90 SY-UZEIT,
100 'PAGE NO',108 SY-PAGNO.
WRITE:/ SY-ULINE.
FOrm to Populate the BDC table.
       Start new screen                                              *
FORM BDC_DYNPRO USING PROGRAM DYNPRO.
CLEAR BDCDATA.
BDCDATA-PROGRAM = PROGRAM.
BDCDATA-DYNPRO   = DYNPRO.
BDCDATA-DYNBEGIN = 'X'.
APPEND BDCDATA.
ENDFORM.                    "BDC_DYNPRO
       Insert field                                                  *
FORM BDC_FIELD USING FNAM FVAL.
IF FVAL <> SPACE.
    CLEAR BDCDATA.
    BDCDATA-FNAM = FNAM.
    BDCDATA-FVAL = FVAL.
    APPEND BDCDATA.
ENDIF.
ENDFORM.                    "BDC_FIELD
*&      Form messages
FORM MESSAGES .
LOOP AT MESSTAB.
    IF MESSTAB-MSGTYP = 'I'.
     WRITE : / MESSTAB-MSGV1.
    ELSEIF
MESSTAB-MSGTYP = 'S'.
      INSERT LINES OF ITAB FROM COUNT TO COUNT INTO TABLE ITAB1 .
      COUNT = COUNT + 1.
     WRITE : / MESSTAB-MSGV1.
    ELSEIF
    MESSTAB-MSGTYP = 'E'.
      INSERT LINES OF ITAB FROM COUNT TO COUNT INTO TABLE ITAB2.
      COUNT = COUNT + 1.
     WRITE : / MESSTAB-MSGV1.
    ENDIF.
ENDLOOP.
ENDFORM.                    " messages

Hi
Go through the doc and do the same using LSMW
BDC is the way to transfer data by writing a batch input program which can use either session or call transaction method.
LSMW used to transfer data without/less code.
What type of data we transfer using LSMW?
LSMW is best suited for transferring master data.
Actually BDC and LSMW are not comparable at all.
for example LSMW itself can use BDC as a way of mass data transfer.
BDC is a mass data transfer technique via screen logic of existing SAP Data entry transactions. It behaves as if you are manually making thousand of entires into sap system as a background job. And that is probably the reason why BAPI's are preffered over BDC's.
On the other hand LSMW is a tool to facilitate DATA migration from other legacy systems ... It contains step by step procedure for data migration.
Like Managing Data Migration Projects , Creating Source Structures , Mapping Source structures wid Target structures , etc etc
LSMW internally might well be using the following techniqes for data transfer..
1. IDOX
2. Direct Input / BDC
4. BAPI's
LSMW is an encapsulated data transfer tool. It can provide the same functionality as BDC infact much more but when coming to techinical perspective most the parameters are encapulated. To listout some of the differences :
LSMW is basicaly designed for a fuctional consultant who do not do much coding but need to explore the fuctionality while BDC is designed for a technical consultant.
LSMW offers different techinque for migrating data: Direct input ,BAPI,Idoc,Batch input recording. While bdc basically uses recording.
LSMW mapping is done by SAP while in BDC we have to do it explicitly .
LSMW is basically for standard SAP application while bdc basically for customized application.
Coding can be done flexibly in BDC when compared to LSMW
1. Maintain Attributes:
Here you have to choose the second option and you can do the recording how this should work. Then assign the same to the Batch Input Recording name.
2. Maintain Source structure:
Create a structure name
3. Maintain Source field:
In this you have to create a structure same as that of the input file
eg: name
age
4. Maintain structure relations:
This will link the structure to the input file.
5. Maintain field mapping and conversion rules:
Here is the place where you can do coding, depending upon the code you have written or assignment you have done the values will get picked up from the file and get processed.
6. Maintain field mapping and conversion rules:
If you have any fixed values you can define here.
7. Specify files:
Specify the input file path and type.
8. Assign files:
This will assign ur file to the Input file
9. Read Data:
This will read ur data from teh file.
10. Dispaly Read Data:
You can see the uploaded data
11. Convert Data
This will convert the data to the corresponding format for processing
12. Display Converted data:
13. Create batch input session
Here this will create a batch input session for processing
14. Run Batch Input session:
By clicking on the session and process the same you can do teh needfu.
http://www.sapbrain.com/TOOLS/LSMW/SAP_LSMW_steps_introduction.html
http://esnips.com/doc/8e732760-5548-44cc-a0bb-5982c9424f17/lsmw_sp.ppt
http://esnips.com/doc/f55fef40-fb82-4e89-9000-88316699c323/Data-Transfer-Using-LSMW.zip
http://esnips.com/doc/1cd73c19-4263-42a4-9d6f-ac5487b0ebcb/LSMW-with-Idocs.ppt
http://esnips.com/doc/ef04c89f-f3a2-473c-beee-6db5bb3dbb0e/LSMW-with-BAPI.ppt
http://esnips.com/doc/7582d072-6663-4388-803b-4b2b94d7f85e/LSMW.pdf
for Long texts Upload
Please take a look at this..
http://help.sap.com/saphelp_erp2005/helpdata/en/e1/c6d30210e6cf4eac7b054a73f8fb1d/frameset.htm
Reward points for useful Answers
Regards
Anji

RFC enabled function module using call transaction

Hi,
We have a scenario wherein we have a RFC enabled function module which inturn uses a call transaction to create a PM order & attaches the PM notification against it. Sometimes it so happens that the order does not get created for some reason or the other and there are no logs generated on the system to investigate. However we are capturing the messages produced via the BDCMSGCOLL. At present we are using the update parameter as 'L'.
In some scenarios it states that the notification is locked by the same notification and comes out without creating the order, in this process we are losing out on the order & the notification number which if successful would have got updated in the database.
I know this could be done via the BAPI, but there are innumerable steps within the BDC which can't be actually done using the BAPI and hence we could not use this procedure.
Is there any other way by which we can ensure that there's always a successful order creation, I mean without losing out on the order/notification number?. Would changing the update mode to 'S' help?. Since this process is time bound, it can't actually take more time then what its taking with the current logic.
Please let me know if you require further details on the same. Any help in this regard would be highly appreciated.
Regards,
Vidya

Sorry for an unclear replay.
In Simple terms; I have 2 scenarios;
Launch a new tab (IW38 tcode), on click of a button in SAP screen of custom transaction in NWBC.
Launch a new tab (IW38 tcode), on click of a button in a Non - SAP App opened (using URL) in NWBC.
For 1st case, i have used
CL_NWBC=>URL_CONSTRUCT
EXPORTING
     CANVAS_WDA__CLIENT_TYPE       = 'nwbc'
     CANVAS_TRANSACTION            = 'IW38'
RECEIVING
     URL                           = lv_URL.
CALL METHOD CL_NWBC=>URL_LAUNCH
   EXPORTING
     URL    = lv_url
But it gets open in NWBC HTML not in NWBC Desktop client.
I tried all the Parameters you have mentioned in your response to this post earlier, but nothing worked. the last one is CANVAS__WINDOW which actually hides the top area and few buttons but still it is a HTML version.
If i set the HTML_CLIENT = ABAP_FALSE, it launches a new window instead of the tab and asks for Login. If i login in can see the IW38 in NWBC desktop client. But the only problem is we have the restriction of single window/single login for users.
I am on NWBC PL12 and also updated the GUI 7.3 to PL8.
Simply the problem is URL_CONSTRUCT for any transaction is launching it in a new tab but in HTML Version.
For 2nd case,
It asks for the login details on click of a button on the 3rd party URL opened in NWBC. which means i am launching SAP from a 3rd party.
Is there any way to achieve the launch of new tab in this case instead of the new window ?
I hope its more clear now.
Regards,
Nik.

Is BDC's CALL TRANSACTION 'VA01' is not equals to ONLINE(manual) creation?

Hi Experts,
Ours is IS-Oil.
If the user do not enters/inputs OIC_MOT (Mode Of Transport) at ITEM level on the External Details popup, SAP will get it from Customar Master-KNA1 and populates on it, because its a mandatory field (OIC_MOT), but, do not throws an Error message and interupts the sales order creation process.
We have a inbound IDOC posting function module for sales order (VA01), which posts the sales oreders by using BDC (CALL TRANSACTION 'VA01') in the system. In this function module, we are not populating the OIC_MOT field contained segment by hoping SAP will populate/default it while it hits CALL TRANSACTION 'VA01' of my BDC of my FM of IB IDOC. But, SAP is not defaulting/populating and throwing error message (saying 'OIC_MOT field is a mandatory input field' data is missing) and IDOC is failing, pls. let me know Wht its so? is the BDC's CALL TRANSACTION 'VA01' is not equals to ONLINE (manual ) creation of sales order?
Thank you

Hi
Several transactions can ba a different behavior between online and bdc process, but if you simulate the trx by SM35 you should find out these gaps
I don't know OIL vertical, but the main transactions have a bapi can be used insted of BDC program (BAPI_SALESORDER_CREATEFROMDAT2, but perhaps there's a particular BAPI for OIL).
Max

Error 00-341 RAISE_EXCEPTION when using Call Transaction for VA01 in backgr

Hi,
I am getting this message when I use call transaction to create a sales order using VA01. Following is the statement I have used. Note that when i execute the program online, I am not getting any errors. I could create sales order without any problem. I am getting this exception only when I run in background.
      CALL TRANSACTION 'VA01'
                 USING BDC_TAB
                  MODE 'N'
                UPDATE 'S'
         MESSAGES INTO W_MESS_TAB.
When I captured message tab, I got following messages.
DC006 - Control Framework: Fatal error - GUI cannot be reached
00341 Runtime error RAISE_EXCEPTION has occurred.
Please help me in this regard.
Regards
Kasi

Some times execution of BDC program in back ground is different from the foreground. Some screens may appear in background and raise error while same will not when executed in foreground.
Double click the message in Session log to know more details.
One way is to suppress the screen while executing BDC.
Alternatively I suggest to use BAPI instead.
- Sanjay

Call transaction KB21N processed by a program in background mode

Hi to all,
I call transaction KB21N using BDCDATA in a custom program. If I process this program in foreground mode all it's OK, but if I process the program in background mode, I have a runtime error with DUMP: RAISE EXCEPTION with exception condition CNTL_ERROR. This program has to be executed in background so a bapi exist to use instead of call transaction or something else?
Thank you very much,
regards
Antonio

HI Antonio,
The transaction you are dealing with is an SAP Enjoy transaction and for such transactions it is not recommended to do a BDC. YOu should search for a BAPI for the same as you have already identified. Basically the enjoy transactions uses GUI controls which cannot be handled by BDC.
BAPI_ACC_ACTIVITY_ALLOC_POST may serve your purpose.
Regards,
ravi
Message was edited by:
Ravi Kanth Talagana

Call transaction Vs BAPI

Similar Messages

Maybe you are looking for