Hierarchy
⤷ MM-CBP (Application Component) Consumption-Based Planning (See Also PP-MRP)
⤷ WRPL (Package) Retail: Replenishment
Basic Data
Data Element | WRPACKETSIZE |
Short Description | Packet Size |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | INT4_NOS | |
Data Type | INT4 | 4-byte integer, integer number with sign |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 10 | |
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 | 20 | Packet Size |
Heading | 10 | Packet sz. |
Documentation
Definition
The packet size indicates the number of replenishment items (recipient/material combinations) that can be processed in a logical unit.
This parameter is only relevant for background processing.
You use this parameter to limit the number of items that have to be rejected when an error occurs. The smaller the packet size, the fewer items have to be reprocessed should an error occur. Small packets slow down performance, so you should not choose a value that is too small. Making a packet too large, on the other hand, can also cause performance problems. There is no optimum range for the packet size, since this depends on various different factors. Determine the correct packet size by testing.
A new packet is created for each recipient even if this means that it is smaller than the permitted packet size set. If the number of items for a recipient already entered exceeds the packet size, the system tries wherever possible to group together items belonging to the same recipient in one packet.
Therefore, items for a recipient that is already entered, that exceed the packet size, are included in the current packet. The number of additional items can be limited by setting a tolerance limit.
Packet size is only relevant for background processing. In online processing, all items are processed as a single logical unit.
History
Last changed by/on | SAP | 19980706 |
SAP Release Created in |