XSL-FO PO_STANDARD_PO.xsl probem

Hi,
In a field SHIP_TO_ADDRESS_INFO, you have a string with a format 'COUNTRY, POSTAL CODE' but i want 'POSTAL_CODE COUNTRY'.
Ex: New York, NY 10022-3422
Have you an solution ?
Thank you
Nicolas

Use Extended SQL Functions
Use instr and substring to display in the manner you want.
<?xdofx:substr(NAME, instr(NAME,',')+1 ) ||','|| substr(NAME, 0,instr(NAME,',') )?>
Change the 'NAME' to the field you want :)

Similar Messages

Named file entity do not load in from xml files(eg., !DOCTYPE PURANA SYSTEM "purana.dtd" [ !ENTITY CHAPTER_1 SYSTEM "./chapter_1.xml" ] ?xml-stylesheet type="text/xsl" href="purana.xsl"? PURANA TITLE /TITLE &CHAPTER_1; /PURANA )

I create several file name entities in an external DTD.
It used to work sometimes back but I don't remember now when it begun to fail.
typical document for eg., is given below:
<!DOCTYPE PURANA SYSTEM "purana.dtd" [ <!ENTITY CHAPTER_1 SYSTEM "./chapter_1.xml"> ]>
<?xml-stylesheet type="text/xsl" href="purana.xsl"?> <PURANA>
<TITLE>
</TITLE>
&CHAPTER_1;
</PURANA>)
the abbreviation used to work by loading the file using XSL script,
but now it does not even work when the entity is defined within the XML document itself.

Too difficult???
Please helped me.
Thank you, Theo

How can i include the file, not xsl file, to xsl ?

Hi,
I would like to include a file called 'head.inc' to xsl. How can i do that ?
the content of the head.inc is simple, just a part of the html code.
say:
<html>
<head></head>
<body>
i can't use <xsl:import /> or <xsl:include />, which tag i can ??
Thx a lot !

You could use the document() function to access it. But it would have to be a valid XML file, XSL doesn't allow you to risk including a fragment that might cause the result to be invalid XML. Which could happen with your example. Remember that XML and XSL work with elements, not with tags.

Xsl:import and xsl:call-template errors for xslt in mediator (ORAMED-03601)

Hello,
I decided for performance issues with bpel execution to use a mediator instead.
In my requester i have a mediator that justs recieves an xml message, uses an xsl transformation (version 2) on that message and then sends it to the EBS.
The xsl file that's works correctly when used in a bpel process has both <xsl:import..../>and <xsl:call_template.../> tags.
When i tried and used the same xsl in the mediator i get an ORAMED-03601 error:
ORAMED-03601:[Invalid transformer configuration]Unable to create transformer. It could be because of transformation file or configuration issues. Reason : "xsl/Xform_PriceListListABMReqMsg_to_PriceListEBMReqMsg.xsl"Possible Fix:Check log file for any exceptions and contact Oracle Support Services for further help
It works correctly again if i comment/remove all the imports and call-template and incorporate them in the xsl file itself.
Do anyone know if there are some limitations using xsl in a mediator instead of a bpel?

Hi,
I have a problem with call-template. I have passed
sed some parameter with call-template tag and used
that parameter in the conditional check tag <xsl:if>
i am getting the error. Can any body tell how to use
this? I actuall want to dynamically pass the tag name
as the parameter and check the attribute value of the
tag passed in the if condition and then i want to
person some action. How can i do it?
Here is the call-template code:
<xsl:call-template name="selected-unselected">
<xsl:with-param
ram name="currentTag">motor-carrier</xsl:with-param>
</xsl:call-template>
Here is the template definition:
<xsl:template name="selected-unselected">
<xsl:param
m name="currentTag">Quick-Quote</xsl:param>
     <xsl:if test="./{$currentTag}/@selected='true'">
          <xsl:text>checked</xsl:text>
     </xsl:if>
     <xsl:if test="./{$currentTag}/@selected='false'">
          <xsl:text>Unchecked</xsl:text>
     </xsl:if>
