How To Fix CCR104 - Expense type &1 (service &2 - paid) is not defined in V_T706S_RECEIPT

SAP Error Message - Details

• Message type: E = Error

• Message class: CCR - Messages for Customizing Check Report Program

• Message number: 104

• Message text: Expense type &1 (service &2 - paid) is not defined in V_T706S_RECEIPT

What causes this issue?

Expense type &V1& is assigned in maintenance view V_TA22A for travel
services category &V2& (paid by company) for the integration of travel
planning and travel expense reports. (See <DS:SIMG.OFTV_INT_COS_TP_02>
Define Assignment of Expense Type - Travel Service Category </>.)
However, expense type &V1& is <zh>not</> defined in maintenance view
V_T706S_RECEIPT (see <DS:SIMG.SIMG_OHR_T706S_RECEI>Restrict Travel
Expense Types for Trip Schemas</>).

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?

Procedure for System Administrators

See the documentation for Customizing activity
<DS:SIMG.SIMG_OHR_T706S_RECEI>Restrict Travel Expense Types for Trip
Schemas</>. If you still want to use the function for this purpose, add
the missing expense in this Customizing activity.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CCR104 - Expense type &1 (service &2 - paid) is not defined in V_T706S_RECEIPT ?

  The SAP error message CCR104 indicates that there is an issue with the configuration of expense types in the system, specifically related to the service and payment details. This error typically arises when the system is trying to process a service or expense type that has not been defined in the relevant configuration table (in this case, V_T706S_RECEIPT).
  Cause:
  
  Missing Configuration: The expense type specified in the error message is not defined in the V_T706S_RECEIPT table. This could happen if the expense type was never created or if it was deleted or modified incorrectly.
  Incorrect Service Assignment: The service associated with the expense type may not be correctly linked or may not exist in the system.
  Data Entry Error: There may be a typo or incorrect entry in the transaction that is causing the system to look for an undefined expense type.
  
  Solution:
  
  
  Check Configuration:
  
  Go to the transaction code SPRO to access the SAP Reference IMG.
  Navigate to the relevant configuration path for defining expense types and ensure that the expense type in question is correctly defined in the V_T706S_RECEIPT table.
  If it is missing, you will need to create a new entry for the expense type and ensure it is linked to the correct service.
  
  
  
  Verify Service Assignment:
  
  Check if the service associated with the expense type is correctly defined and active in the system.
  Ensure that the service is linked to the correct expense type in the configuration.
  
  
  
  Data Validation:
  
  Review the transaction or document that triggered the error to ensure that all entries are correct and that there are no typos or incorrect values.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for guidance on configuring expense types and services.
  
  
  
  Testing:
  
  After making the necessary changes, test the transaction again to ensure that the error is resolved.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  SPRO for configuration.
  SE11 to view the table V_T706S_RECEIPT.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
  User Roles: Ensure that you have the necessary authorizations to make changes to the configuration.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in the relevant module.