How To Fix CTE_FIN_POSTING123 - ID &1 of expense report &2: posting use case (&3) is not supported.

CTE_FIN_POSTING123 - Overview

• Message type: E = Error

• Message class: CTE_FIN_POSTING - ERP - Concur Integration: FIN Postings

• Message number: 123

• Message text: ID &1 of expense report &2: posting use case (&3) is not supported.

What causes this issue?

A change was made to the document that has now led the document to be an
unsupported use case.
Use cases that are not supported include:
Multiple journal: Multiple journals are only supported in combination
with Cash Advance or Fringe Benefit Tax.
Partly deductible tax: This use case is not supported for Canada when
there are two tax lines and they're both partly deductible. The
non-deductible tax is still processed for reporting purposes or for
posting to a special account.
Unknown: With the information provided by Concur, the use case could not
be determined.

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?

The source of the problem can be found in the <LS>reversalExpenseEntry
</> block with ID &v1& in the document's JSON. To access the JSON file,
click <LS><PF>Display </></>-> <LS>Original File (JSON Format)</> or
double-click the document's information in the <LS>Changed</> column
from the <LS>Concur Documents</> screen.
Make the correction(s) in the appropriate field(s) and resubmit the
document in the Concur system.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

CTE_FIN_POSTING123 - Details

• The SAP error message CTE_FIN_POSTING123 typically indicates that there is an issue with the posting of an expense report in the system. This error can arise due to various reasons related to configuration, data entry, or system settings. Here’s a breakdown of the potential causes, solutions, and related information:
  Causes:
  
  
  Unsupported Posting Use Case: The error message suggests that the specific use case for posting the expense report is not supported in the current configuration. This could be due to the type of expense report or the way it is being processed.
  
  
  
  Configuration Issues: There may be configuration settings in the SAP system that do not allow for the posting of certain types of expense reports. This could include settings related to the expense types, cost centers, or other financial parameters.
  
  
  Missing Master Data: Required master data (such as cost centers, internal orders, or expense types) may be missing or incorrectly set up, leading