cancel
Showing results for 
Search instead for 
Did you mean: 
Security Alert Log4j Security Vulnerability. Click here to know more.
cancel
Showing results for 
Search instead for 
Did you mean: 

Modify Import from Spreadsheet Validation to check leveraged subassemblies for consistency

Modify Import from Spreadsheet Validation to check leveraged subassemblies for consistency

The BoMs are loaded through OOTB- Out of the Box Loader file through Actions > Import from Spreadsheet > Choose the right file

Here we go through the process of Initial step of validations and then Import upon successful validations.

When there are some inconsistencies or discrepancies in the OOTB loader file, we expect Windchill to spot those errors in “Validation” step.

One of such discrepancies is the “ Inconsistent of the parameters of the subassembly” across 2 or more places in the BoM.

Here in the cited example, the file WC_10.2_OOTB_File_Ver_1.0- BoM Load for Leveraged Assemblies with the same subassembly #20000 used across two places/levels.

The inconsistencies here are

1. Different Child parts are being used namely 1011 in 1st subassembly and 1010 in the 2nd subassembly.

2. Different quantities for the child parts are being used namely qty 1 for all in 1st subassembly and qty 6 for all in 2nd subassembly.

This passes the validation successfully and while loading , 10.2 WC loads the parameters of the 1st subassembly and ignores the 2nd.

Screen shots of the BoM Tab of OOTB file loaded, BoM structure view after loading in 10.2 WC shown here depict the issue.

Also shown is the comparison between earlier existing Structure of subassembly 20000 and the new loaded one.

Expectation:

Practically while loading complex BoM structures of few hundred lines, there are possibilities of such errors and inconsistencies.

10.2 PTC WC should be able to detect this at the validation stage as “ Error”.

2 Comments
JeffZemsky
17-Peridot

Many errors can be detected at the validation stage.  However there are certain types of errors we can not find at this stage.  For example - if there is a failure at the higher level and then the lower level.

In your example the system actually assumes you are want to make those changes and does not know you do not.  For your use case I would recommend not to have the lower level assembly defined beyond its first level in any sheet it is used.  It should only be defined in the one sheet then. 

olivierlp
Community Manager
Status changed to: Archived

Hello,

We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.

You can always post a new idea with all the details required in the form.

Thank you for your participation.