How To Fix DC1352 - Activation of generated BDT application &1 for business partner

DC1352 - Overview

• Message type: E = Error

• Message class: DC1 - BDT-DC Messages

• Message number: 352

• Message text: Activation of generated BDT application &1 for business partner

What causes this issue?

You created a change document object in the first postprocessing step
that is necessary for the running of the generated code. So that the
operating procedure after generation is not interrupted by this
non-running application, it is marked as "Not Active". In this
postprocessing step you activate the generated application.

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?

Call up the view maintenance of business partner applications.
Double-click on the entry of the application &V1&. Now you can see the
detailed settings of this application. Mark the checkbox "Active" and
save this setting.

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 DC1352 - Activation of generated BDT application &1 for business partner ?

  The SAP error message DC1352 typically occurs during the activation of a generated Business Data Tool (BDT) application for a business partner. This error can arise due to various reasons, and understanding the cause is essential for finding a solution. Here’s a breakdown of the potential causes, solutions, and related information:
  Causes:
  
  Missing Configuration: The BDT application may not be properly configured or may be missing necessary settings in the Business Partner (BP) configuration.
  Authorization Issues: The user attempting to activate the BDT application may not have the required authorizations.
  Inconsistent Data: There may be inconsistencies or errors in the underlying data related to the business partner.
  Technical Issues: There could be technical issues in the SAP system, such as missing transport requests or issues with the BDT framework itself.
  Incorrect BDT Application: The BDT application being activated may not be correctly defined or may have errors in its definition.
  
  Solutions:
  
  Check Configuration: Ensure that the BDT application