eddy 0.1.0 → 0.3.0

data/data/004010/segments/ack.segment.yml

@@ -0,0 +1,15 @@
+---
+id: ACK
+name: Line Item Acknowledgement
+purpose: To acknowledge the ordered quantities and specify the ready date for a specific line item
+elements:
+  - { ref: ACK01, id: '668', req: M }
+  - { ref: ACK02, id: '380', req: X }
+  - { ref: ACK03, id: '355', req: X }
+  - { ref: ACK04, id: '374', req: O }
+  - { ref: ACK05, id: '373', req: X }
+  - { ref: ACK06, id: '326', req: O }
+  - { ref: ACK07, id: '235', req: X }
+  - { ref: ACK08, id: '234', req: X }
+  - { ref: ACK09, id: '235', req: X }
+  - { ref: ACK10, id: '234', req: X }

data/data/004010/segments/bak.segment.yml

@@ -0,0 +1,9 @@
+---
+id: BAK
+name: Beginning Segment for Purchase Order Acknowledgment
+purpose: To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifying numbers and date.
+elements:
+  - { ref: BAK01, id: '353', req: M }
+  - { ref: BAK02, id: '587', req: M }
+  - { ref: BAK03, id: '324', req: M }
+  - { ref: BAK04, id: '373', req: M }

data/data/004010/segments/beg.segment.yml

@@ -0,0 +1,17 @@
+---
+id: BEG
+name: Beginning Segment for Purchase Order
+purpose: To indicate the beginning of the Purchase Order Transaction Set and transmit identifying numbers and dates
+elements:
+  - { ref: BEG01, id: '353',  req: M }
+  - { ref: BEG02, id: '92',   req: M }
+  - { ref: BEG03, id: '324',  req: M }
+  - { ref: BEG04, id: '328',  req: O }
+  - { ref: BEG05, id: '373',  req: M, description: The date assigned to the purchase order by the purchaser. }
+  - { ref: BEG06, id: '367',  req: O }
+  - { ref: BEG07, id: '587',  req: O }
+  - { ref: BEG08, id: '1019', req: O }
+  - { ref: BEG09, id: '1166', req: O }
+  - { ref: BEG10, id: '1232', req: O }
+  - { ref: BEG11, id: '786',  req: O }
+  - { ref: BEG12, id: '640',  req: O }

data/data/004010/segments/big.segment.yml

@@ -0,0 +1,10 @@
+---
+id: BIG
+name: Beginning Segment for Invoice
+purpose: To indicate the beginning of an invoice transaction set and transmit identifying numbers and dates.
+elements:
+  - { ref: BIG01, id: '373', req: M }
+  - { ref: BIG02, id: '76',  req: M }
+  - { ref: BIG03, id: '373', req: O }
+  - { ref: BIG04, id: '324', req: O }
+  - { ref: BIG05, id: '328', req: O }

data/data/004010/segments/bsn.segment.yml

@@ -0,0 +1,10 @@
+---
+id: BSN
+name: Beginning Segment for Ship Notice
+purpose: To transmit identifying numbers, dates, and other basic data relating to the transaction set.
+elements:
+  - { ref: BSN01, id: '353',  req: M }
+  - { ref: BSN02, id: '396',  req: M }
+  - { ref: BSN03, id: '373',  req: M }
+  - { ref: BSN04, id: '337',  req: M }
+  - { ref: BSN05, id: '1005', req: O }

data/data/004010/segments/cad.segment.yml

@@ -0,0 +1,14 @@
+---
+id: CAD
+name: Carrier Detail
+purpose: To specify transportation details for the transaction.
+elements:
+  - { ref: CAD01, id: '91',  req: O } # FIXME: req probably should be M
+  - { ref: CAD02, id: '206', req: O }
+  - { ref: CAD03, id: '207', req: O }
+  - { ref: CAD04, id: '140', req: X }
+  - { ref: CAD05, id: '387', req: X }
+  - { ref: CAD06, id: '368', req: O }
+  - { ref: CAD07, id: '128', req: O }
+  - { ref: CAD08, id: '127', req: X }
+  - { ref: CAD09, id: '284', req: O }

