Most likely the Party number or RecId is already in use as these are the only two fields with unique constraints on DirPartyTable (by standard)
This is typical if data has been manually migrated through SQL without updating the SEQ no for RecIds or NextVal on the numberseqeunce. Of course, migrating data via SQL is for the most part not recommended.
If this is not the case, the numbersequence has possibly been reset or configuration changed to use a new number sequence.
To check the Numbersequence (most likely culprit seeing the partynumber is quite low) have a look at the Numbersequence form and look for Party Id numbersequence, it possibly says next number is 47 if you are still getting that error. This you can compare to the largest PartyNumber in DirPartyTable table.
For RecId you can compare the largest RecId in the same table with the output from this query:
select * from SYSTEMSEQUENCES where Name = 'SEQNO' and TABID = 2303 --DirPartyTable.
If SEQNO is smaller than highest current RecId in DirPartyTable, then be sure to address it with Senior AX technical before making any changes, which will require Flush or possibly AOS restart.
If none of these checks pan out, then the problem may need to be traced (Trace cockpit) or debugged.
Hope this sheds some light on the issue.
WBR
Vidir
