The .SEMREFS section lists all semantic rules in the SEF file, each showing the semantic object that it is attached to.  The semantic objects can be a data segment, composite element or data element that are used within the context of an ASC/X12 Transaction Set or UN/EDIFACT Message.  The state of these semantic objects can dynamically change depending on how the semantic rule that is attached to the object is satisfied.

For an example in ASC/X12, if the following semantic rule states:

if element 309 in segment TAX at 070 is equal to "M" then segment CTP at 090 must be used

The semantic object that is affected by the semantic rule is clearly "segment CTP at 090".  The semantic object  is attached to the semantic rule and, regardless of what the default state is of the semantic object, if the condition "element 309 in segment TAX at 070 is equal to M" is satisfied then the semantic object "segment CTP at 090" inherits the state "must be used".

In the .SEMREFS section, the semantic rule may be represented as follows:

850/8///=[TaxVar'EQ'M:USAGE:0:]

Where:

• "850/8///" is the location of the semantic object that is dependent on the semantic rule.  This semantic object is data segment CTP at position 090 in the ASC/X12 Transaction Set.  For additional information on object location refer to Appendix A: Object Location.
• "[TaxVar'EQ'M:USAGE:0:]" is the semantic rule.

The Semantic Rule Syntax

The syntax of the semantic rule consists of:

1. A condition clause statement.
2. An action statement.

The form of the entire semantic rule syntax:

• <semantic rule> := <conditional clause> ":" <action statement>
• <conditional clause> := <logical statement> [ "&" | "|" <conditional clause>]
• <logical statement> := <object variable> <operator> <literal value>
• <action statement> := <setting action> | <external routine action>
• <setting action> := <type> ":" <setting> ":"
• <external routine action> := <exit name> ":" <external program> ":" <parameters>
• <external program> := <program name> "." <function>

The Conditional Clause

The conditional clause is made up of a series of logical statements, the result, if true, would invoke the action statement.   A single logical statement follows the syntax:

logical statement := <Object Variable> <Operator> <Literal Value>

Where:

• Object Variable is an object variable that references an object in the SEF.  The object could be a data segment, a composite element or a data element.
• Operator is one of the following, in quotes.
  • 'EXISTS' - Data exists in the object referenced by the Object Variable.
  • 'NEXIST' - Data does not exist in the object referenced by the Object Variable.
  • 'EQ' - Data referenced by the Object Variable is equal to the value.
  • 'NE' - Data referenced by the Object Variable is not equal to the value.
  • 'GT' - Data referenced by the Object Variable is greater than the value.
  • 'GE' - Data referenced by the Object Variable is greater than or equal to the value.
  • 'LT' - Data referenced by the Object Variable is less than the value.
  • 'LE' - Data referenced by the Object Variable is less than or equal to the value.
• Literal Value is any value.

Using the example above, the following condition of the semantic rule states that the value referenced by the object variable "TaxVar" is equal to the literal value "M".

TaxVar'EQ'M

Where:

• "TaxVar" is the object variable that is attached to element 309 in segment TAX at 070.
• 'EQ' is the equal to operator.
• "M" is the literal value.

Multiple Conditional Clause

If multiple logical statements are required in the conditional clause then they are separated by the "&" or "|" boolean type operator for "AND" or "OR" respectively.

<conditional clause> := <logical statement> [ "&" | "|" <conditional clause>]

For example,

TaxVar'EQ'M|CurVar'EQ'U&RefVar'NE'ABC

which means: TaxVar is equal to "M" OR CurVar is equal to "U" AND RefVar is not equal to "ABC".  In a semantic rule, the conditional clause always precedes the action statement.

TaxVar'EQ'M|CurVar'EQ'U&RefVar'NE'ABC:USAGE:0:

The Action Statement

The action statement indicates what action to take if the result of the conditional clause is true.  Currently, only the following types of actions are possible:

• USAGE - Dynamically set the user requirement of a data segment, composite element or data element to the following:
• LOCALCODE - Redirect the data element to use a different set of codes.
• APPVALUE - Redirect the data element to use a different list of values.
• COMEXIT - Run an ActiveX/COM component.  Other exit names are allowed in the SEF standard, but the SEFManager only allows COMEXIT type executable routines, which are ActiveX/COM components only.

For USAGE, LOCALCODE or APPVALUE, the type must be specified followed by the setting:

<type> ":" <setting> ":"

Example,

USAGE:0:

LOCALCODE:2:

APPVALUE:DUNS:

Note:  There must be a trailing colon (":").

For COMEXIT, the program name is the program identifier of the interface and the method name to execute, followed by any parameters.

"COMEXIT" ":" <program name> ":" <parameters>

Example,

COMEXIT:FrediTester.Sample.Test:1,2,3,ABC

Where:

• "COMEXIT" is the exit name for the type.
• "FrediTester.Sample.Test" is the program name, which consists of the program identifier "FrediTester.Sample" and the method name to execute "Test".
• "1,2,3,ABC" is the parameter to pass to the routine.