Remove Namespace Prefix from SOAP response

Hi
I have a File-XI-SOAP scenario. I pass data from the file to SOAP. If the data is good, I receive a Response and If the data is bad I get an fault message called AccountUtilsException. But I am not able to read this message properly.
The message we receive from the webservice is
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?><!-- Request Message Mapping --> <edu.purdue.account.AccountUtils.AccountUtilsException xsi:type='ns1:AccountUtilsException' xmlns:ns1='urn://www.purdue.edu/apps/account/ns'><message xsi:type='soapenc:string' xmlns:soapenc='http://schemas.xmlsoap.org/soap/encoding/'>lastName is a required field</message><type xsi:type='xsd:int'>5</type></edu.purdue.account.AccountUtils.AccountUtilsException>
In sxmb_moni when we try to read this message I get the error Reference to undeclared namespace prefix: 'xsi'.
I tried removing the xsi prefix using anonymizer.acceptNamespaces = urn://www.purdue.edu/apps/account/ns ns1.
I tried this too urn://www.purdue.edu/apps/account/ns ''.
the AF_MODULES/AnonymizerBean is second in my processing sequence immediately following the XISOAPAdapterBean.
The problem still persists. Any suggestions? The webservice people are not willing to remove the xsi:
Thanks,
Jahnavi

The XMLAnonymizerBean does not consider namespace prefixes in attributes. So you should allow also those prefixes and namespaces which are used here.
Without the XMLAnonymizerBean the xsi namespace declaration should be available as well, if not it is a bug. Check if you have applied the latest patch and open an OSS ticket, if this is the case.
Regards
Stefan

