Logical System and Logical System Name

[Former Member]

Hi,

I would like to create the following and please tell me how do I go about doing this. I am doing this because I am trying to implement both RFC/Idoc to File and File to Idoc/RFC. The basis admin guys are unavailble at the moment so I am on my own at this moment.

Creating a port(I suppose I need to do this on the R3. What are the steps involved)

Create a Partner Profile

[Former Member · Accepted solution]

Hi Sonia,

For XI communicating with SAP R/3 through Idocs ALE settings need to be done,

just go through the following steps and Configure ALE :-

SAP XI

1) RFC Destination (SM59)

a) Choose create.

b) Specify the name of the RFC destination

c) Select connection type as 3 and save

d) In the technical settings tab enter the details SAP SID/URL and system number#.

e) Enter the Gateway host as same details above SID/URL.

f) Gateway service is 3300+system number#.

g) In the Logon /Security tab, enter the client user & Password details of Destination system.

h) Test the connection and remote logon.

2) Create Port (IDX1)

a) Select create new button

b) Enter the port name as SAP+SID (The starting char should be SAP)

c) Enter the destination client.

d) Enter the RFC Destination created in SAP R/3 towards other system.

e) Save

3) Load Meta Data for IDOC (IDX2) a) Create new

b) IDOC Message Type

c) Enter port created in IDX1.

SAP R/3

1) RFC Destination (SM59)

a) Choose create.

b) Specify the name of the RFC destination

c) Select connection type as 3 and save

d) In the technical settings tab enter the details SAP SID/URL and system number#.

e) Enter the Gateway host as same details above SID/URL.

f) Gateway service is 3300+system number#.

g) In the Logon /Security tab, enter the client user & Password details of Destination system.

h) Test the connection and remote logon.

2) Create Port (We21)

a) First Select Transactional RFC and then click create button

b) Enter the destination port name as SAP+SID (The starting char should be SAP)

c) Enter the destination client.

d) Enter the RFC Destination created in SAP R/3 towards other system.

e) Save

3) Create Partner Profile (WE20)

a) Create New

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

c) Select Partner type LS

d) Enter details for Type: US/USER, Agent, and Lang.

e) Click on the + button to select the message type.

f) Select Partner no. and LS which ever create above.

g) Select Message type

h) Select Process code related to the Message type.

I) save.

In SLD – System Landscape Directory

TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.

Ts for Third Party (Logical system):-

BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.

BS for Third Party (Logical system):-Enter the XI logical system name.

In Transaction SALE

Define and Assign the logical system name.

Regards,

Ashwin M

Reward If helpful

[Former Member · Accepted solution]

Thanks

[Former Member · Accepted solution]

Partner profiles can be created in WE20 transaction and from there you can navigate to ports creation aswell...

depending on your scenario, u need to fill idoc message details/port details in outbound or inbound details....

[Former Member]

<b>Maintain Distribution Model and Distribution Views TCode BD64</b>

Distribution model is for distributed environment we can assign several receiver logical systems to a particular R/3 logical system. We also assign the message types for specific type of communication between logical systems. For example if we assign MATMAS the material master IDOC type there will be only a communication of material master data.

Message types are nothing but the IDOC types, so you have know what type of data you are going get or send using the logical systems, using this data we have to assign the IDOC type. For example if it is for purchase order you have to give it as IORUPD01.

<b> I am trying to add a message type to a Distribution view. So it is asking for Message Type and it looks like I can't just type anything in there.</b>

For adding message type you have to make sure that the screen is in edit mode.

You can get the different IDOC Basic types from WE63

[Former Member]

I have few more questions regarding these steps.

[Former Member]

Hi

see the below link

- File to Idoc

idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi

Regards

Chilla

[Former Member]

Actually my question is very specific. I am almost done with the steps in the R3 side. But I am wondering what is "Maintain Distribution Model and Distribution Views TCode BD64 ". What do we need to do in here

[former_member335553]

Hi

BD 64 Distribution model allows you to automatically create the Logical Systems ( BD54 ) and the partner profiles.

The steps from sending an Idoc from your R3 - XI ,( Bd54, we20 )..... are nothing but the steps in the Distribution Model Bd 64 to send an Idoc to XI,

The ALE distribution model defines which applications in your distributed systems communicate with each other and which types of data are distributed. You require a separate ALE distribution model for a Central User Administration (CUA).

[Former Member]

I am trying to add a message type to a Distribution view. So it is asking for Message Type and it looks like I can't just type anything in there. Actually I am just trying to implement the starter kit mentioned by Aprita Seth( I am not sure of his name). File to RFC scenario. as simple as that. For that I am using RFC BAPI_COMPANY_GETDETAIL. Now tell what message type I need to use

[Former Member]

Actually it is Arpit Seth and this is his blog

/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit by Arpit Seth

[Former Member]

Hi Sonia,

The following settings need to be done for File to Idoc/RFC.

<b>Configuration in the Sender SAP R/3 System.</b>

Step 1: Define Logical Systems for Sender and Receiver Systems TCode SALE

Step 2: Assign the Sender Logical Systems to the Client TCode SALE

Step 3: Create RFC destination to SAP XI TCOde SM59

Step 4: Maintain Distribution Model and Distribution Views TCode BD64

Step 5: Maintain Distribution Model and Distribution Views TCode BD64

Step 6: Distribute the Model View TCode BD64

Step 7: Send the Idocs to the Receiver Tcode Depends up on the IDoc Type for Matmas it's BD10

<b>Configuration in SAP XI</b>

Step 1: Define Logical Systems for Sender and Receiver Systems Tcode SALE

Step 2: Assign Receiver Logical System to client TCode SALE

Step 3: Create RFC destination to SAP XI TCode SM59

Step 4: Port maintenance in IDoc adapter TCode IDx1

Step 5: Load IDoc Metadata TCode IDX2

[bhavesh_kantilal]

This blog discusses the setting to be done on a R3 system to Push an Idoc to XI,

/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi

Regards

Bhavesh

[Former Member]

The subject is not appropriate. Maybe it should be Partner Profile and Port. Sorry about that.