SAP ABAP Data Element RWSH_PACKET_SIZE (Packet size (no. of alloc.tabs))
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ WAUF (Package) Application development R/3 Purchasing, Allocation table
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ WAUF (Package) Application development R/3 Purchasing, Allocation table
Basic Data
Data Element | RWSH_PACKET_SIZE |
Short Description | Packet size (no. of alloc.tabs) |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | NUM5 | |
Data Type | NUMC | Character string with only digits |
Length | 5 | |
Decimal Places | 0 | |
Output Length | 5 | |
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 | Pckt size |
Medium | 15 | Packet Size |
Long | 30 | Packet Size (No. of AllocTabs) |
Heading | 10 | Pckt size |
Documentation
Definition
Defines the grouping of allocation tables.
Use
The package size defines the number of allocation tables that are read from the database and processed in a loop. You can use this value to control how much data is processed.
The packet size can be determined on the basis of the number of materials and plants in the allocation table. If the number of materials and plants is high, you should use a small package. If the number of materials and plants is low, you can use a large packet.
Example
- Using a small packet for a large number of allocation tables ensures that the internal tables of the program do not get too big and therefore reduces the amount of memory required.
- A large packet reduces the number of times the database is accessed, but can lead to more memory being needed.
History
Last changed by/on | SAP | 20010607 |
SAP Release Created in | 50A |