How To Fix CCR020 - Expense type: &1; use: &2

CCR020 - Overview

• Message type: E = Error

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

• Message number: 020

• Message text: Expense type: &1; use: &2

What causes this issue?

Expense type &V1& is used as &V2&. This is potentially inconsistent with
other expense types.
Example: nontaxable use of a wage type in expense type A, but taxable
use of the same wage type in expense type B.

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?

If this is an error, either change the type of payment/taxation of the
expense type in views V_T706B1 (Expense Receipts) and V_T706B1_A (Per
Diems), change the assigned wage/salary type in views V_T706B4 and
V_T706B4_A.
Follow these links to edit the system settings:
<DS:SIMG.SIMG_OHR0050>Create Travel Expense Types for Individual
Receipts</>
<DS:SIMG.SIMG_OHR1070>Create Travel Expense Types for Per Diems/Flat
Rates</>
<DS:SIMG.SIMG_OHR0037>Assign Wage Types to Travel Expense Types for
Individual Receipts</>
<DS:SIMG.SIMG_OHR0039>Assign Wage Types to Travel Expense Types for Per
Diems/Flat Rates</>

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 CCR020 - Expense type: &1; use: &2 ?

  The SAP error message CCR020 typically relates to issues with expense types in the context of the Controlling (CO) module, particularly when dealing with Cost Center Accounting or Internal Orders. The message indicates that there is a mismatch or an issue with the configuration or usage of a specific expense type.
  
  Cause:
  
  Incorrect Configuration: The expense type specified in the error message may not be properly configured in the system. This could be due to missing settings in the controlling area or expense type master data.
  Invalid Usage: The expense type may not be allowed for the specific transaction or context in which it is being used. For example, it might be restricted to certain cost centers or internal orders.
  Authorization Issues: The user may not have the necessary authorizations to use the specified expense type.
  Data Entry Errors: There could be a typo or incorrect entry in the transaction that is causing the system