Entering content frameBackground documentation Stylesheets and Structuring Locate the document in its SAP Library structure

This graphic is explained in the accompanying text

xsl:apply-imports
 

Notes on Conformity:

Parameters can be passed to the called template in the same way as for xsl:apply-templates using xsl:with-param.

This graphic is explained in the accompanying text

xsl:import
 

Notes on Conformity:

The specifications do not contain an exact statement on how "imports to..." is to be understood. But this is of particular interest for the use of includes. Let us assume that an XSLT program A includes programs B and C, and C in turn imports program D. It is now clear that D will be imported to C and A. But what is the case for B?
- In our implementation, we assume that D is also imported to B (in the context of A). This is based on the assumption that there is a distinction between the two importing units U1 = {A, B, C} and U2 = {D} and there is an import relationship from U1 to U2. The consequence of this is that template rules from D are candidates for the statement xsl:apply-imports within B (in the context of A).

Our definition of "imports to..." is therefore to be understood as follows:

a). Import units are defined as nodes in the import tree.

b). The relationship "imports to..." is defined between the import units through the (transitive) relationship in the import tree.

c). Program Y is imported into program X if the import unit of Y has been imported into the import unit of X.

This graphic is explained in the accompanying text

xsl:include
 

Notes on Conformity:

The inclusion uses the name from the R/3 Repository instead of a URL. This name is specified in the sap:name attribute. The href attribute no longer applies in this case.

This graphic is explained in the accompanying text

xsl:stylesheet
 

Constraints:

The extension-element-prefixes attribute is no longer supported.

Notes on Conformity:

XSLT types of stylesheet parameters can be specified as top-level parameters with the statement xsl:param through the sap:type attribute. The following type descriptions can be used as values for sap:type: "string", "number", "boolean", "node-set", "external", and "xstring".
The triggers a type conversion on the ABAP side.

Example

In the standard version, a date in ABAP is passed as a string ("2001-05-16"). With the parameter declaration:

<xsl:param name="p" sap:type="number">

the date is first converted on the ABAP side into a number (number of days from 0001-01-01), and this number is then passed to the XSLT program.

This graphic is explained in the accompanying text

xsl:transform
 

See also: Note for xsl:stylesheet.

 

 

Leaving content frame