User guide

bn_bomprocess Messages
PCN Process User Guide (301945-A)
Error Messages: D-3
<refdes %s used on %s and %s>.
Refdes issues listed above have %s issues. Because of this,
Processing has stopped.
Essentially, you have multiply-defined reference designators, or some other
mismatch. See the files that
bn_bomprocess
lists for log file, schematic
source, include, and depop files.
CFG file required file of type <bom_type>. File <bom_filename> is
of type <actual_bom_type>.
You said the new BOM had a specific type, e.g.,
VL_SCHEM_EXTRACT
, but the
old BOM and new BOM both have to be of the same type, and they aren’t.
Change your
NEW_BOM_TYPE
or
OLD_BOM
parameter(s), or otherwise make
sure that your project is using the right BOM file format.
Component Kit Part number <assy_number> is not in target MRP system
The Material Groups 920, 960, and 980, which are parent-level assemblies,
used to be called “component kits” at Wellfleet and Xylogics. The parent
assembly part number specified by the name of the old BOM is not in the SAP
system. Edit the your config file’s
OLD_BOM
statement to supply the correct
part number.
Config File exists but not found on command line
You specified a configuration file, but it doesn’t exist. Check the spelling and
your current directory location.
Could not create <output file> file
The output file mentioned could not be created, perhaps because the directory
you have specified does not have the correct permissions, or the disk is full, or
the mount point is not available.
Directory <part_number> specified, but does not exist
A part number is specified in one of your input files to
bn_bomprocess
, but
can’t be found on the data servers.
Duplicate Item number: <item_no>
When building the .
sap
file,
bn_bomprocess
looks to see if a duplicate item
number exists.
file <filename> does not exist - EXITING
file <filename> is NOT readable - EXITING
file <filename> is NOT writable - EXITING
The input files have been checked to see if they exist, can be read, or can be
written, as needed.