OSI/MHS Gateway Programmatic Interface (GPI) Programming Guide

EDI Concepts
OSI/MHS Gateway Programmatic Interface (GPI) Programming Guide—424822-001
D-3
EDIMs and X.400
The EDIM body is further divided into one primary body part, and optionally, one or
more additional body parts. The primary body part contains the content of a single EDI
interchange (which may be original or forwarded). Additional body parts contain
information related to the EDI interchange, such as drawings or explanatory text.
The GPI supports X.435 explicitly. It provides attributes and object classes that
conform closely to X.435 protocols. Using the GPI you can encode an EDI interchange
as an EDIM for the best means of transfer through the MTS. Table D-1 lists some
EDIM components and the associated GPI object classes.
EDIMs and X.400
Within the MTS, each EDIM is transferred as X.400 message content accompanied by
an envelope that conforms to P1 protocol (Figure D-3). The format of message content
is similar to, but not the same as, a P2 message.
You should be aware that an EDIM is not the only means of transferring an EDI
interchange through the X.400 MTS. Some EDIMS components do not support X.435
Table D-1. EDIM Components and Corresponding GPI Object Classes
EDIM Component GPI Object Class
Heading EDI-C-HEADING
Primary body part EDI-C-BODYPART
Additional body part EDI-C-EDIM-EX-DF-BODYPART
The EDIM itself EDI-C-EDIM
Figure D-2. Relationship Between EDI Interchange and EDIM
906CDT .CDD
EDIFACT
Fields
Related to
Heading
Fields
Related to
Body
EDIM
Heading
Primary Body
Part
Add'l Body Part n
Add'l Info
n
n+1
Add'l Body Part n+1
Content of the Interchange
Information Describing
the Interchange
Information That May
Accompany Content
(Drawings, etc.)