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.
If the subsystem is installed locally on the SAP server, you will have very few problems because SAP and the subsystem operate under one environment and share a common file system. IDoc files created by the SAP system are automatically available to the subsystem. But, this configuration is not always advisable because of the additional load created on the system.
If the subsystem is installed on a separate server, you must make sure that IDoc files created by SAP are accessible to the EDI subsystem and vice versa. The two options are NFS mounts and remote file copy. Check whether the subsystem can NFS mount the same directory where IDocs are created by SAP.
The transaction code for port creation is WE21 and the path for that is from the Area menu of EDI, choose IDoc, Port Definition.
The EDI process uses 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. Check with your vendor for the port supported.
All vendors support the file port, so don't pick up your phone unless you are interested in using another port. A port is a client−independent object. The following are the parameters specified in a port definition. Figure below shows an example of how to specify the various attributes in a port definition.
The following are the attributes for it.
Port: The port name is any meaningful name that uniquely identifies the port.
Description: Any meaningful description of the port will suffice. This parameter is for documentation purposes only.
Version: You can control the release level of the IDoc being generated by SAP. In SAP, the internal structure of the IDoc has changed in every major release. For example, in release 4.0 and up, the IDoc name can be as long as 30 characters. To support backward compatibility, you set the version of the IDoc to be generated.(64)
Related Posts
EDI RFC set up
EDI basic components configuration part one and two
EDI sub system part one and Two
DELETE FROM DATA
No comments :
Post a Comment