Validate EDI

Validate EDI (XML, Edifact and Ansi X12)  

Functionality

  • Multiupload
    • No data is stored on the server
    • MIME type is detected based on file content
      • It is possible to upload without file extensiom
      • All other files than text (edifact / ansi x12) or xml are skipped / not supported
  • Validate structure (eg schema validation)
  • Validate business logic (eg schematron validation)
  • XSLT Styling, readable document in HTML
  • Calculate content and compare with values in eg an invoice

Milestones

Current task

  • Scoped the project, only a few XML and EDIFACT versions will be implemented
    • OIOUBL (danish adaption of the UBL standard)
    • Peppol BIS
    • Standard eg EDIFACT D96 are considere in a limited version as a start as a proof of concept
    • cXML and xCBL are a possibility
  • Store validation classes / objects in memory cache to use on subsequent requests
  • XSLT transformations uses SaxonHE
    • All stylesheet versions are supported
    • Included stylesheets or XML documents are supported
  • Documentation of source code (XML documentation)
    • SandCastle is used to generate HTML or MD documents
    • Add content documentation to source code

Release

  •  WIP
    • Jun 23: Only local test / development atm, date for a first beta release not estimated
    • Oct 23: Slow process with local test / development, getting closer to a beta release 
    • Dec 23: Testing, prepare for release on VPS with Ubuntu
    • Jan 14: Project running on VirtualBox / Ubuntu 23.10 / NET 8
      • NGINX as Reverse Proxy in fron of Kestrel web server
    • Jan 14: Test memory usage to validate 8 Gb mem limit
    • Jan 23: Released on https://www.validatefile.dk
      • VPS with 2 CPU, 8 Gb mem running Ubuntu 23.10 server and .NET 8
    • Feb 07: Small adjustment, preparation for xCBL and cXML validation, About page added

To do list for project: 

Sandcastle

Use local postman for testing?

Unit test

Check for vulnerability

GDPR (mostly done)

Information or questions: Please contact plykkegaard at gmail dot com

Seeburger: Map from IDOC to Edifact Transactionset

Edit IDOC document properties

Once the IDOC definition is imported in the Mapping Designer make sure to set Max Occurences on the document root (DC1)
Use unlimited (-1) or 9999

  • IDOCs are send from SAP to a queue with append
  • File is read and mapped to edifact
    • Header is set in New Mapping and footer in Mapping End