IDOC error message

hi gurus
in my client place, when ever system sees 3 error messages(canceled PO, canceled line item in PO, free goods) it will automatically reject them, now my requirement is to add new error meesages to this automatic rejection program.
so please suggest me what would be the possible solution for this kind of issue.
thanks in advance
bob

Hi,
If u r using the Z Message type & Z funtion Function Module ,  these are the following steps to be checked...
Process Code : WE42.
Function Module : SE37
Message : WE81
Assign message : WE82
Assgin FM : we57
Characterstics OF FM : BD51
please check if ure function module interface is as per the template below:
IMPORTING
INPUT_METHOD LIKE BDWFAP_PAR-INPUTMETHD
MASS_PROCESSING LIKE BDWFAP_PAR-MASS_PROC
EXPORTING
WORKFLOW_RESULT LIKE BDWFAP_PAR-RESULT
APPLICATION_VARIABLE LIKE BDWFAP_PAR-APPL_VAR
IN_UPDATE_TASK LIKE BDWFAP_PAR-UPDATETASK
CALL_TRANSACTION_DONE LIKE BDWFAP_PAR-CALLTRANS
TABLES
IDOC_CONTRL STRUCTURE EDIDC
IDOC_DATA STRUCTURE EDIDD
IDOC_STATUS STRUCTURE BDIDOCSTAT
RETURN_VARIABLES STRUCTURE BDWFRETVAR
SERIALIZATION_INFO STRUCTURE BDI_SER
This is the general required format for IDoc inblund processing using FM.
Reward Points if it is Useful.
Thanks,
Manjunath MS

