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

Similar Messages

IDOC status 64 not getting processed.

Hi Gurus,
      I have a problem where IDOC's with status 64 are not getting processed via background job. the IDOCs weere getting processed with the background job till today evening, but suddenly no changes were made and the processing of IDOC's with status 64 has stopped and they keep filling up, when i checked the log of the Background job it says finished, and the log has the following information,
17.09.2009 19:05:23 Job started                                                                   00           516          S
17.09.2009 19:05:23 Step 001 started (program RBDAPP01, variant POS_IDOCS, user ID SAPAUDIT)      00           550          S
17.09.2009 19:05:25 No data could be selected.                                                    B1           083          I
17.09.2009 19:05:25 Job finished                                                                  00           517          S
Kindly advise on this.
Regards,
Riaz.

When i process the IDOC's using BD87, they gets processed wiwth out aany issues no dump is displayed, idoc gets a status 53 after processing via BD87.
There is another problem how ever there are other jobs scheduled to run in the background other than this background job which are getting cancelled and have two different error logs for different jobs they are as follows.
1) 18.09.2009 02:00:06 Job started                                             00           516          S
18.09.2009 02:00:06 Logon not possible (error in license check)             00           179          E
18.09.2009 02:00:06 Job cancelled after system exception ERROR_MESSAGE      00           564          A
2) 18.09.2009 00:55:27 Job started                                                          00           516          S
18.09.2009 00:55:27 Step 001 started (program RSCOLL00, variant , user ID JGERARDO)      00           550          S
18.09.2009 00:55:29 Clean_Plan:Gestartet von RSDBPREV                                   DB6PM         000          S
18.09.2009 00:55:29 Clean_Plan:beendet                                                  DB6PM         000          S
18.09.2009 01:00:52 ABAP/4 processor: DBIF_RSQL_SQL_ERROR                                00           671          A
18.09.2009 01:00:52 Job cancelled                                                        00           518          A
This is a production server and the Licence is valid till 31.12.9999, and has no issues with the license.

IDOC status 64 not converting to 53, while trying to post GR with IDOC type MBGMCR02

Hi All,
We are having a issue while posting GR for an inbound delivery using IDOC type MBGMCR02. We are using FM BAPI_IDOC_INPUT1 for the same (taken from the process code BAPI). The IDOC is getting generated, but with status 64. And here it is throwing a dump Messge type "X".
How can we get this IDOC processed to next stage / get status 53. The IDOC is failing to get status 53, while updating the delivery document flow information.
We took the ref' of note # 833603, to post the GR.
Any help is highly appreciated.
Regards,
Simadri

Thanks Sudeesh for replying my question.
I just found one note 1993787 which resolved my isssue and was released recently on 2nd may
Thanks,
Simadri

How to change the IDOC Status from 30 to 03

Hi Friends,
In the Partner Profiles Collect IDOCS option is Selected and the Output mode is 4.
In my Custom Program i am Using the Function Module MASTER_IDOC_DISTRIBUTE to generate the IDOCs
I am getting the IDOCs of Status 30.
then in my Custom Program, I am Submitting the IDOCs to RSEOUT00 program.
to change the IDOC status from 30 to 03.
SUBMIT rseout00 USING SELECTION-SCREEN '1000'
               WITH docnum IN gt_range_idocs
               WITH p_compl EQ 'Y'
               AND RETURN.
but still i am not getting the IDOCs of changed status.
I need to get the Changed IDOC status and if the IDOC status is not changed then I need to generate an Error file for the IDOCs data and send that data to customers as a mail.
so my requirment is to call the RSEOUT00 in the Custom Program and Change the IDOCs Status to 03.
When i am Executing the RSEOUT00 Indidually by giving the IDOCs numbers, then the IDOCs Status is going to change to 03 from 30.
Kindly Guide me how to proceed furthur
Thanks in Advance,
Ganesh

