FILE TO IDOC SCENARIO-Receiver Business system ECC showing Red

HI
     In File-idoc scenario Business system showing red status in RWB .And i have given the role for the business system as application server and configure related integrated server . But the error in a RWB  for the ping and self-test is as follows
     Unable to log on to system buss_ecc_200 in language en with user PIRWBUSER .
I thing from XI side every thing is ok. But for bussiness system side ECC might miss some configuration .
       could any help in this issue:
regards..

Hi
Please try one of the followings:
1) In Configuration --> Business service --> Service --> Adapter specific identifiers. Give logical system name for the sender system (e.g XI_00_800)
2) In Design --> mapping objects. Give all information of sender n receiver in EDIDC40 segment and
   In configuration --> receiver communication channel in that enable the checkbox take sender from payload.
3) In configuration --> Receiver Agreement --> Header mapping --> Sender Service (Give XI1 i.e ur sender system).
Also check the RFC destination that is the major problem with idoc...

Similar Messages

  • Receive acknowledgement in file-to-idoc scenario

    Hello!
    I'm using guide "How to handle acknowledgement for IDOC", and for the first time I want to see an acknowledgement status in sxmb_moni.
    I have passed all steps:
    In CRM I have logical system P1DFILE, this is the system that sends an idoc to CRM.
    Also, I have logical system C2DCLNT100 - this is CRM system.
    First, I go to BD64, create new model view XI_CRM. Then, add message type:
    Sender system - C2DCLNT100
    Receiver system - P1DFILE
    Message type - ALEAUD.
    Then I create RFC destination P1D_001 to my PI server.
    Then I create port SAPP1D using WE21
    Then I go to WE20, choose my Logical System - P1DFILE. I already have the inbound message types (CRMXIF_PARTNER_SAVE and CRMXIF_PARTNER_SAVE_M). I add new outbound message - ALEAUD with receiver port SAPP1D.
    Then I go to RBDSTATE, create variant SAP_AUDIT_SEND and enter:
    Confirmation to system: P1DFILE
    Message type: CRMXIF_PARTNER_SAVE and CRMXIF_PARTNER_SAVE_M
    Then, in SM36 I shedule SAP_AUDIT_SEND as a hourly job (does this mean, that I will receive confirmations only every hour?)
    So, what should I do to see ack in sxmb_moni?

    Dear All,
    For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
    For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
    I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
    Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

  • XI unable to post IDOC to ECC the interface is FILE-to-IDOC scenario

    Hi All,
    The XI interface is a FILE-2-IDOC scenario and some times IDOC's in the receiver system are not posted.  I did see successfully message for that particular messages but the IDOC's were not created in the ECC.  If the messages is reprocessed then IDOC's are posted successfully to the ECC system.  The message has checkered flag in the SXMB_MONI tcode.
    This issue is occurring intermittently so could some point me in the right direction how to trouble shoot the issue.
    Thanks,
    Sarvesh

    Hi,
    Interesting problem...since its intermittant..
    You cannot use any of the traditional RWB or message monitoring or cc chanel monitoring here as the error is in the ecc system, so from an XI standpoint it has left XI succssfully..that explains all the chequered flags..indicating success.
    we19, we12, we14(process all idocs) test out the whole process with a load..use transaction we46..this can tell you why it is failing....in r/3
    from the ecc system to check inbound queue monitoring.
    from there you can select the IDocs or queues which you want to monitor, using the specified selection parameters available.
    Look at the status record for the idoc that should give you more information, processing status of the idoc...that should tell you the status code assigned to it..
    There is one other option here....if you can figure out what sequence they need to be posted in...that might be the reason for the failure..you can specify the sequence to post the idocs in, use qRfc ..
    Hope that helps
    Regards
    Ravi Raman

  • Where to define third party logical system name in file to idoc scenario

    Hi Friends,
      I am shalini shah.
    I have one doubt, where I can define the logical system name in File to Idoc scenario.
    I created Logical system for R/3 system in SALE t.code, but where to define the Third party logical system ,
    In SALE or any where.
    Please give me solution.
    Warm Regards,
    Shalini Shah

    Hi Shalini,
    You need to create Business system in SLD and import the business system in ID.Then u will start with the configuration.
    Just refer the below link for configurations with step by step solution.
    File To IDOC - Part1 (SLD and Design):
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
    File To IDOC - Part2 (Configuration):
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
    File To IDOC - Part3 (Steps required in XI and R3):
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
    Thnx
    Chirag

  • System Level Acknowledgement in File to IDOC Scenario

    Hi All,
    I have the File-> IDOC Scenario. Once the IDOC is successfully sent to R/3, PI  should send a acknowlement file back to the sender system.
    Could someone suggest how to design this scenario?
    Should I use IDOC Acknowledgement. As it is a existing scenario, I dont want much change in r/3 side.

    Dear All,
    For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
    For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
    I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
    Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

  • ** File to IDoc scenario - IDoc not created in target system

    Hi friends,
    We are doing File to IDoc scenario. We made required setting in both application as well as XI system. While test the scenario, the file is picked up and successfully processed in SXMB_MONI, but the inbound IDoc is not created in target system. What could be the problem?
    We are using DEBMAS message type DEBMAS06 IDoc type. We checked the following.
    1) SM59 - Connections are OK both application and XI system
    2) IDX1 - In XI System, we have assigned SAP<R/3> port.
    3) IDX2 - IDoc is imported.
    4) In ID - Sender File - Business Service - Adapter-Specific Identifier - Logical System name is given.
    5) In application system. - Partner Profile maintained correctly.
    6) SM58 - There is no error.
    So, what could be the reason ?
    Kindly reply, friends,
    Thanking you.
    Kind Regards,
    Jeg P.

    Hi,
    Check all the steps ..
    File to IDOC
    Do these configurations in R/3 and in XI...
    SAP XI
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (IDX1)
    a) Select create new button
    b) Enter the port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Load Meta Data for IDOC (IDX2)
    a) Create new
    b) IDOC Message Type
    c) Enter port created in IDX1.
    SAP R/3
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (We21)
    a) First Select Transactional RFC and then click create button
    b) Enter the destination port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Create Partner Profile (WE20)
    a) Create New
    b) Create the Partner no. name as same the logical system name of the destination system.
    c) Select Partner type LS
    d) Enter details for Type: US/USER, Agent, and Lang.
    e) Click on the + button to select the message type.
    f) Select Partner no. and LS which ever create above.
    g) Select Message type
    h) Select Process code related to the Message type.
    I) save.
    Thanks,
    Satya

  • XI 3 File to IDoc scenario - Still referencing Old Logical system

    Hi
    Dont know if you can help. I have a file to idoc scenario  using XI 3 to R/3 4.6c system.
    I had the interface working from a third party system XMLHUB to SAP R/3. The Logical system name for the XMLHUB was XMLHUB01 in the SLD which I have set up as a partner profile in R/3. I have recently changed the logical system name to XMLHUBDEV01 in the SLD and created that logical system in R/3 and changed the partner profile to XMLHUBDEV01.
    Unfortunately in the sender information of the IDoc the partner number is still XMLHUB01 and not XMLHUBDEV01. I don't understand where this partner is sent from to get into the control record of the IDoc.
    I have cleared the SLD cache in both the Repository and the directory. Is there somewhere else I should be looking? Any help would be appreciated.
    Regards
    Daniel

    hi daniel...
    this thread wud answer ur query....
    Re: IDOC Payload
    regards..
    vishal

  • Not sure if IDoc was created or received in file to idoc scenario

    Hi,
    I configured a file to idoc scenario in my test client for idoc MATMAS.MATMAS02 , now after going thru all the phases of design and configuration and creating partner profile using we20 , when I m executing the scenario , I am not sure wht happened to the idoc becz i can't see in the R/3 system using we05/02 or BD87 in the XI system .
    Pl help how to rectify the error and find out where the error has actually occured.
    ans will be rewrded
    rgds
    mojib

    Hi Mojib,
    first check in SXMB_MONI whether you have a success chequered flag for the file messge.................if there is error here, then rectify your this error and re-run your scenario................if you cannnot see your file msg in SXMB_MONI, then go to RWB and in comm channel monitoring, see the error in sender file comm channel status and rectify the error in sender file comm channel in ID and save and activate it and then re-run your scenario............
    then execute SM58 to see in there is anything in tRFC.........if there is not anything here, then it means your IDOC has reached R/3.................
    then in R/3, execute WE05 for the relevant period, then you will see your IDOC there with some status..........
    Regards,
    Rajeev Gupta

  • File to Idoc Scenario using third party systems

    hi,
    Working with a File to Idoc Scenario. Been able to successfully define everything in IR / ID. However when I go to BD87 (reciever system) and see the status of Idoc processed - getting the error code 51 "Function Module Not Allowed: <Function Name>" . What could be the reason for this???
    Have defined partner profiles in WE20 of type LS and also specified an inbound paramter in the post processing tab for partner profile. Are there any other settings I need to take care of to avoid getting that error.

    Hi
    I am giving u all the steps whioch are required for
    <b>File to IDoc</b> Scenario
    SM59-  Create RFC destination
    IDX1-  Create a IDXPORT in idx1
    IDX2-3.     Import metadata of IDoc’s in idx2
    Bus. service adapter specific Identifiers-->Logical sys name
    we05-IDoc status records
    BD54-Create Partner Number
    We20-Create Partner Profile
    WE19-Testing IDoc Processing
    SE16-Table name->LFA1 to check vendor has been created
    Check have u followed all the steps.
    Regards
    Arpit Seth

  • File to idoc scenario in pi 7.1

    Hi All,
    I am testing file to Idoc scenario.
    I have few queries. I am using PI 7.1
    1) in Message mapping - I import the receiver idoc metadata. and doing mapping.
    So there are couple of mandatory fields over there. Please let me know how to treat them. Do I need to diable them or put some value. for exp Direct, Segment. SNDPRN RECPRN all these madatory fields are there. Please advice.
    2) When I am creating communication component for sender side(File system) then should I assign the logical port and if then what name it can be . Is there any other place we need to maintain this entry. I remember in PI 7.0 I dont need to assign the local name. But here i see I need to do. if I am not putting the name over there then it throw error message "Unable to convert the sender service <Business Compoenetname> to an ALE logical system.
    Please advice how to overcome
    3) now any how I am able to process the idoc from PI and its coming to ECC system. but it showing failed over there and giving me error message.
    "EDI: Partner profile inbound not available"
    I checked all the relevent partner prfile configuration is already there"
    I have already used all the forums , I did these scenario in past in PI 7.0 and never faced much issue . but doing first in PI 7.1 after a long time, so I might be possible, I am missing some thing. Please advice and help. thank
    Ram

    Hi Ram,
    There is nothing new in PI7.1 which can cause these errors.. it is because the interface is configured wrongly
    >>1) in Message mapping - I import the receiver idoc metadata. and doing mapping.So there are couple of mandatory fields over there. Please let me know how to treat them. Do I need to diable them or put some value. for exp Direct, Segment. SNDPRN RECPRN all these madatory fields are there. Please advice.
    If you know the value the you can create the control record during mapping and the fields which you don;t required you can map it co constant. It is using this control record the partner profile entries are found and if there is a mismatch then the idoc will fail with the error which you mentioned in point 3
    >>2) When I am creating communication component for sender side(File system) then should I assign the logical port and if then what name it can be . Is there any other place we need to maintain this entry. I remember in PI 7.0 I dont need to assign the local name. But here i see I need to do. if I am not putting the name over there then it throw error message "Unable to convert the sender service <Business Compoenetname> to an ALE logical system.
    No in 7.1 also we dont have to do anything like that. There is a blog on this error from Michael, please go through it and understand why and how this error occurs. May be in PI7.0 you were lucky enough for not getting this error
    >>3) now any how I am able to process the idoc from PI and its coming to ECC system. but it showing failed over there and giving me error message. "EDI: Partner profile inbound not available"I checked all the relevent partner prfile configuration is already there"
    Check the control record of the generated idoc and see whether you have a partner profile entry for the parameters mentioned in it. If not then you need to correct them in PI
    Regards
    Suraj

  • File to IDOC scenario-no messages in SXMB_MONI

    Hi all,
       I know this is asked so many times ,I checked some links but couldn;t find out the gap where it happened.
    I am doing a File to IDOC scenario through XI mapping.
    I am not getting any messages in SXMB_MONI.
    When I check Communication Channel monitering in Runtime Workbench, it shows processing successfully, then it should generate messages in SXMB_MONI and intimate whether the scenario created is correct or not right!
    Please help.
    My scenario goes like this:
    Sender : Business service(Some file location)
    Used File adapter for sender communication channnel.
    Receiver : Business system(SAP R/3)
    Used IDOC Adapter for receiver communication channel.
    One more thing is,do I need to create logical system for Business service also?If so, where do I maintain it?(In SAP R/3 or in XI system?)
    Till now,I maintained my XI system as logical system in WE20 and I didn't create any logical system for business service in any system.Does it create main problem?

    Hi , I am able to poll the files from file location now.and I am receiving IDOC into SAP R/3 with status 56.I already created partner for file path as a logical system and assigned inbound parameters with respective message type . Even the status shows :
    An inbound partner profile could not be found with the following key:
    /LSDEMO/LS//DEBMAS////
    This involves the key fields of table EDP21:
    -SNDPRN  partner number of sender
    -SNDPRT  partner type of sender
    -SNDPFC  partner function of sender
    -MESTYP  logical message type
    -MESCOD  logical message code
    -MESFCT  logical message function
    -TEST    test flag
    I already manitained following data and there is one record in EDP21.
    SNDPRN  = LSDEMO  
    SNDPRT  = LS
    SNDPFC = LS
    MESTYP   =  DEBMAS
    MESCOD = space
    MESFCT = space
    TEST = space
    EVCODE   = DEBM
    SYNCHK = X
    METHOD = space
    USRTYP = space
    USRLNG = space
    INMOD = space
    DCART = space
    And please let me know whether I have to maintain outbound parameters  also for my partner in XI system.I didn't see any difference even I maintained it.
    And my IDOC takes another port rather than I mentioned in my SNDPRN(sender port) of my IDOC control record in message mapping.Let me know whether it's mandatory to maintain port name with SAP<XXX>convension,because IDOC in R/3 is picking the port with that naming convension.
    Edited by: Jaya on Feb 26, 2010 10:17 AM
    Edited by: Jaya on Feb 26, 2010 10:27 AM

  • Reg:file to idoc scenario

    In a file-xi-idoc scenario i created a business service for legacy
    system and a business system for R/3 receiver system
    i didn't assign logical system for the sender business service
    and assigned a logical system for the reciver business system
    so while maintaining partner profile in the R/3 system
    i have to give partner no:
                        partner type:
    here the problem is my sender business service i didn't assign any logical system,and it is not of LS type
    so then what do i need to give in the above two fields?
    answers required briefly

    Hello,
    you know this pdf:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c09b775e-e56e-2910-1187-d8eba09c7a4a
    Could be helpful.
    Regards
    Patrick

  • Problem with Sender service in File to IDOC scenario

    Hello All,
    Am doing a file to IDOC scenario.
    I have configured the sending system as a party and added a business component, to the BC attached the service interface and also configured the sender Communication channel(CC) as file.
    On the receiving end configured the R/3 system from SLD as the business system and configured the receiver CCl. Can see the R/3 logical system in the Adapter specific identifiers at business system.
    Pushing the file get an error "Unable to convert the sender service  to an ALE Logical System".  But choosing "Take sender from Payload" in the receiver CC is resolving the problem, however the sender partner number remains the same as what I have mapped to the control record in message mapping (which is like hard coding).
    My questions are:
    1. Am I doing the correct config in terms of the scenario. (like using  "Take sender from Payload")
    2. I tried using identifiers at the party level to convert the sending system, but nothing seems to work. But sending system remains the same as the constant from mapping.
    Suggestions would be very much helpful..
    --Prashanth
    PS: Have gone through many blogs and posts on the forums, but may be I did not see the correct thread. Apologies if I am asking this again.

    Hi Prashanth,
    refer the below discussion i think it will solve your problem.
    File To Idoc scenario
    Thanks

  • IDocs not created in file to IDoc scenario

    Hi all
    I am trying this file to IDoc scenario.
    File picked up successfully and sent to R/3 Backend…But Idoc is not posted…the status records
    In /n we05 in R/3 Backend shows that EDI: Partner profile inbound not available
    I created/tested all basics like RFC dest, port etc.
    File service that I am using is a business service …hence I am specifying a Logical system name in
    <b>Adapter specific Identifiers</b> of the file service.
    I disabled EDI_DC40 control tag record as IDoc adapter
    takes care of it.
    So at first I tried the configuration of IDoc comm. Channel by checking the Apply control record values from payload
    But SXMB monitor gave an error regarding this control record tag…I guess as we have disabled it so there won’t be any values
    for control record in payload (correct me if I am wrong).
    So I unchecked the checkbox Apply control record values from payload and monitor showed up as successfully processed.
    But in the backend I am getting this error regarding partner profile.
    I also tried to use an existing profile (<b>LS</b> type) by modifying it’s inbound parameters to accept <b>CREMAS</b> Idoc.
    But the error is as persistent as me
    Pls help
    Sudhir

    Hi
    Sender --> LEGACY, maintained in SLD (Logical system).
    Receiver--> ENI maintained in SLD with logical sys name M700.
    Partner Profile LEGACY maintained in R3.
    <b>Following is the IDocOutbound in SXMB monitor in XI</b>.
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Response
      -->
    - <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <SAP:TABNAM>EDI_DC40</SAP:TABNAM>
      <SAP:MANDT>100</SAP:MANDT>
      <SAP:DOCREL>640</SAP:DOCREL>
      <SAP:DOCNUM>0000000000001013</SAP:DOCNUM>
      <SAP:DIRECT>2</SAP:DIRECT>
      <SAP:IDOCTYP>CREMAS03</SAP:IDOCTYP>
      <SAP:CIMTYP />
      <SAP:MESTYP>CREMAS</SAP:MESTYP>
      <SAP:MESCOD />
      <SAP:MESFCT />
      <SAP:SNDPOR>SAPAXI</SAP:SNDPOR>
      <SAP:SNDPRN>LEGACY</SAP:SNDPRN>
      <SAP:SNDPRT>LS</SAP:SNDPRT>
      <SAP:SNDPFC />
      <SAP:RCVPOR>SAPENI</SAP:RCVPOR>
      <SAP:RCVPRN>M700</SAP:RCVPRN>
      <SAP:RCVPRT>LS</SAP:RCVPRT>
      <SAP:RCVPFC />
      <SAP:TEST />
      <SAP:SERIAL />
      <SAP:EXPRSS />
      <SAP:STD />
      <SAP:STDVRS />
      <SAP:STATUS />
      <SAP:OUTMOD />
      <SAP:SNDSAD />
      <SAP:SNDLAD />
      <SAP:RCVSAD />
      <SAP:RCVLAD />
      <SAP:STDMES />
      <SAP:REFINT />
      <SAP:REFGRP />
      <SAP:REFMES />
      <SAP:CREDAT>0000-00-00</SAP:CREDAT>
      <SAP:CRETIM>00:00:00</SAP:CRETIM>
      <SAP:ARCKEY>DF57A2C0532811D9AD84000F206A031B</SAP:ARCKEY>
      </SAP:IDocOutbound>
    <b>Control record of IDoc in R3</b>
    Tab: Typeinfo
         Basic type-->CREMAS03
         Message Type-->CREMAS
    Tab: Partner
         Recipient
          Port  -->SAPENI
          Partner Number--> M700
          Partner Type-->LS
         Sender
          Port  -->SAPAXI
          Partner Number--> LEGACY
          Partner Type-->LS
    Pls help
    Regards
    Sudhir

  • IDOC is posting with Errors in File to IDOC scenario

    Hi,
       I did the File  to IDOC scenario for CREMAS  . IDOC is posting with Errors .. i.e. in the status record it was showing  56- EDI: Partner profile inbound not available  ..
    If I manually process that IDOC in WE19 , then it was processing successfully..    and in the  we19 it was showing Inbound Processing : Port Not Maintained    but even though manually it was posting fine...
    any ideas regarding this will be appriciated..... 
    Regards
    Babu

    Please check whether you had done the following assuming your doing File to Idoc
    Settings in your Business service for the receiving system
    Please specify the RFC detination, SAP System and Client of the Receiving System in the adapter specific detials.
    Settings in R/3
    WE20 - Add the partner profile for the particular message type cremas and process code.
    Your statement
    " and that same logical system name  had given as Message Specific Attributes in the Sender Business Sevice parameters in I.D "
    Please do mention R/3 Details in the receiver business service or system.
    Thnz

