ale

[Former Member]

what is the difference between generate partner profile and create partner profile in ale.

[Former Member]

Generate partner profile automatically limks rfc with logical systems ... Both should have same names

Create (we20) does not

[paruchuri_nagesh]

hi

generate partner profiles tcode BD82

creating partner profiles tcode WE20

 There are two methods for maintaining the partner profile:

 Maintain partner profile manually:

­ To navigate to the partner profile in the sender system, choose Partner profile -> Partner type of Logical System and click on the required Target system. Under Outbound parameters, choose the Create outbound parameters icon, and enter the values for the outbound parameters according to the slide Sender: Partner Profile (outbound).

­ To navigate to the partner profile in the sender system, choose Partner profile -> Partner type of Logical System and click on the required Sending system. Under Inbound parameters, choose the Create inbound parameters icon and enter the values for the inbound parameters according to the slide Sender: Partner Profile (inbound).

 Generate partner profile:

­ Prerequisite: The current distribution model is distributed to all participating systems.

­ In the sender system, choose: Generate Partner Profile, then check the result in the partner profile (outbound)

­ In the sender system, choose: Generate Partner Profile, then check the result in the partner profile (inbound)

reward if u find useful

regards

Nagesh.Paruchuri

[Former Member]

Hi

<b>Create Partner Profiles</b>Although partner profiles are usually created automatically, because of the unusual inbound and outbound profiles needed on the same system, the manual generation of certain profiles is required.

The following subsections describe the partner profile settings for the standard client (assumed here to be ALExxxCyyy), as well as for the corresponding dummy client (assumed to be DUMxxxCyyy). The dummy client partner profiles should have been generated by the automatic generation process completed previously. Nevertheless, these should be checked to ensure that all profiles exist.

<b>Generation of Partner Profiles</b>

The following messages should be added to the 4xx-ORDR model for ALExxxCyyy to DUMxxxCyyy on the reference client:

• ORDERS

• ORDCHG

• ZINVRV

• ORDRSP

• INVOIC

• FIDCMT

• The partner profiles should first be generated using the standard auto-generation procedure on the reference client (for SYNCH messages to be created).

• This model should now be distributed to the both ALExxxCyyy and DUMxxxCyyy.

• The partner profiles should now be generated on the client being configured (i.e. yyy) using the auto-generation procedure defined in the standard ALE configuration procedures.

Generate partner profiles for sending system. (Can only do this if at least 1 message type exists against the sending system's LS). This automatically generates the port if the LS and RFC name are the same.

reward if usefull

[Former Member]

Hi Sri,

You can setup Customer distribution model using BD64, you can generate Partner profiles from the Menu option there. In this case, SAP uses Port, IDOC Packet Size, IDOC Transfer mode, Notification Agent etc. in the selection screen of this option and uses standard IDOC type etc.

With WE20, you can create Partner profile from scratch or you can update the generated partner profile, if required (For example, if you want to add IDOC extension etc.).

<b>Reward Points if Useful</b>

Regards

Gokul