topic Re: Explain this TCODE in Application Development and Automation Discussions

Explain this TCODE

Former Member — Wed, 03 Oct 2007 09:32:51 GMT

Hi,

can anyone explain this TCODE SM!3 briefly.

Regards

sekar sasi.

Re: Explain this TCODE

Former Member — Wed, 03 Oct 2007 09:57:16 GMT

Hi Sasi,

SM13- Monitoring Update Process

• The update process is in charge of executing database changes when requested by dialog or background work Processes.

• R/3 User has No Influence on Update Service

• Update requests are not generated by directly users. Instead they are generated by user’s dialog or Background activities.

It has two types of components:

V1 components for executing time-critical database changes (Immediate)

V2 components for executing non-critical database changes (Regular Interval)

With the SM13 -Update Manager, you can do the following:

• Activate/ Deactivate the Updating function

• Restart processing of unprocessed update records that have accumulated as a result of shutting down the Updating function.

• Displays update records that are pending an update.

• Reprocess an abnormally terminated update record.

• Delete update records.

• Read update statistics.

You can find more information at:

http://help.sap.com/saphelp_47x200/helpdata/en/e5/de870535cd11d3acb00000e83539c3/frameset.htm

Thanks

Ravi

Re: Explain this TCODE

Former Member — Wed, 03 Oct 2007 10:02:29 GMT

I believe u r want to know about SM13 t-code.

SM13---Display Update Records

It helps in

display updates

test and debug canceled updates

reset updates

delete updates

display statistics on updates

U can find more information on

http://help.sap.com/search/highlightContent.jsp

I hope i am able to help u some way.

Regards

Anil

Re: Explain this TCODE

Former Member — Wed, 03 Oct 2007 10:06:16 GMT

Hi Sekhar,

Hope the following throws some light on your querry regarding the update workprocess.

When a user wants to change a record in an SAP transaction, he/she first calls the

corresponding transaction , makes the appropriate entries on the screens,

then finally initiates the update process by saving the data.

This process triggers the following steps:

1. The program locks the data record for other users.

2. If the enqueue work process writes the lock entry to the lock

table, then it passes the lock key it created to the user, the program reads the

record to be changed from the database and the user can change the record

on the screen image of the SAP transaction.

3. In the active dialog work process, the program calls a function module

and writes the change request to database update tables. These are also called VB* tables, because

their names begin with VB. They act as temporary memory and store the

data to be changed until it can be collected and written to the target tables

in the database

4. At the end of the transaction (for example, when the user saves the data

possibly after completing other dialog steps), the program initiates the close

of the transaction with the statement COMMIT WORK. The work process that

is handling the active dialog step triggers an update work process.

5. On the basis on the information transferred from the dialog work process, the

update work process reads the log records that belong to this SAP transaction

from the VB* tables.

6. The update work process passes the changes marked and collected in the

VB* tables to the database as a change request and evaluates the database

response. If the changes were successfully written to the target tables, the

update work process triggers a database commit after the last change to the

database and deletes the entries from the VB* tables. If an error occurs, the

update work process triggers a database rollback, leaves the log records in

the VB* tables and marks them as defective.

7. The lock entries in the lock table are reset.

V1 updates refer to time-critical changes. They are relevant to

objects that have a controlling function in the SAP system, such as a

change to the material stock or an order creation.

V2 updates refer to less time-critical changes, for example, purely

statistical updates such as creating a change document.

If an error occurs during an update, then processing of the active update

component terminates.

SM13 (update requests) provides an analysis tools to handle terminated updates.

Once the error that caused the termination has been corrected ,

the update should be restarted.

For a more detailed insight pl follow the following link

http://help.sap.com/saphelp_nw04/helpdata/en/e5/de870835cd11d3acb00000e83539c3/frameset.htm

Pl dont forget to award is resolved.

Regards