Optimizing package size for multilevel price determination
[A] [determination] [optimizing] [self determination] [wage determination]
Symptom
The following problems occur during the multilevel price determination:
The runtime error TSV_TNEW_PAGE_ALLOC_FAILED occurs due to a memory overflow.In parallel processing, the processing time of individual packages exceeds the time limit set for the dialog work process. This leads to a termination of the relevant parallel mode.Other terms
ACTCLOSE, performance, BOM, bill of material
Reason and Prerequisites
The problems occur because individual packages contain datasets that are too large. This is due to the following reasons:
1. The package contains materials with a very large actual BOM. As a result, the data of a large amount of components and activities has to be read.2. The package contains a large cycle.
In the fist case, the problem can be solved by reducing the package size for materials with a large actual BOM. In extreme cases, these materials should be processed individually.
However, it is difficult to identify the materials with a large BOM;
reducing the package size for all materials would also impair the runtime.
Solution
After you implement the corrections, the closing entry automatically adjusts the size of each package to the size of the actual BOM.
The value (the default value is 50) set in the “Package size” parameter then only defines the maximum package size permitted by the program. For materials with a large actual BOM, the program then automatically selects a smaller package size.
Implement the corrections:
Before you can implement the corrections using transaction SNOTE, you have to carry out the following manual tasks:
Add new fields to the table CKMLMV011: (To do this, call transaction SE11, enter the table name in the “Database table” field and choose “Change”.)
In the “Fields” view, add the following new fields:
Field: CNT_INPUTS
Key: ‘ ‘
Initial Values ‘ ‘
Data Type: NUMC
Length: 10
Decimal Places: 0
Field: CNT_WIP_INPUTS
Key: ‘ ‘
Initial Values ‘ ‘
Data Type: NUMC
Length: 10
Decimal Places: 0
Save and activate the changes.
When you have carried out the manual tasks, implement the attached corrections using transaction SNOTE.