SAP ST TT COND documentation, setup help and usage info

ARTICLE

ST - tt:cond , Conditional Transformations

Syntax
<(><<)>tt:[s-|d-]cond [using="..."]
[data="..."]
[[s-|d-]check="..."]>
...
/tt:[s-|d-]cond

Effect
Conditional transformations are realized as the content of an element tt:[s-|d-]cond . They represent parts of ST programs that are not ignored only if certain prerequisites are met. Conditional transformations are normally used as cases in
tt:switch and tt:group .
The content of tt:[s-|d-]cond is processed depending on

a precondition in the attribute using

an assertion in the attribute data

a condition in the attribute check

. If the content of tt:[s-|d-]cond is not a
pattern , you must specify at least one attribute using ,
data , or check .

The element tt:cond is evaluated during serialization and deserialization.

The element tt:s-cond is evaluated only during serialization and skipped during deserialization. The content of tt:s-cond is never deserialized.

The element tt:d-cond is evaluated only during deserialization and skipped during serialization. The content of tt:s-cond is never serialized.

The condition check can also be used directionally:

The condition check is evaluated during serialization and deserialization.

The condition s-check is evaluated only during serialization.

The condition d-check is evaluated only during deserialization.

It makes no sense to specify s-check in tt:d-cond or
d-check in tt:s-cond .

Serialization
During serialization, the

precondition using

the assertion data

the condition check

are evaluated. The content of element tt:[s-]cond is serialized only if all three prerequisites are met; otherwise the comparison is terminated at the first false prerequisite and the content of
tt:[s-]cond is skipped.
If none of the three possible attributes is specified in tt:[s-]cond
, the prerequisite is considered as being met. If the content of
tt:[s-]cond is empty during serialization, the element is not considered.

Deserialization
During deserialization, before and during the check of the precondition , the system distinguishes whether or not the content of tt:[d-]cond is a pattern
. The deserialization proceeds as follows:
1. Check whether the content of tt:[d-]cond is a pattern .

If the content of tt:[d-]cond is a pattern

it is compared to the current element of the XML inbound stream. If the pattern does not match the current element, the element tt:[d-]cond is skipped and the current element of the XML inbound stream is not consumed; otherwise Step 2 follows.

If the content of tt:[d-]cond is not a

pattern , Step 2 follows.
2. Check the precondition using

If the content of tt:[d-]cond is a pattern

and the precondition is not met, the element tt:[d-]cond is skipped and the current element of the inbound XML stream is consumed without being deserialized. If the precondition is met, Step 3 follows.

If the content of tt:[d-]cond is not a

pattern and the precondition is not met, the deserialization is canceled with the exception CX_ST_REF_ACCESS . If the precondition is met, Step 3 follows.
3. Evaluation of the instruction body
The body of the instruction is evaluated. In this process, data nodes are deserialized. Their existence or type can have been checked in Step 2; the result of the deserialization can be checked for plausibility in Step 5.
4. Establish the assertion data
The value asserted in the assertion is assigned to all data nodes specified in this assertion. If, during deserialization of the current element of the inbound XML stream, a different value is assigned to one of these data nodes, the deserialization is terminated with exception CX_ST_COND_CHECK_FAIL .
5. Check the condition check
The condition [d-]check is checked. If the condition is not met, the deserialization is canceled with the exception
CX_ST_COND_CHECK_FAIL .
If none of the three possible attributes using , data , or check is specified in tt:[d-]cond , the content of
tt:[d-]cond must not be empty; it is evaluated in Step 1, depending on whether or not it is a pattern . The other prerequisites (Steps 3 to 4) are considered as being met.

Notes

You can use an assertion to assign a value to a data node without the node being filled by the inbound stream. Instead of an empty element tt:[d-]cond , you should use the statement tt:assign in this case.

You can use the empty element tt:[d-]cond to check the current content of data nodes during deserialization.

You can use an element tt:[d-]cond without explicit conditions to flag optional content during deserialization. This means, if a pattern does not exist in the inbound XML stream, its evaluation is skipped without triggering an exception.

Example
The transformation below shows conditions:
<(><<)>tt:transform
xmlns:tt="http://www.sap.com/transformation-templates">
tt:root name="ROOT1"/
tt:root name="ROOT2"/
tt:root name="ROOT3"/
<(><<)>tt:template>
<(><<)>X>
<(><<)>tt:d-cond>
<(><<)>X0>
...
<(><<)>/X0>
<(><<)>/tt:d-cond>
tt:d-cond data="ROOT3=333"/
<(><<)>tt:cond using="type-I(ROOT1), type-I(ROOT2)"
data="ROOT1=111"
d-check="ROOT2<(><<)>ROOT3">
<(><<)>X1>
tt:value ref="ROOT1"/
<(><<)>/X1>
<(><<)>X2>
tt:value ref="ROOT2"/
<(><<)>/X2>
<(><<)>/tt:cond>
tt:cond d-check="ROOT2 111"/
<(><<)>/X>
<(><<)>/tt:template>
/tt:transform
If the ABAP data objects bound to ROOT1 and ROOT2 are of type i and ROOT1 has the value 111, then the transformation generates the following XML fragment, regardless of the ABAP data object bound to the data root ROOT3 :
<(><<)>X>
<(><<)>X1>111<(><<)>/X1>
<(><<)>X2>222<(><<)>/X2>
/X
The same transformation can deserialize this XML fragment, thereby setting ROOT3 to the value 333. The deserialization fails if X1 does not have the value 111 and if X2 does not lie between 111 and 333. The element X0 of the transformation is optional. It would also be possible to deserialize the following XML
fragment:
<(><<)>X>
<(><<)>X0>...<(><<)>/X0>
<(><<)>X1>111<(><<)>/X1>
<(><<)>X2>222<(><<)>/X2>
/X
However, if the first subelement of the XML fragment has a name other than X0 , the exception CX_ST_MATCH_ELEMENT would be triggered.

SAP ST TT COND documentation, setup help and example usage