IDOC INBOUND Error !

Actually I received a test IDOC ( FIDCCP02) from middleware see beyond, when it was dropped in our R/3 Box. it has a status 51 - Application Document not posted ( the application failed to return a status record to the ALE layer )
I tried to reprocess with prog. RBDMANIN it didn’t worked and I tried BD87 but it says: this is due to an error in the application function module which processed the inbound IDOC.
Then, I tried to post the IDOC  through WE19 with particular IDOC number, the test IDOC has been created and it is surprisingly posing data to custom segment ( user exit developed for particular IDOC extension ), Actually this custom segment has diverted to custom table. But it is not posting standard segments data to standard tables.
As per my understanding it is posting the data for the user exit which I developed in FM.  But the FM is not triggered properly for the standard segments. May be FM executing only user exit  developed for IDOC extension .
can some one pls tell me  what is the problem behind this ? Appropriate suggestions would be appreciated.

Seshu,
Thank you.
yes checked it with partner profiles, in WE19 by giving the existing idoc number and click on standard inbound option on the menu, it indicates green light, that means partner profiles or correct right ? or do you think it may show like that ?
if problem with the function module, what could be the problem ? whether the user exit  which i developed interpreting the triggering of FM ?
actually i receiving IDOC from see beyond, so created RFC destination for See beyond with TCP/IP Connection, with connection type: T & i used same Program ID which they used at Outbound R/3 system .
Pls suggested me accordingly
Regards,
Sridhar

