Marketplace adapter (receiver) - DDID issue

Hey guys!
We are trying to configure the Marketplace adapter in XI to act as a receiver communication channel.
Our scenario is like this:
SRM (Purchase Order)  >  XI  >  MarketSite (Purchase Order)
It seems as if we need to define the DDIDs (Document Destination IDs) for the various suppliers (receivers) as well as the buyer (sender); however, the only place we know where to define the DDID (Service > Adapter-specific identifiers...) only allows for one DDID to be specified.
Have any of you guys configured the Marketsite adapter (Receiver) before? If so, could you show us how to manage the DDID issue?
Also, we have been using the SAP business connector to send the PO from SRM to MarketSite but we plan to replace it with SAP XI. Should we consider using the business connector adapter in XI? If so, where do we define the DDIDs?
Thanks in advance!
Glenn
ps. as usual, points guaranteed for helpful answers!:)

hi,
>>>>If so, could you show us how to manage the DDID issue?
put the DDID number in DDID field of adapter specific identifiers
where?
- open your business system/service
- service from menu 
- adapter specific identifiers
- DDID field
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Similar Messages

  • Marketplace adapter Multiple DDID Issue

    We have two customers whom we have to send messages to. Both of them use marketplace adapters and they would want our R/3 system to send the messages with 2 different DDIDs. Is this possible?
    I checked the option of using party to differentiate our R/3 system according to the party to add two different IDs to the R/3 business system, but since our R/3 system is a LS system, the message does not get detected as if it is coming from a party.
    Has anybody faced this issue? How have you solved this situation.
    Thanks for your replies!

    hi,
    >>>>If so, could you show us how to manage the DDID issue?
    put the DDID number in DDID field of adapter specific identifiers
    where?
    - open your business system/service
    - service from menu 
    - adapter specific identifiers
    - DDID field
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • Issue about IDoc Adapter Receiver Channel's Performance

    Hi Everyone,
    Currently, I am working on a scenario of File -Integration Process - IDoc in XI 3.0 with patch level 16. The scenario works fine when it process one/two/three files in parallel, and the IDocs arrive R/3 system quite fast. But when I try four files in parallel, the whole XI server blocks, I can not do anything even logon Integration Builder, and the IDocs arrive R/3 brokenly, sometime with the invterval to 10 minutes. When the XI comes back, I found all the four integration processes finish successfully and each transaction works fine and fast. What's more, after I change the IDoc Adapter receiver channel to a File Adapter receiver channel, it works fine for even 20 files in parallel. So I think it is some issue about IDoc Adapter receiver channel. Does anyone have the same experience as me? Any comments will be appreciate.
    Regards,
    Nick

    Hi Nick,
    Can you check this Blog-
    /people/sreekanth.babu2/blog/2005/01/05/delayed-xi-message-processing
    May be useful.
    How are you picking the files .. You can try with EOIO options while picking the file.
    But if you use BPM, it is not applicable. It will act as a EO only.
    Check this SAP Note- 833740
    Thanks,
    Moorthy

  • Marketplace adapter issue and question

    Our scenario :
    MarketPlace > XI MML Adapter
    We have the following error :
    No sender agreement configured in the XI Integration Directory for the given message header: SenderParty=OUR_PARTY; ReceiverParty=; SenderService=SERV_MarketplacePartner; ReceiverService=QALCLNT310; Interface=Order; InterfaceNamespace=urn:x-commerceone:document:com:commerceone:XCBL30:XCBL30.sox
    We have used interface with specific names :
    MIOA_Xcbl30PurchaseOrder (namespace : http://my_www.com/xi/B2B/Marketplace)
    So the sender agreement that exist does not use the same interface name and namespace !
    Is it a way to tell the marketplace adapter to use right interface and namespace names ?
    Or I must re-create my interface objects with standard name Order under a standard namespace ???
    Thanks a lot all

    You have to include your interface in the business service and then create the sender agreement.
    As according to error the intreface taken is order instead of your interface.

  • Configuring Marketplace Adapter

    Hello,
    We want to configure Receiver Marketplace adapter.
    The scenario is to send messages to Marketplace from XI.
    Is there any specific structure in which messages are to be sent?
    also from where could we find DDID value to be specified in adapter specific specifiers?
    Thanks

    prasad,
    check this
    http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/1a/ef487f5b680f4c84d632cfe76ec8cb/content.htm
    go thorugh this threads
    Target Address for "Marketplace-Adapter" on Marketplace
    Problem with Marketplace Adapter
    Market Place Adapter

  • Marketplace Adapter and SonicMQ

    Hi experts,
    I’m trying to configure the XI Marketplace Adapter (MPA) to send JMS messages to a SonicMQ Broker. The only specific SonicMQ configuration requested is the JMS Outbound Queue. I could not figure out how the adapter knows the location/port of the Broker acceptor, username and password, for example. These parameters are not explicit on the adapter configuration. I could not find any useful documentation about this. Can anyone point me any documentation or how can I make this kind of configuration?
    Thanks in advance!
    Best regards,
    Renato Kalman

    Hi,
    First of all, thanks for your answers! But you all mentioned JMS adapter, which I already got to work but it doesn’t solve my problem. Let me see if I can make it clearer.
    I’m working on a project that consists on migrating from a SAP/Commerce One Marketplace EAI solution to a mySAP SRM 5.0 solution, which uses SAP XI as the integration layer. Components from both solutions will coexist during this migration, including SAP XI, SAP Business Connector (BC) and SonicMQ. For this to work, I need to be able to configure XI send and receive messages to SonicMQ in MML format, which is the message format BC expects. That’s why the JMS Adapter doesn’t solve my issue. I read that Marketplace adapter would do exactly what I want but I cannot figure out how to configure it to use the JMS protocol because the only explicit configuration is the Outbound queue.
    Thanks again!
    Best regards,
    Renato Kalman

  • Getting Receiver Agreement issue in IDOC to File scenario

    Hi Gurus,
                Need your help. I'm working on a IDOC to File scenario. I'm using CREMDM.CREMDM04 as outbound Interface & small structure VEND_FILE_IN_MI as Inbound Interface. Though I've configured the receiver Communication Channel as a File Adapter with proper Inbound Interface I'm seeing the message getting failed which is showing CREMDM.CREMDM04 as both Outbound & Inbound interface and pointing a Receiver Agreement issue . The Receiver service is coming Properly, only the Interface is coming wrong as the sender interface. I've checked both Receiver Agreement & Receiver determination and found the Receiver Service, Communication Channel & Interface are perfectly mapped there, I cross checked the same Configurations in IE via SXI_CACHE after full Cache copy.
    Error Message:
    No receiver agreement found for sender -SAPERP to receiver -IDOC2FileReceiver,urn:sap-com:document:sap:idoc:messages
    Error  Category : Outbounding
    Error ID : CO_TXT_OUTBINDING_NOT_FOUND
    My IR design:
    Sender:
          Interface : VEND_IDOC_OUT_MI
          Message Type : CREMDM.CREMDM04
    Receiver:
          Interface : VEND_FILE_IN_MI
         Message Type : VEND_IN_MT , Data Type VEND_FILE_DT
    My ID Config:
    1. Sender / Outbound  Message:  Service Type --> Business System
                                                  Service  ---> SAPERP
                                                 Interface--> VEND_IDOC_OUT_MI
                                                 Adapter Type : IDOC
    2. Receiver / Inbound Message: Service Type --> Business Service
                                               Service       --> IDOC2FileReceiver
                                               Interface    ---> VEND_FILE_IN_MI
                                               Adapter Type--> File
    3. In Sender Agreement : Specified the Sender Communication Channel
                                         VEND_IDOC_OUT_Channel
    4. In Receiver Agreement Configured the receiver service IDOC2FileReceiver aging sender service SAPERP & Interface VEND_IDOC_OUT_MI.
    5. In Interface Determination Specified the Inbound Interface VEND_FILE_IN_MI and Interface Mapping VEND_IDOC_FILE_IMAP
    6. In Receiver Agreement specified the receiver communication Channel IDOC2FileChannel against Receiver Service & Interface.
    I used the Configuration wizard in my second attempt to make sure the sequence of configuration.
    Can anyone help me identifying what's going wrong. I'm very new to XI and basically this  is the first assignment I'm working on.
      Regards,
    Subhadip

    Hi Babu,
               In the Inbound data type all the fields have MinOccurance = 0 and MaxOccurances unbounded.
    Please find the XSD:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://adc.com/poc/sample" targetNamespace="http://adc.com/poc/sample">
         <xsd:complexType name="VEND_FILE_DT">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   8f584d80456311dccd680018fe79f69b
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="VENDCODE" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             a8653cb0390c11dc843000188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Vendor Code
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="VENDNAME1" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             a8653cb4390c11dc84e800188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Vendor name4
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="ORT01" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             a8653cb5390c11dcbe3400188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Vendor City
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="PFACH" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             a8653cb6390c11dc896100188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Vendor PO Box
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="STRAS" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             4811db0335fd11dc9e9600188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Vendor House No &amp; Street
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="PSTLZ" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             4811db0435fd11dc98b000188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Vendor Postal Code
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="LAND1" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             4811db0535fd11dc870500188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Vendor Country
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="STCD1" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7ca8d600403b11dcc9bd00188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Tax Number 1
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="TELF1" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             9abaee7040e611dcce4300188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Telephone number
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="STCEG" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             9abaee7140e611dc8f3900188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             VAT Registration Number
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="LIFNR" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             9abaee7240e611dccef700188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Account Number of Vendor or Creditor
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="ALTKN" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             9abaee7340e611dcb3bc00188bd09370
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
              </xsd:sequence>
         </xsd:complexType>
    </xsd:schema>

  • File adapter receiver channel is not initialized.

    Hi
    iam wrking idoc-file scenario, as per the requirement i have created 4datatypes  4 mapping in IR with 4 communaction chanles in ID. the scenarios is working fine with 3 mappings.but in 4 the scenario
    the file genaraing properly , i have cheked in SXMB_moni payload but it is not creating in destination system
    in runtimeworkbench->message-monitaring-> adpater
    i have find the below issues
    1) File adapter receiver channel CC_DDPWCS_US_TO_101 is not initialized. Unable to proceed: null  Error 2) Exception caught by adapter framework: File Adapter configuration not initialized:
    3) Error Delivery of the message to the application using connection AFW failed, due to: File Adapter configuration not initialized:.
    please tell me how can i reslove the issue
    thanks
    niru

    Hi
    i have checked the content convertion and changed as below
    the structure is
    Row.fieldNamesTrans_Id,Order,Item,Product_Id,Product_desc,Lot_nr,Ship_via,Exp_qty,Carousel_loc,compart,Destination,Label
    Row.fieldSeparator     ,
    Row.fieldFixedType     char
    Row.endSeparator     'nl'
    Row.addHeaderLine     4
    Row.headerlineTrans_Id,Order,Item,Product_Id,Product_desc,Lot_nr,Ship_via,Exp_qty,Carousel_loc,compart,Destination,Label
    even though iam facing the issue. iam wondering  "_i have used in the similar structure for other 3 mappings in same scenario those are working perfect "_ but based on condition if 4 th mapping is executed iam facing the problem
    error message in RWB/Adapeters
    File adapter receiver channel CC_DDPWCS_US_TO_101 is not initialized. Unable to proceed: null
    Error Exception caught by adapter framework: File Adapter configuration not initialized:
    Error Delivery of the message to the application using connection AFW failed, due to: File Adapter configuration not initialized:.
    please help if any of you face the similar situation , i struck-up long ago here
    regards
    niru

  • RFC -- XI t-- MarketPlace adapter

    Hello,
    I want to know is it possible to connect
    RFC >XI>Marketplace Adapter.
    My requirement is :
    From R/3  RFC i will send System component Number to XI , from XI i need to connect to
    SAP-Service market place https://websmp205.sap-ag.de/~SAPIDP/002006825000000234912001E
    by giving Userid and password and get the reponse back in XI as latest Support package availabe for that given component..
    So my Sender is RFC Adpater and receiver is Marketplace Adapter also i need to get back the response from Service market place and have to send back to R/3.
    How to do it??
    Also if it is possible ,In IR part what should be my Target message type?
    Regards,
    Mayank

    It would be easier for you to use HTTP adapter to post the request and get the response.
    For understanding Marketplace, have you seen my article?
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/20df1696-b87a-2a10-74a6-91949c0c752b
    Regards,
    Prateek

  • SAP Marketplace Adapter

    I apologize if this is not the correct forum for this, but all I'm trying to find out is whether the SAP Marketplace Adapter (when used with PI) is able to output xCBL 3.5 and/or 3.0 documents inside MML envelopes, as well as receive and consume xCBL documents inside MML.

    Hi,
      The Marketplace Adapter sends MML document. The content of this MML are made through mapping programs, for instance, if you have a purchase scenario like this: SAP MM -> PI -> Marketplace, you could send an ORDER Idoc to SAP PI, SAP PI make the IDOC transformation to xCbl 3.5 and finally you send this data to marketplace through Marketplace Adapter (MML Format).
       The receiver scenario can use xCbl structure as well.
       The marketplace adapter only create the MML document.
       SAP Business Connector was a better tool for Marketplace communication than SAP PI.
    Regards
    Ivá

  • Marketplace Adapter, how to set recipient IDu00B4s for vendors

    Dear SDN Community,
    currently we use SAP BusinesswConnector/MarketSet Connector for Marketplace communication and have plans to migrate to SAP XI/Marketplace Adapter. I cannot find any place in the Marketplace Adapter where to put the recipient ID´s (MPID) for our vendors.
    XI allows to define only one DDID per each service, but to create per each vendor a service makes no sense.
    Is there a way to put the MPID or DDID dynamically during runtime into the MML header ?
    Any hints ot ideas are appreciated.
    Thanks and regards,
    Holger Baumann

    Hi Holger,
    >>>>>>>Do I have to setup one partner or per each vendor/MPID a partner ?
    Yes.
    >>>>>>>Which values do I have to put in the fields agency, schema and name in idenfifiers tab ?
    In case of Vendor Number for R/3, you have to specify the fields as shown below.
    Agency: BS_SR5( Business System for backend R/3)
    Schema: ALE#<Partner type>#<Partner function>(For example:ALE#LI#LF>
    Name: 0001004000(Vendor Number in the Backend R/3)
    Hope this helps.
    Regards,
    Sam Raju

  • OCEP JMS Adapter implement InboundMessageConverter issue

    Hello,
    I'm new to OCEP. I have a JMS adapter receiving Weblogic JMS message. JMS Message is a TextMessage, so the default MapMessage can't convert it. I need to write my own converter which implement InboundMessageConvert. Eclipse compiles just fine, but when deploying into a runtime OCEP environment, I get an error saying that my custom converter class does not implement InboundMessageConverter which I did. Did anyone encounter this issue and how to get around it?
    I also tried the sample code provided in Developer Guide and it doesn't work. My code bellow is a sample to by pass the deployment issue..
    package com.converter;
    import com.bea.wlevs.adapters.jms.api.InboundMessageConverter;
    import com.bea.wlevs.adapters.jms.api.MessageConverterException;
    import javax.jms.JMSException;
    import javax.jms.Message;
    import java.util.List;
    public class MyMessageConverter
    implements InboundMessageConverter
    public MyMessageConverter(){
    super();
    public List convert(Message message) throws MessageConverterException, JMSException
    return null;
    --- error message when deploy to runtime environment ---
    <Mar 22, 2010 10:30:57 AM PDT> <Error> <Deployment> <BEA-2045010> <The application context "FilteringEvent" could not be started: org.springframework.beans.FatalBeanException: Error in context lifecycle initialization; nested exception is java.lang.IllegalArgumentException: converter-bean com.converter.MyMessageConverter does not implement InboundMessageConverter
    org.springframework.beans.FatalBeanException: Error in context lifecycle initialization; nested exception is java.lang.IllegalArgumentException: converter-bean com.converter.MyMessageConverter does not implement InboundMessageConverter
    at com.bea.wlevs.spring.ApplicationContextLifecycle.onApplicationEvent(ApplicationContextLifecycle.java:136)
    at org.springframework.context.event.SimpleApplicationEventMulticaster$1.run(SimpleApplicationEventMulticaster.java:78)
    at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49)
    at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:76)
    at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:274)
    at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:736)
    at org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext.finishRefresh(AbstractOsgiBundleApplicationContext.java:235)
    at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:358)
    at org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
    at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:320)
    at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:136)
    at org.springframework.scheduling.commonj.DelegatingWork.run(DelegatingWork.java:61)
    at weblogic.work.commonj.CommonjWorkManagerImpl$WorkWithListener.run(CommonjWorkManagerImpl.java:196)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

    Hi,
    I have included the following two lines into the Manifest file, but this action has not fixed the problem:
    com.bea.wlevs.adapters.jms;version="11.1.1.4_0",
    com.bea.wlevs.adapters.jms.api;version="11.1.1.4_0"
    My EPN file is as shown:
    <?xml version="1.0" encoding="UTF-8"?>
    <beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:osgi="http://www.springframework.org/schema/osgi"
    xmlns:wlevs="http://www.bea.com/ns/wlevs/spring"
    xmlns:jdbc="http://www.oracle.com/ns/ocep/jdbc"
    xmlns:spatial="http://www.oracle.com/ns/ocep/spatial"
    xmlns:application="http://www.bea.com/ns/wlevs/config/application"
    xsi:schemaLocation="
    http://www.springframework.org/schema/beans
    http://www.springframework.org/schema/beans/spring-beans.xsd
    http://www.springframework.org/schema/osgi
    http://www.springframework.org/schema/osgi/spring-osgi.xsd
    http://www.bea.com/ns/wlevs/spring
    http://www.bea.com/ns/wlevs/spring/spring-wlevs-v11_1_1_3.xsd
    http://www.oracle.com/ns/ocep/jdbc
    http://www.oracle.com/ns/ocep/jdbc/ocep-jdbc.xsd
    http://www.oracle.com/ns/ocep/spatial
    http://www.oracle.com/ns/ocep/spatial/ocep-spatial.xsd
    http://www.bea.com/ns/wlevs/config/application
    http://www.bea.com/ns/wlevs/config/application/wlevs_application_config.xsd">
         <bean id="myConverter" class="com.bea.wlevs.adapter.example.jmsclient.JMSClient"/>
         <wlevs:adapter id="jmsInbound" provider="jms-inbound">
              <wlevs:instance-property name="converterBean" ref="myConverter"/>
         </wlevs:adapter>
         <application:jms-adapter>
    <application:name>jmsInbound</application:name>
    <application:jndi-provider-url>t3://localhost:9002</application:jndi-provider-url>
    <application:destination-jndi-name>Queue1</application:destination-jndi-name>
    <application:user>wlevs</application:user>
    <application:password>123456</application:password>
    <application:work-manager>JettyWorkManager</application:work-manager>
    <application:concurrent-consumers>1</application:concurrent-consumers>
    <application:session-transacted>false</application:session-transacted>
    </application:jms-adapter>
    <wlevs:event-type-repository>
    The error showned by Eclipse is:
    Multiple annotations found at this line:
         - cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'application:jms-adapter'.
         - schema_reference.4: Failed to read schema document 'http://www.bea.com/ns/wlevs/config/application/
         wlevs_application_config.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the
         document is not <xsd:schema>.
    Thanks!
    Edited by: 899693 on 15-dic-2011 2:48

  • Problem with Marketplace Adapter

    Hi,
    when we send an ORDER-document from marketplace to xi over marketplace-adapter, we get the following error:
    <i>Couldn't retrieve inbound binding for the given P/S/A values:FP=XYZ;TP=;FS=EDC_200;TS=AV4_200;AN=ORDER;ANS=;</i>
    We have a party "XYZ" with the service "EDC_200" and we have a service "AV4_200" without party and a service "ORDER".
    Does anyone know why this error-message appears and how we can solve this problem?
    Regards
    Thorsten

    Hi Sam,
    here the entries we have used for our SA:
    Sender:
    Paty: XYZ
    Service: EDC_200
    Interface: ORDER
    Namespace: http://test.com/xi/pc1
    Receiver:
    Party:
    Service: AV4_200
    sender Communication Channel: Marketplace_Sender
    Here the configuration of the communication channel:
    Party: XYZ
    Service: EDC_200
    Transport-Protocol: HTTP
    Message-Protocol: MML
    Regards,
    Thorsten

  • Material stock received and issued for a given period of time

    HOW to get the material stock received and issued for a given period of time including the open orders.
    if there is any BAPI Available then please tell me. or give me the table relations thaks.
    thanks inadvance

    hi friend,
    Why don't you try using a TIMER. Try using this code
    Timer timer = new Timer((TIMER), new ActionListener()
         public void actionPerformed(ActionEvent ae)
    // perform your task here...
    timer.setInitialDelay(TIMER);
    timer.setRepeats(true);
    timer.start();
    I think this will work fine.
    Bye,
    Ravi.

  • Unable to clone File Adapter receiver channel for parallel processing

    Hi Experts,
    I am using variable substitution for File - RFC - File with out BPM scenario(using request response, oneway bean).
    While i placed the file in the sender FTP folder, the file didnt get picked up, but in communication channel monitoring, i am getting error ' Unable to clone File Adapter receiver channel for parallel processing'.
    Can anybody provide me suggestions to solve this error.
    Note : without variable substitution , the interface is working good.
    Is it due to, i am trying the source structure field in response file adapter?

    Hi,
    In your CC, do you use some additional paramaters ?
    like these one of point 47/48 of [Oss note 821267 - FAQ: XI 3.0 / PI 7.0/ PI 7.1 File Adapter|https://service.sap.com/sap/support/notes/821267]
    Maybe there is conflict with a parallel connexion and the bean used to do asynch-synch bridge...
    Mickael

Maybe you are looking for

  • Generating pdf from scanner

    generating pdf from scanner hp G3010: old windows xp file weight 40-50 K. Macbook pro with new mac os 10.7.2 minimum file weight 1,9 Mbyte with terrible resolution!!!! and no way to reduce. Nice change?

  • Null Pointer Exception

    Hi , We are using SO_DOCUMENT_SEND_API1 this BAPI to send mails in our application.Here we are passing values to the input parameters  SENDER_ADDRESS,SENDER_ADDRESS_TYPE,COMMIT_WORK . and we need to pass values to the tables also.one table name in th

  • Stateful Session Bean accesed by two JSPs.

    Hi there, We are having quite an issue; we have an application that stores session state in an stateful session bean. And we have noticed some parts of the application create a situation where is possible that two frames -and so two jsp- access the s

  • Regarding date format changes

    Hi All, I have a date variable. Th date variable is v_doc_date which is declared like SY-DATUM. I will get value into that variable in format <b>DDMMYYYY</b> EX: <b>18072005</b> now i want make that variable as <b>18.07.2005</b> through Function modu

  • LCM utility taking more time to start

    Hi All, In Hyperion System 9.3.1 when running the LCMUtility.bat file in Hyperion Home\BIPLUS\bin folder it is taking nearly 8-10 minutes to start up the process. The shared services, IR, Core services are in the single box. Even though it is taking