Idocs not sent ?

Hello All,
In my scenario some Idocs will be sne from my server to the other server every 5 minutes.
But they are not being sent.
The status of all of the IDocs is 30.
Can any one tell me what's the reason could be ?
Regards,
Deepu.K

Hello,
The problem is solved.
The user locked the Transaction which issues the Idocs.
Now I released the locks in SM12 and the IDocs are issued again.
Thanks to all.
Regards,
Deepu.K

Similar Messages

How to extract data from custom made Idoc that is not sent

Hi experts,
Could you please advise if there is a way how to extract data from custom made idoc (it collects a lot of data from different SAP tables)? Please note that this idoc is not sent as target system is not fully maintained.
As by now, we would like to verify - what data is extracted now.
Any help, would be appreciated!

Hi,
The fields that are given for each segment have their length given in EDSAPPL table. How you have to map is explained in below example.
Suppose for segment1, EDSAPPL has 3 fields so below are entries
SEGMENT          FIELDNAME           LENGTH
SEGMENT1         FIELD1                   4
SEGMENT1         FIELD2                   2
SEGMENT1         FIELD3                   2
Data in EDID4 would be as follows
IDOC           SEGMENT                          APPLICATION DATA
12345         SEGMENT1                        XYZ R Y
When you are extracting data from these tables into your internal table, mapping has to be as follows:
FIELD1 = APPLICATIONDATA+0(4)        to read first 4 characters of this field, because the first 4 characters in this field would belong to FIELD1
Similarly,
FIELD2 = APPLICATIONDATA+4(2).
FIELD3 = APPLICATIONDATA+6(2).
FIELD1 would have XYZ, FIELD2 = R, FIELD3 = Y
This would remain true in all cases. So all you need to do is identify which fields you want to extract, and simply code as above to extract the data from this table.
Hope this was helpful in explaining how to derive the data.

How can we varify that Idoc is sent to the XI or not

How can we varify that Idoc is sent to the XI or not

Hi
In XI go to transaction IDX5 you will find an entry for the Idoc.
IDX5 maintains the list of all the inbound and outbound IDoc's.
Regards
Santhosh
Remember to set the thread to solved when you have received a solution

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 found in the receiving system

Hi Experts,
In the sending system idoc status is 03 (Data passed to port OK), but in the receiving system the idoc is not there. How to rectify this error?
Thanks & Regards,
Soumya.

Hi Soumya,
Check the RFC connections, becoz in the sending system once the IDOC is sent the status becomes 03 it does not check whether the IDOC has sent to the received system, if there are any errors before sending the IDOC it will not send and the status will be 01, so check the RFC connections at sending and receiving systems.......
Reward points if this helps............
Regards,
Ravi G

Idoc not appearing in Xi system

Hi experts,
I have developed a idoc to file scnario but the idoc trgerred in the ECC system i snot comming to XI. I have done all the setting IDX1 and IDX2 and partner profile settings in ECC. the idoc status is 03 in ECC which says the idoc is sent to port successfully, but it is not appearing in SXMB_MONI in XI. It used to work earlier. Is there any batch job or peogram does this transfer. what do i check?/
thanks
sankar

Hi,
Add the Logical System of SAP R/3 in Integration Directory as shown in the Blog and check Now
The specified item was not found.
And also check these Disscussions
No service for system in Integration Directory
No Service for System XYZ,Client 300 in Integartion Directory
Regards
Seshagiri
Edited by: N V Seshagiri on Aug 7, 2008 8:16 AM

IDOC not Received at XI

Hello folks ,
I need to send a idoc from r/3 to xi. i have made all the necessary configuration in r/3. iThis s a production sytem ....have checked on R/3the IDOC is succesful at we02
checked BD87- IDoc sent to SAP system or external program
SM58 no errors...
wen i checked at XI with the particular IDOC number iI dont find an entry what could be the reason .How to resolve the same.
Regards,
Robin

Thanks guys .. thanks for ur quick response
Solution : Had to run this job RBDMOIND ...(particular IDOC NO, was not sent to XI )
Edited by: Robin on Jul 30, 2010 3:22 PM
Edited by: Robin on Jul 30, 2010 4:43 PM

IDoc not getting processed in Real Time job

