XPath Expressions
Hi,
I am trying to select a particular node in a loaded DOM tree based on XPATH expressions. Rightnow We are using Xerces parser.
Can anyone throw some light on this? i.e. Standard way of implementing this?
Thanks in anticipation.
With Regards
K.RajeshKannan.
Xpath expression is similiar like SQL queries.I don't think you could standardize the way ( if your queries is simple ).Another thing is Xerces does not support XPath.Try Xalan instead.
Similar Messages
-
XPath expression failed to execute.
Hi Everybody ,
I am working AIA PIP 3.1 for JDE E1.I am facing some errors so that i can't proceed.
See the log errors as below:
javax.xml.ws.soap.SOAPFaultException: XPath expression failed to execute. An error occurs while processing the XPath expression; the expression is ora:processXSLT('xsl/Xform_BillOfMaterialsListABM_to_BillOfMaterialsListAXML.xsl',bpws:getVariableData('InitialLoadBillOfMaterialsListReqMsg','InitialLoadBillOfMaterialsList'),bpws:getVariableData('Parameters')). The XPath expression failed to execute; the reason was: oracle.fabric.common.xml.xpath.XPathFunctionException: javax.xml.transform.TransformerException: oramds:/deployed-composites/default/InitialLoadBillOfMaterialsListJDEE1toAgileImpl_rev1.0/xsl/Xform_BillOfMaterialsListABM_to_BillOfMaterialsListAXML.xsl<Line 18, Column 271>: XML-22044: (Error) Extension function error: Error invoking 'lookupXRef':'oracle.tip.xref.exception.RepositoryException: lookup could not find values in column name "AGILE_01" for table name "oramds:/apps/AIAMetaData/xref/ITEM_ITEMID.xref" using reference column name "JDEE1_01" and reference value "731882::M30" Please ensure lookup criteria has a match.'. Check the detailed root cause described in the exception message text and verify that the XPath query is correct.
Please reply me ASAP,
Waiting for your response.....
Regards
Jyoti NayakHi,
Ya i checked the data for same table,but i didn't get any XREF related information in xref_data table.
Did you mean that, data should already present under AIAFPINST_XREF.Probably xref is meant for storing dynamic value.
Please check the above error and reply me soon.
With Regards
Jyoti Nayak -
Using the variable placeholder ? in an XPath expression
I'm trying to using the variable operator (?) in an Oracle prepared statement used in a query where clause. Here is the query:
select xt.APPLICATION_NAME, xt.VERSION, xt.EVENT_TYPE, xt.SENDING_SITE, xt.RECEIVING_SITE, xt.EVENT_ID
from AUDITED_EVENT_XML_MIN e,
XMLTable(XMLNAMESPACES('http://gov/va/med/datasharing/audit/endpoint/audit' AS "xae"),
'/xae:auditable-event'
PASSING e.xml_event_content
COLUMNS
APPLICATION_NAME VARCHAR2(255) PATH 'xae:application-name',
VERSION VARCHAR2(255) PATH 'xae:version',
EVENT_TYPE VARCHAR2(255) PATH 'xae:event-type',
SENDING_SITE VARCHAR2(255) PATH 'xae:xml-event-content/*/MSH/MSH.4/HD.2',
RECEIVING_SITE VARCHAR2(255) PATH 'xae:xml-event-content/*/MSH/MSH.6/HD.2',
EVENT_ID VARCHAR2(255) PATH 'xae:xml-event-content/*/MSH/MSH.10') xt
where existsNode(E.XML_EVENT_CONTENT, '/xae:auditable-event[xae:event-type=?]','xmlns:xae="http://gov/va/med/datasharing/audit/endpoint/audit"') = 1This code works when the ? is replaced with "aValue". I need to use the ? so that my Java client can pass a variable value into the query.
Is this a supportable feature or am I doing something wrong?
I didn't see any examples in the Oracle XML DB Developers Guide where there was a ? in an XPath expression.
I also tried "?" with the same issue...
Here is the version info:
SQL*Plus: Release 11.1.0.6.0 - Production on Mon Sep 10 18:41:55 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing optionsAny assistance would be greatly appreciated.
Thanks in advance...
Edited by: flyeagle5683 on Sep 10, 2012 5:49 PMselect xt.APPLICATION_NAME, xt.VERSION, xt.EVENT_TYPE, xt.SENDING_SITE, xt.RECEIVING_SITE, xt.EVENT_ID
from AUDITED_EVENT_XML_MIN e,
XMLTable(XMLNAMESPACES('http://gov/va/med/datasharing/audit/endpoint/audit' AS "xae"),
'/xae:auditable-event'
PASSING e.xml_event_content
COLUMNS
APPLICATION_NAME VARCHAR2(255) PATH 'xae:application-name',
VERSION VARCHAR2(255) PATH 'xae:version',
EVENT_TYPE VARCHAR2(255) PATH 'xae:event-type',
SENDING_SITE VARCHAR2(255) PATH 'xae:xml-event-content/*/MSH/MSH.4/HD.2',
RECEIVING_SITE VARCHAR2(255) PATH 'xae:xml-event-content/*/MSH/MSH.6/HD.2',
EVENT_ID VARCHAR2(255) PATH 'xae:xml-event-content/*/MSH/MSH.10') xt
where XMLEXISTS(
'declarre namespace xae ="http://gov/va/med/datasharing/audit/endpoint/audit"; (: :)
$XML/xae:auditable-event[xae:event-type=$VALUE]'
passing e.xml_event_content as "XML",
:1 as "VALUE"
) or you can do
select xt.APPLICATION_NAME, xt.VERSION, xt.EVENT_TYPE, xt.SENDING_SITE, xt.RECEIVING_SITE, xt.EVENT_ID
from AUDITED_EVENT_XML_MIN e,
XMLTable(XMLNAMESPACES('http://gov/va/med/datasharing/audit/endpoint/audit' AS "xae"),
'/xae:auditable-event'
PASSING e.xml_event_content
COLUMNS
APPLICATION_NAME VARCHAR2(255) PATH 'xae:application-name',
VERSION VARCHAR2(255) PATH 'xae:version',
EVENT_TYPE VARCHAR2(255) PATH 'xae:event-type',
SENDING_SITE VARCHAR2(255) PATH 'xae:xml-event-content/*/MSH/MSH.4/HD.2',
RECEIVING_SITE VARCHAR2(255) PATH 'xae:xml-event-content/*/MSH/MSH.6/HD.2',
EVENT_ID VARCHAR2(255) PATH 'xae:xml-event-content/*/MSH/MSH.10') xt
WHERE EVENT_TYPE = :1Edited by: mdrake on Sep 10, 2012 7:23 PM
Edited by: mdrake on Sep 10, 2012 7:24 PM -
Using the variable ? operator in an XPath Expression
I'm trying to using the variable operator (?) in an Oracle prepared statement used in a query where clause. Here is the query:
select xt.APPLICATION_NAME, xt.VERSION, xt.EVENT_TYPE, xt.SENDING_SITE, xt.RECEIVING_SITE, xt.EVENT_ID
from AUDITED_EVENT_XML_MIN e,
XMLTable(XMLNAMESPACES('http://gov/va/med/datasharing/audit/endpoint/audit' AS "xae"),
'/xae:auditable-event'
PASSING e.xml_event_content
COLUMNS
APPLICATION_NAME VARCHAR2(255) PATH 'xae:application-name',
VERSION VARCHAR2(255) PATH 'xae:version',
EVENT_TYPE VARCHAR2(255) PATH 'xae:event-type',
SENDING_SITE VARCHAR2(255) PATH 'xae:xml-event-content/*/MSH/MSH.4/HD.2',
RECEIVING_SITE VARCHAR2(255) PATH 'xae:xml-event-content/*/MSH/MSH.6/HD.2',
EVENT_ID VARCHAR2(255) PATH 'xae:xml-event-content/*/MSH/MSH.10') xt
where existsNode(E.XML_EVENT_CONTENT, '/xae:auditable-event[xae:event-type=?]','xmlns:xae="http://gov/va/med/datasharing/audit/endpoint/audit"') = 1This code works when the ? is replaced with "aValue". I need to use the ? so that my Java client can pass a variable value into the query.
Is this a supportable feature or am I doing something wrong?
I didn't see any examples in the Oracle XML DB Developers Guide where there was a ? in an XPath expression.
I also tried "?" with the same issue...
Here is the version info:
SQL*Plus: Release 11.1.0.6.0 - Production on Mon Sep 10 18:41:55 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing optionsAny assistance would be greatly appreciated.
Thanks in advance...I incorporated this suggestion and it worked very well. Thanks!
Now I have converted my solution to use a structured index. As such, I want to write the where clauses in terms of column names rather than XPath expressions.
I hoped it was as simple as changing the code that generates the XPath expression to generate a SQL expression. After making that change, I'm now getting this error:
Caused by: java.sql.SQLSyntaxErrorException: ORA-00920: invalid relational operator
at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:91)
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:112)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:173)
at oracle.jdbc.driver.T2CConnection.checkError(T2CConnection.java:686)
at oracle.jdbc.driver.T2CConnection.checkError(T2CConnection.java:617)
at oracle.jdbc.driver.T2CPreparedStatement.executeForDescribe(T2CPreparedStatement.java:559)
at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1077)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1186)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3381)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3425)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1490)
at gov.va.med.datasharing.audit.dao.jdbc.runner.MapQueryRunner.run(MapQueryRunner.java:47)
at gov.va.med.datasharing.audit.web.dao.jdbc.AuditableEventsQueryDAOImpl.getAuditableEventsByDate(AuditableEventsQueryDAOImpl.java:150)It seemed to me that if it worked for the XPath expression that it should also work for the SQL expression.
The static SQL is:
SELECT PK_ID, EVENT_TYPE, OUTCOME, SENDING_SITE, RECEIVING_SITE, CREATED_TIME, EVENT_ID, PATIENT_ID FROM
(SELECT rownum as rn, PK_ID, EVENT_TYPE, OUTCOME, SENDING_SITE, RECEIVING_SITE, CREATED_TIME, EVENT_ID, PATIENT_ID FROM
(SELECT aet.AUDITABLE_EVENT_XML_PK_ID AS PK_ID, xt.EVENT_TYPE, xt.OUTCOME, xt.SENDING_SITE, xt.RECEIVING_SITE, aet.CREATED_TIME as CREATED_TIME, xt.EVENT_ID, xt.PATIENT_ID
FROM AUDITABLE_EVENT_XML aet,
XMLTable(XMLNAMESPACES('http://gov/va/med/datasharing/audit/endpoint/audit' AS "xae"),
'/xae:auditable-event'
PASSING aet.xml_event_content
COLUMNS
EVENT_TYPE VARCHAR2(255) PATH 'xae:event-type',
SENDING_SITE VARCHAR2(255) PATH 'xae:sending-site',
RECEIVING_SITE VARCHAR2(255) PATH 'xae:receiving-site',
EVENT_ID VARCHAR2(255) PATH 'xae:event-id',
PATIENT_ID VARCHAR2(255) PATH 'xae:patient-id',
OUTCOME VARCHAR2(255) PATH 'xae:outcome') xt
WHERE aet.CREATED_TIME BETWEEN ? AND ?
AND ?
) ORDER BY CREATED_TIME desc
) WHERE rn > ? and rn <= ?So I'm thinking that Oracle must perform strong checking in SQL, not allowing the '=' operator to be substituted. If I run this query in Toad, replacing the ? with the SQL, it runs fine...
Can someone tell me whether or not this is a legal substitution?
The SQL that runs in Toad is:
SELECT PK_ID, EVENT_TYPE, OUTCOME, SENDING_SITE, RECEIVING_SITE, CREATED_TIME, EVENT_ID, PATIENT_ID FROM
(SELECT rownum as rn, PK_ID, EVENT_TYPE, OUTCOME, SENDING_SITE, RECEIVING_SITE, CREATED_TIME, EVENT_ID, PATIENT_ID FROM
(SELECT aet.AUDITABLE_EVENT_XML_PK_ID AS PK_ID, xt.EVENT_TYPE, xt.OUTCOME, xt.SENDING_SITE, xt.RECEIVING_SITE, aet.CREATED_TIME as CREATED_TIME, xt.EVENT_ID, xt.PATIENT_ID
FROM AUDITABLE_EVENT_XML aet,
XMLTable(XMLNAMESPACES('http://gov/va/med/datasharing/audit/endpoint/audit' AS "xae"),
'/xae:auditable-event'
PASSING aet.xml_event_content
COLUMNS
EVENT_TYPE VARCHAR2(255) PATH 'xae:event-type',
SENDING_SITE VARCHAR2(255) PATH 'xae:sending-site',
RECEIVING_SITE VARCHAR2(255) PATH 'xae:receiving-site',
EVENT_ID VARCHAR2(255) PATH 'xae:event-id',
PATIENT_ID VARCHAR2(255) PATH 'xae:patient-id',
OUTCOME VARCHAR2(255) PATH 'xae:outcome') xt
WHERE aet.CREATED_TIME BETWEEN TO_DATE ('9/19/2011 12:00:01 AM','MM/DD/YYYY HH:MI:SS PM')
AND TO_DATE ('12/20/2012 12:00:00 AM','MM/DD/YYYY HH:MI:SS PM')
AND (OUTCOME=0 or OUTCOME=1)
) ORDER BY CREATED_TIME desc
) WHERE rn > 0 and rn <= 5;Any assistance will be appreciated,
Thanks in advance. -
Using xpath expressions in Document-Builder
Hi all
we have re-designed our (existing) DDX-templates with the Document Builder in LC Workbench. The DDX templates are used to assemble PDFs with LC Assembler-Service.
Now my question: Is it still possible to use XPath-expression in the DDX template? Please find our example below:
The XPath expression works only if we copy&paste the DDX source code directly to the Assembler-Service property view (picture below). But referring the DDX-template doens't interpret the xpath path at run time (2nd picture below). Any help on that will be appreciated!
Works (using DDX source code directly):
Doesn't work (using DDX template):Hi,
>
I tried to get a portion of an XML by using XPath Expressions as follows:
String xPathExpression =
"declare namespace xq='http://inti.notariado.org/indices' " +
"$this/xq:RULES/xq:RULE[@disabled]";
I think any XPath expressions which use [] are not supported in stand alone
version, but as this is not documented I could be wrong.
Regards
Arek -
[Error ORABPEL-10039]: invalid xpath expression - array processing
hi,
I am trying to process multiple xml elements
<assign name="setinsideattributes">
<copy>
<from expression="ora:getElement('Receive_1_Read_InputVariable','BILL','/ns2:BILL/ns2:CMS1500['bpws:getVariableData('iterator')']/ns2:HEADER/ns2:SSN')"/>
<to variable="ssn"/>
</copy>
</assign>
where iterator is a index variable .
I am getting into this error .
Error(48):
[Error ORABPEL-10039]: invalid xpath expression
[Description]: in line 48 of "D:\OraBPELPM_1\integration\jdev\jdev\mywork\may10-workspace\multixm-catch\multixm-catch.bpel", xpath expression "ora:getElement('Receive_1_Read_InputVariable','BILL','/ns2:BILL/ns2:CMS1500['bpws:getVariableData('iterator')']/ns2:HEADER/ns2:SSN')" specified in <from> is not valid, because XPath query syntax error.
Syntax error while parsing xpath expression "ora:getElement('Receive_1_Read_InputVariable','BILL','/ns2:BILL/ns2:CMS1500['bpws:getVariableData('iterator')']/ns2:HEADER/ns2:SSN')", at position "77" the exception is Expected: ).
Please verify the xpath query "ora:getElement('Receive_1_Read_InputVariable','BILL','/ns2:BILL/ns2:CMS1500['bpws:getVariableData('iterator')']/ns2:HEADER/ns2:SSN')" which is defined in BPEL process.
[Potential fix]: Please make sure the expression is valid.
any information on how to fix this .
thanks in advancecheck out this note here
http://clemensblog.blogspot.com/2006/03/bpel-looping-over-arrays-collections.html
hth clemens -
Hey Guys...
Currently I am working on one Xpath expression issue..as described below;
Its a File to Idoc scenario ...where in I need to check the two Item level nodes and based on that need to produce the target Idoc. and my souce structure look like this....
DT_Input
Header --- 1 to 1
H1
H2
H3
Item -
0 - Unbounded
Item_1
Item_2
Item_3
Query : If the Item_1 and Item_3 are not equal AND Item_1 not equal to blank ...then I need to produce the target Idoc otherwise not!
Can you please help me out!!!
Cheers.,
SYou could create an advance user defined function.
fed your function with the 3 values (Item_1 and Item3).
Inside the function, check the values of Item_1 and Item_3 nodes.
What is the result of your query? I mean, if your query is meet, Which value do you want to populate in your IDOC?
You should use this sentence: result.addValue(a[0]). It is supposed a is the value returned by the funcion.
If you don`t want create the node in the IDOC, use this other one: result.addValue(ResultListCC).
Regards,
Carlos -
XPATH-expressions and namespaces
I have a xml-file for testing my xpath expression, like this:
<a>
<b>
<c>aaa</c>
<d>
<e>111</e>
</d>
</b>
<b>
<c>bbb</c>
<d>
<e>222</e>
</d>
</b>
<b>
<c>ccc</c>
<d>
<e>333</e>
</d>
</b>What I want is to get the value of element 'e', based on a check on what the value of element 'c' is. I alway know the value of element 'c'.
I solve this by using this xpath-expression in my xsl-file:
<xsl:variable name="xpathTest" select="//e[../preceding-sibling::c = 'bbb']" />This expression should return '222', and it works!!!
But, when I use the another xml-file with a similar structure, with namespaces, like this:
<body xsi:type="fkpsoap:FKPSOAPOperationResponse">
<FKPSOAPOperationResponse>
<fkpsoap_1:fkrdk178_output_data>
<fkpsoap_1:fkrdk178_list_cust_information>
<fkpsoap_1:fkrdk178_list_customerinfo>
<fkpsoap_1:fkrdk178_list_variable_code> aaa </fkpsoap_1:fkrdk178_list_variable_code>
<fkpsoap_1:fkrdk178_list_value_name>
<fkpsoap_1:fkrdk178_list_value_text> 111 </fkpsoap_1:fkrdk178_list_value_text>
</fkpsoap_1:fkrdk178_list_customerinfo>
<fkpsoap_1:fkrdk178_list_customerinfo>
<fkpsoap_1:fkrdk178_list_variable_code> bbb </fkpsoap_1:fkrdk178_list_variable_code>
<fkpsoap_1:fkrdk178_list_value_name>
<fkpsoap_1:fkrdk178_list_value_text> 222 </fkpsoap_1:fkrdk178_list_value_text>
</fkpsoap_1:fkrdk178_list_customerinfo>
<fkpsoap_1:fkrdk178_list_customerinfo>
<fkpsoap_1:fkrdk178_list_variable_code> ccc </fkpsoap_1:fkrdk178_list_variable_code>
<fkpsoap_1:fkrdk178_list_value_name>
<fkpsoap_1:fkrdk178_list_value_text> 333 </fkpsoap_1:fkrdk178_list_value_text>
</fkpsoap_1:fkrdk178_list_customerinfo>
</fkpsoap_1:fkrdk178_list_cust_information>
</fkpsoap_1:fkrdk178_output_data>
</FKPSOAPOperationResponse>
</body>Then the xpath-expression does not work!
I can easily extract the value of the element similar to the element 'e' in my test-file, but then I will always get the value from the first occurance of 'e', which is '111'.
Can anyone help me with this?Most APIs which let you create XPath objects allow you to create a namespace context and attach it to the XPath object. Your API most likely does too, whatever it is. Then you would just use the prefixes which the namespace context describes in your XPath expression.
(This namespace context generally maps prefixes to namespace URIs. Remember that the namespace URI is really what the XPath is looking for and the prefix is just a short cut for you to use.) -
Help Page Error: Using XPath expressions as list indexes and map keys
The help page says for maps to use the XPath expression
/process_data/mapvar[@id='/process_data/@stringvar']
But in reality for things to work you have to omit the quotations.thanks a lot for your help..
there are total 162 records in the v$open_cursor for that user.
among that the open cursor is only 4 and open-recursive cursor is only 6 for that user.
in my session i am executing only the renaming of the constraints and nothing more.
When i have queried the v$open_cursor for cursor_type='OPEN' for all the users, then i got that it has exceeded the value of open_cursors parameter.
So how can i resolve that.... -
XPath Expression in document definition
I am trying to use "XPath Expression1" for 894 in the document definition under XPath in order to retrieve invoice number so that, it would be used in BAM but I am not getting successful in putting exact XPath expression for invoice number. I am using as below
/Transaction-894/Segment-G82/Element-861
Pls suggest is there any wrong in the XPath?
Regards,
Suneel JakkaHere is the XSD for which I am trying XPath for the "Element-861" under "Segment-G82"..
Pls suggest me..
<?xml version="1.0" encoding="UTF-8"?>
<!-- Automatically generated by EDIFECS SpecBuilder (http://www.edifecs.com) -->
<xsd:schema xmlns="http://www.edifecs.com/xdata/200" targetNamespace="http://www.edifecs.com/xdata/200" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="1.0" elementFormDefault="qualified">
<xsd:annotation>
<xsd:appinfo>
<FileName>C:\Documents and Settings\jakkasun\Desktop\11g\X12_5010_894.ecs</FileName>
<InternalID>{0840BE5F-3518-463D-A128-D73D96D4A5D2}</InternalID>
</xsd:appinfo>
</xsd:annotation>
<xsd:element name="Transaction-894" type="Transaction-894"/>
<xsd:complexType name="Transaction-894">
<xsd:annotation>
<xsd:documentation>This X12 Transaction Set contains the format and establishes the data contents of the Delivery/Return Base Record Transaction Set (894) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to enable a Direct Store Delivery (DSD) vendor to communicate the details of a DSD delivery and is to be used during the check-in procedure. </xsd:documentation>
<xsd:appinfo>
<UNMKey>Full|CodeList|-<Parent Node ID>.<Index>|Composite|-<Node ID>|Element|-<Node ID>|Loop|-<Node ID>|Segment|-<Node ID>|Transaction|-<Node ID>|ReplacementCharacter|_|InternalSeparator|-</UNMKey>
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="Internal-Properties" type="Internal-Properties" minOccurs="0"/>
<xsd:element name="Segment-ST" type="Segment-ST"/>
<xsd:element name="Segment-G82" type="Segment-G82"/>
<xsd:element name="Segment-N9" type="Segment-N9" minOccurs="0" maxOccurs="unbounded" nillable="true"/>
<xsd:element name="Loop-LS" type="Loop-LS" minOccurs="0" nillable="true"/>
<xsd:element name="Segment-G72" type="Segment-G72" minOccurs="0" maxOccurs="20" nillable="true"/>
<xsd:element name="Segment-G23" type="Segment-G23" minOccurs="0" maxOccurs="20" nillable="true"/>
<xsd:element name="Segment-G84" type="Segment-G84"/>
<xsd:element name="Segment-G86" type="Segment-G86"/>
<xsd:element name="Segment-G85" type="Segment-G85"/>
<xsd:element name="Segment-SE" type="Segment-SE"/>
</xsd:sequence>
<xsd:attribute name="Type" default="Transaction" type="xsd:string"/>
<xsd:attribute name="ID" default="894" type="xsd:string"/>
<xsd:attribute name="Name" default="Delivery/Return Base Record" type="xsd:string"/>
<xsd:attribute name="XDataVersion" fixed="2.0" type="xsd:string"/>
<xsd:attribute name="Standard" fixed="X12" use="required" type="xsd:string"/>
<xsd:attribute name="Version" default="V5010" type="xsd:string"/>
<xsd:attribute name="GUID" type="GUID"/>
<xsd:attribute name="CreatedBy" type="xsd:string"/>
<xsd:attribute name="CreatedDate" type="xsd:dateTime"/>
</xsd:complexType>
<xsd:simpleType name="GUID">
<xsd:restriction base="xsd:string">
<xsd:pattern value="\{[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12}\}"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="EDI-Element-String-Type">
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="Type" default="Element" type="xsd:string"/>
<xsd:attribute name="EDIDataType" type="xsd:string"/>
<xsd:attribute name="Macro" type="xsd:string" use="optional"/>
<xsd:attribute name="ApplicationInfo" type="xsd:string"/>
<xsd:attribute name="ID" type="xsd:string"/>
<xsd:attribute name="Name" type="xsd:string"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="EDI-Element-Integer-Type">
<xsd:simpleContent>
<xsd:extension base="xsd:integer">
<xsd:attribute name="Type" default="Element" type="xsd:string"/>
<xsd:attribute name="EDIDataType" type="xsd:string"/>
<xsd:attribute name="Macro" type="xsd:string" use="optional"/>
<xsd:attribute name="ApplicationInfo" type="xsd:string"/>
<xsd:attribute name="ID" type="xsd:string"/>
<xsd:attribute name="Name" type="xsd:string"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="EDI-Element-Decimal-Type">
<xsd:simpleContent>
<xsd:extension base="xsd:decimal">
<xsd:attribute name="Type" default="Element" type="xsd:string"/>
<xsd:attribute name="EDIDataType" type="xsd:string"/>
<xsd:attribute name="Macro" type="xsd:string" use="optional"/>
<xsd:attribute name="ApplicationInfo" type="xsd:string"/>
<xsd:attribute name="ID" type="xsd:string"/>
<xsd:attribute name="Name" type="xsd:string"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="EDI-Element-hexBinary-Type">
<xsd:simpleContent>
<xsd:extension base="xsd:hexBinary">
<xsd:attribute name="Type" default="Element" type="xsd:string"/>
<xsd:attribute name="EDIDataType" type="xsd:string"/>
<xsd:attribute name="Macro" type="xsd:string" use="optional"/>
<xsd:attribute name="ApplicationInfo" type="xsd:string"/>
<xsd:attribute name="ID" type="xsd:string"/>
<xsd:attribute name="Name" type="xsd:string"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="EDI-Element-base64Binary-Type">
<xsd:simpleContent>
<xsd:extension base="xsd:base64Binary">
<xsd:attribute name="Type" default="Element" type="xsd:string"/>
<xsd:attribute name="EDIDataType" type="xsd:string"/>
<xsd:attribute name="Macro" type="xsd:string" use="optional"/>
<xsd:attribute name="ApplicationInfo" type="xsd:string"/>
<xsd:attribute name="ID" type="xsd:string"/>
<xsd:attribute name="Name" type="xsd:string"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="EDI-Element-Any-Type">
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="Type" default="Element" type="xsd:string"/>
<xsd:attribute name="EDIDataType" type="xsd:string"/>
<xsd:attribute name="Macro" type="xsd:string" use="optional"/>
<xsd:attribute name="ApplicationInfo" type="xsd:string"/>
<xsd:attribute name="ID" type="xsd:string"/>
<xsd:attribute name="Name" type="xsd:string"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="Internal-Properties">
<xsd:sequence>
<xsd:element name="Data-Structure" type="Data-Structure" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="Data-Structure">
<xsd:sequence>
<xsd:element name="Lookup" type="Lookup" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="Property" type="Property" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="Data-Structure" type="Data-Structure" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="Name" type="xsd:string"/>
<xsd:attribute name="GUID" type="GUID"/>
</xsd:complexType>
<xsd:complexType name="Lookup">
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="Name" type="xsd:string"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="Property">
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="Name" type="xsd:string"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="Segment-ST">
<xsd:annotation>
<xsd:documentation>To indicate the start of a transaction set and to assign a control number</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="Element-143" type="Element-143"/>
<xsd:element name="Element-329" type="Element-329"/>
<xsd:element name="Element-1705" type="Element-1705" minOccurs="0" nillable="true"/>
</xsd:sequence>
<xsd:attribute name="Type" default="Segment" type="xsd:string"/>
<xsd:attribute name="ID" default="ST" type="xsd:string"/>
<xsd:attribute name="Name" default="Transaction Set Header" type="xsd:string"/>
</xsd:complexType>
<xsd:complexType name="Element-143">
<xsd:annotation>
<xsd:documentation>Code uniquely identifying a Transaction Set </xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:restriction base="EDI-Element-String-Type">
<xsd:enumeration value="100"/>
<xsd:enumeration value="101"/>
<xsd:enumeration value="102"/>
<xsd:enumeration value="103"/>
<xsd:enumeration value="104"/>
<xsd:enumeration value="105"/>
<xsd:enumeration value="106"/>
<xsd:enumeration value="107"/>
<xsd:enumeration value="108"/>
<xsd:enumeration value="109"/>
<xsd:enumeration value="110"/>
<xsd:enumeration value="111"/>
<xsd:enumeration value="112"/>
<xsd:enumeration value="113"/>
<xsd:enumeration value="120"/>
<xsd:enumeration value="121"/>
<xsd:enumeration value="124"/>
<xsd:enumeration value="125"/>
<xsd:enumeration value="126"/>
<xsd:enumeration value="127"/>
<xsd:enumeration value="128"/>
<xsd:enumeration value="129"/>
<xsd:enumeration value="130"/>
<xsd:enumeration value="131"/>
<xsd:enumeration value="132"/>
<xsd:enumeration value="133"/>
<xsd:enumeration value="135"/>
<xsd:enumeration value="138"/>
<xsd:enumeration value="139"/>
<xsd:enumeration value="140"/>
<xsd:enumeration value="141"/>
<xsd:enumeration value="142"/>
<xsd:enumeration value="143"/>
<xsd:enumeration value="144"/>
<xsd:enumeration value="146"/>
<xsd:enumeration value="147"/>
<xsd:enumeration value="148"/>
<xsd:enumeration value="149"/>
<xsd:enumeration value="150"/>
<xsd:enumeration value="151"/>
<xsd:enumeration value="152"/>
<xsd:enumeration value="153"/>
<xsd:enumeration value="154"/>
<xsd:enumeration value="155"/>
<xsd:enumeration value="157"/>
<xsd:enumeration value="158"/>
<xsd:enumeration value="159"/>
<xsd:enumeration value="160"/>
<xsd:enumeration value="161"/>
<xsd:enumeration value="163"/>
<xsd:enumeration value="170"/>
<xsd:enumeration value="175"/>
<xsd:enumeration value="176"/>
<xsd:enumeration value="179"/>
<xsd:enumeration value="180"/>
<xsd:enumeration value="185"/>
<xsd:enumeration value="186"/>
<xsd:enumeration value="187"/>
<xsd:enumeration value="188"/>
<xsd:enumeration value="189"/>
<xsd:enumeration value="190"/>
<xsd:enumeration value="191"/>
<xsd:enumeration value="194"/>
<xsd:enumeration value="195"/>
<xsd:enumeration value="196"/>
<xsd:enumeration value="197"/>
<xsd:enumeration value="198"/>
<xsd:enumeration value="199"/>
<xsd:enumeration value="200"/>
<xsd:enumeration value="201"/>
<xsd:enumeration value="202"/>
<xsd:enumeration value="203"/>
<xsd:enumeration value="204"/>
<xsd:enumeration value="205"/>
<xsd:enumeration value="206"/>
<xsd:enumeration value="210"/>
<xsd:enumeration value="211"/>
<xsd:enumeration value="212"/>
<xsd:enumeration value="213"/>
<xsd:enumeration value="214"/>
<xsd:enumeration value="215"/>
<xsd:enumeration value="216"/>
<xsd:enumeration value="217"/>
<xsd:enumeration value="219"/>
<xsd:enumeration value="220"/>
<xsd:enumeration value="222"/>
<xsd:enumeration value="223"/>
<xsd:enumeration value="224"/>
<xsd:enumeration value="225"/>
<xsd:enumeration value="227"/>
<xsd:enumeration value="228"/>
<xsd:enumeration value="240"/>
<xsd:enumeration value="242"/>
<xsd:enumeration value="244"/>
<xsd:enumeration value="245"/>
<xsd:enumeration value="248"/>
<xsd:enumeration value="249"/>
<xsd:enumeration value="250"/>
<xsd:enumeration value="251"/>
<xsd:enumeration value="252"/>
<xsd:enumeration value="255"/>
<xsd:enumeration value="256"/>
<xsd:enumeration value="259"/>
<xsd:enumeration value="260"/>
<xsd:enumeration value="261"/>
<xsd:enumeration value="262"/>
<xsd:enumeration value="263"/>
<xsd:enumeration value="264"/>
<xsd:enumeration value="265"/>
<xsd:enumeration value="266"/>
<xsd:enumeration value="267"/>
<xsd:enumeration value="268"/>
<xsd:enumeration value="269"/>
<xsd:enumeration value="270"/>
<xsd:enumeration value="271"/>
<xsd:enumeration value="272"/>
<xsd:enumeration value="273"/>
<xsd:enumeration value="274"/>
<xsd:enumeration value="275"/>
<xsd:enumeration value="276"/>
<xsd:enumeration value="277"/>
<xsd:enumeration value="278"/>
<xsd:enumeration value="280"/>
<xsd:enumeration value="283"/>
<xsd:enumeration value="284"/>
<xsd:enumeration value="285"/>
<xsd:enumeration value="286"/>
<xsd:enumeration value="288"/>
<xsd:enumeration value="290"/>
<xsd:enumeration value="300"/>
<xsd:enumeration value="301"/>
<xsd:enumeration value="303"/>
<xsd:enumeration value="304"/>
<xsd:enumeration value="309"/>
<xsd:enumeration value="310"/>
<xsd:enumeration value="311"/>
<xsd:enumeration value="312"/>
<xsd:enumeration value="313"/>
<xsd:enumeration value="315"/>
<xsd:enumeration value="317"/>
<xsd:enumeration value="319"/>
<xsd:enumeration value="322"/>
<xsd:enumeration value="323"/>
<xsd:enumeration value="324"/>
<xsd:enumeration value="325"/>
<xsd:enumeration value="326"/>
<xsd:enumeration value="350"/>
<xsd:enumeration value="352"/>
<xsd:enumeration value="353"/>
<xsd:enumeration value="354"/>
<xsd:enumeration value="355"/>
<xsd:enumeration value="356"/>
<xsd:enumeration value="357"/>
<xsd:enumeration value="358"/>
<xsd:enumeration value="361"/>
<xsd:enumeration value="362"/>
<xsd:enumeration value="404"/>
<xsd:enumeration value="410"/>
<xsd:enumeration value="412"/>
<xsd:enumeration value="414"/>
<xsd:enumeration value="417"/>
<xsd:enumeration value="418"/>
<xsd:enumeration value="419"/>
<xsd:enumeration value="420"/>
<xsd:enumeration value="421"/>
<xsd:enumeration value="422"/>
<xsd:enumeration value="423"/>
<xsd:enumeration value="424"/>
<xsd:enumeration value="425"/>
<xsd:enumeration value="426"/>
<xsd:enumeration value="429"/>
<xsd:enumeration value="431"/>
<xsd:enumeration value="432"/>
<xsd:enumeration value="433"/>
<xsd:enumeration value="434"/>
<xsd:enumeration value="435"/>
<xsd:enumeration value="436"/>
<xsd:enumeration value="437"/>
<xsd:enumeration value="440"/>
<xsd:enumeration value="451"/>
<xsd:enumeration value="452"/>
<xsd:enumeration value="453"/>
<xsd:enumeration value="455"/>
<xsd:enumeration value="456"/>
<xsd:enumeration value="460"/>
<xsd:enumeration value="463"/>
<xsd:enumeration value="466"/>
<xsd:enumeration value="468"/>
<xsd:enumeration value="470"/>
<xsd:enumeration value="475"/>
<xsd:enumeration value="485"/>
<xsd:enumeration value="486"/>
<xsd:enumeration value="490"/>
<xsd:enumeration value="492"/>
<xsd:enumeration value="494"/>
<xsd:enumeration value="500"/>
<xsd:enumeration value="501"/>
<xsd:enumeration value="503"/>
<xsd:enumeration value="504"/>
<xsd:enumeration value="511"/>
<xsd:enumeration value="517"/>
<xsd:enumeration value="521"/>
<xsd:enumeration value="527"/>
<xsd:enumeration value="536"/>
<xsd:enumeration value="540"/>
<xsd:enumeration value="561"/>
<xsd:enumeration value="567"/>
<xsd:enumeration value="568"/>
<xsd:enumeration value="601"/>
<xsd:enumeration value="602"/>
<xsd:enumeration value="620"/>
<xsd:enumeration value="625"/>
<xsd:enumeration value="650"/>
<xsd:enumeration value="715"/>
<xsd:enumeration value="753"/>
<xsd:enumeration value="754"/>
<xsd:enumeration value="805"/>
<xsd:enumeration value="806"/>
<xsd:enumeration value="810"/>
<xsd:enumeration value="811"/>
<xsd:enumeration value="812"/>
<xsd:enumeration value="813"/>
<xsd:enumeration value="814"/>
<xsd:enumeration value="815"/>
<xsd:enumeration value="816"/>
<xsd:enumeration value="818"/>
<xsd:enumeration value="819"/>
<xsd:enumeration value="820"/>
<xsd:enumeration value="821"/>
<xsd:enumeration value="822"/>
<xsd:enumeration value="823"/>
<xsd:enumeration value="824"/>
<xsd:enumeration value="826"/>
<xsd:enumeration value="827"/>
<xsd:enumeration value="828"/>
<xsd:enumeration value="829"/>
<xsd:enumeration value="830"/>
<xsd:enumeration value="831"/>
<xsd:enumeration value="832"/>
<xsd:enumeration value="833"/>
<xsd:enumeration value="834"/>
<xsd:enumeration value="835"/>
<xsd:enumeration value="836"/>
<xsd:enumeration value="837"/>
<xsd:enumeration value="838"/>
<xsd:enumeration value="839"/>
<xsd:enumeration value="840"/>
<xsd:enumeration value="841"/>
<xsd:enumeration value="842"/>
<xsd:enumeration value="843"/>
<xsd:enumeration value="844"/>
<xsd:enumeration value="845"/>
<xsd:enumeration value="846"/>
<xsd:enumeration value="847"/>
<xsd:enumeration value="848"/>
<xsd:enumeration value="849"/>
<xsd:enumeration value="850"/>
<xsd:enumeration value="851"/>
<xsd:enumeration value="852"/>
<xsd:enumeration value="853"/>
<xsd:enumeration value="854"/>
<xsd:enumeration value="855"/>
<xsd:enumeration value="856"/>
<xsd:enumeration value="857"/>
<xsd:enumeration value="858"/>
<xsd:enumeration value="859"/>
<xsd:enumeration value="860"/>
<xsd:enumeration value="861"/>
<xsd:enumeration value="862"/>
<xsd:enumeration value="863"/>
<xsd:enumeration value="864"/>
<xsd:enumeration value="865"/>
<xsd:enumeration value="866"/>
<xsd:enumeration value="867"/>
<xsd:enumeration value="868"/>
<xsd:enumeration value="869"/>
<xsd:enumeration value="870"/>
<xsd:enumeration value="871"/>
<xsd:enumeration value="872"/>
<xsd:enumeration value="873"/>
<xsd:enumeration value="874"/>
<xsd:enumeration value="875"/>
<xsd:enumeration value="876"/>
<xsd:enumeration value="877"/>
<xsd:enumeration value="878"/>
<xsd:enumeration value="879"/>
<xsd:enumeration value="880"/>
<xsd:enumeration value="881"/>
<xsd:enumeration value="882"/>
<xsd:enumeration value="883"/>
<xsd:enumeration value="884"/>
<xsd:enumeration value="885"/>
<xsd:enumeration value="886"/>
<xsd:enumeration value="887"/>
<xsd:enumeration value="888"/>
<xsd:enumeration value="889"/>
<xsd:enumeration value="891"/>
<xsd:enumeration value="893"/>
<xsd:enumeration value="894"/>
<xsd:enumeration value="895"/>
<xsd:enumeration value="896"/>
<xsd:enumeration value="920"/>
<xsd:enumeration value="924"/>
<xsd:enumeration value="925"/>
<xsd:enumeration value="926"/>
<xsd:enumeration value="928"/>
<xsd:enumeration value="940"/>
<xsd:enumeration value="943"/>
<xsd:enumeration value="944"/>
<xsd:enumeration value="945"/>
<xsd:enumeration value="947"/>
<xsd:enumeration value="980"/>
<xsd:enumeration value="990"/>
<xsd:enumeration value="993"/>
<xsd:enumeration value="996"/>
<xsd:enumeration value="997"/>
<xsd:enumeration value="998"/>
<xsd:enumeration value="999"/>
<xsd:attribute name="EDIDataType" fixed="ID" type="xsd:string"/>
<xsd:attribute name="ID" fixed="143" type="xsd:string"/>
<xsd:attribute name="Name" fixed="Transaction Set Identifier Code" type="xsd:string"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="Element-329">
<xsd:annotation>
<xsd:documentation>Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set </xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:restriction base="EDI-Element-String-Type">
<xsd:minLength value="4"/>
<xsd:maxLength value="9"/>
<xsd:attribute name="EDIDataType" fixed="AN" type="xsd:string"/>
<xsd:attribute name="ID" fixed="329" type="xsd:string"/>
<xsd:attribute name="Name" fixed="Transaction Set Control Number" type="xsd:string"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="Element-1705">
<xsd:annotation>
<xsd:documentation>Reference assigned to identify Implementation Convention </xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:restriction base="EDI-Element-String-Type">
<xsd:minLength value="1"/>
<xsd:maxLength value="35"/>
<xsd:attribute name="EDIDataType" fixed="AN" type="xsd:string"/>
<xsd:attribute name="ID" fixed="1705" type="xsd:string"/>
<xsd:attribute name="Name" fixed="Implementation Convention Reference" type="xsd:string"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="Segment-G82">
<xsd:annotation>
<xsd:documentation>To transmit identifying numbers, dates, and other basic data relating to the transaction set</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="Element-478" type="Element-478"/>
<xsd:element name="Element-861" type="Element-861"/>
<xsd:element name="Element-860" type="Element-860"/>
Regards,
Suneel Jakka -
Using xpath-expressions inside Task Instructions
Hi all,
I have a process where I would like to build up the task Instructions in a string variable. However I cannot seem to resolve xpath values when I am putting my string as the task instruction.
How can I do this?
Thanks in advance
Sincerely
Kim ChristensenHi again Marcel - thanks for your quick reply
However I am not sure I und erstand your answer correctly.
I have a string variable (str_Inctructions) that I want to set as my Task Instruction.
So at a point in my process I create a set value with an expression like this:
str_Instructions = 'Here are some instructions for {$/process_data/myOtherVar$} please follow them.'
I then set str_Instructions as the Task Instructions (an xpath-expression). When I get the Task in Workspace I see the {$/process_data/myOthervariable$} instead of the value of myOtherVar.
So how can I get the value of myOtherVar? -
XPath expressions in XmlCursor / XmlObjects
Hi all,
I tried to get a portion of an XML by using XPath Expressions as follows:
String xPathExpression =
"declare namespace xq='http://inti.notariado.org/indices' " +
"$this/xq:RULES/xq:RULE[@disabled]";
A simple example of an xml
<rules>
<rule disabled="true">hello</rule>
<rule>hello</rule>
</rules>
It should return one node, but actually it returns nothing. If I use another one:
String xPathExpression =
"declare namespace xq='http://inti.notariado.org/indices' " +
"$this/xq:RULES/xq:RULE";
Then I get two nodes (which is correct). It seems to me a bug or a partial support
for XPath expressions. Or maybe I am using a bad syntax, anyone can help?
Thanks in advance !Hi,
>
I tried to get a portion of an XML by using XPath Expressions as follows:
String xPathExpression =
"declare namespace xq='http://inti.notariado.org/indices' " +
"$this/xq:RULES/xq:RULE[@disabled]";
I think any XPath expressions which use [] are not supported in stand alone
version, but as this is not documented I could be wrong.
Regards
Arek -
I would like to be able to compare two xpath expressions and evaluate whether their result CAN have nodes in common.
For example:
expression 1: /ItemData[@ItemOID='A']
expression 2: /ItemData[@ItemOID='B']
would need to evaluate to 'false'
Other example:
expression 1: /ItemData[@ItemOID='A']
expression 2: /ItemData[@ItemOID='B or @ItemOID='A']
would need to evaluate to 'true'
Other example:
expression 1: /ItemData[@ItemOID='A']
expression 2: /ItemData[not(@ItemOID='B')]
would need to evaluate to 'true'
Other example:
expression 1: /ItemData[@ItemOID='A']
expression 2: /ItemData[not(@ItemOID='A'][not(@ItemOID='B']
would need to evaluate to 'false'
P.S. Sorry if the Xpath expressions do not show up 100% correctly in the above snippets - the editor is doing crazy ...
I would like to do such an evaluation without actually having an XML document (!).
Is this possible?
Did someone ever write a class for doing so ?
Many thanks
JozefXML4Pharma wrote:
Is this possible?As phrased probably. You would need to create a xpath parser then compare the parse trees for expression equivalency.
You might be able to find a xpath parser. The other part you would need to create yourself. -
Is there a Java API that parses XPath expressions and produces the resultant XPath tree in memory?
For example the xpath expression: /a/b[c/d]/e/f
will produce a tree with "a" as the root node, "b" as a sub-node, "c" and "e" as subnodes of "b" and so on.
I don't want one that is to be evaluate against and XML document. I just want the XPath Expression tree to be build in memory.
Thankshi,
look at javacc, a compiler very popular, with many examples.
Raymond -
Hello to all,
I'm trying to create a ABAP based mapping without xslt, as xslt-mapping is running in a timeout.
Is there a way to execute XPATH expressions on a document?
The method "get_elements_by_name" isn't helpfull, as I need to specify a certain path within the xml-document.
Thanks for your suggestions.
Best regards,
ChristianI dont think it will be possible untill you include XSLT mapping in to ABAP mapping as you would need a compiler for XPATH expressions.
Maybe you are looking for
-
I just got finished wiping my device because it had a previous owner. And I don't know how to set my yahoo account so I can get it on my phone. I have a curve 8310. Thanks for any help.:smileyhappy:
-
A report where we see internal order or cc together with suppliers
Hi All, Can you please tell me if there is a report where we see internal order or cc together with suppliers for each account in same report ? Regrads Rudra
-
Weblogic JndiDataSource problem
Hi, I am trying to use JndiDataSource in Weblogic 9.1 Express edition. Everything is configured, but when I am using jdbc datasource and if the connection pool exceeds the limit, i am getting error: <Notice> <WebLogicServer> <BEA-000388> <JVM called
-
Under View Sorting Options the Manual sort option is dimmed and not available; how do I fix?
Under the View tab, Sorting Options, the Manual Sort is dimmed and not available to me; how do I fix?
-
Cannot move ID objects to Quality Server using CTS
Dear Friends, We are using PI 7.1. We have created necessary HTTP & TCP/IP Destinations in PI QA server and then transported using CTS all SLD & ESR objects. Now we are struck up during moving ID objects from DEV PI to QA PI. Please give me your solu