IDOC status 53 but no document is posted

All,
I am sure this would be answered earlier but not able to find the thread.
Can somebody please let me know, when I process the IDOC using WE16, I get status 53 but dont find document as posted.
Thanks
Sameer

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

Similar Messages

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

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

Idoc Status 53 but Applicaton document not posted message type PORDCR

Hi,
Need your help. I am using message type PORDCR and Basic type PORDCR04 to create Purchase order through inbound Idocs. I am getting correct status '53' Application document posted along with the new Purchase order number. When I am trying to see it in EKKO / or ME23N I could not see this purchase order.
Can anyone please let me know what could be the possible reason for document is not getting posted in in database but Idoc status is correct.?
Thanks in advance.
Regards,
Deepak

check SM13 and ST22 to see if there are any errors there

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

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

Inboun IDOC status 52--Application document not fully posted

Hi,
In Inbound IDOC, the status code is 52 ---> Application document is not fully posted(satus of the inbound idoc is in yello colour). I want to reprocess this idoc in BD87 t.code in order to convert the yellow colour to green colour. Before reprocessing the IDOC, i need to rectify the problem and then reprocess the idoc in bd87. am i correct? if yes, what i need to do to solve the error --->application document not fully posted. Please guide me friends.
Thanks in advance.
Regards,
Sri

I am attaching how we documented the process in our troubleshooting guide. Graphics were not pasted.
21.3       Manually run IDOCs reported as 52.
It is possible that IDOCs are found in status 52 for the daily updates.   In principle IDOCs 52 can not be re-proceeed, but there is a way to push the appropriate data from a source system, e.g. ERP.    Following is the process.
21.3.1     You find IDOCs in status 52 in WE02.
21.3.1     Open table EDIDS.
Perform 2 searches for parameter STAPA2 and STAPA1 in status 52 and download the entries for each column to an MS Excel file.
21.3.2     Adjust the MS Excel file.
The strings STAPA2 and STAPA1 have to be truncated and separated into 3 different fields for processing: First 2 characters are the Plan Number, next 2 the Object Type, and next 8 the Object Number.
21.3.3     Manually process the entries via transaction PFAL from the source system, e.g. ERP.
The entries must be processed in the following order sorting by Object Name:
u2022     STAPA2s first, then STAPA1s.
u2022     Each organized by O, S, P, C, and CP.
21.3.3.1     Running individually for each entry.
By running PFAL with the individual entries: Plan number, Object Type, Object Number, Update mode, Target Logical System name ... the respective IDOC will be passed to target system for processing.
21.3.3.2     If there are many entries for processing.
If there are many STAPA2 and STAPA1 for processing.
u2022     Create a text file like the one below with the entries as mentioned above.
u2022     Logon into the source system and make sure CATTs are allowed..
u2022     Via SCAT, create a CATT that emulates the execution of PFAL entering Plan number, Object Type, Object Number, Update mode, Target Logical System name ... the respective IDOCs will be passed to the target system for processing.
. Create the text file with the entries.
. Execute the CATT ... the respective IDOCs will be passed to target system for processing.

IDOC successful but no documents gen.

I have finance/accounting idoc setup
in source client Z1, IDOC 30003 is generated and status 03, 30(receiver exits,ready for dispatch)
in target client, the corresponding idoc 3200005 has generated with status 53 and it is saying 1 transaction were created, but I check there is no accounting document generated, but every month user will receive a idoc and generate one accounting document type ZM. why this time, no accounting document generated.
which idoc functionality I can check the accounting document generated by one IDOC?

Hi,
Goto WE57 and get the Function module mapped against the message type for the inbound idoc.
Place a break-point in the FM.
Copy the inbound idoc number and goto WE19. Input the Existing Idoc with the idoc number and execute. Click on Standard inbound, which takes you to the FM brak point.
Here, you might get some details for the document not being created.
Regards,
Satish Kanteti

IDOC scenario: MATMAS02 (Application document not posted ALE/EDI errors)

Hi!
I am almost ready with with my first File to Idoc scenario and having the following error.
(Idoc of type MATMAS.MATMAS02)
The IDOC will be received on business system B.
Unfortunately the following errors come in tcode BD87 or MM90
Enter a material type
Message no. M3098
No material number transferred
Message no. M3752
Can some one help me to trace and solve this problem?
Thank you very much!
regards
Holger

