User guide

Creating and Updating BOMs
1-8: Getting Started (An Overview)
d.
Run
bn_bomprocess
in /hw/tools/scripts or /swi/tools/scripts/.
4.
If you’re using
mechbom
(see
Creating an Initial Mechanical BOM
on
page 5-8), it creates a config file for you, but first you have to:
a.
Create a mechanical include file called
assembly
.lst.
b.
Provide supporting mechanical data files.
c.
Run /bay
dir
/dra/utils/mechbom.
Note:
If you use either
mechbom
or
xcelbom
, they produce output files just like
bn_bomprocess
does, because they run
bn_bomprocess
internally.
5.
If you’re using /bay
dir
/dra/utils/xcelbom, see
Using xcelbom to Create an
Initial BOM
on page 5-10.
6.
Consult
Pre-Upload Checklist
on page 6-3 for review steps to take after
you’ve created a BOM and before you continue with the next step, which
is requesting a BOM upload, a.k.a generating a PCN. (See
Uploading a
BOM
on page 1-9, below, and refer to Chapter 6 in general.)
Updating a BOM
Update BOMs using
/hw/tools/scripts/bn_bomprocess
(or
/swi/tools/scripts/
bn_bomprocess
), or
/bay
dir
/dra/utils/mechbom
or
xcelbom
, as appropriate.
To update a BOM:
1.
For a mechanical BOM (see
Updating a Mechanical BOM
on page 5-9):
a.
Extract a .saplis file from SAP (see
Downloading a .saplis File from
SAP
on page 5-8).
b.
Run /bay
dir
/dra/utils/build_lst to create
assembly
.lst from that file.
c.
Edit the
assembly
.lst file as needed.
d.
Rerun /bay
dir
/dra/utils/mechbom.
e.
Review the
assembly
_proto.diff file and optionally run
bom_upload
.
2.
For a schematic-based BOM (see
Creating a BOM with bn_bomprocess
on
page 5-6):
a.
Edit the config file,
Project
.lst, and other input files as needed.
b.
Rerun
bn_bomprocess
to output files such as
assembly
_proto.diff.