- Newest
- Most votes
- Most comments
I solved the problem...
I did create a new user under IAM, however it did not attached to the USER GROUP that I created with the necessary permissions, therefore the issue was not the file (even though the error read that the file was not the formatted correctly). once i added the B2Bi user to the right group, then the user can access the file and it validated correctly.
- link for user and permissions documentation: https://docs.aws.amazon.com/singlesignon/latest/userguide/quick-start-default-idc.html
ensure that you see the user under the group.. I had both created but probably I forgot to add the user to the group Hope this helps the next person.
I apologize for the difficulty you're experiencing with AWS B2B Data Interchange. The error you're encountering suggests there might be an issue with the format or content of your EDI document. Here are some steps you can try to resolve this issue:
-
Double-check the document number and version: Ensure that the document type and version you've selected in the console match exactly with what's in your EDI file.
-
Validate your EDI file: Use an EDI validator tool to check if your file is correctly formatted and complies with the EDI standards.
-
Check for special characters: Sometimes, hidden characters or incorrect line breaks can cause parsing issues. Try opening your EDI file in a plain text editor to spot any anomalies.
-
Segment terminators: You mentioned changing the segment terminator. Make sure it's consistent throughout the document and matches what you've specified in the console.
-
Remove any extra spaces or lines: Ensure there are no extra spaces at the beginning or end of segments, or blank lines in the file.
-
Use the exact sample: Since you mentioned that even the sample 214 EDI file from the guide is causing the same error, there might be an issue with how you're inputting the data into the console. Try copying and pasting the sample directly without any modifications.
-
Check file encoding: Ensure your file is saved with the correct encoding (usually UTF-8).
If you've tried all these steps and are still encountering the error, it would be advisable to contact AWS Support for further assistance. They can provide more specific guidance based on your exact configuration and file content.
Remember, B2B Data Interchange is designed to simplify EDI transformations, so once you overcome this initial hurdle, you should be able to automate your EDI workflows more efficiently.
Sources
Announcing AWS B2B Data Interchange
AWS B2B Data Interchange key capabilities
Manage EDI at scale with new AWS B2B Data Interchange | AWS News Blog
answered 2 years ago
Hi Will, thanks for catching this. We plan to update this error message to more accurately reflect the issue (access and permissions). We do agree that the current error message is misleading and not actionable.
Also, our product team would love to connect to learn more about your use case and requirements, if you're willing. Please email b2bi-pm@amazon.com if you'd like to connect. The team is currently planning out the 2025 roadmap and hoping to prioritize features/capabilities that will benefit customers like yourself.
Relevant content
asked 3 years ago
asked 3 years ago

I did all the above mention steps, including to ensure that the file was UTF-8, verifying that there is not an invalid character, the sample 214 file looks clean and it is in linux format with LF and UTF-8 encoding.
again i tried several files, including one that was previously working when i tested this process the first time and it worked well, now it does not work, hence i decided to use the 214 in the sample documentation.
please help..!