In the context of a function, there are many ways to define data objects to work with specific data within a hierarchy of rules.
Examples
The sample application /SCT/QP_GEN_LOCAL is delivered with the QPPD.
Usage
The framework offers various definition possibilities of data objects for reading and writing back data.
Field related Mapping
Individual element values or node information are to be processed at the field level.
For example, the names of element data objects could be:
"VBELN_VALUE" using an element specifying the field name.
„BEDSPEZI_VBELN_VALUE“uses an element preceded by a node context and followed by a field name.
Absolute Mapping
Data from specific locations within a regulation object are to be processed.
For this purpose, the following identifiers can be prefixed to data object names in the context of a function.
Prefix | Subsequent Identifier | Description |
|---|---|---|
HEAD | Head node data. | |
ROOT | _[Object Type] | Head node data. |
CONTEXT | _[Node Context] | Data on specific context. |
ITEM | _[Position Type] | Data for specific position type. |
GRID | _[Object Type] | Data as a grid table. |
PARAM | _[Element] | Data as generation parameter for Element. |
PARAM | Data as generation parameter for Object Type. |
Relative Mapping
Data is to be processed depending on the node at which a function was called.
Prefix | Subsequent Identifier | Description |
|---|---|---|
PARENT | Data from parent node. | |
GRANDPARENT | Data from grandparent node | |
NODE | Data from the current node. | |
NEXT | _[Position Type] | Data from the nearest sibling node. |
PREV | _[Position Type] | Data from the previous sibling node. |
FIRST | _[Position Type] | Data from the first sibling node. |
LAST | _[Position Type] | Data from the last sibling node. |