How To Fix BSP_DYN_MSG_DESIGN026 - Use customer namespace "WRAPPED_" + (X,Y,Z) for wrapped BOR object types

BSP_DYN_MSG_DESIGN026 - Overview

• Message type: E = Error

• Message class: BSP_DYN_MSG_DESIGN - Messages for DESIGN

• Message number: 026

• Message text: Use customer namespace "WRAPPED_" + (X,Y,Z) for wrapped BOR object types

What causes this issue?

You have created a
<DS:GLOS.483BD44C7BB44299E10000000A421948>UI object type</> with a
technical name that starts with "WRAPPED_" and does not continue with
either "X", "Y" or "Z".

System Response

This UI object type is located outside of the customer namespace, and
the system issues a warning message.

How to fix this error?

Ensure that the UI object type is correctly located outside of the
customer namespace.
Note that a newly created UI object type should be located outside the
customer namespace only if you have to integrate a business object
repository (BOR) object of another system.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message BSP_DYN_MSG_DESIGN026 - Use customer namespace "WRAPPED_" + (X,Y,Z) for wrapped BOR object types ?

  The SAP error message BSP_DYN_MSG_DESIGN026 indicates that there is an issue related to the use of Business Object Repository (BOR) object types in the context of Business Server Pages (BSP) applications. Specifically, it suggests that you are trying to use a wrapped BOR object type that is not in the customer namespace.
  
  Cause:
  The error occurs when:
  
  You are attempting to use a wrapped BOR object type that is not defined in the customer namespace.
  The system expects that any custom or wrapped BOR object types should be prefixed with a customer namespace (in this case, "WRAPPED_").
  The object types (X, Y, Z) mentioned in the error message are likely placeholders for the actual object types that are causing the issue.
  
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Object Types: Identify the specific BOR object types (X, Y, Z) that are causing the error. You can do this by reviewing the BSP application