Idoc getting stuck up in SM58

Hi All,
Previously we have created one outbound Idoc. we were passing data to external system via XI. it was successfully reaching to external system.
now we have added one more segment to existing Idoc. after processing doc, in WE05 transaction, Idoc status is showing as 03 i.e. data successfully passed to port. the issue is that the Idoc is not getting passed to external system i.e. XI . In SM 58, the Idoc is getting stuck up. it gives error message as below,
EDISDEF: Port SAPCAG segment defn Z2WY_SV_DLR000 i n IDoc type ZWY_SV_SPG_
Message no. SR053
Please let me know if anybody has idea on this.
Thanks,
Chandra

Hi Chandrashekhar,
If you are using XI/PI, go to IDX2 transaction and see whether the idoc is re-loaded successfully with new segment. If not, just delete the idoc and load it again for the port you are using. I think this should fix your problem.
Thanks,
Adithya K

Similar Messages

IDOC RSRQST is getting stuck frequently, it leads to delay in data loading

hi,
we are using SAP R/3 4.7 E and SAP Netweaver 2004s as BI server .
On daily basis we are loading the data from R/3 to BI system . we are facing problems in data loading
IDOC RSRQST is getting stuck frequently, which leads to delay in data loading..
Please guide me to resolve this issue .
Thanks in advance .

Thanks for your reply kumarsen . I have gone through the referred forum .
In my case , I have checked the TRFC, conncetivity between R/3 and BW and Job scheduled as priority C .
Still many Idocs are got stuck in R/3 [approx every 5 min once] . we are releasing the Idoc's through BD87 only .
Please suggest for some permanent solution .

Idocs stuck in ECC SM58

Dear Experts,
I have an ICO configured scenario where sender is ECC and receiver is a 3rd party application (Sender IDOC_AAE-PI-SOAP asynchronous scenario). Idocs are stuck in SM58 of ECC, connection test of relevant RFC destination is successful.
Error text: Name or password is incorrect (repeat logon)
Please help in resolving the issue.
Thanks and Regards,
Mani

Hi Mani,
Please check the RFC user name and password which you have mentioned in RFC destination with the help of basis team, it will resolve your issue.
Just mail the screenshots to basis team they will help you.
Regards
Bhargava Krishna

Inbound Queues getting stuck up in PI7.1 for Idoc scenario Mpackg. enabled

Hi Experts,
We have an issue while processing Single Idocs in PI 7.1.
we have extended MATMAS05 and we are processing these via PI to FTP folder.
The inbound queues are frequently getting stuck.we will be sending atleast 1000 idocs every hour from R3.The processing time is very slow for this interface and its impacting other interfaces which we are currenlty having.
We have followed the webblog by William Li "Step-by-Step Guide in Processing High-Volume Messages Using PI 7.1's Message Packaging" but still the processing time for Single Idocs is very slow.
We have to use single idocs as we will send only the changed materials from R3.
Could you please assist us in overcoming this issue.
Many thanks in advance.
Points will be awarded for valuable feedback.
Cheers
Jyoti

Hi Jyoti,
Message Packaging works PI7.0 SP 13 and PI7.1 .
we have to configure Message Packaging manually ,
Step 1) 1. Enable packaging for the integration server
SXMB_ADM -> Change Configuration (F9), create a new entry:
Category: RUNTIME (PI7.1)
Parameters: PACKAGING Current Value: 1 (for active) .
Default Value in PI7.0
Current Value: 0 (for inactive)
Step 2) Create "Package Configuration Type u201C
Use Transaction SXMS_BCM .
Configuration Type : Any name.
Description: any text to describe the configuration type .
Wait Time : 60 seconds
Number: 100
Maximum Package Size. 2 MB
Step 3) Create "Sender/Receiver Definition
Transaction :   SXMSIF (Create New Entry).
Sender/Receiver ID:PACKAGE_DEMO .
Description :
Interface Name: Interface Name used in Receiver Determination.
Interface Namespace:   Interface Namespace used in the Receiver Determination .
Step 4: Create "Specific Package Configuration"
Transaction :    SXMS_BCONF .
Step 5: Package Monitoring
TX: XMSPKSTATCNF
Follow above steps and configire message packaging , then you feel diference,
actuualy i configured message mackaging,i am feeling the difference.
if any issues let me know.
Cheers,
Raj

