E - 20210826 - CK40N Issue
E - 20210826 - CK40N Issue
E - 20210826 - CK40N Issue
Symptom
During the analysis of the costing results in Transaction CK40N, the system
displays the results of a different costing run. Note 685958 is either
implemented in your system already or the note is not relevant as the
prerequisites are not fulfilled in your case.
Other Terms
Cause: The extract that was created during the Analysis step for a calculation
run is sometimes overwritten by the analysis of a different calculation run.
Prerequisite: You execute the Analysis step for two calculation runs that were
created on the same calculation run date. The names of the two calculation runs
can only be distinguished by the first two characters.
Solution
When selecting the calculation run names, select names that were created on the
same calculation run date, but which do not just vary in terms of their first
two characters. Otherwise, this results in the symptom described above as only
the last six characters of the name are used to determine the extract name.
• You create the calculation runs Z3500 and 27500 with the calculation run
date 31.05.2005 (May 31, 2005). As the names of the two calculation runs
only vary in terms of the first two characters, the function module
CK_RESULTS_GET_EXTRACT_NAME determines the same extract name for both
calculation runs. The extract for the costing run Z7500 therefore overwrites
the extract from the costing run Z3500 and vice versa.
• The described symptom does not occur if the user selects the calculation run
names differently, for example:
Software Components
1093911