Co-monthly close-job segmentation

Co-monthly close-job segmentation

Original: http://blog.gnolux.com /? P = 7001

 

I am taking a bath for my son ..
At this time, the phone number that shouldn't have arrived is ringing ,(............... A large conversation is omitted .......), conclusion: The monthly settlement problem .....
My mood fell to the bottom. Reluctantly but helplessly turn on the computer, set up the router, connect to the company's sap. Check it, as my colleague said, kss2
The result is incorrect. The displayed fee is the accumulation of the current year rather than the previous period fee.
There should be configuration problems, but there is no problem in the previous year, and there is no problem at the end of the previous month... Isn't it possible? I haven't even touched the CO configuration recently. I'm busy with SD.
What about new project solutions and report development. After carefully checking the operation, it is OK. Check the background configuration.

Okes: Check the Split Structure and assign it to the job by cost element group. It should be okay.

Okew: Check the splitting of cost center connections.

This problem has never been solved before. It should have something to do with the setting of an associated year, but it was okay last month. check whether this problem is correct or not.

Check the version of the cost control scope

After seeing the image below, I feel like it is basically a bit interesting.

 

99% is definitely a problem here

The problem is here that the settings for the first two years are set by the periodic price, and here the accumulative job price is used, which is also consistent with the previous error,

After modification, redo the job to split kss2 and OK ..

Analysis: it should be a small mistake made by the implementation consultant. The settings for, and 11 are the same, but they are different in.