Thanks Shrishit,
RC1_IDOC_SET_STATUS changing the Status from 30 to 03.
Its fine, But my Question is will IDOC Data will be reached to XI Server or not.??
means is the functionality of this Program is same as the RSEOUT00.
MY job is to change Status from 30 to 03 only
and then Check the Status of those IDOCs, and if the IDOC is not sended to XI i.e.;03 status, then I need to send the Details of IDOC (i.e.; data in filed IDOC) to Customer Mail ID through an Attachement.
I hope you Understood my AIM, why I need to change the Status in my Custom Program only, by submitting IDOCs to this report .
Kindly waiting for your reply,
Thanks in Advance,
Ganesh

IDOC not coming in status 30 for collecting idocs

Hi All,
We have a requirement in which we need to collect idocs and send together.
To achieve I am making Collect idocs in Partner profiles so that it goes in status 30 and hence I can run program RSEOUT00 to make it status 03 and hence write in file as a group of idocs.
Now inspite of making collect idocs in partner profile, its not coming in status 30 but directly coming in status 03.
Please let me know what may be the reason for the same.
Thanks,
Vivek

Hi vivek,
If you have set the Collect Idoc option in partner profile then the IDOC's will be collected , irrespective of kind of port you are using and the packet size doesn't matter in this case.
It seems to me that the program RSEOUT00 is already scheduled in your system.
Can you check in SM37 , by putting the program RSEOUT00 and check if any user has scheduled the program.
Hope this helps.
Harry

Idoc status 03 in SAP but in XI idoc not showing

Hi Experts,
in my SAP to file scenario, idoc is created successfully with status 03, but idoc is not coming to PI.
It is not happening always. some times, idocs are missing. But not able to find any error in PI.
Please guide me how to get the missed idoc.
Thanks,
Swapnashree

this is old interface and it only gave issue this time. In ECC side, when I checked, out of 4 idocs one idoc is with 03 status and other three were with 39 status.
But all in green status. No error.
RFC destination and all are correct.
Actually I am not able to see the complete error text in TRFC . that message class is not maintained. Our functional team informed that they added XX text and re import idoc and it worked. Please suggest.

Idocs not coming to XI

Hi,
In our landscape developers are trying to send Idoc from R/3 to XI system.
We have created RFC_XI as RFC connection, which they are using to trigger IDoc from R/3 to XI. Now IDocs are getting triggered from R/3 without any error, but they are not coming to XI.
Now when I checked Inbound queues in XI and found that all queues start with XBTI* are stuck with SYSFAIL error.
Through SXMB_ADM I have tried to register and activate queue for XBTI* but it gives error as below:
Error while activating queue XBTI*
Message no. XMS_ADM610
Can anyone help me regarding this so that IDocs can be processes between these systems.
How can we see wats the issue while activating Queues?
Is there anything else needs to be configured between these two systems?
Thanks & Regards,
Manish

Hi,
First of all thanks for so quick reply.
I have checked at XI Side:
In IDX2 in loaded meta data, two types of Idocs are showing
ORDERS02 and CREMAS01
In IDX1, Partner port and RFC have been configured.
at R/3 side:
RFC is checked its working fine.
Using WE20 and WE21, Partner profile and port been configured already.
In SMQS below is the status:
<R/3 Client> RFC_XI R 10 60 INACTIVE 0 <R/3 HOST NAME>
Register the destination in QOUT scheduler (SMQS) and make it as active
Destination is there (as per above) I hope entries are correct but its showing INACTIVE. How to activate it?
Select the queue from WEOUTQUEUE transaction and start the queue processing; now you can see that your XI starts receiving the Idocs
In WEOUTQUEUE when trying to see IDocs using Reciever Port as RFC_XI its showing nothing.
While I checked sent IDoc status using WE05, previously it was taking port as RFC_XI for sent IDoc but now its taking port SAPID6 after I defined port in XI for R/3 using IDX1.
For SYSFAIL Status, further message is as below:
XI restart in qRFC not allowed
Any more ideas or help? Will appreciate if anything step wise can be refer to check and rectify this error.
Thanks & Regards
Manish

IDOC in 03 staus but not coming to PI system..

