Good morning, I have seen several instances of very long runtimes when shipping order lines. While I was troubleshooting this issue, I found that the source of the long runtimes (20 minutes+) came down to an external SP called EXTSSSFSUnitConfigAutoCreateSp. I have included the nested code path below so you can see where is comes into play.
As a bandaid solution, I put in an EXTGEN on TrackSp to comment out that code that creates FS Units for serial tracked items. I then processed another shipment which completed in 1 second, grabbed the matltrack record for that shipped serialized part and attemped to run this stored procedure for that newly created TrackNum from MatlTrack and found that I had to stop the execution after 5 minutes. If you look at the attached file of some PRINT statements on a couple of procedures including when the ShipShipmentSp starts and completes, this external SP seems to be doing a whole lot of something, but since it is an external SP, I have no indication of what that might be. 20k lines of record affected is all that I have to go on and this is for a single qty shipment of a single serialized part. Do you have any tips or tricks or updates for this code that I could pose as a solution? They need units created for these serial numbers, but not at the expense of a total shutdown of their production environment due to each shipment taking half an hour or more. I would prefer using out of the box code rather than having to reproduce the logic to create the FS Unit records along with any child data, but I will in a pinch if I have to. Thanks in advance.
ShipShipmentSp
COShippingLoopSp
COShipvSp
COShippingTrxPostSp
TrackSp
EXTSSSFSUnitConfigAutoCreateSp <This guy
