topic Re: partner profiles in Application Development and Automation Discussions

partner profiles

Former Member — Fri, 11 Jan 2008 08:15:34 GMT

Hi everybody,

is it necesary to create a partner profile to an abaper...........if it where we create it ?

haaaaaappy pongal

kanny

Re: partner profiles

Former Member — Fri, 11 Jan 2008 08:46:31 GMT

Partner Profile:

A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDoc’s packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.

Define the Partner Profile : T.Code WE20

In the ALE Communication Process the partner Profile to be created is of the oprofile type Logical System (LS).

PARTNERS > PARTNER PROFILE > PARTNER TYPE - LS

PARTNER NO. <give the partner system name>( ex. LERCLNT800)

Note: In the partner profile creation it is essential to maintain the message types that are used for the communication process. Identification of the system to be a sender or receiver is important so that the appropriate Outbound and Inbound parameters are defined.

Outbound Parameters (for the receiver it will be Inbound Parameters)

In the Partner Profile definitions for Outbound Process the Message type, Receiver Port, Basic Type, Out put Mode and Packet Size are to be defined.

Click on 'Add' Button

give the Message type (MATMAS)

give the Receiver Port

give the Basic Type

give the Output Mode and save.

give the Pack Size.

In the Receiving System for an inbound process the partner profile should contain the inbound message type and the process code. Process code is used by the ALE Communication Layer to identify the posting appication program for an Inbound Process.

Reward Points if useful.

Re: partner profiles

Former Member — Fri, 11 Jan 2008 08:50:10 GMT

INBOUND processing the IDOCs are transferred to the interface and stored in te SAP system. The document data is generated in the course of workflow.

In this section the SAP system is made known to the upstream system (startrfc program parameters). Conversele, the upstream system is made known to the SAP System via the port definition.

INBOUND Processing - Create Function Module.

This function module is called when a message type, of the ZINVRV, comes into the receiving system. This needs to be configured. The function module is passed the IDOC as a parameter.

Use the T.code WE19 to test inbound function module in debugging mode.

Use the T.code EW05 to view the IDOCs and their statuses.

Regards.

Re: partner profiles

Kanagaraja_L — Fri, 11 Jan 2008 08:55:02 GMT

Yes...

Logical System name is used to indiacte the application system to which you are ging to send the data.Partner profiles use the above Logical System name to determine the system to which the data is to be sent ie you have to tell wether inbound or outbound.if we are using IDOC to File scenario ,need to menntion the Outbound Parameter in WE20.

Check the Forum to Create PArtner Profile STEPS

Kanagaraja L

Re: partner profiles

Former Member — Fri, 11 Jan 2008 12:19:27 GMT

hi,

Partner profiles declare the communication medium to be used with a partner.

Partner profiles play an important role in EDI communications. They are parameter files which

store the EDI partner dependent information.

When data is exchanged between partners, it is important that sender and receiver agree on the exact syntax and semantics of the data to be exchanged. This agreement is called a partner profile and tells the receiver the structure of the sent file and how its content is to be interpreted.

The following information is defined with the partner profile.

• IDoc type and message type as key identifier of the partner profile

• Names of sender and receiver to exchange the IDoc information for the respective Idoc and message type

• Logical port name via which the sender and receiver, resp. will communicate

If you exchange e.g. sales orders with partners, you may do this via different media

with different customers. There may be one customer to communicate with you via

TCP/IP (the Internet) while the other still insists on receiving diskette files.

They must be defined for every R/3 client individually. They cannot be transported

using the R/3 transport management system. This is because the profile contains the

name of the sending system, which is naturally different for consolidation and

production systems.

The profiles allow you to open and close EDI connection with individual partners

and specify in detail which IDocs are to be exchanged via the interface.

The profile is also the place to lock permanently or temporarily an IDoc

communication with an EDI partner. So you shut the gate for external

communication with the profile.

Partner profiles define the type of data and communication paths of data to be exchanged between partner

For any combination of message type and receiving partner, a profile is maintained.

The communication media is assigned by the profile Profiles cannot be transported

Profiles define the allowed EDI connections

Profiles can also used to block an EDI communication

The transaction WE20 is used to set up the partner profile.

The profiles are defined with transaction WE20, which is also found in the EDI master menu WEDI. From there you need to specify partner and partner type and whether you define a profile for inbound or outbound. Additionally, you may assign the profile to a NAST message type.

The partner type defines from which master data set the partner number originates.

The partner types are the ones which are used in the standard applications for SD,MM or FI. The most important types for EDI are LI (=Lieferant, supplier), CU (Customer) or LS (Logical system). The logical system is of special interest when you exchange data with computer subsystems via ALE or other RFC means.

For every partner and every direction of communication, whether you receive or send IDocs, a different profile is maintained. The inbound profile defines the processing routine. The outbound profile defines mainly the target, where to send the data .

If you send IDocs out of an application’s messaging, i.e. a communication via the NAST table, then you have to link the message type with an IDoc profile. This is also done in transaction WE20.

The processing code is a logical name for the processing function module or object method. The processing code is used to uniquely determine a function module that will process the received IDoc data. The inbound profile will point to a processing code.

reward if helpful

regards,

sravanthi

Re: partner profiles

former_member313782 — Fri, 11 Jan 2008 20:48:36 GMT

Hi Kanny,

Defining a Partner Profile

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

Use

The partner profile contains parameters that define the electronic interchange of data with a partner via that IDoc interface.

Check this link for deatils.

[http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b809b43d711d1893e0000e8323c4f/content.htm]

