Skip to main content

Hi,

we came across no part cost for a component which is manufactured but has a purchased cost template.  So we tried to figure out how this constellation has happend:

  1. If you create a new manuf part cost template in cost set 1 is set automatically to M-110

correct

  1. if you change the part type to purchased, the the cost template in cost set 1 is set automatcally to P-110

correct

But we have 2 jobs running at night:

 

Calculate cost set 3 for all parts and copy cost set 3 to cost set 1

 

Unfortunately the part type change does not change the cost template of cost set 3.

This means we have the wrong cost teplates in all the parts where part type has been changed.

 

Any idea how to solve this dilemma? Do I need to create an event at part type change or at cost template change in cost tab 1 in order to have the same cost template in 3 or are there any settings or easier work arounds?

Cost Set 2 is the one typically associate with cost template P-110.

Cost Set 3 is more likely set to P-130.

The job is only going to pick up where cost has been entered against the estimated cost of Cost Set 3.

Are you using Cost Set 2 for anything?

Sorry you are right.

Using M-110 for manuf parts in Cost set 3 and P-120 for purch parts in cost set 3

When changing the part type, this is not changed in cost set 3

 

@AlexSkupien ,

Could you please check the below 

  1. Default purchase cost template for cost set 3 for your site 
  1. Also the cost parameter which changes the template when part type is changed is set as Yes. if this is set as No then template will be changed only for cost set 1 & 2

Regards,

Mithun K V

@AlexSkupien ,

Could you please check the below 

  1. Default purchase cost template for cost set 3 for your site 
  1. Also the cost parameter which changes the template when part type is changed is set as Yes. if this is set as No then template will be changed only for cost set 1 & 2

Regards,

Mithun K V

 

Hi Mithun,

  1. is as in your screenshot
  2.  seems to be the perfekt solution for our problem. Unfortunately the code_parameter “change_cost_template” is not there in our environment(APPS10UPD9). Do you know when it has been introduced?

 

BR,
Alex

 

Hi Mithun,

found it. In “cost_parameter_api.create_default_parameters(contract_ => :contract_,
                                               lang_code_ => :lang_code_)”

This parameter is existent. So I executed it in our test environement and the parameter appeared.

I guess some upgrade script APPS8->APPS10 was missing to execute cost_parameter_api.create_default_parameters.

Will test the parameter and let you know.

BR,
Alex

It works exactly as expected. Thank you!

Reply


Terms & ConditionsCookie settings