Share
Report
3After doing a migration from AX2012R2 RTM (plain, no CU's) to AX2012R3CU9 we encoutered the same issue as indicated in the next linkedin post :
When posting a statement in AX2012 R2 - HQ I get an error 'Number sequence does not exist'. From <https://www.linkedin.com/grp/post/3726956-230770796>
After testing all the options we had to debug, and found that the datatype definition for the statementid was wrong in the numbersequence tables NumberSequenceDataType and NumberSequenceDataTypeParameterType.
for statement datatypeid 17358 (retailstatementid) we had to chage the Scopetype to be 4 (operating unit) on the NumberSequenceDataType, and for the related record in NumberSequenceDataTypeParameterType we changed the parametertype field to be "Operating Unit"
After doing this and generating the number sequences back again, the system allowed to create the statements.
don't know if this is and issue in the upgrade script.
would appreciate other comments to identify if this situation is happening also in possible upgrade scenarios from AX2009,AX2012FP, AX2012R2 to AX2012R3cu9.
*This post is locked for comments
I have the same question (0)
All responses (
Answers (
