Update Request
Update Request
Definition
An update request or update record describes the data changes defined in an SAP LUW, which are carried out either in full or not at all (in a database LUW). (This only applies to V1 updates. V2 updates are triggered once the V1 update has been completed, and therefore take place in a separate database LUW.) See also
The Update Process.An update request is identified by means of its update key.
Use
Once the dialog transaction has been completed (
COMMIT WORK ), and the update task has been called up, the update header is created. The update request is then created. The update data is stored in the update modules (function modules), which were created with the ABAP statement CALL FUNCTION '…' IN UPDATE TASK . The function module type is defined in the transaction for maintaining function modules (transaction se37,
Function Builder). See below for further details.
Structure
An update request comprises an update header, V1 modules (or components), V2 modules and a
collective run.An update module corresponds to a function module, and contains the update data and, in certain cases, error information, which is generated if the update is canceled.
The following graphic illustrates the structure of an update record.
Integration
The following update tables in the database contain the following information:
Update Table |
Contents/Description |
VBHDR |
Update headers (one per update record), see also Displaying the Update Header |
VBMOD |
Update modules (one per function module), n V1 modules and m V2 modules per update request (see also Displaying Update Modules) |
VBDATA |
Data which is transferred to the modules (variables, structures, internal tables) |
VBERROR |
Error information which is generated if an update is canceled |
The update tables are structured as follows:
You can also call this table up in the SAP System with the table maintenance transaction (se16). Detailed information on maintaining tables can be found in the relevant documentation.