Uploading XSL stylesheet

I have modified the PO_STANDARD_XSLFO stylesheet to include logo.
How do I upload this Stylesheet?
the update button is disabled.
TIA,
Avi

When you submit the request, you can choose which template is used. In the PUI SRS form it's under the "Upon Completion..." block as "Layout". If it is being run as part of a request set, the PUI will not allow you to specify the template: it will use the default.
If you use the OAF based "Update Concurrent Program" window, you can set the default template. The PUI form does not have a field to set the default.
Failing the above, you could define a new Concurrent Program using the same Executable and setup like the seeded program. Then create a new Data Definition for the new program, and assign only the custom template to the new data definition. This way the new program can only use the customized template.

Similar Messages

Using xsl stylesheet with List View Web Part to display custom text

Hi
i have an xsl stylesheet with sharepoint listview webpart. The list view shows some items based on a filter. I want to display custom text such as "No Items" when there are zero items in the list view using the xsl stylesheet. How do i achieve
this. I have spent hours searching but couldnt find the exact answer. Please help me out. I am a light user not a hard core developer so I dont use Visual Studio. Thanks in advance

Hi
I have customised the list view webpart using a custom xsl file by including it in the xsl link of the list view webpart. So i think i need to include the condition in the xsl file itself else it wont work. Since the list view webpart isnt using the default
xsl. Please let me kknow if you have any idea about including a condition in xsl to check if there are not items in view.
The code of the xsl is included below.

<xsl:stylesheet
xmlns:x="http://www.w3.org/2001/XMLSchema"
xmlns:d="http://schemas.microsoft.com/sharepoint/dsp"
version="1.0"
exclude-result-prefixes="xsl msxsl ddwrt"
xmlns:ddwrt="http://schemas.microsoft.com/WebParts/v2/DataView/runtime"
xmlns:asp="http://schemas.microsoft.com/ASPNET/20"
xmlns:__designer="http://schemas.microsoft.com/WebParts/v2/DataView/designer"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:msxsl="urn:schemas-microsoft-com:xslt"
xmlns:SharePoint="Microsoft.SharePoint.WebControls"
xmlns:ddwrt2="urn:frontpage:internal">
<xsl:output method="html" indent="no"/>
<xsl:template match="/" xmlns:x="http://www.w3.org/2001/XMLSchema">
<xsl:variable name="Rows" select="/dsQueryResponse/Rows/Row" />
<table>
<xsl:for-each select="$Rows">
<xsl:call-template name="dvt_1.rowview"></xsl:call-template>
</xsl:for-each>
</table>
</xsl:template>
<xsl:template name="dvt_1.rowview">
<tr>
<td><img height="78" width="60"><xsl:attribute name="src"><xsl:value-of select="@Photo"/></xsl:attribute></img></td>
<td>
<table style="margin-left:10px;">
<tr><td><xsl:value-of select="@FullName"/></td></tr>
<tr><td><xsl:value-of select="@DOBinWords"/></td></tr>
</table>
</td>
</tr>
</xsl:template>
</xsl:stylesheet>

Xsl/stylesheet transformation problem in soap response(usinf xmlx-tags.tld)

Hi,
I have problem in transforming the soap response using xmlx-tags.tld.....
I was not able to read the <EmpName> value from the returned xml...
The stylesheet / xsl does not return any elements if I use other then "/" in match
attribute : <xsl:template match="/">
here is my soap call and stylesheet in JSP:
<x:xslt media="html">
<x:xml>
<ws:soap ttl="360000">
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
... making soap call here...
</soap:Body>
</soap:Envelope>
</ws:soap>
</x:xml>
<x:stylesheet media="html">
<xsl:stylesheet version='1.0' xmlns:xsl='http://www.w3.org/1999/XSL/Transform'>
<xsl:output method="xmll" omit-xml-declaration="no"
doctype-public="-//W3C//DTD HTML 4.0 Transitional//EN" indent="yes" />
<xsl:template match="GetEmpResult">
<html>
<body>
Result: <B>Symbol <xsl:value-of select="EmpName"/></B>
</body
</html>
</xsl:stylesheet>
</x:stylesheet>
</x:xslt>
the SOAP response looks like this:
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<GetEmpResponse xmlns="http://ws.cdyne.com/">
<GetEmpResult>
<EmpID>string</EmpID>
<EmpName>string</EmpName>
<SalAmount>decimal</SalAmount>
<Error>boolean</Error>
</GetEmpResult>
</GetEmpResponse>
</soap:Body>
</soap:Envelope>
I tried all the possibilities of template matches, but not succeeded....
Can somebody help me the correct <xsl:template> to access EmpName from the above
SOAP responses...
regards
Vijay

