If you need to import sales transactions from another system into Microsoft Dynamics GP as Sales Order Invoices, you may need to store some additional data related to the customer, the transaction, or the line items. Even if your company is manually entering transactions in Dynamics GP, you may want to populate a few extra fields in the Dynamics GP Sales Order Invoice.
What are the options for storing additional data elements that are not natively supported by Dynamics GP SOP fields?
Here are some of the common options and some pros and cons.
First, let's start with the additional transaction, or header level fields that are available.
: While Dynamics GP normally defaults the next document number, you do have the option of overriding the number. In my case, I have imported a transaction ID into the SOP Document Number field that will allow the customer to trace transactions between both systems by using the same number. Just make sure that the GP document numbering uses a different sequence or prefix so that the numbers never collide.
: If you click on the blue arrow next to the Document Number field, you can specify a GL reference for the transaction that can flow through to the GL. While this may not necessarily be a great place to store "extra" data, it's an option for folks who would like to trace and reconcile transactions in their GL.
: If …