CO-object Error on Asset Retirement with revenue

[VPS80]

Hi Expert

We are facing the issue while trying to retire an asset with revenue from books. The issue is coming that system asking CO-Object while the same already been assigned with asset master and the same in showing at time of simulating the entry but still showing the error. Please arrange to check and guide us where the gap is.

[BobShen · Accepted solution]

The issue you're facing with asset retirement and the system asking for a CO-Object despite it being assigned in the asset master is a known problem in SAP. Here are some steps to investigate and resolve the issue:

1. Verify Asset Master Data:

   • Ensure that the asset master has the correct CO-Object (cost center, internal order, or WBS element) assigned [1][2].
   • Check if the cost center assigned to the asset is a statistical cost center, as this may cause issues [2].

2. Check Account Determination:

   • Review the account determination settings for the asset class [3].
   • Verify that the NBV Retirement Expense (Gross) and NBV Retirement Revenue (Gross) fields have valid accounts assigned [3].

3. Examine CO-Object Assignment:

   • Ensure that the ASCET (Account Assignment) is correctly configured to include internal order, cost center, and profit center [1].

4. Review G/L Account Settings:

   • Check the G/L field status group for the accounts involved in the retirement transaction [2].
   • Ensure that the settings allow for the use of the assigned CO-Object.

5. Validate Transaction Settings:

   • When using transaction F-92 for asset retirement with revenue, make sure you're using the correct posting keys (e.g., 01 and 50) [4][5].

6. Consider System-Specific Issues:

   • If you're using SAP S/4HANA, ensure that the Asset Retirement Obligation functionality is properly activated and configured [6].

If the issue persists after checking these points, you may need to:

1. Review any recent system changes or upgrades that might have affected asset retirement functionality.
2. Consult with your SAP support team or create a ticket to investigate any potential system-specific issues.
3. Consider performing a test retirement in a non-production environment to isolate the problem.

Remember that the specific resolution may depend on your SAP version and configuration. If you continue to experience difficulties, it's advisable to engage SAP support for a more detailed analysis of your system setup.