Idoc status 3 in r/3, not received in XI

Hello All,
In our production system one order from r/3 which is sent as Idoc has status 3 in r/3, but this order is not in XI ( in sxmb_moni), just one order. How do I validate in XI that this order never came across in XI, or of it did for some reason it is stuck somewhere? sm 58 in r/3 looks fine. smq2 in XI looks fine. our configuartion between XI and r/3, the acknowldegement from XI is not sent back to R/3 for Idoc. Please advice

Hi Shilpa,
As Krishna says, check your TCP/IP connection in SM59. If it is down, restart your J2EE engine. Look at this too..
/people/prashanth.azharuddin/blog/2006/11/24/some-errors-in-an-xi-production-environment
cheers,
Prashanth
P.S Please mark helpful answers

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 status on 03 but not recieved on target system

Hi,
We are recieving inbound idoc from external system and processing Inbound IDOC on SAP system, after processing inbound idoc on SAP we are sending status outbound idoc to external system.
The above functionality was working fine before upgradation.
after upgradation we have recreated RFC (TCP/IP) connection, updated at port level and also configured the new SAP system details ( sid, Hostname, service programsname...) on external system correctly.
Now we are recieving inbound idoc from external system on upgraded system,after processing inbound idoc details on SAP system, generating outbound idoc from SAP and it reaching the outbound prot sucessfully on 03 status with green light.
But external system is not recieving the IDOC. How to find why idoc is not reaching external system even though it is sucessfully passed at outbound port level with green light status 03.
We have also checked the SM58 for TRFC entries but we didn't identified any entries on SM58. Please help us on this issue
Thanks,
Raju