</xsl:template>
Here is the sample xml code:
<motor-carrier selected="true"/>
<motor-truck selected="false"/>
<sched-mobile-equip selected="false"/>
Here instead of writing the condition check for every
tag i want to write it once and dynamically pass the
tag name as parameter to the template. If the
attribute of the tag has value true then one message
should be displayed otherwise a different message
should be displayed.try this:
<xsl:template name="selected-unselected">
     <xsl:paramm name="currentTag">Quick-Quote</xsl:param>
     <xsl:if test="./*[name()=$currentTag]/@selected='true'">
          <xsl:text>checked</xsl:text>
     </xsl:if>
     <xsl:if test="./*[name()=$currentTag]/@selected='false'">
          <xsl:text>Unchecked</xsl:text>
     </xsl:if>
</xsl:template>

Problem with xsl:import and xsl:apply-templates select="element_name"

I import a xsl tranformation into another xsl file.
During the transformation i want to limit the transformation to certain xml elements using the select attribute in apply-templates. However if I want restrict to xml elements whose templates are defined in the imported file, they will not be called.
I'm using currently JWSDP1.4 but problem was also with 1.3.
Can anybody help: Is this not xslt spec compliant or just a bug inXALAN ?
regards pszawlow

Solved it by myself:
the problem was not the import but the following:
xml file: looks like:
<a>
   <b>
   </b>
    <c>
    </c>
</a>xsl file looked like and should omit output of <c> </c>:
<xsl:template match="/">
<xsl:apply-templates select="b" />
</xsl:template>
<xsl:template match="b">
</xsl:template>
However / is not the level <a>, which I thought. So there was no matching <b>.
I changed the xsl file to:
<xsl:template match="/">
<xsl:apply-templates />
</xsl:template>
<xsl:template match="a">
<xsl:apply-templates select="b" />
</xsl:template>
<xsl:template match="b">
</xsl:template>
and it worked !

Xsl question - call xsl from another xsl

Hi,
I have a xsl which should be invoked from another xsl. I have a transformheader.xsl which transforms the header values. I would like to invoke this xsl from various client xsl files.(to transform the header).
transformheader.xsl should take the header as input and give header as output.
Basically I am moving the header transform logic to one xsl file & reuse it.
Can you please help me with the syntax or any links to samples/docs?
transformheader.xsl:
<?xml version="1.0" encoding="UTF-8" ?>
<xsl:stylesheet version="1.0">
<xsl:template match="/">
<ns1:header>
<ns1:ebmAID>
<xsl:value-of select="/ns1:header/ns1:ebmBID"/>
</ns1:ebmAID>
<ns1:ebmBID>
<xsl:value-of select="/ns1:header/ns1:ebmAID"/>
</ns1:ebmBID>
</ns1:header>
</xsl:template>
</xsl:stylesheet>
client1.xsl(transforms one message to other, both has the header)
<?xml version="1.0" encoding="UTF-8" ?>
<?oracle-xsl-mapper......>
<xsl:stylesheet version="1.0">
<xsl:template match="/">
<tns:sampleee>
<hdr:header>
===== invoke the transformheader.xsl to insert the header here
</hdr:header>
<tns:body>
<xsl:for-each select="xxxxx">
</tns:body>
</tns:sampleee>
</xsl:template>
</xsl:stylesheet>

Here you go:
CreateHeader.xsl
<xsl:stylesheet version="1.0"
     xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
     xmlns:inp="http://temp.org/input"
        xmlns:out="http://temp.org/output"
                >
     <xsl:template name="CreateHeader">
             <xsl:param name="InputHeader"/>
               <out:header>
                    <out:ebmAID>
                         <xsl:value-of select="/inp:header/inp:ebmID"/>
                    </out:ebmAID>
                    <out:ebmBID>
                         <xsl:value-of select="/inp:header/inp:ebmContextID"/>
                    </out:ebmBID>
               </out:header>
     </xsl:template>
</xsl:stylesheet>Main XSL:
<xsl:stylesheet version="1.0"
     xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
     xmlns:inp="http://temp.org/input"
        xmlns:out="http://temp.org/output"
                >
     
     <xsl:import href="CreateHeader.xsl"/>
     <xsl:template match="/">
          <out:RootElement>
               
               <xsl:call-template name="CreateHeader">
                    <xsl:with-param name="InputHeader" select="inp:header"/>
               </xsl:call-template>
               <xsl:for-each select="/inp:body">
                    <out:body>
                         
                    </out:body>
               </xsl:for-each>
          </out:RootElement>
     </xsl:template>
</xsl:stylesheet>

Oracle.xml.parser.v2.XSLException: XSL-1009: Attribute 'xsl:version' not found in 'RO

