Understand Blockers and Recommended Next Steps

This topic provides guidance on how the assistant explains capitalization blockers and what users should do after they identify the reported issue.

How the Assistant Explains Blockers

The assistant explains the current blocking reason in business-friendly language and gives supporting transaction detail with guidance on what to review next.

Common Blockers and Next Steps

Here's a table listing some of the common blockers you may encounter while working with the assistant, with guidance on how to resolve them.

Common Blocker	Description	Next Steps
No Eligible Project Asset Exists	This means the cost cannot be assigned to an eligible project asset yet.	Typical next steps include reviewing the project asset, confirming setup and assignment, setting the asset to As-Built when appropriate, entering the actual in-service date, and rerunning Generate Asset Lines.
Accounting Not Completed	This means the transaction is otherwise eligible, but accounting is not complete.	Typical next steps include reviewing accounting status, completing accounting as required, and rerunning Generate Asset Lines.
Assets Not Assigned	This means the project or task does not have the needed asset assignment.	Typical next steps include assigning project assets at the project or task level and then rerunning Generate Asset Lines.
Event Setup Incomplete	For event-based processing, this means the required capital event is not defined or the transaction is not linked to an eligible event.	Typical next steps include reviewing capital event setup, confirming eligible assets are associated to the event, linking the affected costs, and rerunning Generate Asset Lines with the correct event.
Already Capitalized	This means the transaction was already capitalized and no new asset lines will be created.	In this case, no corrective action is usually needed.

Note: The assistant flags the current blocker it found. After you resolve that blocker, another prerequisite might still need review.