Are you mixing segmented inventory in inventory locations?

Body

If you are, then it is likely that you may see issues during RF operations

Some of the common issues that you may encounter are -
'YFS10415: Key Fields cannot be modified' from registerTaskInProgress API during Picking
'YDM00239 : Could not identify matching Shipment line' from addToContainer API during Packing

These issues are seen because Sterling does not have the feature to capture segment information during RF operations.

While this could be taken into consideration for product enhancement, customization could also be a feasible solution.  There are some aspects to be considered, depending on the business use case

1) Do you want to capture segment information during the RF operation?
2) Is segment information available in the shipment
3) Is it safe to assume that the user is picking the expected segment

The issue may not occur if you are not expecting a specific segment to be picked so there would be no requirement to customize this. However, if you have a specific segment stamped in your shipment line, then system would expect you to pick the exact segment.

In case of Picking, since Sterling does not ask for segment information on the screen, once you have entered the other item details,the  system processes the data without segment information and gets inventory details for the location. If the location has only a single segment, then it picks that and no error is seen. However, if you have multiple segments or a mix of segmented and unsegmented inventory for the same itemid in one location, system passes the last item segment in the list to the registerTaskInProgress API. If this entry does not match with the requested segment, you see the error 'Key Fields cannot be modified'

In this case, you can customize the input to registerTaskInProgress API and pass the segment information, to avoid this error

Similar behaviour is seen during Packing. Input to getNodeInventory API does not have segment information causing it to pass the last item segment to the addToContainer API. If this segment info does not match with information in the shipment you see 'Could not identify matching Shipment line' error.

Here you can customize the input to getNodeInventory API and pass the segment information, to avoid this error

On a separate note, instead of mixing segmented inventory, it is also suggested to consider using Tag controlled items and requested tag attributes in the shipment (ShipmentLineInvAttRequest attribute in the shipment XML) to meet your requirement. This issue does not occur with tag controlled items as Sterling does capture tag information during RF operations