Commitment on the WBS from releaed shop floor orders

[Former Member]

Hi all,

We have the following problem linked with PS and PP:

Context:

u2022 We plan specific components on cost activity level in a project with project stock. The plan value is entered on the cost activity level as a global amount.

u2022 The flag for Costing relevancy flag calculation is not activated thus not to have the planned costs twice on WBS level.

u2022 The shop floor orders have the assignment to WBS element for the above mentioned components

u2022 The shop floor orders are released in order to begin the specific production for the project.

Problem:

u2022 There is no commitment on the WBS element as far as the shop floor order are released until there are delivered to the project stock

u2022 Instead of the purchase for which this commitmentu2019s function is well achieved.

Question:

u2022 How can we see (activated) the released shop floor orders as commitment on the project info system value type 21-25.

Do anyone have an idea/input how to solve this issue?

Thanks in advance for your prompt reply.

Best regards

Edited by: Pierre-Alain Berger on Sep 15, 2009 9:59 AM

[Former Member]

Hi Srikrishna,

Thanks for your input again.

The objective is to be able to analyze the delta between the orders which are released and the total planned, in order to be able to the follow the project/production wip.

I spoke about commitment but if a way could be to have the amount via a statistical planning we could also work with.

Thanks in advance for your inputs

Best regards

Pierre-Alain

[Former Member]

Hi Pierre-Alain

Till the production orders are released, the planned cost of network should be the base of analysis.

When the BOM header is assigned to the network actiivity the planned value is updated for the material assigned which would either be the standard price or the moving average price of the component.

After the production orders are created and released the order planned cost comes from the BOM and the routings.

Regards

Srikrishna

[Former Member]

Hi Srikrishna,

Thanks for your answer.

In our case the planned costs of the orders are not overwriting the plan costs in the network, there are added to the costs of other planned activities in the network which which indeed is another issue. But this will be treated outside this problem.

But what we want to see is that the planned values of the orders impact the commitment values and not the planned values.

Do you have an idea how to achieve this?

Thanks in advance for your inputs

Best regards

Pierre-Alain

[Former Member]

Hi

Why would you want planned values to update the commitment. Even network plan costs do not update commitment, unless a PO is made.

The POs created from the production order cannot update the commitment item in WBS element.

Regards

Srikrishna

[Former Member]

Hi

When the shop floor production orders are released, the plan cost of the production order becomes the assigned value in the WBS element. The plan cost in the network is over-written by the assigned value in the production order.

I would suggest you store your "global" plan cost in WBS element in another CO version.

The plan and actual costs from network and production order can always be viewed in CO version 0.

Hope the above helps.

Regards

Srikrishna