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

Similar Messages

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

Issue with using call transaction CJ9F and F.M BAPI_PROJECT_MAINTAIN

Hello All,
In my custom program for a given project in selection screen we are getting all the related data as shown in CJ20N, in this screen I first created the WBS element and during save we used F.M BAPI_PROJECT_MAINTAIN to update the data, and next called transaction CJ9F to update BLC, after this we are comming back to selection screen 1000.
Now from selection screen if i enter again into that project details screen and try to create a new WBS it is showing below information msg.
Changing the contents of the field is not permitted
Message no. CJ727
If i remove the call transaction CJ9F part during save i am not getting the above error msg.
I think i am getting this error when we call the function module BAPI_PROJECT_MAINTAIN twice in the program.
Please help me to resolve this issue, as this msg is not allowing to save or create anything.
But i found that if i come totally out of my custom transaction and enter once again into that Z transaction it is working fine with out that message
Please help me to resolve this issue.

Hi,
Not sure, but if it is possible, complete your project update using the custom transaction and do the CJ9F afterwards seperately.
Regards
Sreekanth

Call transaction MMBE from another program and press Back button

Hello,
I have program that is used as a 'launch pad' for some of our heavily used transactions. When I call the main 'launch pad' program, the user will select a button and a Call Transaction MMBE is initiated (USING the first screen). The user selects a material for display and presses the execute button (F8). The material overview is displayed correctly. When the user presses the Back button (F12), transaction returns all the way back to the first called program and not to the first screen for transaction MMBE as expected.
Does anyone know how I can change the screen flow and go back to the fist screen of MMBE and not the screen of the first called program?
Regards,
RC

Rod,
In your case i think it is not possible as it is standard functionality by SAP.
Try work around, may be modification to the program will work.
Regards,
Amey

How many reocrds update in call transaction method and session method

The flat file having the 10 records but the flat file having the 5 th record is error so in session method how many records will update and in call transaction how many records will update.
can you provide with detailed information like in synchrnous mode and asynchronous mode
Regards
reddy

hi,
session method :up to 4 records will be updated as it is in synchronus mode.
Call transaction method : except 5 th all 9 records will be updated as it is assyncronous method.
Regards
sandeep Reddy

Calling transaction FB50

HI
I want to call transaction each time with a different Document Type is it posible?
i tried to set parameter id 'BAR' field 'SS' and than call transaction 'FB50'
or
doing batch input , but it didnt work! , when i used call transaction i got document typa SA and when i used batch inpt i got errors in screen
what can i do?
thanks

Use FB01 or the accounting doc BAPI. The 'SA' value is the system default. You can configure a different document type default by company code and account type in the IMG, but 'SA' will always be the default if no alternate config is specified. You should not use Enjoy transactions for transaction calls anyway...

BAPI AND BDC

How is BAPI different from call transaction or session

BAPI is a SAP-supplied function module with a defined interface, which allows you to interact with various business objects. SAP guarantees the integrity of your database for anything updated using a BAPI.
BAPI enables SAP and third party applications to interact and integrate with each other at the Business Object / Process level.
Check this link to know more about BAPI.
http://www.sapgenie.com/abap/bapi/example.htm
http://sappoint.com/abap/
BDC is a method of driving screens programatically, for updating SAP data.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.
It can also be used for real-time interfaces and custom error handling & logging features. .
To know more about BDC,check the link.
http://sappoint.com/abap/
BAPI V/S BDC:
SAP comes up with Change in Version, so each and every time they will change the screens/number etc.
so you have to change your BDC programs accordingly.
and also Most of the Latest versions transactions are Enjoy Transaction. They will not support BDC's in Background.
But Using BAPI's No such disadvantages.

CALL TRANSACTION 'ME33K from another program

Hi,
I ma trying to CALL TRANSACTION 'ME33K from another program, but it is not working. The transactions is opening, but it is not opening with the contract number (ls_ekpo-ebeln) i am passing.
ls_ekpo-ebeln does have a valued when CALL TRANSACTION 'ME33K is called.
In debug, I noticed the "value" is blank when step into CALL TRANSACTION 'ME33K .
   WHEN 'EBELN'. "Contract
      l_field = 'EVRTN'.
     IF ls_ekpo-ebeln <> ''.
        GET PARAMETER ID 'VRT' FIELD l_field. "EVRTN.
       SET PARAMETER ID 'VRT' FIELD ls_ekpo-ebeln.
       CALL TRANSACTION 'ME33K AND SKIP FIRST SCREEN.
        SET PARAMETER ID 'VRT' FIELD ls_ekpo-ebeln.
      ENDIF.
