Em Andamento

BOTS EDI (Python) X12 5010 835 to JSON conversion configuration

Functional requirements: Using the BOTS software ([url removed, login to view]), create a BOTS configuration that shall:

1) watch a folder called "input" for new files.

2) read an X12 EDI 5010 835 formatted file from the "input" folder. Use BOTS to read the file to take advantage of automatic processing of the X12 header, delimiters, end of record variations, etc. Do not write a custom file parser - use BOTS for this.

3) stream convert the X12 EDI 5010 835 file to a canonical JSON format. Do not simply pull the whole input file into memory. Use stream processing so the system can scale to larger data sets.

4) it is up to the developer to decide the specific canonical JSON format. We require that the format directly reflect the structure (nested loops, segments) of the X12 EDI 5010 835 file.

5) write the JSON file to a folder called "output"

Nonfunctional requirements:

6) Deliver all code to realize this configuration in a single ZIP file with professional comments.

7) Use efficient processing techniques to scale to 100,000 records in a single X12 5010 835 file.

Example X12 5010 835 file: [url removed, login to view]

Documentation of the X12 5010 835 file format is copyrighted. Many examples of 835 processing can be found on the Internet. BOTS even comes with an example of processing 835 files.

Warm regards. Thanks so much for the help!

One bidder asked what I mean by "canonical JSON format". What I mean is a format of the X12 EDI file in JSON that is standardized, so we have a predictable way to find the segments and loops in the JSON structure for the X12 EDI 835 message. I do *not* mean the definition of Canonical JSON posted here (https://www.npmjs.org/package/canonical-json). I just mean that the representation of the X12 EDI message is done in JSON in a meaningful way. Please keep the questions coming - I am glad to answer them to get as specific as I can get.

A bidder asked about BOTS and the X12 5010 835 format. BOTS already comes with an 835 file reader. You can download it via http://sourceforge.net/projects/bots/files/grammars/x12%20grammars/X12_005010_all_transactions_and_segments.zip/download

Inside the X12_005010_all_transactions_and_segments.zip is a BOTS grammar called 835005010.py.

The grammar format inside 835005010.py is PERFECT to help create the structure of the JSON format for this project output. The file shows the different segments, how many times they can occur (MIN/MAX occurrences), and nesting of objects (perfect for JSON). If you can output the 835 in a JSON format inspired by the below grammar, I will be very happy! I look to the coder to figure out the best way to represent this message in JSON.

Thanks again!

Below is pasted from BOTS grammar file 835005010.py:

structure = [
{ID: 'ST', MIN: 1, MAX: 1, LEVEL: [
{ID: 'BPR', MIN: 1, MAX: 1},
{ID: 'NTE', MIN: 0, MAX: 99999},
{ID: 'TRN', MIN: 0, MAX: 1},
{ID: 'CUR', MIN: 0, MAX: 1},
{ID: 'REF', MIN: 0, MAX: 99999},
{ID: 'DTM', MIN: 0, MAX: 99999},
{ID: 'N1', MIN: 0, MAX: 200, LEVEL: [
{ID: 'N2', MIN: 0, MAX: 99999},
{ID: 'N3', MIN: 0, MAX: 99999},
{ID: 'N4', MIN: 0, MAX: 1},
{ID: 'REF', MIN: 0, MAX: 99999},
{ID: 'PER', MIN: 0, MAX: 99999},
{ID: 'RDM', MIN: 0, MAX: 1},
{ID: 'DTM', MIN: 0, MAX: 1},
{ID: 'LX', MIN: 0, MAX: 99999, LEVEL: [
{ID: 'TS3', MIN: 0, MAX: 1},
{ID: 'TS2', MIN: 0, MAX: 1},
{ID: 'CLP', MIN: 1, MAX: 99999, LEVEL: [
{ID: 'CAS', MIN: 0, MAX: 99},
{ID: 'NM1', MIN: 1, MAX: 9},
{ID: 'MIA', MIN: 0, MAX: 1},
{ID: 'MOA', MIN: 0, MAX: 1},
{ID: 'REF', MIN: 0, MAX: 99},
{ID: 'DTM', MIN: 0, MAX: 9},
{ID: 'PER', MIN: 0, MAX: 3},
{ID: 'AMT', MIN: 0, MAX: 20},
{ID: 'QTY', MIN: 0, MAX: 20},
{ID: 'SVC', MIN: 0, MAX: 999, LEVEL: [
{ID: 'DTM', MIN: 0, MAX: 9},
{ID: 'CAS', MIN: 0, MAX: 99},
{ID: 'REF', MIN: 0, MAX: 99},
{ID: 'AMT', MIN: 0, MAX: 20},
{ID: 'QTY', MIN: 0, MAX: 20},
{ID: 'LQ', MIN: 0, MAX: 99},
{ID: 'PLB', MIN: 0, MAX: 99999},
{ID: 'SE', MIN: 1, MAX: 1},

I agree with one of the bidders that BOTS may not support stream processing of the input file. If it is not possible in BOTS, I do not require it for this project.

Habilidades: Processamento de dados, Javascript, Python, Arquitetura de software, Desenvolvimento de Software

Ver mais: sets in data structure, index data structure, examples of data structure, anthem com, python end, EDI Developer, edi architecture, X12 EDI, json, convert 3 sets, edi bots, python stream, python json, custom parser, parser json, python javascript convert, JavaScript JSOn, help python, edi x12 code, software bots, anthem, json output, JSON Parser, edi 835 x12 parser, index file data structure

Acerca do Empregador:
( 2 comentários ) Des Peres, United States

ID do Projeto: #6801582

Premiar a:


Hi I didn't familiar with X12 EDI and BOTS before this. Seems that it's an old standard and there is not many resources available about it. But what you need is simple, you just need to convert a 835 document to J Mais

$350 USD em 6 dias
(42 Avaliações)

4 freelancers estão ofertando em média $293 para este trabalho


I am an expert in delivering custom scripts and software willing to discuss further about the project specifications .

$252 USD in 5 dias
(98 Comentários)

i can write this python script for BOTS EDI .

$250 USD in 5 dias
(50 Comentários)

A proposal has not yet been provided

$320 USD in 4 dias
(18 Comentários)