wht is the diff between IDOC and BAPI

[Former Member]

hi,

can u tell me wht is the diff between IDOC AND BAPI?

when i need to use bapis?

when i need to use idocs?

i am using bapi_salesorder_createfromdat2 for creating salesorder, is there any idoc for creating salesorder, if is there , wht is the diff between using them?

regards

Guru

[anversha_s]

hi,

<i>IDOC</i> is a intermediate document to exchange data between two SAP Systems.

*IDocs are structured ASCII files (or a virtual equivalent).

*Electronic Interchange Document

*They are the file format used by SAP R/3 to exchange data with foreign systems.

*Data Is transmitted in ASCII format, i.e. human readable form

*IDocs exchange messages

*IDocs are used like classical interface files

IDOC types are templates for specific message types depending on what is the business document, you want to exchange.

WE30 - you can create a IDOC type.

An IDOC with data, will have to be triggered by the application that is trying to send out the data.

FOr testing you can use WE19.

how to create idoc?

*WE30 - you can create a IDOC type

For more information in details on the same along with the examples can be viewed on:

http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404

http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm

http://www.sappoint.com/presentation.html

http://www.allsaplinks.com/idoc_search.html

http://www.sapgenie.com/sapedi/idoc_abap.htm

<b><i>BAPI</i></b>

BAPI stands for Business API(Application Program Interface).

A BAPI is remotely enabled function module

ie it can be invoked from remote programs like standalone JAVA programs, web interface etc..

You can make your function module remotely enabled in attributes of Function module but

A BAPI are standard SAP function modules provided by SAP for remote access.

Also they are part of Businees Objest Repository(BOR).

BAPI are RFC enabled function modules. the difference between RFc and BAPI are business objects.

You create business objects and those are then registered in your BOR (Business Object Repository)

which can be accessed outside the SAP system by using some other applications (Non-SAP) such as VB or JAVA.

In this case u only specify the business object and its method from external system

in BAPI there is no direct system call. while RFC are direct system call.

Some BAPIs provide basic functions and can be used for most SAP business object types.

These BAPIs should be implemented the same for all business object types.

Standardized BAPIs are easier to use and prevent users having to deal with a number of different BAPIs.

Whenever possible, a standardized BAPI must be used in preference to an individual BAPI.

http://help.sap.com/saphelp_46c/helpdata/en/9b/417f07ee2211d1ad14080009b0fb56/frameset.htm

http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html

Checkout !!

http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html

http://techrepublic.com.com/5100-6329-1051160.html#

http://www.sap-img.com/bapi.htm

http://www.sap-img.com/abap/bapi-conventions.htm

http://www.sappoint.com/abap/bapiintro.pdf

http://www.sapgenie.com/abap/bapi/example.htm

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

rgds

Anver

[Former Member]

Hai,

Can I call IDOCs from BizTalk Sever...or ..XI..?

Thanks & Regards,

Sri Krishna Charan

[Former Member]

Helo Guru,

Yes! You can use the Biztalk SAP Adapter to communicates with R3 using RFCs (including BAPIs) and IDOCs. I'll put some information from Biztalk documentation following. If you need further information please don't hesitate do ask for. My email is inside my Profile.

How the Adapter Communicates Using RFCs and IDoc: SAP Connector for Microsoft .NET

The Adapter uses the SAP Connector for Microsoft .NET to bridge Microsoft .NET applications and SAP. The SAP Connector for Microsoft .NET also enables the Adapter to communicate with SAP using BAPIs, RFCs and IDocs.

Connections through the SAP Connector can be made using NTLM/Kerberos or single sign-on (SSO) tickets. However, the SAP Adapter implementation provides BizTalk Authentication using SSO or by specifying a valid SAP user name and password combination.

Encryption and decryption is supported using certificates at the send and receive handler level. The connection between the client and the server is over an RFC connection that uses Encapsulating Security Payload (ESP).

HTTPS and SNC support is not required or provided by the adaptor because SOAP or Web connections to SAP are not used.

How the Adapter Generates Schemas and Exchanges Messages: SAP Connector for Microsoft .NET

The Adapter uses the SAP Connector for Microsoft .NET to generate schemas at design time and to exchange messages at run time. The SAP Connector for Microsoft .NET in general enables Microsoft .NET applications to communicate with a SAP system.

The Adapter only requires the run-time installation of the SAP Connector for Microsoft .NET. At a minimum, you can use version 1.0.3 which is available for download from SAP's Service Marketplace.

Typically the version of the SAP Connector for Microsoft .NET is tied to the SAP WebAS (Web Application Server). For example, the SAP Connector for Microsoft .NET 1.x is tied to the SAP WebAS 6.20, and the SAP Connector for Microsoft .NET 2.x is tied to the SAP WebAS 6.40.

As the design-time functionality is provided directly via the Adapter within Microsoft Visual Studio® 2005, one is not required to install the SAP Connector for Microsoft .NET design-time functionality.

Rgs,

Gustavo Kauffman