How to catch Posting error in File to IDoc Scenario?

I have successfully completed File to IDoc Scenario. Now I am interested in catching posting error. i.e., if mapping goes well and when IDoc is being sent to Recipient system then if any posting error is encountered, then a mail should go to a recipient.
Can anybody suggest the solution.
Regards,
Suraj Kumar

Hi Suraj,
this can be done by triggerring an alert to the recipient.chk out these links to trigger a alert
/people/sap.user72/blog/2005/01/14/alert-management--improving-monitoring-of-your-landscape
/people/sap.user72/blog/2005/01/14/alert-management--improving-monitoring-of-your-landscape
regards
jithesh

Similar Messages

  • Catch Mapping Error in File to IDoc scenario

    Configured BPM and now learning Error Handling. I know that through BPM we can handle system Errors, but I doubt whether Mapping error is a system error.
    I am interested to know the classification of errors with examples, preferably listing out all types of errors.
    Please provide some weblogs or explain briefly how to handle system and application errors through BPM.
    Thanks,
    Raja

    Hi Raja,
    You will need CCMS if you want to send the Alerts to external system or you want to access the ALerts from the transaction. You can capture your alerts without this also.
    When you go to Alert Configuration in the Runtime Workbench you can see Create Alert Rules. These rules are pertaining to the error generated in your AF,AE or IE.
    Once you have completed the whole config. The error happening in the AE, IE or AF would trigger the alert. you can see this in your Alert Inbox.
    The best would be if you go through the URL I have mentioned below.
    http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/content.htm
    You have to use BPM only if you want to do an activity after the alerts are raised. 
    Regards
    Vijaya
    Message was edited by: vijaya kumari

  • 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

  • Error in File-PI-Idoc scenario

    Dear All,
    While working on File-PI-Idoc scenario, I am getting the error as
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">UNAUTHORIZED</SAP:Code>
      <SAP:P1>401</SAP:P1>
      <SAP:P2>Unauthorized</SAP:P2>
      <SAP:P3>(See attachment HTMLError for details)</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    I have checked various other posts on the same error but still I am not able to resolve this.
    Please help me in resolving this error.
    reg,
    nj

    Nishu,
    Please check whether you have assigned the following roles to the particular user you are using for data communication.
    Roles:
    SAP_XI_IS_SERV_USER,
    SAP_XI_APPL_SERV_USER
    Regards,
    Sugata

  • 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 in file-ro-idoc scenario

    Hi! I'm trying this scenario https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
    And and have an error "Unable to convert the sender service MDM_to_CRM_BC to an ALE logical system". What maybe wrong in my scenario ?

    Vishnu, I'm very sorry, but:
    I've opened we02 ---> Inbound idocs ---> CRMXIF_PARTNER_SAVE_M  ---> Status 56
    Then I've opened my idoc and see:
    Control Rec
    Data records - idoc fields
    Status records --> 56 --> EDI: Partner profile not available
    Message no. E0332
    Diagnosis
    A partner profile could not be found with the following key:
    /ls_p1d    /LS/
    This involves the key fields of the table EDPP1:
    -PARNUM  partner number
    -PARTYP  partner type
    Procedure
    Please check the EDI partner profiles.
    What should I do now?

  • File to Idoc Scenario and Idoc to File Scenario's

    Hi Friends ,
    This is Shalini Shah,
    Please give me the details of how many busines sytems required in File to Idoc Scenario and Idoc to File sceanrio's.
    In business system , what is the name of Integration server(this name is related to XI ot Third Party)
    Please give me the full details of these two scenarios from Scratch.
    Thanks in Advance.
    Regards,
    Shalini Shah.

    Hi
    These r few links which gives u complete scenarios...
    for idoc to file:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
    for file to idoc:
    part1
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
    part2
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
    part 3
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
    This link is also good:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
    Troubleshooting File-to-IDOC Scenario in XI.
    /people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
    kindly rewards points if helpful.

  • Idocs with errors added status-56 in file to idoc scenario- how to rectify

    hi ,
    in file to idoc scenario when i m sending the file from ftp server to IS Retail,  file is successfully getting processed but the idoc is showing error ,when we see using WE05 tcode or BD87 , pl sugggest how to rectify it to make the status 53

    Hi,
    Have you configured the partner profile details? check these steps..
    1. In the receiver system you must configure the partner profile for your sender system in WE20.
    2. Add the IDoc message type to inbound parameters of the partner profile and configure the appropriate process code.
    2. Fill the Logical system name for your senderservice-->Adapter Specific identifiers in ID.
    <a href="/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi File-to-IDOC Scenario</a> By Venugopalarao
    <a href="/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi Steps for Posting IDOC's</a> By Ravikumar Allampalam
    Regards
    San

  • How to catch the error occurred in Integration Process, and then save it?

    1. how to catch the error occurred in Integration Process, and then save the detailed error message to the file?
    2. there are fault message type for inbound message interface, how to use the fault message type in IR?
    Thanks,
    Michael
    Message was edited by: Spring Tang
    inital
    Message was edited by: Spring Tang
    detailed message output
    Message was edited by: Spring Tang
    fault message type

    Hi Spring,
    If u give an exception step along with your Transformation Step, whenever some error occurs in your message mapping, this exception block wil be triggered.
    You can configure your exception block to do all exception processing that you want. This exception handling is like any other java Exceptio n Handler. You can do anything that you want in your exception handler block on the basis of your requirements.
    <i>If an exception is triggered at runtime, the system first searches for the relevant exception handler in surrounding blocks. If it does not find the correct exception handler, it continues the search in the next block in the block hierarchy.
    When the system finds the correct system handler, it stops all active steps in the block in which the exception handler is defined and then continues processing in the exception handler branch. Once the exception handler has finished processing, the process is continued after the block.
    If the system fails to find an exception handler, it terminates the integration process with an error.</i>
    Regards,
    Bhavesh

  • 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

  • File to IDoc scenario( Bypass)-- Error ( Segment is missing) -- urgent pls.

    Hi All,
    I am doing File to IDoc scenario( Bypass) for Orders05.
    File is picking succesfully and not posting the idoc in the SAP..
    My source file(idoc-xml) consists of all the required data to post the idoc including the segment 'E1EDK01'.
    but the error it is showing is <b>" Obligatory node 'E1EDK01' missing in the structure ORDERS05 "</b>
    Please suggest me ASAP what is going wrong .
    Thanks in Advance.
    Regards
    Seema.

    The source File is not the idoc XML. It is invalid. You might need to ask the source to change the XML or use a Mapping to do this.
    This is how it should look, ( check the parts in bold),
    <?xml version="1.0"?>
    <ORDERS05>
    <IDOC <b>BEGIN ="1"</b>>
    <EDI_DC40 SEGMENT="EDI_DC40">
    <DOCNUM>1</DOCNUM>
    <DIRECT>2</DIRECT>
    <IDOCTYP>ORDERS05</IDOCTYP>
    <CIMTYP></CIMTYP>
    <MESTYP>ORDERS</MESTYP>
    <SNDPOR>XXXXXXXXX</SNDPOR>
    <SNDPRT>LS</SNDPRT>
    <SNDPFC></SNDPFC>
    <SNDPRN>XXXXXXXX</SNDPRN>
    <RCVPOR>XXXXXX</RCVPOR>
    <RCVPRT>LS</RCVPRT>
    <RCVPFC></RCVPFC>
    <RCVPRN>XXXXXXXX</RCVPRN>
    <CREDAT>20070511</CREDAT>
    <CRETIM>152803</CRETIM>
    </EDI_DC40>
    <E1EDK01 <b>SEGMENT = "1"</b>><BELNR>AAAAAAAAA123</BELNR>
    </E1EDK01<b>SEGMENT = "1"</b>>
    <E1EDKA1 ><PARVW>EK</PARVW> <ILNNR>231654845121</ILNNR>
    </E1EDKA1>
    <E1EDKA1 <b>SEGMENT = "1"</b>><PARVW>LF</PARVW>
    <NAME1>international</NAME1>
    <NAME2>Delhi</NAME2>
    <ILNNR>2121211545</ILNNR>
    </E1EDKA1><E1EDK02 <b>SEGMENT = "1"</b>><QUALF>001</QUALF>
    <BELNR>AAAAAAAAA123</BELNR>
    </E1EDK02><E1EDK02 <b>SEGMENT = "1"</b>><QUALF>002</QUALF>
    <BELNR>AAAAAAAAA123</BELNR>
    </E1EDK02><E1EDP01><POSEX>45</POSEX>
    <E1EDP19 <b>SEGMENT = "1"</b>><QUALF>001</QUALF>
    <IDTNR>00000000002150059</IDTNR>
    <KTEXT>Reddy</KTEXT>
    </E1EDP19><E1EDP19>
    <QUALF>003</QUALF>
    <IDTNR>5484218521214</IDTNR>
    </E1EDP19></E1EDP01>
    </IDOC></ORDERS05>
    Regards
    Bhavesh
    PS : You need to add SEGMENT = "1" for every segment. Please do add it if I have missed in the XML above.

  • How can I include the Header Information....for a File to IDOC Scenario

    Hi,
    I made a File to IDOC Scenario with DEBMDM06 for MDM>XI>SAP R/3. The Header Information in the XML File which is at the XI end is Missing. For that reason In Tcode SXMB_MONI we are getting an Error that <b>"HEADER Information Missing: Message should Start with EDI_DC40"</b> i.e the Header Information.
      My Question is that whether we can do some changes in the Message mapping Step in the Integration Repository. I HardCoded the Few mandatory Fields that were there but it Again gave me the Same Error as above.
    Can you please Suggest some Solution for this. Since the data is Coming in from MDM part the Header information is not there but It actually Important as it has got all the Port Information.
      Kindly Inform me some Solutions.
    Thanks & Regards
    Somnath

    Hi Suraj,
      Thanks for ur Reply, but Since we are Doing a File to IDOC Scenario the IDOC DEBMDM is on the Right Side in Message Mapping and as U know it is Mandatory to Map an IDOC on the Right Part. EDI_DC40 is coming as it is there in the IDOC but our XML File Does not have that. If we Don't Map then it Becomes RED, which is an Error.
      Furthermore in the Receiver Agreement we have put the Necessary Details such as Sender Service and Receiver Service along with the IDOC Communication Channels.
      Can U give as a Better Insight on this Note how to check the Header Part as it is mandatory to MAP.We also tried to HARDCODE it by putting those Values and Mapping them to a Constant but it is Giving the Same Error.
    Thanks and Regards
    Somnath

  • File to IDoc scenario-CREMAS not getting posted

    Hi Experts,
    i am doing a file to idoc scenario in which i am giving the xml file from MDM ,consisting of Vendor Master data and posting the address and the general data into the ADRMAS and CREMAS idocs into the R/3 system.
    The problem that i am facing is that the ARMAS is getting posted correctly but the CREMAS is getting posted with the red signal,status 51.It says "Not authorized to change the Vendor Centrally."
    Can anyone please tell me what is the reason and the solution for this problem?
    Is this a data error or XI error?
    Thanks in advance,
    Shweta.

    Hi Shweta
    Status 51, 52 means Posting error 
    Please check wheteher all the configuration has been done or not
    SM59-rfc destination
    IDX1-port
    IDX2-load metadata
    we05-IDoc status records
    BD54-Create Partner Number
    We20-Create Partner Profile
    WE19-Testing IDoc Processing
    After That check the solution it is due to Authorization
    File to idoc - IDX5 Error
    Regards
    Abhishek Mahajan
    *Please reward points if helpful**

  • Regarding error in XI File to IDoc scenario

    Hi,
    when i was  doing file 2 idoc scenario i got this error "Unable to convert sender service to an ALE logical system". please resolve my issue as early as possible.

    Uday,
    Please go through these threads:
    Unable to convert the sender service to an ALE logical system
    How to convert Sender Party/Service  to a Logical System?
    Unable to convert the sender service to an ALE logical system
    BR,
    Alok
    Edited by: Alok Sharma on Jan 31, 2008 12:39 PM

  • File to IDOC scenario error...

    Hi all,
    we hhave created an File to Idoc scenario .
    we are getting the following error in SXMB_MONI t-code.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
      <SAP:P1>BUS_SENDER</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to convert sender service BUS_SENDER to an ALE logical system</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    can any one plz say wat this error might be..
    TIA
    Regards,
    Raj

    Hi,
    The problem occurs when sender and receiver business system or business service does not have a logical system name.
    ID - Integration Directory
    Posting the IDOC'S into SAP R/3 System, sender and receiver business system or business service requires the logical system name. If the business system (Web As ABAP) does not have the logical system name, then add the logical system for business system.
    If business system type = Web AS ABAP, then add the Logical system in Technical System level and Save.
    If business system type = Third-Party, then add the logical system in business system level and Save.
    If the business service does not have the logical system name in ID, it needs to be configured as follows.
    Go to ID and click the Business service -> Services -> Adapter Specific Identifiers. Enter the logical system name and Save.
    Apply and activate.
    hope this will help you.
    regards
    Aashish Sinha
    PS : reward points if helpful

Maybe you are looking for