AX 2009 R2Refresh RBOTransaction ID issue - transaction already exists

Finance and Operations/AX User Forum
1

Hi,
We have upgraded a test environment from AX2009 Retail R1 to AX2009 Retail R2-Refresh including a test POS terminal.
We created some test transactions at the POS but found that, after polling, these new transactions are not being inserted into the RBOTransaction tables. I presume that this is because the TransactionID already exists in the HQ AX tables (the numbers at the POS are starting over with #1, #2, #3, etc.).
If we create a new POS terminal ID at HQ and change the terminal number in the POS config file, the polling and posting works just fine. However, I would rather not have to create new POS terminal ID’s for all of our store locations once we roll this upgrade into production.
Is there a way to update the transaction number sequence at the POS so that new transactions will start with the correct Transaction ID’s based on the HQ transaction tables?
Thanks,
Hank

2

Hello,

Just checking to see if anyone has ever run into the issues described above. Or, has everyone’s upgrades gone smoother than this?

We were also exploring the possiblity of reseeding the TransactionID number. Is this controlled by an identity column? If so, do you know where it is located?

Thanks,

Hank