Hierarchy
EA-FIN (Software Component) EA-FIN⤷
CA-JVA (Application Component) Joint Venture und Production Sharing Accounting⤷
GJV2 (Package) Joint Venture Development
IMG Activity
| ID | SIMG_ENV_0012 | EDI Port Definition |
| Transaction Code | S_KK4_66000109 | IMG-Aktivität: SIMG_ENV_0012 |
| Created on | 19991013 | |
| Customizing Attributes | SIMG_ENV_0012 | EDI Port Definition |
| Customizing Activity | SIMG_ENV_0012 | EDI Port Definition |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_ENV_0012 |
As part of configuring JVA for EDI, you must define the IDOC Basis interface by defining the EDI port. The port definition specifies the technical characteristics of the connection between the SAP system and the EDI subsystem.
The port definition for JVA EDI consists of the following port types:
- Remote function call (RFC)
- File interface for outbound and inbound EDI
Example
Requirements
Before you can define an RFC for the EDI port, a number range must be specified for the object EDIPORT.
Standard settings
Recommendation
Activities
Define the Remote Function Call (RFC)
To specify the port definition for EDI in JVA, you must define an asynchronous RFC. IDOCs are exchanged with partners' systems by means of RFCs. During transmission the two systems in the interchange determine when responsibility for the transmitted data passes from one partner to the other via the RFC.
In defining an RFC for an EDI port, you must provide a logical destination for the RFC. The system will assign a number to the logical description of the EDI subsystem or port internally.
Define the File Interface
You must also define a file interface for outbound and inbound EDI.
For both outbound and inbound EDI, you should define the following:
- Command file
- Status file
In the command file parameters, you should specify the logical destination of the RFC used in EDI, and you should specify the directory and the file name of the shell script file that controls communication with the EDI subsystem.
In the status file parameters, you should specify the directory and the file name of the file from which status records will be read.
In addition to the command and status file parameters, you should also define either the outbound or inbound file parameters, depending on which applies. In the outbound file parameters, you should specify the directory and file name of the file to which outbound IDOCs will be written. In the inbound file parameters, you should specify the directory and file name of the file from which inbound IDOCs will be read.
Further notes
Business Attributes
| ASAP Roadmap ID | 201 | Make global settings |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| IMGDUMMY | D - Dummy object | WE21 | ENV_0012 | EDI: Maintain Port Definition |
History
| Last changed by/on | SAP | 19991013 |
| SAP Release Created in |
