Hi Ruks
1. Check actual price indicator in act type and ksbt
/kbk6
2. For manual price, maintain the price directly in kbk6
3. If you wanna calculate from system, use method 12 actual qty a as splitting rule in splitting structure
4, assign your mfg cost centre to the splitting structure in okew
5. In the absence of splitting structure, system uses equival no from kp26. By default it is 1
btw, this issue is a different one. We are supposed to have one issue per thread
Ajay M
Hi Ajay,
1. I am testing to calculate actual activity price from system (KSS2--->KSII)
2. Activity Type having 5 as actual price indicator
3. Everything seems to be okay still I am getting error 'KD301' and KD302 .
Have you experienced this situation.
Excuse me for the different issue for this thread.
Regards
Ruksana
Hi Ruksana
This message is coming when there is issue in splitting structure and CCtr assignment in structure.
Check the structure whether rule is taken 12 or not.
Also assign all cost cctr in structure because if there is any cost coming through SCE to your acitivity of prod CCtr will split and do not cause any error.
Kamal
Hi Ruks
refer points 3 and 4 in my reply
Ensure your splitting structure has splitting rule based on activity qty and assign mfg CC in it (okew)
@Kamal- you should not assign all CC in it. Only those CC for which you wanna calculate activity price must be there
Ajay M
Hi Ajay
I had tested one scenario where even I assigned prod cost centers having activity giving me error..because some expenses coming from down below activities through allocation and when I assign all cost centers ( as I don't go for pick and choose) it was working fine and there is no harm to assign all cctrs because if any cctr is not involve will not be effected.
However , choice is yours..
Kamal
Dear Ajay,
I have done all these basic stuffs. Still some issues and error are coming.
Further information:
I have put plant activity rate in KP26 manually.
is it mandatory to plan independent planning in KP06? or KSS2 can be run without planning in KP26. Though actual posting are there in production cost center which are assigned to OKES and OKEW.
Regards
Ruksana
Hi Ruks
Not withstanding any bug in Simple Finance, this is what I feel.. If it does not help, raise an OSS message
1. You can always enter plan rates in KP26 manually.. Ensure that Plan Price indicator in Act Type Master is set to Manual Price (I think it is 3)
2. If you want to calculate actual price automatic based on activity qty, ensure that
a. Actual Price indicator in Act Type Master is set accordingly
b. Also, check the indicator in KBK6... Set it to "automatic based on activity qty"
3. Splitting Structure is what you say you have ensured. But please provide a screenshot (OKES and OKEW) for me to review..
4. Now do KSS2 and provide screenshot of the error if it is still there..
5. Also do KSII and see if there is any error / act price is fine
Rgds
Ajay M
Dear All, Our client is using product cost collector as cost object and Cost object hierarchy for reporting purpose. However they want to see actual cost from material ledger in cost object hierarchy. Is it possible? What are configuration required? Is there standard report available to display actual cost at material ledger level in cost object hierarchy? Thanks, Aju
Hi,
Is my understanding correct?. Please check if it is perfect or just good. Please make help me to complete this list. What would be in case of process order?
Thanks in advance Ajay.
| Date | Step No. | Costing Step | Transaction Code (Repeatitive) | Transaction Code (Discrete) | Process Order | Remarks |
| Last day of the month | 1 | Manual Correction Entry (If any) | KB11N | KB11N | Will it remain same? | |
| Last day of the month | 2 | Post Statistical Key Figures (SKF) | KB31N | KB31N | Will it remain same? | |
| Last day of the month | 3 | Distribution of Cost | KSV5 | KSV5 | Will it remain same? | |
| Last day of the month | 4 | Assesment of Cost | KSU5 | KSU5 | Will it remain same? | |
| Last day of the month | 5 | Actual Cost Splitting Run | KSS2 | KSS2 | Will it remain same? | |
| Last day of the month | 6 | Actual Activity Rate Calculation | KSII | KSII | Will it remain same? | |
| Last day of the month | 7 | Revaluation at actual activity prices for Product Cost Collector | CON1 / CON2 | CON1 / CON2 | Will it remain same? | |
| Last day of the month | 8 | Actual Overhead Calculation of Product Cost Collector | CO42 / CO43 | CO42 / CO43 | Will it remain same? | |
| Last day of the month | 9 | Calculate WIP | KKAS / KKAOH | KKAX / KKAOH | Will it remain same? | |
| Last day of the month | 10 | Variance Calculation of Product Cost Collector | KKS6 / KKS5 | KKS2 / KKS1 | Will it remain same? | |
| Last day of the month | 11 | Settlement of Product Cost Collector | KK87; CO88H | KO88; CO88H | Will it remain same? | |
| Last day of the month | 12 | Cost Center Planing | KP06 | KP06 | Will it remain same? | SAP S/4 HANA still supporting |
| Last day of the month | 13 | Activity Planning | KP26 | KP26 | Will it remain same? | |
| Last day of the month | 14 | Plan Cost Spliiting Run | KSS4 | KSS4 | Will it remain same? | |
| Last day of the month | 15 | Plan Activity Rate Calculation | KSPI | KSPI | Will it remain same? | |
| Last day of the month | 16 | Overhead Rate Maintenace (if required) | KZS2 | KZS2 | Will it remain same? | May be Other Tcode |
| Last day of the month | 17 | Standard Cost Calculation | CK11N / CK40N | CK11N / CK40N | Will it remain same? | |
| Last day of the month | 18 | Standard Cost Estimation - Mark Up | CK24 / CK40N | CK24 / CK40N | Will it remain same? | |
| Last day of the month | 19 | Standard Cost Estimation - Release | CK24 / CK40N | CK24 / CK40N | Will it remain same? |  |
Regards
Ruksana
Hi Kumar,
Thanks for the reply.
But my query is - what other impact in the system if i change the default date as 31.12.9999.
We maintain calendars (SCAL - Factory/Holiday) till year 2017 only. Will there be an error whilst cost estimation as the calendars are not maintained till year 9999
What other impacts in the system with defaulting to 31.12..9999
Regards
Chandu
Hi Gopi
In my opinion, it wont give any error, if you extend it till 9999
The only Impact is that next year if you don't revise your Std cost, the Old Std cost is going to continue, whereas in the present system, you are forced to revise it before the start of next year
Your business team must be OK with it, before you change
Rgds
Ajay M
Hi Gopi
No impact...as I have told you old stand cost will flow for next year..
kamal
Hi Shanid
When you transfer Costs between 2 CO objects, it would post -ve in Sender and +ve in Receiver
The negative would have the effect of reducing the Costs of Project B.. Even if you post a JE from FI, the Credit posting (Revenue) in Project B will still appear as -ve
So, that is correct in my opinion
Rgds
Ajay M
Ajay Sir
GM
Since he has already released std cost which are valid up to the end of current FY so if he dosn't create a new std cost with new date control (on first day of next FY) will the old std cost be valid for next FY also. Kindly advise for my understanding.
Best Regards
Rajneesh
Hi Shanid
Here what you are doing is correct and in my opinion through settlement both requirements will may not be possible because one is revenue posting to Proj B must come through FI posting and other is cost transfer from B to A will come through transfer posting..so 2 things will not be possible through settlement process.
Kamal
Hello Gopi
Even though you have maintained calendar till 2017, there will not be any impact if you set default date to 31.12.9999 in costing date. Your old cost estimates will continue.
Regards
Aniket
Hi Rajneesh
Well, the existing Std cost will be valid only till end of the year
Only the new ones will be valid upto 9999..
Rgds
Ajay M
Hi Ranjeesh/Ajay,
Thanks for the reply.
Just to share my thoughts on Ranjesh reply: My current cost estimate (for 2016) is valid till 31.12.2016 so it has stored similarly in the tables (KEKO, etc) . Thus I would need to run the cost estimate for next year (2017)
And upon changes to Date Control (31.12.9999) next costing run will be valid till 31.12.9999.
How ever this is just the default date when we run CK11N/CK40N. We would still have the flexibility to change if required.
Thanks all for the clarification.
Regards
Gopi
Hi Gopi
Yes..you can change at the start of fiscal year but by default system will pick old one
kamal
Hi Aju
It depends on how you use the Cost Object Hierarchy..
If you are issuing materials directly to the Prod Order nodes, these will form part of Actual Costing in ML. The variances would then flow appropriately categorized..
Once the ML actual costing is done, you would ideally revaluate your Stocks and COGS, which would not flow into Cost Obj Hierarchy
Maria Luisa Munoz - You are the best in my opinion to throw more light on this
Rgds
Ajay M