data/data/004010/segments/ctp.segment.yml

@@ -0,0 +1,19 @@
+---
+id: CTP
+name: Pricing Information
+purpose: To specify pricing information.
+elements:
+  - { ref: CTP01, id: '687', req: O }
+  - { ref: CTP02, id: '236', req: X }
+  - { ref: CTP03, id: '212', req: X }
+  - { ref: CTP04, id: '380', req: X }
+  - { ref: CTP05, id: '355', req: X }
+  - { ref: CTP06, id: '648', req: O }
+  - { ref: CTP07, id: '649', req: X }
+  - { ref: CTP08, id: '782', req: O }
+notes: |
+  1.P0405 - If either CTP04 or CTP05 is present, then the other is required.
+  2.C0607 - If CTP06 is present, then CTP07 is required.
+  3.C0902 - If CTP09 is present, then CTP02 is required.
+  4.C1002 - If CTP10 is present, then CTP02 is required.
+  5.C1103 - If CTP11 is present, then CTP03 is required.

data/data/004010/segments/ctt.segment.yml

@@ -0,0 +1,13 @@
+---
+id: CTT
+name: Transaction Totals
+purpose: To transmit a hash total for a specific element in the transaction set
+notes: http://www.x12.org/rfis/Hash%20Totals.pdf
+elements:
+  - { ref: CTT01, id: '354', req: M }
+  - { ref: CTT02, id: '347', req: O }
+  - { ref: CTT03, id: '81',  req: X }
+  - { ref: CTT04, id: '355', req: X }
+  - { ref: CTT05, id: '183', req: X }
+  - { ref: CTT06, id: '355', req: X }
+  - { ref: CTT07, id: '352', req: O }

data/data/004010/segments/dtm.segment.yml

@@ -0,0 +1,7 @@
+---
+id: DTM
+name: Date/Time Reference
+purpose: To specify pertinent dates and times.
+elements:
+  - { ref: DTM01, id: '374', req: M }
+  - { ref: DTM02, id: '373', req: X }

data/data/004010/segments/envelope/ge.segment.yml

@@ -0,0 +1,7 @@
+---
+id: GE
+name: Functional Group Trailer
+purpose: To indicate the end of a functional group and to provide control information.
+elements:
+  - { ref: GE01, id: '97', req: M }
+  - { ref: GE02, id: '28', req: M }

data/data/004010/segments/envelope/gs.segment.yml

@@ -0,0 +1,13 @@
+---
+id: GS
+name: Functional Group Header
+purpose: To indicate the beginning of a functional group and to provide control information.
+elements:
+  - { ref: GS01, id: '479', req: M }
+  - { ref: GS02, id: '142', req: M }
+  - { ref: GS03, id: '124', req: M }
+  - { ref: GS04, id: '373', req: M }
+  - { ref: GS05, id: '337', req: M }
+  - { ref: GS06, id: '28' , req: M }
+  - { ref: GS07, id: '455', req: M }
+  - { ref: GS08, id: '480', req: M }

data/data/004010/segments/envelope/iea.segment.yml

@@ -0,0 +1,8 @@
+---
+id: IEA
+name: Interchange Control Trailer
+purpose: To define the end of an interchange of zero or more functional groups and interchange-related control segments.
+elements:
+  - { ref: IEA01, id: 'I16', req: M }
+  - { ref: IEA02, id: 'I12', req: M }
+

data/data/004010/segments/envelope/isa.segment.yml

