8/12/2019 IDoc Scenario

1/14

ALE/Idoc configuration - (R3--XI--File)

SAP XI1) RFC Destination (S!")

a) Choose create.b) Specify the name of the RFC destination

c) Select connection type as 3 and saved) In the technical settings tab enter the details SAP SI!"R# and system n$mber%.e) &nter the 'ate(ay host as same details above SI!"R#.

f) 'ate(ay service is 33*system n$mber%.g) In the #ogon !Sec$rity tab+ enter the client $ser , Pass(ord details of estination

system.h) -est the connection and remote logon.

#) Create Port (IDX$)

a) Select create ne( b$ttonb) &nter the port name as SAP*SI -he starting char sho$ld be SAP)

c) &nter the destination client.d) &nter the RFC estination created in SAP R!3 to(ards other system.

e) Save

3) Load eta Data for ID%C (IDX#)a) Create ne(

b) I/C 0essage -ypec) &nter port created in I1.

SAP ECC&

$) RFC Destination (S!")a) Choose create.

b) Specify the name of the RFC destinationc) Select connection type as 3 and save

d) In the technical settings tab enter the details SAP SI!"R# and system n$mber%.e) &nter the 'ate(ay host as same details above SI!"R#.

f) 'ate(ay service is 33*system n$mber%.g) In the #ogon !Sec$rity tab+ enter the client $ser , Pass(ord details of estination

system.h) -est the connection and remote logon.

#) Create Port ('e#$)a) First Select -ransactional RFC and then clic2 create b$tton

b) &nter the destination port name as SAP*SI -he starting char sho$ld be SAP)

c) &nter the destination client.

d) &nter the RFC estination created in SAP R!3 to(ards other system.e) Save3) Create Partner Profile ('E#)

a) Create e(

b) Create the Partner no. name as same the logical system name of the destinationsystem.

c) Select Partner type #Sd) &nter details for -ype4 "S!"S&R+ Agent+ and #ang.

e) Clic2 on the * b$tton to select the message type.

8/12/2019 IDoc Scenario

2/14

f) Select Partner no. and #S (hich ever create above.g) Select 0essage type

h) Select Process code related to the 0essage type.I) save.

In SLD Sste* Landsca+e Director

-S for R!3 #ogical system)45Assign the client name created in R!3 as #ogical system

ame.-s for -hird Party #ogical system)45

6S for SAP R!3 #ogical system)45 Assign the client name created in R!3 as #ogicalsystem ame.

6S for -hird Party #ogical system)45&nter the I logical system name.

FILE ,% ID%C (Asncronous)

%.er.ie

