Use of document function in XSL

We have an existing XSL document which uses a separate XML document for mapping of enumerated values. So in the XSL document, we have a line in our XSL as follows:
<xsl:variable name="enum-doc" select="document('enumerations.xml')"/>
Followed by a load of:
<xsl:key name="a-name" match="//enum[@name ='a-name']/enumeration" use="@value"/> etc.
We would like to use the existing XSL in BPEL. Is this possible? We have been able to deploy the mapping XML file with our BPEL process, but the XML mapping file is not beinig picked up by our XSL, so in our output we have a lot of missing enumerated values.
Any suggestions?
Thanks,
ma7asw

We managed to resolve the problem (We were using the wrong namespace in the XML mapping file).
So to confirm, it is possible to use the document function in an XSL transform within a BPEL process.
ma7asw

Similar Messages

Using document function in xsl template - not working in BI Publisher

Hi,
I have a requirement where I need to display the data in one xml file based on the contents of a second xml. I am using Oracle BI Publisher 10.1.3.4.1 and template used for report generation is xsl-fo.
1) ReportData.xml - contains the data xml
2) ReportFilter.xml - contains the display information.
I need to display the tags in the ReportData.xml based on the presence , absence of different tags in ReportFiler.xml
I guess one of the option is to declare 2 datasource as use concatenated datasources. However , I am trying to use the "Document" function that is available in xsl transformation to reference the display xml.
I have tried the different options for using the document function
*1) <xsl:variable name="filterCheck" select="document('ReportFilter.xml')"/>*
Errors out saying : XML-22021: (Error) Error parsing external document: 'Access not allowed : file:/
C:/OracleBI/oc4j_bi/bin/ReportFilter.xml '.
*2) <xsl:variable name="filterCheck" select="document('file:///C:/OracleBI/xmlp/XMLP/DemoFiles/ReportFilter.xml')" />*
Errors out saying ; Caused by: oracle.xdo.parser.v2.XPathException: Access not allowed : file:/C:/Or
acleBI/xmlp/XMLP/DemoFiles/ReportFilter.xml
*3) <xsl:variable name="filterCheck" select="document('C:/OracleBI/xmlp/XMLP/DemoFiles/ReportFilter.xml')" />*
Errors out saying : Caused by: java.net.MalformedURLException: unknown protocol: c
at oracle.xdo.parser.v2.XSLStylesheet.flushErrors(XSLStylesheet.java:153
*4)<xsl:variable name="filterCheck" select="document('file:/C:/OracleBI/xmlp/XMLP/DemoFiles/ReportFilter.xml')" />*
Errors out syaying : Caused by: oracle.xdo.parser.v2.XPathException: Access not allowed : file:/C:/Or
acleBI/xmlp/XMLP/DemoFiles/ReportFilter.xml
I have placed the document I need to access in all the 3 locations mentioned above
ie in my
*1) C folder*
*2) C:/OracleBI/oc4j_bi/bin*
*3) C:/OracleBI/xmlp/XMLP/DemoFiles*
Is there any special permissions that I need to grant to enable access to these files?
Please let me know if anyone has successfully made the document function to reference other xml documents in BI Publisher.
Regards
Sujith
Edited by: user10979469 on Dec 8, 2009 11:48 AM

Tim,
Thanks a lot for the reply. Set the option to enable external document access and it works perfectly.
Just for other who are looking at this post.
Go to the Report in BI Publisher
Click on Configure link on the top right
Go to the Section FO Processing
Disable external references - Server value is "True" . Set it to "False".
Apply changes.
Restarted the oc4j, just to be on safer side (not sure if this is required)
The document function will open documents from any location on your machine.
Thanks again Tim
Regards
Sujith

Using document() function in xsl - first iteration is OK; second iteration is Empty.

I am processing an input xml file (say input.xml) via (report.xsl) to generate
a report.
report.xsl in turn loads another *xml file (schema.xml) through document() function
so as to process the input.xml. <schema.xml> contains some look-up information
dictating how <input.xml> need to be processed.
Here is how I am referencing the "schema.xml" in the "report.xsl".
<xsl:variable name="schemaFile" select="document('schema.xml')"/>
<xsl:variable name="schemaRoot" select="$schemaFile/Schema"/>
<xsl:variable name="schemaList" select="$schemaRoot/SchemaFactors"/>
When I run the report first time (my appserver is weblogic 7.0), everything is
working fine. I see the results I wanted.
However, when I run the report for the second time during the same session, I
am getting "schemaList" as empty.
The values of "schemaFIle" and "schemaRoot" appear to be correctly loaded in both
the cases. The problem is with "schemaList" variable which is coming out empty
during the second iteration.
can any of you please throw some pointers on why this is happening and how to
resolve this?

