Item That Does Not Exist in Agile Gets Created When Performing Transfer BOM Find Numbers Through MCAD Connector
(Doc ID 2410038.1)
Last updated on JANUARY 24, 2024
Applies to:
Oracle Agile PLM MCAD Connector - Version 3.5.0 and laterInformation in this document applies to any platform.
Symptoms
Actual Behavior
When the assembly includes a structure part which does not exist in Agile, executing "Transfer BOM find numbers" on its Drawings will create a new item in Agile
Expected Behavior
Even the assembly includes a structure part which does not exist in Agile, executing "Transfer BOM find numbers" on its Drawings should not create a new item in Agile
Fact
Setting CaxConfig.xml NonExistingPartsFromCAD to "remove" does not make any changes in the result
Steps to Reproduce
- Create a part in Solidworks. Do not create the item in Agile. Set the item number to the property.
- In Solidworks, create one assembly which will have one structure part. In Agile, create the assembly item
- Checkin to Agile
- Check if item is created in Agile. Item is not created. This is expected.
- In Solidworks, create the drawing for assembly, and create BOM
- Checkin drawing
- Check if item is created in Agile. Item is not created. This is expected.
- From the drawings file, execute 'Transfer BOM find numbers'. Gets error (This is because transfer of the find number of the item which is not in the BOM was attempted, and is expected error)
- Check if item is created in Agile. Item is created. This is not expected.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |