Upload
barrie-anderson
View
217
Download
0
Tags:
Embed Size (px)
Citation preview
EDIMatrix Ltd 1997
DMX OverviewSEMA Infodata
Nov 1997
EDIMatrix Ltd 1997
Introduction
DMX Modular EDI System
A series of self-standing programs which can be used individually or combined seamlessly to make
the EDI system which suits your needs
EDIMatrix Ltd 1997
Important Modules
DMXCONST - construction DMXTRANS - translation DMXERRAN - session report DMXSCHED - scheduler DMXGWAY - traffic analyser WINTASKS - batch file processor DMXPRINT - flat file re-formatter DMXREFRM - relational file re-formatter
EDIMatrix Ltd 1997
EDIFACT Interchange Structure
(U N G -U N E se ldo m use d)+ d a ta e lem en t+
d a ta e le m e n t: d a ta e le m e n t:
+ com po site+
T A G + seg m e n t '
S e gm e nt G ro up
G ro up
U N H - m e ssa g e - U N T
M e ssa ge M e ssa ge
U N G - F un c tio n a l G rou p - U N E
U N B - In te rch a ng e - U N Z
EDIMatrix Ltd 1997
Segments & Groups
A segment has structure:
TAG+element+element:element+ ….. ’
Within a message sequences of segments can be marked as repeatable. They are then said to form a GROUP.
EDIMatrix Ltd 1997
Data Element
Has properties such as:
Fixed/Variable length Maximum Length Alphanumeric/Alphabetic/Numeric content Mandatory/Conditional
e.g. A6 AN..35 N..14
EDIMatrix Ltd 1997
Separators (Syntax Characters)
Components : Data Elements + Segments ’ Escape Character ?
BUT - can be re-specified by a UNA segment before the UNB
EDIMatrix Ltd 1997
Compression - remove
Trailing blanks Leading zeroes Trailing decimal zeroes +element::+ becomes +element+ +element++’ becomes +element’ NOTE +element::element+ unchanged Sigh! These rules are often broken
EDIMatrix Ltd 1997
Mandatory / Conditional
A Group, Segment, Composite or Data Element may be Mandatory or Conditional
The status of a composite structure is independent of the individual statuses of its components
Violations of these statuses are probably the most common fault in EDIFACT messages
SO - you need to understand them!
EDIMatrix Ltd 1997
A Simple EDI System
D M X E R R A N
W IN R U A
D M X 4 00 A P
D M X G W A Y
D M X C O N S T
W in ta skE X P O R T .T S K
W IN R U A
D M X E R R A N
D M X G W A Y
D M X T R A N S
D M X 4 00 A P
W in ta skIM P O R T .T S K
D M X G W A Y(arch iv ing )
S ch ed u le r
EDIMatrix Ltd 1997
An Even Simpler System
D M X E R R A N
D M X C O N S T
D M X G W A Y
W IN R U A
D M X 4 00 A P
D M X E R R A N
D M X T R A N S
D M X G W A Y
W in ta skE D IR U N .T S K
S C H E D U L E R
EDIMatrix Ltd 1997
Management Information Flow
•Converters•Converters
•Session Log
•Session Log
•ErrorAnalyser
•ErrorAnalyser•Gateway•Gateway
•Network I/F•Network I/F•Database•Database
•Renames•Renames
EDIMatrix Ltd 1997
Outgoing DATA Flow
•Application•Application•Re-formatter•Re-formatter
•DmxConst•DmxConst
EDIMatrix Ltd 1997
Incoming DATA Flow
•DMXTRANS•DMXTRANS
•DMXPRINT•DMXPRINT •APP
•APP
•Interchange Files
•Inhouse Files
EDIMatrix Ltd 1997
DMXGWAY
Most of the operational functionality of a conventional EDI Gateway lies in the DMX converters themselves. The DMX Gateway is therefore primarily a Traffic Analyser whose function is to show you what has been happening in your system, and to tie together the various information sources available to you.
EDIMatrix Ltd 1997
DMXGWAY
View EDI traffic using a query generator Update the traffic database Create and view archives Edit and maintain the database Easy links to all EDI system information
EDIMatrix Ltd 1997
Information Sources
•Session Log
•Gateway Log
•Net I/F Log
•Control Log
•Gateway Reports•Gateway Reports
•Data Files
•Net Reports
•Gateway View•Gateway View
EDIMatrix Ltd 1997
Profiles
Switch the operational environment of the converter according to contents of the incoming data stream.
Based on Trading Partner Based on Message Type Based on Test status (?based on User?)
EDIMatrix Ltd 1997
Profiles
•You only need two profiles to cover all your EDI processing; one for
construction (DMXOUT.PRO) and one for translation (DMXIN.PRO).
Once operating under a profile the converter becomes data-driven, and
switches its environment automatically to respond to the
changing requirements made of it
EDIMatrix Ltd 1997
Profile Logic
M essag e1 M essag e2
P A R T N E R 1F red
M essag e1 M essag e3
P A R T N E R 2Joe
M essag e1 M essag e4 M essag e5
D E FA U LTP A R T N E R
•?
•Use DEFAULT
EDIMatrix Ltd 1997
Table Generation
•Table•Table
•Source•Source
•DMXTCOMP •DMXTDUMP
•DMXTEDIT
•DMXSCOMP
•DMXMKTRN
EDIMatrix Ltd 1997
DMXTEDIT
Interactive Direct Quick Automation Edits, not creates Full sets of UNSM’s Intuitive ? EDI knowledge helps
EDIMatrix Ltd 1997
Control of Conversion
•Converter•Converter
•Profile
•Includes•Codes
•CharConv
•Control File
•Command Line Parms
EDIMatrix Ltd 1997
Control File Contents
Table Input File(s) Output File(s) Flags Moves Profile Semaphores Data
Errorlevels Codes Links Logging Seeds Includes Local Variables ….. More!
EDIMatrix Ltd 1997
Flags
Format ... Error behaviour ... Residence ... Fast/Thorough Debug Imp/Exp Nesting Decimal Separator
Buffering Cache Sizes Profile Triggers Convert Characters Timeslicing Empty File Removal
EDIMatrix Ltd 1997
Network Interfaces
Export - identify files to be sent Connect - call and monitor the network program Import - register incoming files and net reports Update traffic database
EDIMatrix Ltd 1997
Network Interface
Desirable, but not essential! Needed for status recording in traffic
database All DMX network interfaces are
modifications of a single generic model The requirements of the network may need
to be considered at converter control file level
EDIMatrix Ltd 1997
Network Communications
Program to dial a network, establish a session, and perform file transfers as dictated by the Network Interface program
Network specific. DMXCOMMS often used, with a script for
the particular network being accessed Network determines facilities available
EDIMatrix Ltd 1997
Compiled Tables
Several programs in the DMX range operate using compiled tables; the information for them is prepared as a text file which is then compiled to a binary form more suitable for active processing by the program involved.
This is done to separate activities which can be performed off-line from those which are part of the ‘real’ processing.
EDIMatrix Ltd 1997
DMX Compilers
Program Source Compiler Table
Profiling Profile.pro Dmxpcwin Profile.cpr
Dmxrefrm Formlist.rfs Dmxrfcc Formlist.rfc
Dmxprint Printlnk.pls Dmxplcc Printlnk.plc
Dmxefax Faxlist.fxs Dmxfaxc Faxlist.fxc
EDIMatrix Ltd 1997
Application Interface
Intermediary file(s) - Inhouse files DMX can create and accept most formats,
providing they are not too crazy! Convenience for Application decides form Semaphores used to prevent conflicts Hierarchical tagged (flat) file often used Relational filesets also popular
EDIMatrix Ltd 1997
Hierarchical Tagged Files
The most common interface file for applications consists of a hierarchy of different records, each identified by a unique tag.
The hierarchical structure tends to be very similar to that of the EDIFACT interchange
BUT - where the number of iterations of an entity is limited it can often be folded into the level above it.
EDIMatrix Ltd 1997
Relational Files
Essentially equivalent to database tables Each repeating entity has its own file with
a discrete record structure Records in different files are linked by Keys Once again, if an entity has a limited
number of repetitions it is often folded into an existing file
EDIMatrix Ltd 1997
DMX Converter Inhouse Files
Are hierarchical tagged files Re-formatting to and from relational files
can be achieved by the DMXPRINT and DMXREFRM programs
These programs have many other uses! The hierarchical tagged file is, in theory,
inferior to a relational fileset but is, in practice, normally better!