SAP ABAP Data Element PRX_XXML (Proxy Runtime: Standard/Extended Rendering and Parsing)
Hierarchy
☛ SAP_BASIS (Software Component) SAP Basis Component
   ⤷ BC-DWB-PRX (Application Component) Proxy Generation
     ⤷ SAI_PROXY_PUBLIC (Package) ES Tools: Proxy Public Interfaces
Basic Data
Data Element PRX_XXML
Short Description Proxy Runtime: Standard/Extended Rendering and Parsing  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type SYCHAR01    
Data Type CHAR   Character String 
Length 1    
Decimal Places 0    
Output Length 1    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Extended 
Medium 15 Extended 
Long 21 Extended XML Handling 
Heading 0   
Documentation

Definition

The attribute extended_xml_handling controls the serializing and parsing of XML messages in ABAP data structures. If extended_xml_handling = space then serialization occurs in accordance with the standard. If extended_xml_handling = 'X', then the control fields are used for serialization and they are completed during parsing. This enables the application override the default procedure, or rather to attain more information about the incoming message (for example, element is initial because the initial value was sent or because the element does not exist in XML).

Restrictions When Setting the Attribute?

If the attribute is set, this has an effect on the performance: the additional information must be evaluated during serialization or fetched during parsing, which is performance intensive. You should not set this attribute if the default procedure is sufficient for your needs.

Currently, it is not possible to generate programs that are required for rendering and parsing for special handling if the interface contains too many elements (more than 1500). This figure is reduced to roughly a quarter when using the default procedure. This enables you to edit such interfaces. In this case, your only option is to not set this attribute.

Default Procedure During Serialization

The ABAP components are rendered according to the description in the Enterprise Services Repository during serialization. The following exceptions are made for simple type (data elements or inline-defined components):

  • If the component has the initial value and a default is saved in the Enterprise Services Repository, then the default value replaces the initial value.
  • If an optional component has the initial value but no default in the Enterprise Services Repository, then the element does not appear in the data stream.

There are no defaults for complex components. The element of a complex component always appears in the data stream.

Default Procedure During Parsing

The tag content is transferred to the corresponding ABAP components during parsing. In the case of simple types, the default value is used if a default is saved in the Enterprise Services Repository and the element either does not exist in the data stream or it has the initial value in the data stream.

Extended XML Handling During Serialization

During serialization the format specifications, which can be set in the control fields for each ABAP component, override the standard procedure. If the format specification is set for a component, then this overrides the contents of the component and the definition in the Enterprise Services Repository. The default procedure defined above is used in components where no format is specified.

You have the following options:

  • sai_ctrl_initial: element is rendered with the initial value (only recommended for simple type components).
  • sai_ctrl_nil: element is sent with the addition xsi:nil='true'. The data stream contains the attributes of the element but no sub-attributes.
  • sai_ctrl_none: element is not rendered.

Extended XML Handling During Parsing

The control fields for the elements are set during parsing.

  • sai_ctrl_initial: element has the initial value in the data stream.
  • sai_ctrl_nil: element has the addition xsi:nil='true' in the data stream.
  • sai_ctrl_none: element is not in the data stream.

Setting the Attribute

  • You set the attribute before the proxy method is called for outbound proxies. Therefore, you can set the attribute differently for each call.
  • You can set the initial value of the interface attribute in the implementing class for inbound interfaces.

Use

Dependencies

Example

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