cancel
Showing results for 
Search instead for 
Did you mean: 

ABAP XSLT Transformation using element include

Lukas_Weigelt
Active Contributor
0 Kudos

Hi there,

I am trying to convert data from SAP-DATA -> DOM over XSLT to a Stream.

For achieving this I have to use certain modularized XSL-Files which will later be accessible over http. At the moment however, those files are on my local hard drive (client) only. I tried to access these files using:

<xsl:transform version="1.0"
  xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
  xmlns:sap="http://www.sap.com/sapxsl"
>

(...)

*<xsl:include href="D:\XSL\include.xsl"/>*

(...)

<xsl:strip-space elements="*"/>

<xsl:template match="/">
</xsl:template>

</xsl:transform>

I get the message "D:\XSL\include.xsl doesn't exist" when checking the syntax. When I test this in my OS however, it works perfectly. Being an SAP- and XML-Newbie my question is the following: Does SAP not know my hard drive mappings while I'm in a transformation or can i only access directories over al11/http. Or is it complete nonsense at all?

Regards, Lukas

Edited by: Lukas Weigelt on Jun 9, 2010 4:18 PM

Accepted Solutions (1)

Accepted Solutions (1)

MichalKrawczyk
Active Contributor
0 Kudos

Hi,

>>>oes SAP not know my hard drive mappings while I'm in a transformation

SAP does know that as you can see

>>> or can i only access directories over al11\

you can put the file using a simple program to the server and it will be visible in AL11

try abap forum for a sample program to import files to SAP server (less then 20 lines...)

Regards,

Michal Krawczyk

Lukas_Weigelt
Active Contributor
0 Kudos

>

>

> you can put the file using a simple program to the server and it will be visible in AL11

> try abap forum for a sample program to import files to SAP server (less then 20 lines...)

>

> Regards,

> Michal Krawczyk

Thanks, I did that. However using

<xsl:include href="https://answers.sap.com/usr/sap/ablage/../include.xsl"/>

returns the same message "doesn't exist". I guess there's some blatant mistake I'm making but the fact that the exact same is working outside of SAP confuses me. I'm not sure whether the include-element expects something else here (did RTFM but didn't succeed in finding an example yet).

Regards, Lukas

MichalKrawczyk
Active Contributor
0 Kudos

Hi,

or maybe href does not work in ABAP xslt at all - (only in java xslt)?

as per:

http://help.sap.com/saphelp_470/helpdata/EN/84/2e4d3ce624b800e10000000a114084/frameset.htm

"The href attribute no longer applies in this case."

Regards,

Michal Krawczyk

Lukas_Weigelt
Active Contributor
0 Kudos

Hi,

according to:

>

> as per:

> http://help.sap.com/saphelp_470/helpdata/EN/84/2e4d3ce624b800e10000000a114084/frameset.htm

> "The href attribute no longer applies in this case."

it appears the include element only works with the repository.... I tried

<xsl:include sap:name="<Name_of_the_Transformation_in_Repository>"/>

and it works.

However this would mean, all includes i have to make have to be imported to the repository. If that's really the case, it'll be a huge problem, because the xsl-files i want to include are outside of my reference

Regards, Lukas

Lukas_Weigelt
Active Contributor
0 Kudos

Hi,

sorry for revitalizing this again but i have to ask one last time.

Considering I have one Transformation in my Repository which should be able to include several xsl-templates from a public source (http, ftp). Is it inevitably nessecary to convert these templates into repository objects for using "sap:name" instead of "href" or is there any workaround to link to outside-of-sap-obejcts? I searched yet again to avoid this redundancy but wasn't lucky.

Regards, Lukas

Answers (0)