A problem about IDOC Receiver

Hi, everybody.
This time, I'm developing a IDOC Receiver though the SAPIDocReceiver class. With the dotnet Connector manual from SAP, the receiver side on dotnet is easy to develop. But how to configure the SAP R/3 to send IDOC to the dotnet side, I can't find the clear steps in the manual.
So I searched some material about how to configure IDOC, and hope it will be useful to my work. But most of them mainly focus on how to configure a IDOC transformation between SAP system but not NON-SAP system.
So what I want to ask is IS there some difference with the two configuration, I mean the SAP to SAP one and the SAP to NON-SAP one. I guess the difference should be have. Are the necessary configure step like create a logic system, allocate logical systems to clients and so on also necessary under the NON-SAP case? I think some of the configure actions is different in this two case. Can anyone give me some clear steps or tell me where I can get them?
thanks to all.

Hi,
for testing purposes you can do the following:
(1) via SM59 create the RFC destination for your dotnet application
(2) via WE21 create a trfc-port pointing to the RFC destination created in (1)
(3) via SM30 maintain view V_TBDLS to create a new logical system for your dotnet application for example DOTNET (and maybe for the SAP client you are testing with - here the name could be for example <SID>CLNT<CLIENT>)
(4) via SCC4 assign the logical system to the SAP client (for example <SID>CLNT<CLIENT>) only if not already maintained.
(5) In WE20 create a partner profile for logical system created for the dotnet application in step (3)
(6) In WE20 add outbound parameters for the message type (for example MATMAS) and idoc type (MATMAS03) you want to send. As partner port use the trfc-port of step (2)
(7) In WE19 create an IDoc via basic type (the idoc type used in step (6), for example MATMAS03) and maintain the following fields in the control record EDIDC:
<b>recipient port</b> the port created in step (2)
<b>recipient partner number</b> the logical system name of the dotnet application created in (2)
<b>recipient partner type</b>'LS'
<b>sender port</b> SAP<SID>, where SID is the SAP system id
<b>sender partner number</b> the logical system name the SAP client maintained in step step (4)
<b>sender partner type</b>'LS'
<b>message type</b> the message type used in step (6), for example MATMAS
In the other segments E1* you can fill in whatever you like
Hit the push button "Standard outbound processing"
(8) you can check if the IDoc has been sucessfully created by BD87. If an error has occurred in the receiving application or there is any other error you can also see it here. Maybe the IDoc is not passed to the receiver, then you can process the IDoc also from here.
This is how you can create your test environment. If you want to get the IDoc created form the SAP application it depends on the application how to do that!
Best regards,
   Willy

