Oftentimes, it is necessary to test our EnterpriseOne inbound EDI transaction sets without having an EDI translator in place. This may be for a number of reasons, many of which relate to a new implementation where all processes have not yet been integrated. The good news is that you do not need to wait for an active EDI Translator to be in place before you can test the inbound transactions. As you may or may not know, each of our inbound EDI transactions comes with its own Status Inquiry/Revisions program. These programs can be utilized to populate the required fields in the inbound EDI interface tables, thus bypassing the need for an EDI translator. Below is a list of our inbound EDI transactions and the associated Status Inquiry/Revisions program.


Inbound 810:  P47040

Inbound 824:  P47191

Inbound 830:  P47060

Inbound 840:  P47090

Inbound 850:  P47010

Inbound 852:  P47120

Inbound 855:  P47020

Inbound 856:  P47030

Inbound 860:  P47130

Inbound 861:  P47070

Inbound 865:  P47140


It should be noted that the info above was taken from EDI Quick Reference Guide (Doc ID 659847.1). This quick reference guide contains a lot of other information that can be helpful with regard to EDI implementations. Of special interest is all EDI white papers listed at the bottom of the document. The inbound papers contain the minimum required fields that need to be populated either via EDI translator or via the Status Inquiry/Revisions programs listed above.