Subject:DESADV D96A Schema vs XML inconsistency Author:Oddbjørn Overskott Date:05 Feb 2007 08:37 AM
There is an inconsistency between the XSD schema and the generated XML for a DESADV D96A message. This problem can be demonstrated by converting the enclosed desadv-message to XML using the EDI adapter. You have to disable the "Force error if value not in codelist" option, and set the "Use long element names" option. The generated XML contains a PAC subsegment named PAC03-PackagingDetails, while the XSD specifies PAC02-PackagingDetails and PAC03-PackageType. This applies to StylusStudio 2007 version 735f.
Subject:DESADV D96A Schema vs XML inconsistency Author:Oddbjørn Overskott Date:06 Feb 2007 05:32 AM
Another one in DESADV D96A: For the FTX segment in GROUP_15, the XSD says FTX03-TextReference and FTX04-TextLiteral, while the generated XML contains FTX04-TextReference.