Hello,
Sounds like a bug. If you have a small test case, could you provide
that to our outstanding support group (http://support.bea.com or
[email protected]), it would certainly help tracking this down.
Thanks,
Bruce
venkata wrote:
>
I am processing an input xml file (say input.xml) via (report.xsl) to generate
a report.
report.xsl in turn loads another *xml file (schema.xml) through document() function
so as to process the input.xml. <schema.xml> contains some look-up information
dictating how <input.xml> need to be processed.
Here is how I am referencing the "schema.xml" in the "report.xsl".
<xsl:variable name="schemaFile" select="document('schema.xml')"/>
<xsl:variable name="schemaRoot" select="$schemaFile/Schema"/>
<xsl:variable name="schemaList" select="$schemaRoot/SchemaFactors"/>
When I run the report first time (my appserver is weblogic 7.0), everything is
working fine. I see the results I wanted.
However, when I run the report for the second time during the same session, I
am getting "schemaList" as empty.
The values of "schemaFIle" and "schemaRoot" appear to be correctly loaded in both
the cases. The problem is with "schemaList" variable which is coming out empty
during the second iteration.
can any of you please throw some pointers on why this is happening and how to
resolve this?

Looking for example - abap xslt - that uses xslt document() function

Hello,
I'm looking for an example that shows the use of abap xslt with the xslt document() function. Using the xslt document() function seems like a straightforward way to use xslt to create a result xml document by processing the content of two or more
source documents. For example, if source document A.xml and aux.xml are available in memory as xstringand using stylesheet ztransformwhat would be the argument for the document() function to associate aux.xml. Thanks for any insight.
Regards,
jb10809

Hi,
Sorry, perhaps I should have been clearer! The function that I picked just to test what you need to do just happened to return a string that contains SPAN tags with style attributes. The actual function code is:
create or replace FUNCTION out_string_fn
   RETURN VARCHAR2
IS
   CURSOR emp_cur
   IS
      SELECT ename
        FROM emp;
   v_string   VARCHAR2 (4000);
BEGIN
   v_string := ' ';
   FOR c IN emp_cur
   LOOP
      v_string :=
            v_string
         || '<SPAN style="font-weight:bold;color:green">'
         || c.ename
         || '</SPAN>'
         || ', </br></br>';
   END LOOP;
   RETURN v_string;
