1 / 34

DMX Overview SEMA Infodata Nov 1997

DMX Overview SEMA Infodata Nov 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. Important Modules. DMXCONST - construction DMXTRANS - translation

nola
Download Presentation

DMX Overview SEMA Infodata Nov 1997

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DMX OverviewSEMA Infodata Nov 1997 EDIMatrix Ltd 1997

  2. Introduction DMX Modular EDI SystemA 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

  3. 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

  4. EDIFACT Interchange Structure EDIMatrix Ltd 1997

  5. 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

  6. Data Element • Has properties such as: • Fixed/Variable length • Maximum Length • Alphanumeric/Alphabetic/Numeric content • Mandatory/Conditionale.g. A6 AN..35 N..14 EDIMatrix Ltd 1997

  7. Separators (Syntax Characters) • Components : • Data Elements + • Segments ’ • Escape Character ? • BUT - can be re-specified by a UNA segment before the UNB EDIMatrix Ltd 1997

  8. 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

  9. 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

  10. A Simple EDI System EDIMatrix Ltd 1997

  11. An Even Simpler System EDIMatrix Ltd 1997

  12. Management Information Flow Converters Session Log ErrorAnalyser Gateway Database Renames Network I/F EDIMatrix Ltd 1997

  13. Outgoing DATA Flow Application Re-formatter DmxConst EDIMatrix Ltd 1997

  14. Incoming DATA Flow Interchange Files DMXTRANS DMXPRINT APP Inhouse Files EDIMatrix Ltd 1997

  15. 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

  16. 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

  17. Information Sources Gateway View Session Log Control Log Gateway Log Data Files Net I/F Log Net Reports Gateway Reports EDIMatrix Ltd 1997

  18. 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

  19. 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

  20. Profile Logic ? Use DEFAULT EDIMatrix Ltd 1997

  21. Table Generation DMXTEDIT Table DMXSCOMP DMXTCOMP DMXTDUMP DMXMKTRN Source EDIMatrix Ltd 1997

  22. DMXTEDIT • Interactive • Direct • Quick • Automation • Edits, not creates • Full sets of UNSM’s • Intuitive ? • EDI knowledge helps EDIMatrix Ltd 1997

  23. Control of Conversion Command Line Parms Converter Control File Profile Includes Codes CharConv EDIMatrix Ltd 1997

  24. Table Input File(s) Output File(s) Flags Moves Profile Semaphores Data Errorlevels Codes Links Logging Seeds Includes Local Variables ….. More! Control File Contents EDIMatrix Ltd 1997

  25. Format ... Error behaviour ... Residence ... Fast/Thorough Debug Imp/Exp Nesting Decimal Separator Buffering Cache Sizes Profile Triggers Convert Characters Timeslicing Empty File Removal Flags EDIMatrix Ltd 1997

  26. 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

  27. 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

  28. 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

  29. 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

  30. DMX Compilers EDIMatrix Ltd 1997

  31. 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

  32. 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

  33. 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

  34. 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! EDIMatrix Ltd 1997

More Related