Most fields have deliberately been greyed out, unfortunately due to dependencies we are not able to completely grey out some fields. Therefore, the only option the user needs to modify is the Upload Action column. When deleting a ‘Material Requirement’ the user would need to select this field to ‘Delete’.
It is recommended that the user downloads the existing material requirement job first in order to see the existing materials that can be deleted.
Fields that require deletion can have the Upload Action field flagged with ‘Delete’ and fields that are not required to be deleted can have the ‘Upload Action’ column left blank.
Rows where the Upload Action column is left blank will be ignored by the template and no work will be performed on these.
Note: In order to delete a Material Requirement, the status of the Discrete Job must be set as ‘On Hold’. If the status is not on hold when attempting to delete, the interface will replace any substitute materials with the original item i.e. effectively not deleting the material.
Once this is done, we can process the record for upload. After this the rest of the process (including submitting a concurrent request, refresh status etc.) is similar to as described in the WIP Material Requirement section.
Regarding the data processing in ‘WIP Material Requirements - Delete Material template’, refer to Submit Concurrent Program and Refresh Concurrent Status points in ‘WIP Material Requirements’ section.
