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.

Similar Messages

Inbound IDOC error - status code 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

HI
If you are FM to process the inbound IDOC,
possibilities are like below .
Reason 1 :
In partner profiles, check is it trigger immediately or not ? for particular partner profile which u r using .
reason 2 :
If you are using BDC code to update the data .if any screen contains error then also you will get the status in yellow .
reason 3 :
Have you tried with TCODE BD87 , might be it is processing error also .
i have worked on same probelm so if u r not solved with the issue after trying above 3 reasons .
reply me back .

52 Application document not fully posted

Hi
I am using IDOCS and after output,this is the status of the IDOC:
52 Application document not fully posted
How can i see where the status is set in order to fix this warning and get a green status?This is an input idoc
Thanks

Solved it by myself,data read from the db was not correct

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

IDOC status 52 - Document not fully posted

Hi all,
On transferring HR data from R/3 to CRM shows two IDOCs, one which is posted- status 53, and the other with status 52 - document not fully posted. IDOC details show that central person for employee and relationships could not be created. The org. structure is replicated but employees are not.
Now there seems to be a reason behind this, this is the second time I am having problems with IDOCs during HR/CRM integration I have had the same problem when earlier a system client copy was taken and faced the IDOC transfer problem in the copied client. In fresh installations the integration works fine. Are there any system buffers to be refreshed or anything else on the technical side or am I missing settings on the CRM side ?
Please help ASAP.
Regards.
PS: the RFC's are working fine as well and already gone through note 550055

Dear Haseeb,
Thanx for your quick response.
For an employee(18730) 1st idoc has been generated on 03.06.2013 from ECC to CRM with these infotypes data (0,1,105) but idoc status is 52, and again changed on 04.06.2013 infotype (2) and idoc hase been generated but status is 52 in CRM and same again changed on 06.06.2013 infotype (6) and idoc hase been generated but status is 52 in CRM. But still Business partner has not been created in CRM.
We are facing for few employees related this issue.
I have been checked SLG1 and WE02 in both ECC & CRM, Please find the attached screen shots for your kind reference.
Please let me know is any other process to solve my issue.
Thanks & regards
Rajasekhar S

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

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

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

Application document not posted / business partner in RPM

Hi,
We tried to import data from ECC HCM System to RPM system, by using tcode PFAL, and when we review the result with tcode bd87 (receiver system) these errors occurs:
51 Application document not posted.
52 Application document not fully posted.
The result it's that we have the HCM Organization created, the positions created, but instead of having person created, we have object "central person". So, in the transaction BP in RPM we can not see the business partner like employee.
In the sap note 1311399 we saw the reason why we have central person created, and not the object person. That is because exits infotype 105 subtype 01.
How can we create these persons like business partner in RPM?
Thanks in advance.
Albio
Edited by: Albio Vivas on Oct 20, 2010 12:02 AM

Hi,
In the receiver system (RPM) we don't have this program "hr_sync_person", but we have this one: "HRALXSYNC".
In the source system (ECC HR) we have both programs hr_sync_person and hralxsync.
1) Are the same programs or similar?
2) The program must be executed in the receiver system (RPM) or in the Origin HR system (ECC)?. (remember we don't have in the receiver system the program hr_sync_person).
3) I tried with the hralxsync in the RPM system (receiver hr data), we executed and we don't have a buttom "repair" instead of that there is a buttom "start syschronization procedure with partner (F8)". But nothings seems to happens.
Thanks,
Albio.-

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

Application document not psted status 51 in ALE/IDOC

Hi Gurus/Experts;
Status number : 51 Application document not psted.
I have configured ALE for distributing material master data. On the outbound side the status of every Idoc is sucess. But on the inbound side some of them are red stating error.
Outbound Side :
we05 t-code.
03 success.
Inbound Side:
we02 t-code.
51 Error.
when I execute the we02 t-code and
Expand Status Record 51
am getting error like : Function module not allowed: AFS_RETAIL_ARTMAS_IDOC_INPUT
Please Give me some suggestion on this..
Thanks;
Ravi.

HI jayanth;
thanks for your replay.
we are almost 1 step ahead i think ...
plz suggest me the same...
those steps are very usefull and its cleard the step status type 51 error
now am getting error on inbound side when we execute we02 t-code.
status Error number 29.
Could not determine recipients for message type MATFET
Message no. B1003
Diagnosis
An IDoc of message type MATFET was passed to the ALE layer, but the three receiver fields in the header record were not filled. In this case the ALE layer tries to determine the receivers from the entries in the distribution model. There are no entries available in the distribution model for the above message type.
Procedure
Define the receivers in your distribution model for this message type or deactivate distribution for these message types.
Thanks;
Ravi.

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

Inboun IDOC status 52--Application document not fully posted

Similar Messages

Maybe you are looking for