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: 070
Message text: Missing entry in tab. COSP_VTYPE for keys VRGNG_OLTP &1 and WRTTP_OLTP &2
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
FCOM_PLANNING_CORE070
- Missing entry in tab. COSP_VTYPE for keys VRGNG_OLTP &1 and WRTTP_OLTP &2 ?The SAP error message FCOM_PLANNING_CORE070 indicates that there is a missing entry in the table COSP_VTYPE for the specified keys VRGNG_OLTP and WRTTP_OLTP. This error typically arises in the context of financial planning or controlling processes, particularly when dealing with cost accounting or profitability analysis.
Cause:
- Missing Configuration: The error usually occurs when the system is trying to access a specific combination of value types (VRGNG) and write types (WRTTP) that have not been defined in the COSP_VTYPE table.
- Data Migration Issues: If data has been migrated from another system or if there have been recent changes in configuration, it is possible that the necessary entries were not created or were lost during the process.
- Custom Development: If there are custom developments or enhancements that rely on specific value types or write types, and those are not properly configured, this error can occur.
Solution:
Check COSP_VTYPE Table:
- Use transaction code SE11 or SE16 to view the COSP_VTYPE table.
- Look for entries corresponding to the keys VRGNG_OLTP and WRTTP_OLTP. If they are missing, you will need to add them.
Add Missing Entries:
- If you have the necessary authorization, you can manually add the missing entries to the COSP_VTYPE table.
- Ensure that you have the correct value types and write types that correspond to your business requirements.
Review Configuration:
- Check the configuration settings in the controlling area to ensure that all necessary value types and write types are defined.
- Use transaction code SPRO to navigate to the relevant configuration settings in the Controlling module.
Consult Documentation:
- Review SAP documentation or notes related to the specific version of SAP you are using. There may be specific notes addressing this error.
Contact SAP Support:
- If you are unable to resolve the issue, consider reaching out to SAP support for assistance. They may provide insights or patches if this is a known issue.
Related Information:
By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
FCOM_PLANNING_CORE069
The infoobject &1 could not be mapped to a field
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_CORE068
InfoObject &1 was not transported
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_CORE071
Cost element &1 cannot be used for cost element planning
What causes this issue? You have entered cost element &V1&. This cost element has the category &V2&, which is not valid for cost elem...
FCOM_PLANNING_CORE072
An SQL exception occurred, DB schema cannot be determined
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.