Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Entries stuck in SM13 queue in 'INIT' status

krishg
Active Participant
0 Kudos

I have been trying to figure out why some entries are stuck in SM13 with status 'init'... user made changes to delivery using VL02N and it resulted in entries stuck in SM13 in 'INIT' status for more than 20 hours..After a while the update task is completed. This is happening randomly and it is difficult to figure out the action taken that caused this issue.

Any ideas?

1 ACCEPTED SOLUTION

raymond_giuseppi
Active Contributor

Are those V3 update ?

Regards,

Raymond

3 REPLIES 3

Former Member

Hello,

Multiple issues could be causing this -

1) First , check if the SAP kernel patch level is up to date.

2 ) Second, auto update might not be active.

What is INIT status:

Update records which have not yet been processed have the status INIT or AUTO. INIT refers to a complete update record (header, function module call of update and data elements are present), which has not yet been processed however.

What to do: SM13 -> Update records -> Update -> All records/Single

you can set the update administration so that all records with the status 'INIT' or AUTO' (all update records which have not yet been updated) are processed (as far as possible).

Warnings: please check with the user who posted the updates in the first place - make sure that they have not already reposted the update manually. If you are in doubt, please re-enter the data manually rather than using this update function.

best regards,

swanand

raymond_giuseppi
Active Contributor

Are those V3 update ?

Regards,

Raymond

0 Kudos

No, it is v1 updates. Since I did not have access to SM50, I did not realize that update task was running in background (a very long running update task).. Curious why does SAP have status 'Initial', eventhough the module was running in background.. Isn't it confusing?