DEBMAS - 'Application document not posted'

HI,
We are passing DEBMAS and ADRMAS from MDM to R/3 via XI.
ADRMAS gets posted successfully.
However in case of DEBMAS we get Error 51 'Application document not posted'.
While debugging we found that the messages are not passed to T_BDCMSGCOLL (include LVV02F3J) in R/3.
Please find the screen shot attached with the error.
This is extremely urgent  as this affects our production schedule.
Thanks in adv.
Gary

Hi AN,
The problem is there is no message from SAP which tells me y this error has occurred.
Earlier I got error messages like some filed is mandatory etc.
I figured out to fill these fields.
Now I am stuck as i do not  know what to do next.
Thanks in adv,
Gary.

Similar Messages

  • 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

  • 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 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

    hi,
    while posting IDOC into R3, I got below error in WE05.
    under status records
    51  Error: Application document not posted
    Account group is not defined in table T077K
    reward points always helpful for helpers.
    Regards,
    Nageswari

    HI,
    Check the posting program use call transaction, if no analyze the error message and fix the problem. If yes then debug your program step by step until you hit the error screen.
    If error in IDoc data , then Exit the IDoc restart from BD87, else problem with application configuration, restart from beginning.
    --related Data error contact your Functional team
    Also see the below links
    IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
    /people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
    idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
    Regards
    Chilla

  • 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 ....

  • LSMW  IDoc error : APPLICATION DOCUMENT NOT POSTED with error 51

    During LSMW matmas04 uploading i m getting error :APPLICATION DOCUMENT NOT POSTED with error 51
    Can some one tell why ots coming so.

    to check errors check We05 or we02 they are same 
    in general i think that most of problem is relate to Dates if that your case check that you converted dates to internal format using conversion step i advice use like this function
    CALL FUNCTION 'CONVERT_DATE_TO_INTERNAL'
    EXPORTING
    DATE_EXTERNAL = ZHEADER-BEDAT
    IMPORTING
    DATE_INTERNAL = MBEPOH-BEDAT.
    <Removed by Moderator>
    Message was edited by: Marcelo Ramos

  • 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

  • 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

  • Application document not posted: while loading hierarchies

    Hi,
    I am trying to load hierarchies for 0costcenter and 0material. I am getting the error '51 Application document not posted'. The load is successful for master data as wellas text data loads. The connections are fine and parter profiles too. Please let me know the step by step by procedure to solve this error.
    Also let me know what can be possible reasons due to which this problem occurs.
    Thnx in advance.....
    and yes i do remember "thanx = Points" :):)

    Check this if it helps:
    Error in Data loading
    Re: Problem with Info Idoc -- please suggest

  • Application document not posted

    hi Gems,
    I am new to BW, have system installed 3.0B, r/3 as 4.7e
    I am learning Generic Extraction,  I have
    InfoCube: 0PA_CO1 which takes data from 2 Info sources 0hr_pa_0,0hr_pa_1 and datasources sources 0hr_pa_0,0hr_pa_1
    Installed BCT for ds
    Steps I followed
    1. Transfer DS
    2. Replicate Ds
    3.Already I have Infosources and already assigned datasources so,
    4. I created Info Packages and loaded the data,
    here I am getting an error, when I check in the Monitor's Details Tab
    Transfer IDoc's.....
          Requested Idoc's:Application document not posted
    will any body help me on this issues
    thanks in advance

    HI,
    Try to look at the links below . Might help you solve the problem
    Error in Data loading
    Re: Problem with Info Idoc -- please suggest
    Cheers,
    Kedar

  • 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

Maybe you are looking for