Hi Experts,
I am working on IDOC to IDOC scenario.All of the IDOCs are in 03 status in R/3 system but some of the IDOCs are not coming to PI system.I checked SM58 also but its fine.
Should it be in 12 staus?
Is it possible that IDOC in status 03 can reach to the target system?
Please reply it asap.Its urgent.
Regards,
Vikram

Hi Vikram,
First of all, bd75 is only for status conversion. This means, that only IDoc statuses are changed, based on the status of the RFC call. IDocs are not despatched again by this transaction.
Secondly, you might want to check the EDI Port that is assigned in the partner profile, if it is pointing to the correct target system.
Finally, if target system is OK and you don't find anything in sm58 in sender system, then you should go to smq2 in PI and you should find your IDocs there, waiting in a blocked queue.
Hope this helps,
Greg

IDoc Status 02 ( Could not find code page for receiving system )

Hi All,
I am getting Idoc status 02 when I am trying to send IDocs from ECC to PI system ( Production ).
Error description.
Could not find code page for receiving system
Message no. E0266
Diagnosis
For the logical destination PIP001, you want to determine the code page in which the data is sent with RFC. However, this is not currently possible, and the IDoc cannot yet be dispatched.
Procedure for System Administration
Possible causes are:
1. The entry no longer exists in the table of logical destinations.
2. The target system could not be accessed at runtime.
3. The logon language is not installed in the target system.
4. In the destination system, no logon language is maintained
Please help.
Thanks - Vinay.

Hi Vinay,
Status 02 occurs when data is not passed to port suceessfully. Check the RFC desination is working fine and your able to connect to target system and also check correct port is assigned.
Regards,
Vinod.

Idoc in status 03 - not received by receiving system

Hello All,
I have researched a lot on this topic on the forum - but what I am facing is something peculiar - so posting the complete scenario.
I have three interfaces based on change pointers mechanism where change pointers have been activated for message type HRMD_A.
There are three distribution models which filter the same message type and send to receiving system GIS – for the logical systems:
FI
Concur
Russia
When IDoc is triggered using standard program RHALESMD (transaction RE_RHALESMD - HR: Evaluate ALE Change Pointers), there could be three or less IDocs produced depending on the filter criteria.
For example, you could have an IDoc each for all above three partners.
When the above program is triggered in the development system all three IDocs reach GIS.
All the custom code and configuration is transported from DEv to QA. When I trigger the above program in QA, not all IDoc reaches GIS. Others stay in the system in status 03.
If I check tRFC queue (transaction BD75), there are no IDocs in the queue.
If I use another program to change status from 03 to 12, the status changes, but IDoc still does not reach receiving system.
I have compared Dev and QA systems, deleted and generated partner profile, distribution model, port in QA – but nothing works.
Not all IDocs reach GIS.
I read on the forum that I need a commit work. But because I am using a standard program - RHALESMD - where do I commit work?
Your inputs will be helpful.

Hi Suneel,
Please go to transaction SM58 and check if the IDocs are stucked up on the t-rfc queue. If so, you can right click and choose Execute LUW to release them.
or
Execute the program RSARFCRD and get the corresponding Transaction id and then execute the program RSARFCSE for processing the entries in TRFC Queue.
Regards,
Ferry Lianto

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

Idoc status is in 12, but it does not reached to Target.

Hello Experts,
We are facing a problem with outbound Idoc.
The problem details are as below.
We have generated an Idoc(Without message Control) and dispatched it to external vendor. Idoc status is 12, when we check it in midleware(seebeyond) it does not reached.
There is no error with RFC and Port definition.
Could you please suggest us whats wrong with it or where its gone.
Thanks in advance.
BR//
Raghu

Hi Siva Prakash,
Thanks for your response.
There is no error with RFC, its working perfectly.
BR//
Raghu

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 status not changed

SAP support
I am not able to change the IDOC status...
I have also processed the IDOCs many times..
Guidance required...
Kamal

Dear Kamal
Please check your entry in SM12 an delete it and again reprocess it with the help of Tcode Bd87
Thanks
Amit Shivhare

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

IDoc status is not coming to '03'

Similar Messages

Maybe you are looking for