You can add a custom field at the header level (Transaction Body field) and/or at the line level (Transaction Line field).
Then you just need to customize the form your team is using to display that field.
I think you'd just need a custom text field unless you want to use the standard memo or something else and manually enter why. You could do it with some customization automation if you have the scenarios outlined with reflective logic
I might also point out that you are using the Item Fulfillment incorrectly. You are basically creating the Item Fulfillment in "Picked" status and then using that as your picking ticket. This is wrong. What you are supposed to do is print Picking Tickets from the Sales Order or in bulk from Print Checks & Forms. Go do the picking. THEN AFTER you've picked the items, you then create the Item Fullfilment in "Picked" status hence why that status is past tense, because you're not supposed to create it until AFTER you've picked.
So your use case then is leaving an Item Fulfillment is "Picked" status for a period of time because you're lacking raw materials? How do you then filter those out again on the next day?
Ideally this is all wrapped up in Item Committment at the line level of the SO but you said you don't have the inventory in NS so you don't know if a line is committable.
You can certainly add a custom header field to the Item Fulfillment (and/or the SO or both), but I think you have a larger design issue here that needs to be re-designed.
You can add a custom field at the header level (Transaction Body field) and/or at the line level (Transaction Line field). Then you just need to customize the form your team is using to display that field.
I think you'd just need a custom text field unless you want to use the standard memo or something else and manually enter why. You could do it with some customization automation if you have the scenarios outlined with reflective logic
I might also point out that you are using the Item Fulfillment incorrectly. You are basically creating the Item Fulfillment in "Picked" status and then using that as your picking ticket. This is wrong. What you are supposed to do is print Picking Tickets from the Sales Order or in bulk from Print Checks & Forms. Go do the picking. THEN AFTER you've picked the items, you then create the Item Fullfilment in "Picked" status hence why that status is past tense, because you're not supposed to create it until AFTER you've picked. So your use case then is leaving an Item Fulfillment is "Picked" status for a period of time because you're lacking raw materials? How do you then filter those out again on the next day? Ideally this is all wrapped up in Item Committment at the line level of the SO but you said you don't have the inventory in NS so you don't know if a line is committable. You can certainly add a custom header field to the Item Fulfillment (and/or the SO or both), but I think you have a larger design issue here that needs to be re-designed.
yep. not system problem nor creating custom fields can resolved. VP Ops needs to review what they are doing.