I'm using the oracle.xml.parser.v2. The files (xml, xsl) are:
<?xml version="1.0" ?>
<?xml-stylesheet type="text/xsl" href="king.xsl" ?>
<ROWSET>
<ROW>
<EMPNO>7839</EMPNO>
<ENAME>KING</ENAME>
</ROW>
</ROWSET>
<?xml version="1.0"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:output method="xml" indent="yes"/>
<xsl:template match="/">
<INVITATION>
<TO>
<xsl:value-of select="ROWSET/ROW/ENAME"/>
<xsl:text> &; FAMILY </xsl:text>
</TO>
</INVITATION>
</xsl:template>
</xsl:stylesheet>
The error is: oracle.xml.parser.v2.XSLException: XSL-1009: Attribute 'xsl:version' not found in 'ROWSET'.
The files are well formed (tested with XML Spy 3.5). Can you see what's the problem? or is it a bug with the parser?
help,
Alberto
null

I encountered the same problem. When I change the order of the XML and XSL files, i am the same problem.
Perhaps it's the environment AIX 4.3.3, JDK IBM 1.2.2 with JIT disable (because when JIT is enable some other problems become)??
How can i resolve this bug ?
Thanks.
null

XSL-1009: Attribute 'xsl:version' not found in 'BatchDelivery'.

I have seen this error in many postings and have never understood just what was being transgressed. I am trying to prepare an xml file for inserting into a table using OracleXML putXML but I never get that far. I have exhausted all my guesses and interpretations of others' postings.
C:\oracle\Samples\BatchDelivery>oraxsl -debug batchdelivery.xsl batchdelivery.txt out.xml
Error occurred while processing batchdelivery.txt: file:/C:/oracle/Samples/Batch
Delivery/batchdelivery.txt<Line 2, Column 83>: XSL-1009: Attribute 'xsl:version' not found in 'BatchDelivery'.
C:\oracle\Samples\BatchDelivery>
batchdelivery.xsl:
<ROWSET xsl.version="1.0" xmlns:xsl="http://www.w3.org/1999/xsl/Transform" >
<xsl:for-each select="BatchDelivery/BatchConfiguration">
<ROW >
<KEYCONFIGID><xsl:value-of select="KeyConfigID"/></KEYCONFIGID>
<CARDREQUIREMENTSID><xsl:value-of select="CARDREQUIREMENTSID"/></CARDREQUIREMENTSID>
<CARDPRODUCTID><xsl:value-of select="CardProductID"/></CARDPRODUCTID>
<PHYSICALDESCRIPTIONID><xsl:value-of select="PhysicalDescriptionID"/></PHYSICALDESCRIPTIONID>
<LOGICALDESCRIPTIONID><xsl:value-of select="LogicalDescriptionID"/></LOGICALDESCRIPTIONID>
<PACKAGECONFIGID><xsl:value-of select="PackageConfigID"/></PACKAGECONFIGID>
</ROW>
</xsl:for-each>
</ROWSET>
batchdelivery.xml
<BatchDelivery xmlns="http://www.activcard.com/xml/ns/acms/batch/1.0" xmlns:xsl="http://www.w3.org/2001/XMLSchema-instance"
xsl:schemaLocation="http://www.activcard.com/xml/ns/acms/batch/1.0/batch_1.0.xsd">
     <Header>
          <DocID>BD-CAC-0000000001</DocID>
          <Date>2001-06-15T00:00:00</Date>
          <Author>Oberthur</Author>
          <Comment>Batch Delivery sample</Comment>
     </Header>
     <DeliveryPlaceInfo>
          <DeliveryPlaceID>OCS-01</DeliveryPlaceID >
          <OrganizationName>Oberthur</OrganizationName>
          <Address>1600 Vault St</Address>
          <City>Storage City</City>
          <ZipCode>33333</ZipCode>
          <State>CA</State>
          <Country>USA</Country>
          <MainContactPerson>
               <PersonName>joeDoe</PersonName>
               <Tel1>1-608-578-5000</Tel1>
               <Tel2/>
               <Fax/>
               <Email>[email protected]</Email>
          </MainContactPerson>
     </DeliveryPlaceInfo>
     <CardManufacturerInfo>
          <CardManufacturerID>Oberthur-01</CardManufacturerID>
          <OrganizationName>Oberthur Card Systems</OrganizationName>
          <Address/>
          <City/>
          <ZipCode/>
          <State/>
          <Country/>
          <MainContactPerson>
               <PersonName/>
               <Tel1/>
               <Tel2/>
               <Fax/>
               <Email/>
          </MainContactPerson>
     </CardManufacturerInfo>
     <BatchConfiguration>
     <KeyConfigID>0000000002</KeyConfigID>     <CardRequirementsID>0000000001</CardRequirementsID>
     <CardProductID>0000000002</CardProductID>     <PhysicalDescriptionID>0000000001</PhysicalDescriptionID>
          <LogicalDescriptionID>0000000001</LogicalDescriptionID>
          <PackageConfigID>0000000001</PackageConfigID>
     </BatchConfiguration>
