SAP COMMUNICATIONS

WITH
MIDDLEWARE (SAPXI)
Submitted to


By
Harleen Kaur Chadha

DOCUMENT INFO
DOCUMENT HEADER
Created by Harleen Kaur Chadha
Created On 30 April 2008
Current ownership Harleen Kaur Chadha
Reviewed by Paresh_deshpande
Contributions fro
Pro!e"t P#$AP%#
Purpose &oK
DOCUMENT HISTORY
Ver DD/MM/Y
YYY
Author Reve!er De"#r$t
o%
0'(A 30)0*)2008 Harleen Kaur
Chadha Paresh +eshpande
+raft
,ersion
( 22)0-)2008 Harleen Kaur
Chadha
Paresh
+eshpande
+raft
,ersion
1
Declaration
I hereby declare that this document is based on my study about the subject. I have
referred to websites of SAP for deriving the content of this document.
Harleen Kaur Chadha
TA!" #$ C#%T"%TS

1 Introduction.3
2 IDOCS.....3
2.1 Introduction to ALE technology..3
2.2 Basic concepts.3
2.2.1 Deinition...3
2.2.2 Structure.!
2.3 "artner "roile...#
2.! In$ound and Out$ound Idocs%
2.!.1 Coniguration settings or Idoc adapter...%
2.!.2 &esting o Idocs...'
3 ()CS..11
3.1 Basics...11
3.2 ()C Adapter11
3.3 Sender ()C Adapter11
3.3.1 Basic coniguration.11
3.3.2 Other coniguration details..13
3.! (ecei*er ()C Adapter.13
3.# &esting Scenarios +ith ()CS..1!
3.#.1 ()C at sender side.1!
3.#.2 ()C at recei*er side...1!
! BA"IS.1#
!.1 Basics1#
!.2 Dierences $et+een ()CS and BA"IS1#
!.3 Dierence $et+een BA"IS,()CS and IDOCS1-
# "ro.ies.1-
#.1 "ro.ies in general.1-
#.2 "ro.ies in SA" /I1-
#.3 ABA" "ro.ies..1%
#.3.1 Deinition1%
#.3.2 Basic coniguration settings1%
#.3.3 Client "ro.ies..1'
#.3.! Ser*er "ro.ies.10
#.3.!.1 /I Adapter..10
#.3.# &esting o "ro.ies...21
#.! 2a*a "ro.ies....21
2
#.!.1 3eneral...21
#.!.2 2a*a pro.ies as a sender.21
#.!.3 2a*a pro.ies as a recei*er..21
- (eerences.22
1 Introduction
&his docu4ent is intended or all those +ho are a4iliar +ith the $asics o /I. &his
docu4ent co*ers the $asic concepts o Idocs5 rcs5 $apis and pro.ies 67a*a 8 a$ap9.It
+ill gi*e good understanding a$out $asic steps re:uired or coniguration settings5 end;
to;end testing o interaces.

2 IDOCS
2.1 Introduction to ALE technology
ALE 66Application lin< ena$ling9 is a SA" proprietary technology. It is used or
co44unication $et+een SA" to SA" syste4s or ro4 SA" to non;SA" syste4s
li<e )&"5 +e$ser*ices5 etc. It is used to e.change $usiness 4essages $et+een
these distri$uted syste4s.
&he distri$uted syste4s are coupled in t+o +ays=.
.Narrow coupling; It is used or synchronous co44unication and it +ants the
the syste4s in*ol*ed to $e a*aila$le at the ti4e o co44unication.(e4ote unction
calls +or<s +ith narro+ coupling.
.Loose coupling;It is used or asynchronous co44unication. &he calling syste4
and called syste4 need not to $e a*aila$le at the ti4e o co44unication.I the
called syste4 is not a*aila$le then only co44unication error +ill occur.
IDOCs 6Inter4ediate docu4ent9 uses loose coupling or 4essage e.change.
2.2 Basic concepts
2.2.1 Deinition
Idocs stores data hierarically in so4e speciic or4at.Idocs are used or
e.changing data $et+een SA" syste4s and non;SA" syste4s
.Idoc ty&e; It is the structure o the data +hich is associated +ith 4essage type.
It is ha*ing data o one particular 4essage type. E*ery idoc represents only one
$usiness type. E.a4ples o IDoc type is >A&>AS116It contains 4aterial
4aster structure9.

.'essage ty&e;&he 4essage type is ha*ing the data $eing e.changed $et+een SA"
and non;SA" syste4s. It relates to the structure o the data= an IDOC type or
e.a4ple5 >A&>AS is a 4essage type or >aterial >aster.
."(tended Idocs; &hese are custo4i?ed Idocs.&he ne+ seg4ents are added to
standard idocs.&he additional seg4ents added starts +ith @. &hese are custo4er
e.tensions5 the additional seg4ents are added to $asic seg4ents supplied $y SA"5
3
so that additional $usiness inor4ation can $e transerred depending on custo4er
re:uire4ents
.
2.2.2 Structure
&he igure $elo+ sho+s the $asic structure o an IDoc and +hich parts are
transerred to and ro4 the e.ternal syste4. &he seg4ent hierarchy is
sho+n here. A total o 3 hierarchy le*els are there.
Idoc Structure

Idocs data is stored in three data$ase ta$les in SA". &hese are or control record5
data record and status record.
.Control )ecord; It is identical or all idocs.It contains the ad4inistration
inor4ation5 or e.a4ple sender inor4ation5 recei*er inor4ation5 4essage5etc.&he
control record structure reers to standard structure EDIADC!1.Be can *ie+ the
structure in transaction se11.
.'a&&ing of control record in *I
I the idoc is used on sender side then +e are getting *alues ro4 SA" syste45
But i the Idoc is on recei*er side5 and +e are getting its *alues at runti4e then
+e can si4ply disa$le it in 4apping.But i +e +ant the *alues to $e illed ro4
payload then +e ha*e to chec< Capply control record *alues ro4 payloadC in
co44unication channel.

Control seg4ent 6EDIADC!19
E1Dna4e1E"arent Seg4ent
D)ield1E
D)ield2E
DE1na4e2E Child Seg4ent

