That is the status assigned to receiver lines that are newly created, but not yet saved.  So if you use the next number toolbar button for a new receiver, the RcvrKey will have a status of 1 (Incomplete).  Once you save the receiver line, the status changes to 2.

So, under expected processing paths, this should mean that there is current activity happening at the time of query.  However, it is possible that the records may hang around if the application were to terminate unexpectedly (you could use the Windows Task Manager to kill poztl001.exe to simulate).  In that case, any entered but unsaved receiver lines would leave behind these tpoReceiverLog records with a status of 1.  They could also be the result of an issue in the system (Sage or customization related).  I took a quick stab at trying to create them in our current upcoming 2018 release and could only create them by manually killing the application.  There could be many ways to process receiver lines (imports, etc.), so my testing was not exhaustive.

In the best case scenario, they are expected due to current activity.  In the worst case, they are likely orphans.  If they are the latest records in the table, they are more likely due to current activity.  The older they are, the more likely they are to be orphans.  Since there is no CreateDate field in that table, you probably have to go off the RcvrKey sequential value to try and estimate when the records were created.

Blindly deleting them all could be dangerous, so appropriate care should be taken when trying to delete any suspected orphans.

I hope this may shed some light onto what might have happened or is happening.

All of them are old, but we seem to get one about once a month, so I was interested in understanding if the users were doing something out of the ordinary, but your explanation makes me feel that it is just the occasional network failure/system lockup/squirrels on the wire kind of thing that is the cause, which I am OK with.  

Thanks for providing such a comprehensive response.

All of them are old, but we seem to get one about once a month, so I was interested in understanding if the users were doing something out of the ordinary, but your explanation makes me feel that it is just the occasional network failure/system lockup/squirrels on the wire kind of thing that is the cause, which I am OK with.  

Thanks for providing such a comprehensive response.