Sample: Implementing custom shortage reasons
A store implementer must be able to set up custom shortage reasons to suit business requirements, which allows store associates to choose the appropriate shortage reason while recording shortage for products during batch pick.
About this task
A store implementer can add custom shortage reasons in Sterling Business Center. The default, and only provided shortage reason is "Inventory Shortage".
a store associate selects a custom shortage reason in the RECORD
SHORTAGE window, the
is run and the
exit is invoked.
To implement your own logic to handle custom shortage reasons, refer to the sample code
available in the
By default, the
exit provides the logic to handle two sample shortage reasons: "Damaged"
and "Pick Later". The
getCommonCodeList API is called
retrieve the shortage reasons. You must configure the
"Damaged" and "Pick Later" shortage reasons respectively. When the
store associate applies the "Damaged" shortage reason, the behaviour
of the application is same as that for "Inventory Shortage". However,
when the "Pick Later" shortage reason is applied, all the batch related
attributes in the
YFS_SHIPMENT_LINE table, mainly
blanked out, which means the shipment line is removed from the batch.
To implement the
exit, follow the procedure:
- Select Applications Platform in Applications Manager.
- Select System Administration.
- Select User Exit Management.
- Select the
- Click the add icon to input the user exit implementation.
- In the Implement As a Java Class field that corresponds to the user exit, enter the fully qualified class name.
- Click Save.
When a store associate selects a custom shortage reason while picking a product in a batch in
Sterling Store Engagement, the
recordShortageForBatchPick API validates the
shortage reason against the
YCD_PICK_SHORT_RESOL code type and then calls the user
For more information about user exits, see IBM® Sterling Order Management System: Javadoc.