D)ield1E
D)ield2E

Status Seg4ent 6EDIADS!19
E
/
&
E
(
F
A
L
S
G
S
&
E
>
In$ound,out$ound
processing
Status Inor4ation
!


I +e chec< this $o.5 and ill all the *alues ro4 payload $ut idoc adapter +ont
ta<e all *alues5 it changes the4 and uses the standard *alues. &here are only e+
ields +hich +e can change in control record 6EDIADC!19 $y pro*iding
4apping logic at design ti4e5those ields are=
>ESCOD5 >ESC)&5 &ES&5 E/"(SS5 S&D5 S&DH(S5 S&D>ES5 SFDSAD5
SFDLAD5 (CHSAD5 (CHLAD5 (E)IF&5 (E)3(" .
.+ata )ecord;&hey contains the seg4ents +hich is ha*ing $usiness
Inor4ation and data is stored hirerachly li<e parent seg4ent is ha*ing so4e
)ields and then child seg4ent as sho+n in igure.Standard sap seg4ent na4es
starts +ith E1.
.Status )ecord;&he status records contain all o the processing status5 as +ell as
the ad4inistration inor4ation. &he status record +ill tell +hether the idoc is
posted to /I or i it has $een added to SA" syste4 successully +ithout
errors.&he status seg4ent is not sent as part o idoc structure +hen idoc is posted
to e.ternal syste4 $ut +e can chec< the status o the idoc in +e12 transaction
6out$ound,in$ound9All the status inor4ation is stored in EDIADS!1 structure in
SA".
%ote= IDOCs are identiied $y a uni:ue IDOC nu4$er 6IDOCFI>9 +hich is
assigned $y SA"J +e can also 4anually assign a nu4$er range o IDOCS.
2.! "artner proile
It plays an i4portant role in EDI 6Electronic data interchange9 co44unications. It
deines the type o data and the co44unication lo+ o data to $e e.changed
$et+een partners.
&ransaction +e21 is used to set the details or partner proile.
&he ollo+ing inor4ation is deined +ith the partner proile.
K IDoc type and 4essage type are <ey identiier o the partner proile
K Fa4es o sender and recei*er to e.change the IDoc inor4ation or the
respecti*e Idoc and 4essage type.
K Logical port na4e *ia +hich the sender and recei*er5 resp. +ill co44unicate
#

"artner proile coniguration is done in +e21."artner details are added +ith
In$ound and out$ound relationships.
Dou$le clic<ing on any o the out$ound or in$ound 4essage type5 it +ill ta<e to another
screen +hich +ill $e ha*ing dierent details or in$ound and out$ound.&his is sho+n in
the $elo+ screen shots.
Out$ound 4essage type
-
In$ound 4essage type
2.# In$ound and Out$ound Idocs

,.-.. Configuration settings for Idoc ada&ter
()C Destination;&hey are the 4eans +ith +hich IdocLs are posted to and ro4
/I. Be need to create the4 +hen +e are dealing +ith idoc.&ransaction s4#0
.#utbound 6Bhen Idoc is used at sender side9;Fo coniguration or Idoc adapter to
$e done as partner proile is $eing created or sending idocs5 no sender
agree4ent is re:uired or the Idocs. ()C destination +ill $e 4aintained in SA"
syste4 +hich points to /I syste4.
.Inbound 6Bhen Idoc is used at recei*er side9;&he recei*er co44unication channel
is conigured or idoc adapter and ()C destination +ill $e created in /I syste4
+hich points to SA" syste4."artner proile 4ust $e conigured or idoc on sap side5
other+ise error +ill co4e that partner proile is not conigured or idoc.


%
,.-., Testing of Idocs
Im&ortant transactions used for testing
./"+I0 SA" Easy Access
IDOC >enu
&his is the user 4enu or the IDOC *ersion5 si4ilar to the standard SA" 4enu
+hen +e irst enter on

./".1; Test tool for IDOC processing
This transaction is used to post outbound IDOC data to XI. Similarly this TCODE is used
for processing inbound IDOC inside XI.

Steps to $e ollo+ed or posting Idoc ro4 sap syste4.

Bhen +e select e.isting Idoc nu4$er ro4 4essage type +e +ant and e.ecute it5
it +ill ta<e to another screen. By clic<ing on the MStandard out$ound
processingN.One pop;up +indo+ +ill co4e. I +e chec< this5 ne+ idoc +ill $e
generated and it +ill $e posted to /I .It +ill display Idoc nu4$er do+n in the
screen.
'

./"2,3/"24;Idoc Listing
&his transaction +ill list all the idocs $oth or in$ound and out$ound process5 In
the idoc list +e +ill ind the status5 seg4ents and data inside the idocs.
Call transaction +e12,+e1#5 +e ha*e to set proper ti4e or enter the IDoc
nu4$er to see i the IDoc +as sent.

Initial screen o transaction +e12,+e1#
0
&ransaction +e12,+e1# search results
#utbound Idocs5 I status is green it says that the Idoc +as successully passed to SA"
syste4 or e.ternal progra4 6status 139.&hen +e can chec< idoc in /I5 $ut I status is red
it 4eans errors are there and idoc is not posted to /I.
Inbound idocs5 Be can chec< in in$ound idocs status +hether the idocs sent ro4 /I to
SA" are added +ith errors or success.
I+*4; SA" Adapter ; >onitoring
Be ha*e to chec< in ID/# +hether the idoc is recei*ed in /I. Be ha*e to enter the idoc
nu4$er or +e can chec< +ithin particular ti4e ra4e that +hether idoc is posted
successully and +e also chec< or in$ound idocs to SA" +hether they are generated. In
the igure $elo+ sho+n the output o transaction ID/#.

>essage ID is the 3IID o the /I syste4 or this particular IDoc. &he IDoc nu4$er is
the IDoc nu4$er as stored $y the Integration Ser*er. &ransaction ID is the transaction ID
+hich is used in the sending process o the IDoc. Bhen you dou$le clic< the entry in
ID/#5 +e co4e to S/>BA>OFI +here the details o the 4essage +e can chec<.
Other useul Idoc transactions
BE-1; Docu4entation or IDoc types
BE10; Search or IDocs $y Content
ID/1; "ort >aintenance in IDoc Adapter
ID/2; >eta Data O*er*ie+ in IDoc Adapter
%ote5 )or detailed inor4ation on Idocs5 please reer to the lin<s in reerences.
11
! %&CS
!.1 Basics
A re4ote unction call 6()C9 is +hen a unction 4odule is called that runs in a dierent
syste4 to the calling progra4. Although it is also possi$le to call a unction 4odule in the
sa4e syste4 as an ()C5 ()Cs are nor4ally used +hen the caller and the called unction
4odule run in dierent syste4s.
In the SA" syste4 the ()C is used to co44unicate $et+een SA" syste4s or $et+een
SA" syste4 and e.ternal syste4s.&he ()C co44unication can $e synchronous or
asynchronous.&he SA" syste4s connects to Integration engine using ()C adapter.
!.2 %&C Adapter
Adapter used to connect SA" co4ponents to an Integration Ser*er $y using re4ote
unction calls 6()Cs9.
I ()C is at sender side then the ()C adapter recei*es ()C 4essage ro4 SA" syste4
and con*erts that 4essage into />L 4essage +hich is process $y integration engine.I
()C is at adapter side then the />L 4essage ro4 integration engine on recei*er side
+ill $e con*erted to ()C 4essage using ()C adapter and or+arded to SA" syste4.
!.! Sender %&C Adapter
6.6.. asic configuration
)or coniguring sender rcadapter5 t+o $asic things are done=
;E()C Destination to $e created in SA" syste4
;E()C channel in the /I directory
()C destinations should $e conigured in SA" syste4s not in /I.&he $asic
coniguration para4eters are=
Program id0the progra4 id can $e anything5 the sa4e na4e should $e gi*en in
$oth the rc destination and rc adapter.
A&&lication Server 78ateway9 and A&&lication Server Service 78ateway9
&CODE= S>3B ;E 3oto;E "ara4eters ;E Display
&he re:uired inor4ation +ill $e under Attri$utes. Application Ser*er 63ate+ay9
is the 3ate+ay hostna4e and Application Ser*er Ser*ice 63ate+ay9 is the
3ate+ay ser*ice. &he 3ate+ay ser*ice is sapg+// +here // is the
syste4 nu4$er.
)$C +estination in SAP system;It is created under transaction s4#05 create
ne+ destination o type & 6&C",I"9.Select (egistered Ser*er "rogra4 option
$eore +riting progra4 id. "rogra4 id is case;sensiti*e. In the gate+ay host and
gate+ay ser*ice5 the *alues to $e gi*en are o application syste4 6Business
syste495 It not /I ser*er.


11

)$C channel in the *I directory;&he *alues or application ser*er5 application ser*er
ser*ice and application progra4 id is ta<en ro4 rc destination created in s4#0 in SA"
syste4.

12
6.6., #ther configuration
)$C 'etadata )e&ository Parameter
&he ()C 4etadata repository para4eters identiy the SA" syste4 containing the
repository or the ()C 4etadata. &his does not necessarily ha*e to $e the sender
syste4.

6.- )eceiver )$C Ada&ter
)or the recei*er channel coniguration5 the ollo+ing coniguration settings need
to $e done.


6.4 Testing Scenarios with )$CS
%&C at sender side:
3o to tcode se3% and e.ecute the rc in SA" syste4 it +ill as< or rc target syste4
6+e ha*e to gi*e the na4e o rc destination that +e had 4ade or pinging the .i9.
Halues are to $e gi*en as per re:uire4ent in I4port para4eters and ta$les and clic<
on the e.ecute $utton.
13