Similar Messages

  • Performance problem in IDoc receive (DELFOR01)

    Hi,
    I have serious problems in receive of Idoc Delfor01 (IDOC_INPUT_DELINS). We receive more than 3000 Idoc daily of this type and the process of then during all day....
    One of more common error is foreing_lock of VBAK table. This error occurs in the Form beleg_sperren (line 459 from IDOC_INPUT_DELINS) when the process try enqueue one vbeln entrie from VBAK (o think by the high number of Idoc received) and, the process waits a large time trying enqueue the table entry until the error...
    When I analyze the IDOC_INPUT_DELINS i see a batch-input for the VA32 transaction (at line 528). I think if call a Bapi instead a Call Transaction have more performance... it´s right?
    I would appreciate help with possible solutions to this problem.. Have a better mode to process large amount of these IDoc type? Or have other FM than IDOC_INPUT_DELINS with better performance???
    Regards,

    Not need immediatly, but a quickly possible... In WE20 if I choose the background program the process will executed* fastly than I choose Imediattly start?
    *executed via schedule job of program RBDAPP01.
    I stil reading the notes above..

  • Problems in IDOC receiver communication channel

    Hi,
    I am trying to build an interface to get data from 3rd party legacy system using JDBC and post the data into ECC using IDOCS. I have IDOC built in ECC, I am able to import the metadata in IDX2 after creating port in IDX1. But after building the whole interface, I dont see the IDOC receiver communication channel which has to post IDOCS in the ECC 6.0 system.
    Please assist.
    Rgds
    Kishore

    OK in that case, we are getting the following error in the Message monitoring:
    <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_ERROR</SAP:Code>
      <SAP:P1>-BS_AVN_TO_FILE_JDBCSERVER</SAP:P1>
      <SAP:P2>-BS_WOAV_IDOC_SENDER,urn:sap-com:document:sap:idoc:messages.ZAVENTITY01.ZENTITY</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>No standard agreement found for , BS_AVN_TO_FILE_JDBCSERVER, , BS_WOAV_IDOC_SENDER, urn:sap-com:document:sap:idoc:messages, ZAVENTITY01.ZENTITY</SAP:AdditionalText>
      <SAP:Stack>Problem occurred in receiver agreement for sender -BS_AVN_TO_FILE_JDBCSERVER to receiver -BS_WOAV_IDOC_SENDER,urn:sap-com:document:sap:idoc:messages.ZAVENTITY01.ZENTITY: No standard agreement found for , BS_AVN_TO_FILE_JDBCSERVER, , BS_WOAV_IDOC_SENDER, urn:sap-com:document:sap:idoc:messages, ZAVENTITY01.ZENTITY</SAP:Stack
    Please check and assist.
    Rgds
    Kishore

  • Problem in IDOC Receiving on MII

    Hi
    I am using MII Version 12.1.4 Build(46). We have configured IDOC in SAP ECC, SAP Netviewer and in MII.
    We are able to generate iDoc from ECC but we are not able to receive it on MII Message Monitor.

    Manoj,
    The underlying NW CE installation must also be at SP3 (minimum).  Please check and let me know if you already have the update.  The IDoc Listener configuration changed a bit from 12.0 to 12.1 so there may be some other modifications needed.
    Regards,
    Mike

  • Problem about Idoc Segment Conversion

    Hi experts,
    When i configured the Idoc conversion in the Sender system, it was correct. But it doesn't work after configuring the Idoc conversion in the Receiver system. The case like this: the Idoc record generated in the Sender system but doesn't generated in the Receiver system.
    I will be appreciate if anyone can help me!

    can not be solved

  • Problem in Idoc Receiver

    Hi guys.
    I have a FILE to IDOC scenario.
    The original idoc have only 1 ocurrence but I've changed the ocurrence with an external definition based on idoc xsd with ocurrence 0..N.
    When any idoc is generated in mapping Im getting the next erro in moni:
    Error: MSGGUID 901EF81123CC4D131091DF1F61EB83B4: Tag found instead of tag IDOC BEGIN=
    Why Im getting this error in sxi_monitor if I've especified my cardinality to 0..N??
    Thanks a lot.
    Regards.

    >> Error: MSGGUID 901EF81123CC4D131091DF1F61EB83B4: Tag found instead of tag IDOC BEGIN=
    First export the idoc locally and change the occurence of idoc tag from 1  to  0 to unbounded. Check in the mapping you specify the modified idoc. Also acivate the objects and update cache.
    Tips
    a) Use your modified idoc in the message mapping target side
    b) Operation mapping - Specify original idoc as target message in the inbound side. (you might get some warning during activation.. please ignore it)
    c) In the interface determination check you specify operation mapping and inbound interface as original idoc....
    If you do all the above steps, You should not get this error. Hope this helps.
    Edited by: Baskar Gopal on Feb 24, 2011 9:30 AM

  • Help, strange problem about SOAP receiver adapter

    Hi XI guru,
    Secnario as following:
    ABAP proxy -> XI -> SOAP receiver
    I am using SOAP receiver to send data to legacy system. It looks good in sxmb_moni, so we go to RWB, I see the following error:
    <b>2007-08-13 13:48:53 Success SOAP: continuing to response message df934151-4960-11dc-a195-0015c5f7cd3b
    2007-08-13 13:48:53 Error SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: java.lang.StringIndexOutOfBoundsException: String index out of range: 0
    2007-08-13 13:48:53 Success SOAP: sending a delivery error ack ...
    2007-08-13 13:48:53 Success SOAP: sent a delivery error ack
    2007-08-13 13:48:53 Error MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: java.lang.StringIndexOutOfBoundsException: String index out of range: 0
    2007-08-13 13:48:53 Error Exception caught by adapter framework: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: java.lang.StringIndexOutOfBoundsException: String index out of range: 0
    2007-08-13 13:48:53 Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: java.lang.StringIndexOutOfBoundsException: String index out of range: 0.
    2007-08-13 13:48:53 Success The asynchronous message was successfully scheduled to be delivered at Mon Aug 13 13:53:53 CST 2007.</b>
    So I use XMLSpy to simulate XI to send SOAP request to legacy system, it works fine.In XI, I use WSDL file which legacy system provided to build the mapping, so I think it should be fine. Please comments, thank you for your time.

    Hi
    For receiver webservice you need to configure a receiver soap adapter
    http://help.sap.com/saphelp_nw04/helpdata/en/43/03612cdecc6e76e10000000a422035/frameset.htm
    Check this blog:
    /people/siva.maranani/blog/2005/05/23/communication-between-sap-system-webservice-using-proxies
    /people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
    /people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2
    Check out these threads..
    RFC -> XI -> External web service
    How to resolve this RFC_adapter_sender to SOAP_adapter_receiver Exception?
    Why getting "DeliveryExcetion" in SOAP->XI->RFC scenario?
    You may refer these fallowing weblogs
    /people/riyaz.sayyad/blog/2006/05/07/consuming-xi-web-services-using-web-dynpro-150-part-i
    /people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
    Pls reward if useful

  • Stop IDOC receiver channel

    Hi folks,
    I have what seems like a simple question about IDOC receiver channels, but I have yet to find an elegant answer.
    My scenario is a Non-SAP system with an http sender through XI to an R/3 IDOC receiver. My R/3 system will go down for upgrade for a 2 day period but the external system will continue to send messages.
    I suspect the IDOCs will queue in XI while R/3 is down because the RFC destination is unreachable, but I would like to stop attempts to send while the R/3 system is down.
    I know about availability times for other channels but this technique is not available for IDOC. Is there some way of scheduling the IDOC distribution from XI so that no attempt to send to R/3 is made during the outage ???
    Thanks in advance,
    Guy

    Thanks Karthik,
    That's exactly what I did to demonstrate what might happen (used the wrong password). The message went into error, I reset the password and re-processed and all was fine.
    It just seems to me that there should be a cleaner way - maybe something in QOut scheduling ??
    Thanks,
    Guy

  • 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

  • Errors about 'No receiver could be determined'

    Hi all:
    I am setting up one scenario about ' IDOC to file '.
    When I send IDOC from one R3 system to XI , I meet with the following errors.
    No receiver could be determined
    The SOAP Error is
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Receiver Grouping
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>No receiver could be determined</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    The trace is
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Receiver Grouping
      -->
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="B" name="IDX_INBOUND_XMB" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">User: KEN</Trace>
      <Trace level="1" type="T">Language: E</Trace>
      <Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>
      <Trace level="1" type="T">IDoc-Inbound-Handling</Trace>
      <Trace level="1" type="T">Syntax-Check-Flag X</Trace>
      <Trace level="1" type="T">IDoc-Tunnel-Flag X</Trace>
      <Trace level="1" type="T">Queueid</Trace>
    - <Trace level="1" type="B" name="IDX_IDOC_TO_XML">
      <Trace level="1" type="T">Get the Metadata for port SAPDEV</Trace>
      <Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>
      <Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>
      </Trace>
      <Trace level="1" type="T">Set Receiver Routing-object</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-SET_IDOC" />
      <Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>
    - <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA">
      <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-ITAB_TO_BINARY" />
      </Trace>
      <Trace level="1" type="T">COMMIT is expected by application !</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
      <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">XMB entry processing</Trace>
      <Trace level="1" type="T">system-ID = XID</Trace>
      <Trace level="1" type="T">client = 800</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = KEN</Trace>
      <Trace level="1" type="Timestamp">2006-03-06T13:55:08Z CET</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Message-GUID = 2B74B179E6789D40BCC4A22D826EBDEF</Trace>
      <Trace level="1" type="T">PLNAME = CENTRAL</Trace>
      <Trace level="1" type="T">QOS = EO</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
      <Trace level="1" type="T">Queue name : XBTI0012</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTI0012</Trace>
      <Trace level="1" type="T">Schedule message in qRFC environment</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Going to persist message</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="1" type="T">system-ID = XID</Trace>
      <Trace level="1" type="T">client = 800</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = KEN</Trace>
      <Trace level="1" type="Timestamp">2006-03-06T13:55:08Z CET</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
      <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      <Trace level="1" type="T">No Relation found - accept given receivers.</Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      </SAP:Trace>
    Could anybody give me some clue to debug this problem ?

    Hi Jianhong,
    Since you are doing an idoc to file scenario, you would not require a sender idoc adapter, you would have to configure only a receiver file adapter. Since i guess this is your first idoc to file scenario refer this blog to check if you have followed the steps correctly in the repository and directory:
    https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1819. [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] The blog does not talk about partner profile setup, and i hope you are aware of how to do this.
    Configure your receiver file adapter according to this:
    http://help.sap.com/saphelp_nw04/helpdata/en/95/bb623c6369f454e10000000a114084/content.htm
    Do ask if you require further information.
    Regards,
    Chandra

  • IP Job in BW finished, but how can I check the IDoc receive status in BW ?

    Hi,experts
    After I execute a Infopackage with loading more than 200000 records data, the infopackage monitor show me yellow light, 186020 from 200000 records. this infomation still show me till now, seaval hours,it looks pause here.
    And I check the request in the R/3, the Job has finished. as you know it means the R/3 push the IDoc already finished.
    and how can I do now ? or how can I check the IDoc receive status in BW side?

    Hi,
    I too had the same problem, i executed the following to solve the proble, may be this will help you:
    1) Go to T-code SM58 and select TRFC and press F6,
    2) For manual push of I-Docs, GO to T-COde BD87 select perticular idoc and see the status if it is not executed properly then do the manual push by pressing Execute option,
    Thanks,

  • Problem sending IDOC DESADV  /AFS/DELVRY03 to XI

    Hi Gurus,
    I have problems sending IDOCs DESADV (basic type /AFS/DELVRY03) created by function LSEND_IDOC to XI system. IDOC is correctly created by R3 system (AFS ECC 5.0) and correctly sent on the XI port (Status: Data passed to port OK - 03), but XI system doesn't receive IDOC.
    If I resend the same IDOC by WE19 tcode goes ok!!
    In R3 sending system nothing warnings/errors in syslog or sm58.
    Any suggests? Thanks in advance.

    Issue solved! It is necessary close the master idoc with a commit

  • IDOC Receiver - Unable to convert sender service to ALE

    Hi!!!
    I am trying to configure the following scenario: FILE - XI - IDoc to R/3. 
    A business service called IDOC_Demo recovers from the server the file, and after mapping it, it tries to send it to IBP, the R/3 system using a IDOC Receiver comunication channel.
    IBP is configured in SLD.
    I have in XI System the RFC conexion, and I have define the port via TCODE IDX1.
    But it does not work, I am geting the following error:
    "Unable to convert sender service IDOC_Demo to an ALE logical system"
    I have checked the adapter specific identifiers, but I can not see anything wrong...
    I do not know what can I check! Could someone help me?! What can I do?
    Thank a lot!!
    Araitz.

    Thank you very much, but I still get the error message! Of course, I read your blogs Michal before posting the question, and they have been very useful, but still...
    In SLD I only have the R/3 system, the name is IBP and the business landscape and the logical system name (I do not know if this could cause a problem…).
    The connexion is IBP, and it works, and in idx1 I have configured a port, and its name is SAPIBP, using the IBP connexion.
    Design… I have imported the CREMAS.CREMAS03 IDOC, and I have done a mapping interface, I have disabled the EDI_DC40, and set “begin” and “segment” to 1.
    Configuration… I have created a business service, IDOC_Demo, that has a communication channel, sender, file type.
    And I have the IBP service. In adapter specific I can see: logical system IBP, and R/3 System IBP, client 100. If I push the “Compare with SLD” button, nothing happens… what should happen?
    IDOC_Demo receives the file, and via an Outbound, async interface, calls IBP, that receives the IDoc using a receiver IDoc type adapter…
    Now the receiver agreement has information in the header mapping, sender service, IDOC_Demo, receiver service, IBP.
    And I do not know why, but it does not work… any idea?
    Than you!
    Araitz.

  • Problem with idoc DEBMAS

    Hi everybody.
    We have a problem with idoc DEBMAS.
    This idoc is sent from R3 to PI throw change pointers then the idoc is field only with the data modified in the master custumer.
    We need the information fill it in the segment /IDOC/E1KNA1M/E1KNVVM to determine the receiver determination but this segment is not always sent.
    What can be done in R3 to send always this segment.
    We dont want to sent the whole data but always this segment.
    Any idea???
    Thanks a lot!!!!!

    Hi,
    As E1KNVVM segement is not mandatory, when you are triggering IDoc based on change poitner data might not populted in the E1KNVVM segment until some sales data is changed.
    if you need that segement always just copy the Idoc type and make it mandaotry field.
    otherwise yoy can populate some fields like STDVRS with the reruried constant and can use in your receiver determination.
    Regards,
    Suresh

  • EDI Idoc -- Receiver JMS Adapter.

    Hi,
    I'm facing this issue from few days.
    Sender is EDI Idoc and contains header and Footer.
    This is placed in the application server of SAP system.
    From there xi picks the EDI Idoc and sends to JMS server.
    Facing problem on the receiver JMS Adapter.
    Find the error message.
    "Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: No transition found from state: ERROR, on event: process_commence for DFA: CC_JMS_RCV_DEVWR0000000:165b1638fd823a8f822f0db8a9b1d488"
    I have provoded the "dict" and "doc" value also.
    Pls suggest.
    Thanks in advance,
    Jeevan.

    Hi Guys,
    There could be some problem while deploying the libraries. Check out the thread No transition found from state: STARTING
    Thanks,
    PP