-he p$rpose of this scenario is to implement a simple one5(ay+ asynchrono$s lin2bet(een a file sender #egacy System) and the R!3 system. 7o$ (ill be able to$nderstand the str$ct$re of ob8ects in the S#+ Integration Repository and

Integration irectory. -his e9ercise (ill also introd$ce the graphical mapping

environment+ the central :;&& adapter engine+ the file adapter for Sender Systemand the Idoc adapter for the Receiving System.

Prere0uisites

6asic 2no(ledge of I+ I/C!A#&+ 0# etc.

Descri+tion

A c$stom 0# doc$ment containing vendor information is pic2ed $p from the filesystem by the file adapter. -he message is mapped to Ioc50# format and then

ro$ted to the Ioc adapter. -he Idoc 0essage -ype CR&0AS vendor master data)is posted into the bac2end R!3 system (ith error stat$s

8/12/2019 IDoc Scenario

3/14

Product

Create a softare +roduct

Softare Co*+onent

1. Select >Soft(are Components? from the drop do(n listCreate a softare co*+onent

,ecnical sste*s

Create tecnical sste* for ID%CSAP has shipped R!3 technical system named I5, on scilssa+#

@ence+ no need of creating ne( technical system for R!3

8/12/2019 IDoc Scenario

4/14

Create ,ecnical Sste* for FILE SER6ER(Coose ,ird-+art)

'ive the technical system name and the host name

Choose appropriate Prod$ct and clic2 on finish

78SI9ESS S:S,ESCreate 7usiness Sste* for ID%C

SAP has shipped R!3 6$siness System named SAPIDES

8/12/2019 IDoc Scenario

5/14

@ence no need of creating R!3 6$siness system

Create 7usiness Sste* for file ser.er

Choose third party system

Provide appropriate technical system and logical system name

Select integration server to connect and clic2 on finish.

@ere+ (e complete the SLD Pre+aration

Ste+ # ; Integration Re+ositor (Design)Ret$rn to the Integration 6$ilder homepage and select >Integration Repository?

and logon

8/12/2019 IDoc Scenario

6/14

From the Integration 6$ilder home page+ select >Integration Repository4 esign?.

-his (ill la$nch the :ava Beb Start application. #og in (ith yo$r $ser I andPass(ord.

Ste+& I*+ort te Softare Co*+onent 6ersion1. Import yo$r soft(are component by selecting -ools 5 -ransfer from System

#andscape irectory 5 Import Soft(are Component Dersions

;. Select yo$r soft(are component version created in the previo$s section and >Import?

3. -he soft(are component version (ill no( appear on the left hand side of theScreen. >&9it? to clear the import (indo(E. o$ble clic2 on the Soft(are Component Dersion to bring it $p on the right hand

Frame Remember the $pper level of the tree is the Soft(are Component ande9panded $nderneath is the SBCD)

=. &nter >&dit? mode on the SBCD.

8/12/2019 IDoc Scenario

7/14

. "nder the >amespaces? add a namespace by clic2ing on the green >*?G. Config$re the namespace as http4!!filetoidoc

H. >Save? (hen done1. &9pand the ne(ly associated namespace and >Imported /b8ects? elements no(

listed $nder the SBCD

Ste+& I*+ort te out

8/12/2019 IDoc Scenario

8/14

E. >Finish? to start the import. >Close? the (indo( once complete

=. Close the (indo( once complete and revie( the imported Ioc str$ct$re $nder

Imported /b8ects 5 Iocs

/-&4 In this specific e9ample Iocs+ once imported+ a$tomatically generate

their $nderlying str$ct$res and can be referenced as 0essage -ypes for

0essage 0appings) and 0essage Interfaces in Interface 0appings) ins$bse$ent steps. ote this import can also ta2e a co$ple min$tesJ

8/12/2019 IDoc Scenario

9/14

Ste+& Create te in

8/12/2019 IDoc Scenario

10/14

ote that the D, type previo$sly created is no( referenced from the main data type.

-his is called nesting of data types. -his is achieved by selecting >Search @elp? fromthe drop5do(n men$ in the >-ype? col$mn. -here yo$ (ill be able to select any

e9isting data type in the same SBC.

essage ,+e

1. "nder yo$r SBCD and e9pand the >Interface /b8ects? element;. Right Clic2 on >0essage -ype? and >e(?3. &nter >vendor? as the name and >Create?

E. In the >ata -ype "sed? section+ associate the >-? either via drop do(n+

copy!insert+ or drag and drop from the ata -ypes section on the left frame and>Save?

8/12/2019 IDoc Scenario

11/14

essage Interface1 $nder yo$r SBCD and e9pand the >Interface /b8ects? element

;. Right Clic2 on >0essage Interfaces? and >e(?3. &nter >o$t? as the name and >Create?

E. Config$re the 0essage Interface as sho(n belo( and >Save?

essage a++ing1. "nder yo$r SBCD and e9pand the >0apping /b8ects? element

;. Right Clic2 on >0essage 0apping? and >e(?3. &nter >6endor>CREAS3? as the name and >Create?

E. Select the So$rce 0essage type >dt? either via drop do(nbe s$re to choose yo$r o(n SBC) from the Interface /b8ects 5 0essage -ypes

section on the left frame=. Select the -arget 0essage type >CREASCREAS3? either via drop do(n or

drag and drop or drag and drop from the Imported /b8ects 5Idoc section on the leftframe

8/12/2019 IDoc Scenario

12/14

Please refer to the table belo( for the mapping r$les segments and fields are sortedaccording to their order of appearance in the Idoc).

. o( (e have to assign constants to certain fields and attrib$tes in the Ioc forsegment $alifiers+ hard coded val$es and 0# attrib$tes). -his can be achieved by

follo(ing the proced$re belo(. Refer to the table belo( for more details on themapping r$les.

G. o$ble5clic2 on the target field in the Ioc.H. At the bottom of the screen+ select >Constants? from the drop5do(n list for

f$nction type.

1. Clic2 on the f$nction >Constant?. o( the >empty? constant appears in thescreen.

11. o$ble5clic2 on the >empty? constant and assign a specific val$e.

8/12/2019 IDoc Scenario

13/14

1;.Connect the constant to the target field.

13.For the segments &1#F610 and &1#F010 please assign an empty constant. -his

is necessary beca$se these segments are optional in the Ioc. Altho$gh some$nderlying fields have already been mapped+ If the parent node is not e9plicitly $sedas the target of a mapping+ the segment (ill not be instantiated at all.

essage a++ing ; ,esting

1. Select the >-est? tab;. &9pand the So$rce -ree

3. Pop$late val$es into the so$rce message fields to be passed to the target message

as defined in the message mapping $se the follo(ing pict$re as a g$ide)

8/12/2019 IDoc Scenario

14/14

Interface a++ing1. "nder yo$r SBCD and e9pand the >0apping /b8ects? element

;. Right Clic2 on >Interface 0apping? and >e(?3. &nter >6endor>out>CREAS3? as the name and >Create?

E. Select the So$rce 0essage interface >vendorNo$t? either via drop do(n or dragand drop from the Interface /b8ects 5 0essage Interface section on the left frame

=. Select the -arget 0essage interface >CR&0AS.CR&0AS3? either via dropo(n be s$re to choose yo$r o(n SBC) or drag and drop from the Imported/b8ects 5 Idoc section on the left frame

Read Interfaces ? to read the interface properties andpop$late the lo(er (indo(

. Select the >DendorNCR&0AS3? message mapping as the 0apping ProgramAgain via drop do(n or drag and drop from the 0apping /b8ects 5 0essage

0apping section on the left frameG. Dalidate the final config$ration against the belo( and >Save?

Ste+& Acti.ate Re+ositor %Change #ists? tab

;. &9pand yo$r change list

3. &9pand yo$r SBCE. Right clic2 on >Standard Change #ist? and >Activate?

=. /n the pop$p (indo( note all the ob8ects that are being activated and>Activate?