Sie sind auf Seite 1von 9

CAS Concepts and Solutions AG

Adapter Modul EDIX

Introduction
The Modul converts EDI-Messages to a XML-Message and vice versa The XML-Message ( incomming EDIFACT ) is validated against a Schema It is possible to use different Schemas for each Party and incomming EDIFACT-Messages The XML-Message ( incomming EDI ) is ready for use in the Integration Server Supported EDI-Types are EDIFACT, ANSI X.12 and TRADACOMS

Folie 2

26.05.11

CAS AG

Configuration (1/2) ( e.g. OPI2-Adapter )

Five Modul Parameters are used


Folie 3 26.05.11 CAS AG

Configuration (2/2)

basicXSDFolderPath: defines the Path to the Subfolders for the XML-Schemas defaultXSDFolder: Default-Schemas for all used EDIMessages are storded here exeptionFlag: should an Adapter Execption be thrown in case of a converting/validating Error originalMessageFlag: is the original EDI-Message Part of the XML-Message validateFlag: should the XML-Message be validated against the XSD ( only for EDIFACT )
Folie 4 26.05.11 CAS AG

Partnerspecific Schemas

If you want to use Partnerspecific Schemas (EDIFACT):


The Subfolder named <ILN> must exist In this Subfolder the Partnerspecific Schemas are stored (e.g. INVOIC.xsd) for all used Message Types This XSD has to be unique per EDIFACT-Messagetype and ILN ( Sender )

If you dont want to use Partnerspecific Schemas (EDIFACT):


The Subfolder <ILN> must not exist The Default-Schema regarding the EDIFACT-Messagetype from the Default-Folder is used

Folie 5

26.05.11

CAS AG

EDIFACT-XML-Structure for the SAP PI


<List> <Message> <Sender></Sender> <Receiver></Receiver> <MessageType></MessageType> <XSDPath></XSDPath> <Payload> <List> <UNB></UNB> <UNG></UNG> <M_INVOIC></M_INVOIC> <UNE></UNE> <UNZ></UNZ> </List> </Payload> <Status></Status> <Text></Text> <EDIMessage></EDIMessage> </Message> </List>

Folie 6

26.05.11

CAS AG

Errorcodes
If the EDI-Message is not valid:
no Adapter Exception is thrown ( exceptionFlag = False ) XML-Message is passed always to the Integration Server The Status in the XML-Message is set as follows

Status 0 1 2 3 4 5 6 7 8 99

Text Message is correct Wrong segment EDI contains a line which is not in the XSD declared There are errors in the temp xml file The XSD is not available EDI file is empty EDI file contains more elements in a component than in XSD UNB segment is missing UNH segment is missing UNZ segment is missing No state for this error defined

Folie 7

26.05.11

CAS AG

Monitoring

Monitoring the Commumication Channel (Runtime Workbench) -> only technical Processing Errors in the Modul are supervised, e.g. missing Modul Parameter

Folie 8

26.05.11

CAS AG

Kontakt

Roland Wffen
Geschftsbereichsleiter Industrie RWoeffen@c-a-s.de +49 2131 20111 02 +49 163 53897 02