Settlement Error Split Delta

[Former Member]

Dear Guru,

I've problem when do settlement CO88 the error :

Order xxxxxxxxx: split delta (3.077,40 in currency 10) according to standard price

Message no. MLCCS015

Procedure

The cost component split determined from the order history has a total value of zero, or the total value of the split varies greatly from the total of the costs posted to the order.

The variance between the total value of the split and the total of the costs posted to the order must be split in accordance with the standard price split. Use standard program MLCCS_KO88_TREATMENT to set the handling of the delta according to standard price split (option "D") for costs on the order.

I already find in this forum for Snote but stil get an error.

For step closing there is no error shown like KKS2, KSII/KSPI,CON2 (there is no report shown but there is no error ether), KKAO, KKS1 , but when settlement there is error.

form information : i use legal and group valuation, ML and Actual costing active, Cost Splitting active, use ECC6.0 EHP 0.

try to run MLCCS_KO88_TREATMENT in SE38 but still error.

Plase need your advice.

Thank you,

Iwan

[Former Member]

Dear Jason,

Could you screen Capture how to make deault "D" in report MLCCS_KO88_TREATMENT.

Thank you,

Iwan S

[jason_shao]

Hello Iwan,

Previously, you need to delete the existing entry if you have used

before the program MLCCS_KO88_TREATMENT with a treatment type.

So please first choose delete settings for the mentioned order and then choose maintain settings afterwards.

Best regards,

Jason

[Former Member]

Dear Jason,

i already do that , delete setting and then maintain setting. but still error.

Thank you,

Iwan S

[jason_shao]

Hello Iwan,

The note 973166 provides the information about the order

number for error message MLCCS015.

According to the explanation given in note 867755, message MLCCS015 only

occurs if there are postings on the order for that no cost component

split data can be determined. If the settings for the FI postings are

correct, the system finds the corresponding cost component. For WIP

postings the system uses the cost component split of the standard price.

So, if message MLCCS015 occurs, there must be some other kind of

manual postings leading to a strange cost component split for order

settlement.

Note 1009417 will avoid error message MLCCS015 in case of

rounding errors.

For solution, you can run report MLCCS_KO88_TREATMENT to overcome this

error.

Check the note 632752 as well related to the use of program

MLCCS_KO88_TREATMENT.

Please check that you maintained option ""D"" (Split Delta according to

Standard Price) with report MLCCS_KO88_TREATMENT for the order that

is causing the problem. This should prevent you from this error.

Previously, you need to delete the existing entry if you have used

before the program MLCCS_KO88_TREATMENT with a treatment type.

Best regards,

Jason

[Former Member]

Dear Jason,

this is the result of MLCCS_KO88_TREATMENT, but still error

but still error when CO88 or KO88.

Thank yu,

Iwan

[jason_shao]

Hello Iwan,

The key point is to：

you maintained option ""D"" (Split Delta according toStandard Price) with report MLCCS_KO88_TREATMENT for the order thatis causing the problem.

But I see you are using treatment type K.

Best regards,

Jason

[Former Member]

Hi Iwan,

the reason for this issue will be

1. The difference between the order settlement values from CO and the values to be settled from the order history is insignificant. This difference amount is caused by a rounding error.
2. This problem is due to the program design. In the goods receipt posting, the system uses the standard price of the posting period for the order credit. However, if the order credit is zero, the standard price of the current period is used as a second strategy. However, this should not be the case if the material ledger is active and if there are materials with the price determination '3'; instead, the system always has to use the standard price of the posting period.

check this NOTE 632752 To solve this issue

Regards

Achyuth