Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
LE-SHP (Application Component) Shipping⤷
LE_SHP_DB_INTERFACE (Package) Database Access for Logistics Execution (Shipping)
Basic Data
| Data Element | LESHP_BYPASSING_BUFFER |
| Short Description | Database Access Does Not Take Application Buffer Into Accnt |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | LESHP_BYPASSING_BUFFER | |
| 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 | Bypass |
| Medium | 15 | Bypass buffer |
| Long | 20 | Bypass buffer |
| Heading | 0 |
Documentation
Definition
If this indicator is set (X) and transferred to the database layer via selection criteria in a request, buffering is avoided and the system accesses the database directly.
Explanation
By using the database access layer for the delivery business object (function group Le_Shp_Delivery_Buffer) you can create another database request with a (different) record of selection criteria, in spite of the fact that the buffer is already full.
This other request is taken as a limitation of the entire contents of the database, according to the selection criteria that were specified. Therefore, the request must be forwarded to the database.
A search in the buffer would not be sufficient, since this search would only further limit the deliveries that were already read in. The deliveries that satisfy the selection criteria of the current request would not be returned, because they would have been filtered out by the previous request that filled the buffer.
Bypassing the object buffer can also lead to performance advantages if the majority of delivery processing uses "common parts" global data structures. However, you should plan to switch to using the buffer at some point, since future partial-functions can then operate in individual objects in the same buffer. It is not necessary to know which partial function down the line will need what data. Each partial function fills in only the data segments of the current object that it actually needs in the buffer.
When you deactivate buffer use, you can control even finer details such as whether only reading of the buffer should be deactivated, even though the deliveries that were read from the database are still filled into the buffer (indicator = X), or whether the buffer is not to be filled in at all (indicator = Y).
History
| Last changed by/on | SAP | 19991221 |
| SAP Release Created in | 46C |
