How does everyone transfer parts correctly from eng. to product structure

What exactly is meant by “blank product structures”? Do you have an example here, perhaps with a screenshot, where we can see the difference between the Eng Part Structure and the Product Structure?

And if a part that is included in over 100 assemblies is replaced, there is no alternative but to transfer all the affected assemblies again. Or where exactly is the “problem” here?

In this case, Blank product structure means there is no list of parts under the Components tab. Its Blank. The engineering structure could have 1+ parts, it doesnt matter. but Components will be blank. 

I believe that happens when the “Engineering Revision Transfer Status” says “changed”. But unless we transfer all the where use boms, they always says changed. 

The problem has been to manual retransfer all of the affected subassemblies. This seems like an immense waste of time. 

Which version of IFS (Cloud) are you using? We once came across an issue here where the changes hadn't been carried over to the sub components:

Description

• Here is the situation regarding the reported situation:
  Master data in Eng Part Navigator with assembly part 2000159 Eng Rev 01 and component part 2000160 Eng Rev 01:
  
  When this is transferred for the first time both the assembly part (head part) and the component part (from tab "Consists Of") are transferred and created Rev No 1 for each:
  
  If I now create a new Eng Rev 02 from both Eng Parts and put these two back together in an assembly and transfer the assembly part (head part) with Eng Rev 02 again, only the new revision 02 of the assembly parts will be created:
  
  This must be a standard bug in the Single Level Transfer procedure, which states that the selected Eng Part is always transferred, as are the Eng Part(s) contained in the "Consists Of" tab in this Eng Part.

Jira Issue Key

• MFZ-27309

IFS Fixed Version

• 26.1E.0 - 26R1 EA
• 25.2.2 - 25R2 SU2
• 25.1.8 - 25R1 SU8

Do you find yourself behaving in the same way?

Hmmm. Not sure the version of cloud, but this was the case in IFS 10 as well

Example 1:

New assembly, subassembly and new part.

We single level transfer as such, part → subassembly → Top assembly. 

TOP ASSEMBLY - REV 1

•  SUBASSEMBLY - REV 1
  • PART  - REV 1

Example 2:

PART goes to Rev 2 and is Single level transferred. 

SUBASSEMBLY now shows “CHANGED”

What seems to happen is if i created TOP ASSEMBLY Z - REV 1 and use SUBASSEMBLY - REV 1 which is at “changed”, and I single level transfer TOP ASSEMBLY Z - Rev 1, Subassembly goes in as BLANK and i dont see it. 

This could be buried in assemblies. And this is a simplified case. 

Not sure if that makes sense?

Did you transfer the updated SUBASSEMBLY – Rev 1 again with the new Part Rev 2 beforehand? This is essential, as otherwise the site won’t recognise the new Part Rev 2 yet. I think that might be the gap.

I did not. Thats the problem i see. 

If there are 150 subassemblies that use that part they will all show changed. Do i have to individually go in and retransfer and make buildable ALL subassemblies manually? Thats the issue. Its a huge time sink. 

So that leads me to think we are doing something wrong. That cannot be the correct way to do that.

If the new part with Rev 2 is contained within 150 subassemblies, then all 150 of these subassemblies will need to be transferred again (which is why the system has marked them as ‘changed’ once more). All 150 subassemblies can, of course, be selected and transferred together in a single step. So it’s only a one-off task, rather than having to do it 150 times individually.

thanks and yes, transferring isn’t the difficult part or time consuming. its then on the Product Structure side, all of those need to now become buildable as well. Each one has to be buildable 1 at a time. Unless there is a quicker way to make that happen as well. 

Oh, I see. The issue involving significant effort isn’t on the transfer side, but on the manufacturing side, specifically regarding product structures status.

If the component is ‘only’ a “replacement” with a new revision (e.g. from Rev 1 to Rev 2) and not a new part (e.g. from 5001 Rev 1 to 5002 Rev 1), it is sufficient to simply transfer the component part with the new revision. To do this, you can manually reset all affected subassemblies in the transfer mask using a “bulk change” from “CHANGED” to “NOT CHANGED”. This is because, in the product structure, the component is not managed by revision; instead, the system checks the validity period to determine which revision of the component should be used.

So changing “Changed” To “NOT Changed” Is valid?

I thought that caused issues as well. I can’t remember now.