| # Performance Parameters (cpcom0100m000) This session contains: A history list of parameter sets and their effective dates The current parameter set, at the top of the list (without an effective date) Performance aspects The settings in this session could affect system performance and database growth. For more information, refer to Multiple bshells concept Related topics To configure Enterprise Planning Date The date and time that the parameters are valid. The parameters are valid up to the effective date of a more recent parameter setting. Description The description of the parameter set. For example, you can indicate why you change the parameters. Note By default, the Description field contains the date and time when the previous parameter set was saved. In order to avoid confusion, if you change the parameters, change or delete the description as well. Display Time Interval The amount of time (in seconds) that ERP LN waits before it displays new information in the progress bar of the Generate Order Planning (cprrp1210m000) session. Sessions that process large volumes of data usually display some runtime information, which enables you to monitor the session's progress. However, if the screen is refreshed frequently, this can affect system performance. Maximum Number of Planned Orders per Requirement The maximum number of planned orders that the order-planning process generates for one requirement. If ERP LN needs more planned orders to fill the requirement, ERP LN generates one more planned order to fill the remainder of the requirement. You can use this field to prevent particular types of errors. These errors can cause ERP LN to generate an extremely large number of planned orders. For example, if you accidentally set an item's maximum order quantity to 1 and you require 1000 piece, ERP LN must generate 1000 planned orders of quantity 1, just to fill one requirement. In general, that situation is undesirable. If you set the Maximum Number of Planned Orders per Requirement field to 10, ERP LN generates 10 planned order of quantity 1 and a final planned order with a quantity of 990. Average Number of Planned Orders per Item In this field, you can indicate the estimated number of planned orders per item. If you use parallel processing, ERP LN reserves a range of order numbers for the planned orders that each bshell generates. ERP LN uses this field to determine the size of the range of reserved order numbers. Important! If this value is too small, the servers for parallel processing try to use the same order number, which leads to errors. Workload per Server In this field, you can define the number of items included in each batch that is distributed over the parallel bshells. The multiple-bshell solution dynamically calculates the optimal workload per server. The number you specify in the Workload per Server field is the upper limit. Performance aspects The setting of this field could affect system performance and database growth. For more information, refer to Workload per server Workload Based on Operations If this check box is selected, the criterion ERP LN uses for workload distribution over the bshells, is the routing composition of each item. The more operations a routing of an item is composed of, the more weight it has. Performance aspects The setting of this field could affect system performance and database growth. For more information, refer to Workload based on operations Dynamic Workload Calculation If this check box is selected, the total workload is equally distributed over the available bshells. |