IDoc Not Posted in R/3 - Monitoring, Trace?

Hi all
I am sending an IDoc type ORDERS05 from XI to SAP R/3. Everything seems to be alright when looking at SXMB_MONI. Nevertheless, there is no IDoc created in SAP R/3, and I cannot find a hint anywhere (queues, etc.) what the problem could be. Does anybody know how to figure out the problem and can I monitor or trace somehow what happens in between systems? Thanks.
Kind Regards,
Daniel

Hi,
When you see nothing in monitoring of R/3(WAS)
take a look at sxmb_admin -> Integration Engine Configuration -> Specific Configuration.
and set this values:
RUNTIME     LOGGING->1     
RUNTIME     LOGGING_SYNC->1     
RUNTIME     TRACE_LEVEL->3     
RUNTIME     TRACE_LEVEL_PROPAGATION->1     
- also test your sm59 Destination.
- and take a look at Adapter Monitoring to your Communication Channel.
maybe it helps.
Regards,
Robin

Similar Messages

  • Idoc not posted in sap system

    Hi All,
    i have configured the file to idoc and idoc to idoc scenario.
    in sxmb_moni,the inbound idoc is fetching one port and the out bound idoc is fetching the default port,how can i config the port that is idoc comming from sap system.
    in interface mapping i am not able to assign the operational mapping that is created in IR, it is fetch the default name space of the idoc ,which is not to our operational mapping created in IR.
    Regards,
    reddy

    in sxmb_moni,the inbound idoc is fetching one port and the out bound idoc is fetching the default port,how can i config the
    port that is idoc comming from sap system.
    In Message Mapping enable the EDI_DC40 segment and then give value to the SNDPOR/ RCVPOR ....once done in receiver IDOC channel check the Apply Control Record from Payload....Michal has written a blog on EDI_DC40 segment check it once.
    in interface mapping i am not able to assign the operational mapping that is created in IR, it is fetch the default name space
    of the idoc ,which is not to our operational mapping created in IR.
    This behavior is correct....IDOC will refer to its own namespace and not to the one created in IR.....and this should not cause any issue while assigning mapping in Interface Determination....if it is causing an error then you have not selected the objects properly.
    Regards,
    Abhishek.

  • One of the IDOCs has an specific error message (status 51 Idoc not posted)

    Dear Experts,
    ple. provide the solution for my issue.
    In my list of compaines one of the company had an external partner(warehouse) who takes care of their products.
    Communication between that external partner software and my system(PVS) is happen through IDOCs.
    But one of the IDOCs has an specific error message ( status 51 and status text : Specification for units and quantites containe error),
    acctually we are receiving picking meterials from the external system to my system.
    I can able to see the Inbound Idoc and status, I am not able to see the Outbound Idoc, then how can I test why its happening this problem and I how can I give the analysis properly please suggest me.
    Thanks in advance
    Suresh

    Suresh,
    Welcome to SDN. Adding to Jürgen Comment, Just double click on status 51 (at node), then in next screen there will be one information (long text) button, just click on it. Some times it will give good details about the error. the information can also suggest direct trasaction to correct the customization, some times!
    try for ur case.
    Reddy

  • Request IDoc : Application document not posted

    I am loading master data in the development system for the first time after the basline config. I am getting the following error.
    Request IDoc : Application document not posted

    Hi
    Recheck the Connectivity RFC & IDOC too. you may ask basis for help.
    verify the IDoc things no problem, connection and authorization between bw and r/3 established well.
    try check in monitoring - menu environment
    -> 'ale management' - in datawarehouse and in source system.
    take a look oss note 520012.
    Symptom
    RSINFO Idocs with status 51 are repeatedly sent to the top. IDOCs with status 51 (document not posted) queue for ALE inbound processing. This may slow down the system.
    Other terms
    IDoc RSINFO, status 51, bd87, we05, RSRQST, R3 013
    Reason and Prerequisites
    The requests are started periodically and cause a R3 013 error message; the message is sent to the BW system but the requests retain a status 51. You can display the IDOCs via transaction we05. Enter RS* in the 'Logical message type' field and execute the process. You can also display the IDOCs with transaction bd87.
    Solution
    IDOCs with status 51 can be selected for deletion by running the 'RBDMANIN' report; do not use the 'Import in the background' indicator (you must manually remove the indicator).
    Each relevant IDOC is then processed separately in the foreground and you can decide for each IDOC if you want to select it for deletion.
    Hope it helps

  • Idoc status 53.Yet application data is not posted.

    IDOC status is 53. But application data is not partially posted.iam generating 2 idocs, one for type INFREC01 and other for COND_A01. iam  Generating IDOC using a fm IDOC_INBOUND_ASYNCHRONOUS. purchase info record is posted succesfully. but condition info record is not posted.
    for both the idoc its shows green status-53. moreover data in EINA EINE KONH KONP is updating, but its not displayed in transaction ME13.
    Kindly help me.

    Hi,
    Check the config stuff if you are usng the right IDoc...See partner profiles and the message types.
    thanks

  • IDOC is created with status 51( application document not posted)

    Hi experts
    iam working on File-IDOC scenario, when i test the process the XML message is created with no errors and
    but the IDOC is created with status 51( application document not posted)
    the details error shows:
    An error occurred in CALL TRANSACTION USING or CALL DIALOG USING
    during a synchronous update.
    The error was caused by the transaction VA01.
    previously i used same test data that time it was working fine,
    please tell me how can i fix the issue.
    regards
    vasavi

    Key in your Idoc number in BD87, execute
    select the error message and then follow the menu path :
    EDIT --> restrict and process  (Select)
    In the next screen UNCHECK the Bkgd Processing and execute
    Now EDIT --> Process --> foreground from error or in foreground mode.
    This will lead you the screen where it errored out.
    Thx
    PSR

  • Urgent: Error in idoc(Application document not posted)

    Hi experts,
    i am getting the error in R/3 side when i am extracting data from it.
    i checked with WE07 it's shows the error as follows
    "Application document not posted".
    it's been urgent how to resolve this issue. please through a light on it.
    Regards
    Harikrishna N

    Hi Hari,
    You start error processing by executing the corresponding work items in your Business Workplace. If a file read error could be corrected, for example, the IDocs which have not yet been read can be read and stored in the database manually, by starting report program RSEINB00.
    This could be the reason for ur error..
    IDoc could not be generated under MC
    EDIN: Evaluates the partner data from the MC record
    TS70008037
    No process code in the additional partner profile MC parameters; Error when writing the application data in the IDoc.
    this link givs u the req info
    [http://help.sap.com/saphelp_nw70/helpdata/EN/dc/6b7f1543d711d1893e0000e8323c4f/frameset.htm]
    Hope it helps U
    Regards,
    NR

  • File to IDOC- Status 51:Application document not posted

    Hi Experts,
    I'm doing a File to IDOC scenario. The Idoc is getting added and then it is trying to post it to the application but i get the error saying that "Fill all required fields SAPMF02D 0111 ADDR1_DATA-COUNTRY".
    The idoc type i'm using here is debmas06. The source file doesn't provide all the data and the idoc type doesn't really contain the field addr1_data in it. What is wrong?
    Plese help.
    Thanks ,
    Merrilly

    Hi
    For Idoc type debmas06 there are few mandatory fields such as ADDR1_DATA-COUNTRY.
    Check if the ADDR1_data is segment in IDOC not field.
    While passing the data from file to xi to IDOC these mandatory fields are not filled up.
    Probably you need to identify these fields and have to pass the default values if incase the inputs are not in file.
    In We30/we31 you can check with the segment editor for the mandatory status of the fields.
    Thanks
    Swarup

  • Idoc not getting post

    Hi Friends,
    i am using transaction WPUK , there if i enter eann number starting from 1, for ex. 1WMDP000023 Then idoc posted but
    if i enter eann number starting from 0, for ex. 0OA103403929908 , idoc not gettign post , error is eann number not exist or not maintained against the material number, but i have already maintained via MM42 in basic view.
    pls suggest what i should do, i am already debugging but can't resolve it.

    Hi Medha,
    Give the leading zeros and check.
    Regards,
    madhu.

  • Inbound idoc application document not posted

    Hi,
    idoc status is 51 i.e. application document not posted.. when im tyring to send the cm data to other system it is successfull and doing some modifications in that and the same is sent from the other non-sap system to sap system.
    During the sending from non-sap to sap system, the inbound idoc is getting the error as 51. and also providing some field name as kna1-cassd is not an input field.
    This field is not being provided with any value but still the idoc is getting error with this field.
    "Even i tried in the sap system itself, taking some sample data tested in we19 and executing with inbound idoc f.m:IDOC_INPUT_DEBITOR.. still the  idoc is getting error message as 51 (with the same field).
    Please provide your valuable suggestions to solve this problem.
    I had created one cm and tried but still the same message is comming.
    Awaiting your help.
    thanks
    rohith

    Thanks for all your suggestions..
    The problem is that im using the standard function module:IDOC_INPUT_DEBITOR..
    So, this function module cannot be modified which is not my requirement.
    My requirement is that i will send an outbound idoc to some non-sap system and now the non-sap system will make some modifications and resent to sap system (here in sap it is an inbound processing).
    So, during inbound processing the status is showing as 51 due to the field kna1-cassd..
    So i cannot make any customization but the inbound processing should be done and it should be saved into the db...
    Hope you have got a clear requirement.
    Waiting for your response.
    Thanks
    rohith

  • Error "Application document not posted" when tried to receive an idoc

    Hi All,
    My scenario is File to IDOC. the idoc reaches the R/3, but when i check in the transaction we02, under Inbound IDOCS, i see my idoc in status 51 - Application document not posted.
    Does it mean idoc has reached R/3, but it didnt update the respective table in R/3? i'm sending idoc of type MATMAS05, its supposed to update table MAKT, but its not. Do i need to make any special settings for this? pls help me, its urgent.
    Thanks & Regards,
    Bhavana

    Hi,
    The IDOC is successfully coming from XI, but there is problem in R\3 end.
    Idoc status is 51 with "Application document not posted"
    This indicates that the logic for posting the application document is not coded properly in inbound function module. Verify the logic once again.
    Also you need to confirm that the data related or in application configuration is right. If the data values are not correct the above error get generated.
    refer blow link for the program
    http://help.sap.com/saphelp_nw04/helpdata/en/78/21760251ce11d189570000e829fbbd/frameset.htm
    Thanks
    Swarup
    Edited by: Swarup Sawant on Jan 28, 2008 11:13 AM

  • Idocs statsu 51 Application document not posted

    Hi All,
    We are having an issue with orders having large number of line items in which Shipping confirmation Idocs coming from warehouse are going to status 51 (Application document not posted) when we look at the status record it shows "Object requested is currently locked by user" . This issue started happening after the ECC 6.0 upgrade.
    Please advice for the same.
    Thanks

    Dear Abid,
    Did you try to search the Forum? There are lots of threads regarding this..... Please use the search option of the forum and you will get lots of material which may further enhance your knowledge.
    Check this thread....
    Object requested is currently locked
    Thanks,
    Raja

  • Request IDoc : Application document not posted  ERROR

    Hi All,
    When I am executing Info Package in BW PROD the system is showing error
    Transfer (IDocs and TRFC): Errors occurred
    Request IDoc : Application document not posted
    I searched the forums but no such kind of error regarding this senario.This problem is for all IP in BW PROD.
    Can anyone help in this issue.
    Thanks,
    Mayur

    In SCC4 the following
    in we21
    Please do not make any changes to these parameters by urself ,ask ur basis team to check it and change it accordingly ....

  • Inbound IDOC error 51 Application Document not posted

    Inbound IDOC error 51: Item: 002 Goods/Service number not entered So application document not posted.
    Please help me out

    hi
    check whether service number is available in the idoc if not check the field mapping

  • BI extraction error --  Application document not posted - IDOC Status 51

    Hi,
    I am getting the following error while extracting data from ECC to BI.
    'Application Document not posted'
    I went to BD87 in ECC and found that the Idoc Status is 51 and the message is
    'Request REQU_4C65QV...V9QRNZ2X9TV9QRNZ does not exist in target system N05CLNT100'.
    I have already checked partner profile parameters with Basis and they claim everything is okay.
    Do you have any ideas what might be the issue?
    Thanks,

    Hello Rajendra,
    You can review the note 417307 which contain information about the MAXSIZE of a  package size. This is a collective note which contain more notes to other extractors.
    417307 - Extractor package size: Collective note for applications
    549184 - FAQ: What is important for extraction
    157652 - Main memory requirement for extraction from R/3
    You can review the table ROIDOCPRMS and check if the parameter StatFrqu contains a 'X' or a number? You can set this option to 99.
    You can also review the correction note 1147326.
    Check as well if the user ALEREMOTE have the proper profiles configured in both source and target system, sometimes the user is missing the profiles, to check this, read the note 150315.
    I hope that the information can help you.
    Regards,
    Daniel

Maybe you are looking for