@@ -0,0 +1,22 @@
+---
+id: ISA
+name: Interchange Control Header
+purpose: To start and identify an interchange of zero or more functional groups and interchange-related control segments.
+elements:
+  - { ref: ISA01, id: 'I01', req: M }
+  - { ref: ISA02, id: 'I02', req: M }
+  - { ref: ISA03, id: 'I03', req: M }
+  - { ref: ISA04, id: 'I04', req: M }
+  - { ref: ISA05, id: 'I05', req: M }
+  - { ref: ISA06, id: 'I06', req: M }
+  - { ref: ISA07, id: 'I05', req: M }
+  - { ref: ISA08, id: 'I07', req: M }
+  - { ref: ISA09, id: 'I08', req: M }
+  - { ref: ISA10, id: 'I09', req: M }
+  - { ref: ISA11, id: 'I10', req: M }
+  - { ref: ISA12, id: 'I11', req: M }
+  - { ref: ISA13, id: 'I12', req: M }
+  - { ref: ISA14, id: 'I13', req: M }
+  - { ref: ISA15, id: 'I14', req: M }
+  - { ref: ISA16, id: 'I15', req: M }
+

data/data/004010/segments/envelope/se.segment.yml

@@ -0,0 +1,7 @@
+---
+id: SE
+name: Transaction Set Trailer
+purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments).
+elements:
+  - { ref: SE01, id: '96',  req: M }
+  - { ref: SE02, id: '329', req: M }

data/data/004010/segments/envelope/st.segment.yml

@@ -0,0 +1,12 @@
+---
+id: ST
+name: Transaction Set Header
+purpose: To indicate the start of a transaction set and to assign a control number.
+elements:
+  - { ref: ST01, id: '143', req: M }
+  - { ref: ST02, id: '329', req: M }
+  # - ref: ST03
+  #   id: '???'
+  #   req: O
+  #   description: "This is a reference assigned to identify implementation convention (similar to Version Number in GS08). The reason for this element is that some translators do not let you map to ISA and GS segments. This element will allow a user to map to the version number (e.g. 005010X222A1) if needed. The ST-03 will always take precedence over GS08."
+  #   description: "The ST03 element was added to all of the above transactions.  This element contains the same value as GS08.  Some EDI translation products omit the ISA and GS segments (envelopes) prior to application (ST-SE) processing.  By providing the information from GS08 at this level, it will ensure that the appropriate application mapping is used at translation time."

data/data/004010/segments/hl.segment.yml

@@ -0,0 +1,9 @@
+---
+id: HL
+name: Hierarchical Level
+purpose: To identify dependencies among and the content of hierarchically related groups of data segments.
+elements:
+  - { ref: HL01, id: '628', req: M }
+  - { ref: HL02, id: '734', req: O }
+  - { ref: HL03, id: '735', req: M }
+  - { ref: HL04, id: '736', req: O }

data/data/004010/segments/it1.segment.yml

@@ -0,0 +1,20 @@
+---
+id: IT1
+name: Baseline Item Data (Invoice)
+purpose: To specify the basic and most frequently used line item data for the invoice and related transactions.
+elements:
+  - { ref: IT101, id: '350', req: O }
+  - { ref: IT102, id: '358', req: X }
+  - { ref: IT103, id: '355', req: X }
+  - { ref: IT104, id: '212', req: X }
+  - { ref: IT105, id: '639', req: O }
+  - { ref: IT106, id: '235', req: X }
+  - { ref: IT107, id: '234', req: X }
+  - { ref: IT108, id: '235', req: X }
+  - { ref: IT109, id: '234', req: X }
+  - { ref: IT110, id: '235', req: X }
+  - { ref: IT111, id: '234', req: X }
+  - { ref: IT112, id: '235', req: X }
+  - { ref: IT113, id: '234', req: X }
+  - { ref: IT114, id: '235', req: X }
+  - { ref: IT115, id: '234', req: X }

data/data/004010/segments/lin.segment.yml

@@ -0,0 +1,10 @@
+---
+id: LIN
+name: Item Identification
+purpose: To specify basic item identification data.
+elements:
+  - { ref: LIN01, id: '350', req: O }
+  - { ref: LIN02, id: '235', req: M }
+  - { ref: LIN03, id: '234', req: M }
+  - { ref: LIN04, id: '235', req: X }
+  - { ref: LIN05, id: '234', req: X }

