How To Fix FINS_ACDOC_CUST052 - No document type found for bus. trans. &1 in company code &2

FINS_ACDOC_CUST052 - Overview

• Message type: E = Error

• Message class: FINS_ACDOC_CUST - Unified Journal Entry - Customizing

• Message number: 052

• Message text: No document type found for bus. trans. &1 in company code &2

What causes this issue?

For business transaction &V1& the system could not determine a document
type in company code &V2&.

System Response

The assignment of CO business transactions to document types is done in
the IMG activity
<DS:SIMG.VCFINS_CO_DOCT_M> Variant for Mapping of CO Transactions
to Document Types</>.

How to fix this error?

In case no mapping variant exists, you have to
<DS:SIMG.VCFINS_CO_DOCT_M>create a variant</> first. For business
transaction &V1& you will need to enter a document type there.
If a mapping variant already exists or if you have just created it,
proceed with one of the following options:
In Customizing, assign this mapping variant to the company code &V2&
using this navigation path:
<ZK>Financial Accounting (New) -> Financial Accounting Global Settings
(New) -> Ledgers -> Real-Time Integration of Controlling with Financial
Accounting -> Check and Define Default Values for Postings in
Controlling</>; or

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

<DS:SIMG.VCFINS_CO_DOCT_M>Select the Default Variant checkbox</> in the
mapping variant.

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 FINS_ACDOC_CUST052 - No document type found for bus. trans. &1 in company code &2 ?

  The SAP error message FINS_ACDOC_CUST052 indicates that there is no document type defined for a specific business transaction in the specified company code. This error typically arises during the posting of financial documents when the system cannot find a corresponding document type for the transaction being processed.
  
  Cause:
  
  Missing Document Type: The primary cause of this error is that the document type for the specified business transaction (indicated by &1) is not defined in the configuration for the specified company code (indicated by &2).
  Incorrect Configuration: The document type may not have been set up correctly in the system, or it may have been deleted or deactivated.
  Transaction Type Mismatch: The business transaction being processed may not match any of the configured document types for the company code.
  
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check Document Type Configuration:
  
  Go to the SAP transaction code OBY6 (or OBD2 for document types) to check the configuration