SAP ABAP Data Element MD_TSIZE (Packet Size for Parallel Requirements Planning Run)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ MD03 (Package) Appl. development R/3 MPS/determin. requirements planning
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ MD03 (Package) Appl. development R/3 MPS/determin. requirements planning
Basic Data
Data Element | MD_TSIZE |
Short Description | Packet Size for Parallel Requirements Planning Run |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | INT4 | |
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 | Pack. Size |
Medium | 15 | Packet Size |
Long | 25 | Packet Size Parallel MRP |
Heading | 25 | Packet Size Parallel MRP |
Documentation
Definition
Packet size for the planning run for requirements planning or long-term planning with parallel processing.
In a planning run with parallel processing, the materials are planned in several processes via asynchronous RFC. The package size determines the number of materials in the package. The smaller the package is, the better the system can execute the process in parallel. On the other hand, each package requires RFC communication expense and a loss in performance as a result of reimporting programs and data. The optimal package size greatly depends on the individual data situation.
History
Last changed by/on | SAP | 20010918 |
SAP Release Created in | 470 |