data/data/004010/segments/loop/hl.segment.yml

@@ -0,0 +1,8 @@
+---
+id: HL
+name: Hierarchical Level
+purpose: To identify dependencies among and the content of hierarchically related groups of data segments.
+elements:
+  - { ref: HL01, id: '628', req: M }
+  - { ref: HL02, id: '734', req: O }
+  - { ref: HL03, id: '735', req: M }

data/data/004010/segments/man.segment.yml

@@ -0,0 +1,7 @@
+---
+id: MAN
+name: Marks and Numbers
+purpose: To indicate identifying marks and numbers for shipping containers.
+elements:
+  - { ref: MAN01, id: '88', req: M }
+  - { ref: MAN02, id: '87', req: M }

data/data/004010/segments/n1.segment.yml

@@ -0,0 +1,9 @@
+---
+id: N1
+name: Name
+purpose: To identify a party by type of organization, name, and code
+elements:
+  - { ref: N101, id: '98', req: M }
+  - { ref: N102, id: '93', req: X }
+  - { ref: N103, id: '66', req: X }
+  - { ref: N104, id: '67', req: X }

data/data/004010/segments/n2.segment.yml

@@ -0,0 +1,7 @@
+---
+id: N2
+name: Additional Name Information
+purpose: To identify a party by type of organization, name, and code.
+elements:
+  - { ref: N201, id: '93', req: M }
+  - { ref: N202, id: '93', req: O }

data/data/004010/segments/n3.segment.yml

@@ -0,0 +1,6 @@
+---
+id: N3
+name: Address Information
+purpose: To specify the location of the named party
+elements:
+  - { ref: N301, id: '166', req: M }

data/data/004010/segments/n4.segment.yml

@@ -0,0 +1,9 @@
+---
+id: N4
+name: Geographic Location
+purpose: To specify the geographic place of the named party
+elements:
+  - { ref: N401, id: '19',  req: O }
+  - { ref: N402, id: '156', req: O }
+  - { ref: N403, id: '116', req: O }
+  - { ref: N404, id: '26',  req: O }

data/data/004010/segments/pid.segment.yml

@@ -0,0 +1,10 @@
+---
+id: PID
+name: Product/Item Description
+purpose: To describe a product or process in coded or free-form format
+elements:
+  - { ref: PID01, id: '349', req: M }
+  - { ref: PID02, id: '750', req: O }
+  - { ref: PID03, id: '559', req: O }
+  - { ref: PID04, id: '751', req: O }
+  - { ref: PID05, id: '352', req: X }

data/data/004010/segments/po1.segment.yml

@@ -0,0 +1,14 @@
+---
+id: PO1
+name: Baseline Item Data
+purpose: To specify basic and most frequently used line item data
+elements:
+  - { ref: PO101, id: '350', req: O }
+  - { ref: PO102, id: '330', req: X }
+  - { ref: PO103, id: '355', req: O }
+  - { ref: PO104, id: '212', req: X }
+  - { ref: PO105, id: '639', req: O }
+  - { ref: PO106, id: '235', req: X }
+  - { ref: PO107, id: '234', req: X }
+  - { ref: PO108, id: '235', req: X }
+  - { ref: PO109, id: '234', req: X }

data/data/004010/segments/prf.segment.yml

@@ -0,0 +1,9 @@
+---
+id: PRF
+name: Purchase Order Reference
+purpose: To provide reference to a specific purchase order.
+elements:
+  - { ref: PRF01, id: '324', req: M }
+  - { ref: PRF02, id: '328', req: O }
+  - { ref: PRF03, id: '327', req: O }
+  - { ref: PRF04, id: '373', req: O }

data/data/004010/segments/ref.segment.yml

@@ -0,0 +1,7 @@
+---
+id: REF
+name: Reference Identification
+purpose: To specify identifying information.
+elements:
+  - { ref: REF01, id: '128', req: M }
+  - { ref: REF02, id: '127', req: X }

data/data/004010/segments/sac.segment.yml