END;And this returned a naff list in green (see [http://apex.oracle.com/pls/otn/f?p=55041:57] and click the Test button) - but it does show that you can style the validation error messages
Andy

Error using custom xpath function with XSL transformations in BPM

Hi,
We have created a custom xpath function for use with SOA Suite and BPM. This has been built as per specified within the http://docs.oracle.com/cd/E29597_01/dev.1111/e10224/bp_appx_functs.htm#SOASE11100. We have also reviewed the Oracle Sample for mapper-107-ExtensionFunctions (sample demonstrates the use of user-defined extension functions). This has been registered with jDeveloper and SOA within the oracle.soa.ext_11.1.1 (run ant to include in oracle.soa.ext.jar)
We ideally want to use this is BPM within an xsl. However when consuming this function is either BPEL or BPM using an xsl, the xsl fails with an error such as:
XPath expression failed to execute. An error occurs while processing the XPath expression; the expression is ora:doXSLTransformForDoc("xsl/Transformation_1.xsl", $inputVariable.payload). The XPath expression failed to execute; the reason was: javax.xml.transform.TransformerException: oramds:/deployed-composites/default/gwCustomXpathUtil_rev1.0/xsl/Transformation_1.xsl<Line 9, Column 113>: XML-22043: (Error) Extension function error: Method not found 'getWeekDayDate'. Check the detailed root cause described in the exception message text and verify that the XPath query is correct.
In an Assign it operates fine and returns the expected result. We have included a combination of both of the Config files (ext-mapper-xpath-functions-config.xml and ext-soa-xpath-functions-config.xml) in the META-INF folder, however neither allow the use of this function in the XSL.
I believe there may be an issue getting the custom xpath functions within XSL files. Hence I have also raised an SR. Has anyone experiences of this?
Our SOA / BPM suite environment is using 11.1.1.6.4 and has the following patches applied:
13801175
14406487 (11.1.1.6.4 SOA Bundle)
13896993
13088538
Regards Dave
Edited by: DavidGaskell on Mar 14, 2013 10:08 PM

Hi All,
I am also facing the same issue...Experts can you please help us.
hi DavidGaskell, did you find any resolution, if so can you share it with me.....
Thanks,
RR

Code sample for using change document function modules

Can someone send me some sample code for using function modules CHANGEDOCUMENT_READ_HEADER and CHANGEDOCUMENT_READ_POSITIONS? I'm specifically looking for changes that occured to the standard price field in the material master (MBEW-STPRS) and I need to pull the most recent price change for a given material. I'm not sure how to write the code efficiently since I don't have a date to pass (again, since we're looking for the most recent change.)
Thanks!

hi check this..
CHANGEDOCUMENT_READ_HEADERS
Example:
CALL FUNCTION 'CHANGEDOCUMENT_READ_HEADERS'
EXPORTING
objectclass = 'EINKBELEG'
objectid = l_objectid
username = space
TABLES
i_cdhdr = lt_cdhdr.
LOOP AT lt_cdhdr WHERE udate IN s_aedat.
CALL FUNCTION 'CHANGEDOCUMENT_READ_POSITIONS'
EXPORTING
changenumber = lt_cdhdr-changenr
TABLES
editpos = lt_editpos.
LOOP AT lt_editpos WHERE fname = 'LOEKZ'
AND f_new = 'L'.
p_desc = text-r01. " Cancel Contract
ENDLOOP.
ENDLOOP.
CHANGEDOCUMENT_READ_POSITIONS
Example:
CALL FUNCTION 'CHANGEDOCUMENT_READ_HEADERS'
EXPORTING
objectclass = 'EINKBELEG'
objectid = l_objectid
username = space
TABLES
i_cdhdr = lt_cdhdr.
LOOP AT lt_cdhdr WHERE udate IN s_aedat.
CALL FUNCTION 'CHANGEDOCUMENT_READ_POSITIONS'
EXPORTING
changenumber = lt_cdhdr-changenr
TABLES
editpos = lt_editpos.
LOOP AT lt_editpos WHERE fname = 'LOEKZ'
AND f_new = 'L'.
p_desc = text-r01. " Cancel Contract
ENDLOOP.
ENDLOOP.
Check this link.
http://www.sap-img.com/mm001.htm
<REMOVED BY MODERATOR>
venkat.
Edited by: Alvaro Tejada Galindo on Mar 18, 2008 4:05 PM

How to use xsl document() function with LiveCycle XSLT processor

Hello,
I would like to use LiveCycle XSLT processor to merge xml documents by using the xsl document() function.
However, I have not, yet, found clear reference information on the specifics of how to accomplish in LC. For instance if you have
a transformation that does merging using a standalone xml editor (such as Oxygen), than what is required to accomplish the same
using the LiveCycle XSLT service. How do you specify the URI of the XML document that is specified as an input in the xsl document() function. Your insight is appreciated. Regards

Hello Steve,
I checked the reference that you cited (XSLT Transformation). The reference omits discussing how to use xlst document() function within a stylesheet. I think that probably means that feature of xslt technology is not directly available through LiveCycle. When I find a workaround, I'll post an update...for the user community that might encounter the same issue. Thank you for your response and insight. Regards, jb1809

Use document() function in xslt

Hi I want to use the xslt function document() to import a data file into the transformation.
However I don't seem to be able to import the xml file onto the osb. can this be done ?
Basically can you use the document() function?
I've tried googling and searching the docs but i think i'm missing something basic :-)
Thanks in advance

Not an answer to the particular point but i've got round the issue by adding a stage which inserts the data xml into the xml document being transformed.
I then supress the data injected from being copied to the output tree and use a variable which references the data nodes rather than a variable referencing
an external doc variable name="myvar" select="//injecteddatanode" /> rather than <variable name="myvar" select="document("path/doc.xml")
The question still stands though : how do you import an xml doc which can then be used by the document function in a transform

