Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Partner profiles ?

Former Member
0 Likes
2,279

what is a Partner profiles ?why r u using this ?explain plzzzz?

i will give the points for better explanation.

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
1,144

Hi ,

After you create the necessary ALE configuration, you can carry out the steps for process

configuration.

1. Create a new message type.

2. Link the message type to the IDoc type.

3. Allocate the function module to the logical message type.

4. Define the attributes for the inbound function module.

5. Create a new process code.

6. Assign input methods

7. Create (or change) a partner profile.

The Port Definition

Transaction: WE21

Path: From the ALE customizing in IMG, choose Sending and Receiving Systems,

Systems in Network, Asynchronous Processing, Assigning Ports, DefinePort.

A port defines the medium in which data is exchanged between the two systems. In the ALE

process, IDocs are transferred via memory. As of release 4.6, six port types are available.

--Transactional RFC (tRFC) :ports used for ALE communication

-- File ports :used by EDI

-- CPI-Cports :used to communicate with R/2 systems

-- Internet ports :used to connect with Internet applications

-- ABAP-PI :ports used to process data via the ABAP programming interface

-- XML ports : used to process files in XML format

NOTE: For port definitions to be generated automatically, the RFC destination

name must be the same as the logical system name.

Port definitions are client-independent objects. The tRFC port used in the ALE process can be

generated automatically when you generate partner profiles, or it can be maintained manually.

Create or Change the Partner Profile

Transaction: WE20

Menu Path: From the Area menu of EDI, choose IDoc, Partner Profile.

A partner profile is created for every partner system with which you exchange IDocs.

In the partner profile, a record is created for every incoming message.

Create a partner profile if it does not exist. Add a record for your incoming message.

. Maintain sending system partner profile (WE20) Client dependent

With this function, you define the partner profiles for all outbound and inbound messages on the basis of the customer distribution model.

After you have defined and distributed the customer model, you will have to maintain the partner profiles locally. To do this read the ALE configuration procedure.

• Enter the output mode (background, immediately) and the package size for outbound processing.

Requirements

• The customer model must be maintained.

• RFC destinations must be maintained.

• The customer model must be distributed.

• To ensure that the appropriate persons in charge are informed if a processing error occurs, you must make settings

A partner profile specifies the components used in an outbound/Inbound process (<b>the logical name of the

remote SAP system, IDoc type, message type, and tRFC port), an IDoc's packet size, the mode</b>

in which the process sends an IDoc (batch versus immediate), and the person to be notified in

case of errors.

A partner profile is created for each SAP system with which you communicate, and a record

exists for each message sent and received from a system. For example, if you are sending two

outbound messages-purchase order (ORDERS) and material master (MATMAS)-to the

SHIPPING system, a partner profile will exist for the SHIPPING system. Two outbound recordsone

for each message type (ORDERS and MATMAS)-will exist in the partner profile.

<b>Reward with points if helpful.</b>

Regards,

Vijay

3 REPLIES 3
Read only

ferry_lianto
Active Contributor
0 Likes
1,144

Hi,

Partner profiles are a prerequisite for data exchange. This involves defining who can exchange messages with the SAP system and using which port.

To define a partner profile, you run transaction WE20.

Regards,

Ferry Lianto

Read only

Former Member
0 Likes
1,144

We must maintain the business partners with whom we communicate via IDocs, in Partner Profiles.

Steps to create Partner Profile

- Goto Transaction WE20.

- Click on Create Button.

- Enter the Number of Vendor Created in Partner No. and ‘LI’ in Partner

Type fields.

- Save the Data.

- For Outbound Partner Profile we have to create Outbound

Parameters

- Specify Partner Function, Message type created, Port (create a port in WE21),Basic Type and Output Mode.

- Goto “Message Control” Tab and link the Message Type and Process

Code created.

- Save.

Read only

Former Member
0 Likes
1,145

Hi ,

After you create the necessary ALE configuration, you can carry out the steps for process

configuration.

1. Create a new message type.

2. Link the message type to the IDoc type.

3. Allocate the function module to the logical message type.

4. Define the attributes for the inbound function module.

5. Create a new process code.

6. Assign input methods

7. Create (or change) a partner profile.

The Port Definition

Transaction: WE21

Path: From the ALE customizing in IMG, choose Sending and Receiving Systems,

Systems in Network, Asynchronous Processing, Assigning Ports, DefinePort.

A port defines the medium in which data is exchanged between the two systems. In the ALE

process, IDocs are transferred via memory. As of release 4.6, six port types are available.

--Transactional RFC (tRFC) :ports used for ALE communication

-- File ports :used by EDI

-- CPI-Cports :used to communicate with R/2 systems

-- Internet ports :used to connect with Internet applications

-- ABAP-PI :ports used to process data via the ABAP programming interface

-- XML ports : used to process files in XML format

NOTE: For port definitions to be generated automatically, the RFC destination

name must be the same as the logical system name.

Port definitions are client-independent objects. The tRFC port used in the ALE process can be

generated automatically when you generate partner profiles, or it can be maintained manually.

Create or Change the Partner Profile

Transaction: WE20

Menu Path: From the Area menu of EDI, choose IDoc, Partner Profile.

A partner profile is created for every partner system with which you exchange IDocs.

In the partner profile, a record is created for every incoming message.

Create a partner profile if it does not exist. Add a record for your incoming message.

. Maintain sending system partner profile (WE20) Client dependent

With this function, you define the partner profiles for all outbound and inbound messages on the basis of the customer distribution model.

After you have defined and distributed the customer model, you will have to maintain the partner profiles locally. To do this read the ALE configuration procedure.

• Enter the output mode (background, immediately) and the package size for outbound processing.

Requirements

• The customer model must be maintained.

• RFC destinations must be maintained.

• The customer model must be distributed.

• To ensure that the appropriate persons in charge are informed if a processing error occurs, you must make settings

A partner profile specifies the components used in an outbound/Inbound process (<b>the logical name of the

remote SAP system, IDoc type, message type, and tRFC port), an IDoc's packet size, the mode</b>

in which the process sends an IDoc (batch versus immediate), and the person to be notified in

case of errors.

A partner profile is created for each SAP system with which you communicate, and a record

exists for each message sent and received from a system. For example, if you are sending two

outbound messages-purchase order (ORDERS) and material master (MATMAS)-to the

SHIPPING system, a partner profile will exist for the SHIPPING system. Two outbound recordsone

for each message type (ORDERS and MATMAS)-will exist in the partner profile.

<b>Reward with points if helpful.</b>

Regards,

Vijay