SAP ABAP Data Element PRX_MSG_SPLIT_PATH (Split path for Messagetype)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-DWB-PRX (Application Component) Proxy Generation
⤷
SAI_PROXY_GENTIME (Package) ES Tools: Proxy Generation
⤷
⤷
Basic Data
| Data Element | PRX_MSG_SPLIT_PATH |
| Short Description | Split path for Messagetype |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | PRX_STRING | |
| Data Type | STRG | Character String of Variable Length |
| Length | 0 | |
| Decimal Places | 0 | |
| Output Length | 0 | |
| 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 | Split Path |
| Medium | 15 | Split Path |
| Long | 27 | Split Path for Message Type |
| Heading | 27 | Split Path for Message Type |
Documentation
Definition
The Message Type Split Path determines the tabular element in a message that is used to split up a message for bulk/error message processing. The split path is realized as XPath and stored with the message type.
The syntax of the split path is
/ [ '{' valid_namespace '}' ] element_name '[1]/' ) * '{' valid_namespace '}' ]element_name
A split path has the following restrictions:
- all path elements exist in the hierarchy of the message
- the leaf element has to be a table type (maxOccurs > 1)
- all other elements determining the XPath are no table types
Use
The split path can be maintained in the message type Proxy Editor external/internal view.
The path can be either entered manually via detail attributes for the message type or via context menu in the external/internal view for the split element.
Dependencies
Example
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 803 |