Skip to main content

We face a situation when we change Part Type from Manufactured to Purchased in Part Cost. Cost template is changed and cost calculated is correct. However we noticed that Structure multilevel still presents components from Manufactured structure type despite part type is changed to purchased where no components exists. Is this correct behavior? Reason why we discovered this is that an information message was presented “Zero Cost Parts Exists”. This message is not applicable for the purchased part, only for the manufactured structure that is no longer in use. Very confusing for user. Only way to get around this, as we have identified, is to create a new revision for part. Is there another better way to handle this scenario?

 

Hi 

Now your parent part (the topmost part to which the cost calculation is performed) is Purchased.

So have you defined estimated material cost / Supplier Price in the Supplier for Purchased part for this parent.

In other words what is the purchased cost defined for this parent part?

I think you need to enter Purchased Costs based on the Cost buckets of the selected template for this parent part. E.g if the Cost Bucket 110 is present int the template P-141, then enter some Estimated Material Cost for the part and perform the Cost Calculation again.

If Planned purchase price Bucket is present, then enter a Price in the Supplier for Purchased Part record for the Primary Supplier.


Hi,

I defined price on supplier for purchase part. I use a version of std template P-140 including general Del OH. Calculated cost is ok, this is not the issue or question. The issue/question is why structure multi level tab still appears from manufacturing structure when part type is now defined as purchased and how I can avoid that.


If you have the Price defined, then it's highly unlikely to get the 0-cost message if you have not got it when the part is Manufactured.

The cost calculation filters the Structure Type to be considered when running the Part Cost Calculation.

The Structure Multi level lists down the components of the Parent irrespective of the Inventory Part Type. That how it is designed to work.

 

 


Ok, so then there is no way to get rid of structure multi level parts and any related messages? Despite they are not relevant for part type defined on inventory part?


If you delete the Cost Set for the Parent Purchase part using the delete option and then perform one level part cost calculation for the Purchased Part by opening the All level part Cost Calculation Dialog from the Navigator and entering the information or load from a different Cost Set for the same part and replace the “Cost Set” from the Deleted Cost Set (Cost Set 5 in your example above) by entering in the said dialog.

Then the calculation will not look into the components, so you will not get the zero-cost error and also structure in the Structure Multi level tab.


Hi my previous reply needed to be corrected as below (it should be One Level Part Cost Calculation” dialog.

If you delete the Cost Set for the Parent Purchase part using the delete option and then perform one level part cost calculation for the Purchased Part by opening the One level part Cost Calculation Dialog from the Navigator and entering the information or load “One Level Part Cost Calculation” from a different Cost Set for the same part and replace the “Cost Set” from the Deleted Cost Set (Cost Set 5 in your example above) by entering in the said dialog.

Then the calculation will not look into the components, so you will not get the zero-cost error and also structure in the Structure Multi level tab


Hi,

Right now the system works as designed. When the cost calculation find a top part, it explodes that part, looking at both Purchase and Manufacturing structure types! Why? Well, perhaps if you switch from manufactured to purchased, then there might be some parts sitting in the manufacturing structure that only exists below this top part. System needs to calculate them again, since they a few minutes earlier was removed (by the ALL parts cost calculation). At this point in time, system does not know if these components are sitting in other structures. The top parts are sequentially calculated, one by one. Perhaps if we at RnD could spend a month in redoing this we might come up with a better solution.

Also, system does the explosion, prior it is looking at the manufacturing/acquire split. You can actually set up the Cost Template so it fetches both from the manufacturing leg and the purchase part, using the manufacturing/acquire split.

I really do understand that this is a bit confusing for you. One day we might be able to improve this.

Cheers,

Mats


Reply