What are steps involved to get the entire BOO records from Pilot to Live?
Do you have to first DMT the info from ECOOper table and then the info from ECOOpDtl table? Or do you create a BAQ that links them both first?
Is there a way to mark them all unapproved - so after they are created they can be reviewed and approved before GO LIVE?
The new boo template I used to go from another system, but should get you started. You might need to start from PartOpr and PartOpDtl unless all of your BOOs are checked out.
Make a baq from where your data is (Part or ECO ). Make an ECOGroup for the import, since each line will do a check out/check in. I had 80,000 boo operations, so I split them into imports of 10,000 each and ran 8 sessions on two machines.
The part Revision Template can approve or unapprove.
Run the process in a dev system and do time studies.
Greg
New BOO Template.xlsx (10.5 KB)
New Part Revision Template.xlsx (12.5 KB)
Not trying to hijack a thread but,
Greg,
How long did it take to run the imports for your BOO’s? I’m looking at about 150k lines on our BOO’s and over 600k on the material side.
What were the server specs you used.
Thanks,
I have in my notes 5 hours, but I didn’t record the rpm. I used 2 i7 pcs with 24GB ram and an ssd drive and as many sessions as I needed of DMT as long as the rpm didn’t drop. The most I did was 8 for job operations and that was hard to follow on the screen.
I ended up doing only the changed values. I had a spreadsheet with an odbc links got all of the BOO or Bom records from the new system in one sheet and all of the old system in another sheet. Concatenated all of the relevant fields partnum, revision, etc together and did a vlookup against the new system.
Then filtered for changes.
Took that spreadsheet and had a macro to split into 5k or 10K sections and ran all of them at the same time.
How does it move from PartOpr to ECOOper? and PartOpDtl to ECOOpDtl?
Part is where they are normally, ECO is when they are checked out to the Engineering Workbench.
The check out process copies them to ECO
When you approve and check-in a part from engineering workbench (after making changes) - does it update the PartOper tables and clear the ECO tables?
I had a bad resource group in about 15 parts - we checked them all out and removed the resource from each one and approved and checked them back in but for some reason we still can’t delete the resource group - it says it’s still ‘Referenced by at least one Engineering Change Order’
It must leave the versions of the Boo/BOM in ECO. I did a count on an assembly and I have 101 rows in PartOpr and 505 in ECOOpr.
To get rid of the Bad Resource Group you would need to make an Updatable BAQ and change those ECOOpr records.
And be sure it had never gotten onto a job.
That’s what I was afraid of - no way to just update the PartOper tables without making ECO table entries…?
If you update the BAD RESOURCE GROUP with another - wouldn’t that be doing the same thing - populating more ECO records with another bad resource group? We just want to remove that group as it was setup and added to a few methods by mistake before DB was copied out for testing.
Or are you think to replace it with a ‘good resource group’ and then remove the detail from from the Oper records?
yes, that is what the UBAQ would do. Update PartOpr thru the BAQ not thru Eng. WB.
There is a method flag in the part rev table - ever work with that to see if you turn it off - by chance it will lose all preceeding ECO records?
I’ll give that a try - I’ve done it thru DMT but that creates ECO table records.
Update BAQ PartOpr.baq (14.6 KB)
I took a Part update and made a PartOPDtl update.
I can and already have updated the PartOpr records - the problem is that the ‘bad resource group’ is referenced in the ECOOpDtl records - so can not be deleted. I can’t find a way to remove it from the ECOOpDtl records…I think we’re stuck with the ‘resource group’ - probably only thing we can do is mark inactive…
so much for a ‘clean’ DB to start with
Here it that described.
270
Method
xhttp://svr-eapp2/datadictionary/Mfgsys/00-cross-m.html#Method
?
logical
yes/no
no
D: An internal flag which indicates that this part revision contains Method of Manufacture details (PartMtl/PartOpr records). We use this to avoid processing raw material part records during processes such as BOM Cost roll up, Indented BOM lists, etc…
Update BAQ ECOOpDtl.baq (14.1 KB)
Sorry, I was on autopilot. This does ECOOpDtl
Thank you so much for all the info. This is a bit over my head and doesn’t appear to be working - looks like some things don’t transfer from 9.05 to 10.1…I’m getting errors regarding the BPM directives. I don’t know how to use update BAQs yet - so I’m at a loss
Sorry, I am still in 9 and won’t be going to 10 till later this year, so I have not started to educate myself on any E10 processes yet.
Hey Greg,
Any updates on uBAQ for partopr table in E10?
No, I have not had time to make any progress on getting to E10.