Hello,
The configurations are done as per the below link to receive iDoc from SAP in BODS.
How to Receive IDOC in BODS from SAP (Outbound to SAP)
An iDoc is sent and Real Time Services on management console shows that request is received successfully. But I cannot see output xml file created. When I checked the real time services and client interfaces, I could see all are in green.
But the real time job status shows its in running state. It has been in running state for 2 days. Trace shows as below. There is no error message.
14.2) 04-24-14 18:47:41 (18417:1140171104) JOB: Optimizing job <JOB_BODS_RT_IDocMatmas01>.
(14.2) 04-24-14 18:47:47 (18417:1140171104) JOB: Job <JOB_BODS_RT_IDocMatmas01> is started.
(14.2) 04-24-14 18:47:47 (18417:1140171104) DATAFLOW: Data flow <DF_RT_IDocMatmas01> is initialized.
(14.2) 04-24-14 18:47:47 (18417:1140171104) DATAFLOW: Data flow <DF_RT_IDocMatmas01> using IN MEMORY Cache.
(14.2) 04-24-14 18:47:48 (18417:1140171104) DATAFLOW: Data flow <ActaDefaultNotificationSender> is initialized.
(14.2) 04-24-14 18:47:49 (18417:1140171104) DATAFLOW: Data flow <ActaDefaultNotificationSender> using IN MEMORY Cache.
Can anyone please let me know if there is anything missing in the configuration? How do I resolve this issue?
DS version: 4.2

Hi,
Try to reimport the metadata of IDOC into PI in idx2. Also check the port definition in ECC and whether the segment is released or not. Please go through the below discussions it may help you.
EDISDEF: Port XXX segment defn E2EDK35 in IDoc type ORDERS05 CIM type
IDoc 0000000000181226 was saved but cannot or should not be sent
Regards,
Priyanka

IDOC -- File:(R/3-- XI) : Idocs not reaching XI. Where to check for error

Hi,
I have completed the config for IDOC to XI (R/3-->XI) scenario based on various weblogs available on Sdn.
For testing, I am using we19 to trigger the outbound idoc from R/3. But when I look in IDX5 in XI or message monitor, I do not see any message or IDOC there. Even SXMB_MONI in XI does not have any message.
What could be the potential issue for this behaviour. Is there a way where I could debug or any steps that could tell me where to look for the error.
So far only odd behaviour I have observed is:
When in WE19 I trigger the IDOC for outbound processing, XI login screen pops up, where I need to enter password. Once I click enter the screen disappears and the message, IDOC sucessfully sent to external system/Port appears.
Appreciate your help.
Thanks
Shirin

Hi,
I checked SM58 and teher indeed are errors saying
"Name or Password is incorrect (repeat logon) "
So which connection is having incorrect password in SM59?
I checked and I have a working RFC connection (TYpe 3) in SM59 for XI.
Just to add TCP/IP connection(Type T) has 2 connections not working. They are LCRSAPRFC and SAPSLDAPI.
So what should be my next step in correcting this error as I am not sure which RFC connection user-id is responsible for SM58 errors.
Any feedback is welcome.
Thanks
Shirin

Message via SM59 "HTTP connection to external partner" not sent to partner

I have a scenario where I am supposed to send a message to an external partner using https. I have created the HTTP connection in SM59 "HTTP connection to external server" and selected the default certificate. This connection is referenced in the http receiver CC in PI 7.1, but when I send the iDoc message from the backend it is not sent out of PI to the external partner.
There are no apparent errors in the trace files in SMICM on the PI system, but our firewall guys say, that they cannot see the outgoing call in our firewall and the external partner cannot see the message either.
There is connection to the external server from the PI server, which has been confirmed by a telnet connection.
We think that there might be a problem on our web server, but we are not sure.
We have previously succeeded in calling an other server at the external partner from the PI system using a different client certificate. When we do a connection test in SM59 we get an error 500 but the external partner can see the GET request in their firewall.
Any suggestions are more than welcome
MIkael

The error message appears in the call adapter pipeline step before the supposed mapping is supposed to take place. The error message is:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand=""><SAP:Category>XIAdapter</SAP:Category><SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code><SAP:P1>400</SAP:P1><SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2><SAP:P3/><SAP:P4/><SAP:AdditionalText/><SAP:Stack>HTTP client code 400 reason ICM_HTTP_CONNECTION_FAILED
</SAP:Stack><SAP:Retry>A</SAP:Retry></SAP:Error>
Mikael

IDOC not reaching destination system