Hi,
Dynamic xslt are not quite supported in OSB, there are some approaches that may be helpful for your case though...
Have a look at these...
http://atheek.wordpress.com/2011/12/21/using-xalanevaluate-to-parametrize-xpath/
http://beatechnologies.wordpress.com/2010/12/01/dynamic-xquery-in-oracle-service-bus/
Let me know how you go...
Cheers,
Vlad

Can i view an xsl stylesheet? My message log is formatted and I can't read it.

I have found a message log in My Downloads. When I try to read it, it's an xsl stylesheet. What is this? Why is it in this format, and can I convert it so I can read it? Thanks--need details--I don't know much about computers!

An XSL stylesheet usually contains layout rules for an XML data file, but not actual data. Maybe what you found is actually the XML data file, which refers to the XSL style sheet?
If it doesn't help to open it in a Firefox tab, try opening it in Internet Explorer or Microsoft Excel. Both have some capability to decode XML.

XSL Stylesheet syntax

In .xsl file,
<xsl:stylesheet xmlns:xsl="http://www.w3.org/TR/WD-xsl">
What is this xmlns:xsl="http://www.w3.org/TR/WD-xsl" for?
and what is the different between xmlns:xsl="http://www.w3.org/1999/XSL/Transform ?
Any help will be grateful.
Regards,
Kelly Chen
null

Thanks for your response Rick and I hope it resolves Kelly's issue. But I too would like to know exactly what the difference is between the two examples Kelly provided because I have run into an issue where some code will run with the first example but not with the second and vice verse and without knowing why the parser is reporting an error it's hard to know which reference to use when:
1. Exactly what does a parser do with a namespace (or other URI) reference that causes it to treat the two examples differently?
2. Is there any documentation (or freeware source code) available that might show how namespace (and other) references are used to validate?
3. Does the parser compare the given string with a hard-coded string in the parser to see if they match? Does the parser look the URI up on the net to see if it exists? Does it do something like:
if uri = 'xmlns:xsl="http://www.w3.org/TR/WD-xsl"' then load namespace values from new.txt
else if uri = 'xmlns:xsl="http://www.w3.org/1999/XSL/Transform' then load namespace values from old.txt
Thanks again!
null

Howto add static text in xsl stylesheet

Hi,
I'am having problems trying to write a static text to a fixed length file using the file adapter.
I'am using the FlatStructure sample provided.
When I run the sample, there's no problem... But when I remove the mapping from tns:State <-> fix:State (in addr1Toaddr2.xsl) and change the fix:State to a static text (Set Text option in right mouse popup menu) then this text will NOT show up in the written fixed length file.
My addr1Toaddr2.xsl looks like this:
<?xml version="1.0" encoding="windows-1252"?>
<?oracle-xsl-mapper

<mapSources>
<source type="XSD">
<schema location="file://D:/OraBPELPM_2/integration/bpelpm/orabpel/samples/tutorials/121.FileAdapter/FlatStructure/address-csv.xsd"/>
<rootElement name="Root-Element" namespace="http://xmlns.oracle.com/pcbpel/demoSchema/csv"/>
</source>
</mapSources>
<mapTargets>
<target type="XSD">
<schema location="file://D:/OraBPELPM_2/integration/bpelpm/orabpel/samples/tutorials/121.FileAdapter/FlatStructure/address-fixedLength.xsd"/>
<rootElement name="Root-Element" namespace="http://xmlns.oracle.com/pcbpel/demoSchema/fixedLength"/>
</target>
</mapTargets>

?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://xmlns.oracle.com/pcbpel/demoSchema/csv" xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd" xmlns:fix="http://xmlns.oracle.com/pcbpel/demoSchema/fixedLength" xmlns:ldap="http://schemas.oracle.com/xpath/extension/ldap" xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20" xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:ora="http://schemas.oracle.com/xpath/extension" xmlns:orcl="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc" exclude-result-prefixes="xsl xsd tns nxsd fix ldap xp20 bpws ora orcl">
<xsl:template match="/">
<fix:Root-Element>
<xsl:for-each select="/tns:Root-Element/tns:Address">
<fix:Address>
<fix:Name>
<xsl:value-of select="tns:Name"/>
</fix:Name>
<fix:Street>
<xsl:value-of select="concat(tns:Street1,' ',tns:Street2)"/>
</fix:Street>
<fix:City>
<xsl:value-of select="string('C2345678901')"/>
</fix:City>
<fix:State>
<xsl:text disable-output-escaping="no">D2345678901
</xsl:text>
</fix:State>
<fix:Country>
<xsl:value-of select="string('E234567')"/>
</fix:Country>
</fix:Address>
</xsl:for-each>
</fix:Root-Element>
</xsl:template>
</xsl:stylesheet>
Note:
The construct "<xsl:value-of select="string('E234567')"/>" is my 'patch'to write a static text.
Can you tell me what I'am doing wrong? Or is this a bug...
greetings,
Jan.