Maybe you are looking for

  • How to set up SAPconnect with email server

    Hi, Does any one know <b>how to set up SAPconnect with email server</b> We are using workflow and when it fails it we are sending the notification mail to the user on his company mail id, i.e. [email protected] This is working in the current producti

  • Global Chord Track and Marquee Tool

    Hi there, I wanted to select some Chords on the global chord track, but the marquee tool doesn't seem to work here. When i click & drag (with the marquee tool, of course!), no marquee will draw, but the first chord that i touch is selected and pulled

  • SP02 showing update was terminated and not showing Spool no and other data

    Hi Friends, Can anyone guide me in the below problem After going to change mode of transaction when i go to message and i have done repeat output and further data and communication methods. After that i have saved document. After that when i enter in

  • Someemail@somedomain.ASIA not able to register at oracle

    Hi, It is not possible to register at Oracle (Single Sign On) by using a .ASIA address. It will say: The email address must end in a well-kown domain or two letter country. I hope the users from ASIA are still welcome here. Is it possible to fix this

  • Error in c project accounting

    Dear plm consultant, I am facing problem in c project costing . when i go for calulate the cost, i get following error. <b>Error occurred in accounting - see controlling cockpit (cProjects) Message no. DPR_FIN_GECCO024</b> Diagnosis Errors occurred w