XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Conferences Close Tree View
+ Stylus Studio Feature Requests (1168)
- Stylus Studio Technical Forum (14416)
-> + Unable to auto detect JRE in X... (2)
-> - Unable to auto detect JRE in X... (1)
-> - where to find information (1)
-> + X16 - XPath 3.0, XQuery 3.0, X... (2)
-> - Test (1)
-> + XSLT debugger shows [symbol u... (2)
-> - How do i use *.conv to process... (1)
-> - How do i use *.conv to process... (1)
-> + Not able to configure JVM in ... (5)
-> + Converting Cobol flat file to ... (2)
-> + Problem with uninstall - Windo... (2)
-> + Function current() is not reco... (6)
-> + API or web version (2)
-> + How to use Saxon for X16 on WI... (9)
-> + Error in SS X14 syntax highlig... (2)
-> + Option not available (2)
-> + XML Diff functionality and sor... (3)
-> + Convert Oagis XML file to TXT (4)
-> + DataDirect xqresultsequence is... (2)
-> - xfile Legacy file format suppo... (1)
-- [1-20] [21-40] [41-60] Next
+ Website Feedback (244)
+ XSLT Help and Discussion (7593)
+ XQuery Help and Discussion (1941)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (363)
+ Stylus Studio Announcements (113)
Topic  
Postnext
Jon RobertsSubject: Help needed with SLSRPT - EDIFACT or EANCOM
Author: Jon Roberts
Date: 07 Apr 2017 12:23 PM
I have developed an application for a client using SLSRPT messages. He sent the sample EDI file, which I loaded using the EDI Conversion into Stylus Studio and used as my target.

Now it's in the Production environment, my DataDirect coverters are failing as they see it as an EANCOM file, not an EDIFACT file. We either need to buy a license or used EDIFACT (which our license covers).

As we alse exchange DESADV and RECADV messages in EDIFACT format with this client, it would seem sensible to use that format for the SLSRPT too.

As I start the conversion by working backwards, I need an EDIFACT SLSRPT message to start from, or at least I need to know what the differences are. How does the converter know what the format is?

The obvious difference is this:
<UNH0205><!--0057: Association assigned code-->EAN004</UNH0205>

as that is the only difference in the header I can see between the EANCOM XML file and the EDIFACT one but just removing that line doesn't seem to work. My converter still thinks it's EANCOM and the conversion fails with a license error.

Any suggestions very welcome

Posttop
Ivan PedruzziSubject: Help needed with SLSRPT - EDIFACT or EANCOM
Author: Ivan Pedruzzi
Date: 10 Apr 2017 03:39 PM
We answered this thread offline.

If Jon requires support for EANCOM SLSRPT he will need to acquire the appropriate license.

Considering that most of the messages processed by his application are EDIFACT, may be the data sample provided to him is inaccurate.

We have suggested creating an EDIFACT SLSRPT skeleton using EDI to XML and check if that suffix his requirements.

Hope this helps
Ivan Pedruzzi
Stylus Studio Team

   
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.