SM.01 – Declaration and Sale of Scrap Flowchart | FMS Application (CLAY) Training

This training video explains the SM.01 – Declaration and Sale of Scrap process in the FMS Application (CLAY), covering the complete workflow from monthly scrap quantity updation to finalizing the expected lifting date. Process Initiation The process is initiated on the 1st of every month for the previous month, provided the Project Master Status = Ongoing. The system generates the Project, Month [MMMYY], Source [System], and UID automatically. An Adhoc initiation is also available when required, with Source [Adhoc] and an auto-generated UID. Task 1 – Monthly Updation of Scrap Quantity Doer: Asst_Storekeeper_Inventory TAT: Initiation + 1 Day The Asst_Storekeeper_Inventory updates the scrap quantity for the applicable material categories: TMT [MT] Structural Steel [MT] Cement [Bags] The process then checks whether there is any scrap to declare. Task 2 – Verification and Finalizing Scrap Quantity Doer: Store Management TAT: Initiation + 1 Day The declared scrap quantity is inspected and verified. After inspection, the Final Inspected Quantity is entered and finalized. If there is no scrap to declare, the process follows the applicable “No scrap to declare” flow. Task 3 – Confirmation of Scrap Readiness After the scrap quantity is finalized, the process checks whether the scrap is ready to lift. If the quantity is not sufficient for lifting, the process follows the Not Enough Qty to Lift flow. If the scrap is ready, the process proceeds to the lifting-date coordination. Task 4 – Enter Expected Date of Scrap Lifting Doer: Asst_Storekeeper_Inventory TAT: Task 3 Actual + 5 Days The expected date of scrap lifting is entered after coordination with the Transporter / Client / AT_HO. Input: Expected Date of Lifting of Scrap Reference SM Master and Template Link: https://bit.ly/3QvxgPb Training Disclaimer: This video is created for internal training and demonstration purposes to explain the workflow in the FMS Application (CLAY). Actual screens, data, responsibilities, and process execution may vary based on system configuration and applicable process requirements.