Technical review check
CHECKRESOURCEWarning (W)
A resource code that isn't valid this year
CDE's wordingThe following codes for RESOURCE are not valid. Data should be corrected or narrative must be provided explaining why the exception(s) should be considered appropriate.
Warning. CDE accepts it with an explanation entered in the TRC explanations.
What it means
A resource code that isn't valid this year
Each resource is checked against CDE's valid list for the year. Because grants come and go, this is the most common code failure at year end: a resource that posted all year can be retired by the time the actuals are due.
Why it fires
The usual causes
- A one-time grant resource CDE closed, still carrying a residual balance or late activity
- A resource CDE renumbered between years
- A local resource outside the ranges CDE reserves for locally defined codes (the export must roll it up to the CDE resource)
How to fix it
The repair
- Move the balance and activity to the successor resource CDE named, or to the resource that should carry them.
- If a small residual balance is all that remains and it cannot be moved, CDE accepts a written explanation with the warning.
- Expect CHK-FUNDxRESOURCE and CHK-RESOURCExOBJECTA to fire on the same rows; they clear together.
In SACS Pre-Flight
What the tool shows
Lists the code with line numbers and, where it is one edit away from a valid resource, the likely intended one. The combination checks that fire because of it are shown under their own ids.
See every check on your own file before the system runs them. Drop a SACS Other Export (.dat) into SACS Pre-Flight: findings with line numbers, free, entirely in your browser. The file never leaves your computer.
Run SACS Pre-Flight free