Reasons why TRFC's get stuck in SM58

Hi
Can anyone give reasons why TRFCS get stuck in SM58.
We have a problem and it isnt as simple as just releasing them manually as it is happening a lot so wondered if there was any tables or log that could be deleted etc
Cheers
Andy

Hi,
Please check the OSS Note 1025249 - Entries in transaction SM58 "hang"
Thanks,
Sridhar
Edited by: Sridhar Kaukuntla on Jun 30, 2009 9:40 PM

IDOCs are "stuck" in the transaction IDXP

Hello,
I have a problem: IDOCs payment fornecedres are "stuck" in the transaction IDXP. I do not know exactly what is happening, but I release the IDOCs in IDXP and then they get stuck in the transaction SMQ2.
In transaction SM58 has an error log "Command to tRFC / qRFC: Execute LUW again.", Which is the same that appears in the log SMQ2.
The only thing I got is that the identifier field "package" is not filled in within the IDOC IDXP, but do not know if this influences into something.
Has anyone experienced a similar problem and could help me?
Thank you.
Edited by: fernando.mbernardi on Jan 9, 2012 2:26 PM

Hi,
It has nothing to do with Package filed,
please check below things...
Check if the Idocs are configured to process immediately in the partner profile.
Check if the Queues are scheduled to run automatically.
Check if the connection between the servers are working fine thru sm59.
Thanks...
Sukarna

Executing Idocs if stuck

Hi All,
When the data is moved fom ECC to BI, the idocs are getting stuck and hence the process is getting delayed.
One way to clear this queue would be loging to ecc side and then executing the LUWs.
Is there any other way to clear the idocs from the queue or excecute them.
Please do put in your thoughts on this.
Thanks in advance,
Veena A

Veena,
I hope there are so many threads available about this. Search with key work "BD87". You can find somany.
Executing LUW's is while transfering data after the extraction process. That is done in SM58 transaction.
But the IDocs could be stuck before the extraction. To find out whether there are any IDoc stuck in the source system, go through the following steps.
Go to TCode BD87 in the Source System.
In the selection screen, input the following values.
Partner system: <BW/BI Logical system name>
IDoc Status: 64 (IDoc ready to be transfered)
Message type (Optional): Most of the times it will be RS*
Execute the transaction, it will show you if any IDocs are in 64 status. Expand the node and select the IDocs that are in 64 status, Click on "Process" button in Appl tool bar.
If you look at the details in the Data Load Monitor (RSMO), also you can find out the OLTP IDoc number. That is pretty easy to process the IDoc from the source system.
Regards,
Shashi

SOAP to IDocs Scenario...IDocs getting locked at SAP

Dear Experts
We are sending measuring point details to SAP system from 3rd Party. Scenario is working fine for small amount of load. If more number of messages triggered (say 100) IDocs at SAP are getting stuck u201CMeasPoint 10000211 currently locked -> document processing not possibleu201D.
I tried configuring Sender SOAP adapter as EOIO and specified the Queue name as Test Queue. Still IDocs are getting stuck at SAP ECC. Now one more issues messages are getting stuck in queue SMQ2. We can control the flow by using BPM in PI. I donu2019t want to use BPM for this. Can we control this from SAP or using Trigger by background program in Partner profiles?
Please suggest. Thank You.
SAP Error Details:-MeasPoint 10000211 currently locked -> document processing not possible
Message no. IR007
Diagnosis
The object you want to access is locked, either
u2022     By yourself in another session, or
u2022     By another user
u2022     or by the system, which is still processing data for this object
System Response
The system cannot access the object.
Procedure
u2022     If you are locking the object yourself in another session, exit processing in the other session and continue processing in this session.
u2022     If the object is locked by another user, you can
o     contact the other user
o     wait until the other user has finished processing the object
u2022     If the object is locked because the system is still processing its data, wait a while, and then call up the object again.

