Shipping Request Picklist Tab: Add Non-Received Coil

Add Non-Received Coil Coil: This function was added in order to add a Non Received Coil to the picklist It will only work if at least 1 BL is created against the shipping request. The CSR will use this function in instances where a customer will ask for a certain coil to be assigned to a certain load number before it has arrived at or been received at Precision Strip yet. In theory, the customer will tell the PSI CSR to add a coil to a load number. The CSR will go into that specific shipping request and add the Non-Received Coil to the Picklist. The coil shows up on the picklist as non received and will not allow the shipment to ship until that coil is received in and added to the load. Once the coil is delivered at PSI, the material handler will scan the coil in and get a notification that it is on a Non-Received list to add to a load and then they must notify shipping so that the coil can be received in and added to the load. Once the coil is received in, it is removed from the Non Received Picklist and the PSI CSR will go in and set require that Inv ID to the picklist so that it is on the load.

Any questions, ask William Clayton in BG (8269) to test since incoming coil has to be scanned into receiving by material handler to prompt the alert. This function is basically used only in BG for Constellium.

1.) Shipping Picklist Reports need changed to show NR coils on the picklist

2.) When a NR coil is added to a shipping picklist, 

     - automatically mark it required

     - create an ASN with an alarm that says coil is on the picklist for whomever they say it needs to send the alarm to

3.) We must have a load in order to add a nr coil to a picklist 

3.) Check on change partner / part if there is a not received coil for the s-req.part-id, The rcpt-id must = inv-id in order for it to attempt to attach the inv-id  to the NR coil.

4.) Notify the MH via the scanner if material is scheduled to SHIP similar to the way it does for notifying that it will need to process

5.) Prevent a load from being released if the NR coil is not on the load since it is required. <- this may already work, except see if there is anything we need to do because there is only a change to the messaging.

6.) There are no UFD implications for this effort since these are storage coils.  Make sure the UFD program doesn't break.

7.) There shouldn't be implications on the autogenerate picklist but make sure that doesn't break because of NR coils

8.) Make sure nothing breaks in the auto receiving rules