</BatchDelivery>

I am cursed by the tendency to mistype whenever I repeatedly cut/paste/test/post! Changing the "." to ":" has no affect whatsoever. I wish it did!
Mike

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">

Loading XSL file in XSL Transforam action at run time

Hello everyone ,
I want to use XSL Transforamtion action in weblogic integration and name of
XSL file should pick at run time from a variable.
I am using :"com.bea.wlxt.repository" package APIs for connecting to repository &
get the XSL file from it. Check the following code
RepositoryURL repURL = new RepositoryURL();
URL myUrl = repURL.create
("wlxt://xslt/4112req-mli0018req-xsl");
InputStream in = myUrl.openStream();
This code gives me error that "java.io.IOException:Entity 4112req-mli0018req-xsl"
not found in repository.
Where as the file is actually present in the root of the repository. I am not sure
why I am getting this error. Has somebody done something similar ? I am doing something
wrong ?
Any help in this regard is appreciated.
Thanks in advance
-Kiran R.

Hi !
I'm struggelig with the same problem, did you find any solution ?
Thanks in advance
Jon Rustand
"Kiran Rane" <[email protected]> wrote:
>
Hello everyone ,
I want to use XSL Transforamtion action in weblogic integration
and name of
XSL file should pick at run time from a variable.
I am using :"com.bea.wlxt.repository" package APIs for connecting to
repository &
get the XSL file from it. Check the following code
RepositoryURL repURL = new RepositoryURL();
URL myUrl = repURL.create
("wlxt://xslt/4112req-mli0018req-xsl");
InputStream in = myUrl.openStream();
This code gives me error that "java.io.IOException:Entity 4112req-mli0018req-xsl"
not found in repository.
Where as the file is actually present in the root of the repository.
I am not sure
why I am getting this error. Has somebody done something similar ? I
am doing something
wrong ?
Any help in this regard is appreciated.
Thanks in advance
-Kiran R.

Xsl:import in XSL templates

Hi,
I have BIP version 5.6.3 in EBS.
I have an XSL-TEXT template and I would like to use the <xsl:import> statement to import subtemplates.
So I do:
<xsl:import href="http://myapps.xxx.yy:8000/OA_MEDIA/my_subtemplate.xsl"/>This works pretty well, if I place my template file in the $OA_MEDIA folder on my APPS server.
BUT: This is using an absolute path to my server (myapps.xxx.yy:8000 in this case). For my development environments this absolute path is different of course.
So my question:
Does anybody know how to refer to my subtemplates by relative paths, or to construct an xsl:import statement that allows to have different paths based on the environment that I am currently working on?
Thanks,
David.

Hi,
well, the templates are always in the same path on the server, they are all either uploaded to Template Manager in BIP or stored in $OA_MEDIA.
But the server name is different of course.
Oracle has implemented a nice feature to reference to subtemples in RTF templates, would be nice if one could do the same in XSLT.
Thanks,
David.

XSL transformation with xsl:import generates exceptions

