topic Re: DIFFERENCE BETWEEN WE20 AND BD64 in Application Development and Automation Discussions

DIFFERENCE BETWEEN WE20 AND BD64

Former Member — Mon, 15 Oct 2007 07:34:48 GMT

What is the difference between creating partnerprile in WE20 and BD64..

by using both transactions we can create partner profile.. but then what is the difference neween these two.. is there any restriction is there for select the particular thing..

and generating partner profile we are using BD82 .. what is this generating meansing.. why we need to do this.. plz explain briefly..

thansk

Babu

Re: DIFFERENCE BETWEEN WE20 AND BD64

former_member404244 — Mon, 15 Oct 2007 07:46:28 GMT

Hi,

Partners profiles

In SAP, all partners systems involved in a distribution model have a profile. There exist several profile types such as customers profiles, vendors profiles, ... but this distinction between profiles is generally not necessary and you will create in most cases your partners profiles using a generic Logical System type.

Before entering the settings of the logical systems partners, you have to create them in customizing. Also, each system in the distribution model must be assigned in its own system its own logical system that represents it. This assignment is done at client level and not at system level. This is not easy to explain nor to understand so let's take a simple example. Let's consider we have a simple distribution model made up of a sender system (S01) and a receiver system (R01). We need to transfer data from S01 / client 100 to R01 / client 200. In both the systems, we will define the logical systems S01_100 and R01_200. But in sender system S01, the logical system S01_100 will be assigned to the client 100 while in the receiver system R01, it will be R01_200 that will be assigned to client 200. With such a configuration you see it is even possible to transfer data between two clients from the same system.

A partner profile is used to determine a lot of important settings that will be involved in the data transfer. These settings vary depending on the role of the partner system (sender / receiver) and are defined per message type. A message type is more or less a version independent IDoc type. It is mainly a convenient way of defining settings and identifying IDocs using a criterium independent of the partner system.

For a sender partner system (inbound parameters are filled in), following important settings are set per message type in the partner profile:

A process code used to indicate which function module will be used to convert the IDoc data to SAP data.

The time of input of the IDoc: as soon as the IDoc is created in the system or on request (using program RBDAPP01).

The post processing agent who will have to treat the data input errors if need be. The post processing agent may be either a user or any other HR organizational unit.

For a receiver partner system (outbound parameters are filled in), following settings are specified in the partner profile:

The receiver port to which the data will be sent.

The sending method: one IDoc at a time or by packets.

The IDoc type that will be sent to that partner. For a given message type, the IDoc type sent may vary depending on the receiver system. Indeed you may have different versions of SAP in your system landscape.

Definition of the distribution model and data filtering

We have already seen that the distribution model is used to decide who sends what to who. But, as you guessed, there is a little bit more to be said about it and the way to manage it.

The distribution model is maintained in a central transaction (BD64) which lets you access the most useful environmental settings necessary to set up the model. Before creating the model, you must first decide on which system you are going to create it. Indeed the model must exist in all partners systems and two possibilities exist to achieve this.

Either you create the model on each system manually (with the same model technical name), which is feasible only with few systems and/or simple models. Either you create it in a specific system (usually the source system) and distribute it to the other systems thanks to the distribution command in the BD64 transaction menu.

If we want to copy the customers master data from the production system to the other systems in the maintenance line for example, we may create the distribution model on the production system and distribute it to all partners systems.

The actual creation of the model requests that you mention a technical name for the model (unique identifier in the systems landscape), a sender system, a receiver system and message types to exchange between those systems. You may afterwards add more sending and receiving systems in the model as well as more message types.

For each message type defined between a sender and a receiver, you may set filters on specific fields of the message type so that IDocs be generated only when these specific values are matched. For example, you may decide to send only customers of a specific account group. These filters are set by selecting the 'no filter set' text under message types in BD64.

There exists also another kind of filters which are segments filters. They do not filter IDocs creation based on values like we have just seen but filter unconditionally segments of created IDocs which must be excluded from the transfer (transaction BD56).

Reward if helpful.

Regards,

Nagaraj

Re: DIFFERENCE BETWEEN WE20 AND BD64

paruchuri_nagesh — Mon, 15 Oct 2007 07:56:37 GMT

babu

WE20 is to generate partner profile manually

it is to specify the charactersic of data that we are going to exchange between the partners

BD64 is to generate model view

here we have to specify

who is the sender and who is the reciever

depends upon the recievers coommunication idocs will be generates

so that idocs can be transfered to the target sysyem

reward if u find use ful

regards

Nagesh.Paruchuri

Re: DIFFERENCE BETWEEN WE20 AND BD64

hymavathi_oruganti — Mon, 15 Oct 2007 07:56:54 GMT

we20---- we can create partner profiles manually by giving all the details like message type and all.

we21- manually generates ports.

BD64--- Automatically generates partner profiles and port. Not only that, we can create model view here.

BD82- Automatically generates ports and partner profiles.

In ale configuration.

no need to go to we21 &we20 or BD82 if you do it in bd64.

Re: DIFFERENCE BETWEEN WE20 AND BD64

Former Member — Mon, 15 Oct 2007 08:04:13 GMT

hi,

We20 -

used for creating a partner profile with inbound and outbound parameters

inbound parameters

process code

message type

partner type

partner no

outbound parameters

message type

partner type

partner no

port no

receiver packet size

BD64 --- use for distributing a partner profile.

i.e the partner profiles which are created at sender side should be distributed to receiver side for idoc transformation for that we ll create a model n add message type to it n distribute to receiver side.

in BD82 -

no facility to create a model view [ we should use the existing model view]

if helpful reward some points.

with regards,

Suresh Aluri.