Hierarchy
![](/abap/icon/s_instal.gif)
⤷
![](/abap/icon/s_b_tree.gif)
⤷
![](/abap/icon/s_pckstd.gif)
Basic Data
Data Element | JIT_DELSB |
Short Description | Delete Buffer |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | RADIO | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Delete SB |
Medium | 10 | Delete SB |
Long | 21 | Delete shared buffer |
Heading | 0 |
Documentation
Definition
Causes the data in question to be seleted from the shared buffer.
Use
When a JIT call is being processed, the system draws on the data that is stored in the shared buffer.
If you change this data and the changes are written to the database, you should ensure that the data in the shared buffer is deleted (otherwise the system will be using data that is no longer current). Once you have deleted data from the shared buffer, you can reconstruct it using the current data from the database.
Note
Call up the corresponding transactions again. This will ensure that all data in the global internal tables is also be deleted.
Dependencies
Only the shared buffer of the current application server is deleted. If you use several servers, delete the shared buffers on all the application servers used for processing JIT calls to ensure that your data remains consistent. Theoretically, the JIT process should only be processed on one application server.
History
Last changed by/on | SAP | 20050301 |
SAP Release Created in |