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

Similar Messages

  • 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

  • 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

  • Monitoring receiver idoc communication channel

    Hi All
    I have an idoc to idoc scenario.
    I am unable to see my receiving idoc communication channel in communication channel monitoring of RWB. It is not available in the dropdown list.
    I want to have a look at the audit log to see if the idoc is delivered to the receiving system.
    How can i monitor receiver idoc communication channel?
    How can i ensure that the idoc is delivered to the receiving system?
    In sxmb_moni, status is checkered flag.
    Many Thanks
    Chandra Sekhar

    Hi,
    IDOC is on ABAP stack hence u can not monitor IDOC.
    For testing purpose
    1) GO to SXMB_MONI check the status of message.
    2) Go to R3 and enter Tcode WE02 and check the IDOC which is send from XI. enter the idoc name and see the status of IDOC it should be in green status if it is posted successful or else see the status record for checking the error message.
    chirag

  • RFC Look Up APIs for a IDOC Receiver Communication Channel

    Hi,
    Can we use RFC Look Up APIs in UDF for a IDOC Receiver Communication Channel. (File to IDOC Scenario). Requirement is to send a notificaiton when IDOC got posted with IDOC number.
    Best Regards,
    Madan Agrawal

    As the name suggests, RFC lookup uses RFC receiver channel only. In mapping of your File to Idoc scenario, you may perform this lookup.
    Requirement is to send a notificaiton when IDOC got posted with IDOC number.
    Configure ALEAudit for this requirement. How were you planning to use RFC lookup for such a requirement?
    Regards,
    Prateek

  • Issue in Dynamic configuration in SOAP receiver channel

    Hi All,
    My scenario is file to SOAP. At receiver side I want to generate URL dynamically.
    To proceed step by step, I started with passing a constant URL to Dynamic configuration UDF.
    mapping:
    Dynamic conf. UDF
    Channel Configuration:
    From testing, I found that channel always takes the url given in Target URL field and dynamic URL in TserverLocation is been ignored by the channel.
    That is dynamic configuration is not working completely.
    I went through a lot of blogs and also tried a lot of trial and error methods, but none helped. Every thing I configured looks perfect for me, but still not working. I don't understand where I went wrong. Please help me.

    Hi Experts,
    I am facing similar issue,
    URL --> UDF --> @dynamicvariable
    I have created a variable underparent node eg: DESADV-->dynamicvariable
    passed complete URL to UDF, below is the UDF
    & configured SOAP Receiver Channel as well. This is IDOC to IDOC scenario, using IDOC_AAE on sender side and SOAP on receiver in single stack.
    --> Checked ASMA
    --> Checked Variable Transport Binding and given "TServerLocation" without quotes in XHeaderName1
    --> Target URL: http://
    But when I am running this interface, nothing is coming in Dynamic configuration.
    Ref: Message Log:
    MM and OM is also perfect in ESR.
    Any suggestions? Please advice.
    Regards
    Singh

  • Sender party of reciever determination is getting used in IDOC receiver

    Hi All,
    i am having a very strange problem in my XI scenarios.
    i have 2 scenarios: S1 and S2.....S1 scenario is running on production.......S2 scenario is on development....both S1 and S2 are similar in the sense, they are sending IDOC to SAP R/3.......
    s1 scenario is having in recever determination :
    sender party A
    sender service A1
    receiver service R/3 by IDOC adapter - in this apply control rec values from payload is checked.......This S1 scenario is running fine on production.....
    s2 scenario is having in recever determination :
    sender party B
    sender service B1
    receiver R/3 bY IDOC adapter - in this when i check apply control rec values from payload, then in SXMB_MONI i get error :<b>Unable to convert sender XI party http://sap.com/xi/XI/XIParty/B to an IDoc partner</b>....<i>So you see the sender party B is getting used in the IDOC comm channel.</i>.....But when i uncheck control rec values from payload, then my msg is successfully processed in SXMB_MONI...
    Now my question is : why S1 is runnig fine and S2 is not running fine on check apply control rec values from payload option......both are having party and service in sender.........So has it to do something with the definition of party......
    Thanks,
    Rajeev Gupta
    Message was edited by:
            RAJEEV GUPTA

    Hi Bhavesh,
    my scenario is file - idoc........basically it is XI msg->IDOC scenario....the source xi msg i am getting from another XI system.....but on dev, i cannot connect to that external XI system, so on dev i am having file sender adapter to send the source file to be mapped to IDOC and then to be send to R/3 dev..........
    i saw the control rec values of both S1 of prd and S2 of dev........
    S1 scenario is similar to S2 in the sense it also has XI msg from that external system.....but since prd is connected to that external XI system, so we have created a party and a business service in it.......it has in IDOC adpatere the option of appy control rec checked........
    i saw that the control rec of both S1 and S2 msgs were similar......moreover the control rec values of S2 msg with and without the option of appy control rec checked were similar.........the only issue is when the apply control rec option is checked, then it gives error that "Unable to convert sender XI party http://sap.com/xi/XI/XIParty/B to an IDoc partner"......
    But in S1 prd scenario, it is not giving this error on checking the option of appy control rec.......
    <b>Can you suggest why this is  happening - why party B of S2 is considered differently from party A of S1</b>......moreover these parties are simple parties created in ID.........
    Thanks,
    Rajeev Gupta

  • File-XI-File:one sender channel, multiple receiver channels on same BS

    Hi !
    We need to send some files from one server to another. On the source, the filenames have a fixed prefix and a timestamp. On the target, the files should have a fixed name (time stamp trimmed). We would like to use one sender channel with the advanced file selection option and for example 3 receiver channels, each channel for each fixed filename. All destination channels are for the same business service. And because we do not need mapping, and want to improve performance, we don't use the repository.
    Is this possible? or because this only a 3 files scenario, we should make it as 3 different scenarios, each with its own sender and receiver channels?
    Thanks,
    Matias

    Hey
    >>But Ahmad, as mentioned in the blog, XI scenario without IR can be used only if it's non xml mesage. Is that right?
    can you please tell me where it says this:)
    is it this line which is confusing you <b>"Contrary to popular believe, the message or document sent thru XI does NOT have to be in XML format"</b> ?
    well it just means that you can send any data(.jpeg,.pdf xml .xls or anything) by doin the bypass scenario.
    IDOC's are something which can give u problems if you dont do IR steps(specially mapping)coz a lot of values need to be hard coded.but suppose ur doing a async File to RFC,then i guess you can do that by using the bypass scenario.
    i won't count on bypass scenarios for all of my requirements,but yeah if both source and target have exactly same data type i will give it a shot,irrespective of the interface i m integrating.
    Thanx
    Ahmad
    Message was edited by:
            Ahmad

  • 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

  • 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.

  • Error in SOAP Receiver channel

    Hi,
    We are working on IDOC to SOAP Scenario (Connecting to third party).
    We have configured the SOAP Receiver channel with the Target URL and teh corresponding SOAP Action.
    But the SOAP Receiver channel gives the error while processing and sends back the following error message in log :
    "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: Server was unable to process request. ---> Value cannot be null. Parameter name: s."
    Payload seems to look fine in XI and SAP.
    Any help on this ?
    Thanks and regards,
    Vikas

    Hi Vikas,
                Copy the payload from SXMB_MONI  after mapping and check with SOAPGUI or Altova, if it working fine then your payload is good. You can use the WSDL to ganarate and send independent soap request from these tools.
    Besides this IDOC is Asyc, you need to use RequestResponseBean and ResponseOneWayBean to get the response from SOAP.  Check the following  and try to simulate it.
    https://wiki.sdn.sap.com/wiki/display/XI/File-RFC-File%28Without+BPM%29
    Server was unable to process request. ---> Value cannot be null. Parameter name: s."
    The error specifies that the request has null value, check the parameter specified in the error message and make sure that is not null while you are sending the request.
    Regards,
    Prasanna

  • Error in SOAP receiver channel: java.io.IOException: invalid http response:

    Hi experts,
    I have a IDOC to SOAP scenario where SOAP receiver channel is sending data to web service. In the receiver channel I am getting error as below. Kindly help me to resolve this issue. Thanks.
    "Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid http response: null"

    Did you check this?
    http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4
    Regards
    Pothana

  • OFTP_TCP Receiver channel error

    Hello All,
    To an exisitng sceanrio of EDI Sales Invoices i have added new party. For this i have taken as refrence an exisiting party in the scenario.
    While testing newly configured party interface I am getting the errors in receiver channel as below.
    Delivery of the message to the application using connection OFTP_TCP_http://seeburger.com/xi failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: Recoverable Error: Invalid state transition in session state machine.: State: WF_CF_CF, event: REL_IND, Recoverable Error: Invalid state transition in session state machine.: State: WF_CF_CF, event: REL_IND: javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: Recoverable Error: Invalid state transition in session state machine.: State: WF_CF_CF, event: REL_IND, Recoverable Error: Invalid state transition in session state machine.: State: WF_.
    When I have tested the existing party interface the message was processed successfully.
    How to trouble shoot this error? any check points to avoid this error?
    Cheers
    Veera

    Hi,
    Total 18 party's were there. All parties were had having the same Sender & Reciever SSID. I have copied the same channel. An module was used "SaveAttachment". Modified the parameter value of this. I.e  to save the file using parameter name.
    Provided ODETTE as Agency, Scheme - OFTP and Name - XXXXXXXXX0453.
    The Invoice messages are successfull in MONI for newly added party.The Idoc messages are converted into EDI format too.
    Pls let me know if you a
    Cheers
    Veera

  • Start and stop the Communication channel from Java Mapping

    How to start and stop the Communication channel from Java Mapping in XI 3.0
    Scenario  PI - > MQ -> Third Party web application 
    Web application is down and then Communication channels are stop manually .  
    We need to automate this process,
    MQ Solution - Trigger will be set in MQ which will be called when web application is stopped
    Trigger will send u201CSTOP u201C message to PI
    How to configure PI scenario to stop different com channels when this message received ?

    check this link: http://help.sap.com/saphelp_nw04/helpdata/EN/45/0c86aab4d14dece10000000a11466f/frameset.htm
    make sure that MQ send http request to PI. i dont think a configuration scenario is required in PI. Only roles should be enabled with proper user provided to MQ team.
    However, for security reasons, you can configure a scenario if you dont want to expose PI infrastructure directly to 3rd parties.

  • JMS Adapter Fail - Receiver channel. Details: Receive timed out

    Its an IDOC to JMS scenario. IDOC gets processed through the pipeline in XI successfully, can see the checkered flag.
    However in Adapter monitoring, JMS adapter is in red.
    The error text against the Communication Channel is "Receiver channel. Details: Receive timed out".
    I am trying to connect to the JMS queue provided by a third party on port 1100 ( as configured in JMS adapter).My initial analysis is to check if the port is open on the third party's firewall( Need to get the response back from them yet).
    However i would like to know, if there is something else that i should look into?

    Following are the error messages in RWB audit log for the message sent.
    Exception caught by adapter framework: The JMS channel with channel ID 3f307d6854683859b39f978a43e88872 is errornous. Details:Receive timed out
    Error Delivery of the message to the application using connection AFW failed, due to: The JMS channel with channel ID 3f307d6854683859b39f978a43e88872 is errornous. Details:Receive timed out.
    what might be the problem?

Maybe you are looking for