Often times in our industry, we will need to requote an existing product to our customer. The Bid Estimate module does allow us to pull in the existing Inventory Part, which is great. However, I have noticed that if you do that, you cannot modify the Std Lot Size on the part. I’ve attempted to create a new Version and Revision, but I am still unable to change this. Often times we will change the Std Lot Size to give several cost options. Is there a way to accomplish this in IFS?
Best answer by Hans Andersen
Hi,
I guess, I was mostly talking to myself. We are going to have the same problem later on, so I tested it this morning.
First create a custom field for the std lot size.
Then create a RMB to update the std lot size:
code:
declare
objid_ varchar2(1000);
objversion_ varchar2(1000);
version_qty_ varchar2(100) :=&version_qty;
qty_per_assembly_ varchar2(100) :=&qty_per_assembly;
shrinkage_factor_ varchar2(100) :=&shrinkage_factor;
comp_qty_required_ varchar2(100) :=&comp_qty_required;
estimate_structure_db_ varchar2(100);
user_changed_cost_ varchar2(100) :=&user_changed_cost;
cf$_std_lot_size_ varchar2(100) :=&cf$_std_lot_size;
added_from_client_ varchar2(100) :='TRUE';
attr_ varchar2(32000);
null_ varchar2(100) := null;
begin
select objid, objversion, estimate_structure_db
into objid_, objversion_, estimate_structure_db_
from estimate_component
where estimate_id = &estimate_id and node_id= &node_id;
client_sys.Clear_Attr(attr_);
client_sys.Add_To_Attr('VERSION_QTY', version_qty_ , attr_);
client_sys.Add_To_Attr('QTY_PER_ASSEMBLY', qty_per_assembly_ , attr_);
client_sys.Add_To_Attr('SHRINKAGE_FACTOR', shrinkage_factor_ , attr_);
client_sys.Add_To_Attr('COMP_QTY_REQUIRED', comp_qty_required_ , attr_);
client_sys.Add_To_Attr('ESTIMATE_STRUCTURE_DB', estimate_structure_db_ , attr_);
client_sys.Add_To_Attr('USER_CHANGED_COST', user_changed_cost_ , attr_);
client_sys.Add_To_Attr('STD_ORDER_SIZE', cf$_std_lot_size_ , attr_);
client_sys.Add_To_Attr('ADDED_FROM_CLIENT', added_from_client_ , attr_);
estimate_component_api.modify__( null_ , objid_ , objversion_ , attr_ , 'DO');
end;
Flow:
result:
Hence, it is possible to change the std lot size though the api. Why you cannot do it through the UI most be a question for IFS dev.
Update - the easiest way I’ve found to do this is to copy the existing Inventory Part to an “Estimating” site in IFS. From there, you would adjust the Std Lot Size and then pull the part into the Estimating Module for cost building. You would then need to keep adjusting the lot size and pulling those into the estimating module. I do not know that this is the correct way, but it’s the only way I’ve found that works.
+21cjohnson,
Where is this ‘The Bid Estimate module’ part of?
If I type ‘bid’ in the navigator filter, I get no results.
I’m checking IFS 10 update 6.
Steve
+21cjohnson,
Thanks for letting me know. I found it.
When looking at a presentation of Aurena, it all seems so simple, do you happen to have that available?
Steve
You could try to update it through IFSAPP.ESTIMATE_COMPONENT_API.MODIFY__
if that is not working, you could try with:
update Estimate_Component_Cost_tab v set std_order_size = :std_order_size
where v.ESTIMATE_ID = :ESTIMATE_ID and node_id=:node_id
You might get away with it...
Sorry, I’m not understanding the suggestion. Are you saying I should try to grant those to a Permission Set?
Hi,
I guess, I was mostly talking to myself. We are going to have the same problem later on, so I tested it this morning.
First create a custom field for the std lot size.
Then create a RMB to update the std lot size:
code:
declare
objid_ varchar2(1000);
objversion_ varchar2(1000);
version_qty_ varchar2(100) :=&version_qty;
qty_per_assembly_ varchar2(100) :=&qty_per_assembly;
shrinkage_factor_ varchar2(100) :=&shrinkage_factor;
comp_qty_required_ varchar2(100) :=&comp_qty_required;
estimate_structure_db_ varchar2(100);
user_changed_cost_ varchar2(100) :=&user_changed_cost;
cf$_std_lot_size_ varchar2(100) :=&cf$_std_lot_size;
added_from_client_ varchar2(100) :='TRUE';
attr_ varchar2(32000);
null_ varchar2(100) := null;
begin
select objid, objversion, estimate_structure_db
into objid_, objversion_, estimate_structure_db_
from estimate_component
where estimate_id = &estimate_id and node_id= &node_id;
client_sys.Clear_Attr(attr_);
client_sys.Add_To_Attr('VERSION_QTY', version_qty_ , attr_);
client_sys.Add_To_Attr('QTY_PER_ASSEMBLY', qty_per_assembly_ , attr_);
client_sys.Add_To_Attr('SHRINKAGE_FACTOR', shrinkage_factor_ , attr_);
client_sys.Add_To_Attr('COMP_QTY_REQUIRED', comp_qty_required_ , attr_);
client_sys.Add_To_Attr('ESTIMATE_STRUCTURE_DB', estimate_structure_db_ , attr_);
client_sys.Add_To_Attr('USER_CHANGED_COST', user_changed_cost_ , attr_);
client_sys.Add_To_Attr('STD_ORDER_SIZE', cf$_std_lot_size_ , attr_);
client_sys.Add_To_Attr('ADDED_FROM_CLIENT', added_from_client_ , attr_);
estimate_component_api.modify__( null_ , objid_ , objversion_ , attr_ , 'DO');
end;
Flow:
result:
Hence, it is possible to change the std lot size though the api. Why you cannot do it through the UI most be a question for IFS dev.
Excellent! Thank you very much! I’ll give this a shot, as this would definitely save a lot of time vs. having to Copy Part and change each time!
I’ve discovered some functionality with the system I was not aware of. If you pull in an existing part, you have the routing and structure, but you cannot change the Std Lot Size. However, if you simply append a character to the PN, the Component Type changes to “New” and you are then permitted to adjust the lot size.
Above is the existing part. In the example below, I have modified the PN and I am now allowed to make changes to the lot size:
This makes the process of re-quoting extremely easy, and you are then able to make changes to an existing PN and compare the original costs to the modified version using the the Compare Estimates feature.
We are currently on IFS Apps 10 UPD 8. I do not know if this functionality existed on previous versions of IFS Apps 10.
Thanks for sharing.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.