Similar Messages

  • Alert with IDOC error message

    Hi All
    We are configuring IDOC monitoring process in BPIM of Solution Manager. One of our requirement is Alert mail should include IDOC number and error message.
    Example
    IDOC Number: 8358000
    Status: 51
    Message:  Payment term not found
    Could you please tell how to configure error message in alert?
    Regards
    Raju

    Dear Raju,
    Idoc monitoring functions and capabilities are explained in following documentations:
    www.service.sap.com/bpm -> Media Library -> Technical Information-> Setup Guide - Interface Monitoring
    "Business Process Monitoring functionalities in SAP Solution Manager u2013 ALE / IDoc Monitoring"
    /people/johannes.fleig/blog/2008/05/25/new-business-process-monitoring-functionalities-in-sap-solution-manager-150-ale-idoc-monitoring
    As you can read in the above documentations, the alerts display the total and delta number of IDOCs found.
    In order to get the detailed error message for an alerted IDOC, you must click on the "Detail Info" button, to access the monitored system and read the buffered information for the alert.
    Thefore, it is not possible to get this information in the alert email as this text is not displayed per default.
    An idea to overcome this would be, that you setup IDOC monitoring for the different message types (i.e. MATMAS), and then
    specified further on key figure level using the parameters "Status Message ID" and "Status Message Number", and entering the Message  Text as Alert Name (column "short text" ). This way you would get the message text in the email.
    Please see the example in the above SDN Blog, screenshots 2 and 3.
    Maybe you could also check if, changing the email configuration via the BADI, you cold add the required informaitons to the mails. To get details on this please see another useful SDN blog:
    "Create your own auto-reaction messages in Business Process Monitoring via BAdI exit"
    /people/johannes.fleig/blog/2010/06/02/create-your-own-auto-reaction-messages-in-business-process-monitoring-via-badi-exit
    A complete description on how to set up auto-reaction messages in BPMon, and to implement and work with BAdIs in the BPMon environment, can be found in the u201CSetup Guide u2013 Auto-Reaction Messagesu201D which is available on SAP Service Marketplace, alias BPM (http://www.service.sap.com/bpm -> Media Library -> Technical Information).
    I hope this helps,
    kind reagrds,
    Marta
    SolMan Team

  • Inbound idoc error message

    Hello support team,
    I am developing a report in which i have to give a select option "date" when i entered the date in this select-option then after executing , the corresponding idoc type, idoc date, idoc number , idoc receiving site and idoc message that appers in Wper is shown.
    all the field are from EDIDC, EDID4, EDIDS tables except idoc message.
    Please suggest me from which table i found the message field .
    EX:
    site: 017
    idoc number : 6346213
    idoc type WPUWBW
    idoc date: 07.04.2010
    Idoc message:  "Delivery completed" indicator cannot be set for item 00018 .
    Thanks and Regards,
    Preeti thakur

    Hi digvijya,
    Its an Retail idoc and started with 'W'. These fields has not sufficient use for me. i tried it already.
    see this example. i need to fetch this type of error message "  Base unit of measure PC or article 000000000002014037 unknown  ". please suggest now.
    0000000027                                                                               
    idoc type:  WPUWBW Goods movements                                                                               
    idoc number: 1760035             idoc date:  07.04.2010                                                                               
    idoc message: Base unit of measure PC or article 000000000002014037
    Regards,
    Preeti

  • TS30000020 - IDOC error message

    Hi All,
    In our production system, we had some workflows got stuck up with SWF_RUN 609 error message. So i tried using SWPC
    transcation to resume those workflows. I worked fine. But some did not show up in SWPC and so i used SAP_WAPI_ADM_WORKFLOW_RESUME Fm to resume, it also didnt work. So i searched through sdn and some other sites and found out the standard report   "RSWWERRE - Report for restarting workitems with temporary errors", and tried that. My workflows got resumed. But over 2500 new workflow with TS30000020 and description "EDI: Incorrect status  for inbound IDoc" got triggered without any agents and it went all users. Iam not aware of IDOC.  Can anyone suggest why this has happened and how should i overcome this?
    Regards,
    Kevin.
    Edited by: kevin.jk on Jul 27, 2011 7:54 AM

    Hello,
    RSWWERRE is normally scheduled to run periodically (usually every 20 mins) to handle temporary errors.
    I'm not sure about how these IDOC workflows got started. If they're not necessary then you can logically delete them.
    If you look in the IDOC workflows, when does it sya they started? Recently?
    regards
    Rick Bakker
    hanabi technology

  • Idoc error message "This change has been superseded by another"

    Hi,
    I am trying to process multiple idocs together which will create/update info records using the program RBDAPP01.  But it is processing correctly only single record and for all other records its giving the error message "This change has been superseded by another"
    The function module used for processing is IDOC_INPUT_INFREC and when I checked this error is coming from it.  Infact it is comparing the output of FM IDOC_SERIALIZATION_CHECK  and populating the error message.
    If we process the same record in single, it is processing correctly and not giving such kind of message.
    I am not sure what is happening here.  Please help.

    I was trying to create multiple PIR for same material using multiple idocs.  And that is the reason it is giving the error when trying to process the idocs together. When I tried changing the same into one record ie different PIR for same article in one idoc, its processing correctly.

  • IDOC : error message 20 : Error triggering EDI subsystem

    Hi,
          I am creating an extended idoc for WP_PLU message type . I am sending the data from my LS to KU(Customer).
    In WE20, I have configured the message type for that KU. I am using an XML port .
    The problem is that the Idoc file is getting created properly but it is thowing this message : Error 20 : Error triggering EDI Subsystem.
    In WE21 , I have ticked the Start subsytem radiobutton. I am not using any Middleware.It is simple data transfer .
    Same thing is working file when I am assigning a File port instead of XML port.
    Please help me on this urgently.

    Dear All,
    Many thanks for all suggestions. Very appreciated it guys.
    My problem solved, the issue was actually from the Functional configuration.
    After debugging i found out that there's a option to generate a trigger file (related to POS Outbound). If you tick this option then maybe you have to maintain the download path somewhere.
    My case is the option was ticked but system can't find the path.
    SAP put as error message 20 in the IDOC status.
    This maybe can explain also why i still can see my IDOC reached XI and file generated. Since the issue is not really related to any setting in IDOC but more to business configuration.
    Best Regards,
    Victor.

  • EDI IDOC error message

    Dear Team,
    may I kindly ask you to help me with regard to an error message I am getting for inbound idoc message type INVOIC.
    The message is "Field format is incorrect" and 'Field content is incorrect". Segment E1EDS01.
    I have tried various ways of fixing this but havent succeeded yet.
    Has anybody encountered this problem and how has one fixed it.
    Thanks

    Hi Dany,
    First identify which field value in that segment is throwing the error.
    For this, first see which all fields are filled in the error IDOC now.
    Then clear all values, and fill same value in one field at at time, and see if IDOC goes into error.
    Once you identify which field is having wrong format, you can check in detail.
    Regards,
    Nisha Vengal.

  • Where can get IDOC Error Message from Data base tables

    Hi ,
    i am automating idoc  checking process,in which i am getting control record from EDIDC tables,now i need to fetch Error message
    using this idoc no.
    How can fetch   error message text ?
    Thanks in advance.
    Regards
    sarath

    Hi its a structure, it doesnt store data.
    Take it from the table specified,
    Pass STAMID,STAMNO,STAPA1,STAPA2,STAPA3,STAPA4 to function module MESSAGE_PREPARE and you will get the message text.
    Also check the function module IDOC_READ_COMPLETELY

  • Viewing Idoc Error Message

    Hi,
    We have Idocs where the correct error message is obtained after going to WE02, clicking on the icon next to 51 status and then on the next screen clicking on the application log button.
    We have hundreds of Idocs in failed status and want to view the error messages, displayed after clicking on the application log button. Is there an easier way to do this, where I can see the error messages of all the Idocs at one shot rather then going inside each and everyone of the Idocs?
    Any help would be appreciated.
    Regards,
    Mick

    Thanks Chandra.
    But this FM will give me the error message that is displayed after you click on the icon next to 51 status.
    The requirement is that after you click on the icon next to 51 status, on the next screen click on the application log button. We want to see the error message displayed here.
    Also as mentioned earlier we have hundreds of Idocs in failed status and would like to see the error messages at one shot and not one idoc at a time.
    Regards,
    Mick

  • Re: IDOC error message

    Please help me with this error message when processing IDOC.
    Message no.AM034 : An address has already been created for this handle.
    I have checked the sales order and delivery, and there is no duplication.
    Can anyone tell what is this error message means?
    TQ

    Hello Sreelakshmin,
    Please refere to the following SAP note : 651008
    Hope this will help,
    Best regards,
    GL
    http://newitbizz.blogspot.com/

  • Idoc error message report

    To see most of the EDI IDOC errors, we need to go into additional log to check that, is there any report were we can get list of idoc errors in one go for the users
    Can any one tell me the tables which get updated when error shows up
    pls help
    vin

    The tables are EDIDC (IDoc control segment) and EDIDS (Status messages). From EDIDC you can select IDoc numbers that have errors (check STATUS field) and then link EDIDS by DOCNUM and STATUS (note that there might be multiple entries, you may use additional criteria to skip what you don't need).
    If you need the segment data then the table is EDID4 (or could be another number depending on the release).
    Hope this helps.

  • Outbound idoc error message

    Dear all,
    When i am manually create a direct request for POS outbound, the system shows the error message as below. It cannot generate an outbound idoc. Do anyone know how to detect this error and how to solve this problem?
    Error message:
    Processing Status
    Recipient: XX01
      IDocs created
         None
         Trigger file for status ID: 00000000260056
         does not have to be created       No messages needed
    Thanks and regards
    Chris

    Dear all,
    i have solved the problem. thanks you for your attention.
    Chris

  • IDOC  error  message in SRM 3.5

    Hi all,
       I am using SRM 3.5(EBP 3.0)with ITS and R/3 4.7.
    While executing the service "Create shopping cart",after  ordering the item i.e. saving the shopping cart,the approval workflow is executed but when i login as the approver and go to the workflow entries in the approver's inbox, i get an error message stating, "error in MW-BDOC-Processing, Type BUPA_MAIN_ID".
        Is this error due to some customizing setting in the middleware or somethin else?Please Help.
    Thanks & regards,
    Deepti.

    It seems that plug-ins are not automatically "transferred" to LR 3.6. You have to copy the plug-in from the "Modules" folder of your previous LR version to the "Modules" folder of Lr 3.6 - or if there is no "Modules" folder yet, create one.
    The "Modules" folder is in your LR-folder in Program files on your C-drive.
    WW

  • IDOC Error Message no. B1500

    Hi Experts,
    I am trying to generate an IDOC using the 'Standard inbound' tool of Transaction WE19 & I am getting the message that 'IDOC was saved and processed by function APPL_IDOC_INPUTI' however in transaction WE05 this IDOC shows status 51 & gives an error that 'The IDoc interface is not complete for message type HRSM_A' (Message no. B1500). What should be the problem, Please help...
    Thanks & Regards,
    Amit

    Hi Amit,
    well, it could be the reason that your IDOC is not filling correctly. Which Infotypes are you updating? Mind if I have a look at your IDOC XML? You can mask sensitive information of course.
    To find the reference documentation on IDOC type HRMD_A05, go to WE60 and input HRMD_A05.
    By the way, there're some flags in segment E1PLOGI which are quite important.
    1)OPERA: By updating records you should set it as "u".
    2)OTYPE: for personal master data, here we should have a "P"
    3)PLVAR: check table T778P, which is your current plan variant?(you may follow your HR consultant's advice here) Then fill it here too.
    Here's an example, although it's an outbound, but hopefully it'll help:
    <?xml version="1.0" encoding="UTF-8"?>
    <HRMD_A>
         <IDOC BEGIN="1">
              <E1PLOGI SEGMENT="1">
                   <PLVAR>01</PLVAR>
                   <OTYPE>P</OTYPE>
                   <OBJID>00000001</OBJID>
                   <OPERA>I</OPERA>
                   <E1PITYP SEGMENT="1">
                        <PLVAR>01</PLVAR>
                        <OTYPE>P</OTYPE>
                        <OBJID>00000001</OBJID>
                        <INFTY>0000</INFTY>
                        <BEGDA>18000101</BEGDA>
                        <ENDDA>99991231</ENDDA>
                        <E1P0000 SEGMENT="1">
                             <PERNR>00000001</PERNR>
                             <INFTY>0000</INFTY>
                             <ENDDA>20080331</ENDDA>
                             <BEGDA>20080101</BEGDA>
                             <SEQNR>000</SEQNR>
                             <AEDTM>20081023</AEDTM>
                             <UNAME>CLN</UNAME>
                             <MASSN>01</MASSN>
                             <STAT2>3</STAT2>
                             <STAT3>1</STAT3>
                        </E1P0000>
                        <E1P0000 SEGMENT="1">
                             <PERNR>00000001</PERNR>
                             <INFTY>0000</INFTY>
                             <ENDDA>20080531</ENDDA>
                             <BEGDA>20080401</BEGDA>
                             <SEQNR>000</SEQNR>
                             <AEDTM>20081112</AEDTM>
                             <UNAME>CLN</UNAME>
                             <MASSN>02</MASSN>
                             <STAT2>3</STAT2>
                             <STAT3>1</STAT3>
                        </E1P0000>
                        <E1P0000 SEGMENT="1">
                             <PERNR>00000001</PERNR>
                             <INFTY>0000</INFTY>
                             <ENDDA>99991231</ENDDA>
                             <BEGDA>20080601</BEGDA>
                             <SEQNR>000</SEQNR>
                             <AEDTM>20081112</AEDTM>
                             <UNAME>CLN</UNAME>
                             <MASSN>02</MASSN>
                             <STAT2>3</STAT2>
                             <STAT3>1</STAT3>
                        </E1P0000>
                   </E1PITYP>
                   <E1PITYP SEGMENT="1">
                        <PLVAR>01</PLVAR>
                        <OTYPE>P</OTYPE>
                        <OBJID>00000001</OBJID>
                        <INFTY>0001</INFTY>
                        <BEGDA>18000101</BEGDA>
                        <ENDDA>99991231</ENDDA>
                        <E1P0001 SEGMENT="1">
                             <PERNR>00000001</PERNR>
                             <INFTY>0001</INFTY>
                             <ENDDA>20080331</ENDDA>
                             <BEGDA>20080101</BEGDA>
                             <SEQNR>000</SEQNR>
                             <AEDTM>20081023</AEDTM>
                             <UNAME>CLN</UNAME>
                             <BUKRS>1000</BUKRS>
                             <WERKS>1000</WERKS>
                             <PERSG>1</PERSG>
                             <PERSK>21</PERSK>
                             <VDSK1>1000</VDSK1>
                             <BTRTL>0001</BTRTL>
                             <JUPER>0001</JUPER>
                             <ABKRS>01</ABKRS>
                             <ORGEH>00000000</ORGEH>
                             <PLANS>00000000</PLANS>
                             <STELL>00000000</STELL>
                             <SACHA>001</SACHA>
                             <SACHP>001</SACHP>
                             <SACHZ>001</SACHZ>
                             <SNAME>TARILFER ALLGMEIN GEWERBLICHER</SNAME>
                             <ENAME>Gewerblicher Tarilfer allgmein</ENAME>
                             <OTYPE>S</OTYPE>
                             <SBMOD>1000</SBMOD>
                             <KOKRS>1000</KOKRS>
                        </E1P0001>
                        <E1P0001 SEGMENT="1">
                             <PERNR>00000001</PERNR>
                             <INFTY>0001</INFTY>
                             <ENDDA>20080531</ENDDA>
                             <BEGDA>20080401</BEGDA>
                             <SEQNR>000</SEQNR>
                             <AEDTM>20081112</AEDTM>
                             <UNAME>THIEDEPE</UNAME>
                             <BUKRS>1000</BUKRS>
                             <WERKS>1000</WERKS>
                             <PERSG>1</PERSG>
                             <PERSK>10</PERSK>
                             <VDSK1>1000</VDSK1>
                             <BTRTL>0001</BTRTL>
                             <JUPER>0001</JUPER>
                             <ABKRS>01</ABKRS>
                             <ORGEH>00000000</ORGEH>
                             <PLANS>00000000</PLANS>
                             <STELL>00000000</STELL>
                             <SACHA>001</SACHA>
                             <SACHP>001</SACHP>
                             <SACHZ>001</SACHZ>
                             <SNAME>TARILFER ALLGMEIN GEWERBLICHER</SNAME>
                             <ENAME>Gewerblicher Tarilfer allgmein</ENAME>
                             <OTYPE>S</OTYPE>
                             <SBMOD>1000</SBMOD>
                             <KOKRS>1000</KOKRS>
                        </E1P0001>
                        <E1P0001 SEGMENT="1">
                             <PERNR>00000001</PERNR>
                             <INFTY>0001</INFTY>
                             <ENDDA>99991231</ENDDA>
                             <BEGDA>20080601</BEGDA>
                             <SEQNR>000</SEQNR>
                             <AEDTM>20081112</AEDTM>
                             <UNAME>THIEDEPE</UNAME>
                             <BUKRS>1000</BUKRS>
                             <WERKS>1000</WERKS>
                             <PERSG>1</PERSG>
                             <PERSK>21</PERSK>
                             <VDSK1>1000</VDSK1>
                             <BTRTL>0001</BTRTL>
                             <JUPER>0001</JUPER>
                             <ABKRS>01</ABKRS>
                             <ORGEH>00000000</ORGEH>
                             <PLANS>00000000</PLANS>
                             <STELL>00000000</STELL>
                             <SACHA>001</SACHA>
                             <SACHP>001</SACHP>
                             <SACHZ>001</SACHZ>
                             <SNAME>TARILFER ALLGMEIN GEWERBLICHER</SNAME>
                             <ENAME>Gewerblicher Tarilfer allgmein</ENAME>
                             <OTYPE>S</OTYPE>
                             <SBMOD>1000</SBMOD>
                             <KOKRS>1000</KOKRS>
                        </E1P0001>
                   </E1PITYP>
                   <E1PITYP SEGMENT="1">
                        <PLVAR>01</PLVAR>
                        <OTYPE>P</OTYPE>
                        <OBJID>00000001</OBJID>
                        <INFTY>0002</INFTY>
                        <BEGDA>18000101</BEGDA>
                        <ENDDA>99991231</ENDDA>
                        <LONG_INFTY>X</LONG_INFTY>
                        <E1P0002 SEGMENT="1">
                             <PERNR>00000001</PERNR>
                             <INFTY>0002</INFTY>
                             <ENDDA>99991231</ENDDA>
                             <BEGDA>19700101</BEGDA>
                             <SEQNR>000</SEQNR>
                             <AEDTM>20081023</AEDTM>
                             <UNAME>SBE</UNAME>
                             <INITS>12345</INITS>
                             <NACHN>Tarilfer allgmein</NACHN>
                             <VORNA>Gewerblicher</VORNA>
                             <KNZNM>00</KNZNM>
                             <ANRED>1</ANRED>
                             <GESCH>1</GESCH>
                             <GBDAT>19700101</GBDAT>
                             <GBORT>Bielefeld</GBORT>
                             <NATIO>DE</NATIO>
                             <SPRSL>D</SPRSL>
                             <FAMDT>00000000</FAMDT>
                             <ANZKD>0</ANZKD>
                             <GBPAS>19700101</GBPAS>
                             <GBJHR>1970</GBJHR>
                             <GBMON>01</GBMON>
                             <GBTAG>01</GBTAG>
                             <NCHMC>TARILFER ALLGMEIN</NCHMC>
                             <VNAMC>GEWERBLICHER</VNAMC>
                             <SPRSL_ISO>DE</SPRSL_ISO>
                             <NACHN_40>Tarilfer allgmein</NACHN_40>
                             <VORNA_40>Gewerblicher</VORNA_40>
                             <GBORT_40>Bielefeld</GBORT_40>
                             <E1Q0002 SEGMENT="1">
                                  <PERNR>00000001</PERNR>
                                  <INFTY>0002</INFTY>
                                  <ENDDA>99991231</ENDDA>
                                  <BEGDA>19700101</BEGDA>
                                  <SEQNR>000</SEQNR>
                             </E1Q0002>
                        </E1P0002>
                   </E1PITYP>
                   <E1PITYP SEGMENT="1">
                        <PLVAR>01</PLVAR>
                        <OTYPE>P</OTYPE>
                        <OBJID>00000001</OBJID>
                        <INFTY>0006</INFTY>
                        <SUBTY>1</SUBTY>
                        <BEGDA>18000101</BEGDA>
                        <ENDDA>99991231</ENDDA>
                        <E1P0006 SEGMENT="1">
                             <PERNR>00000001</PERNR>
                             <INFTY>0006</INFTY>
                             <SUBTY>1</SUBTY>
                             <ENDDA>99991231</ENDDA>
                             <BEGDA>20080101</BEGDA>
                             <SEQNR>000</SEQNR>
                             <AEDTM>20081031</AEDTM>
                             <UNAME>THIEDEPE</UNAME>
                             <ANSSA>1</ANSSA>
                             <STRAS>Teststr. 1</STRAS>
                             <ORT01>Bielefeld</ORT01>
                             <PSTLZ>33611</PSTLZ>
                             <LAND1>DE</LAND1>
                             <ENTKM>0</ENTKM>
                             <HSNMR>000000</HSNMR>
                             <ENTK2>0</ENTK2>
                             <RAILW>0</RAILW>
                             <STRAS_40>Teststr. 1</STRAS_40>
                             <ORT01_40>Bielefeld</ORT01_40>
                        </E1P0006>
                   </E1PITYP>
                   <E1PITYP SEGMENT="1">
                        <PLVAR>01</PLVAR>
                        <OTYPE>P</OTYPE>
                        <OBJID>00000001</OBJID>
                        <INFTY>0016</INFTY>
                        <BEGDA>18000101</BEGDA>
                        <ENDDA>99991231</ENDDA>
                        <E1P0016 SEGMENT="1">
                             <PERNR>00000001</PERNR>
                             <INFTY>0016</INFTY>
                             <ENDDA>99991231</ENDDA>
                             <BEGDA>20080101</BEGDA>
                             <SEQNR>000</SEQNR>
                             <AEDTM>20081023</AEDTM>
                             <UNAME>CLN</UNAME>
                             <LFZFR>42</LFZFR>
                             <LFZZH>010</LFZZH>
                             <LFZSO>00</LFZSO>
                             <KGZFR>0</KGZFR>
                             <PRBZT>6</PRBZT>
                             <PRBEH>012</PRBEH>
                             <ARBER>00000000</ARBER>
                             <EINDT>00000000</EINDT>
                             <KONDT>00000000</KONDT>
                             <CTTYP>01</CTTYP>
                             <CTEDT>00000000</CTEDT>
                             <CTBEG>00000000</CTBEG>
                        </E1P0016>
                   </E1PITYP>
              </E1PLOGI>
         </IDOC>
    </HRMD_A>
    Otherwise, I suggest you set a breakpoint and debug it.
    Regards,
    Chen

  • IDoc error :'Message has error at outbound side'.

    Hi Experts,
    am working on JMS-->IDoc, where TIBCO sends MBGMCR01 IDoc to ECC through XI .
    in SXMB_MONI : shows red flag in outbound:with the message as 'Message has error at outbound side'.
    please, suggest  to solve the issue.
    thank you,
    <b>MK</b>

    Hi
    Have a look this
    Message has error on outbound side in sxmb_moni
    BPM - Message has error on the outbound side
    Reprocess a message with error at outbound side

Maybe you are looking for

  • Function module import parameter....Urgent

    Hi Experts, I am using User Exit M06E0004 which is using <b>FM EXIT_SAPLEBND_002</b>. It has 4 inport parameters I_CEKKO             LIKE CEKKO           IT_BEKPO            TYPE MMPUR_BEKPO     IT_BEKET            TYPE MMPUR_BEKET     IT_EKKNU      

  • Issue in creating data server for xml in ODI

    Hi, I have a XMl which has a size around 95 MB. When i tried to create data server in ODI for this xml file. I encounter below error, "oracle.odi.jdbc.datasource.ConnectionTimeoutException: A login timeout occured while connecting to the database at

  • Mapping with transient filed

    Hello, how can a transient field get "offerlistsize" a value of subquery "select count(*) from OFFER o where o.REQUEST_ID = rr.ID" from db? Entity Bean RawRequest.java @SqlResultSetMapping(name="GetOfferSize", entities={         @EntityResult(entityC

  • Problem with losing configuration of DAQPad 6508...software related???

    I started the below thread in the Digital I/O forum, but now I'm seeing that it could possibly be software related...but I'm not sure. Any help on this would be appreciated: http://forums.ni.com/ni/board/message?board.id=70&message.id=6107 Thanks! Ry

  • Importing/exporting playlists in Tunes - will take decades

    Is there a program that can do this effeciently or another method than ordinary manual selection? It's really frustrating having to select one and one playlist to import at a time when you have hundreds... Is there a way to import/export playlist fol