PanatrackerGP creates transactions in Dynamics GP. Transactions created from PanatrackerGP will be assigned a number sequence independent to Dynamics GP. There are multiple reasons:
- Because the users for PanatrackerGP do not have to be setup within GP as a user, the audit history of the transactions are captured and maintained within the Panatracker logging database.
- The transactions completed from the PanatrackerGP application can also be entered directly in the Dynamics GP interface. With a different sequence numbering system, it is easy to identify the entry point of each transaction by the transaction number assigned.
- An independent sequencing and numbering eliminate any possibility of duplication of the transaction numbering within GP. In some cases, a transaction that may be set as pending or failed submitted from Panatracker will be assigned a transaction number. This allows tracking of the sequence even if the transaction is eventually discarded.
- Having an independent transaction numbering system adds the ability for us to provide better support. We can easily confirm the transaction source by the transaction number.
- For some transactions that PanatrackerGP updates versus creates or for data captured that updates GP that is not actually transactional, a transaction number is still assigned within the Panatracker logging. (Examples include sales order fulfillment, and assignment of manufacturer cross reference.) Our independent transaction numbering provides consistent support across the system.
Under the Transaction setup in the Panatracker administrative dashboard, you can set the next sequence number and also a prefix for each transaction. We recommend that your prefix is different from the prefix assignment in GP to make it easy to identify the source of the transaction for audit and review purposes.