Business Scenario
Kevin now has the task of preparing company codes for Asset Accounting. Before he or his colleagues can create or post assets, he must check the initial settings for the company code in Asset Accounting.
Company Code Status – Asset Accounting Specific
To use a company code in Asset Accounting, the Bike Company must first define the correct status. The status determines which actions are allowed in a company code's Asset Accounting.

These three status options are available:
- For Testing:
Purpose: To perform the initial setup and testing of a new company code.
Effect: This status allows the deletion of master and transaction data in Asset Accounting.
Kevin sets the company code to For Testing mode, then completes the configuration and carries out initial test asset creations and postings.
- Productive:
Purpose: For the ongoing, productive operation of the company code.
Effect: Once the status is Productive, the system prevents any deletion of master and transaction data in Asset Accounting. This ensures data integrity.
In coordination with project stakeholders, Kevin changes the status to Productive at the company code's Go-Live. At this point, the team has completed the configuration, successfully concluded the tests, and performed the legacy data transfer. From this point on, all transactions are productive.
- Deactivated:
Purpose: To decommission a company code that is no longer required for Asset Accounting.
Effect: This status blocks all further postings in Asset Accounting. Additionally, reports will no longer include this company code.
Note
This status change is irreversible.
Additional Function: Company Code Lock
A lock immediately prevents all postings and changes to asset master data in this company code.
Purpose: To temporarily block all user activity (postings and master data changes) during administrative tasks, such as data migration. This ensures data consistency while work is in progress.