Similar Messages

  • How to remove namespace prefix from target payload when using HTTP in PI7.0

    Hi,
    i have a requirement to remove namespace prefix from target payload when receiver receives the payload by an HTTP request.
    i am not able to use XML Anonymizer Bean as in HTTP channel its not possiile.
    Target structure after mapping now is:
    <?xml version="1.0" encoding="UTF-8"?>
    <ns3:Order xmlns:ns3="urn:xxx-com:pi:project">
    fields
    </ns3:Order>
    i need the target structure after mapping should look like:
    <?xml version="1.0" encoding="UTF-8"?>
    <Order xmlns:="urn:xxx-com:pi:project">
    fields
    <Order>
    i removed namespace from source and target Message Type of message mapping but still getting "ns3" prefix. My requirement is to just have this ns3 removed.
    Please reply if anyone has solved this problem before.
    Thanks

    Hi ,
    >>>i removed namespace from source and target Message Type of message mapping but still getting "ns3" prefix. My requirement is to just have this ns3 removed.
    Which process you've used for removing namespace...java/xslt mapping. In case of java mapping plese remove ns3 while creating the target element. Please go through the below blog it may help you.
    Quick Tips: Dealing with Namespaces in XI/PI
    Regards,
    Priyanka

  • Remove namespace prefix with the XMLAnonymizerBean is possible at SOAP Adap

    Hello,
    I am wondering is it possible Remove namespace prefix with the XMLAnonymizerBean at SOAP Receiver Adaptor?
    Thanks

    Hi Rajiv,
    Pl. go through this blog:
    /people/stefan.grube/blog/2007/02/02/remove-namespace-prefix-or-change-xml-encoding-with-the-xmlanonymizerbean
    Also if you want to use this at sender side, SOAP adapter will not support. Please check stefans reply in this thread:
    XMLAnonymizerBean doesnt work
    Regards,
    ---Satish

  • How to remove namespace prefix

    hi,
    i have a problem in receiver SOAP adapter because of namespace prefix.
    so i have to remove the namespace prefix from the paylaod. but namespace should be there...
    what are the possibilities to remove the namespace prefix alone from the payload?
    Thanks & Regards,
    Krish

    hi,
    you have to simply add one module in your communication channel
    that is XMLAnonymizerBean
    you can refer below for help:
    Remove namespace prefix or change XML encoding with the XMLAnonymizerBean
    http://help.sap.com/saphelp_nw04/helpdata/en/2e/bf37423cf7ab04e10000000a1550b0/frameset.htm
    hope it helps.
    regards,
    ujjwal kumar

  • NameSpace Prefix in SOAP Request

    How can I create SOAP Request without namespace prefix from a WSDL file.
    I am using ClientGen (WL 7.0, SP2)
    My Application doesn't accept namespace prefix.
    Thanks

    How can I create SOAP Request without namespace prefix from a WSDL file.
    I am using ClientGen (WL 7.0, SP2)
    My Application doesn't accept namespace prefix.
    Thanks

  • Oracle ESB 10g : Blank namespace in the SOAP Response from DB adapter

    Hi All,
    I am currently working on a ESB project to route input XML file as a parameter to a DB Function.
    This Function has a input parameter of type XMLTYPE and returns VARCHAR2 values.
    I have configured the DB Adapter to invoke this function and return the result as a SOAP response.
    The WSDL of DB adapter contains XML_DATA as input and XMLMAIN as the output result.
    The ESB project works fine as expected. But in the result from DB adapter contains a blank namespace [xmlns=""] for the XMLMAIN element .
    I hereby attach the output XML.
    Please help how to remove this blank namespace from the output.
    We are using SOA Suite 10g 10.1.3.5
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <env:Header/>
    <env:Body xmlns="http://xmlns.oracle.com/pcbpel/adapter/db/XXWEB/XMLMISCRCPTINSERTPKG/XMLMAIN/">
    <OutputParameters xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <XMLMAIN xmlns="">100</XMLMAIN>
    </OutputParameters>
    </env:Body>
    </env:Envelope>
    Thanks and Regards,
    Justin Michael Raj

    well..the problem is..the db adapter has it's own transaction..so the transactions fails or not.
    you're just not capable of checking if the transaction went ok...and return 'process completed ok' or when the transaction failed for some reason return 'the process aborted'.
    So you just need some extra steps for it to be able to return some response-message

  • XSLT mapping to remove namespace prefix

    Hi experts,
    I have one requrement where I need to remove the prefix ns0 from the xml (given below) getting generated in message mapping.
    <?xml version="1.0" encoding="UTF-8"?><soap:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><ns0:ExecuteRequest xmlns:ns0="http://test/">
    <ns0:_sRequestXML><inteflow>body</inteflow></ns0:_sRequestXML></ns0:ExecuteRequest></soap:Body></soap:Envelope>
    I am usimg the below xslt and it is now adding one ns0 prefix in the tag <inteflow>.
    <?xml version="1.0" encoding="UTF-8"?>
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
    <xsl:template match="/">
    <ExecuteRequest xmlns="http://test/">
    <_sRequestXML>
    <inteflow>
    <xsl:copy-of select="//inteflow"/>
    </inteflow>
    </_sRequestXML>
    </ExecuteRequest>
    </xsl:template>
    </xsl:stylesheet>
    Result after using xslt.
    <?xml version="1.0" encoding="UTF-8"?><soap:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><ExecuteRequest xmlns="http://test/"><_sRequestXML>
    <inteflow xmlns:ns0="http://decisionintellect.com/inteport/"></inteflow></_sRequestXML></ExecuteRequest></soap:Body></soap:Envelope>
    Can you please help. What is wrong in the xslt and how I can get the desired result.
    Thanks & Regards,
    Pratyus Ganguly
    <?

    Hi Pratyus
    XMLAnonymizerBean works fine when I try it with your payload. Here is the config, basically I included the namespace for everything except the ns0.
    Parameter Name
    Parameter Value
    anonymizer.acceptNamespaces
    http://www.w3.org/2001/XMLSchema xsd http://www.w3.org/2001/XMLSchema-instance xsi http://schemas.xmlsoap.org/soap/envelope/ soap
    Before
    After
    Rgds
    Eng Swee

  • Namespace prefix in SOAP Elements causes problems in XI

    Hi guys,
    I'm using code generated by NW Developer Studio for use inside Portal components acting as a web service consumer. The problem is that the code generated includes a namespace prefix for each element in the body of the message, but XI doesn't like the namespace prefixes and throws back a DeliveryException.
    The SOAP message created by the generated NWDS code is:
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wn3="http://www.w3.org/1999/XMLSchema" xmlns:wn2="http://www.w3.org/2000/10/XMLSchema" xmlns:wn1="http://www.w3.org/2001/XMLSchema" xmlns:wn0="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wn4="http://allieddomecq.com/poc" xmlns:tns="http://allieddomecq.com/poc">
         <SOAP-ENV:Body>
              <wn4:PortalSOAP_MT_Request>
                   <wn4:CustomerIdentifier>0001000064</wn4:CustomerIdentifier>
                   <wn4:SalesOrganization>ES50</wn4:SalesOrganization>
                   <wn4:SystemIdentifier>R3D</wn4:SystemIdentifier>
              </wn4:PortalSOAP_MT_Request>
         </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    The problem is the "wn4" prefixes on the CustomerIdentifier, SalesOrganization, and SystemIdentifier tags. When we send the soap request from XML Spy without the prefixes, the response comes back OK with the expected data.
    I've had a very good look around the generated code - the serializers for creating the soap request - but could not find what exactly might be changed to leave off the prefixes.
    Alternatively, is there something I could ask our XI consultant to do, to make his component accept the request with the redundant prefixes in the tags?
    Many thanks for any advice/help,
    Laura

    Hi Laura,
    you have to realize that the two documents
    <ns:CustomerRecord xmlns:ns="http://company.com">
    <ns:CustomerNumber> </ns:CustomerNumber>
    <ns:CustomerDetails> </ns:CustomerDetails>
    </ns:CustomerRecord>
    and
    <ns:CustomerRecord xmlns:ns="http://company.com">
    <CustomerNumber> </CustomerNumber>
    <CustomerDetails> </CustomerDetails>
    </ns:CustomerRecord>
    from an XMl point of view have totally fifferent structure. Thus, a mapping which is able to deal with the first structure will fail for the second and vice versa.
    Surely, both structures somehow can carry the same information, but they do this with different languages (Maybe you can compare this to the fact, that you may deliver the same information in English or in German language).
    When you model the structure in Integration Repository using datatypes and message types (what I think you did), you will always get a structure that looks like the second one. This is just a convention (like the convention that all information in this forum should be presented in English). When defining a message mapping for this structure it also relies on this fact and thus will not understand the other kind of document.
    External Definitions are more flexible. They are also able to understand structures that are modelled the other way. This greater flexibility is due to the fact that External Definitions were designed to understand structures that come from an external world where different conventionts might be used.
    To come to a conclusion: If the structure you have to deal with has been defined externally then it is not intended that you model it inside the Integration Builder using datatypes and message types. In this case the external source should provide a description of the message as XSD, WSDL, or DTD. You upload this as External Definition, and everything works fine.
    If you have designed the structure yourself, you can model it with datatypes and message types. But then you will always get a structure which looks like the second one. In this case you should make sure that all other participants in the game also stick to that structure. Then everything will be fine, too.
    Greetings Stephan

  • Removing namespace prefixes

    I am familiar with the XmlOptions.setUseDefaultNamespace() to remove the namespace prefixes on the XML generated by my XMLBean. However, how do I specify which namespace prefix should be removed (if my XMLBean contains multiple namespace prefixes)? The docs for XmlOptions specify:
    "If this option is set, the saver will try to use the default namespace for the most commonly used URI. If it is not set the saver will always created named prefixes."
    Doing some testing, I have found that sometimes the correct namespace is being set as the default namespace. If my original document is:
    <ns1:a ...>
    <ns1:b ...>foo</b>
    <ns2:c ...>bar</c>
    </a>
    if I use the xmlText(XmlOptions) method then I sometimes get back:
    <a ...>
    <b ...>foo</b>
    <ns2:c ...>bar</c>
    </a>
    and sometimes get:
    <ns1:a ...>
    <ns1:b ...>foo</b>
    <c ...>bar</c>
    </a>
    Any thoughts?

    Hello,
    I'm using xmlbeans in my project. I'm constructing xml using the xmlbeans
    generated sources from the XML Schema files. The server to which I'm
    sending the request doesn't recognize the namespace URI's or the prefixes.
    so, once the XML document is constructed, I'm trying to strip of the
    namespace URI's and prefixes using the below code and couldn't get it to
    work.
    Map m=
    new HashMap();
    m.put(
    http://www.abc.com/schemas/myproj/avail/2008/01, "");
    m.put(
    http://www.abc.com/schemas/myproj/common/2008/01,"";);
    opts.setLoadSubstituteNamespaces(m);
    opts.setUseDefaultNamespace();
    SampleRQDocument propAvailRQDoc = SampleRQDocument.Factory.*newInstance*
    (opts);
    The schemas are defined under 3 different namespaces.
    How can I remove the Namespace URI's and Prefixes after I construct the XML
    document?
    Next thing, when the server sends the response, the response doesn't include
    any Namespace URI or the prefixes. How can I embed the URI's and Prefixes in
    the response document after I receive it so, I can use XML Beans
    to bind the XML to the generated sources.
    I searched on google but couldn't find a suitable solution.
    Any help in this regard is greatly appreciated.
    Thanks,
    Sridhar.

  • How to remove namespace Prefix ns0

    Hi ,
    I receive an xml from an external service.In that each element in prefixed by namespace ns0: How can I remove that name space.I trieed using
    ora:ProcessXSLT.But its not working.Its giving TypeError
    Please find below my xml and xslt files.
    XML ---
    <ProcessSalesLead xmlns:ns0="http://www.starstandards.org/STAR/ProcessSalesLead" revision="3.0" release="8.1-Lite" environment="Production" lang="en-US" xmlns="http://webservice.services.freeway.wipro.com">
    <ns0:ApplicationArea>
    <ns0:Sender>
    <ns0:Component>String</ns0:Component>
    <ns0:Task>SalesLead</ns0:Task>
    <ns0:ReferenceId>1-4CPJ</ns0:ReferenceId>
    <ns0:CreatorNameCode>XX</ns0:CreatorNameCode>
    <ns0:SenderNameCode>XX</ns0:SenderNameCode>
    </ns0:Sender>
    <ns0:CreationDateTime>2007-11-28T15:33:16+05:30</ns0:CreationDateTime>
    <ns0:Destination>
    <ns0:DestinationNameCode>XX</ns0:DestinationNameCode>
    <ns0:DealerNumber>10005</ns0:DealerNumber>
    </ns0:Destination>
    </ns0:ApplicationArea>
    <ns0:DataArea>
    <ns0:Process acknowledge="Never" confirm="Always"/>
    <ns0:SalesLead>
    <ns0:Header>
    <ns0:DocumentId>1-4CPJ</ns0:DocumentId>
    <ns0:IndividualProspect>
    <ns0:PersonName>
    <ns0:GivenName>Ray</ns0:GivenName>
    <ns0:FamilyName>Aamos</ns0:FamilyName>
    </ns0:PersonName>
    <ns0:Address>
    <ns0:AddressLine>1200 Davisville Rd</ns0:AddressLine>
    <ns0:City>York</ns0:City>
    <ns0:StateOrProvince>AL</ns0:StateOrProvince>
    <ns0:Country>US</ns0:Country>
    <ns0:PostalCode>78201</ns0:PostalCode>
    </ns0:Address>
    <ns0:Contact>
    <ns0:Telephone desc="Day Phone">2018742349</ns0:Telephone>
    <ns0:EMailAddress desc="Work">[email protected]</ns0:EMailAddress>
    <ns0:Fax desc="Work">2018745698</ns0:Fax>
    </ns0:Contact>
    <ns0:OwnedVehicle>
    <ns0:Model>Sonata</ns0:Model>
    <ns0:ModelYear>2006</ns0:ModelYear>
    <ns0:Make>Hyundai</ns0:Make>
    </ns0:OwnedVehicle>
    </ns0:IndividualProspect>
    <ns0:Provider>
    <ns0:Contact>
    <ns0:PersonName>
    <ns0:GivenName/>
    <ns0:FamilyName/>
    </ns0:PersonName>
    </ns0:Contact>
    </ns0:Provider>
    <ns0:Dealer>
    <ns0:DealerName>Metro Motors Florida</ns0:DealerName>
    <ns0:Address>
    <ns0:AddressLine>Miami</ns0:AddressLine>
    <ns0:City>Miami</ns0:City>
    <ns0:StateOrProvince>FL</ns0:StateOrProvince>
    <ns0:Country>US</ns0:Country>
    <ns0:PostalCode>33010</ns0:PostalCode>
    </ns0:Address>
    <ns0:SalesContact>
    <ns0:Telephone desc="Day Phone">3058938000</ns0:Telephone>
    </ns0:SalesContact>
    <ns0:OrganizationName>Metro Motors Florida</ns0:OrganizationName>
    </ns0:Dealer>
    <ns0:LeadComments>Existing Vehicle info</ns0:LeadComments>
    </ns0:Header>
    <ns0:Detail>
    <ns0:LeadStatus>Accepted</ns0:LeadStatus>
    <ns0:SalesVehicle>
    <ns0:Model>Camry</ns0:Model>
    <ns0:ModelYear>2007</ns0:ModelYear>
    <ns0:ModelDescription>Camry LE</ns0:ModelDescription>
    <ns0:Make>Toyota</ns0:Make>
    <ns0:VehicleNote/>
    <ns0:ExteriorColor/>
    <ns0:TransmissionType>A</ns0:TransmissionType>
    </ns0:SalesVehicle>
    </ns0:Detail>
    </ns0:SalesLead>
    </ns0:DataArea>
    </ProcessSalesLead>
    XSLT --
    <?xml version="1.0" encoding="UTF-8"?>
    <xsl:stylesheet version="1.0"
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
    <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>
    <xsl:template match="*">
    <!-- remove element prefix (if any) -->
    <xsl:element name="{local-name()}">
    <!-- process attributes -->
    <xsl:for-each select="@*">
    <!-- remove attribute prefix (if any) -->
    <xsl:attribute name="{local-name()}">
    <xsl:value-of select="."/>
    </xsl:attribute>
    </xsl:for-each>
    <xsl:apply-templates/>
    </xsl:element>
    </xsl:template>
    </xsl:stylesheet>
    Please help me on this.Its very urgent .
    thanks
    deepthi

    can you please copy paste your schema validation errors. i suspect there is a mismatch between your schema and xml data that you input to your schema processor. can you copy paste the definition of your schema for <ProcessSalesLead>.
    you mentioned you received this xml from external service, maybe this external service doesn't have the correct schema and generates this xml which is not compatible with your schema.
    I would suggest to validate this xml as part of your receive, please use "validateXML" partner link property in bpel.xml, so you avoid invalid documents getting into the system at first.
    <partnerLinkBindings>
    <partnerLinkBinding name="...">
    <property name="wsdlLocation">http://localhost:8888/orabpel/default/1.0/yourParnerProcess?wsdl</property>
    <property name="validateXML">true</property>
    </partnerLinkBinding>

  • JDeveloper 10.1.3 - Disabling ns0: namespace prefix in soap body children ?

    I am attempting to use a PeopleSoft web service. However, the PeopleSoft web service does not recognize operations which have a namespace prefix. Using visual studio, namespace prefixes are not used in the child elements of the soap body element. I am able to call the service using visual studio.
    JDeveloper 10.1.3 uses a namespace prefix for children of the body element which is recommended by the soap spec. However, I need to disable that behavior so that I can actually get the program working with PeopleSoft.
    Can anyone tell me if there is an easy way to disable the ns0: prefix that is used by the generated web service proxy stub? I have traced through the generated proxy code but I do not see any properties that can be modified. The only thing I can think of is to modify the generated code but I do not want to go that route.
    Thanks,
    Rich

    Delete the NS0: related text, in JDev, from your WSDL and it should work. I had the same problem with .NET not liking it also.
    Keep in mind you'll have to tweak the WSDL again if you regenerate it.
    You sure you're using 10.1.3? I upgraded and it shows the NS0: as a problem in existing projects. I'm working on the latest, production download so maybe it's been corrected.

  • Remove XML Prefix in SOAP Sender Adapter

    Hi
    I am using a SOAP sender adapter and testing it from SOAP UI. The format that is generated from the web service is
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
       <soapenv:Body>
          <sap:SALES_ORDER xmlns:sap="http://XYZ.org/">
             <sap:HEADER>
                <sap:BATCH_ID>XYZ</sap:BATCH_ID>
                <sap:CREATE_DT>XYZ</sap:CREATE_DT>
    This format when processed in SOAP UI gave error which its not giving for other files. Clearly I need to remove this sap: tag, I can't use XML anonymizer as it is SOAP adapter and I can't select do not use soap env...Could anyone provide me Java/xslt code for the same..I tried all the codes on sdn but none of them worked.
    Regards,

    SImple Java mapping, that should help
    import java.io.InputStream;
    import java.io.OutputStream;
    import com.sap.aii.mapping.api.*;
    import org.w3c.dom.*;
    public class DeleteCDATA_DOM_mapping extends  AbstractTransformation  {
         public void traceXML(Node n,int i)
         {   AbstractTrace trace = getTrace();
              trace.addInfo(i+"$"+n.getNodeName());
              trace.addInfo(i+"$"+n.getNodeValue());
              trace.addInfo(i+"$"+n.getNodeType()+"");
         public void traceNL(NodeList nl)
              {       for (int i=0 ; i<nl.getLength();i++)
                        traceXML(nl.item(i),i);
         public void transform(TransformationInput in, TransformationOutput out)
                   throws StreamTransformationException {
                        AbstractTrace trace = getTrace();
                             try {
                                  InputStream is0=in.getInputPayload().getInputStream();
                                  StringBuffer out1 = new StringBuffer();
                                  byte[] b = new byte[4096];
                                  for (int n; (n = is0.read(b)) != -1;) {
                                       out1.append(new String(b, 0, n,"UTF-8"));
                                  String sss=out1.toString();
                                  sss=sss.replaceAll("<sap:", "<");
                                  sss=sss.replaceAll("</sap:", "<");
                                  OutputStream os = out.getOutputPayload().getOutputStream();
                                  os.write(sss.getBytes("UTF-8"));
                             } catch (Exception e) {
                                  throw new StreamTransformationException(
                                       "Exception in DeleteCDATA_DOM_mapping JAVA mapping ): "
                                            + e.getMessage());

  • Data from SOAP response not getting into Flex object

    I'm trying to get data from an ALM application we use(Collabnet TeamForge) using a SOAP webservice, and am running into a problem.  I should mention that I am new to both Flex, and webservices.
    I used the "Import Web Services" option in Flex Builder 3, and had it generate code for all operations in the WSDL.  Some of them work just fine.  However, there are several where the data from the SOAP response does not get into the Flex object. The senario that doesn't work is when the response contains a data type that extends another datatype.  In TeamForge, they have a type called TrackerSoapRow.  It extends FolderSoapRow, adding 3 fields.  The problem seems to be that in the response from TeamForge, the 3 fields defined in TrackerSoapRow are in the middle of the fields defined in FolderSoapRow.  I've debugged into it, and the problem occures in mx.rpc.xml.XMLDecoder.getApplicableValues( starting at line 2204 of XMLDecoded.as).  As I read the code, the only way a match can be found is if the fields in the response are in the exact same order as in the definintion.  When its processing the extended data type(  by a call to XMLDecoder.decodeComplexExtension ) at some point, one of the derived type's fields is encountered, and the process stops.
    I have called the service using soapui and verified that all the data I expect is in the response.
    As I mentioned, I'm new to web services.  So, I suppose its possible that the format of the data being returned from TeamForge is incorrect.  That they are not supposed to intermingle base and derived fields.  If thats the case, then I need to report this as a bug to Collabnet.
    All help is appreciated.
    Marc Robertson

    Not knowing any of the details about how you call a web service from OAF myself - I'd suggest you post on the proper forum for OA Framework questions: {forum:id=210}
    John

  • Remove L01 prefix from Olap uni

    HI Experts
    In my webi doc . i should not have L01 prefix from the olap universe.
    For ex: if i have L01Country from olap uni . i should only have country in webi.
    My issue is i can edit object properties and do it but how to do it at once when there are around 2000 or more object details i cant edit each and every one .
    any procedure to hide it r remove it at universe level
    Regards

    i think this link may help you
    http://www.forumtopics.com/busobj/viewtopic.php?t=21029&postdays=0&postorder=asc&start=0
    good luck
    Amr

  • How to remove namespace link from the output XML

    i have to remove 'xmlns:xdoxslt="http://www.oracle.com/XSL/Transform/java/oracle.apps.xdo.template.rtf.XSLTFunctions"' (namespace) from the output xml file which is generated from the BIP. I need my output XML file without that namespace link, this namespace link is coming for each element.
    Anybody know how to do that please help.
    output xml file
    <?xml version="1.0" encoding="UTF-8" ?>
    <Reports version="2.00">
    <deliveryNote xmlns:xdoxslt="http://www.oracle.com/XSL/Transform/java/oracle.apps.xdo.template.rtf.XSLTFunctions">
    <subjectId />
    </deliveryNote>
    <deliveredReports xmlns:xdoxslt="http://www.oracle.com/XSL/Transform/java/oracle.apps.xdo.template.rtf.XSLTFunctions">
    <referDate>[Delivery note->H4]</referDate>
    </deliveredReports>
    <simpleReports xmlns:xdoxslt="http://www.oracle.com/XSL/Transform/java/oracle.apps.xdo.template.rtf.XSLTFunctions">
    <numberOfReports>2</numberOfReports>
    <nReport>
    <reportName>Xyz</reportName>
    <reportVersion>1.0</reportVersion>
    <observations>
    <numberOfObservations>15</numberOfObservations>
    <columnObservation>
    <y>9</y>
    <rO>
    <x>14</x>
    <o>11</o>
    <o>21</o>
    <o>121</o>
    </rO>
    </columnObservation>
    </observations>
    </nReport>
    </simpleReports>
    </Reports>
    my xslt file
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xdoxslt="http://www.oracle.com/XSL/Transform/java/oracle.apps.xdo.template.rtf.XSLTFunctions" >
    <xsl:output method="xml" encoding="UTF-8"/>
    <xsl:template match="/">
         <xsl:element name="Reports">
              <xsl:attribute name="version">2.00</xsl:attribute>
                   <deliveryNote>
                        <subjectId></subjectId>
                        </deliveryNote>
                   <deliveredReports>
                        <referDate>[Delivery note->H4]</referDate>
                   </deliveredReports>
                   <simpleReports>
                        <numberOfReports>2</numberOfReports>
                        <nReport>
                                  <reportName>Xyz</reportName>
                                  <reportVersion>1.0</reportVersion>
                                       <observations>
                                       <numberOfObservations>15</numberOfObservations>
                                       <columnObservation>
                                            <y>9</y>
                                            <rO>
                                                 <x>14</x>
                                                      <xsl:for-each select="TEST_XML/LIST_R1/R1">
                                                           <o><xsl:value-of select="xdoxslt:lpad(COL1,10,' ')"/></o>
                                                      </xsl:for-each>
                                            </rO>
                                       </columnObservation>
                                       </observations>
                             </nReport>
                        </simpleReports>
              </xsl:element>
    </xsl:template>
    </xsl:stylesheet>

    Please post the same in BI Publisher forum
    BI Publisher
    Thanks,
    Vino

Maybe you are looking for

  • Function Module RSDRI_DATA_WRAP_V

    BI Experts, As part of BI 7.0 SAP has delivered a Function Module 'RSDRI_DATA_WRAP_V' which is basically called by the Function Module 'RSDRI_INFOPROV_READ_RFC'. In our particular case we are exposing FM ' RSDRI_INFOPROV_READ_RFC' as a web service. U

  • R12 plsql web toolkit disabled - what are the alternatives?

    We have developed a fair amount of add-on applications in our e-business suite using the plsql web toolkit (htp). This functionality has been disbaled in R12. My question to Oracle, "What is the work around for using applications we developed in 11i

  • Black background after update to 10.6.7 or 10.6.8

    Hello Community, im new in here and would like to ask for help. My Problem is that when i will update my machine from 10.6.6 to 10.6.7/10.6.8 my backgrounds in Finder and the rest of my OS Control panels are in black so that i can´t use my machine re

  • How to divide a large avi file

    Hope that this is the appropriate forum for this. I have a large .avi movie file which will not fit onto a single DVD-R disc (4.7GB) when I try to use Toast for burning. Is there any simple way of dividing the file into two parts so that each part wi

  • How do you get icloud on my pc

    I have aspire one notebook laptop and I want Icloud in my pc so how do I find that or get it or whatever?