Professional Documents
Culture Documents
EDI
Functional Design
Version 2.2
Page 1 of 7
TABLE OF CONTENTS
1
Version 2.2
Page 2 of 7
1.4 Assumptions
There will be a separate EDI sub-system for each SAP database server;
An asynchronous batch driven interface (not event driven) with minimal
controls will be developed to meet the short to medium term business
requirements;
Telkom will provide the translation mappings from an IDOC to an
EDIFACT message and vice-versa;
Telkom will provide all scripts for the Gentran:Director product i.e.
translation maps, and upload and download scripts;
All inbound IDOCs are appended to a single file per day; and
All operational issues relating directly to the Gentran:Director product
will be dealt with by the EC team.
Version 2.2
Page 3 of 7
Outbound Message
Creation
Creation
1
EDI sub-System
Management &
Control
Sender
Sender
Queue
Queue
2
Transfer
Transfer
Standard or EC
Development
Unattended
scheduler
Translation
((Outbound Script)
4
3
Receiving
Receiving
Queue
Queue
Custom Development
Translation
EDI
EDITranslator
standard
message
Dispatch
VAN
via VAN
Description
1. An EDI IDOC is created (in SAP) and stored in the sender queue at
the UNIX operating system (OS) level;
2. A transfer process is activated that transfers the EDI IDOC from the
sender queue to the EDI sub-system receiving queue;
3. The EDI sub-system control mechanism triggers (based on a
schedule) the EDI translator which retrieves the IDOC file and
translates the IDOCs into an EDIFACT standard message; and
4. The EDI sub-system transmits the EDIFACT message via the VAN.
Architectural Constraints
Version 2.2
Page 4 of 7
1.5.2
Inbound Message
SAP
SAPEDI
EDIimport
import
process
process
Unattended Schedular
Unattended Schedular
5
EDI Sub-System
Management &
Control
Receiver
ReceiverQueue
Queue
Custom Development
Transfer
Transfer
2
4
Sender
SenderQueue
Queue
Translate
Translateinto
into
EDI
EDIstandard
standard
message
message
Standard or EC
Development
1
Transported
Transportedvia
via
VAN
VAN
Description
1. A EDIFACT message is transported via the VAN and stored in the
EDI sub-system;
2. The EDI control mechanism triggers off the translation process which
translates the EDIFACT message into a IDOC message;
3. The EDI translator script stores the SAP IDOC in the sender queue;
4. A transfer process is activated that transfers the EDI IDOC from the
sender queue to the EDI sub-system receiver queue; and
5. The SAP control mechanism triggers (based on a schedule) the SAP
EDI inbound process which retrieves and imports the IDOC into the
SAP system.
Architectural Constraints
Version 2.2
Page 5 of 7
Transfer Function
Only the custom components of the design are described below. The
assumption is that the other components will be provided by the vendor
and/or Telkom.
Requirements
Requirements
Schedule.
File Name :250261104.doc
Print Date :[ 4/25/2002 07:11:00 AM]
Version 2.2
Page 6 of 7
Outputs
Responsibility
Version 2.2
Page 7 of 7