How To Fix FTBCVA033 - No reference entity found for company code

SAP Error Message - Details

• Message type: E = Error

• Message class: FTBCVA - Credit Value Adjustment

• Message number: 033

• Message text: No reference entity found for company code

What causes this issue?

A reference entity for the company code is required in order to access
credit spread market data, which in turn is required to calculate the
product of probability of default and loss given default. However, no
reference entity was found for the company code.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Maintain reference entities for company codes using transaction
<DS:TRAN.RMRE>RMRE</>. The indicator <LS>Curve</> has to be set.
Alternatively, if no credit spread market data is available for a
particular company code, you can define a default company code in the
evaluation type (transaction <DS:TRAN.JBREVAL>JBREVAL</>).

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FTBCVA033 - No reference entity found for company code ?

  The SAP error message FTBCVA033, which states "No reference entity found for company code," typically occurs in the context of financial transactions, particularly when dealing with bank accounting or financial statement processing. This error indicates that the system cannot find a reference entity (such as a bank account or financial institution) associated with the specified company code.
  Causes:
  
  Missing Configuration: The reference entity (like a bank account) may not be configured for the specified company code in the system.
  Incorrect Company Code: The company code entered may be incorrect or not properly set up in the system.
  Data Inconsistency: There may be inconsistencies or missing data in the master data records related to the company code.
  Authorization Issues: The user may not have the necessary authorizations to access the reference entity for the specified company code.
  
  Solutions:
  
  
  Check Configuration:
  
  Navigate to the relevant configuration settings in SAP (usually in the Financial Accounting module) and ensure that the reference entity (e.g., bank accounts) is properly set up for the company code in question.
  Use transaction codes like OB52 (for fiscal year variant) or FI12 (for bank master data) to verify the settings.
  
  
  
  Verify Company Code:
  
  Ensure that the correct company code is being used in the transaction. You can check this in the transaction where the error occurs.
  Use transaction code OX02 to check the company code settings.
  
  
  
  Review Master Data:
  
  Check the master data for the reference entity to ensure it is complete and correctly linked to the company code.
  Use transaction codes like FI01 (for creating a bank master record) or FI02 (for changing a bank master record) to review the details.
  
  
  
  Check Authorizations:
  
  Ensure that the user has the necessary authorizations to access the reference entity. This can be checked with the help of your SAP security team.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help files related to bank accounting or financial transactions for additional guidance on the error.
  
  
  
  Contact Support:
  
  If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting SAP Notes for any known issues or patches related to this error.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OB52, FI01, FI02, FBL1N, and FBL3N for managing financial data.
  SAP Notes: Search for SAP Notes related to FTBCVA033 for any specific fixes or updates that may address the issue.
  User Forums: Consider checking SAP community forums or user groups for similar issues and solutions shared by other users.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.