project set up cost code error

Hi ​@epan ,

Can you verify below-

1. Does not exist in the Cost Codes (PM209500) master table, or
2. Has formatting/segmentation mismatches (e.g., trailing spaces, leading zeros, or segment masking), or
3. Was defaulted or substituted during the upload process due to project settings or template mapping.

Because the system triggers a DAC field-verifying validation on row events (including row deletion), Acumatica throws an exception ('Cost Code' cannot be found in the system) before it can process your change or delete the row.

Hope above helps!!

@epan That 864 isn't a cost code. It's the internal record ID the budget line is pointing at, and no cost code with that ID exists. When the Revenue Budget tab can't find the record, it shows the raw ID in the Cost Code column. I reproduced your exact error on a 2026 R1 test instance by pointing a saved budget line at a cost code ID that doesn't exist.

Cost Code is part of the budget line's key. Every edit, delete or save sends that key back, the lookup fails, and the whole request is rejected. That's why picking a valid code snaps back and Delete Row doesn't take. As Rakshanda said, it fails before your change is processed. I also tried switching the Revenue Budget Level so the column is hidden. Same result.

So there's no fix from the screen. The cost code ID on that one budget record (PMBudget) has to be corrected in the database. Open a support case, or have your partner do it if you're on a private instance, and have them run it on a snapshot copy first. In my test, once the record pointed at a valid cost code, the line edited and deleted normally.

I couldn't get 2026 R1 to create this from an upload. There, a cost code in the file that doesn't match anything falls back to the default cost code and saves cleanly. Put your version and the upload file in the support case. If you're willing to share them here too, I'll run the same import on my test instance. If you'd rather not make them public, send me a DM.