Hi!
I corrected the error!
Now the Idoc has the status "yellow" which mean "IDOC ready to be transformed to application".
Is that still an error/warning or is everything is ok?
I mean does some background job started and create a material from this IDoc?
I loooked into tcode MM03 and cannot unfortunately detect any new materials....
kein Filtern , kein Umsetzen , kein Versionswandel .
Message no. B1005
In Log I could find:
IDoc successfully processed in the ALE layer
The IDoc has passed through the ALE layer successfully and can now be passed to the application. This transfer is either done online or as a background job, depending on the settings in the partner profile.
If there are no further status records, the IDoc waits for the next run of the transfer report to the application.
Success or failure when passing the IDoc to the application is documented in the subsequent status records.
Actions in the ALE layer
The parameter 'kein Filtern' indicates whether the processing in the ALE layer led to segments of the inbound IDoc being omitted. The important criteria here are the settings in the segment filter and in the distribution model for this sender.
The parameter 'kein Umsetzen' indicates whether field values were converted in the ALE layer. This is the case if the IDoc contains organizational units to be converted, or if the ALE conversion tool for this sender is activated.
The parameter 'kein Versionswandel' indicates whether the IDoc was converted into an earlier version of the IDoc type. This happens if the IDoc type of the sender is different from its own IDoc type.
Holger

IDOC STATUS - 51 " IDOC HAS TEST STATUS"

I am trying to simulate store orders using WVFB transaction. Idoc is getting generated , but with the staus : 51 " IDOC HAS TEST STATUS". In WPER its not showing any erros. Idoc is - ORDERS05.
Pls let me know, from where its getting test flag.

Rajaram Karthigayan
The IDOC is getting the status 51 saying that an error has occurred assigning the data in the segment.
This segment is a MANDATORY segment.
IDoc status 51 - Application document not posted,
Follow these link
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6743507d11d18ee90000e8366fc2/frameset.htm
http://eai.ittoolbox.com/groups/technical-functional/seebeyond-l/idoc-status-51-error-has-occurred-assigning-the-data-in-the-segment-375696
Thanks
Sandeep sharma
PS: if helpful please reward points

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

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

IDoc status 51 - LSMW for Creating Purchasing Info Records

Dear All,
My req is to create a Conversion for Purchasing Info Records. LSMW's IDoc method is used to develop this conversion wherein Message Type "INFREC" and Basic Type "INFRECMASS01" are being used.
In the 14th step (Start IDoc Processing), I 'am getting the IDoc status "51" and Status Text "Application document not posted". If I double click on respective IDoc number, I got its Control record, Data records, and Status records; in the status records I can see "51" in Red color with the message "Function module not allowed: IDOC_INPUT_INFREC". If I double click on this it asks me to check the process code...
Request you guys to resolve the issue....
Solution will b rewarded.. Thanks in advance....

I shouldnot use basic type INFREC01 instead of NFRECMASS01.
'coz Within the FM there is a check for basic type like:
check idoc type
if f_idoc_control-idoctp c_idoctp_infrec01. " INFREC01
raise wrong_function_called.
endif.
Even one can go to WE57 and see the basic Type INFREC01 assigned to the FM IDOC_INPUT_INFREC, hence one shud use this basic type...

IDoc status 51 - LSMW for Creating Purchasing Info Records using IDoc meth

Dear All,
My req is to create a Conversion for Purchasing Info Records. LSMW's IDoc method is used to develop this conversion wherein Message Type "INFREC" and Basic Type "INFRECMASS01" are being used.
In the 14th step (Start IDoc Processing), I 'am getting the IDoc status "51" and Status Text "Application document not posted". If I double click on respective IDoc number, I got its Control record, Data records, and Status records; in the status records I can see "51" in Red color with the message "Function module not allowed: IDOC_INPUT_INFREC". If I double click on this it asks me to check the process code...
Request you guys to resolve the issue....
Solution will b rewarded.. Thanks in advance....

U should use basic type INFREC01 instead of NFRECMASS01.
Within the FM there is a check for basic type like:
check idoc type
    if f_idoc_control-idoctp <> c_idoctp_infrec01. " INFREC01
      raise wrong_function_called.
    endif.
Edited by: Joyjit Ghosh on Sep 15, 2008 4:57 PM

IDOC status 53 but no document is posted

Similar Messages

Maybe you are looking for