How To Fix GA835 - Cost Center Accounting and Activity-Based Costing not active in &

SAP Error Message - Details

• Message type: E = Error

• Message class: GA - Allocations

• Message number: 835

• Message text: Cost Center Accounting and Activity-Based Costing not active in &

What causes this issue?

In controlling area &V2& and fiscal year &V1& the cost centers are not
active, nor is Activity-Based Costing active as the operative
accounting system.

System Response

The system therefore rejects the maintenance of cycles for assessment
to CO-PA

How to fix this error?

To carry out a cost center assessment, you must activate the cost
centers for each controlling area and fiscal year. To carry out a
process cost allocation you must activate Activity-Based Costing as the
operative accounting system (Active indicator 2)
Check these settings for the control indicator of the controlling area.
<DS:SIMG.SIMG_CFMENUORK3OKKP>Maintain controlling area</> -> Activate
components / control indicator -> Detail.
Check the validity interval of the corresponding cycle.
<DS:SIMG.SIMG_CFMENUORKEKEU1>Cycle - cost center assessment (actual)</>
<DS:SIMG.SIMG_CFMENUORKEKEU7>Cycle - cost center assessment (plan)</>
<DS:SIMG.SIMG_CFMENUORKE5055>Cycle - process cost assessment (act.)</>
<DS:SIMG.SIMG_CFMENUORKE3055>Cycle - process cost assessment (plan)</>

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message GA835 - Cost Center Accounting and Activity-Based Costing not active in & ?

  The SAP error message GA835 indicates that Cost Center Accounting (CCA) and Activity-Based Costing (ABC) are not active in the specified controlling area. This error typically arises when you attempt to perform operations related to cost centers or activity types in a controlling area where these functionalities have not been activated.
  Cause:
  
  Inactive CCA/ABC: The controlling area in question has not been configured to use Cost Center Accounting or Activity-Based Costing.
  Configuration Issues: The necessary settings in the controlling area configuration may not have been completed.
  System Settings: The system may not have been set up to support these functionalities for the specific controlling area.
  
  Solution:
  To resolve the GA835 error, you need to activate Cost Center Accounting and/or Activity-Based Costing for the controlling area. Here are the steps to do this:
  
  
  Access the Configuration:
  
  Go to the SAP Easy Access screen.
  Navigate to SPRO (SAP Project Reference Object) > SAP Reference IMG.
  
  
  
  Activate Cost Center Accounting:
  
  Follow the path: Controlling > Cost Center Accounting > Master Data > Maintain Control Parameters.
  Select the relevant controlling area and ensure that the settings for Cost Center Accounting are activated.
  
  
  
  Activate Activity-Based Costing (if needed):
  
  Follow the path: Controlling > Activity-Based Costing > Basic Settings > Activate Activity-Based Costing.
  Again, select the relevant controlling area and ensure that the settings for Activity-Based Costing are activated.
  
  
  
  Check for Dependencies:
  
  Ensure that all necessary prerequisites for activating CCA and ABC are met, such as the existence of cost centers, activity types, and other related master data.
  
  
  
  Save Changes: After making the necessary changes, save your configuration.
  
  
  Testing: After activation, perform a test transaction to ensure that the error no longer appears.
  
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like OKKP (for controlling area settings) and KS01 (to create cost centers) to manage related configurations.
  Documentation: Refer to SAP Help documentation for detailed steps and guidelines on configuring Cost Center Accounting and Activity-Based Costing.
  User Roles: Ensure that you have the necessary authorizations to make changes in the controlling area settings.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or functional team for further investigation, as there may be additional underlying issues or configurations that need to be addressed.