Hello,
I am trying to send DOCMAS type IDOC from one SAP sys to another SAP sys.The IDOC has the status 03 (The IDoc was sent to an SAP system or an external program via a transactional RFC) but i dont see the IDOC in the target sys.
Please let me know what could have gone wrong.
Thanks,
Rakesh.

Hello Rakesh More ,
First let us know how you corrected the previous error???. What was wrong?
Then talk about the next issue.
If you maintain properly the Inbound IDOC partner profile this error should not come. Make sure you have the below things set-up properly:-
1) In the inbound IDOC in the destination system there should be a partner receiver in the IDOC control data. Make sure you have maintained the partner profile for that partner and for the partner type as well.
2) For the partner make sure you have maintained the proper inbound mesaage type and process code properly.
Thanks,
Greetson
Edited by: Greetson Shunmugasundaram on Aug 1, 2011 9:47 PM

Idocs are sent in random order

Hello,
We use idocs DELVRY01 to send deliveries to external systems. The communication is done via RFC connections.
In the partner profiles, we customized the 'send immediately' option (in order to have real time interface).
We supposed that the idocs would be sent in the order of their idocs numbers or of their serialization orders, but it seems that it is not the case.
What is the way to ensure that the idocs are sent in a First in first out way?
Thanks a lot for any help

