Recording custom Shortage Reason code during pack

Answer

The only 2 shortage reasons supported OOTB are:

Inventory Shortage
Shortage Resolution: inventoryShortage
Shortage Resolution Name: Inventory Shortage

Pack Later
Shortage Resolution: packLater
Shortage Resolution Name: Pack Later

If it is a custom shortage reason, you will need to change the mashup class and provide your own java class implementation for the recordShortageforPack API. In this java class, you can either do a
massageInput or massageOutput handling. In the OOB implementation there is already a java class
"com.ibm.wsc.shipment.container.pack.GetUpdateShortedLineInfo" being invoked for the recordShortageforPack API. You will have to change this java class to your custom implementation
class. It is expected the handling is also done by the implementation team.

For custom reason code system will only log the shortage reason note but what operation
needs to be performed must be decided by the implementation team. With reference to the steps shared above, you will have to identify the mashup and replace the implementation class to handle the custom logic as per business requirement.