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.

Similar Messages

  • Idoc-xi-file scenario.  how to display file in html format

    I am not sure whether this is a valid question.........but want to confirm as it was asked by somebody
    In idoc-xi-file scenario.......  how to display file in html format ??
    Thanks in advance
    Kumar

    Hi Vijayakumar,
    Thanks for your reply !! You mean to say I got to use XSLT mapping and also .htm and .html extension together to produce the html file ?? or it is sufficient to use any one of them to produce the html file ??
    Regards
    Kumar

  • In idoc to file scenario, if XI system is down where do idocs pile up?

    In idoc to file scenario, if XI system is down where do idocs pile up (get stuck)
    what tcode can I use to reprocess it?

    Sender System ,Check  BD87 .. you will see alll the IDOCs in Yellow state ..
    You can reprocess all the IDOCs in go from there .. if only they are in yellow state ...
    regards
    PS

  • FIle Content Conversion Problem in IDOC-XI-File Scenario

    Dear All,
    I am doing IDOC-XI-FILE scenario.
    I am facing one problem related to File Content Coversion.My requirement was to generate a dynamic file like <b>%store_code%_%current_date%_sitemaster.xml</b> , I have completed the dynamic generation successfully .
    Now there is slight change in the requirement ,<b>we have to suppress the current_date node of the xml content</b> . i have tried to suppress the current_date using these <b>DATE.fieldFixedLengths 0 , Date.fixedLengthTooShortHandling Cut</b> , But I am unable to suppress it Can some body provide me the details on this .
    The output xml version generated by Reciever file adapter is as below :
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:MT_SITE_MASTER xmlns:ns0="http://sample-xitest.com/sitemaster">
    - <SITE_DATA>
    <STORE_CODE>N002</STORE_CODE>
    <TITLE_MEDI>Company</TITLE_MEDI>
    <STORE_NAME>Mount Road</STORE_NAME>
    <STREET>Chennai</STREET>
    <COUNTRY>IN</COUNTRY>
    <SALES_TAX_NO>12345678910</SALES_TAX_NO>
    </SITE_DATA>
    </ns0:MT_SITE_MASTER>
    Plz provide me the code I have to write in the file content conversion .
    Thanks in advance
    Regards
    Prabhat

    If u see my earlier reply, I mentioned that u can not suppress the field from the one node.i.e Form SITE_DATA data type u can not suppress the field called CURRENT_DATE.
    My suggestion is that , modify the Data type in such a way that you will be having two nodes as I have mentioned earlier.  Then use the Suppress Logic for the Current Date.
    So it will look like this-
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:MT_SITE_MASTER xmlns:ns0="http://sample-xitest.com/sitemaster">
    - <SITE_DATA>
    <STORE_CODE>N002</STORE_CODE>
    <TITLE_MEDI>Company</TITLE_MEDI>
    <STORE_NAME>Mount Road</STORE_NAME>
    <STREET>Chennai</STREET>
    <COUNTRY>IN</COUNTRY>
    <SALES_TAX_NO>12345678910</SALES_TAX_NO>
    </SITE_DATA>
    <CURR_DATE>
       <CURRENT_DATE>20051105</CURRENT_DATE>
    </CURR_DATE>
    </ns0:MT_SITE_MASTER>
    So ur SITE_DATA is not having a field called CURRENT_DATE. This field is in separate node (segment ) called CURR_DATE. Now u can use the Suppress Logic for the same like this.
    CURR_DATE.fieldFixedLengths - 0
    CURR_DATE.fixedLengthTooShortHanling - Cut
    And in your Variable Substitution you can use the date from the other segment called CURR_DATE.
    Hope this solves ur problem.
    Regards,
    Moorthy

  • Error/Doubts in Idoc-XI-File scenario

    Dear All,
    I am doing one scenario in which DELIVERY idoc is posted from R/3 to XI and then from XI that idoc is to be sent as flat file to one local folder.
    For this scenario, I have done all ALE settings and I am able to see the idoc in XI in cXML format.Now I want to sent it as flat file.
    Now, for doing this I created 2 BS & 2 TS. 1 BS & TS of type Third Party for receiver & 1 BS & TS are of type Web as ABAP for sender. Then I have created one namespace in IR. I have not created any DT, MT, MI, MM becoz the structure of source and target file are same. Now, I created one IM in which I specified specified Type as "ABAP Class" & Mapping program name as one of the Z function module as specified in one of the SAP Guides.
    Then in ID, I created 2 Parties ie. one for Sender & one for receiver. Sender is having a communication channel of type Idoc & receiver is having communication channel of type File. And thn further Receiver Agreement, Inetrface Determination, Sender Agreement & Receiver Agreement are configured.
    In my system there is one scenario already configured which is using Delivery idoc so I have used party in my scenario for both sender & receiver.
    Now, when I am sending the idoc from R/3, I am able to see cXML in SXMB_MONI but it is taking receiver as the one which is defined for the already existing scenario but not the receiver defined by me.
    Can anybody guide if I have followed the correct steps & where I am doing the error.
    Warm Regards,
    N.Jain

    Hi ,
    Plese refer the following blogs ,
    IDoc to File
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    You have to do all this settings mentioned in the docuemnt:
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
    Also can you check this weblogs on the same:
    /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
    /people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
    /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
    /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    /people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
    Thanks ,
    Suvarna
    Award pts if  it helps .

  • 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

  • Pass system ack of JDBC adapter to ERP in IDoc - XI - JDBC scenario

    Dear all,
    i have an IDoc -> XI -> JDBC scenario (without using ccBPM). In the standard way the ERP system, sending the IDoc waits for an application acknowledgement. However the JDBC adapter is only capeable to send system acknowledgements.
    Is there a way to pass these acknowledgements to the IDoc status record?
    In help.sap.com (http://help.sap.com/saphelp_nwpi71/helpdata/en/ab/bdb13b00ae793be10000000a11402f/frameset.htm) under "IDoc Processing with the IDoc Adapter " there is a table that maps XI system/applic acknowledgement to IDoc status. So in my opinion the status record of my IDoc should at least chenge to the corresponding status for the system ack.
    Can anyone tell, if this is really working? What if I deactivate the acknowledgement request in the NOALE programm?
    In any case, can I achieve to transfer the system ack to the IDoc status without using a ccBPM?
    Many thanks and best regards
    Florian

    Is there a way to pass these acknowledgements to the IDoc status record?
    Without BPM, No.
    So in my opinion the status record of my IDoc should at least chenge to the corresponding status for the system ack.
    The ack referred here is related to idoc status whether it is properly reached till XI or not and not related to the JDBC ack.
    What if I deactivate the acknowledgement request in the NOALE programm?
    Then u won't have any ALEAUD message at sender R3.
    In any case, can I achieve to transfer the system ack to the IDoc status without using a ccBPM?
    No
    Regards,
    Prateek

  • IDoc missing in IDoc - XI - IDoc scenario

    Hello!
    The integration scenario is R/3 4.6C (IDoc) -> XI -> (IDoc) R/3 4.6C for DELFOR, ORDERS, ORDCHG, DESADV and ORDRSP.
    Now we switched to a new XI development system and the flow is working for all message types besides DELFOR.
    WE20 -> New XI Logical System Name -> DELFOR points to the new receiver port which referenced to the correct SM59 destination that is used by all other message types as well.
    There is also no error in SM58 in the sending R/3 system and the DELFOR IDocs are in status 12 in WE02 but when I search the IDoc number in IDX5 on XI the IDocs are not there.
    Does anybody have an idea where to find the DELFOR IDocs?
    Regards, Tanja

    Hello!
    > IDOC staus if it is sent out from R/3 should be 03 or
    > 12?
    First it was 03 but as I was not able to find it anywhere I ran a report and the status changed to 12 afterwards.
    > if IDOC is coming out of R/3 without any errors( sm58
    > no errors) then it should come in the SXMB_MONI in XI
    > as it usess th TRFC Port........
    Yes, this is also my understanding but it is not in SXMB_MONI nor in IDX5.
    > if it is not check the SMQ2 and SMQ! in both XI and
    > R/3...it cannot go anywere else (-:
    I have checked SMQ2 and SMQ1, the queues are empty in XI and R/3.
    Regards, Tanja

  • Integration server as logical system in IDoc to file scenario

    Hi,
    Will we configure integration server as logical system in IDoc to file scenario or the RFC destination related to the port will be suffice?
    For which logical system will the outbound partner profile configured?
    Regards,
    Gajendra.

    Hello,
    I feel that the RFC destination linked to the port is the key here.
    Because the scenario (IDoc to File) works in both the cases:
    Case 1: Used the logical system as Integration server
    Case 2: Used the logical system related to the file (third party) in the SLD.
    In both the above cases the RFC destination points to the integration server.
    Is this the case that in the XI scenarios (where IDoc are sent) the logical system name in the partner profile is just dummy and has not much significance??
    It is the port that matters and once the Idoc reaches XI the routing takes place based on the configuration in ID.
    Thanks.
    Regards,
    Gajendra.

  • How to suppress the Acknowledgement  Error in IDOC to File scenario?

    Hi -
    I got the status in SXMB_MONI as 'Processed Successfully' for the IDOC to File scenario but the Acknoledgement status throws an error saying 'Acknowledgement not possible'.
    I read one of the documents in the forums on how to suppress the acknowledgement using a table on R/3 side using IDXNOALE,
    i tried that option but i still get the 'Acknowledgement not possible' error.
    Is there any other way to suppress this error?
    Thanks,
    Tirumal

    Hi Tirumal,
    Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender. Acknowledgements are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed. Receiver adapters do not support application acknowledgments. The RNIF and CIDX adapters are exceptions to this rule, since they also support scenario-dependent application acknowledgments. Sender adapters of the Adapter Engine do not request any acknowledgments.
    This means, JDBC adapter does only send system acks, however IDoc adapter is requesting application acks. Therefore as mentioned by the previous poster, you have to disable acks for this scenario using report IDX_NOALE.
    Also go through these documents for any further help:
    http://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how to handle acknowledgments for idoc.pdf
    http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
    Regards,
    abhy

  • IDOC to JDBC scenario in case of Cost Element Group IDOC.

    This is an IDOC to JDBC scenario.
    The Cost Element Group IDOC is having different segments. The main segment E1COGH (1...unbound) is consisting of different subsegment like E1OGS (0...unbound) & E1COGV (0...unbound). The main segment (E1COGH) along with subsegments E1OGS & E1COGV) is occuring more that 1 times. I have to insert data into the table, which we can do in single rows (no hierarchy  is possible in tables). I have used "use one as many" in message mapping. Now if E1OGS or E1COGV is repeating in a single E1COGH segment then we dont get any error. But if I duplicate the main segment then I am getting runtime exception.
    Please suggest about how to map in this case.

    In my scenario:
         E1COGH
         |
          -> E1COGS
             E1COGV
    where     E1CGH -> Main segment
         E1COGS & E1COGV -> sub segment
    E1COGH -> 1..unbound
    E1COGS -> 1..unbound
    E1COGV -> 1..unbound
    At the target side I have created two Statement Structure (ie.Statement & Statement_1) . One for E1COGS (ie. Statement) & the other for E1COGV (ie. Statement_1).
    Case 1 ->  If E1COGS is present in the main segment E1COGH then it is mapped AS IS.
    Case 2 -> If E1COGS is not present in the main segment E1COGH then it is mapped as blank.
    This will be mapped with Statement & in the absence of E1COGS this Statement structure is SUPPRESSED.
    Similarly,
    Case 1 -> If E1COGV is present in the main segment E1COGH then it is mapped AS IS.
    Case 2 -> If E1COGV is not present in the main segment E1COGH then it is mapped as blank.
    This will be mapped with Statement_1 & in the absence of E1COGV this Statement_1 structure is SUPPRESSED.
    All the elements of the segment E1COGH, E1COGHT & E1COGHR are replicated in all the rows for X (no. of occurance of E1COGS) + Y (no. of occurance of E1COGV).
    While testing in Message Mapping, I am able to get the output as for multiple occurence of E1COGS & E1COGV in a single E1COGH.
    But if I increse the occurence of E1COGH the it is giving the following error :
    Runtime exception during processing target field mapping /ns0:MT_Cost_Element_Group_Response/Statement/DBtablename/access/GROUPNAME. The message is: Exception:[com.sap.aii.mappingtool.tf3.IllegalInstanceException: Too few values in first queue in function useOneAsMany. It must have the same number of contexts as second queue.] in class com.sap.aii.mappingtool.flib3.NodeFunctions method useOneAsMany[com.sap.aii.mappingtool.flib3.CollapseContexts@51197231, , ]
    Please suggest how to map the occurence of E1COGH simultaneously with the occurence of E1COGS & E1COGV.

  • RFC Destination not getting connected - IDoc to XI scenario

    Hi Everybody,
    I want send an IDoc from R/3 System to Xi, I have created Two logical systems (Sender and Receiver correspondingly) and i have assigned the clients to them.
    Once i create RFC destination, i have specified all my technical settings as well as Login/Security settings, once i click, "Remote Log On" it takes me directly to Login page of XI. Please guide me how to solve the problem. If i click Test---> Authorization, it prompts out with an error "Name and Password is incorrect (repeat Logon)", but i have given exact username and password.
    I am a fresher to XI.... please give me some documents related to IDoc to XI scenario step by step to [email protected] I would be grateful and appreciate you if u would help me to sort out this problem....
    Please give me step by step solutions.... Thanks in Advance...
    Regards/Guru

    Requirements in R3 system:
    1. Create RFC destination pointing to XI in SM59
    2. Create port for XI using we21
    3. create Outbound Entry in partner Profile for XI in we20.
    Requirements in XI system:
    1. Create Technical System pointing to the R3 system.
    2. create Business System pointing to the R3 system.
    If you want to send IIDOC out of XI,
    1. SM59 - Create RFC destination
    2. IDX1 - Create port
    3. IDX2 - Import Metadata.
    Note:u dont need a IDOC sender adapter or a Sender Agreement to sent a IDOC to XI.
    Check dis link for more info:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
    please refer to michel book on IDCO usage in XI
    Message was edited by:
            Sreeram Reddy

  • IDOC to file scenario

    Hi Experts,
    In IDOC to file scenario i did in this way.
    1)created logical system.
    2)Using SALE tcode I assign logical system to client ,created RFC destination,Port and Partner's profile.
    It is showing all the thing correct.
    3) In XI system , I configured using IDX1 and IDX2.
    Then I created the material and checked the status which is green in we05.
    But in tcode IDX5, the material is not coming.
    Here I am confused that why data is not coming to XI system.
    can anyone help me?
    Thanks
    Rabi

    Hi,
    The Following are the Possible checks
    1) Check in R/3 side SMQ1 & SMQ2
    2) Check in R/3 side SM58
       In R/3 system, Goto SM58 tcode and see if the IDOC have stuck up in Queue.
       If the entry is available then select it and press F6, to push it manually.
        This happens normally if IDOC stuck up in queues.
    3) Check in PI SMQ2 and IDX5
    regards,
    ganesh.

  • Sender port is not picking in PI for idoc to idoc scenario

    Hi Guru's,
    i am doing idoc to idoc scenario passing through sap pi ,while executing this idoc from client1 is successfully coming to PI, but while going from PI to client2 , i am getting error 51 (company code is defined for LS(logical system) for 1000 (vendor),i checked the configurations for sender idoc from pi ,it is taking a port value which is not present neither in xi nor in r/3 it is MDM interface port value i tried makking the port value constant in PI mapping ,but still same error is comming.
    idoc created with partner type LI in source system.i am posting it as LS in receiver system.
    Please help me  in resolving this error.
    Regards,
    reddy

    Hi,
    The error mentioned by you is not related to the port..but its related to the Application ...
    IDoc 51 means idoc has been received in R/3 client and when it tries to process it ended in error..
    Check with the functional consultant for the error you have received..
    HTH
    Rajesh

Maybe you are looking for