Do you have any question about this error?
Message type: E = Error
Message class: FCOM_PLANNING_CORE - Messages for Package FCOM_PLANNING_CORE
Message number: 036
Message text: Activity type &1 does not exist in fiscal year &2
Activity type &V1& is not valid in any period of fiscal year &V2&.
You have entered invalid master data or referenced invalid master data
that the system cannot process. Depending on where this occurred, the
system prevents you from entering the data, prevents you from navigating
further, or prevents further processing.
Correct your entries for the activity type or create the activity type.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
FCOM_PLANNING_CORE036
- Activity type &1 does not exist in fiscal year &2 ?The SAP error message FCOM_PLANNING_CORE036 indicates that the specified activity type does not exist in the given fiscal year. This error typically arises in the context of planning and budgeting processes within SAP, particularly when working with cost centers, internal orders, or other planning-related transactions.
Cause:
- Activity Type Not Defined: The activity type you are trying to use has not been defined for the specified fiscal year in the system.
- Fiscal Year Variants: The fiscal year variant may not be correctly set up, or the activity type may not be assigned to the fiscal year variant being used.
- Data Migration Issues: If data has been migrated from another system, there may be inconsistencies or missing configurations.
- Incorrect Configuration: The configuration settings for the controlling area or the activity type may not be properly maintained.
Solution:
Check Activity Type Configuration:
- Go to the SAP transaction code KP26 (Change Activity Type Planning) or KP06 (Change Cost Center Planning) and verify if the activity type exists for the specified fiscal year.
- If it does not exist, you may need to create it or adjust the planning settings.
Verify Fiscal Year Settings:
- Check the fiscal year variant settings in the configuration (transaction code OB29).
- Ensure that the fiscal year variant assigned to your controlling area is correct and that the activity type is included in the fiscal year.
Create or Adjust Activity Type:
- If the activity type is missing, you can create it using transaction code OAYD (Define Activity Types) or KOT2 (Define Activity Types for Cost Centers).
- Ensure that the activity type is assigned to the relevant cost centers or internal orders.
Check Planning Layouts:
- If you are using planning layouts, ensure that the layout is correctly set up to include the activity type for the fiscal year in question.
Consult Documentation:
- Review SAP documentation or help resources for specific details on configuring activity types and fiscal years.
Contact SAP Support:
- If the issue persists after checking the above points, consider reaching out to SAP support for further assistance.
Related Information:
By following these steps, you should be able to resolve the error message and ensure that the activity type is correctly configured for the specified fiscal year.
Get instant SAP help. Start your 7-day free trial now.
FCOM_PLANNING_CORE035
Cost element &1 does not exist in fiscal year &2
What causes this issue? Cost element &V1& is not valid in any period of fiscal year &V2&.System Response You have entered invalid ma...
FCOM_PLANNING_CORE034
Cost center &1 does not exist in fiscal year &2
What causes this issue? Cost center &V1& is not valid in any period of fiscal year &V2&.System Response You have entered invalid mas...
FCOM_PLANNING_CORE037
Error when reading hierarchy &1: &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FCOM_PLANNING_CORE038
You are not authorized for cost center planning in controlling area &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.