To upload a transaction:
1. Go to Transactions on the navigation menu.
2. Click on New Transaction.
3. Select Upload a transaction from the drop-down.
4. Choose a file from your computer.
Note:
- You can upload a .json, .x12 or .txt file
- The content of the file must be either JSON or X12.
More details on the section Accepted transaction formats. - You can upload only 1 file at a time
- The size of the file must be less than 1MB
5. Click Open.
6. Look at the snackbar on the bottom left of your screen to see the result of your upload.
- If the file upload is successful, open the newly created transaction from the snackbar link or refresh the transaction list view.
- If the file upload failed, read the error message to fix the error.
List of known failure reasons
A file upload can fail because:
- The partnership doesn’t exist in Orderful
Resolve: Create a trade requests to add a new partnership. - The sender doesn’t exist in Orderful
Resolve: Check you correctly defined your EDI accounts and/or Check your trade requests have the correct ISA IDs. - The receiver doesn’t exist in Orderful
Resolve: Check you correctly defined your EDI accounts and/or Check your trade requests have the correct ISA IDs. - The relationship doesn’t exist in Orderful
Resolve: Go to scenario testing to create a new change request and add a new relationship. - The relationship in SETUP
Resolve: Finish your relationship configuration. - The file couldn’t be parsed
Resolve: Check your file respects the accepted format.
Transaction stream
The stream of the transaction you upload will be Test if you upload a file containing:
- an X12 transaction with a T indicator
- OR a transaction belonging to a relationship with Test status
- OR a transaction where you are the receiver
The stream of the transaction you upload will be Live if you upload a file containing:
- a transaction belonging to a relationship with Live status
- AND a transaction where you are the sender
- AND a transaction with a P indicator (for X12 transactions)
Accepted transaction formats
Upload an X12 transaction
If you choose to upload an X12 transaction, you must respect the X12 standards. Each file must:
- Start with an ISA segment.
- Have at least one interchange envelope (ISA/IEA segments).
- Have at least one functional group inside each interchange envelope (GS/GE segments).
- Have at least one transaction set inside each functional group (ST/SE segments).
- Respect the presence and order of loops, segments ,and elements defined by the X12 standards for each transaction type inside each transaction set.
Upload a JSON transaction
If you choose to upload a JSON transaction, you must respect the following JSON structure:
{
"type": {
"name": "TRANSCATION_TYPE_NAME"
},
"stream": "test",
"message": {
[...] // transactionSet
},
"sender": {
"isaId": "ISA_ID_SENDER"
},
"receiver": {
"isaId": "ISA_ID_RECEIVER"
}
}
The transactionSet, the value of the message field is the actual transaction you want to upload.
The other fields identify the relationship of the transaction you want to upload.