cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Preference for merging usages automatically when populating in MAPSB

Preference for merging usages automatically when populating in MAPSB

If populating a structure with the same part in multiple actions the part is displayed in multiple rows also in usage mode.

Suggestion is to have a preference to allow this or not - choices should be Yes, No, Automatic merge.

3 Comments

This is a must have and would be a major time saver.  Right now we have to go in and modify one row to have the total and remove the other rows.  This leaves room for user error.  When you have 175 lines to look over and make sure if there are duplicates or not, it can be easy to miss something.

 

It also messes up the XML file created when a structure is sent to a distribution target.  The XML behavior was sort of fixed in 11.0 where it would roll up the totals in the XML file, but in 11.2 it seems to not work and really messes with the XML and what gets added.

Guest
Hi Brian



Thanks for your reply - however the way of working you describe robs you of a lot of occurrence information as I see it - e.g. I think your visualization of the mbom part structure is messed up.



I propose that you select the abundant rows and Cut

[cid:image002.jpg@01D5CB74.D387E0C0]

Then on the "primary" row (the one which was not selected to be cut) and then "Merge Usage After Cut"



[cid:image006.jpg@01D5CB74.D387E0C0]



That leaves you one row in usage mode with the right quantity and in occurrence mode you have your 175 individual rows each pointing to a specific occurrence on ebom side.



I hope that gives you a bit of help also with the xml



BR Preben


Hello Preben,

 

Thank you so much for that information.  That works so good for what we do.

 

It has been a long time since I have used this module and just support a couple of people that do.  They do not know about this so I will let them know.

 

It was just in 

 

Sincerely,

Brian