Hi Julien,
Since you indicate in the partner profile that IDoc's are to be sent immediately (packet size is always 1) each IDoc is treated as a separate process.
If you have more than 1 application server, it is possible that IDoc's can be processed at the same time on different application servers.
Sollution: Make sure IDoc handling is done by only one application server.
If you have delivery notes with differences (like delivery notes with only one delivery item and also delivery notes with many items), then the creation of one IDoc is faster with small delivery notes and slower with larger ones. Since more dialog processes are defined it is possible that smaller delivery notes are sent earlier as larger ones (thuis disrupting the order).
Solution: 1. Combine IDoc's by using the Collect IDocs with a small PacketSize (i.e. 10 - 20) and trigger report RSEOUT00 every now and than. (This reduces the IDoc delivery note interface to a batch interface).
Solution 2: Use message control (it goes to far to explain it here, but in SAP Help (located on the path /SAPHelp/Helpdata/EN/dc/6b803343d711d1893e0000e8323c4f/frameset.htm) you can find many details for this, also the selection conditions for sending the IDoc's.
If nothing is to your liking, you can always program your own processing unit that will ensure the right order (using the function module MASTER_IDOIC_DISTRIBUTE).
Hope this gives you some clues,
Regards,
Rob.

SAP ERP - SAP ME - iDOCS - Not received

Dear Experts,
We are trying to send data ( MATMAS iDOC) from ERP to ME.
We used the below transaction in SAP.
1. using BD10 transaction in SAP ( Send material) Idoc was sent
Checks :
We checked in WE05 in SAP and found that Idocs sent is successful
Opened MII ( Queue Monitor) and Found that Idoc was received successfully with ID but Message ( "" sucessfully Queued) Status : Queued
Problem : We are not able to see the material in ME system
No errors found in NWA logs.
Kindly suggest any solution.
Regards
Shankar

Make sure you have the plant id in the idoc. Here are the few place in the idoc that you need to add the PlantID. We're using TN01 as our plant.
<MATMAS03>/ <IDOC>/ <E1MARCM>/ <WERKS>TN01</WERKS>
<MATMAS03>/ <IDOC>/ <E1MBEWM>/ <BWKEY>TN01</BWKEY>
<MATMAS03>/ <IDOC>/ <E1MVKEM>/ <DWERK>TN01</DWERK>

IORDER01 IDoc is sent without plant code from SAP ECC

Hi MEINT experts,
Does anyone experience before on the service order integration between SAP ERP and SAP ME, somehow the IORDER01 IDoc is sent over with empty plant code embedded in the original document? (where we suppose to see <WERKS> data tag is attached to the IDoc sent over from SAP ECC). This has resulted to the corresponding IDoc is not able to process by MEINT due to empty plant code.
Please advice how to resolve this if you have done that before.

Hi,
Once the issue stems from ERP side of integration process, this question should be either re-posted to ERP-related forum or submitted as a customer ticket against PP-MES component.
Regards,
Sergiy

CO54: Message is not sent to any destination: Commit Work is getting failed

Hello,
While processing the Messages from XFP to SAP Update is getting terminated due to the use of Commit Work. SAP Note 147467 - Update termination when sending process messages has been referred which is for 4.6C, but we are in ECC6.0.
While processing the message in second iteration Commit Work triggres and Update happens in the data base.
Following Issue is only concerned with Nested HUs
T-Code used CO54
Following are the analysis:
it looks like u201CCreate and Post a Physical Inventory Docu201D is failing in the initial processing because the inventory doc is created when the Transfer Order to the PSA (or the TO from the PSA) is not yet completed (quant is still locked somehow).
CO54, process message category=ZHU_CONS: HU to be consumed is a nested pallet (unpacking/ repacking and TOs to/from) and qty to consume is greater that HU qty in SAP (creation of a physical inventory doc is required).
1. The error occurs while clearing the inventory posting for the physical inventory document.
2. The surprising factor is the u201CProcess Messageu201D is not processed correctly for the first time.
3. Indeed it is successfully processed without any error if you do process it second time.
Error Log from C054 T-Code.
02.08.2010                                         Dynamic List Display                                                1
Type
Message text
LTxt
Message category: ZHU_CONS ---    Process message: 100000000000000621   "Send to All Destinations" Is Active
Message to be sent to destination:
ZHGI ZPP_0285_XFP_GOODSISSUE Individual Processing Is Active
=> Message will be sent to destination (check log for destination)
Message category: ZHU_CONS ---    Process message: 100000000000000621   "Send to All Destinations" Is Active
Message destination ZPP_0285_XFP_GOODSISSUE triggered COMMIT WORK
Input parameters OK, passed to source field structure
Step 0: Now checking if scenario with HU
Step 2: Scenario with HU, Now checking if HU nested
Step 3: HU nested, checking if HU in repack area
Step 4: HU not in repack area, moving it to repack area
HU moved to repack area, TO number 0000000873
Step 5: Depacking nested HU...
Nested HU depacked, HU pallet n°: 00176127111000461994
Steps 6-7: Moving back HUs to supply storage type / bin...
HU 00376127111000462001 moved back to original area with TO number 0000000875
Steps 6-7: Moving back HUs to supply storage type / bin...
No need to move back HU 00176127111000461994 (not in table LEIN)
Step 8: Checking if HU fully used and quantity matches HU system quantity
HU not fully used but picked quantity > HU quantity: inventory necessary
Step 9: Inventory needed, creating physical inventory document...
Physical inventory document 0000000126 created
Step 10: Adding weighted quantity on inventory document...
Weighted quantity entered in document 0000000126
Step 11: Posting rectification in inventory document 0000000126...
Physical inventory document 0000000126 rectified
Error: rectification for doc 0000000126 not updated in DB!
=> Destination ZHGI ZPP_0285_XFP_GOODSISSUE can currently not process the message
=> Message is not sent to any destination
The errors in SM13 for this contain the program SAPLZPP_0285_HUINV_ENH (creating/changing the HUM physical inventory doc). WM Function module L_LK01_VERARBEITEN is also involved.
From SM13, it displays the following piece of code in include LL03TF2M (read the LEIN table=Storage Units table):
WHEN CON_LK01_NACH.
       IF (LEIN-LGTYP = LK01-NLTYP AND
             LEIN-LGPLA = LK01-NLPLA) OR
              NOT P_LEDUM IS INITIAL.
       ELSE.
Das ist der Fall einer TA-Quittierung wo Von-Hu = Nach-HU ist und sofort die WA-Buchung erfolgt. Dann steht die HU noch auf dem Von-Platz, daher darf hier kein Fehler kommen, sondern es wird ein. Flag gesetzt, daß verhindert daß die LE fortgeschrieben wird.
         FLG_NO_LE_UPDATE = CON_X.
        MESSAGE A558 WITH P_LENUM.
       ENDIF.
Translation in English of the German text via Google:
"This is the case where confirmation of a TO source-HU = destination-HU, and now the WA (Good Issue?)- made book. Then, the HU is still on the From-space may therefore come here not a mistake, but it sets a flag that prevents that the LE is updated."
Thanks and Regards,
Prabhjot Singh
Edited by: Prabhjot Singh on Aug 2, 2010 4:39 PM

Hope you have carried out following things in Production ( Please refer to SAP help before actually doing it in production).
1. Transport the predefined characteristics from the SAP reference client (000) to your logon client.
2. Adopt Predefined Message Categories - In this step, you copy the process message categories supplied by SAP from internal tables as Customizing settings in your plants.

Idocs not sent ?

Similar Messages

Maybe you are looking for