You use this program to generate a hierarchical (vertical) view of structure and routing data based on the structure of the components.
The report is useful if you design a product, because it is generated from an engineering perspective to provide a complete view of the product.
| Field | Description |
|---|---|
| Stock code selection | |
| Stock code | Indicate the stock item for which to generate the
report. This must be a made-in item, a phantom part, a notional part, a co-product or a subcontract item. |
| Rev/Rel | Indicate the revision and release of the parent
Stock code for which to generate the
profile. This is only relevant when the Stock code is ECC controlled (Stock Codes). |
| Routing selection | |
| Routing |
Indicate the route to use for the Stock code. This is the routing configured in the Structures and Routings program and is only relevant when the option: Alternate routingsis enabled (Bill of Materials Setup). |
| Quantity to make | Indicate the quantity of the parent Stock code you want to make. |
| Print manufacturing u/m quantities | Select this to print the quantities on the report in the manufacturing unit of measure. This applies when using Manufacturing unit of measure (Work in Progress Setup). Quantities are printed in the manufacturing unit of measure when a Manufacturing unit of measure is defined against the stock code (Stock Codes) and the Manufacturing unit of measure is used in the Bills of Materials.Quantities are printed in the stocking unit of measure when this option is not enabled. |
These options enable you to apply a theme to the report and to define multiple output destinations for the report once it has been compiled (SRS Output Options).
The report indicates how components are used in sub-assemblies; how sub-assemblies are used in assemblies; and how assemblies are used in the parent part.
Through all the levels of the structure, the operations in the routing are clearly identified. If a routing has not been defined, a dummy operation with a No route found description ensures clarity in the report.
Operations for soft phantom components are ignored and the message Routing ignored - soft phantom is output.