IDOC COmmunication Channel

Hi
i have created a receiver idoc communication channel, and when i want to check whetehr its working fine or not in Runtime Work Bench , when giving the receiver communication channel name it is saying " Communication Channel" does not exist??
plz help me

Hi,
      As you said you have created the receiver idoc communication channel and if you are monitoring the idocs in IDX5 for the same then the idoc will be outbound and not inbound....
if you are confused with directions then check with out giving the directions in filter criteria....
Also are you sure that the idocs have generated successfully in PI for sending..check the interface message in MONI for the same...
Hope this clears you
Regards
Rajesh

Similar Messages

  • 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

  • Its possible to Create Bussiness Service for IDOC Communication Channel

    HI FRNDS,
    My scenario File to Idoc,
      When we will go for business Service , Its possible to create Business Service SAP R/3, its a Good advice.
    To which Adapters we will use business Service, business System
    Regards,
    raj

    Hi,
    This is the basic difference between Business Service and Business System. This will help you in concluding why you use them and hence you can deduce your answer....
    Business System
    Business systems are logical systems that function as senders or receivers within the SAP Exchange Infrastructure. You configure business systems in the SAP System Landscape Directory (SLD). A business system is always associated with a technical system (here: SAP Web AS ABAP system).
    Business Service
    Using a business service, you can define the technical or business subunits of the companies involved and then assign them the relevant interfaces.
    You usually use business services when configuring cross-company processes. In this case, you only make your interfaces known to the business partners involved and either do not make any details about your own system landscape available, or only specific details.
    Regards
    Arpil
    Reward points for the useful answer

  • Sender Communication Channel for Integration Scenario IDoc - XI - IDoc?

    Hello All,
    One general question. I have to configure an IDoc - XI - IDoc Scenario. For this Scenario I have to configure an Receiver Communication Channel (IDoc Adapter) to the Backend System but what about Sending Communication Channel for the Sending R/3 system.
    Is the (IDoc) Communication Channel from Sending system to XI required to configured?
    Many thanks in advanced!
    Jochen

    Hi Jochen,
    for sending IDOCs from SAP to XI, sender IDOC adapter is not required. when XI will send the IDOC to a SAP system, then receiver IDOC adapter is needed.
    Thanks,
    Rajeev Gupta

  • IDoc adapters not in "communication channel monitoring"?

    Hi,
    I've modified some information that the receiver IDoc adapter is using (the logical system ID). But after I refreshed all the caches the change is not updated when I send an IDoc to R/3.
    When this kind of problem happens with RFC adapter you just have to stop and restart the communication channel in communication channel monitoring. But IDoc adapter is not here... so, how can I restart the IDoc communication channel?

    Hi,
    IDoc adapter doesnt reside on Adapter Engine, its part of ABAP stack, because of this you cannt find it in RWB-Communication channel monitoring...
    Try refreshing the cache:
    Transaction: sxi_cache
    CPACache refresh using the below url:
    http://<server:port>/CPACache/refresh?mode = full
    to get the changes affected.
    Regards,
    Sreenivas.

  • Why is a sender communication channel not required for IDOC and PROXY ?

    Hello,
    In case of IDOCs, metadata will be available in PI for the IDOCs used both at inbound and outbound.
    Why is a sender communication channel is not required in case of IDOC and PROXY outbound scenarios (i.e. IDOC to File or PROXY to file ..)  when a receiver channel is required for scenarios like file to IDOC or file to PROXY.
    Though this might be a regular question, I am not able to find a proper reason.
    Please let me know the reason for the above request.
    Thanks & Regards.

    You will create RFC destination in ECC , it will have details about PI system details, when ever you send IDoc, ECC will use Port and RFC destination to connect PI Integratiion engine to deliver data to PI.
    But when receiver side you will create RFC destination in PI with ECC details, but to call RFC destination and Port we need medium that was the reason we create IDoc communication channel.
    Even the same case for Proxy also, but HTTP deastination establish the conection between ECC and PI, but receiver side you have to create XI channel with PI integratioin engine adress to post data.
    Regards,
    Raj

  • Communication Channels for IDOC scenario

    Hi!
    I have a conceptual question regarding the communication channels within IDoc scenario.
    Case 1:
    - File_to_RFC scenario
    Here I defined a File communication channel from business system A.
    1a) For which system (business system A or B) do I need to define a IDoc communication channel?
    1b) What is the RFC destination and Port I need here?
    Case 2:
    - IDOC_to_IDOC scenario
    2a) Do I need in this scenario only one communication channel for business system A?
    2b) What is the RFC destination and Port I need here?
    Thank you very much!
    Thom

    >
    Thom Heinemann wrote:
    > Hi!
    >
    > I have a conceptual question regarding the communication channels within IDoc scenario.
    >
    > Case 1:
    > - File_to_RFC scenario
    > Here I defined a File communication channel from business system A.
    > 1a) For which system (business system A or B) do I need to define a IDoc communication channel?
    >  1b) What is the RFC destination and Port I need here?
    >
    in this case no IDoc CC is involved. All you need is a File sender adapter and RFC receiver adapter
    > Case 2:
    > - IDOC_to_IDOC scenario
    > 2a) Do I need in this scenario only one communication channel for business system A?
    >  2b) What is the RFC destination and Port I need here?
    >
    >
    > Thank you very much!
    >
    > Thom
    in this case you will need a IDoc receiver adapter only.
    The basic settings:
    In XI
    SM59 - R3 connection pointing to R3
    IDX1 - define the port with the above dest.
    In R3
    SM59 - R3 connection pointing to XI
    WE21 - define the port with the above dest.
    WE20 - Partner profile type outbound/Inbound
    Further ref:
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&

  • IDOC adapter is not shown in communication channel

    hi gurus,
    at present i am using PI and in the communication channel list (adapters types) no idoc adapter is displayed ,can anyone help me to solve this problem.
    and also when i create any scenario related to idoc those messages where not displayed in communication channel.

    Hi Allen,
          U r checking for an IDoc channels in Communication channel monitoring.IDoc adapter is reside in ABAP stack.So that u cant see the Idoc communication channels from monitoring of CC's. If Idoc messages is at sender side no need of CC.
    If you want to view the source and target messages of Idoc's u can see those from SXMB_MONI.Choose u r processed message,Dbl click,For Idoc as sender u can view the message from payloads of Inbound message,For Idos as Receiver u can view the message from Payloads of Request message Mapping.
    Hope it will helps..
    Cheers
    Veera
    >>>Reward points,if it is needful

  • Why IDoc Sender Channel Used in Outbound Scenario's

    Hi Team,
    In my outbound scenario's ,I never used IDoc sender channel.Only ALE settings I have configured..PartnerProfile,RFC dest,Port etc.
    Why can we use Idoc Sender channel? Is it only used for IDocFlat file format OR for normal Idoc's also? If we use Idoc sender Channel , how it is processing - Is it TRFC queues-sm58 ?
    Can you give me clear idea on it / suggect any blogs.
    Thanks.
    Drumi

    HI,
    In my outbound scenario's ,I never used IDoc sender channel.Only ALE settings I have configured..PartnerProfile,RFC dest,Port etc.
    Why can we use Idoc Sender channel? Is it only used for IDocFlat file format OR for normal Idoc's also? If we use Idoc sender Channel , how it is processing - Is it TRFC queues-sm58 ?
    we dont necessary to create Sender Communication channel for IDOC and Proxy and http because xi and sender systems(out bound) resides on abap stack and also dont need for any idoc.
    The reason is that R/3 can directly send Idocs to XI via ALE layer using RFC destination specified in SM59.
    This IDoc after reaching XI is converted in IDoc-XML. This is done when we specify IDoc metadata IDX2 in XI. It is then used in IR for mapping.
    Now for the receiver side, when IDoc-XML is created after mapping program run is sent to R/3. Before that, it has to
    be converted into IDoc. This conversion is IDoc-XML to IDoc is done by IDoc Receiver adapter.
    one case we need to create sender IDoc Communication channel for IDOC packaging concept thats all.
    thanks,
    Edited by: bhavanisankar.solasu on Dec 16, 2011 7:12 AM

  • Unable to create communication channel - RFC

    Hi ,
    I am trying to create communication channel automatically , when adding business systems from SLD to integration repository. I get the following error only for RFC
    all other communication channel gets generated correctly.. Is there any thing i am missing.
    HTTP communication channel GeneratedReceiverChannel_HTTP created
    IDoc communication channel GeneratedReceiverChannel_IDoc created
    XI communication channel GeneratedReceiverChannel_XI created
    Unable to create communication channel: Unable to generate the communication channel (NWR_107, GeneratedReceiverChannel_RFC): com.sap.aii.utilxi.misc.api.ClientServerException
    Thanks,
    Ganesh Ram

    Please run transaction SLDCHECK. The connection to SLD might not be working properly.
    Plus, in the business system you created, check if client number and all other parameters associated with SAP systems are valid.
    Dmitriy

  • How to set up the communication channel for third party idoc

    Hello,
    I am trying to send an idoc from an sap 4.6c system to an third party system. The third party system is supporting idcos with trfc.
    My problem is to set up the communication channel in the integration builder (configuration) for the third party system. The idoc is waitung in XI to transport.
    My settings are:
    adapter type: idoc
    transport protocol: idoc
    message protocol: idoc
    adapter engine: integration engine
    rfc destination: xyz (is working fine)
    interface version: sap release 4.0 or higher
    port: ??
    sap release 46c
    My problem is the port. should i set up a port in idx1? But the third party is not an sap system and so i dont have a client.
    On the xi i have defined a port in transaction we21 (transactional rfc) for the third party with my rfc destination xyz. But if i enter that port in communication channel i got error messages.
    Thanks for any help.

    Hi Christian,
    yes, you have to mainztain that port in idx1.
    First ypi load the rfc-metadata from an SAP referenzsystem and afterwards copy this metadata to the third party port.
    For further details check the onlinedocumentation "IDoc Processing with the IDoc Adapter" XI -> runtime -> adapter
    Good luck,
    Holger

  • 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

  • FlatFile 2 IDOC: Error in Communication Channel Monitoring

    The given below is the Audit Log:
    ===========================
    Error convert()
    Error: convertCalledFromModule()
    Error: process()
    Error process()
    Error MP: Exception caught with cause javax.resource.ResourceException: --- Conversion of synchronous request from module chain ended with errors ---[Error:ID=3069;LEVEL=3] SegmentDescription: checkAndResetChildrenCounter() not enough repetitions of the segment S_BGM found: 0 instead of 1 offset :2588 DESCRIPTION: SegmentDescription Warning: Not enough repetitions of the segment S_BGM ([not specified]/[not specified]).
    Note:
    My IDOC has S_BGM with 1..1 occurance.
    S_BGM is created at the target.
    But still, the above excception.
    Can any one provide the solution?

    Hi,
          The test is successfull in the IR.
    Error shown in communication channel moni.
    I hope, mapping a constant is not required here as S_BGM is a 1..1 (occurance)
    Edited by: santosh kumar on Dec 19, 2007 12:53 PM

  • Sender agreement & communication channel not needed in case of IDOC adapter

    Hello everyone ,
       I am new to xi , as far as i know a communication channel cannot be created in ID when using IDOC adapter , the answer for this question is like , the idoc adapter resides on the integration server & not part of j2ee AF .
    Can some one explain me in the terms of a laymen , its not clear to me.
    Thanks & Regards,
    Reena.

    Hi ! Reena
    IDOC adapter resides on Integration server, so Integration engine takes care of the conversion format from IDOC to XML, hence there is no need for sender Adapter .Also since its residing on Integration server you can directly post the message in the Integration engine.
    well lemme explain a little bit,the main reason for sender agreement is to associate namespace with the sender adapter,now when we shoot IDOC from R/3 it already contains its standard SAP namespace so no need of sender agreement.
    now comes the sender CC,main use of sender CC is to identify the sending system and the adapter.the IDOC header contains details of all the this,so again there is no need for sender CC
    loook at this thread discuss the same
    Re: Why we r not Creating Sender Agreement For HTTP & IDOc Adapter at Sende
    Re: why HTTP & IDOC adapter do not require sender communication channel?
    Thanks!!
    Questions are welcome here!!
    Also mark helpful answers by rewarding points
    Regards
    Abhishek Agrahari

  • RFC , IDoc , XI and JDBC receiver communication channel--- Good Design

    Hi Experts,
    We have developed around 60+ interfaces on PI7.1 EHP1, in that 20 interfaces sending data to Data Base using JDBC receiver communication channel, 15 interfaces ABAP inbound proxy using XI adapter,10 Scenarios using IDoc receiver channel and 15 scenarios using RFC receiver channel.
    But I have created only one IDoc, XI , JDBC and RFC channel.
    Is it right idea/design or do I need to create more channels to handle multiple request.
    Please share your thoughts on this.
    Regards,
    JAM

    Hi,
    For XI,RFC and Idoc when it's pointing to one SAP system you don't need any further comm channels.
    For JDBC , if you are pointing to only one database you can use the same channel, if the target/databse changes you need more comm channels.
    Your Design is as per the standards.
    Regards,
    Sainath Chutke

Maybe you are looking for