Application Not Posted in Inbound

Hi All,
I'm getting an Application Not Posted Error in Inbound Process.
Can Some one Please tell me how to get the material which i sent.I mean the steps in Inbound Process.
Regards,
Ravi S.

Hi Ravi,
Open the IDOC by going into the transaction WE02 and by giving the IDOC number and press F8 remove the dates in the slection screen.
Now you see the IDOC and then open the status records and double click on the text icon beside it and it will give you the actual error why it has failed. 
If you can tell that error then I can help you. At the same provide the message type of the idoc as well.
Thanks,
Mahesh.

Similar Messages

  • ALE : Error msg 'Application not posted'

    Hello all,
    when i send master data from sender to receiver then at recaiver side it shows the error like  'Application not posted'.
    what it means ?
    I have checked all the connection for both system.Remote connection is also working.IDOC generated at sender side is showing status 3. i.e. data is successfully transfered
    whats the problem?
    regards
    Nilima

    Hi Nilima,
    Application not posted. error is for data integrity as already said.
    Means that document can not be posted in recieving system. Say if you are sending a currency which is not configured in the recieving system. You are sending INR and recieving system needs USD say. So data can not be posted.
    Try posting a document in the recieving system with the same data, it will through the same error take help of any functional consultant and solve the issue.
    Now go to we05 and edit the idoc replicate the same changes as you already found. and reprocess the idoc using tcode BD87.
    Hope this answers your curiosity,
    Award points if useful revert otherwise,
    Aleem.

  • 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

  • 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

  • Extended Payment Order with status 51 Application document not posted in IHC

    Dear Gurus,
    We are make an extended payment order (PAYEXT), through the transaction F110, and then when we want to see the IDOC (by Tx. WE02) we have the following error in the Inbound IDOC´s:
    IDoc: 0000000002179110 Status: Application document not posted
    Error Message: A transaction type could not be (uniquely) determined - IHC 0308
    We enter a payment method and payment method supplement in the proposal on F110.
    I don´t know whats the reason of the error. I hope you can help me please.
    Kind Regards,

    Hi Jayj,
    Thanks for your response. Sorry for the delay in responding you
    I make the following steps to get the error:
    1. I´ve created the invoice through FB60, on the company CO05.
    2. IThen I pay the invoice by F110, (I´m attaching the log of the payment).
    3. When I want to check by WE02 the IDOC the system generate the error message: a transaction type could not be determine. (I´m attaching the error message)
    Please I hope you can help me.
    Thanks a lot and kind regards,
    Ivan R. Menacho

  • 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

  • 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

  • IDocStatus Application document not posted, No status record passed to ALE

    Hi,
    I am sending CREMAS04 IDOC to receiver system.The receiver system should create vendor entry in master table by using IDOC data.
    IDOC is getting posted successfully in R/3,but while calling inbound function module i.e process code CRE1 I am getting following status records :
    51 Application document not posted
    No status record was passed to ALE by application.
    62 IDOC passed to application
    Direct call started.
    64 IDOC ready to be transfered to application
    No filters , No conversion , No version change .
    50 IDoc added
    Please help me to resolve this problem.

    Shweta,
    The IDOC has been posted by XI to the R3 system.  It is the funtional module that is not able to handle the IDOC and only your Functional Team can tell you why the IDOC is not being processed properly by the R3 system.
    It can be because of multiple reasons including invalid data, etc . For instance we once faced an issue once when the User ID used to post the IDOC did not have the authorizations to do financial manipulations and it was our functional team that was able to pin point the reason to us.
    Regards,
    Bhavesh

  • Application Document Not posted:  No T100 message exists (ECC5.0)

    Hi,
    In the Inbound idoc processing, the customers are getting created without any problem, but the status of idoc is still being shown as "Application Document Not posted". It doesnt have any error message. The T100 Text in WE05 shows: No T100 message exists. When I processed this using BD73 in ECC5.0, in the foreground only one informative message displayed: "Special character for emptly field is  /". Otherwise this got posted successfully. Can anybody suggest what could be the reason for the status not being shown as 53.
    Regards,
    Hari

    This is probably not directly pertinent, but...
    I am a (non-SAP) developer who hit this when developing an integration that sent IDocs inbound to SAP. we02 showed this mysterious error.
    Using bd73 to process the IDoc in the foreground did not shed any light -- it just said "error during input of document" (or something like that)
    The error was fixed by our BASIS admin - he said a job to cleanup log files had not been running. After he ran it, the same IDocs that generated this error processed fine when I resent them

  • IDoc: Status: Application document not posted

    Hi Friends,
           I am New to ALE/IDOC.  Based on the ALE_QUICKSTART  documentation. I have tried to send  material from one client to other client. (within system) To do that
    I have created two logical systems and assigned them to corresponding clients.
    Created a RFC destination and assigned logical systems.
    Created Distribution model in sending client.
    Created partner profile in both clients.
    Created Material and send to receiving system using BD10 tcode.
    I checked Idoc status in Sending system, Idoc status is 03-Data is passed to port OK, status 30-Idoc ready for dispatch and  status 01- Idoc generated.
    But in receving system  (Inbound Idoc)- I got status- 51-Application document not posted and Function module not allowed: AFS_RETAIL_ARTMAS_IDOC_INPUT.
    I also checked partner profiles in both systmes- both r same.
    Kindly tell me what went wrong and what should i do.
    Pl.provide answers pertain to this problem only.
    Thanks in advance,
    S.Senthil

    Hi Chris,
            Thanks for ur reply.  I am not using is-retail and I have Generated MATMAS idoc in sending system.
          Kindly provide me answer.
    Thanks in advance,
    s.senthil kumar

  • Idoc number have status  is   51     Error: Application document not posted

    hi friend
    i have error in idoc number status  51     Error: Application document not posted. basic type is  ORDERS05   Purchasing/Sales
    what i do for solve this issue
    with regards
    dinesh
    Edited by: code acess on Feb 9, 2011 4:35 AM

    Hi,
    {1.how i check in the delivery documents have idoc number ? }
    Go into the delivery, output. Check if any output has been triggered for EDI. If yes, then select the output and click on 'Process details' (it is the button just after communication where you give the print name). It will display the Idoc number.
    { what are the required for cofiguration of EDI. Pls Send me the configuration setting . i didnt have help here ..iam expecting configuration setting }
    Though it is difficult to share all the config settings in this thread, what I will do is to put in a few steps which are general settings. Only a few things vary.
    For EDI / ALE - Idoc the common settings are
    a. The port should be enabled for sending and receiving the data thru Idocs. Usually basis does this.
    b. Partner profile should be configured in WE20. Example if you are sending a sales order confirmation to ship to party then, You should set up a partner profile in WE20 for partner number in KU (Customer) folder. You can copy any of the existing customer. What you have to make sure is you have added the message type and the Basic Type in the outbound parameters of the partner in WE20. Also, you have to make sure that you are giving the output type and the process type as well.
    This is same even when you are receiving the Idocs from customer. Say for example customer PO. However, instead of outbound, you will add all these details in inbound. 
    Similarly, if you are sending PO to your vendos, then, you have to make changes in folder for partner LS. There are so many other folders as well.
    Check WE60/61 for the documentation for what is Basic types, Message types and segments. It is very important for you to know about these when you are dealing with Idocs. To start with, you can give Orders01 in Basic types in WE60 selection screen and read out the details.
    c. Once the partner profile is set up, there is a table called VOE4. This is the table where you can maintain the customer cross reference for incoming idocs.
    d. Output type should be set up for EDI trigger (Tcode NACE) . You can use the existing programs. You can Check BA00 which is normally set up for EDI trigger as well. You can try triggering that first. You may get some errors at first. But do not panic. Just read those errors and then search the form for errors. You will get to know the next step.
    e. Once you have the above settings, I think you are pretty much ready for EDI... you can try these. If you get struck in between, the form is there to help you...
    Hope this helps...
    Regards,
    Mukund S

  • 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

  • Inbound IDOC for sales orders not posting the configuration data

    Hi all,
    I am facing a problem in posting the inbound IDOC (message type ORDERS). The configuration data maintained in the parent segment E1CUCFG and in the segment E1CUVAL is not getting posted though i am passing the data in these segments which is 100% correct.
    Can any one solve this problem

    Hi Ravi,
    Please check the two segments are active. You can do that in BD53.
    In BD53 enter message type, and make the segments active.
    If segments are active, it appears in white colour.
    After this post the IDoc and check with segments.
    If its useful, award points pls..
    Regards,
    Bharadwaj

Maybe you are looking for