Use of Document Area/Document Space in KPro

Hi,
I hope this is the correct forum for my question. If not, suggestions are welcome.
We are using KPro to store documents for quality notifications.
While configuring content repositories (Tx OAC0) and content categories (Tx OACT) I found the field "Document Area" (sometimes referred to as "Document Space"). The documentation on that topic is not very helpful. Could anyone tell me, what's the use of a document area/space? Examples would be very helpful.
Thanks,
Marcus.

We managed to resolve the problem (We were using the wrong namespace in the XML mapping file).
So to confirm, it is possible to use the document function in an XSL transform within a BPEL process.
ma7asw

Using xsl document function in transform xsl

I'm trying to use an external xml document in an xsl transform that's used in a Transform activity in an 11g BPEL process:
<xsl:variable name="plants" select="document('plantTransposeLookup.xml')/plants"/>
I need to load up the document to use it in a lookup to get replacement values for a key.
This works fine in JDev, but not when I deploy it to the server.
The error I get when I run it is:
The XPath expression failed to execute; the reason was: javax.xml.transform.TransformerException: XML-22021: (Error) Error parsing external document: 'no protocol: plantTransposeLookup.xml'.. Check the detailed root cause described in the exception message text and verify that the XPath query is correct.
I've also gotten:
The XPath expression failed to execute; the reason was: javax.xml.transform.TransformerException: XML-22021: (Error) Error parsing external document: 'Unsupported feature: 'document(''), when stylesheet built using InputStream, Reader'.
I've also tried using the ora:doc function:
<xsl:variable name="plants" select="ora:doc('plantTransposeLookup.xml', 'plants')"/>
......but this doesn't work in JDev and is also erroring off on the server with:
The XPath expression failed to execute; the reason was: javax.xml.transform.TransformerException: XML-22016: (Error) Extension function namespace should start with 'http://www.oracle.com/XSL/Transform/java/'.. Check the detailed root cause described in the exception message text and verify that the XPath query is correct.
Does anyone know how to actually import an xml doc into a mapper??? I must be doing something stupid.
Thanks for any help.

In OSB, document() function needs absolute path of the XML file. So if you want to access the XML document for lookup, you need to put the XML file on the server itself and use the path of the XML file.
Although this is not a correct approach for managing lookups in OSB. The resource of XML Document type are not to be used for such use cases. What you can do is create a XQuery which can server as DVM.
Here is an example on how to use DVMs in OSB:
https://blogs.oracle.com/christomkins/entry/domain_value_maps_in_oracle_se
If you dont want to use XQuery and want to rely only on XSLT, then within the same XSLT document create a separate template which can store all the lookup data.

Use DOM as an argument of XSLT document() function

