IDOC scenarios

Couple of things I don't understand
I am doing a IDOC to File scenario
On the R3 side
I have created Partner Profile,
Port, Logical System and RFC Destination and also a message type
ON the XI side
I have created a port and RFC destination. Now comes several questions
1. Where am I creating the IDOC and IDOC Type and how do I know what is it
2. In XI I am trying to load MetaData in transaction IDX2 and somehow I don't see my system in there. How do I make my system appear in there. Anyway I choose the create option. I enter the port from which I need to import the IDOC and it says there is no RFC destination for the Port whereas I specifically know that I created one for that port
Please help.

did you follow all the basic steps ???
Listed below is the steps that are req. for IDOC-XI communication.
Sent/Receive IDOC:
you need to do the following:
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&
Configuration steps required for posting idoc's(XI) -
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
ALE configuration for pushing idocs from SAP to XI -
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi

Similar Messages

  • Error while executing a JDBC to Idoc scenario : No standard agreement found

    Hello SAP PI Gurus, 
    I am having a JDBC to idoc Scenario .And the interface is running at 10 min of duration. 
    <SAP:AdditionalText>No standard agreement found for ,
    BS_EXT_CTBSREPDB, , BS_ERPQAS_QE1_320, http://XYZ.com/FI/FI_FI_01/Charges, FIDCC2</SAP:AdditionalText>.
    While i test the configuration...i get an error in reciever agreement as mentioned above.
    Can you pls help me in resolving this issue.
    Regards,
    Ravi

    Hi,
        I think the problem is with namespace....for IDOC the namespace will be "urn:sap-com:document:sap:idoc:messages"...but in your case it is different.....i.e http:....etc.....please check whether you 've used the same IDOC withe above mentioned namespace in all the configuration objects like interface determination, receiveragreement etc.....
    Thanks
    Priyanka

  • Idoc-XI-Idoc Scenario

    Dear All,
    I am working on Idoc-XI-Idoc scenario in which I am getting ORDRSP Idoc in input. In one of its segment I am getting value as either A or B. If value is coming as A in input then in the output we want PORDCR101 Idoc but if we have B as value in the source idoc then we should have multiple PORDCR102 Idocs ie for each line item there will be different idocs.
    Please guide me on how we can implement BPM in this scenario as required two MM i have created and they are working fine.
    Regards,
    NJ

    Hi,
    If value is coming as A in input then in the output we want PORDCR101 Idoc but if we
    have B as value in the source idoc then we should have multiple PORDCR102 Idocs ie for
    each line item there will be different idocs.
    For Source = A:
    SourceField----
                          -----equalS ----ifwithoutElse ----then Constant(blank) ---> PORDCR101
    Constant(A)---
    Assuming that A in input then in the output we want PORDCR101 Idoc means that you need only one occurence of the IDOC
    For Source = B:
    SourceField----
                          -----equalS ----ifwithoutElse ----then LineItem ---> PORDCR102
    Constant(B)---
    Regards,
    ABhishek.

  • 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

  • Issue in IDOC-XI-IDOC scenario

    Hi,
    We are facing a strange issue in an IDOC-XI-IDOC scenario. We are using a SAX parser to parse the code here.
    The error we are getting in 'sxmb_moni' is
    <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
      <SAP:P1>com/abc/def/dev/sapxi/clfmas/Idoc2IdocMapperCLFMAS</SAP:P1>
      <SAP:P2>java.lang.RuntimeException</SAP:P2>
      <SAP:P3>For input string: ""</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>During the application mapping com/abc/def/dev/sapxi/clfmas/Idoc2IdocMapperCLFMAS a java.lang.RuntimeException was thrown: For input string: &quot;&quot;</SAP:Stack>
    The strange thing is, when I restart the message, it gets processed successfully. Also, when I copy the payload, and test the same on a different environment, it gets processed successfully.
    Would really appreciate some pointers here!
    cheers,
    Prashanth

    Hi,
    This related to mapping error check it once again.Check in Interface mapping Test tab.see the result.check the sxmb_moni and get the source of mapping come back to interfcae mapping and test .
    See the below links
    Hi I got EXCEPTION_DURING_EXECUTE in RWB->Message Monitoring
    I am getting MAPPING  EXCEPTION_DURING_EXECUTE
    EXCEPTION_DURING_EXECUTE- Error in Mapping. Doubt about IE and AE
    EXCEPTION_DURING_EXECUTE
    Mapping problem - EXCEPTION_DURING_EXECUTE
    ERR: EXCEPTION_DURING_EXECUTE while using FILE CONTENT CONVERSION
    Regards
    Chilla..

  • Error in IDOC-XI-IDOC scenario

    Hi folks,
    Let me explain the issue. This is an IDOC-XI-IDOC scenario. No BPM’s involved. SAX parsing used to parse the IDOCs.
    We had around 35000 IDOCs coming in from Brazil system, and they are all stuck in SMQ2 (Inbound queue) in XI. The first message of every queue is in SYSFAIL status, with the status text as <b>‘Problems found during the EXPORT to specified keyin table’</b>.
    When I try to execute the queue manually, nothing happens, but an error comes at the bottom of the screen, saying <b>‘Function module does not exist or EXCEPTION raised’</b>.
    I checked the dump on ST22, and it shows 130 runtime errors yesterday. The name of the runtime error is<b> ‘EXPORT_TABLE_UPDATE_CONFLICT’</b>.
    In the ‘what happened?’ part of the dump, it says ‘Error in ABAP application program. The current ABAP program <b>“CL_XMS_PERSIST=============CP”</b> had to be terminated because one of the statements could not be executed. This is probably due to an error in the ABAP program.’
    Even SXMB_MONI is not opening (for yesterday’s date). When I try to open it, it hangs for a long time, and finally opens an ‘ABAP Runtime Errors’ page with the runtime error titled as<b> ‘SNAP_NO_NEW_ENTRY’</b> and the error short text as ‘ Runtime error: Unable to write short dump’
    Please advise.Thanks a ton!
    cheers,
    Prashanth

    Hello Prashanth,
    First of all this is an XI issue and belongs in that forum.
    The export problem is typical to situations where your XI DB is out of space/out of table space. Please check with your Basis team.
    ‘Function module does not exist or EXCEPTION raised’- This message is a standard ABAP RFC message. For an RFC function call to succeed, you need the same RFC function to exist on both systems. However this is probably not the case- it is more likely that you're out of DB space as I already wrote.
    Good Luck (don't forget to award points)
    Ofer

  • Message has error status at outbound side File To Idoc Scenario

    hi ,
    In my File to Idoc scenario , when i go to sxmb_moni , i found that its showing red flag at Outbound Status Tab and showing message "Message has error status at outbound side".
    When i go to IDX5 and and select my idoc and click on Transaction Id it shows "Password logon no longer possible - too many faile" .
    Please suggest what may be the problem ?
    Regards,
    Rohit

    1. First check the RFC destination name used in receiver Idoc adapter communication channel.
    2. As i said earlier, in sm59 transaction in XI gui, u can check same rfc destination under type 3. There check the logon credentials and the username.
    3. Now goto the R3 system GUI and check in su01 that same user is locked or not. If locked unlock it.
    4. And if u change the password of that user, then do the similar change in XI -> sm59 -> rfc destination logon credential
    Regards,
    Prateek

  • Deleting data from a table(JDBC to IDOC scenario).

    Hi,
    For JDBC to IDOC scenario, the requirement is as explained below:
    1: There are 2 tables-> GDDB and CHANGES
    2: Poll the CHANGES table every 30 mins everyday.
    3: a)Publish the records for which the 'published' flag status is 'N'
       b)Update the status as 'Y' after publishing.
    4: On the first day of every month, delete the records from the CHANGES table if the record is 3 months old and 'published' status is 'Y'
    I would like to know how  update and delete can be done using one JDBC adapter?
    Regards,
    Vishal.P.Kulkarni

    Hi,
    update:
    there is a field in the sender jdbc adapter - SQL statement for update - put it there
    delete - On the first day of every mont
    create a job on the database which will trigger the delete statement
    it does not/ should not have to be done with XI
    Regards,
    Michal Krawczyk

  • Error in File to IDOC Scenario

    Hi,
    I have File to IDOC scenario.
    I am getting error in sender file channel.
    "Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found "
    Although I have used this parameter in content conversion 'xml.keyfieldName' (for each sub structure and defined a key field).
    Despite of this error in sender channel I am receiving the message in XI.
    But in XI also it throws error :
    "Unable to convert the sender service PG_TOM_CEEMEA_RU_SFA to an ALE logical system"
    Any help on this ?
    Thanks,
    Vikas

    Hello Vikas,
    I am getting error in sender file channel.
    "Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found "
    Although I have used this parameter in content conversion 'xml.keyfieldName' (for each sub structure and defined a key field).
    Check your flat file structure whether the key field you have chosen is appropriate and also recheck the FCC details whether you have assigned the value for the key field i.e.  keyFieldValue.
    "Unable to convert the sender service PG_TOM_CEEMEA_RU_SFA to an ALE logical system"
    regarding the above error refer this
    https://wiki.sdn.sap.com/wiki/display/XI/Unable%20to%20convert%20Sender%20system%20to%20ALE%20logical%20system
    Regards,
    Prasanna

  • Error while doing a File to IDOC scenario

    Hi Experts,
    I have created a File to IDOC scenario where in i have sent a file which has to pass data to ABSEN1 IDOC.I could see the IDOC reaching R/3 ,but with the status 56: "EDI: Partner profile inbound not available"
    I have checked with all the configurations and couldnt find where it went wrong.
    Kindly help me in this regard.
    Thanks.

    Hi
    Check the inbound parameter and the process code.
    To find Process code for IDoc use Tcode WE42.
    ALE idoc trouble shooting use
    Troubleshooting of ALE Process
    look also this configuration
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6bd6f69a-0701-0010-a88b-adbb6ee89b34

  • IDoc to JDBC  and JDBC to IDoc Scenario

    Dear All,
    I am working on IDoc to JDBC and JDBC to IDoc Scenario.
    I have to send Idoc from SAP to Non SAP system(.NET application) i almost configured in XI but still i don't know when my INTEGRATION will INVOKE how my data will proceed from IDOC to Oracle database(Through JDBC) and in case of revese how and when Data flow will start.
    Does anyone have completed STEP by STEP scenario document for this?
    How my Idoc will sent to XI?
    How XI will pick up data from IDoc?
    How XI will Convert data to JDBC and UPDATE in Oracle Database?
    And i reverse case(JDBC to IDoc) when my INTEGRATION will INVOKE?
    Where and When i can watch my process and data?
    How can i test the whole integration?
    I AM GETTING ERROR WHILE TESTING CONFIGURATION IN Integration Directory "Error while refreshing the XI runtime cache" and when i check this in SXI_CACHE  it gives me error
    "Unable to refresh cache "NO_BUSINESS_SYSTEM"
    "Error during last refresh to cache"LCR_GET_OWN_BUSINESS_SYSTEM - NO_BUSINESS_SYSTEM"
    Please solve all the above problems i will reward u points
    thanks,
    RP

    Hi,
    While we working on IDOC to JDBC interface..
    We have to deploy JDBC Drivers?
    Go through this links,
    /people/varadharajan.krishnasamy/blog/2007/02/27/configuring-jdbc-connector-service-to-perform-database-lookups
    http://searchsap.techtarget.com/tip/0,289483,sid21_gci1246926,00.html
    To install JDBC driver follow the how to guide.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how%20to%20install%20and%20configure%20external%20drivers%20for%20jdbc%20and%20jms%20adapters.pdf
    Configuration of JDBC Adapter for SQL Server
    JDBC Driver = com.microsoft.jdbc.sqlserver.SQLServerDriver
    Connection = jdbc:microsoft:sqlserver://hostname:<port>;DatabaseName=<DBName>
    UserID and Password.
    If the connection is not working find the correct port number.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40b92770-db81-2a10-8e91-f747188d8033
    JDBC- X I -  R/3 Scenario
    /people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
    /people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
    Please check the driver path as mentioned below.
    JDBC Driver : sun.jdbc.odbc.JdbcOdbcDriver
    Connection:jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=//location of DB table.mdb;
    No JDBC driver required.
    Receiver JDBC scenario MS access - /people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn
    follow this thread
    Re: Problem when connecting to MS Access through JDBC Adapter.
    SAP Note 850116 has details
    /people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
    Configuring the Sender JDBC Adapter
    http://help.sap.com/saphelp_nw04/helpdata/en/1d/756b3c0d592c7fe10000000a11405a/content.htm
    Configuring the Receiver JDBC Adapter
    http://help.sap.com/saphelp_nw2004s/helpdata/en/b0/676b3c255b1475e10000000a114084/content.htm
    Idoc Reveiver adapter..
    http://help.sap.com/saphelp_erp2004/helpdata/en/b9/c5b13bbeb0cb37e10000000a11402f/content.htm
    Thanks,
    Satya Kumar
    /people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
    Edited by: SATYA KUMAR AKKARABOYANA on May 8, 2008 5:51 PM

  • JDBC to IDOC Scenario

    Hi Experts,
              I have tried JDBC to IDOC Scenario but it is giving No Segments Found Exception. I don't know where I am doing the mistake.
           can any body please send me a pdf document for JDBC TO IDOC Scenario with step by step procedure from scratch (including creation of LS,LI etc)
    Thanks in Advance,
    Murthy

    Hi Murthy
    The steps are pretty much the same as any other scenario with some exceptions
    1: You import the IDOC structure from the R/3 System. This acts as the DT, MT and MI.
    You also need to do some configurations on the ABAP Stacks of sender and XI system.
    Sender:
    WE20 Partner Profiles
    SM59 RFC Destination
    XI:
    SM59 RFC Destination
    IDX1 Ports
    IDX2 This is the metadata repository so you wont necessarily need this.
    Also because you IDOCs can be sent directly to the ABAP stack/Integration Server you do not need a sender comm channel or sender agreement.
    The rest is pretty much as any other scenario.
    Please see the below links
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
    idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
    Cheers..
    Vasu
    <u>** Reward Points if found useful **</u>

  • How to handle the control records in case of file to idoc scenario.

    Hi All,
    can you please clarify me how to handle the control records in case of file to idoc scenario.

    Hi,
    In File to Idoc scenario even though you selected apply control record values from payload and you are not getting those correct values which you have provided in the mapping.
    Also check the checkboxes Take sender from payload and Take receiver from payload along with the Apply control record values from payload checkbox
    Regards
    Seshagiri

  • About FILE to IDOC scenario

    Hi Experts,
    i need some help for doing file to idoc scenario.
    1. what are the configurations we must do while doing this scenario?
    2. How to communicate with Legacy system to sap system?
    3. How to create the business and logical systems for SAP systems in SLD?
    4. How to define parameters in communcation in ID?
    5. what work shold be done using SM59 and WE20? and specify the steps please?
    6. finally if u having word file please send from the creation of logical system for sap system?
    thanx.

    Go thru below mentioned links.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/73527b2c-0501-0010-5398-c4ac372c9692
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6bd6f69a-0701-0010-a88b-adbb6ee89b34
    once you go thru them you will find answers for questions.
    thanks,
    Venkat

  • JDBC to Idoc scenario - change of logical system name

    Hi,
    I have a JDBC to idoc scenario that worked. Now i had to change the logical system name from my sender system from ABC_123 into ABC123 in the SLD (Business System - Integration - Logical System name). I did so and also refreshed my Cache.
    Afterwards I started the process, but it failed in the Receiver system. The idoc is correct expect of the partner name. My receiver system expect ABC123 - as I changed in the SLD - but PI send ABC_123.
    If io look in SXI_CACHE - Services my Business System still got the "old" name (ABC_123).
    Did i miss something resp. how can i load the current configuration from SLD?
    Thanks in advance
    Michael

    Hi Michael,
    Again Import the changed logical system in the Integration directory of you PI system.
    And check the scenario (Sender Agreement, Receiver agreement ) what system they are reflecting.
    If they are showing old system then you have to replace the business system in all the scenario.
    Edited by: Rajhans Abhay on Jan 7, 2010 3:14 PM

  • 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

Maybe you are looking for