Description
3010 Transaction Set
Invoice 810
Payment Order/Remittance Advice 820
Purchase Order Acknowledgement 855
Advanced Ship Notice 856
Functional Acknowledgement 997
Description Transaction Number
3010VICS (Voluntary Inter-industry Commerce Standard) Transaction Set 810
820
Purchase Order 850
Product Activity Data 852
Transaction Set and Acknowledgement Support
Description Transaction Number
3020 Transaction Set
Motor Carrier Load Tender 204
Motor Carrier Freight Details and Invoice 210
Invoice 810
Payment Order/Remittance Advice 820
Application Advice 824
Planning Schedule with Release Capability 830
Product Activity Data 852
Purchase Order Acknowledgement 855
Advanced Ship Notice 856
Shipment and Billing Notice 857
Purchase Order Change Request 860
3021 Transaction Set
Routing and Carrier Instruction 853
A. Ebix-Supported Transaction Sets
Description Transaction Number
3030 Transaction Set
Invoice 810
Payment Order/Remittance Advice 820
Purchase Order 850
Purchase Order Acknowledgement 855
Advanced Ship Notice 856
Shipment and Billing Notice 857
Purchase Order Change Acknowledgement 865
Product Transfer and Resale Report 867
Functional Acknowledgement 997
Description Transaction Number
3040 Transaction Set
Invoice 810
Payment Order/Remittance Advice 820
Application Advice 824
Purchase Order 850
Purchase Order Acknowledgement 855
Advanced Ship Notice 856
Shipment and Billing Notice 857
Receiving Advice 861
Shipping Schedule 862
Purchase Order Change Acknowledgement 865
Transaction Set and Acknowledgement Support
Description Transaction Number
Product Transfer and Resale Report 867
Functional Acknowledgement 997
Description Transaction Number
3050 Transaction Set
Invoice 810
Payment Order/Remittance Advice 820
Application Advice 824
Planning Schedule with Release Capability 830
Price/Sales Catalog 832
Purchase Order 850
Purchase Order Acknowledgement 855
Advanced Ship Notice 856
Shipment and Billing Notice 857
Purchase Order Change Acknowledgement 865
Product Transfer and Resale Report 867
Functional Acknowledgement 997
Description Transaction Number
3060 Transaction Set
Return Merchandise Authorization 180
Invoice 810
A. Ebix-Supported Transaction Sets
Description
Product Activity Data 852
Purchase Order Acknowledgement 855
Advanced Ship Notice 856
Shipment and Billing Notice 857
Purchase Order Change Request 860
Purchase Order Change Acknowledgement 865
Functional Acknowledgement 997
Description Transaction Number
3070 Transaction Set
Return Merchandise Authorization 180
Payment Order/Remittance Advice 820
Purchase Order 850
Product Activity Data 852
Purchase Order Acknowledgement 855
Advanced Ship Notice 856
Shipment and Billing Notice 857
Purchase Order Change Request 860
Purchase Order Change Acknowledgement 865
Functional Acknowledgement 997
Transaction Set and Acknowledgement Support
Description Transaction Number
4010 Transaction Set
Air Freight Details and Invoice 110
Return Merchandise Authorization 180
Mortgage Credit Report 200
Motor Carrier Load Tender 204
Motor Carrier Freight Details and Invoice 210
Motor Carrier Shipment Status Inquiry 213
Transport Carrier Ship Status 214
Booking Cancellation (Ocean) 303
Shipping Instructions 304
U.S. Customs Manifest 309
Invoice 810
Consolidated Service Invoice/Statement 811
Organizational Relationships 816
Payment Order/Remittance Advice 820
Financial Information Reporting 821
Application Advice 824
Planning Schedule with Release Capability 830
Application Control Totals 831
A. Ebix-Supported Transaction Sets
Description Transaction Number
Product Activity Data 852
Purchase Order Acknowledgement 855
Advanced Ship Notice 856
Shipment and Billing Notice 857
Purchase Order Change Request 860
Purchase Order Change Acknowledgement 865
Product Transfer and Resale Report 867
Order Status Report 870
Grocery Products Purchase Order 875
Price Information 879
Grocery Products Invoice 880
Item Maintenance 888
Promotion Announcement 889
Delivery/Return Base Record 894
Warehouse Shipping Order 940
Warehouse Stock Transfer Shipment Advice 943
Warehouse Stock Transfer Receipt Advice 944
Warehouse Shipping Advice 945
947
Transaction Set and Acknowledgement Support
Description Transaction Number
Response to a Load Tender 990
4010UCS (Uniform Communication Standard) Transaction Set Invoice
810 812
Purchase Order 850
Product Activity Data 852
Advanced Ship Notice 856
Text Message 864
Grocery Products Purchase Order 875
Price Information 879
Grocery Products Invoice 880
Item Maintenance 888
Promotion Announcement 889
Delivery/Return Base Record 894
Delivery/Return Acknowledgement or Adjustment 895
Functional Acknowledgement 997
A. Ebix-Supported Transaction Sets
Description Transaction Number
4010VICS (Voluntary Inter-industry Commerce Standard) Transaction Set 180
4020 Transaction Set
Invoice 810
Payment Order/Remittance Advice 820
Transaction Set and Acknowledgement Support
Description Transaction Number
4030 Transaction Set 140
Product Service Claim Response 141
Product Service Claim 142
Motor Carrier Load Tender 204
Motor Carrier Freight Details and Invoice 210
Transport Carrier Ship Status 214
Motor Carrier Pick-up Manifest 215
Motor Carrier Package Status 240
Eligibility, Coverage, or Benefit Inquiry 270
Eligibility, Coverage, or Benefit Information 271
Health Care Claim Status Request 276
Health Care Claim Status Notification 277
Health Care Services Review Information 278
Payment Order/Remittance Advice 820
Lockbox 823
Application Advice 824
Planning Schedule with Release Capability 830
Price/Sales Catalog 832
A. Ebix-Supported Transaction Sets
Description Transaction Number
Benefit Enrollment and Maintenance 834
Health Care Claim Payment/Advice 835
Health Care Claim 837
Request for Quotation 840
Response to Request for Quotation 843
Product Transfer Account Adjustment 844
Price Authorization Acknowledgement 845
Response to Product Transfer Account Adjustment 849
Purchase Order 850
Product Activity Data 852
Purchase Order Acknowledgement 855
Advanced Ship Notice 856
Shipment and Billing Notice 857
Purchase Order Change Request 860
Purchase Order Change Acknowledgement 865
Warehouse Shipping Order 940
Warehouse Shipping Advice 945
Functional Acknowledgement 997
Transaction Set and Acknowledgement Support
Description Transaction Number
4030UCS (Uniform Communication Standard) Transaction Set Grocery Products Invoice
880
Delivery/Return Base Record 894
4040 Transaction Set
Product Service Claim Response 141
Product Service Claim 142
Motor Carrier Load Tender 204
Motor Carrier Freight Details and Invoice 210
Transport Carrier Ship Status 214
Motor Carrier Pick-up Manifest 215
Eligibility, Coverage, or Benefit Inquiry 270
Eligibility, Coverage, or Benefit Information 271
Health Care Claim Status Request 276
Health Care Claim Status Notification 277
Health Care Services Review Information 278
Shipping Instructions 304
Vessel Schedule and Itinerary (Ocean) 323
Invoice 810
A. Ebix-Supported Transaction Sets
Description Transaction Number
Payment Order/Remittance Advice 820
Lockbox 823
Planning Schedule with Release Capability 830
Price/Sales Catalog 832
Benefit Enrollment and Maintenance 834
Health Care Claim Payment/Advice 835
Health Care Claim 837
Request for Quotation 840
Response to Request for Quotation 843
Product Transfer Account Adjustment 844
Price Authorization Acknowledgement 845
Response to Product Transfer Account Adjustment 849
Purchase Order 850
Product Activity Data 852
Purchase Order Acknowledgement 855
Advanced Ship Notice 856
Shipment and Billing Notice 857
Purchase Order Change Request 860
Purchase Order Change Acknowledgement 865
Transaction Set and Acknowledgement Support
Description Transaction Number
Grocery Products Invoice 880
Warehouse Shipping Order 940
Warehouse Shipping Advice 945
Functional Acknowledgement 997
Description Transaction Number
4050 Transaction Set
Invoice 810
Purchase Order 850
Advanced Ship Notice 856
Functional Acknowledgement 997
Description Transaction Number
5010 Transaction Set
Air Freight Details and Invoice 110
Return Merchandise Authorization 180
Motor Carrier Load Tender 204
Motor Carrier Freight Details and Invoice 210
Transport Carrier Ship Status 214
Motor Carrier Package Status 240
Invoice 810
Credit/Debit Adjustment 812
A. Ebix-Supported Transaction Sets
Description Transaction Number
Payment Order/Remittance Advice 820
Product Activity Data 852
Purchase Order Acknowledgement 855
Advanced Ship Notice 856
Shipment and Billing Notice 857
Purchase Order Change Request 860
Receiving Advice 861
Text Message 864
Purchase Order Change Acknowledgement 865
Order Status Report 870
Functional Acknowledgement 997
Description Transaction Number
5010UCS (Uniform Communication Standard) Transaction Set Grocery Products Invoice
880
Delivery/Return Base Record 894
994
Functional Acknowledgement 997
Transaction Set and Acknowledgement Support
Description Transaction Number
5020 Transaction Set
Functional Acknowledgement 997
Description Transaction Number
5030 Transaction Set
Eligibility, Coverage, or Benefit Inquiry 270
Invoice 810
Payment Order/Remittance Advice 820
Application Advice 824
Benefit Enrollment and Maintenance 834
Health Care Claim Payment/Advice 835
Health Care Claim 837
Purchase Order 850
Advanced Ship Notice 856
Shipment and Billing Notice 857
Functional Acknowledgement 997
A. Ebix-Supported Transaction Sets
Transaction Set and Acknowledgement Support
iWay
Separators and Terminators
B
Topics:
All EDI documents are embedded with tokens that are separated by special characters called separators and terminators. These separators and terminators are used to identify:
Separators and Terminators
element separators sub-element separators segment terminators
This appendix provides a list of the separators and terminators that are allowed during the configuration of preparsers and preemitters in iWay Service Manager.
Separators and Terminators
Separators and Terminators
iWay
Special Register (SREG) Types
C
Topics:
This section describes the Special Register (SREG) types that are created during EDI to XML transactions and 997 creation.
Special Register (SREG) Types
Special Register (SREG) Types
During EDI to XML transactions and 997 creation, the following types of Special Registers (SREGs) are created:
SYS (System) - These SREGs exist until you restart iWay Service Manager.
USR/DOC - These SREGs exist throughout the life of the document.
CFG - These SREGs are configuration related.
SEGMENT COUNT
1. <variable name="SEGCOUNT" type="USR">20</variable>
2. <variable name="basename" type="DOC">stephan_850_bad</variable>
3. <variable name="console-master-port" type="SYS">9999</variable>
CORRELATION ID
4. <variable name="correlid" type="USR">000001000</variable>
5. <variable name="doclocation" type="SYS">config</variable>
END OF STREAM FLAG
6. <variable name="eos" type="USR">1</variable>
7. <variable name="extension" type="DOC">x12</variable>
8. <variable name="filename" type="DOC">stephan_850_bad.x12</variable>
FROM PARTY
9. <variable name="fromparty" type="USR">NOTP </variable>
GROUP CONTROL NUMBER - GE
10. <variable name="ge_groupctlnumber" type="USR">1000</variable>
NUMBER OF TRANSACTIONS - GE
11. <variable name="ge_numtransactions" type="USR">1</variable>
12. <variable name="ibse-port" type="CFG">9000</variable>
INTERCHANGE CONTROL NUMBER - IEA
13. <variable name="iea_interchangectlnum" type="USR">000001000</variable>
VALIDATION REPORT/ACK Special Register (SREG) Types
14. <variable name="iwaf.validationReport" type="USR">ISA*00* *00*
15. <variable name="iway.eos" type="DOC">true</variable>
16. <variable name="iwayconfig" type="SYS">base</variable>
17. <variable name="iwayhome" type="SYS">C:/Program Files/iway55sm/</variable>
18. <variable name="iwayversion" type="SYS">5.5.012.SM</variable>
19. <variable name="iwayworkdir" type="SYS">C:/Program Files/iway55sm/config/base</variable>
20. <variable name="locale" type="SYS">en_us</variable>
21. <variable name="name" type="SYS">EDI_XML</variable>
NUMBER OF FUNCTIONAL GROUPS
22. <variable name="numfunctionalgroups" type="USR">1</variable>
23. <variable name="parent" type="DOC">c:\testing\edix12\input</variable>
24. <variable name="protocol" type="SYS">FILE</variable>
25. <variable name="source"
type="DOC">C:\testing\edix12\input\stephan_850_bad.x12</variable>
SPLIT COUNT
26. <variable name="splitcount" type="USR">1</variable>
27. <variable name="tid"
type="DOC">EDI_XML-FILE-W.EDI_XML.1_20080605152319600Z</variable>
TRANSACTION ID
28. <variable name=”edi.transactionID” type=”USR”>850</variable>
VERSION
29. <variable name=”edi.version” type=”USR”>004010</variable>
C. Special Register (SREG) Types
Special Register (SREG) Types
iWay
Sample EDI Files
D
Topics:
This appendix includes a sample Electronic Data Interchange (EDI) 4010 850 Purchase Order, 4010 810 Invoice, and 4010 856 Advanced Ship Notice.
These are the key EDI documents in wholesale distribution.
Sample EDI 4010 850 Purchase Order Sample EDI 4010 810 Invoice Sample EDI 4010 856 Advanced Ship Notice
Sample EDI 4010 850 Purchase Order
The following is a sample EDI 4010 850 Purchase Order.
ISA*00* *00* *12*NOTP *12*NOTP
*080501*1700*U*00401*000001000*0*P*>
GS*PO*NOTP*NOTP*20080501*1700*1000*X*004010 ST*850*000000010
BEG*00*SA*08292243254**20010501*610385388 REF*DP*030
REF*PS*
ITD*14*3*2**45**46 DTM*001*20010510
PKG*F*68***PALLET, SHRINKWRAP 48W X 40D X 45H PKG*F*66***REGULAR
TD5*A*92*P3**SEE ROUTING GUIDE FOR ROUTING N1*ST*RETAIL STORE*9*0001234567890
N3*123 ANYWHERE AVENUE N4*CITY*ST*12345
PO1*1*120*EA*9.25*TE*CB*(12) 0-083628-838*PR*RO*VN*ABA18783 PO1*2*220*EA*13.7 9*TE*CB*(69) 0-093 83 7-991*PR*RO*VN*RUP83112 PO1*3*126*EA*10.9 9*TE*CB*(71) 0-099172-837*PR*RO*VN*CPR19293 PO1*4*76*EA*4.35*TE*CB*(71) 0-012110-737*PR*RO*VN*PIW28173 PO1*5*72*EA*7.5*TE*CB*(71) 0-0848 88-9 75*PR*RO*VN*JBM1938 7 PO1*6*696*EA*9.55*TE*CB*(71) 0-003 922-121*PR*RO*VN*IUI19283 CTT*6
SE*20*000000010 GE*1*1000 IEA*1*000001000 Sample EDI 4010 850 Purchase Order
Sample EDI 4010 810 Invoice
The following is a sample EDI 4010 810 Invoice.
ISA*00* *01* *ZZ*NOTP *ZZ*NOTP
*050108*0954*U*00501*000000001*0*P*>
GS*IN*NOTP*NOTP*20050108*0954*1*X*004010 ST*810*0001
BIG*20021119*184*20021015*BMB REF*IA*040682
N1*BT*WALGREEN*92*0000
ITD*02**1.000**30**31*****1% 30 NET 31 FOB*CC
PID*S**VI*FL
IT1*0001*267*CA*53.52**IN*859067
PID*F*08*VI**BARBIE SING W/ME DISC GRL CD PLYR TDS*1421839*1428984
CAD*T***CFWY*CONSOLIDATED FREIGHTWAYS SAC*A*D240***7145**********FREIGHT CHARGE ISS*267*CA
CTT*1 SE*15*0001 GE*1*1
IEA*1*000000001
D. Sample EDI Files
Sample EDI 4010 856 Advanced Ship Notice
The following is a sample EDI 4010 856 Advanced Ship Notice.
ISA*00* *00* *ZZ*NOTP *ZZ*NOTP
*080105*1026*U*00501*100000001*0*P*:
GS*NOTP*NOTP*20080105*1026*1*X*004010 ST*856*0001
BSN*00*PC123456*20071205*1026*0004 DTM*067*20070717
HL*1**S
TD1******A3*5.750*EA*1*1N TD5**S*DHL
REF*BM*PC123456 N1*SF*ACME PHARMA CO
N1*ST*DISTRIBUTION CENTER*92*0001 HL*2*1*O
PRF*PWS6***20080103 HL*3*2*P
MAN*GM*00007287900000256222 HL*4*3*I
LIN*10*UP*72879096026*LT*804813-5 50 Safety Pins*CH*CN CTT*4
SE*17*0001 GE*1*1
IEA*1*100000001
Sample EDI 4010 856 Advanced Ship Notice
iWay
Defining a Route With iWay Designer
E
Topics:
iWay Designer is a Windows-based design-time tool. You can use it to create and publish a process flow that is bound to a channel as a route. Through the process flow, you control the sequence in which tasks are performed and the destination of the output from each task.
Defining a Route With iWay Designer
Defining a Route With iWay Designer
How to:
Create an iWay Designer Project and Start the Process Flow Add a Copy Service Object
Add an End Object for the Copy Service Object Add an Acknowledgement Service Object
Add an End Object for the Acknowledgement Service Object Define a Route and Associate the Process Flow With It
This topic describes how to create a process flow with iWay Designer and bind it to the sample channel as a route. These instructions replace Defining a Route on page 46.
For details on the full features of iWay Designer, and additional information on using its capabilities, see the iWay Designer User's Guide.
You will complete the following high-level steps to define the route.
1. Using iWay Designer, create a new project and start a new process flow.
2. Add a copy service object to the process flow.
3. Add an acknowledgement service object to the process flow.
4. Validate the process flow and publish it to the Registry of the iWay Service Manager Administration Console. See the iWay Designer User's Guide for instructions on validating and publishing.
5. Add a route to the Registry and associate the process flow with that route.
How to Create an iWay Designer Project and Start the Process Flow Procedure:
1. From the Windows Start menu select Programs, iWay 5.5 SM, tools, and then iWay Designer.
2. Connect to the repository from which you want to work, for example, iWay.
3. Right-click the repository node and select New Project from the drop-down list.
The Designer Project Information dialog box opens, prompting you for a project name and optional description.
4. In the Name field, type EDI_PF_Configuration as the project name.
In the Description field, type Defining a route for EDI inbound processing using iWay Designer to describe the project.
Defining a Route With iWay Designer
5. Click Next.
The Designer Project Bindings dialog box opens.
6. To create the project in the iWay Registry, select iWay Registry and click Finish.
The choice of project association depends on where you intend to publish (deploy) your process flow. If you are developing a process flow for use as part of a channel, you must publish it to the Registry for subsequent deployment.
7. The EDI_PF_Configuration project node appears under the repository in which it was created (in this example, it appears under iWay).
8. To save the project to the repository, right-click the project node and select Save from the drop-down list.
9. Expand the EDI_PF_Configuration project node to expose the project elements (Processes, Services, Transforms, and so on).
10. Right-click the Processes folder and select New Process from the drop-down list.
The iWay Process Configuration dialog box opens.
11. In the Name field, type EDI_Process_Flow as the process flow name.
In the Description field, type Process flow for EDI route for channel for inbound processing.
E. Defining a Route With iWay Designer
12. Click Finish.
The new EDI_Process_Flow node appears under the Processes folder, and the workspace displays a Start object.
You are ready to build the EDI_Process_Flow by adding objects to it and specifying their relationships.
How to Add a Copy Service Object Procedure:
The copy service redirects an output document to a destination.
1. Drag and drop the Service object from the toolbar to the workspace.
The Service Name and Description dialog box opens.
2. In the Name field, type EDI_PFlow_Copy, and leave the default value (Service object) in the Description field.
3. Click Next.
The Service Type dialog box opens.
Defining a Route With iWay Designer
4. Select Class Name and enter com.ibi.agents.XDCopyAgent.
5. Click Next.
The Define Service dialog box opens.
Do not select the check box, since you do not want to use this service in other process flows.
6. Click Next.
The Properties dialog box opens.
7. Click Finish to accept the default values and close the dialog box.
The new EDI_PFlow_Copy Service object appears in the workspace.
Now you need to connect the Start object to the Copy Service object.
8. Select the Start object, right-click the EDI_PFlow_Copy Service object, and select Relation from the drop-down list.
The Line Configuration dialog box opens.
9. From the Event drop-down list, select OnCompletion and click OK.
This option indicates that there are no conditions that affect the path, and that the path between the two objects will always be followed.
A line appears between the objects to indicate that a relationship has been established.
E. Defining a Route With iWay Designer
How to Add an End Object for the Copy Service Object Procedure:
All processing paths must terminate with an End object.
1. Drag and drop the End object from the toolbar to the workspace.
The End Name and Description dialog box opens.
2. In the Name field, type CopyEnd, and leave the default value (End object) in the Description field.
3. Click Next.
The End Name Schema dialog box opens.
4. Since no schemas are used in this processing path (that is, the process flow will not be exposed as a Web service), from the Schema drop-down list, select None.
5. Click Next.
The Properties dialog box opens.
6. Click Finish to accept the default values and close the dialog box.
The new CopyEnd object appears in the workspace.
7. Select the EDI_PFlow_Copy Service object, right-click the CopyEnd object, and select Relation from the drop-down list.
The Line Configuration dialog box opens.
8. From the Event drop-down list, select OnCompletion and click OK.
This option indicates that there are no conditions that affect the path and that the path between the two objects will always be followed.
Your process flow will look similar to the following. The EDI_PFlow_Copy Service object is a unit of work that redirects the XML output to a defined destination through a custom emit. The CopyEnd object terminates this single process.
You can reposition the objects as desired.
Defining a Route With iWay Designer
How to Add an Acknowledgement Service Object Procedure:
You will add an acknowledgement service to return a functional acknowledgement (997) to the originator of the input document. The acknowledgement indicates that the input document was received and validated for structure. The acknowledgement does not indicate that business processing was performed on the document.
1. Drag and drop the Service object from the toolbar to the workspace.
The Service Name and Description dialog box opens.
2. In the Name field, type EDI_PFlow_Ack, and leave the default value (Service object) in the Description field.
3. Click Next.
The Service Type dialog box opens.
4. Select Class Name and enter com.ibi.agents.XDX12AckAgent.
5. Click Next.
The Define Service dialog box opens.
Do not select the check box, since you do not want to use this service in other process flows.
6. Click Next.
The Properties dialog box opens.
7. Click Finish to accept the default values and close the dialog box.
E. Defining a Route With iWay Designer
The new EDI_PFlow_Ack Service object appears in the workspace. The process flow will look similar to the following.
8. Select the Start object, right-click the EDI_PFlow_Ack Service object, and select Relation from the drop-down list.
The Line Configuration dialog box opens.
9. From the Event drop-down list, select OnCompletion and click OK.
A line appears between the objects to indicate that a relationship has been established.
How to Add an End Object for the Acknowledgement Service Object
How to Add an End Object for the Acknowledgement Service Object