Similar Messages

  • Idoc inbound error status code 56

    Hi,
       when i am sending custom idoc from source system to destination , idoc sent successfully from source system .But  in the receiver system idoc status code is 56 ( idoc with errors added) .
    partner profile also available in the receiver system. How to solve the error.can any one pls give me the solution.
                                                                                    Regards,
                                                                                    Suhash.

    Hi,
    Check this link..[IDOC Status code 56 !!   |IDOC Status code 56 !!]
    [Re: Status 56 - IDOC with errors added   |Status 56 -  IDOC with errors added]
    Edited by: Avinash Kodarapu on Mar 19, 2009 4:55 PM

  • BD87 idoc inbound error for message type HRMD_A

    Hello there,
    I am getting below error  while fetching Inbound idoc in tcode BD87, see log below from ST22
    Short text
        An SQL error occurred when executing Native SQL.
    What happened?
        The error "-10328" occurred in the current database connection "LCA".
    What can you do?
        Note down which actions and inputs caused the error.
        To process the problem further, contact you SAP system
        administrator.
        Using Transaction ST22 for ABAP Dump Analysis, you can look
        at and manage termination messages, and you can also
        keep them for a long time.
    How to correct the error
        Database error text........: "Mismatch of number of stream members for
         parameter (3) (application 6, database 9)."
        Database error code........: "-10328"
        Triggering SQL statement...: "EXECUTE PROCEDURE "SIM_SIMSESSION_CONTROL""
        Internal call code.........: "[DBDS/NEW DSQL]"
        Please check the entries in the system log (Transaction SM21).
        If the error occures in a non-modified SAP program, you may be able to
        find an interim solution in an SAP Note.
        If you have access to SAP Notes, carry out a search with the following
        keywords:
        "DBIF_DSQL2_SQL_ERROR" "CX_SY_NATIVE_SQL_ERROR"
        "/SAPAPO/SAPLOM_CORE" or "/SAPAPO/LOM_COREU07"
        "SIMSCTRL_EXEC_COM"
        If you cannot solve the problem yourself and want to send an error
        notification to SAP, include the following information:
        1. The description of the current problem (short dump)
           To save the description, choose "System->List->Save->Local File
        (Unconverted)".
        2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    The exception must either be prevented, caught within proedure
    "SIMSCTRL_EXEC_COM" "(FORM)", or its possible occurrence must be declared in
    the
    Do we need SAP_APO in order to install LiveCache?
    We have below landsacpe
    - SAP ECC 6 EHP4 with SQL server 2005 S BACKEND
    -LCAPPS Component release 2005_700 with SP
    SAPKIBHD05.
    - We dont have SAP_APO component
    -SAP LiveCache system have MAXDB 7.7.04.29 as backend.
    - Live cache client is installed on same SAP ECC system where we have SAP ECC EHP4 system.
    any suggestion how to resolve it?
    Mani

    >
    Mani wrote:
    > I installed a standalone server and i need it only for SAP HR (specifically Idoc processing in SAP HR Human capital management module). But i am getting error while running ibound idoc process.
    > So Do i still need SAP_APO component?
    I never heard of this specific scenario for liveCache usage in the past 7 years working in SAP support on the liveCache component.
    Might be useful if you provide some more details (documentation, notes, links) that describe this usage scenario.
    In any case you will need to have a liveCache version that is compatible to your application ABAP coding.
    The error message you posted indicates that your liveCache version does not fit your application version (or vice versa).
    > I installed SAP MAxDB and LiveCache buid using Installation master DVD for SAP ERP. So i think i followed the right method as specified in installation guide.
    Be precise, please. Which installation guide? There are hundreds of them - not THE installation guide.
    > Secondly can you help me something specific to my problem in coding form?
    Already did.
    > i tried in LC10, using LCA monitoring i am not able to run SQLDBC trace under
    > LCA >> LiveCache Monitoring >> Tools
    > but i am not able to execute the same, is it a error or we need to configure something?
    Well, the liveCache needs to be integrated into the LC10. You'd do this in transaction SM59 - but as you've followed an installation guide, this would have been covered in it...
    > Operational status is active green light, below is file status.
    >
    >
    KNLMSG     KnlMsg     1.098.697     28.01.2011     06:59:55     Database Messages     ASCII
    > KNLMSGARC     KnlMsgArchive     8.192     28.01.2011     06:59:50     Database Errors     ASCII
    > KNLMSGOLD     KnlMsg.old     342.663     28.01.2011     06:59:50     Database Messages (OLD)     ASCII
    > KNLTRC     knltrace     6.209.536     28.01.2011     06:59:56     Database Trace (Raw/Binary)     BINARY
    > BACKHIST     dbm.knl     570     10.01.2011     06:18:41     Backup History     ASCII
    > DBMPRT     dbm.prt     133.843     29.01.2011     11:41:27     Database Manager Log File     ASCII
    > DBMPAHI     L00.pah     214.225     10.01.2011     06:18:16     Database Parameter History     ASCII
    > LCINIT     lcinit.log     15.299     28.01.2011     07:00:00     LiveCache Initialisation     ASCII
    > LCINITCMD     lcinit.bat     3.047     28.10.2008     14:45:51     LiveCache Initialisation Script     ASCII
    > LCINITHIS     lcinit.his     46.742     28.01.2011     07:00:00     LiveCache Initialisation History     ASCII
    > INSTPRT     dbm.ins     863.981     10.01.2011     06:18:47     Installation Log File     ASCII
    > DIAGDIR     File     0     10.01.2011     06:18:18     Diagnose History     DIRECTORY
    > ANALYZER     analyzer     0     29.01.2011     00:00:36     DB Analyzer File     DIRECTORY
    > LCTRC#init.his     lcinit.his     46.742     28.01.2011     07:00:00     LiveCache Trace (ASCII)     ASCII
    > LCTRC#init.log     lcinit.log     15.299     28.01.2011     07:00:00     LiveCache Trace (ASCII)     ASCII
    > LCTRC#_apo_version.txt     lc_apo_version.txt     164     28.01.2011     07:00:00     LiveCache Trace (ASCII)     ASCII
    >
    > any clue whats wrong?
    > Mani
    The only thing this tells us is: the liveCache instance itself apparently comes up and writes out the standard log files.
    That's it.
    As I already tried to explain, the problem seems to be the dependence between your application and the liveCache version.
    Usually I'd recommend to open a support message for this, but the colleagues would (hopefully) ask the same questions as I did.
    regards,
    Lars

  • IDOC INBOUND ERROR ( STATUS - 51 )

    hi all,
    when procssing the inbound idoc's i am getting an error ststing that " No status record was passed to ALE by the application " what may be the problem .
    helpfull answers will be rewarded with points.
    regards,
    murali.

    See the code in this function module IDOC_INPUT_CLOSE. I think, even though you are writing the status records to the database, you need to send a status back to XI(ALE) with your status record. That is why I think you are getting this message.
    In WE02, what do you see as status records for 1)original IDOC and 2) your new IDOCs?
    Are you getting this message after you create the new IDOCs or before you split them? Can you tell us what is the logic of your function module(just design logic not the code)?
    Regards,
    Srinivas

  • Idoc inbound error - encoding question

    Hello,
       I receive idoc file from a parnter.
       I create a File Ports(WE21) : Non-unicode format and Checked 'Continue Despite Conversion Error'.
       The partner send to us a file with ASCII-encoding including  German NÄHER .
       In WE02, I found the line with German NÄHER disordered.  ÄH became char  腍 ，but I have set 'Continue Despite Conversion Error'.
       like this:
               PCKAR     SACK NICHT N腍ER SPEZIFIZIERT      0
               PCKNR     000SAC                            8
               ANZAR     00.000        0
               VBELN     301866818                         0
               POSNR     00060                        6
               BTGEW     000.000          0
               NTGEW     .000             1
               TARAG     .000             K
               GEWEI     GM0
               BTVOL     .000             0
       If the parnter don't want to change the encoding, Can I do something to make it worked ?
                                                                                    Thanks.

    I post the same question on Expert Forums » Application Server » Unicode
    It's OK now.
    ======================
    Good way:
    Add this code before CALL FUNCTION 'EDI_DATA_INCOMING'
    SET LOCALE LANGUAGE 'D'. "table t002
    Nils Buerckel's answer :
    Hi Harry,
    this is not a conversion error.
    The file contains Latin-1 data with the special character "Ä".
    Now I assume you use as logon language in the Unicode system ZH (or another Asian language) ... ?
    Then the system evaluates SY-LANGU and converts the Non-Unicode file based on the Asian code page.
    Then ÄH will be interpreted as 腍. Hence the system gets a word with 4 characters instead of 5.
    This can lead to shiftings in the whole idoc and the idoc might be invalid.
    Therefore I would propose to upload the idoc using logon language EN or change it via "setlocale " in abap code.
    Best regards,
    Nils Buerckel
    SAP AG
    Edited by: Harry on Jul 29, 2009 2:38 AM
    Edited by: Harry on Jul 29, 2009 2:39 AM

  • IDoc inbound error..over delivery tolerance

    Hi folks!!
    While receiving order acknowledegement through EDI we are getting following error.
    "For PO 4500085609 confirmation/acknowledgment date is 20090921 5 days too late
    Message no. ME792"
    We have define tollerence for too late confirmation date as 10days in SETUP FOR CONFIRMATION CONTROL. While the delivery date in PO is 16.09.2009
    If we compare PO delivery date with confirmation date it is only 5 days late, so error should not come.
    Pleas guide me to solve this problem.
    Best regards,

    See OSS Note 874264 - MB01/MIGO: Default quantity for goods receipt posting
    3. The basis used for calculating the over or under delivery tolerance is the quantity ordered, in case of purchase orders, and the suggested quantity, in the case of scheduling agreements. If you want the system response to be the same for scheduling agreements as it is for purchase orders (that is, you need more generous tolerances) see also the SAP Consulting Note 741385.
    For items with a confirmation control key, the basis for the calculation of the over or under delivery tolerance is the quantity ordered or the total of the schedule line quantities.

  • Error : Pre Settings for IDoc inbound processing are missing error

    Hi Experts,
    There is a CRM job which executes LSMW and I am facing a strange problem during the IDOC posting the error "Pre Settings for IDoc inbound processing are missing error". Can anyone please tell me how to correct this error?
    Thanks in advance.
    Madhurima.

    I'd start with the following document, with one modification. At step 12 after typing GEARAspiWDM press the Enter/Return key once prior to clicking OK. (Pressing Return adds a carriage return in the field and is important.)
    [iTunes for Windows: "Registry settings" warning when opening iTunes|http://support.apple.com/kb/TS3299]

  • IDOC inbound Posting Error no 51

    Hi Friends,
      I am triggering Inbound error using XI.
    I am getting Error no 51(Application document notposted), when i am checking in WE05.
    Can any one guide me how to trace further error???
    Cause of Error????
    If data is incorrect in IDOC how can i check, that error is due which field record????
    Please guide me and give some T.Codes to trace error in inbound IDOCs
    Thanks & Regards
    Umesh

    the hint with the status record is correct: If you double-click it, you may have a button 'application log' - but only if the inbound processing creates a log.
    SAP knows thousands of IDOC basic types, message types, process codes and almost nothing is handled the same way.
    So first get the details about Idoc and message types, find out how the inbound IDOC is processed, get the function modules name, use the debugger to see where what error is issued.
    You may also have a look at the IDOC's segments contents and see if some data is obviously wrong.
    Or just tell the readers here what business process you try to handle using what IDOC - experience may be just one click away.
    regards,
    Clemens

  • IDoc - Inbound delivery

    Hi Experts,
    Inbound EDI message order acknowledgments:
    When we cancel a purchase order item with IDoc message 'ORDRSP', this leads to an error message in the IDoc inbound processing.
    There is note 890812, but i guess it is till release 5.0
    Can anybody please guide me for the solution.
    Thanks,
    Sourabh Kothari

    Hi Experts,
    When we tested for the note, it is giving the status that this cannot be implemented.
    Could any one give me the alternate solution for the IDoc inbound processing.
    When the vendor sends the quantity 0 against any of the line items, the other line items are also not posted. There error message is ME794.
    As per the above note implementing the corrections & when the item is deleted in PO, again processing the idoc would be successful. But the note is not valid for ECC 6.0
    Please guide.
    Thanks,
    Sourabh Kothari

  • Need IDOC inbound and outbound programs

    hi,
    i am new to xi.
    i want IDOCs , inbound and outbound / function module  programs for    PURCHASE ORDER
    and GOODS RECEIPT.
    ex:  BD10 for material master (matmas01).
    thanks and regards
    v ijender

    for purchase order.
    ORDERS / ORDERS04
    ORDCHG / ORDERS04
    ORDRSP / ORDERS04
    Programs
    RBDMIDOC – Creating IDoc Type from Change Pointers
    RSEOUT00 – Process all selected IDocs (EDI)
    RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
    RSARFCEX - Execute Calls Not Yet Executed
    RBDMOIND - Status Conversion with Successful tRFC Execution
    RBDMANIN - Start error handling for non-posted IDocs
    RBDSTATE - Send Audit Confirmations
    FOr testing you can use WE19.
    and also check the below link
    http://www.erpgenie.com/sapedi/message_types_masterdata.htm
    regards
    kummari

  • *IDOC INBOUND ( NON SAP system - SAP system )*

    I am transferring IDOC  INBOUND ( NON SAP system ->> SAP system ) by calling SAP standard funtc module IDOC_INBOUND_SINGLE using SAP JCo.
    In which I am passing all necessary information in Control Record regarding sender and receiver port/IDOC/segment etc.
    BUT help me to clarify my doubt that if i am calling a function and i am able to access SAP FM, then why i have to specify the SAP port/RFC connection at RECEIVER end in WE21.
    Whats the Significance if i am calling the FM from same SAP system and configuring the port explicitly in WE21.*
    If i don't Specify in we02 i am getting error as EDI : RECEIVER PORT in CONTROL RECORD is INVALID

    Dear Sree,
    For Basic understanding of IDOC read : saptechnical - Step-by Step ALE IDOC guide ( all necessary TCodes available here )
    Kindly let me know your data flow .
    In short :
    As per my scenario the data flow is from  non SAP to SAP  i,.e. Inbound processing.
    At my non SAP  i am calling SAP standard function IDOC_INBOUND_SINGLE using SAP Jco 2.1.
    You have to fill all Control Structure EDI_DC40 ( port etc. ) and Table parameter EDI_DD40 ( segment etc. )
    Read IDOC status and error in WE02.
    Goodluck.
    - Aakash

  • LSMW idoc Inbound Processing settings

    Hi,
    We have done LSMW with BAPI method to create Bank master.
    In Idoc Inbound Processing settings -
    We created partner type as 'B' i.e, for BANK
    While creating Partner Number it is not allowing to create Partner Number. The error is  "Enter a permissible partner number"
    Please let me know what would be the problem.
    Regards,
    Hari
    Edited by: Bhatlapenumarthy Hari Krishna on Sep 12, 2008 9:31 AM

    Hi,
    Use patner type as US only and LSMW as Patner number.
    this will surely solve your problem .
    plz do this way :
    The first requirement is a file port for the file transfer. If required, create a port of the file type via Maintain ports. To do this, position the cursor on "File" and press Create. You should be in change mode. SAP recommends:
    Port: LSMW
    Name: Legacy System Migration Workbench
    Version: 3 (IDoc record types SAP Release 4.x)
    Outbound file Please enter a (dummy) physical directory and a file name, i.e. u2018filelsmwu2019 ·
    As an addition, you can specify a tRFC port. This port is required, if you do not want to create a file during data conversion but submit the data in packages directly to function module IDoc_Inbound_Asynchronous.
    SAP recommends:
    Port: assigned by the system
    Version: 3 (IDoc record types SAP Release 4.x)
    RFC destination: Name of R/3 System
    Name of port: Legacy System Migration Workbench.
    Then the partner type should be defined or selected. SAP recommends:
    Partner type: "US" (User)
    As of release 4.5A, this partner type is available in the standard system. Up to release 4.0B inclusive, this partner type is not available in the standard program and should be added. SAP recommends:
    Partner type: Create US
    Report name: /SAPDMC/SAP_LSMW_PARTNERTYPES
    Form routine: READ_USER
    Short description: any.
    Finally a partner number should be defined or selected. SAP recommends:
    Partner number: LSMW
    Partner type: US
    Partner status: A (active)
    Type: US
    Language: DE or EN
    Person in charge: Your user ID.
    Activate IDoc inbound processing
    reference : help.sap
    thanx.
    Edited by: Dhanashri Pawar on Sep 12, 2008 7:10 AM

  • IDOC INVOIC02 Error

    Hello Friends,
    Inbound error code is 51.
    error details as in application log.
    Error segment  :  E1EDP01
    Error desc        : Field format is incorrect, Required field MENGE is missing in segment E1EDP01
    When i checked this field in IDOC segment it as follows-
    POSEX :  1
    MENGE : 1
    Strange thing is some IDOCs are posted with the identical values of POSEX , MENGE.
    If you have faced this issue before(even though the format is right), please let me know
    the resolution.
    Regards,
    Vinay

    The problem was that while processing insise the inbound idoc fm.. the value of menge was converted to negative based on some conditions and IDOC was expecting only positive values after processing for FM and that's y the error.
    we are in the process of resolution.

  • IDoc Inbound Processing for CREMDM & DEBMDM

    Hi experts,
    I'd like to gather some feedback from you regarding the topic ERP IDoc Inbound Processing for CREMDM & DEBMDM. As you all know, there's currently no option to directly process CREMDM/DEBMDM IDocs in ERP. Currently you have to use PI for splitting the CREMDM/DEBMDM message into its related ADRMAS and CREMAS/DEBMAS IDocs.
    My areas of interest are:
    1) How satisfied are you with the current situation? Does the split work? Are there issues or problems in the current message handling? What are the Pro's and Con's from your point of view?
    2) What would be the requirements for a CREMDM/DEBMDM handler? What would you expect? Maybe you have implemented  something similar on project basis and could post some feedback?
    One painpoint I'd see with a CREMDM/DEBMDM inbound is that you'll lose the IDoc Monitoring capabilities. The message split allows a single record tracing in the IDoc Monitor (as there is a 1:1 relation between IDocs and records). This changes for the mass processing. The monitor would display only the status of the IDoc and you'd need some other monitoring capabilities to check the results on record level. What are your thoughts about that? Is the monitoring important? Would the application log be a feasible solution for that challenge?
    Additional comments are welcome, of course.
    Best regards
    Michael
    PS: @ Matt, please contact me by mail. thanks.

    Hello ,
    Here are some other pain areas regarding the message split :
    1. Complicated monitoring proess & reprocessing error idocs : We have to monitor ADRMAS & CREMAS or ADRMAS & DEBMAS during inbound processing. Also we could not find any best practices to reprocess error idocs. E.g. If ADRMAS fails & CREMAS succeeds what is the impact . Also the impact if it is reveresed. We know for sure that if CREMAS fails , vendor will not be created / updated. But we could not find specific pointers for ADRMAS failures.
    2. It is a tedious process to link CREMAS with corresponding ADRMAS idoc specially when SAP maintains internal number range for vendors.
    3 . The process is complicated if you are managing customer or vendor contact information with contact address . We could succesfully implement the integration but it took us a while to reach end-point.
    4. Splitting really does not seem to support if ERP maintains internal number range.
    5. Another major issue we observed is , if ADRMAS is under process & corresponding DEBMAS or CREMAS is posted , it fails raising the message that Account is locked. Default serialization does work in ERP system . But overlap of few microseconds also cause this error.
    Hope this helps !!
    Please let me know if you need any other specific details since we have used MDM - ECC integration using PI to its maximum extent .
    Regards
    Yogesh

  • HRMD_A IDoc in error not raising an event

    I have workflows enabled for IDocs in error.
    If an inbound order IDoc (ORDERS) arrives in status 51, it triggers a workflow.
    If an HR master data IDoc (message type HRMD_A) arrives in status 51, no workflow is triggered.
    Here is what I have checked:
    Partner profile has me as responsible agent in both cases.
    Both type linkages are active for IDOCHRMD and IDOCORDERS event InputErrorOccurred.
    Both IDocs types are posted in with the test tool and end up in status 51.
    When I investigate the event trace, I can see that an event is raised for the ORDERS IDoc but not for the HRMD_A IDoc.
    There are no errors in the type linkage status column.
    So why would it be that the event is not being raised for the HRMD_A IDoc?
    How can I find out what should be raising the event? I guess that there is a function module call to SWE_EVENT_CREATE or SAP_WAPI_CREATE_EVENT.
    Kind Regards,
    Tony.

    Hi Tony,
    I am a complete novice to workflow but I have a requirement liek yours to trigger workflow for idocs in error, so I was hoping you could point me in the direction of some documentation/steps on how to do this?

Maybe you are looking for