How To Fix SPRX067 - The XSD type &1 does not exactly correspond to the ABAP type &2

SAP Error Message - Details

• Message type: E = Error

• Message class: SPRX - Proxy Generation

• Message number: 067

• Message text: The XSD type &1 does not exactly correspond to the ABAP type &2

What causes this issue?

You used the XSD Type &V1& in the interface description.
This cannot be mapped exactly to ABAP since
the permitted value ranges &V1& and &V2& do not match exactly.
The value ranges for the following types do match exactly (these should
be used in preference to others):
xsd:string with length > 65535 (becomes STRING in ABAP)
xsd:string with length <= 65535 (becomes CHAR in ABAP)
xsd:string with length <= 65535 and pattern="\d+" (becomes NUMC im
ABAP)
xsd:int (becomes INT4 im ABAP)
xsd:short (becomes INT2 im ABAP)
xsd:byte (becomes INT1 im ABAP)
xsd:date (becomes DATE im ABAP)
xsd:time (becomes TIME im ABAP)
xsd:decimal with fractionDigits <= 14 and totalDigits <= 31 (becomes
DEC im ABAP)
xsd:binary with length > 65535 (becomes RAWSTRING im ABAP)
xsd:binary with length >= 65535 (becomes RAW im ABAP)

System Response

The systems displays a warning for this type.

How to fix this error?

You must check the permitted value range when entering these types in
your program.

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 SPRX067 - The XSD type &1 does not exactly correspond to the ABAP type &2 ?

  The SAP error message SPRX067 indicates a mismatch between the XML Schema Definition (XSD) type and the ABAP type. This error typically occurs when there is an inconsistency between the data types defined in the XSD and those defined in the ABAP program or data structure.
  
  Cause:
  
  
  Type Mismatch: The XSD type defined for a particular element does not match the corresponding ABAP type. This can happen if:
  
  The XSD specifies a different data type (e.g., string vs. integer).
  The length or precision of the data types do not match.
  The structure of the data types is not compatible (e.g., a complex type in XSD vs. a simple type in ABAP).
  
  
  
  Changes in Data Model: If there have been recent changes to the data model or the XSD, and the ABAP code has not been updated accordingly, this error can occur.
  
  
  Incorrect Mapping: If the mapping between the XSD and ABAP types is not correctly defined, it