806 Project Schedule Reporting (003040)

This is the standard X12 003040 spec, with 3 loops and 22 segment positions, as OpenEDI JSON, an ediFabric C# template and an ediFabric Native model. To change it for a trading partner, customize it in the EDI Spec Builder.

Loading the spec…

The spec as an OpenAPI 3 schema with x-openedi-* extensions, for ediFabric Native, ediFabric Cloud and the EDI Spec Builder. Download OpenEDI (43 KB) Generate classes

The ediFabric .NET template, class TS806. It needs the common segments, composites and codes of X12 003040, one download for every transaction in the version. Download C# (1 KB) Common files (185 KB)

The intermediary model ediFabric Native loads with set_map. Download Native (34 KB)

Use the 806 spec in your code

ediFabric .NET

Add the C# template and its common files to your project, or reference the template NuGet package, and read 806 files into TS806 objects. See ediFabric .NET.

ediFabric Native

Map version 003040 to the Native model with set_map, then parse 806 files to JSON from Python, Java, C or C#. See Convert between EDI and JSON.

OpenEDI

Select Customize in Spec Builder to copy the spec under your own name, change it for your partner, and parse files against it in EdiNation, ediFabric Native or ediFabric Cloud. Read about OpenEDI.

Generate 806 classes in Python, Java, Node.js, Go, Rust or C

ediFabric Native returns each 806 as JSON, with the property names of the OpenEDI schema. To work with that JSON as typed objects, generate classes from the OpenEDI file in your language and deserialize the JSON into TS806. Serialize the objects back to JSON to build EDI with ediFabric Native. The classes keep the loops, segments, lengths and code lists, but not the EDI data formats, so validate files with ediFabric Native. Read more in Generate a class from OpenEDI.

Python: datamodel-code-generator. Node.js: openapi-typescript. Java, Go, Rust and C: OpenAPI Generator.

806 structure

Loops and segments of the standard 806, with their usage and maximum repeats.

ID	Name	Usage	Max use
ST	Transaction Set Header	Optional	1
BPP	Beginning Segment for Project Schedule Reporting	Mandatory	1
REF	Reference Numbers	Optional	100
Loop CAL	Calendar	Optional	200
CAL	Calendar	Mandatory	1
QTY	Quantity	Optional	100
DTM	Date/Time Reference	Optional	10000
Loop TID	Task Identification	Mandatory	>1
TID	Task Identification	Mandatory	1
REF	Reference Numbers	Optional	50
DTM	Date/Time Reference	Optional	50
QTY	Quantity	Optional	100
AMT	Monetary Amount	Optional	100
PCT	Percent Amounts	Optional	100
RES	Resource	Optional	100
MIL	Milestone	Optional	1000
MSG	Message Text	Optional	1000
Loop N1	Name	Optional	200
N1	Name	Mandatory	1
N2	Additional Name Information	Optional	1
N3	Address Information	Optional	1
N4	Geographic Location	Optional	1
PER	Administrative Communications Contact	Optional	2
DTM	Date/Time Reference	Optional	10
SE	Transaction Set Trailer	Optional	1