Tuesday, January 7, 2014

Update work process (V)

BASIS FAQ'S

                                              Update work process (V)
 
 A.    It is used to update the database by reading from the temporary tables. It can’t    communicate     with user directly
B.    There are 2 types of update work process. They are v1 and v2
        V1 update is used for critical jobs and V2 update is used for non critical jobs
C.    We need at least one update work process per sap system and we have more than per dispatcher
D.    The update profile parameter name is rdisp\wp_no_vb, rdisp\wp_no_vb2
E.    Update monitoring is – SM13
        Here we can check critical and non critical updates. We can specify date and time
F.    Update program administration – SM14
        This transaction code is used for active to deactivate & deactivates to activate update request and you configure the update servers, update groups and display & monitoring update parameters.
G.    Update temporary table is VB*
1)    Vbmod – update function module
2)    Vbdata – update data
3)    Vberror – update error information
4)    Vbhdr – update header
5)    Vbwrk – work list for mass processing at a time have update
H.    Update status are
1)    Init – the status will be initial.
2)    Run – update is started in main database.
3)    Error – update is thrown into error.
4)    Auto – update is thrown into error due to problem in database space.
I.    Update tables are stored in TBLOD
J.    SAPMV45A: which update work process is going on?

K.    Update types are 3: they are
1)    Local update: Dialog work processes update the directly in Database that is called local update.
2)    Synchronous: Dialog work processes update goes to the temporary table that is called 
        synchronous.                   .
3)    Asynchronous: temporary table goes to database that is called asynchronous
L.    Update statistics are 4:  they are
        Read, Write, Execute and Delete
M.    Update parameters
1)    rdisp\vb_stop_acive: Set to “0” so that update can be deactivated. If the value is set to be “1” update can be activated.
2)    rdisp\vbdelete: This parameter is used to delete the old update requests based on the no. of days. It will delete default 50 days.
3)    rdisp\vbmail: It is used to send an email. It update thrown an error which can be viewed in “SBWP” (“sap business workplace”) based on your user (set to “0” or “1”).
4)    rdisp\vbname : Name of the server running where update are processed
5)    rdisp\vbreorg: It is used to delete the incomplete update request.
        1=delete, 0=no, we can also schedule a background job “RSM13002” but it will delete the update request which are in completed it will be deleted after restarting.
6)    rdisp\vb_delete_after_execution: It is used to delete the update request soon after the execute of the update. Set it to”1” to delete the record (or) “2” to the record will not be deleted. If it is set to “1” the background job “RSM13002” is not required. If not schedule periodically daily during off peak hours.

3 comments:

  1. I feel it is right place to get info on SAP GRC.I will get detailed information in this blog. This blog is suitable to learn sap people. please share this type of blogs. Anybody interest to learn please click this linkSAP GRC ONLINE TRAINING.

    ReplyDelete
  2. Fascinating read! It's clear that supply chain management is evolving rapidly, and businesses need to adapt to stay competitive. Your breakdown of the different supply chain models, from lean to agile, was both informative and insightful. Each approach has its merits, and understanding when to apply them can make a significant impact on a company's success. Looking forward to delving deeper into this subject with your future posts! Fusion SCM Training in hyderabad

    ReplyDelete