ports

Former Member — Wed, 23 Jan 2008 09:18:44 GMT

can any one explain me what is port? why should we define port?

what is a message type?

what is a partner porfile why should we define it?

thanks

alka

Re: ports

Former Member — Wed, 23 Jan 2008 09:36:25 GMT

Hi!!

Actually ports helps in asynchronous communication.Actual communication is through ports only.Every idoc u send is first received by the port only.creation of ports is done through WE21.

Partner profile is Created because if the communication has to be done it needs the destination.so before sending idocs we have to define partner profile.creating parter profile we use BD54.

It is created for all partners who enable business like banks,marketing agencies etc.

@mit.

Re: ports

Former Member — Wed, 23 Jan 2008 09:39:19 GMT

Basic Type:

Basic IDoc type defines the structure and format of the business document that is to be exchanged between two systems.

Segments:

Segments form the basic building blocks of an IDoc type and are used to store the actual datta. A segment type is the name of a segment and is independent of the SAP elease. A segment definition is the release-specific name of a segment.

Steps in creating Segments:

T.Code WE31

Enter the name for your segment type and click on the create icon.

Type the Short text.

Enter the variable names and data elements.

Save and Go back.

Go to Edit -> Set Release.

Repeat the steps to create more segments.

IDOC TYPE:

Business data is exchanged with an external system using the IDoc Interface.

IDoc types (Special Structures) An IDoc type is defined through its permitted segments. Segments can be dependent on each other (parent and child segments). The IDoc interface can check for each IDoc whether thhe segments contained are compatible with thhe definitiion of its type. This systax check is activated or deactivated in the Partner Profiles.

Steps in creating IDoc Type:

T.Code WE30 to create IDoc Type.

Enter the Object Name, Select Basic Type and click Create Icon

Select the create new option and enter a description for your basic IDOC type and press enter

Select the IDoc name and click Create icon

The system prompts us to enter a segment type and its attributes

Choose the appropriate values and press enter

The system transfers the name of the segment type to the IDoc editor.

Follow these steps to add more number of segments to Parent or as Parent-child relation.

Save it and go back.

Go to Edit -> Set Release.

Message Type:

Steps in Creating Message Type:

T.Code WE81.

change the details from Display mode to Change mode

After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.

Click New Entries to create new Message Type.

Fill details

Save it and go back.

Assign Message Type to IDoc Type:

T.Code WE82

Change the details from Display mode to change mode.

After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.

Click New Entries to create new Message Type.

Fill details

Save it and go back.

Partner Profile:

If you go to WE20 and see any one partner profile you will get idea.

It defines which are the inbound and outbound message type, IDOC type to be used, the port defination, how to transfer IDOC, what is the processing code etc.

Port Definition

The port definition defines the medium in which data is exchanged between the two systems in the ALE process, IDocs are transferred via memory. Six port types are available.

• Transactional RFC (tRFC) ports used for ALE communication.

• File ports used by EDI

• CPI-C ports 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.

Port Settings

Implementation Guide for R/3 Customizing (IMG) - Basis Components - Application Link Enabling (ALE) - Sending and Receiving Systems - Systems in Network - Asynchronous Processing

- Define Number Range for Ports

- Define Port

Transaction: Port Definition WE21

Port Definition

The port defines the technical characteristics of the connection between SAP and the Subsystem. It also defines the medium in which data is exchanged between the two systems. In the EDI process, IDocs are transferred to external systems via ports. The EDI processes use the file port. The type of port also depends on the receiving side. If the receiver cannot accept data in the medium used by a port, the port cannot be used. For example, the tRFC port cannot be used for EDI unless the receiving subsystem has support for tRFC.

Types of Ports

Port Function

Transactional RFC Used for ALE Communication

File Used by EDI

CPI-C Used to communicate with R/2 system

Internet Used to connect with Internet Application

ABAP-PI Used for Custom IDoc processing via ABAP Programming Interface

XML Used for processing files in IDoc/XML format

A port is a client-independent object. The parameters specified for port definitions are

Port: The port name is any meaningful name that uniquely identifies the port.

Description: This is for documentation purpose only.

Version: The internal structure of the IDoc has changed in every major release.

Reward points if useful.

topic Re: ports in Application Development and Automation Discussions

ports

Re: ports

Re: ports