Import for WSDL in rpc-Style Format with ComplexContent SOAP-ENC:Array

Hello, we are working on a business process that consume a web services using XI and ABAP Proxy.
We have and error type CANNOT_PRODUCE_ELEMENT, problably because the WSDL rpc-style imported on Integration Respository contents elements like this:
<complexContent>
  <restriction base="SOAP-ENC:Array">
    <attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="ns1:mytype[]" />
  </restriction>
</complexContent>
SO, anybody knows if it's possible to dessign mapping correctly with others elements like "sequence"... ?
Thanks a lot,

Alex,
I would recommend to check your WSDL for any syntax errors etc in any of the external tools like XML SPY or Stylus Studio etc and then upload into XI.
---Satish

Similar Messages

  • Catch: could not retrieve wsdl imports for wsdl

    Hello, I am using JDeveloper 11.1.1.17 and am configuring a catch in a BEPL for a web service.
    The web service itself works, and the composite that is calling the web service works properly.  I am now trying to configure the catch for the web service.  I create the catch, and double-click it to get the GUI for the configuration.
    I click on the magnifier to open the "Fault Chooser" window.  I click on the Partner links, then the service, and then the "Imported WSDL" for the service.  This exposes an error message:  Exception: could not retrieve wsdl imports for wsdl
    Given that the web service calls a service on a remote server (within my organization, however), I tried re-creating the web service call, and the second time specified that it "copythe WSDL and its dependent artifacts into the project" to see if this would allow the catch to "grab" the wsdl.
    It does not.  The wsdl is listed under the project wsdl files, but each project wsdl file does not show the necessary information.
    Does anyone know if I am doing anything incorrect?
    Points Vigorously awarded!
    Stuart

    Hi HDeiby,
    We are facing similar issue and trying to resolve the Oracle advices not to Copy the WSDL files locally , and writes a note " Keeping a copy of WSDL may result in synchronization issues "  in Jdeveloper when you try to create a reference .
    We found out a way to access the Fault by adding PartnerLink to the WSDL ( I know that it is not a best practice to mix interface and implementation ) . This avoids the synchronization issues .
    Do you have any other Thoughts .
    Cheers,
    Lakshmi

  • Using XSLT "adapter" for invoking a WS with SOAP-ENC array type param.

    Hello,
    I had to write a BPEL process that calls inside it a web service which has as an input an array parameter and as an output, also an array. I already know that BPEL has limitations regarding using the SOAP-ENC Array type. I tried to rewrite the web service in order to use a literal encoding of the array parameters (using "maxOccurs" attribute), but unfortunately, the OC4J container 9.0.4 that I have to use doesn't allow this. It only allows the SOAP-ENC types for array types.
    I started to write, inside the BPEL process, some "adapters" XSLT transformations before and after the invoking of the web service that uses SOAP-ENC array. The XSLT transformation before the web service invoking will translate the input array parameter defined with no SOAP encoding types (based on "maxOccurs" attribute) into a SOAP-ENC type, as it is expected by the web service. The XSLT transformation after the web service invoking will translate the returned array SOAP-ENC type into a data type defined with no SOAP encoding types (based on "maxOccurs" attribute).
    The approach is pretty hairy, from the XSLT point of view and it introduces a supplementary delay due to the XSLT processing needed, but it works. The only think is that when I build the service, I obtain the following error message:
    [bpelc] [Error] GCDBWebservice?WSDL:30:42: src-resolve.4.2: Error resolving component 'SOAP-ENC:Array'. It was detected that 'SOAP-ENC:Array' is in namespace 'http://schemas.xmlsoap.org/soap/encoding/', but components from this namespace are not referenceable from schema ...
    But in spite of this, the process is built and deployed successfully and I was able to run it from the BPEL console.
    Do you think that this approach could hide some other future problems that I can't see in this moment?
    Thanks,
    Marinel

    Please help me for this.
    I am new to Webservices and SOAP.
    I am facing problem when i am calling a "add" method in the .net webservices with the following code but it gives correct result when i'm calling the "HelloWorld" method present in the webservice.
    I think it will happening because, when i'm going to pass any parameter to the "add method , it does not process it.It will return me 0.
    Please help me in this.
    The code is:
    import java.io.*;
    import java.util.*;
    import java.net.*;
    import org.w3c.dom.*;
    import org.apache.soap.util.xml.*;
    import org.apache.soap.*;
    import org.apache.soap.encoding.*;
    import org.apache.soap.encoding.soapenc.*;
    import org.apache.soap.encoding.literalxml.*;
    import org.apache.soap.rpc.*;
    import org.apache.soap.transport.http.SOAPHTTPConnection;
    import org.apache.soap.transport.*;
    import org.apache.soap.messaging.*;
    import org.apache.xerces.parsers.*;
    import org.apache.xerces.dom.DocumentImpl;
    public class testClient {
    public static void main(String[] args) throws Exception {
    URL url = new URL ("http://Eurotele-it3/webService1/Service1.asmx");
    //Map the Types.
    SOAPMappingRegistry smr = new SOAPMappingRegistry ();
    StringDeserializer sd = new StringDeserializer ();
    smr.mapTypes(Constants.NS_URI_SOAP_ENC,new QName("http://Eurotele-it3/WebService1/Service1","addResult"),Integer.class,null,sd);
    // create the transport and set parameters
    SOAPHTTPConnection st = new SOAPHTTPConnection();
    // build the call.
    Call call = new Call();
    call.setSOAPTransport(st);
    call.setSOAPMappingRegistry(smr);
    call.setTargetObjectURI ("http://Eurotele-it3/WebService1/Service1/add");
    call.setMethodName("add");
    //call.setEncodingStyleURI("http://schemas.xmlsoap.org/soap/encoding/");
    call.setEncodingStyleURI(Constants.NS_URI_SOAP_ENC);
    Vector params = new Vector();
    params.addElement(new Parameter("x",Integer.class,"10",null));
    params.addElement(new Parameter("y",Integer.class,"20",null));
    call.setParams(params);
    Response resp = null;
    try {
    resp = call.invoke (url,"http://Eurotele-it3/WebService1/Service1/add");
    catch (SOAPException e) {
    System.err.println("Caught SOAPException (" + e.getFaultCode () + "): " +e.getMessage ());
    return;
    // check response
    if (resp != null && !resp.generatedFault()) {
    Parameter ret =resp.getReturnValue();
    Object value =ret.getValue();
    System.out.println ("Answer--> " +value );
    else {
    Fault fault = resp.getFault ();
    System.err.println ("Generated fault: ");
    System.out.println (" Fault Code = " + fault.getFaultCode());
    System.out.println (" Fault String = " + fault.getFaultString());
    This is the complete WSDL format:
    <?xml version="1.0" encoding="utf-8" ?>
    - <wsdl:definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://Eurotele-it3/WebService1/Service1" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" targetNamespace="http://Eurotele-it3/WebService1/Service1" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    - <wsdl:types>
    - <s:schema elementFormDefault="qualified" targetNamespace="http://Eurotele-it3/WebService1/Service1">
    - <s:element name="HelloWorld">
    <s:complexType />
    </s:element>
    - <s:element name="HelloWorldResponse">
    - <s:complexType>
    - <s:sequence>
    <s:element minOccurs="1" maxOccurs="1" name="HelloWorldResult" type="s:int" />
    </s:sequence>
    </s:complexType>
    </s:element>
    - <s:element name="add">
    - <s:complexType>
    - <s:sequence>
    <s:element minOccurs="1" maxOccurs="1" name="x" type="s:int" />
    <s:element minOccurs="1" maxOccurs="1" name="y" type="s:int" />
    </s:sequence>
    </s:complexType>
    </s:element>
    - <s:element name="addResponse">
    - <s:complexType>
    - <s:sequence>
    <s:element minOccurs="1" maxOccurs="1" name="addResult" type="s:int" />
    </s:sequence>
    </s:complexType>
    </s:element>
    </s:schema>
    </wsdl:types>
    - <wsdl:message name="HelloWorldSoapIn">
    <wsdl:part name="parameters" element="tns:HelloWorld" />
    </wsdl:message>
    - <wsdl:message name="HelloWorldSoapOut">
    <wsdl:part name="parameters" element="tns:HelloWorldResponse" />
    </wsdl:message>
    - <wsdl:message name="addSoapIn">
    <wsdl:part name="parameters" element="tns:add" />
    </wsdl:message>
    - <wsdl:message name="addSoapOut">
    <wsdl:part name="parameters" element="tns:addResponse" />
    </wsdl:message>
    - <wsdl:portType name="Service1Soap">
    - <wsdl:operation name="HelloWorld">
    <wsdl:input message="tns:HelloWorldSoapIn" />
    <wsdl:output message="tns:HelloWorldSoapOut" />
    </wsdl:operation>
    - <wsdl:operation name="add">
    <wsdl:input message="tns:addSoapIn" />
    <wsdl:output message="tns:addSoapOut" />
    </wsdl:operation>
    </wsdl:portType>
    - <wsdl:binding name="Service1Soap" type="tns:Service1Soap">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
    - <wsdl:operation name="HelloWorld">
    <soap:operation soapAction="http://Eurotele-it3/WebService1/Service1/HelloWorld" style="document" />
    - <wsdl:input>
    <soap:body use="literal" />
    </wsdl:input>
    - <wsdl:output>
    <soap:body use="literal" />
    </wsdl:output>
    </wsdl:operation>
    - <wsdl:operation name="add">
    <soap:operation soapAction="http://Eurotele-it3/WebService1/Service1/add" style="document" />
    - <wsdl:input>
    <soap:body use="literal" />
    </wsdl:input>
    - <wsdl:output>
    <soap:body use="literal" />
    </wsdl:output>
    </wsdl:operation>
    </wsdl:binding>
    - <wsdl:service name="Service1">
    <documentation xmlns="http://schemas.xmlsoap.org/wsdl/" />
    - <wsdl:port name="Service1Soap" binding="tns:Service1Soap">
    <soap:address location="http://eurotele-it3/webService1/Service1.asmx" />
    </wsdl:port>
    </wsdl:service>
    </wsdl:definitions>

  • Thank you very much Ken your answer was very important for me. Could I discuss with you about several topics of Imaq

    My email -> [email protected]

    Hi Frank,
    I'm glad to have helped you out. You can also contact National Instrumentst Technical Support directly through www.ni.com/ask
    Ken Sun
    Applications Engineer
    National Instruments

  • Import RPC-style WSDL

    Hello!
    I currently implement a RFC -> RFC adapter -> XI -> SOAP adapter -> Web Service scenario. I have imported the WSDL of the Web Service as External Definition into the Integration Repository to use it for the RFC <-> Web Service mapping within the graphical mapping tool.
    Until now I only have imported document-style WSDL and there never have been any problems. Now the WSDL is RPC-style which means that the messages described by the <wsdl:types>...</wsdl:types> part should be enclosed by an additonal structure describing the Web Service operation to be executed.
    However, in the graphical mapping tool the structure for  the Web Service operation is missing and thus the Web Service call cannot be executed. How can I solve this problem without changing the WSDL or creating an additional XLST or Java mapping?
    It seems that there is no problem with the WSDL. When I loaded it with the Web Service Navigator test tool of the SAP Web Application Server the structure describing the Web Service operation has been generated in the request message.
    Regards, Tanja Schättler

    Hi Tanja
    Check this note 856597, it even has some examples of WSDL documents and sample SOAP messages that illustrate how one can write an equivalent WSDL in another style.
    A snippet from the note,
    "Q: Can I convert an RPC styled WSDL to a document styled WSDL?
                A: It is difficult to answer yes or no because the answer depends on the WSDL instance and the implementation of the code that binds the XML instance to some native object. The problem comes from the fact that these two styles describe web services in different layers. The document style WSDL describes how one can bind an XML document to the SOAP message format. In contrast, the RPC style WSDL describes how one can bind an object to the SOAP message format. One can imagine that this works in two steps: first representing the object as an XML document and then binding this XML document to the SOAP message format. How this first step works is controlled by the SOAP encoding name. For the standard encoding specified in the SOAP specification, most objects can be easily described in an equivalent XML schema. Some special objects such as references and arrays must be represented by some special rules and some additional meta information in XML. This implies that these additional attributes and elements must also be described in the XML schema and the document style based proxy must set these values in the instance appropriately.
                One must however note that even if one has an equivalent document style WSDL, this does not automatically guarantees the interoperability. Some RPC styled service implementations have significant interoperability problems such as requiring the xsi:type attribute for every element or the SOAP encoding attribute at some particular element. If one has to call such non conformant SOAP service, one must adjust the message accordingly.
               Attachment wsdl_style_samples. zip contains some examples of WSDL documents and sample SOAP messages that illustrate how one can write an equivalent WSDL in another style.
                Related Questions "Does the RPC or Document style in WSDL play a role in the SOAP adapter?"
    cheers
    Sameer

  • Excel Importer for Visual Studio LightSwitch 2013

    Has anyone managed to get the 'Excel Importer for Visual Studio LightSwitch' extension working with Visual Studio 2013?

    Hi Kevin,
    I assume you mean this extension here -
    http://code.msdn.microsoft.com/silverlight/Excel-Importer-for-Visual-61dd4a90
    From what I can tell that does not yet support VS 2013.  The source code is of course available, so you could attempt to fix it up yourself and tell us the result.
    Thanks.
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Exception on creation of service metadata for WSDL

    trying to access webservice (generated on Oracle applic. Server)  as Adaptive WebServiceModel i get the following error:
    Exception on creation of service metadata for WSDL
    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory
    Initialization problem. Could not load web service model. See nested exception for details.
         at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:150)
         at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.<init>(DGenericServiceImpl.java:50)
         at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:88)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:412)
         ... 53 more
    Caused by: java.lang.UnsupportedOperationException: Type {http://schemas.xmlsoap.org/soap/encoding/}Array is not supported!
         at com.sap.engine.services.webservices.espbase.client.dynamic.types.impl.MetadataLoader.loadMetadata(MetadataLoader.java:129)
    So, the code in WSDL is like:
    targetNamespace="http://com.rwe.lis.webservices/IWSFidLis.xsd"
             xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns="http://www.w3.org/2001/XMLSchema">
    <complexType name="ArrayOfcom_rwe_lis_model_Flurstueck" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
                <complexContent>
                   <restriction base="SOAP-ENC:Array">
                      <attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="ns1:com_rwe_lis_model_Flurstueck[]"/>
                   </restriction>
                </complexContent>
             </complexType>
    generated by JDeveloper on Ora Server.
    So - how to get access to this WebService?!?
    Bernhard

    Hi,
       The use of SOAP-ENC:Array is not supported in NW because it is not WS-I compliant. For a possible solution check [this|Re: unknown namespace error when generating a client proxy; link.
    Regards,
    Satyajit

  • Unwanted Default Formatting with import XML

    I have a problem of unwanted default formatting with import XML. Under InDesign CS6, I  import XML with merge mode.
    One frame is difficult to apply with the placeholder, I should put the XML element A inside by hand. InDesign automatically applies the character style of the child element B to the following text in element A.
    I tried the steps of this article http://indesignsecrets.com/fixing-unwanted-default-formatting.php/comment-page-1#comment-5 62875
    But it doesn't work for me.
    Dose anyone have an idea? Thanks.

    Kasyan, I agree with you!
    So this is what i did in xslt.
    First I added the following namespace to the stylesheet.
    xmlns:file="http://www.jclark.com/xt/java/java.io.File"
    This is not supported by indesign, you have to do this with a parser. I used saxon to parse the xml.
    And this is the part for the existing file lookup.
    If the file exists the image is placed as a href, if it doesn't exist i put the name of the image between brackets. In this case we can see in which image doesn't exist.
    <xsl:choose>
         <xsl:when test="file:exists(file:new(string($imagefile)))">                                         
              <xsl:element name="Articleimage">
                   <xsl:attribute name="href">file://../images/<xsl:value-of select="Properties/Property[@field = 9]"/></xsl:attribute>
              </xsl:element>
          </xsl:when>
          <xsl:otherwise>
              <xsl:text>[</xsl:text><xsl:value-of select="Properties/Property[@field = 9]"/><xsl:text>]</xsl:text>
          </xsl:otherwise>
    </xsl:choose>
    I hope it helps for others.
    Good luck!
    Glen

  • Rpc style wsdl

    Dear Experts,
               We have a wsdl with soapenc type and soapenc array type. The webservice is RPC style.
    does PI 7.0 support rpc style call. I read we could do it by creating soap request and using do not use soap
    envelope.  Still do we need to encode the values before sending it out of PI?   where does the encoding take place ?
       I am using the soap lookup for the webservice call. So can i use the soap request structure directly inside the udf ? Please help...
    Thanks,
    Aju

    Hi Shabarish,
                   Thanks for the reply.
    1. So our option is to ask the webservice provider to change it to doc type , right?
    2.And what to do with soapen data type . do we need to do the encoding before we send.. what i mean to ask is how does PI handle the datatype differences.. for example if we send a string type data to a soap enc type data type ... should we do the encoding. and where does the encoding happen ?
    3. when we use the do not use soap envelope , we need to create the soap request in the message mapping ,
    including the header and send to adapter, and adapter makes the call with it wihout making any changes. is that right ?
    Thanks,
    Aju

  • Generate Client Proxy from a RPC-Style encoded WSDL

    Hi Experts,
    I was just trying to consume a RPC-Style encoded WSDL,
    but the creation of the client proxy failed with the following error message:
    Exception occurred in library handler     
    Incorrect value: Unknown Namespace http://schemas.xmlsoap.org/soap/encoding/     
    Does anyone know, if it's possible to consume a RPC-Style encoded Web Service?
    Thanks in advance!

    Hi Sandeep,
    Could you try invoking clientgen [1] directly to see if this properly
    consumes your WSDL?
    Thanks,
    Bruce
    [1]
    http://e-docs.bea.com/wls/docs81/webserv/anttasks.html#1080160
    Sandeep wrote:
    >
    Hi,
    I am using Weblogic 8.1 SP1. I created a webservice which takes a XMLBean object
    as parameter and returns another XMLBean object. The web service works fine when
    tested using the workshop's test browser but when i am trying to generate a client
    proxy trough the workshop's test browser, it displays this warning:
    Failed to generate client proxy from WSDL definition for this service
    and does not generate the proxy.
    I'll appreciate any thoughts on this.
    Thanks
    Sandeep

  • How do I import music from a flash drive that was formatted with a windows PC to my MacBook?

    How do I import music from a flash drive that was formatted with a windows PC to my MacBook - the drive is showing it has over 3GB of info on it but none of the files are showing up in finder?  I had backed up my iTunes library on the flash drive about a year and a half ago before I switched from a dell to a MacBook pro.

    What I found works for me is to make sure iTunes keeps the music files organzied in the iTunes Media folder according to album, artists, etc. and that it copies the music files there when adding them to the library.  That way, if something happens to the library, the raw files can always be re-imported again.

  • Best Practice for WSDL Generate Proxy Class for Web Service with Two Versions

    Dear All
    Thank you in advance for you help.
    I would like to generate proxy classes for same function but with two versions.
    Old version web service (v23.2) is used for stable modules in a project which is not going to modify.
    However, enhancement is added in new version web service (v24) and is going to use in any future modules.
    For example,
    wsdl.exe -o="TestProxy.cs" -l:CS -n:Test -sharetypes https://community.workday.com/custom/developer/API/Notification/v23.2/Notification.wsdl https://community.workday.com/custom/developer/API/Notification/v24.0/Notification.wsdl
    It generates similar classes with an '1' added at the end of the class name.
    ublic partial class Event_TargetObjectType {
    private Event_TargetObjectIDType[] idField;
    public partial class Event_TargetObjectType1 {
    private Event_TargetObjectIDType1[] idField; ...}
    Since the function inside some class is the same, is it possible for WSDL.exe to generate proxy classes automatically that if the class is the same, then generate one class only (sameFunction())  but if it detects the class is different, then add '1'
    to the end of class name (differentFunction() and differentFunction1())
    i.e.
    public class sameFunction()
    public class differentFunction()
    private int a;}
    public class differentFunction1()
    { private int b;
    Best Regards
    mintssoul

    Hi  mintssoul,
      As per this case, I have shared corresponding details below :
    1.As far as I know, WCF doesn’t support method overloading directly
    2.Because WSDL doesn’t support method overloading (not OOPs).
    3.WCF generates WSDL which specifies the location of the service and the operation or methods the service exposes.
    4.WCF use Document/Literal WSDL Style : Microsoft proposed this standard where the soap body element will contain the web method name.
    5.By default all the WCF services conform to the document literal standard where the soap body should include the method name.
    6.but you can differ the method in the same manually by using Name attribute like below 
    For example:
        [OperationContract(Name="Integers")]
        int Display(int a,int b)
        [OperationContract(Name="Doubles")]
    double Display(double a,double b)
    7. Or I suggest you that can use svcutil to map multiple namespaces for generating wcf service proxies .
        for more information about this, refer here :
    http://stackoverflow.com/questions/1103686/use-svcutil-to-map-multiple-namespaces-for-generating-wcf-service-proxies

  • Data import for users of forms created with Livecycle Designer

    Hello,
    I have seen several posts regarding data import for forms created by Livecycle Designer but nothing that helps with something I am trying to accomplish.  I can create a data connection and import information in a form but what I would like to do is import data, then send the pdf for completion to a user.  There are a few data elements that I have available and the rest of the information comes from from the user.  The problem I run into is once I create a data connection, the pdf is ALWAYS looking for the source file for that data.  I simply want to prepopulate some fields and send to the various users for completion.  Any help would be greatly appreciated.
    Thanks!

    Which type of Data Connection are you trying to create?
    XML Schema, Sample Data File or WSDL?
    Creating any one of first two types(mentioned above) will only create schema and will never import any data into PDF.
    If you create the WSDL connection, you can surely import data (i.e. prepopulate data) into your PDF and forward it for users review/fill.
    If I misunderstood your question, please get me clarified.
    Nith

  • PI 7.1: Importing a wsdl file with references to other xsd files

    Hi Experts,
    I am trying to import a wsdl file that has got references to other xsd files. When i do this with SOAP UI, i can get the full message structure for the other xsd files. But when i try to import the same wsdl in the ESR, i only get to the messages and not the referenced xsd.
    Any ideas!
    Thank you in Advance,
    Danny

    Hi,
    First convert your main WSDL in to XSD,use Stylus or any XML editors to convert the same,thecn check the genarated XSD refering sun XSD tsrutures.then zip the all xsd in to one File and import in PI,then select you main xsd in the folder,and select root element.
    Normally withour converting in to XSD only if you group al import it in to PI,it wil work.
    or
    if you have some good knowledge about XSD then convert WSDL in to XSD and remove referece tags and include XSD content of sub xsds in to main XSD,and validate that one,and imnprt one XSD.
    Regards,
    Raj

  • Import Format with Invalid Character

    I have accidentally created an Import format with an & which is bad character for FDM. It let me create the import format but now I am recieving a page error everytime I try to access the Import Format screen. This is preventing me from deleting the problematic import format. I have tried to export the import formats, delete the bad one from the xml file and re-import but this did not work.
    Any idea of how to delete this import format?

    You'll have to fix this through the database. Below are some SQL commands that will work in SQL Server.... Oracle is probably the same idea, but I won't claim those work in PL/SQL as I don't focus on it....
    If it's in the Import Format details, you should find it by executing the following SQL :
    Safe way (just to double check what you are going to change)
    select * from tBhvImpItemfile where ImpfldFixedtext like ('%&%')
    Update tBhvImpItemfile set ImpFldFixedText = 'new text here' where ImpSeq = <number(s) returned from first query>
    You know what you're doing and don't want to see what records you might impact first
    update tbhvImpItemfile set ImpFldFixedText = replace(ImpFldFixedText, '&', '-') where ImpFldFixedText like ('%&%')
    If the & is in the Import Format (Name, Description, etc), then you would apply the same idea, but look at the table tBhvImpGroup and most likely the fields ImpGroupKey / ImpGroupDesc......

Maybe you are looking for