The EDI Out Bound Process comprises of the following.
- Selection Program
- Message Control
- The Port Definition
- The RFC Destination
- The Partner Profile
WEDI is the main transaction for IDOCs. This has a sub-menu that lists all other transactions.
I will list the transactions related to the above mentioned topics.
1) Message Control:
The transaction NACE will list all the applications that use Message Control. For example
V1 Sales
V2 Shipping
from the NACE transaction you can view the following for the various applications
Condition Records
Procedures
OutPut Types
Access Sequence
Message control is responsible to process various outputs fro example EDI, FAX, Printing and Mail.
2) Port Definition:
Transaction WE21
Port definition is used to determine the following
Transaction SM59
RFC destination is basically the Remote Function Call Destination. RFC destination is used to define access to the EDI subsystem.
Basically it is used to define the following types of connections
4) Partner Profile
Transaction WE20
Basically partner profiles are used to define the following
For establishing EDI process with the business Partners (ex Vendors, Customers) A partner Profile is created for each partner.
I will list the transactions related to the above mentioned topics.
1) Message Control:
The transaction NACE will list all the applications that use Message Control. For example
V1 Sales
V2 Shipping
from the NACE transaction you can view the following for the various applications
Condition Records
Procedures
OutPut Types
Access Sequence
Message control is responsible to process various outputs fro example EDI, FAX, Printing and Mail.
2) Port Definition:
Transaction WE21
Port definition is used to determine the following
- Path and name of the IDOC file at the operating system level
- EDI subsystem subprogram
- RFC Destination
Transaction SM59
RFC destination is basically the Remote Function Call Destination. RFC destination is used to define access to the EDI subsystem.
Basically it is used to define the following types of connections
- R/2 connections
- R/3 connections
- Internal connections
- Logical destinations
- TCP/IP connections
- Connections via ABAP/4 driver
4) Partner Profile
Transaction WE20
Basically partner profiles are used to define the following
- IDOC Type
- Partner Number
- Port
- Message Type
- Process Code
- Mode of communication with Sub-System
- Person to be notified
For establishing EDI process with the business Partners (ex Vendors, Customers) A partner Profile is created for each partner.
No comments:
Post a Comment