Skip to Content
avatar image
Former Member

Collective Run (MC3V) is not Updating SM13 records


I'm currently facing the next situation and I'd love some suggestion on where to look for a solution.

Records in SM13 are increasing as some modules are in still INIT status. We have the collective run job scheduled to run on a daily basis, however this records are not being updated and continue to be in INIT status.

I'm trying to find where to look if there's something wrong with the program that is being triggered by the job that it is scheduled in MC3V.

- Could someone please point me on where to find a log or something?

- Does having too much records in SM13 affect operation, how?

This is very similar to SAP Note 1914402, however as already mentioned, solution is not working for me.


Julio M.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Dec 21, 2016 at 11:19 PM

    Hello Julio,

    What modules are in INIT status?

    Only the V3 (collective run) modules?

    The V3 modules will be processed only if the V2 and V1 parts were already processed.

    If only the V3 modules are pending, is the job executing the collective run finishing ok? Or is it ending in error?

    If it is ending ok, you could double check the selection criteria of the job to ensure that it is indeed picking up the pending requests.



    Add comment
    10|10000 characters needed characters exceeded