Inhaltsverzeichnis

Analysator Typen

eBiss.Api.ITypedEntityAnalyzer

FIXME

eBiss.ClassLib.Analyzers.AnsiX12EntityAnalyzer

FIXME

eBiss.ClassLib.Analyzers.AnsiX12EntityAnalyzerEx

FIXME

eBiss.ClassLib.Analyzers.ediBoxInhouseEntityAnalyzer

FIXME

eBiss.ClassLib.Analyzers.EdifactEntityAnalyzer

FIXME

eBiss.ClassLib.Analyzers.FlatFileAnalyzer

FIXME

eBiss.ClassLib.Analyzers.IDataBoundEntityAnalyzer

FIXME

eBiss.ClassLib.Analyzers.InternalXmlEntityAnalyzer

FIXME

eBiss.ClassLib.Analyzers.JsonTypeAnalyzer

FIXME

eBiss.ClassLib.Analyzers.RepositoryTypeAnalyzer

FIXME

eBiss.ClassLib.Analyzers.SoapXMLTypeAnalyzer

FIXME

eBiss.ClassLib.Analyzers.VDAFlatFileAnalyzer

FIXME

eBiss.ClassLib.Analyzers.XMLTypeAnalyzer

FIXME

eBiss.ClassLib.Analyzers.XMLTypeAnalyzerEx

Compared to the regular XMLTypeAnalyzer, XMLTypeAnalyzerEx allows you to mark and recognize elements in the XML hierarchy as documents. This requires that an element within the XML structure is marked as an envelope (interchange) of the document using the MapInterchangeRecord attribute. Afterwards, an element that is located as deep as you like in the XML structure can be marked as a document using MapTrigger attribute. All higher-level elements of the trigger up to the root of the structure must then be provided with a MapTriggerParent attribute to mark the path to the trigger.

sample structure: 

<root>
  <header>[MapInterchangeRecord] (Hinzugefügt in der Definition des Map-Objekts) 
    ...
  </header> 
  <body> [MapTriggerParent]
    ... 
    <documentparent> [MapTriggerParent]
      <document> [MapTrigger]
        ...
      </document>
    </documentparent>
  </body>
</root>

eBiss.Sap.SapIDocAnalyzer

Evaluates the segment EDI_DC40 and enables, for example, partner recognition based on the information in a Custom Interchange Communication Address.
The following data elements are evaluated in the EDI_DC40 segment by the SapIDocAnalyzer.

  1. „DOCNUM“ → document number
  2. „DOCREL“ → document sub type
  3. „IDOCTYP“ → document type
  4. „ILN_HEAD“ → if exists, get the ILN number
  5. „RCVPRN“ → recipient identifier1)
  6. „RCVPRT“ → receiver port 2)
  7. „SERIAL“ → Interchange reference number
  8. „SNDPRN“ → Sender Identifier3)
  9. „SNDPRT“ → Sender Port4)

eBiss.Tradacoms.TradacomsEntityAnalyzer

FIXME

1)
ID2 of a custom interchange address
2)
ID of a custom interchange address
3)
ID2 of a Custom Interchange Address
4)
ID of a Custom Interchange Address