@@ -0,0 +1,20 @@
+---
+id: SAC
+name: Service, Promotion, Allowance, or Charge Information
+purpose: To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service,promotion, allowance, or charge.
+elements:
+  - { ref: SAC01, id: '248',  req: M }
+  - { ref: SAC02, id: '1300', req: X }
+  - { ref: SAC03, id: '559',  req: X }
+  - { ref: SAC04, id: '1301', req: X }
+  - { ref: SAC05, id: '610',  req: O }
+notes: |
+  1.R0203 - At least one of SAC02 or SAC03 is required.
+  2.P0304 - If either SAC03 or SAC04 is present, then the other is required.
+  3.P0607 - If either SAC06 or SAC07 is present, then the other is required.
+  4.P0910 - If either SAC09 or SAC10 is present, then the other is required.
+  5.C1110 - If SAC11 is present, then SAC10 is required.
+  6.L130204 - If SAC13 is present, then at least one of SAC02 or SAC04 is required.
+  7.C1413 - If SAC14 is present, then SAC13 is required.
+  8.C1615 - If SAC16 is present, then SAC15 is required.
+  https://www.jobisez.com/edi/documents/elements-codes.aspx?segment=SAC

data/data/004010/segments/sln.segment.yml

@@ -0,0 +1,12 @@
+---
+id: SLN
+name: Subline Item Detail
+purpose: To specify product subline detail item data.
+elements:
+  - { ref: SLN01, id: '350', req: M }
+  - { ref: SLN02, id: '350', req: O }
+  - { ref: SLN03, id: '662', req: M }
+  - { ref: SLN04, id: '380', req: X }
+  - { ref: SLN05, id: '355', req: O }
+  - { ref: SLN06, id: '212', req: X }
+  - { ref: SLN07, id: '639', req: O }

data/data/004010/segments/sn1.segment.yml

@@ -0,0 +1,11 @@
+---
+id: SN1
+name: Item Detail (Shipment)
+purpose: To specify line-item detail relative to shipment.
+elements:
+  - { ref: SN101, id: '350', req: O }
+  - { ref: SN102, id: '382', req: M }
+  - { ref: SN103, id: '355', req: M }
+  - { ref: SN104, id: '646', req: O }
+  - { ref: SN105, id: '330', req: X }
+  - { ref: SN106, id: '355', req: X }

data/data/004010/segments/td1.segment.yml

@@ -0,0 +1,13 @@
+---
+id: TD1
+name: Carrier Details (Quantity and Weight)
+purpose: To specify the transportation details relative to commodity, weight, and quantity.
+elements:
+  - { ref: TD101, id: '103', req: O }
+  - { ref: TD102, id: '80',  req: X }
+  - { ref: TD103, id: '23',  req: O }
+  - { ref: TD104, id: '22',  req: X }
+  - { ref: TD105, id: '79',  req: O }
+  - { ref: TD106, id: '187', req: O }
+  - { ref: TD107, id: '81',  req: X }
+  - { ref: TD108, id: '355', req: X }

data/data/004010/segments/td5.segment.yml

@@ -0,0 +1,11 @@
+---
+id: TD5
+name: Carrier Details (Routing Sequence/Transit Time)
+purpose: To specify the carrier and sequence of routing and provide transit time information.
+elements:
+  - { ref: TD501, id: '133', req: M }
+  - { ref: TD502, id: '66' , req: X }
+  - { ref: TD503, id: '67' , req: X }
+  - { ref: TD504, id: '91' , req: M }
+  - { ref: TD505, id: '387', req: X }
+

data/data/004010/segments/tds.segment.yml

@@ -0,0 +1,10 @@
+---
+id: TDS
+name: Total Monetary Value Summary
+purpose: To specify the total invoice discounts and amounts.
+elements:
+  - { ref: TDS01, id: '610', req: M }
+  # - { ref: TDS02, id: '', req: X }
+  # - { ref: TDS03, id: '', req: O }
+  # - { ref: TDS04, id: '', req: O }
+