Scrap

mantsu's order cockpit includes dedicated pages for scrap reason codes and reason code assignments similar to the downtime tree structure, scrap reasons are organized in a hierarchical tree with all possible reason codes reason code assignment all configured reason codes can be assigned to a material class or an individual material on the reason code assignment page you can assign the full reason tree , or a sub selection of specific reason codes this gives the flexibility during configuration as we can re use the tree structure how do you register scrap? once configured, scrap can be registered for two types of materials end product the finished good being produced bill of materials components any material in the bom (bill of material) when entering scrap, the base uom is pre filled by default the operator selects the applicable reason from the assigned reason tree to categorize the scrap, ensuring that reporting can be built on this information registrations tab each scrap entry appears in the registrations tab with the following information field description material material code + description reason code the selected scrap reason code qty + uom scrapped quantity and unit of measure timestamp date and time of the entry confirmed by the user who registered the scrap note that only when the material is linked to a scrap reason tree, the operator will be able to link scrap reason to the scrap that is produced in case of a automatic scrap detection (coming from a machine) the operator can open the registration of the scrap, and navigate through the tree like structure