ALE/Idocs

[Former Member]

1. Where BAPI and Idocs are used?

2. ALE Comminication type (Syncronous / Asyncronous) ?

3. How will yoy include message control in ALE/EDI

[Former Member]

Hi,

SAP TO NON SAP COMMUNICATION WE NEED A API FUNCTION MODULE

SO WE WILL CREATE THE FUNCTION MODULE FOR NON SAP COMMUNICATION.

IDOCS ARE USED IN COMMUNICATION IN THE DISTRIBUTED SYSTEMS...

IF THERE IS A STRONG LINK IN THE DISTRIBUTED SYSTEM THEN WE WILL GO TO IDOCS...

ALE COMMUNICATION TYPE IS ASYNCRONOUS..

NO SPECIAL MESSAGE CONTROLS...

THROUGH IDOCS WE CAN PASS THE STRUCTURES IN THAT WE CAN PASS THE MESSAGES ONE SYSTEM TO ANOTHER SYSTEM...

THANK U

REWARD IF IT USE FUL

[Former Member]

hi

good

BAPI->

Definition

A Business Application Programming Interface (BAPI) is a precisely defined interface providing access to processes and data in business application systems such as R/3.

BAPIs of SAP Business Object Types

BAPIs are defined as API methods of SAP business object types. These business object types and their BAPIs are described and stored in the Business Object Repository (BOR). A BAPI is implemented as a function module, that is stored and described in the Function Builder.

BAPIs of SAP Interface Types

As of Release 4.5A BAPIs can also describe interfaces, implemented outside the R/3 System that can be called in external systems by R/3 Systems. These BAPIs are known as BAPIs used for outbound processing. The target system is determined for the BAPI call in the distribution model of Application Link Enabling (ALE).

BAPIs used for outbound processing are defined in the Business Object Repository (BOR) as API methods of SAP Interface Types. Functions implemented outside the R/3 System can be standardized and made available as BAPIs. For further information see BAPIs Used For Outbound Processing.

IDOCS->

Definition

A Business Application Programming Interface (BAPI) is a precisely defined interface providing access to processes and data in business application systems such as R/3.

BAPIs of SAP Business Object Types

BAPIs are defined as API methods of SAP business object types. These business object types and their BAPIs are described and stored in the Business Object Repository (BOR). A BAPI is implemented as a function module, that is stored and described in the Function Builder.

BAPIs of SAP Interface Types

As of Release 4.5A BAPIs can also describe interfaces, implemented outside the R/3 System that can be called in external systems by R/3 Systems. These BAPIs are known as BAPIs used for outbound processing. The target system is determined for the BAPI call in the distribution model of Application Link Enabling (ALE).

BAPIs used for outbound processing are defined in the Business Object Repository (BOR) as API methods of SAP Interface Types. Functions implemented outside the R/3 System can be standardized and made available as BAPIs. For further information see BAPIs Used For Outbound Processing.

http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp

2-

ALE communication is asynchronous and message-based. ALE communication is the preferred way to integrate distributed SAP Systems, for example, for distributing master data.

Since Release 4.0 BAPIs are the standardized interfaces for ALE-supported communication. ALE services, such as asynchronous BAPI calls, distribution model, monitoring and error handling can be used for BAPIs. The IDoc types required for the ALE services can be generated from BAPIs.

See also: Using the ALE Services

When you use BAPIs for asynchronous messaging, the application in the sending system calls the generated ALE IDoc interface instead of the BAPI. The ALE IDoc interface performs the following tasks:

Creates an IDoc from the BAPI data

Sends the IDoc to the target system

Receives the IDoc in the target system, creates the BAPI data from the IDoc and calls the BAPI

You can use Transaction BDBG to create the other objects required for the asynchronous communication (message type, IDoc type, inbound and outbound function module).

3-

Message type

The message type for forecast delivery schedules which are sent via EDI is in standard LPH1.

The following condition components are used:

http://help.sap.com/saphelp_sm32/helpdata/en/11/dcbd16bd9211d188ef0000e8216438/content.htm

reward point if helpful.

thanks

mrutyun^

[paruchuri_nagesh]

BAPIS ARE USED FOR TO GET DATA FROM NON SAP SYSTEM TO SAP VICE VERSA

IDOC IS NOTHING BUT ACONTAINER WHICH IS USED TO EXCHANGE DATA BETWEEN DIFFERENT SYSTEMS

IN ALE MOSTLY WE USED TRFC'S

TO INCLUDE MESSAGE CONTROL WE HAVE TO CONFIGURE THE THINGS IN TCODE WE20

REWARD FOR USE FUL INPUTS

REAGRDS

NAGESH.PARUCHURI

[Former Member]

hi,

BAPIS N IDOCS are used for providing communication between sap and legacy systems. a bapi is defined as RFC enabled function modules. bapis contains API methods which are resided at BOR [business object repository] of sap.

both are used for same purposes and in different ways.

BAPIS are mainly used for providing synchronous way of communication between sap and legacy systems.

IDOCS are used to provide asynchronous way of communication between sap and legacy systems. idocs are the interfaces which provides asynchronous way of communication b/w sap system n legacy system r b/w 2 sapsystems.

ALE -

---

Application Link Enabling is a internal tool of sap for providing communication between two sap systems. when we want to have communication between 2 sap systems via idocs r bapis we go for ALE.

if helpful reward some points.

with regards,

Suresh Aluri.