Hi Raju,
As mentioned by The specified item was not found., the one common problem for the IDocs not being sent might be a missing COMMIT WORK. I.e. when using the standard SAP API's for sending outbound IDocs, SAP actually creates the IDoc and registers an update function for sending the IDoc out. So without the COMMIT WORK, the IDoc usually exists on the database (implicit or database commmits), is in status 03, but hasn't been sent out and cannot be found in the outbound RFC queue (because SAP never tried to send it).
If you're convinced that a COMMIT WORK is happening (and after trying to send the outbound IDoc) then I'd try the following: Replace the used RFC destination (or re-define it temporarily) with one that points to the same system from where you're sending. If you don't see the IDocs as inbound IDocs or in the outbound RFC queue, the sending never happens. (Ok, might be a moot point if you completely trust your external system, but usually it's good to even rule out the most unlikely causes - if it's simple.)
So if this didn't help, maybe you can provide some further insight into how you're creating/sending the outbound IDocs. This could help us in trying to get some answer, but for a starter the COMMIT WORK mentioned by The specified item was not found. is in my opinion the best candidate.
Cheers, harald
p.s.: Even if you're using ALE, I don't think it could be due to anything in your distribution model as mentioned by The specified item was not found.. If you wouldn't have setup the distribution model, the SAP API's should create a master IDoc in memory and then no communication IDocs (since there's no recipients or due to filtering) and thus there should be no outbound IDocs on the database.

Idoc status green but data not posted correctly to destination system.

Hi,
Can anyone help me out with idoc problem that I am facing.
The problem has come out with outbound idoc.
The status of the idoc is green when it has been sent but the objects that has been sent with that idoc are not getting posted in the destination system.Some of them are posted correctly but some of them are not.
What may be the reason behind this.
Regards,
Rachana.

Good morning
What was the resolution here? We are siitng with the same problem, but IDoc's are correct, but data packet not processed.
Thanks, have a nice day
Cj

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 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 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 not received in receiver , sender shows successful in WE02

Hello,
I am sending Vendor from Production to Quality , sender system shows in WE02, idoc status as sucessful. I have checked all ALE settings and they are perfectly fine.
But in receving system I am not able to receive it. In sender , transaction SM58 is showing error:
No authorization to send IDocs with message type CREMAS
Can any one suggest what is the soultion for this scenario?
Thanks,
Madhura

Hello,
Solution for above problem:
After executing transcation SM58, screen will show Function Module as IDOC_INBOUND_ASYNCHRONOUS , put cursor on FM IDOC_INBOUND_ASYNCHRONOUS
, go to EDIT->Execute LUW.
This will solve the problem of authorization.
Thanks,
Madhura

Outbound IDOC not received at the receiver system.

Hi,
Im sending an IDOC from sap to a non-sap system. During this process, from sap system it is executing successfully without any erros and the status is also '03' .
The problem is that the other system is unable to receive the IDOC sent from SAP system.
The connection is like TCP/IP and the registered server program is given as 'PROGRID' in RFC destination.
I would like to know what would be the possible cases where this IDOC is not received at the receiver system.
The configuration is perfect as per my knowledge. Just want to confirm one thing 'do i need to include any message type such as "SYNCH".
Awaiting for your solutions.
Thanks
rohith

Hi,
If the IDOC is sent successfully from the sender system then the status of the IDOC will be '03' , no matter whether the receiver has received the IDOC or not.
As per your case,
Check the Partner Profile parameters , whether the basic and extended message types are used properly.
The message type Synchron (Sync) is generally needed in Inbound IDOC side. Check whether you have added SYNCH or not.
Hope this Helps.
Regards,
Abhinab Mishra.
Experience is the name everyone gives to their mistakes.

IDoc not received by the Webmethods

Dear Abapers,
I have a scenario :
Here the idoc is being created perfectly with all the segments prooperly populated. Also from SAP side, we are getting the message that it has been sent.
However, the receiver ( Webemthods) is saying that it is not receiving the idocs . So, what can be the possible reason ??
Appreciate your reply...
Thanks and Best Regards,
Kunal.

error send questionnaire in srm Ros
Registration - Error after Send / No Questionnaire
ROS Questionnaire link sent by email
ROS Questionaire
Re: Status for the transferred Suppliers is not updated in ROS client!

Can not receive IDocs

Hi together,
I have configured an IDoc listener in xMII 12. The listener is started. According to the connection test in transaction SM59 the connection to the listener is fine.
Distribution model and so on are all created.
Now I try to send me the IDocs I want by using transaction CI42N which is used to send production orders.
Looking to transaction WE05 the IDocs are in the list with status "IDoc sent to SAP system or external program".
But in xMII there is no IDoc received. Either with or without message rules.
There also is no entry in the table XMII_JCOMESSAGES.
I checked the default trace and warnings of the xMII (Netweaver) Server. But there is no entry within the time range when IDocs were sent and also before or after is no entry that has to do something with IDocs or message listeners.
The xMII Version used is 12.0.2 Build(88).
Anyone has an idea what goes wrong there?
Regards
Timo

Hi Timo
I am not sure if you already got the answer to the problem u mentioned.
There can be various reasons for IDocs not received in XMII. So I will list the most obvious ones that I think might happen. Just take some time to check through this list one by one.
1. Go to SM59 and do a connection test on ur RFC Destination. If it is successful then go to Menu option "Extras" -> "Target System". Do this a couple of times and see if on al the tries it points to the correct XMII System. It is possible that u have used the same Program Id for 2 connections and RFC gateway is working as a Loadbalancing server.
2. If 1 is correct the go to trx BD64 and do a Model View Distribute of ur configuration. In XMII u should get a RFC message of type "Model_View_Distribute". If this is there then your configuration is correct.
3. send the idocs from ur trx and check in trx sm58 for the status. If it fails there then they never reached XMII. Check the error message here.
4. If all 3 are correct check if you have a processing rule which might be deleting the messages or a clean up rule which is cleaning them.
Best of luck.
Hope this helps.
Partha

BW system not receiving Idocs from R/3 system

Hi all, I am having a problem with my BW system. What happened is that we deleted logical systems in R/3 and then recreated them but now in BW we can't display received data. We checked using rsa3 extractor checker and the data is available in R/3 but we are failing to bring it across to BW. BW is saying there is no data. And the monitor status when loading data is reporting missing messages that is: Request received, Number of sent records and Selection completed. May you assist me it's urgent because all BW work has stopped because of this.
Thanks in advance!!

Hi, we recreated RFC destinations but the problem still remains. This is the message under my Monitor status on the "Details" tab:
Overall status: Missing messages or warnings.
Requests(messages): Everything Ok.
   Data request arranged
   Confirmed with: OK
Extraction(messages): Missing messages
   Missing message: Request received
   Missing message: Number of records sent
   Missing message: Selection completed
Transfer (Idocs and TRFC): Missing messages or warnings
   Request Idoc: Application Document posted
   Info Idoc 1: sent, not received; Data passed to port OK
   Info Idoc 2: sent, not received; Data passed to port OK
   Info Idoc 3: sent, not received; Data passed to port OK
Processing(data packet): no data
I think the messages above may assist in a big way for you guys who are willing to assist. I am a bit stuck on the issue.
Thanks once again in advance!!

Idocs are not received in Destination side.

Hi Friends,
I have a small doubt regarding SM58.
I have 2 dev systems.
client 100 & 200 we are send the Material data from 100 to 200.
In 100 system all are fine and the status is 12 and green but those are not received in 200.
When we check in 200 all the IDOCs are strucked in SM58(TRFC queue).
Please suggest me?
Regards,
Venkat.

Hi,
Please check the system RFC connection in WE21 and resend.
Regards,
Nandha

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

Idoc Not received on MII Message Listener

Hi All,
I am trying to post Idoc from R/3 to MII Server , but some how I am not getting it
I have configured Destination, Parter, Partner Profile on the R/3 and Message Listener on MII.
When I am trying to send Idoc from R/3 using BD10 transaction (Idoc type MATMAS), Idoc Status as 03 in WE02 transaction , but I the MII server does not show up for this.
Even the Failed Messages is showing no results.
Am I missing some thing here.
Any help is appreciated.
Kind Regards

I got the issue,
The problem was Partner was wrongly selected.
Thanks

Idoc Not received?

Hi
During data loading , I got one Error that Idoc Not received.
What will be the cause of problem and How to resolve it?
Regards & Thanks
Durai

Hi Robert Negro !
I checked , Dump has been there.
How can I resolve?
what will be other causes apart from the Dump?
Thanks A Lot .
Regards
Durai

Idoc status 3 in r/3, not received in XI

Similar Messages

Maybe you are looking for