How To Fix TPM_TRM1009 - VWBEVI record: CoCd &1, daybook number &2 does not agree with corp.action

SAP Error Message - Details

• Message type: E = Error

• Message class: TPM_TRM1 - Migration 4.6 - CFM 1.0

• Message number: 009

• Message text: VWBEVI record: CoCd &1, daybook number &2 does not agree with corp.action

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 TPM_TRM1009 - VWBEVI record: CoCd &1, daybook number &2 does not agree with corp.action ?

  The SAP error message TPM_TRM1009 indicates a discrepancy between the company code (CoCd) and the daybook number in relation to the corporate action. This error typically arises in the context of Treasury and Risk Management (TRM) when processing transactions related to financial instruments, particularly in the area of corporate actions.
  Cause:
  The error message suggests that there is a mismatch between the expected values for the company code and the daybook number in the context of a corporate action. This could be due to several reasons:
  
  Data Entry Error: Incorrect data may have been entered for the company code or daybook number.
  Configuration Issues: There may be a misconfiguration in the system settings related to corporate actions or daybook processing.
  Inconsistent Data: The data in the system may not be consistent, possibly due to changes in corporate actions that were not properly updated in the relevant records.
  Missing or Incorrect Mapping: The mapping between the corporate action and the financial instruments may not be set up correctly.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  Verify Data Entry: Check the entries for the company code and daybook number to ensure they are correct and match the expected values.
  Review Configuration: Look into the configuration settings for corporate actions and ensure that they are set up correctly in the system.
  Check for Updates: Ensure that all relevant data related to corporate actions has been updated correctly in the system. This includes checking for any recent changes that may not have been reflected.
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on handling corporate actions and daybook processing.
  Run Consistency Checks: Use SAP tools to run consistency checks on the relevant data to identify any discrepancies.
  Contact Support: If the issue persists, consider reaching out to SAP support or your internal SAP team for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes in SAP that pertain to Treasury and Risk Management, such as TPM1, TPM2, etc.
  Corporate Actions: Understand the different types of corporate actions and how they are processed in SAP.
  Documentation: Review SAP Notes and Knowledge Base Articles related to TPM_TRM1009 for any specific patches or updates that may address this issue.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.