Summary:
Running Depreciate Assets for period 6/30/2026 (Posting Period Jun 2026) is not creating any Journal Entries, for any asset in the batch — not just a subset. The process reports as "Completed" with the "Create Journal Entries" stage marked "Not Required," but no June JEs exist anywhere in the system, including for assets that posted successfully in every prior month (Jan–May 2026).
Timeline:
- Ran Depreciate Assets for 6/30/2026 (Process ID 228). Result: 7 specific assets failed at Stage 2/7 "Create Journal Entries" with
MAP_ERROR: The following field(s) are inactive: Depreciation Account, tied to BG Summary records 128, 129, 130, 131, 132, 134, 206. - Investigated the named account (15000 – Accumulated Depreciation): confirmed it is Active, has no subsidiary restriction (Parent Company + Include Children), and matches the account correctly mapped on the affected assets' Accounts tab (verified directly on FAM000128). No duplicate "Accumulated Depreciation" account exists in the Chart of Accounts (confirmed via Show Inactives).
- Deleted the 7 stale BG Summary records (128, 129, 130, 131, 132, 134, 206) and re-ran Depreciate Assets for 6/30/2026. Result: Process ID 331, "Completed," no errors reported.
- Re-ran Depreciate Assets a third time with identical settings (Asset Type = all 5 types, Subsidiary = Parent Company + Include Children, Depreciation Period = 6/30/2026, Posting Period = Jun 2026). Result: Process ID 332 — every stage shows "Not Required," including "Create Journal Entries" (Stage 2/7).
- Checked Depreciation History directly on multiple assets (FAM000002, FAM000012, FAM000129 — none of which were among the original 7 failures). All show a depreciation row for 6/30/2026 with a calculated Transaction Amount and Net Book Value, but no Posting Reference — meaning no JE was ever created for June, for any asset, not only the originally-flagged 7.
Question for Support:
It appears the original Create Journal Entries failure on Process 228 may have blocked JE creation for the entire June batch (all assets), not only the 7 assets with the account-mapping error. Deleting the 7 flagged BG Summary records appears to have cleared FAM's internal "pending work" tracking for June, causing subsequent runs to report each stage as "Not Required" even though no June Journal Entries actually exist for any asset.
Can you confirm the current internal processing state for the June 2026 depreciation batch (Process IDs 228, 331, 332), and advise the correct way to force FAM to regenerate and post June Journal Entries for the full asset population without creating duplicate postings for periods that may have partially processed?