Skip to main content

Trading Partner Onboarding - Morris Dickson

If you are looking to implement Morris Dickson as a new Trading Partner within your EDI network, this article will provide you with an understanding of the requirements, preliminary and next steps, as well as commonly used transaction types.

S
Written by Stacie McGee

Trading Partner: Morris Dickson


EDI IDs


Morris Dickson utilizes the following Electronic Data Interface (EDI) IDs for identification purposes. These EDI IDs are made up of a Qualifier and an ID which will be sent within their Interchange Control Header, ISA segment, on your inbound transactions. This allows Transaction Manager to be able to identify the Sender and Receiver of any EDI transaction that is sent or received.

Below is a list of the most common EDI IDs typically used by Morris Dickson:​

X12 Qualifier

EDI ID

Primary ID?

01

007995079

Yes

ZZ

PM0334443

No

01

007995079PO

No

Morris Dickson will expect a specific EDI ID based on your business relationship with them. Selecting the wrong EDI ID will result in EDI Transactions not being sent or received.

You will need to work with Morris Dickson to determine the proper EDI ID to use.


Preliminary Steps


To initiate the EDI Setup process, Morris Dickson vendors will be required to email [email protected] and supply the following details:


Direct Trading Partner Testing


Morris Dickson requires you to complete compliance testing before Go-Live. Please refer to the below Next Steps section for detailed instructions and expectations. If you prefer, TrueCommerce can conduct and complete compliance testing on your behalf.


Commonly Used Transactions


Below is a list of most commonly used EDI transactions with Morris Dickson:


Next Steps


Once the purchase of the Morris Dickson plug-in is complete, your Implementation Specialist will reach out to schedule time to complete and/or coordinate a plan for compliance testing and/or Enterprise Resource Planning (ERP) system integration testing.


Related Documentation


rev: 8/14/2026

Did this answer your question?