Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Save to My Library
Look up keyword
Like this
1Activity
0 of .
Results for:
No results containing your search query
P. 1
Bapi Alecommunication 110127083800 Phpapp01

Bapi Alecommunication 110127083800 Phpapp01

Ratings: (0)|Views: 22 |Likes:

More info:

Published by: Anumandla Harikrishna on Jul 03, 2012
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

07/03/2012

pdf

text

original

 
Asynchronous BAPI-ALECommunication
 © 2006 SAP AG The SAP Developer Network:http://sdn.sap.com1
Applies To:
Asynchronous BAPI-ALE communication on Netweaver 2004s.
Summary
The following scenario will be demonstrated and explained: -Source System creates a calendar appointment in a Target System using the ASynchronous BAPI-ALE communication mechanism.The Source System requests the creation of an appointment. It uses a custom program to call a BusinessObject's method – BAPI. The method will create an outbound IDoc that will be sent to the Target System,and be received as an inbound IDoc on the Target System. The inbound IDoc will be processed accordinglyin the Target System, resulting in a newly created appointment. The appointment can be viewed in TargetSystem’s SAP Office, Appointment Calendar (SSC1). The Target System does not return any messages.To demonstrate
true 
system independence between the Source and Target Systems, they must not in thesame SAP System (SID).The tilde symbol “~”, denotes a more advanced knowledge understanding. Information in this document isincluded for completeness.Error handling code has been omitted to avoid complicating code and issues.
By
: Glen Spalding
Company
:
gin
gle ltd
Date
: 16
th
January 2006
 
Asynchronous BAPI-ALECommunication
 © 2006 SAP AG The SAP Developer Network:http://sdn.sap.com2
Table of Contents
 
Asynchronous BAPI-ALECommunication
 © 2006 SAP AG The SAP Developer Network:http://sdn.sap.com
Object Stack
o/b – outboundi/b – inbound3
 
Source SystemTarget SystemProgramNotice the inbound process flow exits during the i/b FM. Above the i/b FM sits a BAPI and supporting BO.They are required for the generation of the BAPI-ALE interface objects, but are not utilized during theprocessing of the inbound IDoc.BOBAPIo/b FMBAPI-ALE o/b FMIDocPartner ProfilePortBOBAPIi/b FMBAPI-ALE i/b FMPartner ProfileRFC Destination

You're Reading a Free Preview

Download
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->