Maybe you are looking for

  • "Document is not a valid photoshop document"

    I started working on a file a few days ago and I saved it before closing out of Elements 11. When i came back it said that the document wasnt valid and i wasnt able to open it. I'm not sure what went wrong and i spent a great deal of time on this and

  • Bad playback with 2-monitor setup

    I've got a working 2-monitor setup connected through my ATI X1900 (a Viewsonic A91f+ and a 50" Sony VGA LCD). When I choose to view playback through the Sony (All frames, Digital Cinema Desktop Preview-any setting), the preview only shows the frame w

  • Creating New Menus that follow the playing of a movie clip

    I was wondering if it is possible to have iDVD display a new menu after playing a movie clip off of the first menu. Then from that second menu if it would then be possible to play a new movie clip. Essentially I want to create a progressive DVD where

  • Flash SWF won't play in captovate

    Hi all, I've created a simple flash file in Flash CS3 and published the SWF and HTML. The SWF and HTML both play fine. Now I want to insert this into a Captivate file. I have tried two methods: Insert Animation into a blank slide Insert an Animation

  • Firefox Sync cannot connect to server

    Firefox Desktop 12.0 on Win7 HP 64bit Firefox Mobile 14.0 on Android 4.0.3 (didn't work on 2.3.6 either) Hello, I'm trying to set up Sync between my Firefox Mobile and Desktop. On the mobile, I tap on "Sync" and get the three alphanumerical codes. I