Hi ,
I am assuming you are using Oracle JDeveloper XSL Mapper for designing the XSL. Currently , our XSL Mapper has a limitation due to that whenever you add any static text to target node in mapper, it adds an extra "\n" with that static text. And so our Native format translator doesn't find the definition for that and that's why it doesn't get printed in the file.
Workaround [although little painful] is remove those extra "\n" after you finish your XSL design.
We are working to fix this issue asap.
HTH.
Thanks,
Rakesh

XML having a JSP as XSL stylesheet ...

Hi,
In WLS 5.1 SP6, I have a XML which uses as XSL stylesheet a JSP served by WebLogic (<?xml/stylesheet href="style.jsp?order=3"?>
It appears that, when I try to pass more than one parameter to my JSP (i.e. "style.jsp?order=3&value=1"), the XML page does not "recognize" it anymore ... I have to pack all my parameters in a single string, pass it to my JSP and then parse it, which is quite ugly. Has somebody an explanation for this ? Thanks

Perhaps you need to encode the '&' in the stylesheet processing instruction.
<?xml/stylesheet href="style.jsp?order=3&value=1"?>
"Stephane Jantzen" <[email protected]> wrote in message
news:3a6ff593$[email protected]..
>
Hi,
In WLS 5.1 SP6, I have a XML which uses as XSL stylesheet a JSP served byWebLogic (<?xml/stylesheet href="style.jsp?order=3"?>
>
It appears that, when I try to pass more than one parameter to my JSP(i.e. "style.jsp?order=3&value=1"), the XML page does not "recognize" it
anymore ... I have to pack all my parameters in a single string, pass it to
my JSP and then parse it, which is quite ugly. Has somebody an explanation
for this ? Thanks
>

Portability problem for XSL stylesheet

Hi,
I created a xsl stylesheet and a java program which just do the normal xml transformation. however, they works fine in my windows XP environment, but once i move them to my Red hat (linux) environment, they stop working... why this happening? from the exception error, the problem occurs when the stylesheet is loaded. some friends suggest that i should try to use different xslt processors, but how should i do this in the run time?
(I am currently using Xerces2.6.2 to vaildate xml file and do the transformation)
Thanks for any help

You should look at the stacktrace from the exception and fix your problem based on what you see there.
Or you could post it here so we don't have to guess...

Error applying XSL stylesheet to XML

Hi,
after installed SPS 21 into portal we are facing an issue:
A contentadministrator wants to publish a new newsfact in portal, but get the following error message:
Error applying XSL stylesheet to XML:
com.sapportals.wcm.WcmException: com.sap.engine.lib.xml.util.NestedException: Variable '$system_config_activateClipboard' has not been bound to a value
     at com.sapportals.wcm.service.pipeline.Pipeline.handle(Pipeline.java:284)
Hope that somebody can give me some help.
thanks a lot in advance.
Regards,
Edwin

Hi Lorcan,
You help solved our issue, thanks a lot.
After generate the existing xml project with the Forms builder in the Content Management,
the contentadministratoris able to produce a new newsfact without errors
Regards, edwin
Posts: 123
Registered: 11/29/04
Forum Points: 346
Solved problem (10)
Very helpful answer (6)
Helpful answer (2)
   Re: Error applying XSL stylesheet to XML
Posted: Apr 19, 2010 11:13 AM    in response to: Edwin Theuns           Reply
Hi Edwin,
You need to recompile the xml forms project and that should resolve the issue. Unfortunately there is no alternative solution in such a scenario.
Regards,
Lorcan.

XSL stylesheet transformation of RSS feeds

Does Safari support XSL transformation of RSS feeds? Or does it always override XSL with its own RSS reader format? Details below:
I'm starting to mass-produce RSS feeds for our organization. We just want one file for each purpose which can be universally used in RSS readers, iTunes/other podcatchers, and web browsers. I created an XSL stylesheet for it which works perfectly in Internet Explorer, Opera, and Firefox (current release, anyway!), but Safari always adds the "feed://" prefix and displays it with its blue RSS reader format. Is there no way around this? If I take out the the <rss version="2.0"> header, it works, but then iTunes won't accept it.
Do I have to produce two separate files, the first without the RSS notation for Safari's sake, and the second with the notation for iTunes? That seems like an unnecessary step for us, and confusing for our users. Is there any way around this? I couldn't find any support documents that addressed this directly. Thanks -- Jim

You're getting a URL like this:context.getResourceAsStream("/Web-Inf/viewStudentDetails.xsl")and it looks like the MalformedURL exception is complaining about it. So my first step would be to look at it and see what's wrong with it.

Accessing lookup table from XSL stylesheet

HI Gentlemen,
Given two XMLTYPE tables: a Master and a Lookup. The Lookup table consists merely of {key, value} pairs. I am about to display Master table contents--subtrees selected from one big XMLTYPE column. The display process is governed by an appropriate XSL stylesheet. Master table elements have data only in their attributes. For example: <time U="2"/> which means that the value of the Unit attribute is 2, meaning "Minute" according to the Lookup table.
My question is: Does anybody of you know a fast and safe method to SELECT from the Master AND Lookup (inner join, as in a pure relational environment), thereby REPLACING the key value with its MEANING (textual interpretation). This would be extremely important as numeric codes do not have meaning to the user. User-friendly behavior requires that all important information be displayed at once. (Note that I have nothing against modifying my stylesheet to query the Lookup table as well, if no straightforward master-detail querying technique exists.)
Please give me an idea if you have.
Thank you in advance, kind regards:
Miklos HERBOLY

HI odie,
Here is the stuff you requested. I admit, it is fairly abundant, but you will see the structure and the main points. Some of the elements are multiple-occurrence, hence the XMLTABLE() solution was no good because of the large number of generated rows. The stylesheet would be ideal to display embedded "nested collections".
Please let me know if you have anything for me.
Thanks, regards
Miklos
HERE ARE THE XMLTYPE MASTER TABLE CONTENTS. TABLE IS NON-SCHEMA-BASED.
=====================================================================
SQL> select * from z;
XML_DOCUMENT
<?xml version="1.0" encoding="WINDOWS-1252"?>
<?xml-stylesheet type="text/xsl" href="file://c:/XSL/ziffer.xsl"?>
<ehd:ehd xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:ehd/go/001" xmlns:ehd="urn:ehd/001" ehd_versio
n="1.20">
<ehd:header>
<ehd:id EX="E7F454A3-0F6E-460e-A495-BBBBBBBBBBB3" RT="1.2.276.0.76.3.1.1"/>
<ehd:version_nbr V="1"/>
<ehd:document_type_cd V="851"/>
<ehd:service_tmr V="2006-07-01..2007-12-31"/>
<ehd:origination_dttm V="2006-05-03"/>
<ehd:provider>
<ehd:provider.type_cd V="KV" S="1.2.276.0.76.5.104" SV="1.0"/>
<ehd:person>
<ehd:id EX="3223" RT="2.3.5.3.T.e.s.t" RTV="1.10"/>
<ehd:person_name>
<ehd:nm>
<ehd:GIV V="Hans"/>
<ehd:PFX V="von"/>
<ehd:FAM V="Mustermann"/>
</ehd:nm>
</ehd:person_name>
<ehd:organization.nm V="KV Hessen"/>
<ehd:addr>
<ehd:STR V="Ottostr."/>
<ehd:HNR V="12"/>
<ehd:ZIP V="50859"/>
<ehd:CTY V="Köln"/>
</ehd:addr>
<ehd:telecom V="tel:030-4005-2121 begin_of_the_skype_highlighting 030-4005-2121 end_of_the_skype_highlighting begin_of_the_skype_highlighting 030-4005-2121 end_of_the_skype_highlighting"/>
</ehd:person>
<ehd:organization>
<ehd:id EX="46" RT="1.2.276.0.76.5.233"/>
</ehd:organization>
</ehd:provider>
<ehd:interface>
<ehd:id EX="SDEBM" RT="1.2.276.0.76.5.109" RTV="1.0"/>
<ehd:interface.nm V="Gebührenordnungsstammdatei / Satzart 851"/>
<ehd:version V="01.30"/>
</ehd:interface>
</ehd:header>
<ehd:body>
<gnr_liste>
<gnr V="01700V" USE="46" USE-DOMAIN="1.2.276.0.76.5.233" VT="2006-05-03">
<allgemein>
<gueltigkeit>
<service_tmr V="2006-07-01.."/>
<effective_tmr V="2006-07-01.."/>
</gueltigkeit>
<legende>
<kap_bez V="1.7" DN="Gesundheits- und Früherkennungsuntersuchungen, Mutterschaftsvorsorge, Empfängnisregelun
g und Schwangerschaftsabbruch (vormals Sonstige Hilfen)">
<bereich V="II" DN="Arztgruppenübergreifende allgemeine Leistungen"/>
<kapitel V="1" DN="Allgemeine Leistungen"/>
<abschnitt V="7" DN="Gesundheits- und Früherkennungsuntersuchungen, Mutterschaftsvorsorge, Empfängnisregel
ung und Schwangerschaftsabbruch (vormals Sonstige Hilfen)"/>
</kap_bez>
<kurztext V="Grundpauschale für Fachärzte für Laboratoriumsmedizin u.a."/>
<langtext V="Grundpauschale für Fachärzte für Laboratoriumsmedizin, Mikrobiologie und Infektionsepidemiologi
e, Transfusionsmedizin und ermächtigte Fachwissenschaftler der Medizin für die Erbringung von Laborleistungen gemäß den
Richtlinien des Gemeinsamen Bundesausschusses über die ärztliche Betreuung während der Schwangerschaft und nach der En
tb indung (Mutterschafts-Richtlinien) und/oder der Richtlinien des Gemeinsamen Bundesausschusses zur Empfängnisregelung
und zum Schwangerschaftsabbruch bei Probeneinsendung, "/>
<quittungstext V="Grundpauschale für Fachärzte für Laboratoriumsmedizin u.a."/>
</legende>
<anmerkungen_liste>
<anmerkung V="Die Leistung nach der Nr. 01100 ist nicht berechnungsfähig, wenn Sprechstunden vor 07:00 Uhr o
der nach 19:00 Uhr stattfinden oder Patienten zu diesen Zeiten bestellt werden."/>
<anmerkung V="Im Rahmen der unvorhergesehenen Inanspruchnahme des Vertragsarztes ist die Leistung nach der N
r. 01100 auch dann nur einmal berechnungsfähig, wenn es sich um eine Gruppenbehandlung handelt."/>
<anmerkung V="Die Leistung nach der Nr. 01100 ist ausschließlich bei kurativer Behandlung berechnungsfähig."
/>
</anmerkungen_liste>
<leistungsinhalt>
<komplex V="OBLIGAT">
<leistung V="Persönlicher Arzt-Patienten-Kontakt im organisierten Not(fall)dienst"/>
</komplex>
<komplex V="FAKULTATIV">
<leistung V="Beratung und Behandlung bis zu 10 Minuten Dauer,"/>
<leistung V="2...Beratung und Behandlung bis zu 10 Minuten Dauer,"/>
<leistung V="3...Beratung und Behandlung bis zu 10 Minuten Dauer,"/>
</komplex>
<komplex V="FAKULTATIV">
<leistung V="In Anhang 1 aufgeführte Leistungen,"/>
</komplex>
</leistungsinhalt>
<bewertung_liste>
<bewertung V="5595" U="1" U-DOMAIN="1.2.276.0.76.5.236">
<leistungserbringerart V="1" S="1.2.276.0.76.5.234" SV="1.02"/>
<leistung_typ V="GL"/>
</bewertung>
<bewertung V="2797.5" U="1" U-DOMAIN="1.2.276.0.76.5.236">
<leistungserbringerart V="2" S="1.2.276.0.76.5.234" SV="1.02"/>
<leistung_typ V="GL"/>
</bewertung>
</bewertung_liste>
<zeitbedarf_liste>
<zeit V="21" U="2" U-DOMAIN="1.2.276.0.76.5.238">
<leistung_typ V="AL"/>
</zeit>
</zeitbedarf_liste>
<pruefzeit V="1" U="2" U-DOMAIN="1.2.276.0.76.5.238">
<zeitprofilart V="3" S="1.2.276.0.76.5.228" SV="1.00"/>
</pruefzeit>
<rlv V="0" S="1.2.276.0.76.5.241" SV="1.00"/>
<leistungsgruppe V="10" S="1.2.276.0.76.5.227" SV="1.00"/>
</allgemein>
<bedingung>
<fachgruppe_liste V="true">
<versorgungsbereich V="2" S="1.2.276.0.76.5.237" SV="1.01">
<fachgruppe V="110" S="1.2.276.0.76.5.114" SV="1.00"/>
<fachgruppe V="111" S="1.2.276.0.76.5.114" SV="1.00"/>
<fachgruppe V="112" S="1.2.276.0.76.5.114" SV="1.00"/>
<fachgruppe V="303" S="1.2.276.0.76.5.114" SV="1.00"/>
<fachgruppe V="357" S="1.2.276.0.76.5.114" SV="1.00"/>
<fachgruppe V="501" S="1.2.276.0.76.5.114" SV="1.00"/>
<fachgruppe V="532" S="1.2.276.0.76.5.114" SV="1.00"/>
</versorgungsbereich>
</fachgruppe_liste>
<anzahlbedingung_liste>
<bezugsraum V="1" U="7" U-DOMAIN="1.2.276.0.76.5.226">
<anzahl V="1"/>
</bezugsraum>
</anzahlbedingung_liste>
<abr_best V="je Behandlungsfall mit Auftragsleistung(en) der Abschnitte 1.7.4 und/oder 1.7.5"/>
</bedingung>
<regel>
<ausschluss_liste>
<bezugsraum V="1" U="7" U-DOMAIN="1.2.276.0.76.5.226">
<gnr_liste V="false">
<gnr V="12220" DN="Grundpauschale für Fachärzte für Laboratoriumsmedizin u.a."/>
<gnr V="12225" DN="Grundpauschale für Vertragsärzte aus nicht in der Nr. 12220 aufgeführten Arztgruppen
bei Probeneinsendung"/>
</gnr_liste>
</bezugsraum>
</ausschluss_liste>
</regel>
<kv V="46" S="1.2.276.0.76.5.233" SV="1.01">
<kennzeichen>
<arztpraxis V="1"/>
</kennzeichen>
<kv_bewertung_liste>
<kv_bewertung V="100" U="1" U-DOMAIN="1.2.276.0.76.5.236">
<leistungserbringerart V="2" S="1.2.276.0.76.5.234" SV="1.02"/>
</kv_bewertung>
<kv_bewertung V="150" U="1" U-DOMAIN="1.2.276.0.76.5.236">
<leistungserbringerart V="1" S="1.2.276.0.76.5.234" SV="1.02"/>
</kv_bewertung>
</kv_bewertung_liste>
</kv>
<vdx>
<gkv_kontenart_liste>
<gkv_kontenart V="530" S="1.2.276.0.76.5.258"/>
<gkv_kontenart V="463" S="1.2.276.0.76.5.258"/>
</gkv_kontenart_liste>
</vdx>
</gnr>
</gnr_liste>
</ehd:body>
</ehd:ehd>
1 Zeile wurde ausgewählt.
SQL> spool off
==========================
HERE IS THE XQUERY COMMAND
==========================
<?xml version="1.0" encoding='windows-1252'?>

<page xmlns:xsql="urn:oracle-xsql" connection="gksconnection">
<xsql:query xmlns:xsql="urn:oracle-xsql">
SELECT XMLQuery('xquery version "1.0";
declare namespace n1="urn:ehd/001";
declare namespace n2="urn:ehd/go/001";
let $i := /n1:ehd/n1:body/n2:gnr_liste/n2:gnr
where $i[@n2:V = "01700V"]
return $i'
PASSING xml_document
RETURNING CONTENT)
FROM z
</xsql:query>
</page>
======================
HERE IS THE STYLESHEET - relevant part only
======================
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:ehd="urn:ehd/001" xmlns:pe="urn:ehd/go/001">
<xsl:output method="html"/>
<xsl:template match="pe:gnr">
<html>
<head>
<title>EBM Ziffer</title>
<style type="text/css">
table
border-collapse:collapse;
table, td, th
border:1px solid black;
</style>
</head>
<body style="font-family:verdana;color:black">
<h2><xsl:text>Ziffer: </xsl:text>
<xsl:value-of select="@V"/>
</h2>
<table border="1">
<tr>
<td><xsl:text>KV</xsl:text></td>
<td><xsl:value-of select="@USE"/></td>
</tr>
<tr>
<td><xsl:text>Gültigkeit</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:gueltigkeit/pe:service_tmr/@V"/></td>
</tr>
<tr>
<td><xsl:text>Bezeichnung Kapitel</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:kap_bez/@V"/>
<xsl:text> </xsl:text>
<xsl:value-of select="pe:allgemein/pe:legende/pe:kap_bez/@DN"/></td>
</tr>
<tr>
<td><xsl:text>Bereich</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:kap_bez/pe:bereich/@V"/>
<xsl:text> </xsl:text>
<xsl:value-of select="pe:allgemein/pe:legende/pe:kap_bez/pe:bereich/@DN"/></td>
</tr>
<tr>
<td><xsl:text>Kapitel</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:kap_bez/pe:kapitel/@V"/>
<xsl:text> </xsl:text>
<xsl:value-of select="pe:allgemein/pe:legende/pe:kap_bez/pe:kapitel/@DN"/></td>
</tr>
<tr>
<td><xsl:text>Abschnitt</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:kap_bez/pe:abschnitt/@DN"/></td>
</tr>
<tr>
<td><xsl:text>Unterabschnitt</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:kap_bez/pe:uabschnitt/@DN"/></td>
</tr>
<tr>
<td><xsl:text>Block</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:kap_bez/pe:block/@DN"/></td>
</tr>
<tr>
<td><xsl:text>Kurztext</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:kurztext/@V"/></td>
</tr>
<tr>
<td><xsl:text>Langtext</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:langtext/@V"/></td>
</tr>
<tr>
<td><xsl:text>Langtext (Fortsetzung)</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:langtext_continued/@V"/></td>
</tr>
<tr>
<td><xsl:text>Quittungstext</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:quittungstext/@V"/></td>
</tr>
</table>

<h4><xsl:text>Anmerkungen</xsl:text></h4>
<table border="1">
<xsl:for-each select="pe:allgemein/pe:anmerkungen_liste/pe:anmerkung">
<tr>
<td><xsl:value-of select="@V"/></td>
</tr>
</xsl:for-each>
</table>

<h4><xsl:text>Leistungsinhalt</xsl:text></h4>
<table border="1" >
<tr>
<th><xsl:text>Komplex</xsl:text></th>
<th><xsl:text>Leistung</xsl:text></th>
</tr>
<xsl:for-each select="pe:allgemein/pe:leistungsinhalt/pe:komplex">
<tr>
<td><xsl:value-of select="@V"/></td>
<td>
<xsl:for-each select="pe:leistung">
<xsl:value-of select="@V"/>
</xsl:for-each>
</td>
</tr>
</xsl:for-each>
</table>

<h4><xsl:text>Bewertungen</xsl:text></h4>
<table border="1">
<tr>
<th><xsl:text>Bewertung</xsl:text></th>
<th><xsl:text>Einheit</xsl:text></th>
<th><xsl:text>Gebührenordnung</xsl:text></th>
<th><xsl:text>Leistungserbringerart</xsl:text></th>
<th><xsl:text>Leistungstyp</xsl:text></th>
<th><xsl:text>Versorgungsgebiet</xsl:text></th>
</tr>
<xsl:for-each select="pe:allgemein/pe:bewertung_liste/pe:bewertung">
<tr>
<td><xsl:value-of select="@V"/></td>
<td><xsl:value-of select="@U"/></td>
<td><xsl:value-of select="pe:gebuehrenordnung/@V"/></td>
<td><xsl:value-of select="pe:leistungserbringerart/@V"/></td>
<td><xsl:value-of select="pe:leistung_typ/@V"/></td>
<td><xsl:value-of select="pe:versorgungsgebiet/@V"/></td>
</tr>
</xsl:for-each>
</table>

<h4><xsl:text>Zeitbedarfliste</xsl:text></h4>
<table border="1">
<tr>
<th><xsl:text>Zeit</xsl:text></th>
<th><xsl:text>Einheit</xsl:text></th>
<th><xsl:text>Leistungstyp</xsl:text></th>
</tr>
<xsl:for-each select="pe:allgemein/pe:zeitbedarf_liste/pe:zeit">
<tr>
<td><xsl:value-of select="@V"/></td>
<td><xsl:value-of select="@U"/></td>
<td><xsl:value-of select="pe:leistung_typ/@V"/></td>
</tr>
</xsl:for-each>
</table>
</body>
</html>
</xsl:template>
</xsl:stylesheet>
=====================================
THE REQUESTED SAMPLE LOOKUP TABLE FOR TIME UNITS
=====================================
<keytabs>
−
<keytab S="1.2.276.0.76.5.238" SN="S_KBV_ZEITEINHEIT" SV="1.00">
<key V="1" DN="Sekunde" S="1.2.276.0.76.5.238" SV="1.00"/>
<key V="2" DN="Minute" S="1.2.276.0.76.5.238" SV="1.00"/>
<key V="3" DN="Stunde" S="1.2.276.0.76.5.238" SV="1.00"/>
<key V="4" DN="Tag" S="1.2.276.0.76.5.238" SV="1.00"/>
<key V="5" DN="Woche" S="1.2.276.0.76.5.238" SV="1.00"/>
<key V="6" DN="Monat" S="1.2.276.0.76.5.238" SV="1.00"/>
<key V="7" DN="Quartal" S="1.2.276.0.76.5.238" SV="1.00"/>
<key V="8" DN="Jahr" S="1.2.276.0.76.5.238" SV="1.00"/>
</keytab>
</keytabs>
==================================================================================================
And this is, from an earlier trial with XMLTABLE() what I become when stylesheet is commented out. Only for your information here!
Due to the three "Anmerkung" three rows were generated. What is this notation? I got it when
executing the XSQL sheet without stylesheet. Produced by the browser.
I can not find any info in the whole web.
==================================================================================================

<page>
<ROWSET>
<ROW num="1">
<ZIFFER>01700V</ZIFFER>
<GUELTIGKEIT>2006-07-01..</GUELTIGKEIT>
<KAP_NR>1.7</KAP_NR>
<KAP_BEZ>
Gesundheits- und Früherkennungsuntersuchungen, Mutterschaftsvorsorge, Empfängnisregelun g und Schwangerschaftsabbruch (vormals Sonstige Hilfen)
</KAP_BEZ>
<BEREICH_NR>II</BEREICH_NR>
<BEREICH>Arztgruppenübergreifende allgemeine Leistungen</BEREICH>
<KAPITEL_NR>1</KAPITEL_NR>
<KAPITEL>Allgemeine Leistungen</KAPITEL>
<ABSCHNITT>
Gesundheits- und Früherkennungsuntersuchungen, Mutterschaftsvorsorge, Empfängnisregel ung und Schwangerschaftsabbruch (vormals Sonstige Hilfen)
</ABSCHNITT>
<KURZTEXT>
Grundpauschale für Fachärzte für Laboratoriumsmedizin u.a.
</KURZTEXT>
<LANGTEXT>
Grundpauschale für Fachärzte für Laboratoriumsmedizin, Mikrobiologie und Infektionsepidemiologi e, Transfusionsmedizin und ermächtigte Fachwissenschaftler der Medizin für die Erbringung von Laborleistungen gemäß den Richtlinien des Gemeinsamen Bundesauss
</LANGTEXT>
<QUITTUNGSTEXT>
Grundpauschale für Fachärzte für Laboratoriumsmedizin u.a.
</QUITTUNGSTEXT>
<ANMERKUNG>
Die Leistung nach der Nr. 01100 ist nicht berechnungsfähig, wenn Sprechstunden vor 07:00 Uhr oder nach 19:00 Uhr stattfinden oder Patienten zu diesen Zeiten bestellt werden.
</ANMERKUNG>
</ROW>
<ROW num="2">
<ZIFFER>01700V</ZIFFER>
</ROW>
</ROWSET>
</page>

Expert in xsl - stylesheets for unicode (UTF8)

Hi,
I am looking for an expert in xsl-stylesheets for unicode (UTF-8 format) in order to check the syntax of a stylesheet for the browser-based PI-Sheet in SAP ERP PP-PI.
Can you advise someone ?
Thanks & BR,
Miriam

Hi Kannan,
thanks for your answer!
Unfortunately this problem is a bit more tricky.
We are looking for so. who really can check the syntax of ~ 1.000 lines of XSL coding. The problem is that it cannot be converted to UTF8 because of syntax errors.
=> Do you have an idea who could help here?
Thanks a lot, best regards,
Miriam

Required attribute version missing from element xsl:stylesheet

Tools:
Jdeveloper : 10.1.3.3
Error:
Every time I add transform process activity and try to create mappings I am not able to save them.
In source view I see this error "Required attribute version missing from element xsl:stylesheet".
I cannot continue and do not understand how to proceed.
Any ideas ?

We have the same problem here from time to time. This has to be some kind of bug in JDeveloper. There is nothing wrong with our xsl files! But for some reason JDeveloper complains about the version attribute of xsl:stylesheet which in all the cases I've seen IS THERE!
Sometimes restarting JDeveloper helps - sometimes not. I even ended up reinstalling JDeveloper a few times.
I hoped this would be fixed in 10.1.3.3 (we use 10.1.3.2) but sadly it's not it seems.

How to create a Layout Template of XSL Stylesheet (XML) type

Hello,
I am new to OBIEE. I need to generate layout template to be of XSL Stylesheet (XML) format. ( output report to be in XML format )
Please share if anybody know How to create a Layout Template of XSL Stylesheet (XML) type for BI Publisher.
Waiting for your reply

Look at this, for example.
http://xlspe.com/news.php?item.15.1

XSL-1009: Attribute 'xsl:version' not found in 'xsl:stylesheet'

I'm just starting to test XML in Oracle 8.1.7 for NT, and received the following error while testing the Oracle provided "xslsample" procedure. I modified the "iden.xls" stylesheet and added version="1.0", but still receive the same error.
execute xslsample('C:\XML\Sample','family.xml','iden.xsl','family.out','errors.txt');
Parsing XML document C:\XML\Sample/family.xml
Parsing XSL document C:\XML\Sample/iden.xsl
The id is16777216
The id is16777217
XSL Root element information
Qualified Name: xsl:stylesheet
Local Name: stylesheet
Namespace: http://www.w3.org/XSL/Transform/1.0
Expanded Name: http://www.w3.org/XSL/Transform/1.0:stylesheet
A total of 1 XSL instructions were found in the stylesheet
BEGIN xslsample('C:\XML\Sample','family.xml','iden.xsl','family.out','errors.txt'); END;
ERROR at line 1:
ORA-20100: Error occurred while processing: XSL-1009: Attribute 'xsl:version'
not found in 'xsl:stylesheet'.
ORA-06512: at "SCOTT.XSLPROCESSOR", line 22
ORA-06512: at "SCOTT.XSLPROCESSOR", line 346
ORA-06512: at "SCOTT.XSLSAMPLE", line 59
ORA-06512: at line 1
null

There is a bug in the demo stylesheet. In iden.xsl the line:
<xsl:stylesheet xmlns:xsl="http://www.w3.org/XSL/Transform/1.0">should instead be:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

Uploading XSL stylesheet

Similar Messages

Maybe you are looking for