SAP ABAP Message Class SPRX Message Number 067 (The XSD type &1 does not exactly correspond to the ABAP type &2)
Hierarchy
☛ SAP_BASIS (Software Component) SAP Basis Component
   ⤷ BC-DWB-PRX (Application Component) Proxy Generation
     ⤷ SAI_PROXY_GENTIME (Package) ES Tools: Proxy Generation
Attribute
Message class SPRX  
Short Description Proxy Generation    
Message Number 067  
Documentation status       Space: object requires documentation
Authorization check Error Message      
Changed On 20130531   
Message Text
The XSD type &1 does not exactly correspond to the ABAP type &2
Help Document

Diagnosis

You used the XSD type in the interface description.

This cannot be mapped exactly to ABAP, since the permitted value ranges and 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 in ABAP)
  • xsd:int (becomes INT4 in ABAP)
  • xsd:short (becomes INT2 in ABAP)
  • xsd:byte (becomes INT1 in ABAP)
  • xsd:decimal with fractionDigits <= 14 and totalDigits <= 31 (becomes DEC in ABAP)
  • xsd:binary with length > 65535 (becomes RAWSTRING in ABAP)
  • xsd:binary with length <= 65535 (becomes RAW in ABAP)

Using a type where the value ranges do not match exactly may lead to severe runtime errors if a value outside the ABAP range is supposed to be assigned. Please use the above types instead if at all possible.

The value ranges for the following types do not match exactly:

  • xsd:float (becomes FLTP in ABAP)
  • xsd:double (becomes FLTP in ABAP)
  • xsd:base64Binary with length <= 65535 (becomes raw in ABAP)
  • xsd:base64Binary with length > 65535 (becomes rawstring in ABAP)
  • xsd:hexBinary with length <= 65535 (becomes raw in ABAP)
  • xsd:hexBinary with length > 65535 (becomes rawstring in ABAP)
  • xsd:integer (becomes INT4 in ABAP)
  • xsd:positiveInteger (becomes INT4 in ABAP)
  • xsd:nonPositiveInteger (becomes INT4 in ABAP)
  • xsd:nonNegativeInteger (becomes INT4 in ABAP)
  • xsd:negativeInteger (becomes INT4 in ABAP)
  • xsd:long (becomes INT4 in ABAP)
  • xsd:byte (becomes INT4 in ABAP)
  • xsd:unsignedLong (becomes INT4 in ABAP)
  • xsd:unsignedInt (becomes INT4 in ABAP)
  • xsd:unsignedShort (becomes INT4 in ABAP)

For the following types a more flexible mapping is possible; see also

Mapping XSD to ABAP Data Types

  • xsd:time (becomes TIMS in ABAP)
  • xsd:date (becomes DATS in ABAP)
  • xsd:boolean (becomes CHAR(5) in ABAP)

All remaining XSD types are mapped as follows:

  • With length <= 65535 and pattern = "+" to NUMC
  • With length <= 65535 to CHAR
  • With length > 65535 to STRING

Note that ABAP types DATS and TIMS correspond to the XSD types xsd:date and xsd:time with the following or equivalent restrictions, which must be defined as such in the XML schema and which explicitly eliminate entering time zones in the XML:

<restriction base="xsd:time">

<pattern value="[^:]2:[^:]2:[^:]2"/>

</restriction>

<restriction base="xsd:date">

<pattern value="[^-]4-[^-]2-[^-]2"/>

</restriction>

System Response

The system displays a warning for this type.

Procedure

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

History
Last changed on/by 20140121  SAP 
SAP Release Created in   620