Planned values remain in FAAT_PLAN_VALUE after asset deletion via AS06 – causing period-end close er

[LEESEYOUNG]

Dear SAP Community,

I hope this message finds you well.
We are currently facing a challenging issue in a customer system running SAP S/4HANA ,
and I would greatly appreciate your insights or shared experience if anyone has encountered a similar case.
__________________________________________________________________

Scenario:
Assets have been fully deleted using transaction AS06.

However, FAAT_PLAN_VALUE still contains planned value entries for those asset numbers.

The XPOST flag in these records is set to 'X', causing the system to treat them as planned assets.

This leads to blocking errors during period-end closing, such as:

“Book values are incomplete” messages,

Inconsistencies in depreciation runs,

Company codes failing to close due to unresolved planned values.

__________________________________________________________________
Questions :
1. Is this behavior expected in ALA?
Are planned values not automatically removed when the asset master is deleted (i.e., is this by design)?

2. Does SAP offer any standard cleanup report or internal tool
to remove such orphaned records from FAAT_PLAN_VALUE?

3. If not, are there any SAP-recommended methods or best practices to safely remove these entries
without compromising data consistency?

__________________________________________________________________
 Final Words:
As I have not yet been granted access to the relevant S-user authorizations from the customer client,
I am reaching out here to seek insights and advice from experienced experts in the community.

Thank you very much in advance for your time and kind support. (--) 

Sera