When a COMMIT WORK is issued, in what order does processing occur.
Refer to
the following code
1. Dialog-task FORM routines logged with PERFORM…. ON COMMIT.
2. High-priority (V1) update-task function modules.
3. Low-priority (V2) update-task function modules.
1, 2, 3
2, 3, 1
3, 2, 1
Refer to the following code. How would you program a generic lock on all rows of a
table that have key values 'AA', '111' for the first 2 fields
Call Function Enqueue_ESMYLOCK
Exporting
Field1 = …
Field2 = …
Field3 = …
It is not possible in this case
Field 1 = ’AA’, FIELD2 = ’111’, Field3 = Initial
Field 1 = ’AA’, FIELD2 = ’111’, Field3 = Space
Field1 = Generic, Field2 = Generic, Field3 = Space
When are V2 updates processed
Parallel to relative V1's
After all V1's are complete
Before V1's are started
After each related V1
What is true about V2 updates within the same SAP LUW
An error in one V2 function module cause all other V2 functions to be
rolled back
Each V2 function module for a given COMMIT WORK always runs in
its own (separate) DB LUW
V2 errors cause V1 updates to be rolled back
They are usually time critical updates
The Scope Parameter for your lock object function module has been set to 2. What
does this imply..
(More than one answer is correct)
The locks are automatically released when the updates complete
You must release the locks programatically
An update termination error holds the locks
Locks generated in the dialog program are passed on to the update
program
How are locks removed from the lock tables
Commit Work statement is issued
The database breaks
The update task removes them at the end of the SAP LUW
The update task removes them at the beginning of the SAP LUW
A commit work is issued in a transaction that employs asynchronous updating,
what takes place.
(More than one answer is correct)
User is notified of updates
SAP LUW is concluded
Update requests are processed
Database commit is triggered
What is true about Perform… On Commit.
RollBack Work is allowed in the FORM
Commit Work is allowed in the form
Multiple calls to a FORM result in single execution of the FORM
Parameter passing is allowed
Identify the synchronous update techniques.
(More than one answer is correct)
PERFORM.. .. ON COMMIT and WAIT
Update table.. ..
COMMIT WORK AND WAIT
CALL FUNCTION in Update Task
Which statements would conclude a SAP LUW.
(More than one answer is correct)
MESSAGE S101
CALL Transaction
COMMIT WORK
ROLLBACK WORK
What attribute on an update task function module determines how update requests
are processed
Application
Function Group
Function Type
Processing type
A commit work is issued in a transaction that employs asynchronous updating,
what takes place.
(More than one answer is correct)
User is notified of updates
SAP LUW is concluded
Database commit is triggered
Update requests are processed
Which does not provide synchronous processing.
PERFORM.. .. ON COMMIT
an update-task function module triggered with COMMIT WORK
an update-task function module triggered with COMMIT WORK AND
WAIT
Batch Input Programs
The following can cause long running queries
(More than one answer is correct)
SQL that does not pick any DB index
‘For All Entries’ over an INNER JOIN
SQL with access using a secondary index field
‘For All Entries’ with an empty driver table
What will cause the system to implicitly trigger database commits.
(More than one answer is correct)
At User-Command
CALL SUBSCREEN
Exit the Transaction
CALL TRANSACTION
Message I001.
Mark the items that are true with the Asynchronous Update technique in a SAP
LUW.
(More than one answer is correct)
You can combine update requests from consecutive dialog steps
COMMIT concludes the SAP LUW
Requests are not passed directly to the DB
Update task functions are logged in the SM12 log tables
All updates are performed or none at all
What Functions are generated on the Activation of Lock Object EZMARA.
(More than one answer is correct)
DEQUEUE_EZ_MARA
ENQUEUE_EZ_MARA
DEQUEUE_EZMARA
ENQUEUE_EZMARA
