Update Monitoring ( SM13 )


The record that needs to be updated by update process is displayed in SM13 with status INIT. If the records stay for a longer time in INIT status that indicates the updates are busy or there are no sufficient update processes or update mechanism is deactivate from SM14.

Update handles the record and changes the status to “RUN”. If the update stays a long time in status RUN then any one of these might be the problem you are facing.

1. Longer Update
2. Dead Lock (Needs to inform SAP for Program correction)

Updates which could not be updated will be thrown into ERR Status.

1. Update deactivated in SM14
2. Programming problems in LUW
3. Table Space overflow (ORA-1653; ORA-1654)
4. Max Extents reached (ORA-1631; ORA-1632)
5. Archive Struck (ORA-255; ORA-272)

Each SAP transaction is considered as Single LUW (Logical unit of work) which in turn contains multiple LUW’s needs to be committed to committing the SAP Transaction. If any one of the LUW is failed the entire transaction is rolled back. That is the reason why dialogue updates Temp Table.

1. User submits the request.
2. Dialogue handles the request.
3. Obtains lock from Enqueue so the data consistency is achieved and the records are only for display.
4. Updates the request in Temp tables (VBHDR, VBDATA, VBMOD, VBERROR)
5. Gets the transaction ID from NRIV (Number Range Interval Table)
6. Update gets initiated to update the VB* content permanently into the database.
7. Update inherits the locks.
8. Updates the database based on transaction ID.
9. Update releases the lock from the record.

Leave a Reply

Your email address will not be published. Required fields are marked *

%d bloggers like this: