How To Fix 67828 - Costs could not be saved

SAP Error Message - Details

• Message type: E = Error

• Message class: 67 - Loans Messages - Financial Assets Management

• Message number: 828

• Message text: Costs could not be saved

Self-Explanatory Message

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.

What else can you do?

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message 67828 - Costs could not be saved ?

  The SAP error message "67828 Costs could not be saved" typically occurs in the context of cost planning or cost allocation processes within SAP. This error can arise due to various reasons, and understanding the cause is essential for finding an appropriate solution. Here are some common causes and potential solutions:
  Causes:
  
  Missing Authorizations: The user may not have the necessary authorizations to save cost data.
  Data Inconsistencies: There may be inconsistencies in the data being processed, such as incorrect or missing cost center, internal order, or other relevant master data.
  Locked Records: The records being updated may be locked by another user or process, preventing the save operation.
  Technical Issues: There could be underlying technical issues, such as database problems or system configuration errors.
  Validation Errors: The system may have validation rules that are not being met, leading to the inability to save costs.
  
  Solutions:
  
  Check Authorizations: Ensure that the user has the necessary permissions to perform the action. This can be verified by checking the user roles and authorizations in the SAP system.
  Review Data Entries: Double-check the data being entered for any inconsistencies or missing information. Ensure that all required fields are filled out correctly.
  Check for Locks: Use transaction codes like SM12 to check for any locks on the records. If a lock is found, you may need to wait for the other user to release it or contact your system administrator.
  Consult Logs: Check the application logs (transaction SLG1) for any additional error messages or warnings that could provide more context about the issue.
  Technical Support: If the issue persists, it may be necessary to involve your SAP Basis team or technical support to investigate any underlying system or database issues.
  Validation Rules: Review any validation rules that may be in place and ensure that the data being saved complies with these rules.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as KP06 (Cost Center Planning), KP26 (Activity Type Planning), and others related to cost planning.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide patches and updates.
  Documentation: Review SAP documentation related to cost planning and allocation for best practices and troubleshooting tips.
  
  If the problem continues after trying these solutions, it may be beneficial to escalate the issue to your SAP support team for further investigation.