Skip to main content
Solved

Create Part Revision for each Eng Revision

  • September 7, 2026
  • 3 replies
  • 44 views

s.lebourdais
Do Gooder (Customer)
Forum|alt.badge.img+1

We are on IFS cloud 25R2 and have turned the parameter “Create Part Revision for each Eng Revision” to “NO” on Part Transfer Template screen.
Why the system never wants to update the first part revision even if it is with a tentative structure and not in effect part revision 1 ?
For a purchased part (with empty structures), the fact that a second part revision is systematically created when transfering eng part rev is a problem.
Actually, with 2 differents part revisions for a purchased part, you have to make a distinct counting on each rev when inventorying.
If we have decided to manage a technical modification of a purchased part by usage of a new revision instead of a new part number, this is really because we don’t want to make a different stock management on this part..
Thank you for the explanation about the specific behaviour of 1st revision 

Best answer by dameenda

Hi, This was there for decades. there is no information about why, but transferring this creates the first revision for this Part, that is important when this part is used as a component in a structure and vise versa. Like this part cannot be a component of a parent Revision which is having an older phase in date than the component part. Another similar odd behavior we observed that if we select Single Level Transfer, still the component parts in the immediate level are Transferred.

3 replies

Forum|alt.badge.img+11
  • Hero (Employee)
  • September 8, 2026

http://clouddocs/ifsdoc/Greenhouse/Documentation/en//ProcessModels/Process_Model/TransferFromEngineering.htm

As per the information above, the intended design is to not to replace the first Revision.


s.lebourdais
Do Gooder (Customer)
Forum|alt.badge.img+1
  • Author
  • Do Gooder (Customer)
  • September 8, 2026

Hi dameenda,
I have already read this doc and understood that it is an intended behaviour.
Can you explain me why this specific behaviour has been designed regarding this 1st revision ? For which customer need it is done ?
Thank you


Forum|alt.badge.img+11
  • Hero (Employee)
  • Answer
  • September 10, 2026

Hi, This was there for decades. there is no information about why, but transferring this creates the first revision for this Part, that is important when this part is used as a component in a structure and vise versa. Like this part cannot be a component of a parent Revision which is having an older phase in date than the component part. Another similar odd behavior we observed that if we select Single Level Transfer, still the component parts in the immediate level are Transferred.