Importing GAS Error: Record Already Exists, but it doesn't

SUGGESTED

Sage X3 ERP v7 Patch 8

I'm trying to figure out how to import Journal Entries to alleviate the time spent by our Accounting Dept. I know the data I'm inputting is accurate because I'm just re-importing data exported from the Production server (excluding the Document Number). When importing this into the Test environment (where this record does not exist), I get the below error message.

As you can see, when I search for this entry it does not appear. The last entry in the Test environment was GEN006298, so GEN006299 is the next available document number. 

Has anyone else experienced this? I've found no resources that address this issue. 

  • 0
    SUGGESTED

    Hi Lee,

    Here are a few things to check out

    • Are you using an unmodified version of the GAS template?
    • Check these tables to see if the journal exists: GACCENTRY, GACCENTRYD, GACCENTRYA.
    • Sage Knowledgebase article: Error: Record already exists Table: GACCENTRYD [DAE]; (71777)

    If these don't help you resolve your issue, you should contact your local support team

  • 0 in reply to pnightingale

    Thanks for the reply. 

    To address your questions, there's no good way for me to confirm this. The UPDDAT_0 in AOBJEXT is 2010-09-08. The Sage X3 Online Help Center doesn't provide any information on the GAS import template (at least for our account) for me to compare it to. 

    I'm unable to find any record with GEN006299 when querying GACCENTRY, GACCENTRYD, or GACCENTRYA.

    And although the Sage KB article matches up with what I'm seeing, the error is appearing on the first line and the data has been pulled from Sage X3 itself so I don't understand how there could be an error with the data (new data from PROD that doesn't exist in TEST3). 

  • 0

    Hello from France, when you export a dataset with an export model, you have to considere the following action to do to sent it in your test folder. You should manually eliminate the piece number in the ascii file in the way to let X3 recreate it.  The same rule applies for all fields with a counter.