I am using the Schematron's basic XSL file basic-schematron.xsl to validate the XML format of one of our data files. The XSL file looks something like this
================
<xsl:stylesheet
version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:axsl="http://www.w3.org/1999/XSL/TransformAlias">
<xsl:import href="skeleton1-5.xsl"/>
<xsl:template name="process-prolog">
<axsl:output method="text" />
</xsl:template>
==================
But, the validation fails while trying to run the transformation on my Schematron input file using this basic-schematron.xsl with java.lang.NoSuchMethodError:
======= OUTPUT ============
Markup Error: no match attribute on <key> outside <rule>
Exception in thread "AWT-EventQueue-0" java.lang.NoSuchMethodError: GregorSamsa.process$dash$root(Lcom/sun/org/apache/xalan/internal/xsltc/DOM;Lcom/sun/org/apache/xml/internal/dtm/DTMAxisIterator;Lcom/sun/org/apache/xml/internal/serializer/SerializationHandler;ILjava/lang/Object;)V
     at GregorSamsa.applyTemplates()
     at GregorSamsa.applyTemplates()
     at GregorSamsa.transform()
     at com.sun.org.apache.xalan.internal.xsltc.runtime.AbstractTranslet.transform(AbstractTranslet.java:594)
     at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:640)
     at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:279)
     at com.solipsa.xsdvalidator.XSDValidator.validateSchematron(XSDValidator.java:137)
     at com.solipsa.xsdvalidator.XSDValidator.validate(XSDValidator.java:181)
     at com.solipsa.xsdvalidator.XSDValidatorUI.jButton1ActionPerformed(XSDValidatorUI.java:244)
     at com.solipsa.xsdvalidator.XSDValidatorUI.access$300(XSDValidatorUI.java:21)
     at com.solipsa.xsdvalidator.XSDValidatorUI$4.actionPerformed(XSDValidatorUI.java:140)
     at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849)
     at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169)
     at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
     at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
     at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:234)
     at java.awt.Component.processMouseEvent(Component.java:5488)
     at javax.swing.JComponent.processMouseEvent(JComponent.java:3093)
     at java.awt.Component.processEvent(Component.java:5253)
     at java.awt.Container.processEvent(Container.java:1966)
     at java.awt.Component.dispatchEventImpl(Component.java:3955)
     at java.awt.Container.dispatchEventImpl(Container.java:2024)
     at java.awt.Component.dispatchEvent(Component.java:3803)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
     at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
     at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
     at java.awt.Container.dispatchEventImpl(Container.java:2010)
     at java.awt.Window.dispatchEventImpl(Window.java:1766)
     at java.awt.Component.dispatchEvent(Component.java:3803)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:234)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
============= OUTPUT ==============
I tried the individual JAXP 1.3 for J2SDK 1.4.2 (Using the -Djava.endorsed.dirs JVM param) and tried the JDK 1.5.0_02 which has JAXP 1.3 inbuilt and they all fail.
I tried the above with separate Xalan/Xerces jar files, and then it works fine.
The problem seems to be somthing specific to the JAXP 1.3 environment. I can provide more details, if required. Any help is highly appreciated.

One morning your code woke up and found it had been transformed into a giant insect.
But seriously, here's the name of the method that doesn't exist:GregorSamsa.process$dash$rootIs GregorSamsa your class? Maybe your server has an old version of it which is missing that method? (Or: those $ signs look strange to me, maybe they are a mistranslation of some other character?)

Diff between XSL - JAVA and XSL - ABAP

Hi All,
What is the difference between the XSLT in JAVA and XSL in ABAP? which is the preferable one.

for
<b>XSL in ABAP</b>
refer these links
/people/sap.user72/blog/2003/09/18/xsl-and-abap
http://help.sap.com/saphelp_nw04/helpdata/en/09/b7463c32a3fe13e10000000a114084/frameset.htm
/people/achim.bangert/blog/2005/07/17/code-generation-using-xsl-transformations
/people/tobias.trapp/blog/2006/10/06/xml-processing-in-abap-part-9-150-abap-processing-using-xslt
/people/udo.martens/blog/2006/08/23/comparing-performance-of-mapping-programs
for <b>XSL in JAVA</b>
http://help.sap.com/saphelp_nw04/helpdata/en/4c/b2ad3de2d76b3be10000000a114084/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/05a3d62e-0a01-0010-14bc-adc8efd4ee14
http://help.sap.com/saphelp_nw04/helpdata/en/ce/1d753cab14a909e10000000a11405a/frameset.htm
XSLT Mapping:
http://help.sap.com/saphelp_nw04/helpdata/en/73/f61eea1741453eb8f794e150067930/content.htm
Java Mapping:
http://help.sap.com/saphelp_nw04/helpdata/en/e2/e13fcd80fe47768df001a558ed10b6/content.htm
Links of blogs on java mapping...
/people/prasad.ulagappan2/blog/2005/06/29/java-mapping-part-i
/people/prasad.ulagappan2/blog/2005/06/29/java-mapping-part-ii
/people/prasad.ulagappan2/blog/2005/06/29/java-mapping-part-iii
Have a look at this blog on XSLT mapping in ccbpm:
/people/sap.user72/blog/2005/03/15/using-xslt-mapping-in-a-ccbpm-scenario
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping(file to xslt mapping)
/people/pooja.pandey/blog/2005/06/27/xslt-mapping-with-java-enhancement-for-beginners(xslt with java enhancement function)
XSLT Mapping:
http://help.sap.com/saphelp_nw04/helpdata/en/73/f61eea1741453eb8f794e150067930/content.htm
and article on XSLT Mapping
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi%20code%20samples/generic%20xslt%20mapping%20and%20sample%20code.pdf
Java Mapping:
http://help.sap.com/saphelp_nw04/helpdata/en/e2/e13fcd80fe47768df001a558ed10b6/content.htm
Message Mapping:
http://help.sap.com/saphelp_nw04/helpdata/en/ee/bf9640dc522f28e10000000a1550b0/content.htm
this thread could give u a better understanding....
https://www.sdn.sap.com/sdn/collaboration.sdn?contenttype=url&content=https%3A//forums.sdn.sap.com/thread.jspa%3FthreadID%3D40283%26tstart%3D25
/people/ravikumar.allampallam/blog/2005/02/10/different-types-of-mapping-in-xi(types of mappping in xi)
/people/sap.user72/blog/2005/03/15/using-xslt-mapping-in-a-ccbpm-scenario(XSLT mapping in bpm)
refer this thread
Difference in using java,xslt,message mapping
XSLT-transformation in Java-Mapping with javax.xml
Thanks !!!!

