SAP Netweaver Enterprise Controlling

Unjustified termination of iteration

June 23, 2009 at 4:08 am

[ACTCLOSE] [cpu termination] [dpm iteration] [It] [iteration] [termination]

1. ABC: Program termination TABLE_INVALID_INDEXSymptom The program termination TABLE_INVALID_INDEX occurs when you use the F4 help in the template maintenance. Other terms CO-ABC, ABC, Activity-Based Costing, template, template function Programs: RKABCCD9, SAPLKWTU Transactions: CPT1, CPT2 Reason...
2. CKUC: Termination SAPSQL_ARRAY_INSERT_DUPREC with savingSymptom You execute a multilevel unit costing (transaction CKUC). When you save the result, the program terminates with a short dump of the type SAPSQL_ARRAY_INSERT_DUPREC with the exception CX_SY_OPEN_SQL_DB. Other terms Worklist,...
3. FPG3: Termination COLLECT_OVERFLOW_TYPE_P in SAPLKAUPSymptom Program termination with ABAP short dump COLLECT_OVERFLOW_TYPE_P in program SAPLKAUP, FORM routine COLLECT_COEP. According to the short dump, field MEGBTR is undersized. The error occurs during the transfer of a reconciliation...
4. KE21N: termination CONVT_OVERFLOW if value field too largeSymptom When you enter an actual line item in CO-PA with transaction KE21N, a program termination occurs if you enter a value field with too many characters on the tab page ‘Value...
5. Termination DATA_LENGTH_0 in the form routine SPLIT_COMPLEXSymptom In the form SPLIT_COMPLEX in the program LKYERU04, the termination DATA_LENGTH_0 occurs. For example, the problem can occur in transaction KEA5 if you want to save a characteristic despite warnings. Other...
6. Termination DATA_LENGTH_0 in the form routine SPLIT_COMPLEXSymptom In the form SPLIT_COMPLEX in the program LKYERU04, the termination DATA_LENGTH_0 occurs. For example, the problem can occur in transaction KEA5 if you want to save a characteristic despite warnings. Other...
7. Termination DATA_LENGTH_0 in the form routine SPLIT_COMPLEXSymptom In the form SPLIT_COMPLEX in the program LKYERU04, the termination DATA_LENGTH_0 occurs. For example, the problem can occur in transaction KEA5 if you want to save a characteristic despite warnings. Other...
8. MR11: Termination when posting to previous periodSymptom Using transaction MR11, you post to a material in the previous period. However, the material already has the material ledger status “entered at closing” in the previous period. The program terminates...

Symptom

During the multlilevel price determination, the iteration of a cycle terminates due to presumed divergence, even though the cycle would actually converge due to its values.
This results in the following symptoms:
In the log of the multilevel price determination, the system issues warning message CKMLMV 039 “Iteration of cycle &1 diverges in currency/valuation &2″.In the log of the multilevel price determination, the system issues message CKMLMV 005 “Cycle &1 broken off after &2 repititions”.Depending on the error handling selected for the case of non-convergence, the materials of the cycle either remain completely unprocessed, or the system does not transfer all differences in the cycle. The differences not transferred remain as “non-allocated” differences for the input materials.Other terms

ACTCLOSE: Iteration, convergence
Reason and Prerequisites

The iteration terminates due to the
logic implemented from Note 1125252 about advance recognition of field overflows.
This logic check is too strict in some cases, and the iteration terminates, although the cycle would converge without a field overflow occurring. This may occur, for example, if the price differences are already very large during the first iteration run, but would have reduced during the iteration.
Solution

Implement the corrections.

Permalink