How To Fix BSP_DYN_MSG_DESIGN029 - Design objects were copied to customer layer

SAP Error Message - Details

• Message type: E = Error

• Message class: BSP_DYN_MSG_DESIGN - Messages for DESIGN

• Message number: 029

• Message text: Design objects were copied to customer layer

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message BSP_DYN_MSG_DESIGN029 - Design objects were copied to customer layer ?

  The SAP error message BSP_DYN_MSG_DESIGN029 indicates that design objects (such as Web Dynpro components or BSP applications) have been copied to the customer layer. This typically occurs when you are working with SAP's Business Server Pages (BSP) or Web Dynpro applications, and it signifies that the system has detected that certain design objects have been modified or copied into the customer layer (the Z layer) from the standard layer.
  Cause:
  
  Modification of Standard Objects: The error usually arises when standard design objects are modified or copied into the customer layer. This can happen during development or when a transport request is imported that includes changes to these objects.
  Transport Issues: If a transport request containing design objects is imported, and those objects already exist in the customer layer, the system may raise this message to inform you of the duplication or modification.
  Development Practices: Poor development practices, such as directly modifying standard objects instead of creating Z-objects or enhancements, can lead to this error.
  
  Solution:
  
  Review Changes: Check the changes made to the design objects. If they were intended, ensure that they are documented and that the changes are necessary.
  Use Custom Objects: Instead of modifying standard objects, create custom objects (Z-objects) to avoid conflicts and maintain the integrity of the standard SAP system.
  Transport Management: Ensure that your transport requests are properly managed. If you are importing a transport that includes design objects, verify that there are no conflicts with existing customer layer objects.
  Revert Changes: If the changes are not needed, consider reverting the design objects back to their original state in the standard layer.
  Consult Documentation: Refer to SAP documentation or notes related to the specific design objects you are working with for any additional guidance or best practices.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional context on handling design objects.
  Development Guidelines: Familiarize yourself with SAP's best practices for development, especially regarding modifications to standard objects.
  Transport Organizer: Use the Transport Organizer (SE09/SE10) to manage and review transport requests effectively.
  BSP and Web Dynpro Documentation: Review the official SAP documentation for BSP and Web Dynpro to understand the implications of copying design objects and how to manage them properly.
  
  If the issue persists or if you need further assistance, consider reaching out to your SAP Basis or development team for a more in-depth analysis of the situation.