Help-XML report which uses XSL-FO and XSL-FO contains OAF VO

Hello All,
I want to know functionality of one XML report developed by Oracle.
From one oracle form after clicking one button, it is populating PDF file output of report to open.
Here is what Oracle has done to achieve this:
On the click of button on oracle form, it is calling one OAF form. (fnd_function.execute(function_name=> 'ONT_PRINT').
This OAF form contains nothing on its layout. One CO (File is attached) and AM is attached to this OAF page.
In CO, may be it is somehow it is calling RTF file.
I got the RTF file from XML publisher, RTF imports one XSL-FO (ONTBSAEXSL is a Template of XSL-FO type in Oracle apps in XMP Publisher administrator responsibility) file using <?import:xdo://ONT.ONTBSAEXSL.en.00/?>
In the XSL file, OAF View Objects has been used like,
<xsl:variable name="LinesVO" select="/*/HeaderVO/HeaderVORow/LinesVO/LinesVORow"/>
What is the meaning of " /*/HeaderVO/HeaderVORow/LinesVO "? Does it mean LinesVO is getting called by HeadersVO. But in OAF this never happens.
I want to add some columns in the RTF from LinesVO. But "Unit price" is not available in LinesVO.
Do I need to extend this VO in JDeveloper and upload the .JPX and extended VO files?
I have done extending the VO, but no use..
So,
In short my question is,
If I extend the VO LinesVO by XXLinesVO, then will this <xsl:variable name="LinesVO" select="/*/HeaderVO/HeaderVORow/LinesVO/LinesVORow"/>
statement in XSL-FO use my XXLinesVO or LinesVO?
Regards,
Parag

I want to customize one RTF template by adding some columns. This RTF imports one XSL-FO stylesheet.
RTF has tags like <?for-each:/*/HeaderVO/HeaderVORow/LinesVO/LinesVORow?>
and XSL file has tags like <xsl:variable name="InternalOrgName" select="/*/HeaderVO/HeaderVORow/InternalOrgVO/InternalOrgVORow/Name"/>
If I want to add one colun in LinesVO, what are all things I need to do?
I customized it by adding the new columns through JDeveloper and extending the VO's and substituting them, importing JPX and bounced apache.
But the XSL-FO file is very strange (attached herewith). Those changes are not reflecting in report even after extension.

xsl:include in XSL Workshop

I am trying to use <xsl:include> for some proxy stylesheet. I use the form
<xsl:include href="filename.xsl" />
I get the following error when process the stylesheet:
'Bad URI found while including/importing file: no protocol: filename.xsl'
Currently I am just working with the workshops, I have not deployed the xsl stilesheets yet to the server.
Everything works as expected in XMLSpy.
Does anybody have an example of a working <xsl:include>?

what about putting that file in the respository? or set up the XMLDIR and put it there? I have never done it but just a though.
Ben

XSL-FO PO_STANDARD_PO.xsl probem

Similar Messages

Maybe you are looking for