Trying to add an assembly to an existing job, getting an error “Invalid Child Assembly”. I get the error both when using the DMT to upload and using the UI to enter directly.
This is for a client upgrading from E9 (9.05.072A) to 10.2.200.6, and the job exists with this assembly in E9. I’ve looked at both the parent and this assembly part records, MOMs, plants, and there isn’t anything different in E9 than exists in E10 that I can find. The “Detail” on the error is voluminous but doesn’t say much I can understand.
Any thoughts on where else to look before I call it in?
Do you have some revision effective dates that are bad? I don’t know anything about E-10, but I know that effective dates can cause problems, and if upgrading, and putting in jobs with older dates, I could see that causing problems.
If you re-create that same job in E9 can you import the BOM? If the job already existed in E9 it (the dates) might have been fine when it was first created, but not now. I’ve seen errors (although I’m not certain it’s the same one) when rebuilding/appending jobs that have old due dates.
That’s what I’m trying to do via DMT… they have 7,000-odd jobs I’m importing… with up to 14 levels of subassembly. I’m up to level 4 and these ones just fell out.
So I tried deleting the assemblies and ops already on the job, then running Get Details… and now get an error “BOM Resequence could not be completed due to corrupt information in peer pointers. Please review if conversion programs to fix this needs to be run”
Okay… so the fix for this APPEARS to be to check out the Job level part/rev (ultimate parent part) to Engineering workbench, then in the MOM go to Actions > Materials > Resequence. If this gets to be too much of a problem (so far only 3 parts), I’ll call it in and see if there is a more global way of taking care of it.