IDOC again...

OK on the sender side....
Do you need to configure a port on XI for each sender system? or can you have one port specific on XI for receiving IDOCs from all R/3 senders?

Hi Recardo,
See in your XI system, for your IDOC scenarios -if you have multipe SAP R/3 sytems or multiple clients of a single SAP R/3 system, then you have multiple sending systems. So you will have a port for each of them. So you will have multiple sending ports in your XI system for multiple sending systems of R/3.
For completion of your IDOC scenario, you will need to create a logical system for XI in each of your SAP R/3 Systems by WE20 transaction code - but this thing you will do in your SAP R/3 sytems.
Thanks,
Rajeev Gupta
Message was edited by:
        RAJEEV GUPTA
Message was edited by:
        RAJEEV GUPTA
Message was edited by:
        RAJEEV GUPTA
Message was edited by:
        RAJEEV GUPTA

Similar Messages

  • How to merge source data with RFC response and post back again as Idoc

    Hi All,
    This is the requirement we have for an interface
    The legacy application is sending Vendor master to PI 7.0
    If it is new vendor then it is send as an Cremas Idoc into SAP. Legacy (New Vendor) -
    > PI 7.0  -
    >Cremas Idoc SAP
    If it is changed Vendor legacy will only send changed fields for that Vendor.In PI we would like to call an RFC which will return all the data for that changed Vendor Number and then merge the RFC response with changed data from legacy and then send it to SAP as Cremas Idoc again with all values.
    I know these can be achieved using Proxy by custom Abap Code in SAP.But we would like to avoid it.
    How can we achieve it?
    1.RFC lookup - Shall we use these , when PI receives changed Vendor from legacy ,it will call RFC using RFC lookup and the response message from RFC lookup should be merged with source data .Is this possible?
    2.Shall we achieve this using BPM ?Is it feasible and How?
    Any Help greatly appreciated
    Thanks,
    V

    If it is changed Vendor legacy will only send changed fields for that Vendor.In PI we would like to call an RFC which will return all the data for that changed Vendor Number and then merge the RFC response with changed data from legacy and then send it to SAP as Cremas Idoc again with all values.
    I am not sure why you want to pull whole data from R3 and send back to R3.
    you can follow any of these approach..
    if you have any indicator for new/ changed cusotmer in the legacy data then trigger CREMAS IDoc accordingly.
    mapping rules will be diffrent for New and changed CREMAS idoc.
    otherwise just do RFC look up for each record then based on the output(new/changed) create or update cusotmer data through CREMAS IDoc.
    when changing the customer through CREMAS no need to pass whole data again. it is enough if pass the changed fields. offcourse qualifier values  for segments will differ.

  • Problem Sending ARTMAS IDoc

    Hello,
    we have following error.
    ARTMAS04 IDOC contains a field like <2STEP_PICK>.
    But a XML tag with a number in front isn't well-formed.
    So i got an error on my XSLT Mapping.
    Any Idea?
    Reagards,
    Robin

    Hi Robin,
    the field is called "_--32STEP_PICK". May be load metadata again in IDX2 or load IDoc again to Repository.
    Regards,
    Udo

  • IDOC --- XI ----- SOAP

    Hi All,
    Our Scenario is IDOC XI SOAP synchronous.
    We get data from IDOC to XI and send it to SOAP, I get response back from SOAP which is sent to R3 by STATUS IDOC.We have implemented BPM in our scenario and there is no Exception handling.
    My question is, if the SOAP server is down then I get a System Error.What we want to know is
    1. Whether it is possible to send the failed IDOC again to SOAP from XI and get the response back( I guess this is not possible in our case). Does Exception handling enables this feature ??
    2. Is it possible to know the status of SOAP server in BPM so that we can keep the incoming IDOCs in queue and send them once the SOAP is up?
    3. If Exception handling/Fault messages concept is implemented then can we send response back to STATUS IDOC from XI(Note: We need the incoming IDOC number must for this as R3 should know which IDOC is failed).
    Points will be rewarded for helpful answers.
    Thanks & regards,
    Satish

    Hi Satish,
    1. Whether it is possible to send the failed IDOC again to SOAP from XI and get the response back( I guess this is not possible in our case). Does Exception handling enables this feature ??
    Ans) It is possible to resend the data from the XI system if it is failed and sits in the Adapter engine (Message monitoring) here you can resend it once the SOAP server is up.............
    2. Is it possible to know the status of SOAP server in BPM so that we can keep the incoming IDOCs in queue and send them once the SOAP is up?
    Ans) Yes it is possible to know the status of the SOAP , for this you need to include a step in the BPM to have a lookup at the server(SOAP)...Once it is up the workflow can be restarted again manually.................
    3. If Exception handling/Fault messages concept is implemented then can we send response back to STATUS IDOC from XI(Note: We need the incoming IDOC number must for this as R3 should know which IDOC is failed).
    Ans) Yes if the exception handling is done then it is important to have the incoming idoc number so that the response will be send with this idoc number and also the status of the mentioed idoc ..you can achive this with exception handling
    Regards
    Sai
    Reward with points will helpfull

  • For IDOC monitoring, analysis and error handling in  ALE & idoc

    Hello...experts..can u please tell me about idoc monitoring,analysis and error handling..and can u please tell as per interview  point of view in this area..if availble can u send material about this...
    thx
    Message was edited by:
            durga kottapalli

    Hi,
    Reprocessing IDocs with errors
    Outbound (BD88)
    Once the error has been determined and corrected it is not necessary to resend the IDoc again. You simply resend the IDocs that have already been generated.
    Using the IDoc overview screen you need to take note of the following for each IDoc that was not processed:
    Error number: 2, 4, 5, 25, 29
    Error number: 30 (Execute Check IDoc dispatch to process)
    IDoc number
    Using the Error number, the IDoc number and the transaction BD88 , with the required message type you can resend the IDoc. Match the error number with this transaction and execute the function for the IDocs incorrectly processed.
    Just check the below link, u will get all IDOC related Interview questions
    http://www.allsaplinks.com/idoc_sample.html
    http://www.allsaplinks.com/
    http://www.sappoint.com/abap.html
    http://www.sap-img.com/
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
    http://www.sappoint.com/abap.html
    http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://expertanswercenter.techtarget.com/eac/knowledgebaseCategory/0,295197,sid63_tax296858_idx0_off50,00.html
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
    http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sap-img.com/
    http://www.allsaplinks.com/
    Regards,
    Suresh.
    Message was edited by:
            SureshKumar Ramamoorthy

  • IDOC Acks not working

    Hi All,
    I have spent hours searching SDN for this specific problem, and can see some similar threads but none with a successful answer, so I will ask again.
    I have the following scenario:
    R/3 system sending an IDOC to XI, then XI mapping that to a custom XML message and sending it via the HTTP Adapter to an external business partner.
    We have no issues with the above and get a chequered flag in SXMB_MONI.
    But we want an Acknowledgement of that transmission to go back to the initiating IDOC in the R/3 system and update the status. e.g. If there was a HTTP comms failure and the message ended up in error in SXMB_MONI then we want that status sent back as an Acknowledgement to the original IDOC so that the R/3 system is aware of the failure.
    We can see that XI tries to send the Ack back, but in SXMB_MONI in the "Ack Status" column there is an error associated with the Ack which says either "Acknowledgement not possible" or "Acknowledgement contains system errors". When we look into the error message contained within the Acknowledgement it says:
    Unable to convert the sender service XXXXX to an ALE logical system
    The Sender Service listed in the error message is the original Receiver Service which passed on the HTTP message to the 3rd party receiver. But in this case it is the sender because it is trying to send an Ack back to the R/3 system that is now the Reveiver. Note that it is a Business Service (not in SLD), it is NOT a Business System.
    My question is - where is XI looking for an ALE Logical System name? My Business Service is not in the SLD (doesn't need to be, it's a 3rd party external system and I can send to it fine). I even tried populating the Adapter Specific Identifers for this Business Service with the IDOC Logical System name and R/3 System ID and Client, but that did nothing becasue this isn't using the IDOC Adapter, it's using the HTTP Adapter.
    And note that we have SXMB_ADM param RUNTIME-ACK_SYSTEM_FAILURE = 1.
    And please dont post a bunch of links, I've looked at every message in SDN that refers to the above. Please only reply if you can type the exact answer and it refers to the Acks only.
    Thanks,
    Brendan.

    Hi,
    Open(Double click) the Receiver Business service in ID and goto Change mode
    goto Adapter Specific Identifiers---just give the LS name as HTTP and click on Apply and save Activate.
    Do SXI_Cache also
    Now try to post the Idoc Again from R/3
    Regards
    Seshagiri

  • How to change field values AFTER Inbound IDOC Posted successfully

    Hi SAP Experts,
    In my project I receive the inbound IDOC PORDCR05 from PI and posted as an Purchase Order in ECC.
    I create the Z process code and Z function module (which is a copy version of IDOC_INPUT_PORDCR) and complete all the necessary configuration steps. It works perfectly.
    My problem is: I have to  collect some inbound idocs (that satisfied some criteria) and change the value of field EKPO-TXJCD and EKKN-KOSTL of the PO AFTER  it posted successfully (means the purchase order is created and save in database).
    How can I do this? I've try to put the logic code in Z function module, but it does not work, since at that time, the Inbound IDOC is not updated to the database yet.
    Aprreciate your advise.
    Regards,
    Elaine.

    Hi Elaine ,
    as per your cretiria pick the idocs and take created PO# from status 53 & use the BAPI (BAPI_PO_CHANGE) to change the neccessary values in the PO. We can't reprocess those idocs again.
    Reddy

  • Transactional behaviour in third party - XI idoc scenario

    Hi,
    a third party system is sending an idoc via TRFC-call with the function module "IDOC_INBOUND_ASYNCHRONOUS" to the XI-system.
    The scenario is working fine, but one day the XI table space was full.
    The third party systems gets the following error message:
    <b>RFC_ERROR_SYSTEM_FAILURE Problems found during the EXPORT to specified key in table.</b>
    For the sending third party system that is an error and the internal status is set to mode "rollback". That means the third party systems is going to send the idocs again after a specified period of time.
    If i look in transaction SXMB_MONI i can see that the inbound queues were stopped (XI tried to open more than one queue, but all queues were stopped).
    After getting more table space available for XI all (stopped) inbound queues were activated manually, and <b> now all messages waiting in XI were processed!</b>. To me that means XI was able to receive all messages, even the table space was full???!!!!
    But this behaviour is wrong in a transactional view of the whole process. The sending system is going to send the idocs again and so the idoc's were processed twice in the XI system and respective in the receiver system.
    How to handle that?

    Hi Udo,
    what is the effect of setting that value to 1??
    I dont understand how can the message be in the XI system, if the database is full??? More queues will be opened but cannot be processed, but the message seems to be in the XI system...and if so (the message is in XI) the error message to the sending system is wrong!?
    Should i delete the messages (after solving the database problems) in transaction SXMB_MONI (is that possible?)and tell the sending system to send the messages again?? I am quite confused...
    Regards,
    Christian

  • IDOC is successfully triggered from SAP ECC

    hi,
          IDOC has been Trigerred from ECC Sucssesfully and the status is 03, but it not reached in PI, what will be the error, please do the needful at the earliest.
    Share some more errors where i can stuck with idoc when doing IDOC to File scenario.
    Nissi

    Hi
    Please check the following options:
    1. In SM 58 are you getting any error message, if yes analyse it and correct.Delete the entry and try triggering the IDOC again.
    2.Check the connection test  RFC destination for PI maintained in SAP system, check if the User ID maintained there is not locked
       ,try resetting the pwd .RFC connection works even if the user is locked.
    3. I think you can also check if correct port is maintained in PI IDX1 and also try loading metadata again in PI  IDX2.
    4. Check with sap guys if they have written  Commit in the IDOC program.
    Regards,
    Srinivas

  • Issue with IDoc adapter

    Hi
    I have sent a couple of IDocs from r3 to a legacy system through a Xi interface. Sender adapter is IDoc. For example I have sent 100 IDocs from r3 and 80 reached legacy system. Where we can check for missing IDoc? I am able to see 100 in BD87 of r3 system.
    Thanks

    I can see that message in SXMB_MONI as a success message. But if go to the let of the display there is a column with name outbound status. In that column is is showing a red flag( error at outbound side). No message in SMQ1or SMQ2. Also no error message in RWB. Where it can be found? How to reprocess it? Do we have to resend the IDoc again?
    thanks

  • IDoc - Incorrect Number Sequence

    Hi,
    I have created a custom IDoc and sending it to 2 different SAP boxes. This has been triggered every half an hour interval. But my problem is IDoc numbers are not in proper sequence
    Below find the screen image of WE02.
    Here you see the IDoc No. 42202 created on time 10.20 and IDoc number 43004 created on 10.34 and IDoc No. 42203 created on 10.50
    |     IDoc Number|Segments|Status|StatusGrpg|Partner      |BasicType|Date      |Time    |Messg.Type|Direction|Port   |
    |0000000000042200|      28|03    |          |US/  /TP1    |Y101     |06/01/2007|09:50:32|Y101      |Outbox   |TP1    |
    |0000000000042201|      42|03    |          |LS/  /AP1    |Y101     |06/01/2007|10:20:31|Y101      |Outbox   |AP1    |
    |0000000000042202|      26|03    |          |US/  /TP1    |Y101     |06/01/2007|10:20:31|Y101      |Outbox   |TP1    |
    |0000000000043004|   18593|03    |          |US/  /TP1    |Y101     |06/01/2007|10:34:24|Y101      |Outbox   |TP1    |
    |0000000000042203|      14|03    |          |LS/  /AP1    |Y101     |06/01/2007|10:50:31|Y101      |Outbox   |AP1    |
    |0000000000042204|       8|03    |          |US/  /TP1    |Y101     |06/01/2007|10:50:31|Y101      |Outbox   |TP1    |
    |0000000000042205|       7|03    |          |LS/  /AP1    |Y101     |06/01/2007|11:20:31|Y101      |Outbox   |AP1    |
    I have checked the Number range object EDIDOC,  "No. of numbers in buffer" is mentioned as 1000.
    incorrect sequence of IDoc numbers is created due to this?
    How to correct this ?
    Thanks
    aRs

    Don't change standard settings.
    1) What happen if you try small files, this happens only to huge segments.idoc:43004(18593 segments) is huge file.
    2) What happen if you trigger same idocs again.If you didn't try can you please try again and check.If say thing occurs than i guess that's the standard functionality of
    buffering.
    Again this issue is very instresting to me. I never faced this probem.
    If you get solution please update.
    Thanks,
    Narayan

  • Receiver IDOC adapter - IDOC_ADAPTER" ATTRIBUTE_IDOC_METADATA

    Scenario:
    EDI (Sender File adapter)-->PI7.11-(Receiver IDOC adapter)---->ECC
    I'm getting an error (below) at the Call Adapter stage:
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error SOAP:mustUnderstand="" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
      <SAP:P1>I::000</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Error: I::000</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Then I went to IDX2 and deleted the IDOC (in this case, ORDERS05) and tried to create the IDOC again, but I get a pop up window with
    I::000
    and thus the IDOC can't get recreated.
    Need to mention that both PI and ECC enviroments that I'm working in are sandboxes (XS1400 and RS1400) that are copies of our Development environment (XD1400 and RD1400).
    Can someone please shed some light?

    Hi,
    Addition to the above
    Check the port name you are mentioned in the receiver idoc adapter it should not be with client no...
    it should be only SAPSID..(SID is your system name..)
    HTH
    Rajesh

  • XI idoc to idoc scenerio

    Hi
          my problem is that  i passed data from Source R3 sytem to XI.I am receiving XML message in XI.But XML massege is not passed to target R3 System.
    Suoure System Distribution Model Details:
    Sender:TESTBSYS2        (r3source)
    Receiver:IQXCLNT600       (xi)
    in target System:i have creted 2 logical system TESTBSYS2 and IQXCLNT600
    now u can find from where i m doing misstake?
    one thing is also confuse me:
    in IR i have created 2 business system 1:TESTBSYS1  and 2:TESTBSYS2
    TESTBSYS2  is sender so i have not make Communication Channel
    TESTBSYS1 is sender so i have make CC using Idoc adapter and define port and RFC destination
    still idoc is not pass from XI to target R3.
    Please help

    Hi Mohit
    If it is in error then how can you expect that this will be posted to R3.
    XI basic thing is to check the messge in moni for error.
    Now solve that error and then trigger the idoc again to check.
    If you dont know how to solve that particular error then post it we all will try to resolve it.
    Now seen ur error----
    Go to Receiver Determination and check have you correctly defined there who is the receiver.
    Edit the Receiver Determination and activate it again, sometimes it also solve the problem.
    Regards
    Dheeraj Kumar
    Edited by: Dheeraj Kumar on May 11, 2010 3:29 PM

  • RSEOUT00 run sends duplicate IDOCs causing duplicate payments

    We are using RSEOUT00 to send out payments to vendor using PAYEXT type. Program is run in background job mode on daily basis.
    Occasionally, 1 IDOC out of couple of hundred gives error and then program starts from the beginning and send out all IDOCs again sending those before the 'error' IDOC twice.
    Today's error IDOC had below status in the given sequence:
    01
    30
    02 - Could not write to file  (At this stage it restarted the process)
    30 (Second attempt worked fine)
    03
    20
    24
    06
    08
    10
    This is happening atleast once a month.. Any suggestions would be appreciated.
    thanks.
    sudhir

    Hi Sudhir,
    I see two seperate issues here...1) why is the job periodically failing to write to the output file and 2) why is RSEOUT00 not marking the idocs written to the file to status 03 as they are written?  Sounds like it is trying to write all idocs to the file before changing the status messages.
    As to point number 1, please check with the unix team to determine if the files are written to a NFS mount point.  There could be a possibility that the NFS mount has sporadic issues, causing failure of the job.  This situation would be very difficult to diagnose and recreate.  However, I have seen this issue at a client site.
    My concern is that I would expect RSEOUT00 to exit at failure, leaving a single file on the server with 19 records.  I would then expect the next occurance of RSEOUT00 to run and process/write all 380 idocs to a second file.  However, per our conversation you indicated that RSEOUT00 only ran one time, creating two files.  Can you please confirm if my understanding is correct, and if there are any other batch jobs (or steps within other jobs) that call RSEOUT00 and picking up these idocs.
    Whether RSEOUT00 ran once or twice, I see the failure during the write to the file as the primary problem to be solved.
    Terri

  • IDOC  - HRMD_A - Infotype 35

    Guys ,  everytime i change infotype 2 for example  a new idoc is created with this new information, however i want to do this for infotype 35 , i mean send the idoc again but without send any information of the infotype 35. how could i achive this ?
    thank you very much for your advice .

    Hi,
    make sure infotype 0035 is included in the filter in your distribution model. Change pointers are just created for infotypes included there.
    Regards,
    Ana

Maybe you are looking for