docs.intersystems.com
Home  /  Application Development: Using EDI Documents in Productions  /  Routing EDIFACT Documents in Productions  /  Available Tools


Routing EDIFACT Documents in Productions
Available Tools
[Back]  [Next] 
InterSystems: The power behind what matters   
Search:  


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:
Using the EDIFACT Schema Structures Page
The [Interoperability] > [EDIFACT Schemas] page enables you to import and view EDIFACT schema specifications.
To display this page, click Interoperability, click Interoperate, click UN/EDIFACT. Then click UN/EDIFACT Schema Structures and click Go.
On this page, you can do the following:
The table on this page shows the following information:
Also see Importing EDIFACT Schemas Programmatically.”
For information on creating custom schema categories, see Creating Custom Schema Categories in Using Virtual Documents in Productions.
Using the EDIFACT Document Viewer Page
The [Interoperability] > [EDIFACT Document] 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.
To display this page, click Interoperability, click Interoperate, click UN/EDIFACT. Then click UN/EDIFACT Document Viewer and click Go.
For general information on using this page, see Using the Document Viewer Page in Using Virtual Documents in Productions.
Importing SEF Files Programmatically
You can load SEF files programmatically as follows:
  1. Start a Terminal session.
  2. Change to a production-enabled namespace and issue the following command:
    Where filename 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.
  3. 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:
    .INI
    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.
  4. 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.
EDIFACT Classes
For reference, this section lists the classes that InterSystems IRIS provides to enable you to work with EDIFACT documents.
Item Classes Notes
Business services Each of these EDIFACT business service classes uses a different adapter, as indicated by the class name.
Business processes EnsLib.MsgRouter.VDocRoutingEngine This class is the standard virtual document routing process.
Business operations Each of these EDIFACT business operation classes uses a different adapter, as indicated by the class name.
Messages EnsLib.EDI.EDIFACT.Document This is a specialized message class to carry EDIFACT documents as virtual documents.
Search tables EnsLib.EDI.EDIFACT.SearchTable This is a specialized search table class for 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:
For information on other configurable targets, see Reference for Settings.”