IDOC- PORT CREATION

[Former Member]

Hi all,

1. How to create the port.

2.wats the need of creating port.

3.port has to created for outbound or indound .

please give me the relevent answer.

[Former Member]

Hi Suprith,

You can create a port from transaction WE21.

When the SAP system needs to transfer IDocs to (outbound) or receive IDocs from (inbound) - it needs to know how to communicate with the "other" system. This data, e.g. RFC destination of the communicating system is stored in ports and IDoc communication occurs through ports.

Type of port defines the type of "other" system with which SAP communicates and how it can communicate.

Inbound/Outbound is explained in previous to last para.

Hope this basic explanation helps.

Regards,

Aditya

[Former Member]

hi suprith,

1)go to t-code we21,to create a port.

2)Ports are a fundamental requirement for communicating by means of the IDoc Interface.

IDoc data can be sent and received through a multitude of different media. In order to decouple

the definition of the media characteristics from the application using it, the media is accessed

via ports.

A port is a logical name for an input/output device. A program talks to a port which

is presented to it with a common standard interface. The port takes care of the

translation between the standard interface format and the device dependent format.

Instead of defining the communication path directly in the partner profile, a port

number is assigned. The port number then designates the actual medium. This

allows you to define the characteristics of a port individually and use that port in

multiple profiles. Changes in the port will then reflect automatically to all profiles

without touching them.

Typical ports for data exchange :

• Disk file with a fixed name

• Disk file with dynamic names

• Disk file with trigger of a batch routine

• Standard RFC connection via TCP/IP

• A network channel

• TCP/IP FTP destination (The Internet)

• Call to a individual program e.g. EDI converter

Every application should send or receive its data via the logical ports only. This

allows you to easily change the hardware and software used to make the physical

I/O connection without interfering with the program itself.

The transactions used to define the ports are

• WE21 to create the port and assign a logical

name, and

• SM59 to define the physical characteristics of the I/O device used.

regards,

sravanthi

[former_member667836]

Hi surprith,

check this..

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.

Message Edited by

shibu kurian

[Former Member]

Hi Suprith,

1.Creation of posts

To establish an RFC connection using the port maintenance in the IDoc adapter, proceed as follows:

1. Call the transaction Port Maintenance in IDoc Adapter (IDX1).

On the left-hand side the system displays a list of ports that are already defined, for example SAPABC_123, and a description.

2. Choose Create to create a new port (a new RFC connection) for the selected system.

The system converts the display area on the right-hand side of the screen into an input area where you can enter the specifications for the new port.

3. Enter the required data for the new port and save the data.

The system creates the new entry and places it alphabetically in the list of already defined ports. The system displays a corresponding message.

2.Need of creating post.

You use the port maintenance in the IDoc adapter to establish an RFC connection to the system that contains the metadata that the IDoc adapter requires to convert IDocs (Intermediate Documents) that have been sent to it to IDoc XML format. This system is defined by the sender port and the client in the IDoc control record. It is either the sender SAP system or an SAP reference system.

The metadata comprises the IDoc structures for the corresponding IDoc types. Using this port you can call this data either directly at runtime or you can load it to the Integration Server (the system with the IDoc adapter) beforehand.

You must maintain a port in the IDoc adapter for all clients in each SAP system that you want to connect to the Integration Server using IDocs.

This is also the case for receiver systems if they are subsystems (non-SAP systems). Systems of this kind are defined using the receiver port in the respective communication channel.

3.Creation for outbound or inbound.

Their should be two ports each for both inbound and outbound , it can be treated as sender port and reciever port.

Reward if useful.

Thankyou,

Regards.