1. Create a new process code "Z" and check the enque state of the objects before passing back to standard processing modules. Id also change to process immediate as part of this change
or
2. I think assuming RBDAPP01 is still used you may be able to make use of an exit there to do the same thing .. check and wait before processing.
or
3. In message mapping place a UDF that has some kind of wait timer in it (this is random and wont always work cause you wont know when the lock is dropped) but should work.
or
4. Dont use IDOC's create an abap proxy to do the work as a sync process. Processing will need to finish in the proxy and return to the PI stack before the next message is processed in the EOIO queue - this would be the prefered option as far as im concerned, it guarenteed to work and as long as your proxy sticks to the standard rouintes it should be upgrade friendly.
or
5. Use a proxy as above but dont do any processing, just use the proxy to build the IDOC and post it - then check the status of the locks until you are ready then rinse and repeat ..... but like scratching your right ear with your left hand .. but it will work.

Message getting stuck in XBQO queue - Time limit exceeded

Hi All,
We have a BPM scenario in our project (on PI 7.0 SP18), where bundle of PEXR2002 Payment IDocs are received as a single flat file. This file is then consumed by the BPM, to split the message into multiple payments using Java Mapping.
However, when we get an IDoc file of size greater than 5 MB (more than 500 IDocs), the message gets stuck in XBQO queue and eventually giving a SYSFAIL with the message "Time limit exceeded". Could you please let us know if you have encountered a similar issue and are aware of a possible solution.
Any pointers to this will be really appreciated.
Thanks & Regards,
ROSIE SASIDHARAN

H Rosie,
1) Goto SXMB_ADM-> Integration Engine Configuration->Parameter EO_MSG_SIZE_LIMIT->possible values 0 - 2,097,151 (KB)
The parameter EO_MSG_SIZE_LIMIT enables serial processing of messages of a particular size. This applies for messages with the quality of service Exactly Once (EO). If the message is larger than the parameter value, the message is processed in a separate queue.
2) Goto SXMB_ADM-> Integration Engine Configuration->Parameter HTTP_TIMEOUT->possible values n Seconds, where n is a whole number.
The parameter Specifies the timeout for HTTP connections (time between two data packages at line level). This value overrides the system profile parameter icm/server_port_n (for example, icm/server_port_0 : PROT=HTTP, PORT=50044, TIMEOUT=900). If you do not set the parameter HTTP_TIMEOUT or if you set the parameter to 0, then the setting for the system profile parameter is used.
See SAP Note 335162 for sysfail issue....
Hope these will help u....
Regds,
Pinangshuk.

Messages getting stuck in QRFC Queue

Hi,
Today I noticed that a message had gotten stuck with the status "Sheduled for Outbound Processing" (scenario IDOC->XI->File), XI 3.0 SP11.
This in turn had the effect that the whole QRFC queue got stuck, and all following messages got stuck with status "Sheduled".
I had to remove the first message from the queue manually so that XI could start to purge the other messages from the queue.
What could be the reason for the first messages getting stuck with this status ("Sheduled for Outbound Processing")?
The message was very small, just a couple of lines. One thing that comes into mind, is that XI received 4 IDOCS for the same interface, within one second. These 4 messages were assigned to different queues, but one of them got stuck. Could there be problems with XI when several messages arrive on the same interface within a very short time?
Is it possible to use Alerts to detect this kind of problem in the future? As I have understood, Alerts only handle XI "errors", but according to XI, this message did not have an "error status", it just had the status "Sheduled for Outbound processing"..
Thanks for any help,
Hans

Hi,
If the message got struck in Queue, you try to activate the queues in smq2 to reprocess the data instead of deleting it. This is the final solution. But you should able to see a dump in ST22 for this problem.
thanks,
sasi

EDI / IDoc : While posting inbound IDocs, IDocs gets into status 56

EDI / IDoc : While posting inbound IDocs, IDocs gets into status 56 with message "EDI: Sender port in control record is invalid".
But if I reprocess the same idoc without doing any changes using RBDINPUT and select radio button to processs idocs for status 56, then it gets successfully posted.
So not getting why this stucks for the first time.
Thanks in Advance..........