I have in memory several DOM documents. I have not stored in file system the XML files that are represented by these DOMs. I want to process with a stylesheet
all of these DOMs (as DOMSource's) using document() function from the stylesheet. How can I refer to the secondary DOMs from document function if I haven't the files?
F.e.
<xsl:value-of select="document('file.xml')/.../..."/> file.xml only exists loaded in memory as DOM.
Can anybody help me?? Thanks

Thank you DrClap but I'm not sure about the use of URIResolver:
if my xslt:
<xsl:value-of select="document('file1.xml')\...\..."/>
<xsl:value-of select="document('file2.xml')\...\..."/>
I must define my own class that implements URIResolver and write my own resolve method, isn't it?
class Resuelve implements URIResolver{
     private Document doc1;
     private Document doc2;
     public Resuelve(Document doc1, Document doc2){
          this.doc1 = doc1;
          this.doc2 = doc2;
     public Source resolve(String href, String base){
          if(base.equalsIgnoreCase("file1.xml")){
               Source s1 = new DOMSource(doc1);
               return s1;
          else if(base.equalsIgnoreCase("file2.xml")){
               Source s2 = new DOMSource(doc2);
               return s2;
          else{
               return null;
I suppose that XSLT processor use automatically resolve method. I don't understand the href parameter...
Is this class correct? if not, can you show me an example please?
Thank you very much

How can I use JavaScript extention functions with Xalan for transforming XML with XSL

While transforming standart XML and XSL files to HTML with this servlet:
package mypackage1;
import javax.servlet.*;
import javax.servlet.http.*;
import java.io.*;
import java.util.*;
import java.net.URL;
import javax.xml.transform.*;
import javax.xml.transform.stream.StreamSource;
import javax.xml.transform.stream.StreamResult;
import org.mozilla.javascript;
public class Servlet2 extends HttpServlet
private static final String CONTENT_TYPE = "text/html; charset=windows-1252";
public void init(ServletConfig config) throws ServletException
super.init(config);
public void doGet(HttpServletRequest request, HttpServletResponse response)throws ServletException, IOException
try
response.setContentType(CONTENT_TYPE);
PrintWriter out = response.getWriter();
TransformerFactory tFactory = TransformerFactory.newInstance();
Source xmlSource = new StreamSource(new FileReader("c:/aaa.xml"));
Source xslSource = new StreamSource(new FileReader("c:/bbb.xsl"));
Transformer transformer = tFactory.newTransformer(xslSource);
transformer.transform (xmlSource, new StreamResult(out));
catch (Exception e)
e.printStackTrace();
everything is going ok,
but when try to use javascript function in XSL file, for example like in this:
<?xml version="1.0"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"
xmlns:lxslt="http://xml.apache.org/xslt" xmlns:my-ext="ext1"
extension-element-prefixes="my-ext">
<lxslt:component prefix="my-ext"
functions="getdate">
<lxslt:script lang="javascript">
function getdate() {
var d = new Date();
return d.toUTCString();
</lxslt:script>
</lxslt:component>
<xsl:template match="/">
<p><xsl:copy-of select="my-ext:getdate()"/></p>
</xsl:template>
</xsl:stylesheet>
recieve error-message:
XSL-1000: (Fatal Error) Error while parsing XSL file (Extension function namespace should start with 'http://www.oracle.com/XSL/Transform/java/'.).
What kind of namespace I should specify?

Hello, Paul.
I'm sure you may not use JavaScript as a language for creating XSLT extention functions with Oracle XDK Parser. This is since parser might have JavaScript interpreter to work with JavaScript, but it has not.
If you need to build any XSLT extention functions you must build them as Java class' static methods.
After that, you define the usage of the class by mean of namespace declaration as:
xmlns:your-ns="http://www.oracle.com/XSL/Transform/java/yourpackage.Yourclass"
(Prefix "http://www.oracle.com/XSL/Transform/java/" may differs if you use non-Oracle XML parser)
and use class' static method in XSLT:
<xsl:value-of select="your-ns.staticMethodName(paramsIfAny)"/>
In your case you may wish to use standard Date class:
xmlns:date="http://www.oracle.com/XSL/Transform/java/java.util.Date"
<xsl:value-of select="date:toString(date:new)"/>

How can I get INSTID_B for the documents which are stored using Store Business Document functionality

Dear experts,
I had activated the functionality of Store Business document and successfully stored documents in external server.
My client have a custom function module which is used to send emails.In that FM they used SO_DOCUMENT_READ_API1, SO_DOCUMENT_SEND_API1 function modules.They passed Instance Ident(SRGBTBREL->INSTID_B)(eg: FOL33000000000004EXT39000000000026) as export parameter to the FM 'SO_DOCUMENT_READ_API1' and get the attachment details and content.
Here my problem is I do not have entries in the table SRGBTBREL for the documents which are stored using the Store Business Document functionality and without INSTID_B I am unable to use the FM 'SO_DOCUMENT_READ_API1' to get the document details and content. Please help me to find INSTID_B for documents which are stored using Store Business Document functionality or please let me know if there is any other way to use FM 'SO_DOCUMENT_READ_API1' for documents which are stored using Store Business Document.
Thanks in advance.
Regards,
Kiran

Hi Kiran,
You can use the following method to get the information. For example if you want to get BO documents for a customer
CALL METHOD cl_binary_relation=>read_links
   EXPORTING
     is_object           = ls_lpor
     it_relation_options = lt_relat
   IMPORTING
     et_links            = lt_links.
then fill ls_por-instid with a customer number (KUNNR), ls_por-typeid = 'KNA1' and ls_por-catid = 'BO'.
Table lt_relat should contain a line option for each document type (for example 'I' 'EQ' 'NOTE', 'I' EQ 'ATTA', 'I' EQ 'URL', ...
In table lt_links you will get your information.
Maybe some other methods of class CL_BINARY_RELATION may also solve your issue.
Regards,
Klaus

XSLT mapping error using document function

Hello,
We migrated from XI 3.0 to PI 7.1. XSL is made use of for mapping. We are encountering this error of 'File not found' when we use the document funcion to look into an xml file. The xml file along with the xsl map is zipped and uploaded. I am not sure of why this is happening in PI 7.1. What is the cause. Looking forward to your early replies with solutions.
Kind Regards,
InduShekar

Check the file contents and see whether the content is same as that of the older version. You can export the same file from xi and pi and see both are same and having same contents. Check the file is imported in the right namespace.

External document using XQuery doc() function - SEGV

The following code involving an XQuery using the doc() function to access an external document via the filesystem produces a segmentation fault on Windows XP 32 using Java 1.6.11 and BDB XML 2.4.16 + P1.
The input doc is just "<Urmel>Huhuhu</Urmel>".
Maybe some basic error of mine. How am I supposed to access external documents via XQuery's doc() function?
Michael Ludwig
# Problematic frame:
# C [libdbxml24d.dll+0x86401]
# The crash happened outside the Java Virtual Machine in native code.
package milu;
import java.io.File;
import com.sleepycat.db.Environment;
import com.sleepycat.db.EnvironmentConfig;
import com.sleepycat.dbxml.XmlException;
import com.sleepycat.dbxml.XmlManager;
import com.sleepycat.dbxml.XmlManagerConfig;
import com.sleepycat.dbxml.XmlQueryContext;
import com.sleepycat.dbxml.XmlResults;
import com.sleepycat.dbxml.XmlTransaction;
import com.sleepycat.dbxml.XmlValue;
public class TestExternalAccess2 {
     static final String envDirStr = "C:/MILU/data/dbenv46";
     static final File envDir = new File(envDirStr);
     static EnvironmentConfig envConf;
     static {
          envConf = new EnvironmentConfig();
          envConf.setAllowCreate(true);
          envConf.setRunRecovery(true);
          envConf.setInitializeCache(true);
          envConf.setInitializeLocking(true);
          envConf.setInitializeLogging(true);
          envConf.setTransactional(true);
     public static void main(String[] args) throws Exception {
          Environment env = new Environment(envDir, envConf);
          XmlManagerConfig mgrConf = new XmlManagerConfig();
          mgrConf.setAllowExternalAccess(true);
          XmlManager mgr = new XmlManager(env, mgrConf);
          String qry = "doc('file:C:/milu/dev/u.xml')";
          XmlQueryContext qc = mgr.createQueryContext();
          XmlTransaction txn = mgr.createTransaction();
          XmlResults res = mgr.query(txn, qry, qc);
          while (res.hasNext()) {
               XmlValue val = res.next();
               StringBuffer sb = new StringBuffer();
               sb.append(val.getClass());
               sb.append(" - ");
               sb.append(val.asString());
               System.out.println(sb.toString());
          res.delete();
          txn.commit();
}

I did a diff of my dbxml-2.4.16 and a clean version of dbxml-2.4.16 and found this difference, which looks like a fix for your bug. Please tell me if this works.
Lauren Foutz
--- dbxml-2.4.16-orig/dbxml/src/java/dbxml_java_wrap.cpp     2008-10-21 18:28:16.000000000 -0400
+++ dbxml-2.4.16/dbxml/src/java/dbxml_java_wrap.cpp     2009-02-27 15:24:32.000000000 -0500
@@ -1309,8 +1309,12 @@
                   break;
              default:
-                   if(docid != 0)
-                        (*cdoc).setAsNotMaterialized();
+                   if(docid != 0 && cid != 0)
+                         (*cdoc).setAsNotMaterialized();
+                    else if(!(*cdoc).getDbMinder().isNull() && cid == 0) { //set query constructed documents as DOM
+                         (*cdoc).getDocDb();
+                         (*cdoc).setContentAsNsDom(docid, (*cdoc).getCacheDatabase());
+                    }
              createCPPMetaData(jenv, jdoc, cdoc);Edited by: LaurenFoutz on Apr 16, 2009 6:48 AM

Use of document function in XSL

Similar Messages

Maybe you are looking for