Be +ill chec< in /I +hether ()C has reached or not in S/>BA>OFI.
%&C at recei'er side(
/I +ill gi*e the input through rc recei*er co44unication channel to rc and
through the sa4e co44unication channel the response +ill $e $ac< to .i +hich is
generated $y rcs 6I or ()C +e are using synchronous interace9.Be can chec<
the 4essages in S/>BA>OFI in /I and sap syste4.
%ote= &here is no such tcode or chec<ing ()C as +e do or IDOC on recei*er
Side.Be can chec< in S/>BA>OFI in SA" +hether the 4essages are reached or
not5or else +e can chec< in ABA" ta$les +hether the data +e are sending is getting
populated or not.
%ote5 )or detailed inor4ation on rcs5 please reer to the lin<s in reerences.
# BA"IS
#.1 Basics
A usiness A&&lication Programming Interface 6API9 plays an i4portant role
or integration and e.change o data $et+een SA" and non;SA" co4ponents
BA"Is pro*ides co4plete unctionality or a particular $usiness process.&hey +or<
on re4ote unction call protocol.E.a4ple BA"IA"OAC(EA&E= &his is standard
BA"I used or creating purchase orders. It +ill peror4 this particular $usiness
process and can $e called in progra4s or peror4ing this tas<. Be can also create
1!
custo4i?ed $apis or so4e $usiness processes.
BA"Is are deined in the BO( 6Business o$7ect repository9 as 4ethods o SA"
$usiness o$7ect types +hich are used or speciic $usiness unctions.A $usiness
o$7ect is not o$7ect as the o$7ect +e reer in co4puter progra44ing5 $ut its $usiness
entity.eg. custo4er.BA"Is are accessi$le through transaction BA"I and SBO1.
#.2 Dierences $etween %&CS and BA"IS
()CS and BA"IS $oth are re4otely ena$led unction 4odules that can $e called
e.ternally ro4 SA". &he critical dierence is that $apis are +rapped in $usiness
o$7ects $ut rcs cannot. Be create $usiness o$7ects and those are then registered in
BO( 6Business O$7ect (epository9 +hich can $e accessed outside the SA" syste4
$y using so4e other applications 6Fon;SA"9 such as HB or 2AHA. In this case +e
only speciy the $usiness o$7ect and its 4ethod ro4 e.ternal syste4.In BA"I there
is no direct syste4 call. Bhile ()C are direct syste4 call So4e BA"Is pro*ide
$asic unctions and can $e used or 4ost SA" $usiness o$7ect types.Inli<e $apis5 rc
are 7ust (e4ote ena$led unctions +hich are not released and +ill not pro*ide
co4plete unctionality o a $usiness process,transaction.>ostly $apis and rcs +ill
$e used or synchronous interaces
#.! Dierence $etween BA"IS)%&CS and IDOCS
BA"Is,()Cs and Idocs are used to integrate /I +ith SA" syste4. &he data transer
using IDOC is an asynchronous process5IDocs are te.t encoded docu4ents +ith a
rigid structure that are used to e.change data $et+een SA" and an e.ternal
syste4.&he data is pac<ed into idoc and the sent to /I or processing
&he data transer using ()C is a synchronous or asynchronous process.RC ma!es
direct and synchronous calls o a progra4 in the re4ote syste4.I the caller is an
e.ternal progra4 it +ill call an ()C;ena$led unction in SA" and i the calling
progra4 is the SA" syste4 it +ill call an ()C;unction in another SA";syste4 or it
+ill call a non;SA" progra4 through a gate+ay;pro.y.BA"Is uses ()C protocol5
i.e.they are ()C;ena$led unction 4odules5 especially designed as Application
"rogra44ing Interace 6A"I9 to the SA" $usiness o$7ect5 or in other +ords= are
unction 4odules +hich are oicially released $y SA" to $e called ro4 e.ternal
progra4s.
%ote5 )or detailed inor4ation on $apis5 please reer to the lin<s in reerences
* "%O+IES

*.1 "ro,ies in general

"ro.ies are the progra44ing lines o code or are application progra44ing
interaces that are generated or application languages li<e ABA",2a*a,.Fet.
&he e.ecuta$le interaces are generated or these applications +ith +hich they
e.change 4essages in />L,SOA" +ith e.ternal applications.
1#
*.2 "ro,ies in SA" +I
SA";/I integrates SA" and non;SA" syste4s using *arious adapters.But +ith
applications li<e ABA" and 2AHA e.change 4essages using /I $y using
e.ecuta$le interaces and these e.ecuta$le interaces are <no+n as pro.ies.
2AHA +ants to e.change 4essages using /I.&he pro.y originals are located in
integration ser*er. &he pro.y structure is created at design ti4e i.e. 4essage
interace +ill $e created in integration repository.Ising this 4essage interace
the pro.y +ill $e generated in application syste4s.ABA" pro.ies are generated
using transaction S"(O/G in SA" syste4.2a*a pro.ies are generated using
Integration repository
%ote= "ro.y generation is a*aila$le in applications that are $ased on SA" Be$
AS -.21 and that ha*e installed the /I 2.1 Add;On.

*.! ABA" "ro,ies

4.6.. +efinition
ABA" pro.ies are used +hen ABA" applications needs to send or recei*e
4essages.ABA" pro.ies are generated on the Application ser*er +ith
transaction S"(O/G5 $ased on the BSDL representation o the 4essage
interace.
&he type o the 4essage interace deter4ines +hat type o pro.y is generated.
&he out$ound 4essage interaces in /I are client &ro(ies in application syste4s
the in$ound 4essage interace in /I are server &ro(ies in application syste4s.
*.6., asic configuration settings
&he coniguration settings are re:uired on the $usiness syste4 6SA"9 side or
in$ound and out$ound pro.ies=
1. O&&" connection is created in the $usiness syste4 using transaction S>#0
&echnical Setting=
Connection &ype= O
&arget Oost= Syste4 na4e
Ser*ice Fu4$er= O&&" "ort na4e
"ath= "rei.= ,sap,/I,engine,P typeQentry
1-
Logon Security
On the Logon,Security ta$ page5 enter the ollo+ing logon data=
Iser= /IA""LISE( 6or e.a4ple9J this user should represent the sending
syste4 6see also the SA" /I Security 3uide under Ser*ice Isers or >essage
E.change9.
"ass+ord= the pass+ord you ha*e speciied or this user
Client= SA" /I Integration ser*er
Language= Language re:uired
1%
4.6.6 Client Pro(ies
Client pro.ies 6out$ound9 are generated ro4 out$ound 4essage interaces. &hey
can $e triggered $y an ABA" progra4 o SA" syste4. A 4essage +ill $e send to
/I.
&he steps in*ol*ed in out$ound,client "ro.y de*elop4ent are=
;EAll necessary Integration repository o$7ects +ill $e de*eloped at design ti4e.
6&he out$ound client pro.y data type5 4essage type and 4essage interace9.
;EAter the 4essage interace is de*eloped in the integration repository5 pro.y is
generated in SA" syste4 using S"(O/G transaction. S"(O/G transaction lists
all the 4essage interaces in the integration repository under respecti*e sot+are
co4ponent *ersions. Be ha*e to choose the re:uired 4essage interace and clic<
Create. In the dialog $o. that appears5 enter the na4e o the pac<age +here +e
+ant to create the pro.y o$7ects.+e can also enter prei. or all the o$7ects you are
a$out to create5 +hich pre*ents na4e conlicts +ith e.isting o$7ects in the syste4.


1'
;Once pro.y is created then it generates a class and structures for message type and
data type. The "#"$ program %ill be %ritten in S"$ system to trigger client pro&y re'uest
from S"$ system.
Sender communication channel5 Fo sender adapter conigurations are re:uired
+ith a$ap pro.ies.

4.6.- Server Pro(ies
&he steps in*ol*ed in In$ound,ser*er "ro.y de*elop4ent are=
;Fecessary repository o$7ects are de*eloped during the design phase. &he in$ound
datatype5 4essage type and the corresponding 4essage interace.
;In$ound pro.y or the corresponding in$ound 4essage interace is generated in
the SA" syste4.
;In$ound ABA" pro.y generates the ollo+ing O$7ects=
1. ABA" Interace.
2. Structure or the 4essage type in ABA" Data Dictionary.
3. Structure or the data type in ABA" Data Dictionary.
!. An ABA" class is generated 6i it does not already e.ists or the ABA"
4essage interace that has $een generated9 +hich i4ple4ents the
interace. All the generated o$7ects need to $e acti*ated
)eceiver communication channel5 /I Ises /I Adapter to co44unicate to SA"
syste4 +hen the SA" Syste4 is i4ple4enting a$ap pro.ies.
4.6.-.. *I Ada&ter
&he /I adapter is to e.change 4essages +ith an Integration Engine. Both /I 3.1
and /I 2.1 4essage protocols are supported. /I adapters co44unicate directly
+ith integration engine. It is usually used during pro.y co44unication.&here is
no need to create co44unication channel +hen /I adapter is used at sender side.
It is used internally in the Integration engine. E.a4ple5 In case o B"> scenarios
/I adapter is used internally.In case o ser*er pro.ies5 /I adapter is
used on recei*er side for /I to co44unicate to SA" Syste4 +hen the SA" Syste4
is i4ple4enting pro.ies.
Belo+ are the coniguration para4eters o /I Adapter.
10


4.6.4 Testing of Pro(ies
/hen &ro(y is sender5 3o to S/>BA>OFI in the /I syste4 gi*e the sender
ser*ice na4e to ilter the 4essage and see i it sho+s a success lag or proper
transer. In case o any error the errors can $e corrected $y inding the4 out in the
trace.
/hen &ro(y is receiver5
3o to S/>BA>OFI in the SA" syste4 and i it sho+s a success lag +hich
indicates that the data is successully transerred to the SA" syste4.
&he @ ta$le in the SA" syste4 can $e chec<ed or population +ith the intended
data.

*.# -a'a "ro,ies
4.-.. 8eneral
2a*a "ro.ies are 2a*a Class iles created to access the SA". 2a*a pro.ies are used
+hen 7a*a applications needs to send or recei*e 4essages. Ising the 7a*a
pro.y generation unction5 +e can generate 7a*a classes ro4 the interace
description in the Integration (epository. Ising these o$7ects5 +e can then
i4ple4ent sender and recei*er applications in 2a*aJ the pro.y o$7ects
esta$lish the connection to the Integration Ser*er $y using the 2a*a pro.y
runti4e.

4.-., :ava &ro(ies as a sender
Bhen the 4essage is $eing sent ro4 7a*a application to Integration ser*er.
"re;re:uisites or sender pro.ies=
Data types5 4essage types and out$ound 4essage interaces are created in
Integration repository5 right clic< on the out$ound interace and choose
the generate 7a*a "ro.y option ro4 the conte.t 4enu +hich creates the
client pro.y $eans and client pro.y classes5 +hich +e include in sender
application.
21

In Fet+ea*er de*elop4ent studio5 +e ha*e to add this pro.y generation
classes and ater inishing all settings or client pro.ies and then
deploy it to 22EE engine and ater deploying +e ha*e to +rite 7a*a
application that in*o<es pro.y call.
Sender co..unication channel( Fo sender adapter conigurations are re:uired
+ith 7a*a pro.ies.
4.-.6 :ava &ro(ies as a receiver
Be +ant to 4a<e a ser*ice a*aila$le on the 22EE ser*er. &he ser*ice is to
$e pro*ided $y 4eans o the Integration Ser*er.
"re;re:uisites or recei*er pro.ies=
Data type5 4essage type and in$ound 4essage interace are created or the
ser*ice in the Integration (epository. Ising 2a*a pro.y generation5ser*er pro.y
$eans and ser*er pro.y classes +ill $e created5 +hich +e include in the
application.
)eceiver communication channel5 &o send 4essages ro4 the Integration
Ser*er to the SA" 22EE Engine and to the 2a*a pro.y runti4e5co44unication
channel should $e conigured in the Integration Directory.


21
&he 2a*a pro.y runti4e is descri$ed as a technical recei*er or the recei*er
Application $y using a co44unication channel.

%ote5 )or detailed inor4ation on pro.ies5 please reer to the lin<s in reerences
/ %eerences
+++.help.sap.co4
+++.sdn.sap.co4
+++.google.co4
Ser*er pro.ies
https=,,+++.sdn.sap.co4,ir7,sdn,+e$logsP$logQ,pu$,+lg,1!#%
Client pro.ies
https=,,+++.sdn.sap.co4,ir7,sdn,+e$logsP$logQ,pu$,+lg,13'%
2a*a pro.ies
https=,,+++.sdn.sap.co4,ir7,sdn,go,portal,prtroot,docs,li$rary,uuid,d1-31#a-;e--e;
2011;130c;$a'$$$d23%12
Bapis and (cs
https=,,+++.sdn.sap.co4,ir7,sdn,threadPthreadIDQ3-0!01
IDOCS
http=,,help.sap.co4,saphelpAn+%1,helpdata,en,e,!'ee%113%!#'!1a0'ac11#!!1a2$,ra
4eset.ht4
http=,,a$approgra44ing.$logspot.co4,211',11,partner;proiles;and;ports.ht4l
22