ALE interface

[Former Member]

Hi, Can anybody suggest me... regarding

while creation of partner profile in to R3 system

or one r3 second one is legacy...

we have to maintain the partner profile explicitly ????

in both the system....

2> for using the model view distribute ? is there any need to transport the modelview... while replicating between development and quality server ???

thanks in advance

Manish

[former_member189629]

Hey Manish,

You will have to generate and configure Partner profiles in the sending & receiving systems. Follow the flow given below

ALE CONFIGURATION:

-

---

SALE - Define Logical System

- Assign Client to Logical System

- Define Target Systems for RFC Calls

- Maintain Distribution Model and Distribute Views

- Maintain Partner Profile Manually

- Generate Partner Profiles

- Check Technical Consistency

IDOC ADMINISTRATION

-

---

WE05 - IDoc Lists

WE02 - Display IDoc

DISPLAY STATUS

-

---

WE20 - Partner Profile

WE21 - Port Definition

SM59 - RFC Destination

BD71 - Distribute Model

DEVELOPMENT

-

---

WE31 - IDoc Segments

WE30 - IDoc Types

WE81 - Message Types

WE82 - IDoc Type / Message

WE57 - Message/Application Object

WE34 - IDoc Styles

WE32 - IDoc Views

CONTROL:

-

---

WE41 - Outbound Process Code

WE42 - Inbound Process Code

WE43 - Display Status Record

WE64 - Process Codes

outbound & inbound operations

-

---

BD10 Send Material

BD11 Get Material

BD12 Send customer

BD13 Get customer

BD16 Send Cost Center

BD17 Get Cost Center

BD18 Send General Ledger Account

BD19 Get General Ledger Account

If you find this answer useful, please reward me for the same.

Good luck

Karthik Potharaju

[Former Member]

Hi manish joshi,

1)yes u have to maintain partner profile explicitly in both systems.

2)just a distribute the model view and u can see it in target system after that.

regards,

kiran B

[Former Member]

Hi,

It is required to maintain the partner profiles in both the systems.

If the other system is a legacy system, then this whole process itself is not possible. You would require a Middleware (say for example SAP-XI) in that case.

ModelView is required to be distributed.

Follow the below steps-

1. Define Logical System SALE (BD54)

2. Assign Client to the Logical System SALE(SCC4)

3. Maintain RFC Destination - SM59

4. Assign RFC Destination to Receiver Logical System -BD97

5. Create Distribution Model - BD64

6. Port Creation - WE21

7. Create partner profile - WE20

8. Distribute the model - bd64(BD82)

Reward if useful.

Regards,

Tanuja.

Message was edited by: Tanuja Sarraju

Message was edited by: Tanuja Sarraju