Any help or suggestions would be great.
Thanks,
Naing

Dear Naing,
I execute the same code
IF ls_ekpo IS INITIAL.
GET PARAMETER ID 'VRT' FIELD LS_EKPO.
SET PARAMETER ID 'VRT' FIELD ls_ekpo.
CALL TRANSACTION 'ME33K' AND SKIP FIRST SCREEN.
SET PARAMETER ID 'VRT' FIELD ls_ekpo.
ENDIF.
And it is working.
Try to do de simple sintax.
A program with one pararmeter to introduce the contract number.
The set parameter for this parameter and the call transaction.
I´m waiting your comments.
Regards.
Antonio.

Call transaction SM30..

Hi
My requirement is when user clicks on Pushbutton.
it should directly navigate to inside SM30 in Maintain mode.
what i know is to use the Set parameter id and use
call transaction 'SM30' . -> which will take to SM30
but how can i make directly to inside of SM30 with maintain mode.
It that possible or not??

Yes. instead of BDC we should use the FM which is suggested by Vijay :).
you can find code for BDC below. In this code you need to just replace VIEWNAME to your viewname.
DATA: bdcdata_wa TYPE bdcdata,
bdcdata_tab TYPE TABLE OF bdcdata.
DATA opt TYPE ctu_params.
CLEAR bdcdata_wa.
bdcdata_wa-program = 'SAPMSVMA'.
bdcdata_wa-dynpro = '0100'.
bdcdata_wa-dynbegin = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
perform bdc_field       using 'BDC_CURSOR'
                              'VIEWNAME'.
perform bdc_field       using 'BDC_OKCODE'
                              '=UPD'.
perform bdc_field       using 'VIEWNAME'
                              'ZVXX_CM_TP'.
opt-dismode = 'E'.
opt-defsize = 'X'.
opt-UPDMODE = 'S'.
CALL TRANSACTION 'SM30' USING bdcdata_tab OPTIONS FROM opt.
       Insert field                                                  *
FORM BDC_FIELD USING FNAM FVAL.
    CLEAR bdcdata_wa.
    bdcdata_wa-FNAM = FNAM.
    bdcdata_wa-FVAL = FVAL.
    APPEND bdcdata_wa TO bdcdata_tab.
ENDFORM.

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.

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

Function (or BAPI, ...) to skip calls and release calls in maintenance plan

Hi, gurus!
We need to find a function (or BAPI, ...) in order to skip a call number in a maintenance plan.
We need a function (or BAPI, ...) to release a call in a maintenance plan, too.
We could use a call-transaction to IP10, but we guess there could be problems with scroll and with pop-up warning messages.
We also thought about using IP30 but there's a problem: if there are previous calls that are not skipped, transaction IP30 releases all those previous calls and we need to skipped them.
Thanks in advance. We really appreciate your help.
Best regards,
J Madariaga

You cannot skip a call in the middle of a list of active calls - this is standard functionality.
Can you please give more info as to why you would want to do this?
PeteA

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.

Call transaction , and session method in the same program

hi experts,
Can anybody tell me in which cases we will use both call transaction and session methods in same program
if possible send me example code.
Regards
Trinadh

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.

Why we cannot commit inside BAPI and what if we call workflow inside BAPI?

hi,
can anyone tell me why we cannot use Commit statement inside BAPI ?
Also what if in my BAPI ,i have triggered my workflow and through that can i commit??
Regards,
Mayank

Hi,
it is a part of the BAPI programming model that BAPIs use a certain transaction model. This transaction model says that one BAPI has to follow the so called ACID (atomar, consistent, isolated, durable) principle. To ensure that a BAPI is atomar you cannot put a commit work just anywhere in mid of a BAPI as this would violate the modell. Furthermore BAPIs shall allow external commit handling that means it has to be possible to include several BAPI calls in one LUW. For this there are BAPIs which are only for committing or rolling back a transaction. For more detailed information you can check as usual the SAP help [click me|http://help.sap.com/saphelp_nw04/helpdata/EN/a5/3ec8654ac011d1894e0000e829fbbd/frameset.htm]
If would suppose that when you throw a workflow event it is triggered once the LUW is closed. At least SAP should work that way. But I have to admit in newer ABAP OO developments SAP often just calls the Event raising function module with the option to not wait for the DB commit. Seems there are some problems with the newer LUW concepts / OO and the old workflow technology. This can lead in worst case to events raised for objects which were rolled back later but SAP seems to accept that so it is in my oppinion an acceptable solution.
Hope that helps a bit
Roman

D/W BAPI and sesssion ,call transaction

Similar Messages

Maybe you are looking for