Routing EDIFACT Documents in Productions
This chapter provides an overview of the InterSystems IRIS™ tools that you can use to work with EDIFACT schemas and documents. It contains the following sections:
On this page, you can do the following:
The table on this page shows the following information:
> UN/EDIFACT Document Viewer
page enables you to display EDIFACT documents, parsing them in different ways, so that you can determine which DocType to use. You can also test transformations. The documents can be external files or documents from the production message archives.
You can load SEF files programmatically as follows:
Start a Terminal session.
Change to an interoperability-enabled namespace and issue the following command:
is the full pathname of the SEF file and EDIFACT
is needed to override the class default value for filetype
This command imports the data from the SEF file and makes it available as a schema definition in InterSystems IRIS.
InterSystems IRIS creates a name for the new schema category from the first piece of the first line in the .INI section of the SEF file. For example, in the file D96A.sef
you might see this:
D96A,,D 96A,UN,D96A,D96A schema
The extracted schema category has the name D96A
Due to the schema naming convention, if you want to edit a SEF file to customize it, InterSystems suggests you first change the text in the SEF file that provides its category name, so that you can distinguish your version from any other SEF file that you also import into InterSystems IRIS.
A SEF file may contain syntax errors. If so, InterSystems IRIS issues an error message and identifies the location of the error in the SEF file.
For reference, this section lists the classes that InterSystems IRIS provides to enable you to work with EDIFACT documents.
You can also create and use subclasses of these classes.
The business host classes include configurable targets. The following diagram shows some of them:
Content Date/Time: 2019-04-23 15:16:12