ORG_ID issue following RPC5 Patching

A customer is testing RPC5 patches.

On the upgraded test instance, they have noticed that the ORG_ID on the Request is generally populated now, whereas on the non upgraded instance, it is NULL - e.g. examples from SQL checking concurrent requests (ORG_ID on the far left of the output):

Upgraded with RPC5:

Not upgraded with RPC5:

Also I have noticed that if I submit e.g. a Request Set on the upgraded instance, to start with, the Operating Unit is NULL:

But then when the job resubmits itself, the OU is populated.

I wondered if anyone might know what has caused this change in behaviour? I realise it's something in RPC5, but I wondered if there is something more specific?