AS 4033.9-1998

1 Scope2 Normative references3 Definitions 3.1 Common definitions for MHS 3.2 Common definitions for abstract syntax notation one 3.3 Terms imported from EDI service 3.4 Other EDI definitions 3.4.1 Terms imported from EDI for administration, commerce and transport 3.4.2 Terms imported from United Nations trade data interchange 3.4.3 Terms imported from ANSI X12.5 3.5 EDI messaging system definitions 3.5.1 EDI message store 3.5.2 EDI messaging system 3.5.3 EDI user agent4 Abbreviations5 Conventions 5.1 Terms 5.2 ASN.1 5.3 Conventions for Attribute Types in Table 1 5.4 Conventions for Attribute Types in Table 26 Information objects7 Common data types 7.1 EDIM identifier 7.2 Extensions8 EDI message 8.1 Heading field component types 8.1.1 Interchange recipient/sender 8.2 Heading fields 8.2.1 This EDIM 8.2.2 Originator 8.2.3 Recipients 8.2.4 EDIN receiver 8.2.5 Responsibility forwarded 8.2.6 EDI body part type 8.2.7 Incomplete copy 8.2.8 Expiry time 8.2.9 Related messages 8.2.10 Obsoleted EDIMs 8.2.11 EDI application security elements 8.2.12 Cross referencing information 8.2.13 EDI message type 8.2.14 Service string advice 8.2.15 Syntax identifier 8.2.16 Interchange sender 8.2.17 Date and time of preparation 8.2.18 Application reference 8.2.19 Heading extensions 8.3 Body part types 8.3.1 EDI body part 8.3.2 EDIM body part 8.3.3 Externally defined body parts9 EDI notifications 9.1 Common fields 9.1.1 Subject EDIM 9.1.2 EDI notification originator 9.1.3 First recipient 9.1.4 Notification time 9.1.5 Security elements 9.1.6 EDIN initiator 9.1.7 Notification extensions 9.2 Positive notifications 9.2.1 PN supplementary information 9.2.2 Positive notification extensions 9.3 Negative notifications 9.3.1 Negative notification reason 9.3.2 NN supplementary information 9.3.3 Negative notification extensions 9.4 Forwarded notifications 9.4.1 Forwarded to 9.4.2 Forwarded notification reason 9.4.3 FN supplementary information 9.4.4 Forwarded notification extensionsSection 2 - EDI environment and abstract service definition10 Primary object types 10.1 EDI messaging user 10.2 EDI messaging system11 Primary port types 11.1 Origination port 11.2 Reception port12 Abstract operations 12.1 Origination abstract operations 12.1.1 Originate probe 12.1.2 Originate EDIM 12.1.3 Originate EMIN 12.2 Reception abstract operations 12.2.1 Receive report 12.2.2 Receive EDIM 12.2.3 Receive EDIN13 Abstract errors 13.1 Recipient improperly specified14 Other capabilities15 Secondary object types 15.1 EDI user agent 15.2 EDI message store 15.3 Telematic agent 15.4 Physical delivery access unit 15.5 Message transfer system16 Secondary port types 16.1 Submission port 16.2 Delivery port 16.3 Retrieval port 16.4 Administration port 16.5 Import port 16.6 Export portSection 3 - Procedures17 User agent operation 17.1 Performance of origination operations 17.1.1 Originate probe 17.1.2 Originate EDIM 17.1.3 Originate EDIN 17.2 Invocation of reception operations 17.2.1 Receive report 17.2.2 Receive EDIM 17.2.3 Receive EDIN 17.3 Internal procedures 17.3.1 Acceptance of responsibility 17.3.2 Refusal of responsibility 17.3.3 EDI ForwardingSection 4 - Message store18 Message store operation 18.1 Binding to the MS 18.1.1 Abstract-bind argument 18.2 Abstract-bind result 18.3 Creation of information objects 18.3.1 Mapping of an MHS message in MSTables & Figures

Specifies the message handling application called EDI messaging, a form of message handling tailored for exchange of electronic data interchange information, a new message content type and associated procedures known as P(sub)edi(/sub). It is designed to meet the requirements of users of (EDIFACT), and other commonly used EDI systems. This Standard is identical with and has been reproduced from ISO/IEC 10021-9:1995.

This part of ISO/IEC 10021 is one of a set of standards for message handling. The entire set provides a comprehensive blueprint for a message handling system (MHS) realized by any number of cooperating open systems.NOTE - The Message-Oriented Text Interchange System (MOTIS) was formerly the title of 10021:1990 parts and has been superseded by amendment to become Message Handling Systems (MHS). MHS is also published by the ITU-T as part of the X.400 series of Recommendations.The purpose of an MHS is to enable users to exchange messages on a store-and-forward basis. A message submitted on behalf of one user, the originator, is conveyed by the message transfer system (MTS) and subsequently delivered to the agents of one or more additional users, the recipients. Access units (AU) link the MTS to communication systems of other kinds (e.g., postal systems). A user is assisted in the preparation, storage, and display of messages by a user agent (UA). Optionally, it is assisted in the storage of messages by a message store (MS). The MTS comprises a number of message transfer agents (MTA) which collectively perform the store-and-forward message transfer function.This part of ISO/IEC 10021 defines the message handling application called EDI messaging (EDIMG), a form of message handling tailored for exchange of electronic data interchange (EDI) information, a new message content type and associated procedures known as Pedi. It is designed to meet the requirements of users ofISO 9735 (EDIFACT), and other commonly used EDI systems.This part of ISO/IEC 10021 is one of a series on message handling. ISO/IEC 10021-2 CCITT Recommendation X.402 constitutes the introduction to the series and identifies the other documents in it.The architectural basis and foundation for message handling are defined in still other parts. ISO/IEC 10021-2 CCITT Recommendation X.402 identifies those documents as well.

First published as AS 4033.9-1992.