Assignment of components to more than one operation in routing.

Hi to all,
I am trying to allocate components of material BoM to more than one operation in routing. I know one way to do it is to define that components again & agin in material BoM & assigned them to operations in routing. Are other ways available to do the same.
Thanks & regards,
Abu Arbab

Dear,
Now I am clear.
You need to create different 2 BOM and with BOM items, as below,
example - total requirement of material A is say 10.
Semi finished Product- X BOM
BOM item 1 - material A-qty 8
BOM item 2 - material B-qty -5
Finished material Y - BOM
BOM item 1 - semifished material X-qty 10
BOM item 2 - material C-qty 10
BOM item 3 - material A-qty 2
BOM item 4 - material D-qty -2
You need to create above 2 BOM's if you want to see semifished product into inventory, if not proceed as below
Finished material Y - BOM
BOM item 1 - material A-qty 8 assign it to routing operation 10
BOM item 2 - material B-qty -5 assign it to routing operation 10
BOM item 2 - material C-qty 10 assign it to routing operation 20
BOM item 3 - material A-qty 2 assign it to routing operation 30
BOM item 4 - material D-qty -2 assign it to routing operation 30
I think this is the only way you can map it.

Similar Messages

  • More than one operation defined. Unable to resolve operation

    Hi,
    Using the attached WSDL to define a BPEL sequence I allways get the following error message:
    More than one operation defined. Unable to resolve operation:
    This occured in the moment i introduced a seconde operation. With one operation everything works fine.
    Does anybody know how to define a WSDL that works for the BPEL system with more than one operation?
    Best Regards,
    Axel.
    WSDL:
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://dummy.ws.axelbenz.de/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" targetNamespace="http://dummy.ws.axelbenz.de/" name="StringInOutService" xmlns:plink="http://schemas.xmlsoap.org/ws/2004/03/partner-link/">
    <types>
    <xsd:schema>
    <xsd:import namespace="http://dummy.ws.axelbenz.de/" schemaLocation="upperService.xsd" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" />
    </xsd:schema>
    </types>
    <message name="lowerMessage">
    <part name="lowerParameters" type="tns:lowerType" />
    </message>
    <message name="lowerMessageResponse">
    <part name="lowerResponseParameters" type="tns:lowerTypeResponse" />
    </message>
    <message name="upperMessage">
    <part name="upperParameters" type="tns:upperType" />
    </message>
    <message name="upperMessageResponse">
    <part name="upperResponseParameters" type="tns:upperTypeResponse" />
    </message>
    <portType name="StringInOut">
    <operation name="lowerOperation">
    <input message="tns:lowerMessage" />
    <output message="tns:lowerMessageResponse" />
    </operation>
    <operation name="upperOperation">
    <input message="tns:upperMessage" />
    <output message="tns:upperMessageResponse" />
    </operation>
    </portType>
    <binding name="StringInOutPortBinding" type="tns:StringInOut">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
    <operation name="lowerOperation">
    <soap:operation soapAction="lower" style="document" />
    <input>
    <soap:body use="literal" parts="lowerParameters" />
    </input>
    <output>
    <soap:body use="literal" parts="lowerResponseParameters" />
    </output>
    </operation>
    <operation name="upperOperation">
    <soap:operation soapAction="upper" style="document" />
    <input>
    <soap:body use="literal" parts="upperParameters" namespace="" />
    </input>
    <output>
    <soap:body use="literal" parts="upperResponseParameters" />
    </output>
    </operation>
    </binding>
    <service name="StringInOutService">
    <port name="StringInOutPort" binding="tns:StringInOutPortBinding">
    <soap:address location="http://GWBE0040.int.gematik.de:18181/DummyServices/StringInOutService" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" />
    </port>
    </service>
    <plink:partnerLinkType name="partnerlinktype1">
    <plink:role name="serviceRequestor" portType="tns:StringInOut"/>
    </plink:partnerLinkType>
    </definitions>
    XSD:
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema version="1.0" targetNamespace="http://dummy.ws.axelbenz.de/" xmlns:xs="http://www.w3.org/2001/XMLSchema">
    <xs:element name="lower" type="ns1:lowerType" xmlns:ns1="http://dummy.ws.axelbenz.de/" />
    <xs:complexType name="lowerType">
    <xs:sequence>
    <xs:element name="inp" type="xs:string" minOccurs="0" />
    </xs:sequence>
    </xs:complexType>
    <xs:element name="lowerResponse" type="ns2:lowerTypeResponse" xmlns:ns2="http://dummy.ws.axelbenz.de/" />
    <xs:complexType name="lowerTypeResponse">
    <xs:sequence>
    <xs:element name="return" type="xs:string" minOccurs="0" />
    </xs:sequence>
    </xs:complexType>
    <xs:element name="upper" type="ns3:upperType" xmlns:ns3="http://dummy.ws.axelbenz.de/" />
    <xs:complexType name="upperType">
    <xs:sequence>
    <xs:element name="inp" type="xs:string" minOccurs="0" />
    </xs:sequence>
    </xs:complexType>
    <xs:element name="upperResponse" type="ns4:upperTypeResponse" xmlns:ns4="http://dummy.ws.axelbenz.de/" />
    <xs:complexType name="upperTypeResponse">
    <xs:sequence>
    <xs:element name="return" type="xs:string" minOccurs="0" />
    </xs:sequence>
    </xs:complexType>
    </xs:schema>

    What client are you using? Are you using the netbeans enterprise pack test driver? If so, you can set the soap action in the test properties to match the ones you have defined in the WSDL.
    Also if you could post the actual soap message you are sending that would help.
    I also noticed that you're using parts defined via types with a document/literal binding. To be more basic profile compliant in that casue you may want to use RPC style instead - it is not strictly necessary, but increases interoperability.
    Andi

  • Service interface with more than one operation

    Hi all,
    is it possible to have a service interface with more than one operation?
    I have found this blog:
    http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3414900)ID0209118050DB10459657028039341762End?blog=/pub/wlg/15123
    But this sentence:
    ABAP proxy (inbound/ outbound) cannot be developed out of a Service Interface having Operations with different type of messages included. If an ABAP proxy is to be developed then all the messages included should be of one type i.e. either the included messages should be Message Type, External Message, IDOC or RFC Message. This behavior can be observed when a Service Interface is created and then subjected for a check
    regards

    Hi,
    now the interface is running but I get another error in .NET.
    "The header 'Diagnostic' from the namespace 'http://sap.com/xi/XI/Message/30' was not understood by the recipient of this message, causing the message to not be processed.  This error typically indicates that the sender of this message has enabled a communication protocol that the receiver cannot process.  Please ensure that the configuration of the client's binding is consistent with the service's binding. "
    Any ideas?
    regards

  • Publish more than one operation by WebService

    Hi all
    Somebody can helpme saying me how to do the following with eGate ( i cant use eInsight ):
    For now im enabled to publish one operation and one webservice, but mi problem is that i can't publish one WebService with more than one operation and i can't change the mandatory "ExecutePortType", all my webservices url are in the form:
    http://<server>:<port>/myws/ExecutePortType
    1. Why the context name is about the WebService and why ExecutePortType is mandatory ?
    2. I can't publish a Web Service with more than one operation ( The documentation says that the ExecutePortType supports just one operation )?
    some body can helpme with an example ?

    What client are you using? Are you using the netbeans enterprise pack test driver? If so, you can set the soap action in the test properties to match the ones you have defined in the WSDL.
    Also if you could post the actual soap message you are sending that would help.
    I also noticed that you're using parts defined via types with a document/literal binding. To be more basic profile compliant in that casue you may want to use RPC style instead - it is not strictly necessary, but increases interoperability.
    Andi

  • Javax.jbi.messaging.MessagingException: More than one operation defined

    Hi,
    i had already implemented a web service consisting of 6 methods that works fine. Now i want to access this service via JBI. Therefore i developed a service assembly containing only of a soap binding component. When i try to access the jbi environment via the inbound endpoint OpenESB throws following exception:
    [#|2006-07-26T16:23:50.531+0200|WARNING|sun-appserver-pe9.0|com.sun.jbi.component.com.sun.httpsoapbc-1.0-2com.sun.jbi.httpsoapbc.embedded.GrizzlyRequestProcessor|_ThreadID=32;_ThreadName=httpWorkerThread-12010-2;_RequestID=a33dbb24-d088-4a6a-9642-96187c32bb36;|Exception in processing request.
    javax.jbi.messaging.MessagingException: More than one operation defined. Unable to resolve operation: {http://service}UseRepositoryService,UseRepository,inbound
         at com.sun.jbi.httpsoapbc.InboundMessageProcessor.execute(InboundMessageProcessor.java:214)
         at com.sun.jbi.httpsoapbc.embedded.GrizzlyRequestProcessor.processAsynchRequest(GrizzlyRequestProcessor.java:214)
         at com.sun.jbi.httpsoapbc.embedded.GrizzlyRequestProcessor.service(GrizzlyRequestProcessor.java:173)
         at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
         at com.sun.jbi.httpsoapbc.embedded.JBIGrizzlyAsyncFilter.doFilter(JBIGrizzlyAsyncFilter.java:70)
         at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.invokeFilters(DefaultAsyncExecutor.java:143)
         at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.interrupt(DefaultAsyncExecutor.java:132)
         at com.sun.enterprise.web.connector.grizzly.async.AsyncProcessorTask.doTask(AsyncProcessorTask.java:81)
         at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
         at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
    How can i specify in my service assembly that if i send a SOAP request for method X on my client that OpenESB routes this message to the correct Outbound endpoint?
    Thank you
    Thomas

    Hello Andi,
    thanks for your reply. To exclude the soap action error i will post the complete wsdl file now. But in my opinion every operation has its own input and output definition.
    The consumer wsdl:
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions targetNamespace="http://service" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://service" xmlns:intf="http://service" xmlns:tns1="http://types" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <!--WSDL created by Apache Axis version: 1.2.1
    Built on Jun 14, 2005 (09:15:57 EDT)-->
    <wsdl:types>
    <schema elementFormDefault="qualified" targetNamespace="http://service" xmlns="http://www.w3.org/2001/XMLSchema">
    <import namespace="http://types"/>
    <element name="loadEcore">
    <complexType>
    <sequence>
    <element name="ecoreId" type="xsd:long"/>
    </sequence>a
    </complexType>
    </element>
    <element name="loadEcoreResponse">
    <complexType>
    <sequence>
    <element name="loadEcoreReturn" type="xsd:base64Binary"/>
    </sequence>
    </complexType>
    </element>
    <element name="loadInstance">
    <complexType>
    <sequence>
    <element name="instanceId" type="xsd:long"/>
    </sequence>
    </complexType>
    </element>
    <element name="loadInstanceResponse">
    <complexType>
    <sequence>
    <element name="loadInstanceReturn" type="xsd:base64Binary"/>
    </sequence>
    </complexType>
    </element>
    <element name="loadInstanceForProject">
    <complexType>
    <sequence>
    <element name="instanceId" type="xsd:long"/>
    </sequence>
    </complexType>
    </element>
    <element name="loadInstanceForProjectResponse">
    <complexType>
    <sequence>
    <element name="loadInstanceForProjectReturn" type="xsd:base64Binary"/>
    </sequence>
    </complexType>
    </element>
    <element name="deleteInstance">
    <complexType>
    <sequence>
    <element name="instanceId" type="xsd:long"/>
    </sequence>
    </complexType>
    </element>
    <element name="deleteInstanceResponse">
    <complexType>
    <sequence>
    <element name="deleteInstanceReturn" type="xsd:boolean"/>
    </sequence>
    </complexType>
    </element>
    <element name="getAllInstancesFromDB">
    <complexType/>
    </element>
    <element name="getAllInstancesFromDBResponse">
    <complexType>
    <sequence>
    <element maxOccurs="unbounded" name="getAllInstancesFromDBReturn" type="tns1:InstancePackageValueBean"/>
    </sequence>
    </complexType>
    </element>
    <element name="saveInstance">
    <complexType>
    <sequence>
    <element name="resourceBytes" type="xsd:base64Binary"/>
    <element name="fileName" type="xsd:string"/>
    </sequence>
    </complexType>
    </element>
    <element name="saveInstanceResponse">
    <complexType>
    <sequence>
    <element name="saveInstanceReturn" type="xsd:boolean"/>
    </sequence>
    </complexType>
    </element>
    </schema>
    <schema elementFormDefault="qualified" targetNamespace="http://types" xmlns="http://www.w3.org/2001/XMLSchema">
    <complexType name="InstancePackageValueBean">
    <sequence>
    <element name="ecoreId" type="xsd:long"/>
    <element name="fileName" nillable="true" type="xsd:string"/>
    <element name="id" type="xsd:long"/>
    <element name="name" nillable="true" type="xsd:string"/>
    <element name="usedModels" nillable="true" type="xsd:string"/>
    </sequence>
    </complexType>
    </schema>
    </wsdl:types>
    <wsdl:message name="loadEcoreRequest">
    <wsdl:part element="impl:loadEcore" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="loadEcoreResponse">
    <wsdl:part element="impl:loadEcoreResponse" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="saveInstanceResponse">
    <wsdl:part element="impl:saveInstanceResponse" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="loadInstanceForProjectResponse">
    <wsdl:part element="impl:loadInstanceForProjectResponse" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="loadInstanceResponse">
    <wsdl:part element="impl:loadInstanceResponse" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="getAllInstancesFromDBRequest">
    <wsdl:part element="impl:getAllInstancesFromDB" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="loadInstanceRequest">
    <wsdl:part element="impl:loadInstance" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="getAllInstancesFromDBResponse">
    <wsdl:part element="impl:getAllInstancesFromDBResponse" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="loadInstanceForProjectRequest">
    <wsdl:part element="impl:loadInstanceForProject" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="saveInstanceRequest">
    <wsdl:part element="impl:saveInstance" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="deleteInstanceRequest">
    <wsdl:part element="impl:deleteInstance" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="deleteInstanceResponse">
    <wsdl:part element="impl:deleteInstanceResponse" name="parameters"/>
    </wsdl:message>
    <wsdl:portType name="UseRepository">
    <wsdl:operation name="loadEcore">
    <wsdl:input message="impl:loadEcoreRequest" name="loadEcoreRequest"/>
    <wsdl:output message="impl:loadEcoreResponse" name="loadEcoreResponse"/>
    </wsdl:operation>
    <wsdl:operation name="loadInstance">
    <wsdl:input message="impl:loadInstanceRequest" name="loadInstanceRequest"/>
    <wsdl:output message="impl:loadInstanceResponse" name="loadInstanceResponse"/>
    </wsdl:operation>
    <wsdl:operation name="loadInstanceForProject">
    <wsdl:input message="impl:loadInstanceForProjectRequest" name="loadInstanceForProjectRequest"/>
    <wsdl:output message="impl:loadInstanceForProjectResponse" name="loadInstanceForProjectResponse"/>
    </wsdl:operation>
    <wsdl:operation name="deleteInstance">
    <wsdl:input message="impl:deleteInstanceRequest" name="deleteInstanceRequest"/>
    <wsdl:output message="impl:deleteInstanceResponse" name="deleteInstanceResponse"/>
    </wsdl:operation>
    <wsdl:operation name="getAllInstancesFromDB">
    <wsdl:input message="impl:getAllInstancesFromDBRequest" name="getAllInstancesFromDBRequest"/>
    <wsdl:output message="impl:getAllInstancesFromDBResponse" name="getAllInstancesFromDBResponse"/>
    </wsdl:operation>
    <wsdl:operation name="saveInstance">
    <wsdl:input message="impl:saveInstanceRequest" name="saveInstanceRequest"/>
    <wsdl:output message="impl:saveInstanceResponse" name="saveInstanceResponse"/>
    </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="UseRepositorySoapBinding" type="impl:UseRepository">
    <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <wsdl:operation name="loadEcore">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="loadEcoreRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="loadEcoreResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="loadInstance">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="loadInstanceRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="loadInstanceResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="loadInstanceForProject">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="loadInstanceForProjectRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="loadInstanceForProjectResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="deleteInstance">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="deleteInstanceRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="deleteInstanceResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="getAllInstancesFromDB">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="getAllInstancesFromDBRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="getAllInstancesFromDBResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="saveInstance">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="saveInstanceRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="saveInstanceResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="UseRepositoryService">
    <wsdl:port binding="impl:UseRepositorySoapBinding" name="UseRepository">
    <wsdlsoap:address location="http://localhost:12010/service/repository"/>
    </wsdl:port>
    </wsdl:service>
    </wsdl:definitions>
    Except for the service name, port, address etc the provider wsdl is the same.
    Could you tell me if it works when i will only use one operation for example?
    I had already implemented a service assembly which contained only one operation. That SA worked fine.
    If the Service Assembly and Binding Component descriptors had wrong references e.g. the wrong interface-name, would OpenESB throws an exception while deployment?
    In addition, could you tell me a good link to a nice bpel engine example? How is the interaction between client ans service using the bpel engine?
    I think using the SoapBC the interaction is following:
    Client --> BC --> Service
    With Bpel engine?
    Client --> BC --> bpel --> BC2 --> service?
    Thanks a lot
    Thomas

  • Assign purchase organization to more than one co codes??

    Hey gurus...
    Can somebody tell me to how can we assign same purchase organization to more than one company code?
    Ganesh.....

    You cannot assign one purchase organization to multiple company codes, but you can assign and use one purchase organization to multiple plants belongs to different company codes.
    This cross company code purchase organization is useful for better negotiations at corporate level. You can get header level discounts (applicable on total PO Value) across multiple company codes. If you use cross company code purchase organization, you cannot manually enter company code at header level in the PO. The company code is derived from the plant at GR level.

  • How to assign a iview to more than one page at a same time

    Hi Experts,
    I have created 40 pages. I have to assign ivews to these pages. One of the iviews is common to all the pages. Going to each page and assigning the iview to that page will take alot of time. Is there a way in which i can add an iview to more than one page at the same time?
    Thanks in advance,
    Prisford Pereira.

    Hi
    You can do that using XML Content and Actions.
    You can write XML in specified format and upload it to portal, that will automatically create the content for you in PCD. You can create iviews, pages, assign iviews to pages etc.
    More details are available at the how to guide.
    [http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/207a2141-c870-2910-e080-90c920b24f47|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/207a2141-c870-2910-e080-90c920b24f47]
    Hope this helps.
    Best regards,
    Ritesh Chopra

  • Can we assign cost center to more than one company code.

    Hi All,
    Can we  use same cost center for more than one company code to post the cost ? Or is it company code dependant?
    Thanks,
    Kumar

    Hi Kumar,
    Although the cost center is created under a controlling area, we cannot extend to more than once company code in that controlling area. The Co.code field in Cost Center Master data cannot allow you to feed more than one company code.
    But you can post some values from a company code other than the company code to which it is extended. In such case, inter company postings will trigger.
    Hope this will clarify your issue.
    Best Regards
    Surya

  • Web Service with more than one operation?

    Hey,
    a web service could contain 1..N operations. It is possible
    to define this with XI? Normally I took an outbound interface
    and create a web service, but this outbound interface defines
    the structure of the only operation of this web service, did it?
    Does SAP XI supports only a one-operation web service?
    thanks
    chris

    This is supported from PI 7.1 onwards.
    VJ

  • Handling WebService with more than one operation

    Hi Everybody,
    I have a hassle!
    First of All, I'm Newbie, using Oracle Service Bus
    I have to Implement a WS with aproximately 6 operations, in Service Bus.
    I create my WSD and my XSD Artifacts, with no problem, the issue comes when I try to create My Proxy Service in OSB
    Step 1 .- Create Proxy Service
    Step 2 .- I make a Link from my Proxy Service to my Business Service wich contains the WSDL with the 6 operations
    Step 3 .- I clic on edit the message flow in the actions panel to add route
    Step 4 .- I edit the route looking for a Webservice and selecting the method (In this Case I select one method, because I don't know how to route many operations in one Proxy Service)
    When I did that, my WS in OSB wasn't able to invoke one method. I got a timeout .. I don't know, if maybe I'm doing something wrong!!.
    What I want is a way to route many methods in a same Web Service
    I've done operational bifurcation in the Web Proxy.. With that component, I can choose methods like conditionals, and I can add a route destination for each method.. when I test it .. My OSB WS never reply me an asnwer, I got Timeout. Takes a lot of time
    I also tried to do it with IF ELSE conditionals trying to know the name of the method from the WLS Headers and routing them to a specific webservice method. But I couldn't do it!
    I check the WS out by itself and works in 2 seconds, so it's Working!
    Any clues?, Well I hope you can help me!!
    Thanks in Advance!
    Edited by: user11334562 on 05-ago-2011 17:38

    Pierluigi,
    Thanks for your answer,
    I had to rebuild my OSB project, and refact all my OSB artifacts,
    My Proxy Service, I was trying to do it with my WSDL again, when I already had done in a Business Service,
    So in my proxy I chose the BS instead WSDL and all Works Perfectly using SOAP Content.
    Pretty Thanks!!
    ABC

  • Undo/Redo button are not performing more than one operation at a time

    Hi,
    I have created undo/redo button on my paint application. But it performing only last action to undo.I have just the code which store offscreen image into undo buffer image like this :
        if (OSC == null || widthOfOSC != getSize().width || heightOfOSC != getSize().height) {
                     // Create the OSC, or make a new one if canvas size has changed.
                 OSC = null;  // (If OSC & undoBuffer already exist, this frees up the memory.)
                 undoBuffer = null;
                 OSC = createImage(getSize().width, getSize().height);
                 widthOfOSC = getSize().width;
                 heightOfOSC = getSize().height;
                 OSG = OSC.getGraphics();  // Graphics context for drawing to OSC.
                 OSG.setColor(getBackground());              
                 OSG.dispose();
                 undoBuffer = createImage(widthOfOSC, heightOfOSC);
                  OSG = undoBuffer.getGraphics();  // Graphics context for drawing to the undoBuffer.
                  OSG.setColor(getBackground());            
                  OSG.fillRect(0, 0,widthOfOSC, heightOfOSC);
                   and the button performed it's action :
    else if (command.equals("Undo")) {
                 // Swap the off-screen canvas with the undoBuffer and repaint.
                 Image temp = OSC;
                 OSC = undoBuffer;
                 undoBuffer = temp;
                 repaint();I want to create undo button that performed end operation on canvas.
    please help me
    Thanks in advance....

    Don't post the same question repeatedly. I've removed the thread you started 4 days after this one with the identical same question.
    db

  • Asset Master to be assigned to more than one WBS element

    Hi Guys
    I have a scenario in which a Asset should be assigned to more than one Project, i.e. WBS Element.
    Is it possible by any way to assign a asset to more than one WBS element.
    Warm Regards
    Bala

    Hi Vijay Kumar
    Your right, but my situation is different.
    Take an example, i have server in a software company, that will be used for more than one project. In this case the asset number is the same as the same asset is used for different project at a given point of time
    Warm Regards
    Bala

  • Notify more than 1 operator in a SQL Agent job

    Hi Forum,
    is there a way to notify more than one operator if a SQL Agent job fails?
    TIA
    Alex

    Hello Alex,
    If you are using a "maintenance plan" task "Notify operator" you can select several operators from a list.
    In a SQL Server Agent job itself you can only add several operator for "warnings", but for the notifications like "finished" just one.
    Olaf Helper ----------- * cogito ergo sum * errare humanum est * quote erat demonstrandum * Wenn ich denke, ist das ein Fehler und das beweise ich täglich http://olafhelper.over-blog.de

  • Automatic goods receipt for more than one phase

    Hi all,
    I want to make automatic goods receipt in the confirmation COR6N for more than one phase , i know that it is not possibe in the standard system but is ther any fuction module or note can support this issue?
    Regards
    Ahmed Sobhi

    Dear Ahmed Sobhi,
    If my understanding is correct,then it's not possible to perform Automatic GR for more than one operation or phase in standard
    SAP.
    Regards
    Mangalraj.S

  • RegionRenderer encodeAll The region component with id: pt1:r1 has detected a page fragment with multiple root components. Fragments with more than one root component may not display correctly in a region and may have a negative impact on performance.

    Hi,
    I am using JDEV 11.1.2.1.0
    I am getting the following error :-
    <RegionRenderer> <encodeAll> The region component with id: pt1:r1 has detected a page fragment with multiple root components. Fragments with more than one root component may not display correctly in a region and may have a negative impact on performance. It is recommended that you restructure the page fragment to have a single root component.
    Piece of code is for region is:-
       <f:facet name="second">
                                                <af:panelStretchLayout id="pa1"
                                                                       binding="#{backingBeanScope.Assign.pa1}">
                                                    <f:facet name="center">
                                                        <af:region value="#{bindings.tfdAssignGraph1.regionModel}" id="r1"
                                                                   binding="#{backingBeanScope.Assign.r1}"/>
                                                    </f:facet>
                                                </af:panelStretchLayout>
                                            </f:facet>
    How do I resolve it ?
    Thanks,

    Hi,
    I see at least 3 errors
    1. <RegionRenderer> <encodeAll> The region component with id: pt1:r1 has detected a page fragment with multiple root components.
    the page fragment should only have a single component under the jsp:root tag. If you see more than one, wrap them in e.g. an af:panelGroupLayout or af:group component
    2. SAPFunction.jspx/.xml" has an invalid character ".".
    check the document (you can open it in JDeveloper if the customization was a seeded one. Seems that editing this file smething has gone bad
    3. The expression "#{bindings..regionModel}" (that was specified for the RegionModel "value" attribute of the region component with id "pePanel") evaluated to null.
    "pageeditorpanel" does seem to be missing in the PageDef file of the page holding the region
    Frank

Maybe you are looking for