[http://download-uk.oracle.com/docs/cd/B14099_19/integrate.1012/b14061/processing.htm]

Partner Profile : t/code is WE20.

This is very important configuration for establishing communication settings between 2 business partners.

With whom we are exchanging information, their details we need to maintain

i.e

Partner Number

Partner Type

Partner Function

Message Type

Process Code

Reciever port

..........

These all details need to be maintainded in Partner Profile.

the partner profiles are client dependent and must be configured in each client that ALE is used.

Hope this wiill be helpful to you,

Regards,

Jose

Re: partner profiles

Former Member — Fri, 11 Jan 2008 20:52:49 GMT

Hi Kanny,

Yes you have to create partner profile in order to send an IDOC.

For the steps to create the partner profile check the below link.

http://forum.saptechies.com/viewtopic.php?p=6824&sid=42ab835afe136bcbd65f09e0f8d367b5

Re: partner profiles

Former Member — Fri, 11 Jan 2008 21:29:38 GMT

Hi Kanny,

It is neccessary to create a partner profile to send and idoc.

Definition of parameters for the electronic interchange of data with a trading partner using the IDoc interface.

To communicate with a partner using the IDoc interface, you must have a partner profile.

Different partners may speak different languages. While the information remains the same, different receivers may require completely different file formats and communication protocols.

This information is stored in a partner profile.

In a partner profile you will specify the names of the partners which are allowed to

exchange IDocs to your system. For each partner you have to list the message types

that the partner may send.

For any such message type, the profile tells the IDoc type, which the partner expects

for that kind of message.

For outbound processing, the partner profile also sets the media to transport the data to its receiver, e.g.

• an operating system file

• automated FTP

• XML or EDIFACT transmission via a broker/converter

• internet

• direct remote function call

The means of transport depends on the receiving partner, the IDoc type and message

type (context).

Therefore, you may choose to send the same data as a file to your vendor and via

FTP to your remote plant.

Also you may decide to exchange purchase data with a vendor via FTP but send

payment notes to the same vendor in a file.

For inbound processing, the partner profile customizsng will also determine a

processing code, which can handle the received data.

Steps to define a partner profile :

Run the we20 transaction.

The Partner profiles window is displayed.

In the left pane, expand Partner type LS and select the logical system you configured from the list, for example, ORACLETDS.

In the right pane, the Partn.number field refers to the name of the logical system

Click Save.

From the Inbound parameters table, click the Create inbound parameter icon.

The Partner profiles: Inbound parameters window is displayed.

Partner profiles : Inbound parameters.

In the Message type field, enter the message type you want to use, for example, MATMAS.

You can click the icon to the right of each field to browse from a list of available message types.

The Inbound options tab is selected by default.

In the Process code field, enter the process code you want to use, for example, MATM.

You can click the icon to the right of each field to browse from a list of available process codes.

In the Processing by function module area, select one of the following options:

Trigger by background program.

In this case the adapter writes IDocs to the SAP database, which is processed immediately.

Trigger immediately.

In this case, the adapter waits for the SAP system to process IDocs. This can take anywhere from 1 to 15 minutes.

Click Save.

Regards,

Kashyap

Re: partner profiles

former_member313782 — Sat, 12 Jan 2008 13:34:47 GMT

Hi again,

Please follow the steps to configure partner profile.

First you need to maintain partner function.

1. go to NACE

2. select Application type

3. Click on "Output types"

4. Select required output type entry.

5. Double click on "Partner Functions"

6. Go to change mode & click "New Entries" button

7. Make a new entry with following values:

a) Medium: EDI

b) Function: as per your requirement

8. Press enter. Name will appear automatically.

9. Back.

You need to maintain 2 partner profiles.

1. Sender

2. Receiver

Tcode: WE20

1. Configuring Sender Partner Profile

a) Under "Partner Profile", you will find different partner types.

b) Expand required partner type.

c) Click on Sender's Partner Number (Eg. TEMCLNT100)

d) go to change mode.

e) In Outbound Parameters table, click on "+" sign to add new entry.

f) In "Outbound Option" tab Enter Message Type.

g) Enter Receiver Port.

h) Output mode: Transfer IDoc Immed.

i) Enter Basic Type.

j) In "Message Control" tab make a new entry.

k) Enter Application, Message Type and Process Code (Eg. QCERT_OUT)

l) Keep checkbox unchecked.

m) Go back and Save.

1. Configuring Receiver Partner Profile

a) Under "Partner Profile", you will find different partner types.

b) Expand required partner type.

c) Click on Receiver's Partner Number.

d) go to change mode.

e) In Inbound Parameters table, click on "+" sign to add new entry.

f) Enter Message Type.

g) Enter Process Code (Eg. QCERT_IN)

h) Back and Save.

Hope this will help you.

And here aer some additional T codes related to IDOC's.

• Bd87 is the transaction for manual processing of idoc.

• WE47 is for viewing all idoc status information.

• WE 20 Maintain partner profiles manually

• BD82 Generate partner profiles automatically

• WE21 Port definitions

• SM59 RFC Definitions

• BD64 Customer Model

• WE19 Test tool for Idocs

• WE02 Idoc Display

• WE05 Idoc list

• WE60 Idoc documentation

• WE 31 Segment Editor

• WE 30 Idoc editor to create and extend IDoc

• WEDI Main menu for EDI related activities

• BALE Main menu for ALE related activities

• SALE Main Menu for ALE Configuration

Kindly reward if useful,

Regards,

Jose