Parse Incoming New Agreement X12 Data

[djfurman]

Background

The post-award tool does not exist in a vacuum, nor is it reasonable to expect that at launch the system, any system will be in a place to use of post-awards own Open Source JSON based RESTful APIs. Therefore, the system must be capable of parsing incoming data into these formats reliably and bubbling up errors in usable states.

Should Support

It is a known state that B2B and some B2C transactions are transmitted by ANSI ASC X12 in the United States and UN UNESCO EDIFACT throughout Europe and the eastern hemisphere.

While numerous proprietary standards have been created over time including XML/SOAP, iDOC, fixed width text, TRADACOM or JSON, the post-award API will process known standards into the post-award open source API.

Acceptance Criteria

• external formatted data can be accepted by the application
• the parser can bubble up errors in parsing/processing
• the parser can support X12 850003050 and X12 850004010
• the parser can be packaged as a composer package
• the composer package can be autoloaded by Laravel 5.5 dependency discoverer

[djfurman]

Explicitly out of scope for this Epic are support for

• Other x12 transaction sets
• Other x12 versions
• Common proprietary XML formats
• Common EDIFACT transaction sets/versions

All of these will be considered for future implementation and can be prioritized by opening an issue for discussion