i fixed this my self

Loading getting stuck to master data infoobject

I am loading data to a matplant master data infoobject ,its taking hell lot of time in loading.....infact its getting stuck at a point .I am not sure what can be possible issues.
though I put some filters on plant then it loaded for some plants ,but still in some plants its getting stuck.
Actually there are some field enhancements done and and extraction code for those enhanced fields are written in R/3 side.

Hi.
1) First go to SM58....check if any TRFC is stucked......then press F6 to push them....
2) After pushing also if the load does'nt proceed.......then check for Shortdumps in ST22......
also check the jog log >> copy the request nimber >> go to the source system >> SM37 >> give the request no (BI as prefix) >> check the job log........if you find Sysfail.....that means short dump......
Then cancel the job if it is active.........make the QM status red and repeat the load.......
3) Also check the system performance........if there is any locks or deadlocks in ST04...........also check SM21......
Hope this helps you.......
Regards,
Debjani.......

I was editing photos and it was getting stuck or frozen and working really slow, so I attempting to close aperture and reopen it but it won't quit aperture and now it won't open up to my photos either. Any ideas?

I was editing photos and it was getting stuck or frozen and working very slowly. I attempted to restart the computer but it would not allow me to quit aperture. Now aperture appears in my toolbar but will not open up so I can work on any photos. Any ideas?

Did you try opening from the Applications folder?
Depending on how far that gets you, I would also take a look at the Troubleshooting Basics.

I am unable to email an image from camera roll. the image gets "stuck". cannot input email address or subject line. am unable to cancel and go back to camera roll

i am unable to email images from my camera roll. the image gets "stuck". cannot insert email address or subject line. cannot cancel... return to camera roll.
what to do. i tries taking new picture and sending it in an email... same thing... gets "stuck "
Waht to do ?

Hello lohmann8,
Thank you for providing so much detail about the issue you are experiencing with emailing photos from the Camera Roll.
The first thing I recommend is quitting and relaunching the applications on your iPhone:
Double-click the Home button.
Swipe left or right until you have located the app you wish to close.
Swipe the app up to close it.
You can find the full article here:
iOS: Force an app to close
http://support.apple.com/kb/ht5137
If you are still seeing the same issue after quitting and relaunching the Photos and Camera app, I recommend restarting your phone and then resetting if it's still not working:
Restarting your device
Press and hold the Sleep/Wake button for a few seconds until the red "slide to power off" slider appears, and then slide the slider.
Press and hold the Sleep/Wake button until the Apple logo appears.
Note: Reset your device only if you are unable to restart it.
Resetting your device
Press and hold the Sleep/Wake button and the Home button together for at least ten seconds, until the Apple logo appears.
You can find the full article here:
iPhone, iPad, iPod touch: Turning off and on (restarting) and resetting
http://support.apple.com/kb/ht1430
If the issue persists, the last thing I recommend is backing up and restoring your iPhone:
iOS: How to back up and restore your content
http://support.apple.com/kb/HT1766
iTunes: Restoring iOS software
http://support.apple.com/kb/HT1414
Thank you for using Apple Support Communities.
Best,
Sheila M.

Logout, restart, shutdown all get stuck

After Quicksilver G4 has been idle for a few hours and I come along to shut it down or log out, it starts the process but gets stuck at the blue screen and spinning doohickey. (not the beachball). I've let it sit for over a half hour.
I can SSH into it and there are no stuck processes, no CPU overload, no memory overruns. It's just sitting there drooling.
The only other symptom is that the eject key doesn't function sometimes. If it is one of those times, I can be sure it will hang on reboot. Other times the eject key works fine regardless of whether there is a disc in there or not.
Happened with 10.5, 10.5.1, 10.5.2, but never with 10.4.x
Strange huh?

Open Activity Monitor (/Applications/Utilities/Activity Monitor.app), and see if you can spot any thing to do with Safari or Firefox in there.

Idoc getting stuck up in SM58

Similar Messages

Maybe you are looking for