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

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 .

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.

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

Idoc not fully posted

Dear All,
I am trying to download employees from HR to CRM system. Connection is already set up. When I process an Idoc in BD87 in CRM, system gives me a warning message that Object 01,CP,<pernr number> does not exist: infotype 5580 cannot be created. Same is the case with other infotypes like 1001, 5585 etc. and status of Idoc is 52(no fully posted).
I browsed through related SDN posts and found that T77S0 table settings and general configurations might be an issue. I tested them with another system which is already connected to HR and validated above settings.
Up on debugging, I found that BP is created in CRM for the PERNR but the HRP* tables are not being filled. Also the above warning message is coming from the peform CHECK_PNNNN inside include LRHA0F05 and method CREATE_PD_OBJECTS.
Any pointers on this would be very helpful.
Thanks and Regards,
Narendra

Solved by myself.
The mandatory CP infotype 1000 is not created since the segment E1P0001 is not populated. After it is filled, Idoc is processed fully.
Regards,
Narendra

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

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

Controlling Document Not Getting Posted

Dear All,
We have a peculiar scenario of Controlling Document not getting posted. Any pointers on wat could be the issue will be highly helpful.
Scenario:
We have an interface which posts an accounting document.
Dr. Expense
Cr. Balance Sheet.
The Cost Center is supplied thru the interface and FI document and Profit Center Document is posted without any issues. However, CO document is not generated, not sure wat could be the issue. We have performed the basic checks. Also, for the same expense account, we observe some postings have gone into CO where are some didnt'. The difference between documents posted with corresponding CO and documents without corrsponding CO posting is only the "Transaction Key". When we maintain blank Transaction key.. the system posts CO document, when transaction key is "WRX" for that specific GL the system doesn't post.
Not sure why Standard SAP behaves like that. Please advice wat items i need to check to resolve
this.
regards
Diwakar

Hello,
Make sure in OBYC, for key WRX, you have maintained the GL accounts.
Regards,
Ravi

Logic behind "sales documents, not fully confirmed"

HI MASTERS !
go to transaction VA03. Select the drop-down to search for an order. Execute the second tab titled u2018Sales documents, not fully confirmedu2019. The logic within this search operation is what i need.
plz, answer as soon as possible.

Hi,
The only BAPI available to get the sales order details is "BAPI_SALESORDER_GETLIST". This doesn't have the input criteria mentioned by you. You may have to write custom program to get the details as per your requirement.
Regards
Vinod

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

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 scenario-CREMAS not getting posted

Hi Experts,
i am doing a file to idoc scenario in which i am giving the xml file from MDM ,consisting of Vendor Master data and posting the address and the general data into the ADRMAS and CREMAS idocs into the R/3 system.
The problem that i am facing is that the ARMAS is getting posted correctly but the CREMAS is getting posted with the red signal,status 51.It says "Not authorized to change the Vendor Centrally."
Can anyone please tell me what is the reason and the solution for this problem?
Is this a data error or XI error?
Thanks in advance,
Shweta.

Hi Shweta
Status 51, 52 means Posting error
Please check wheteher all the configuration has been done or not
SM59-rfc destination
IDX1-port
IDX2-load metadata
we05-IDoc status records
BD54-Create Partner Number
We20-Create Partner Profile
WE19-Testing IDoc Processing
After That check the solution it is due to Authorization
File to idoc - IDX5 Error
Regards
Abhishek Mahajan
*Please reward points if helpful**

COPA Documents not getting posted - Doc with unauthorized busi.trans SD00

Dear Experts,
COPA Documents are not getting posted, although billing /accounting documents are getting posted
We are getting the below error message, when KE4ST is executed
Kindly share your inputs for this issue
Document with unauthorized business transaction "SD00"
Message no. KE/AD604
Diagnosis
Document 6000000026 cannot be transferred to Profitability Analysis (CO-PA) because the business transaction"SD00'"(Billing document) is not profit-related.
System Response
The document is not posted to CO-PA.
Procedure
If you decide that the document does contain data relevant to CO-PA and that it therefore should be posted to CO-PA, change your Customizing settings accordingly. Otherwise you can ignore this message.
Advance Thanks,
Sanjai

Hi,
   1. First please check if COPA is active in the system i.e. tcode KEKE
   2. Then check if operating concern is active in tcode KEA0
   3. If so then check if billing document has an account assignment to PA segment. If not then maybe you have changed the account assignment in OKC9.
   4. If all the 3 conditions above are satisfied then you need to check if this is a made-to-order scenario (MTO). A made-to-order scenario can be identified in COPA in that the billing doc will have an account assignment to a sales order in addition to a
PA segment (field vbap-kzvbr = 'E' and vbap-vbelv = sales order no).
If the above conditions are satisfied then from a COPA point of view it is a MTO. In this case the invoice will be assigned to the sales order and will not be directly transferred to COPA. With the order settlement the costs and the revenues (invoice) will then be posted to COPA.
regards
Waman

IDoc status is not coming to '03'

Hi,
When I run my program, it is giving IDoc status as 30. When I go and see in WE05, it is showing same status. It's not getting 03 status.
I know that we can bring the status to 03 by executing the program RSEOUT00. But I want this to come from my program where I have used MASTER_IDOC_DISTRIBUTE function module.
Generally, even though I get status 30 in the program, when I go and see in WE05, 03 status is displayed. But I don't know what happend this time, it is showing 30 status even in WE05 also.
Please tell me what could be the reason.
Regards,
Suman.

Hello,
Check if there are any dumps in the system
Or
if there are any authorization issues.
IF there are dumps, then the system usually stops autoprocessing the idocs and you might need to schedule the program at periodic intervals to get the idoc in status 03.
Thanks,
Sushil Joshi

Material Document not geting posted Error Message RW011

Dear Friends,
The users have created the Material Document thru Invoice Verification, however when we view the Follow on Document, we get the message - Accounting Document not generated, message RW011. How to check the error and find out the reason for the same.
Your help would be highly appreciated.
Regards

Check SAP note 781498...Solution provided is
Using transaction SE16, table RBKP, enter document number, Fiscal Year.
Check the value of logical system, field LOGSYS.
Using transaction SE16, table T000, check logical system maintained for the client. If there is a change in logical system use report ZZLOGSYS referenced in note 28958 Link to follow-on documents is lost, to
re-establish links between documents.
Please go through the entire Note to check all the other related notes
Regards,
Indranil

IDOC status 52 - Document not fully posted

Similar Messages

Maybe you are looking for