When implementing common fields over a HD relationship, does those common fields become required even when not table required?
Ian is correct, making a field a common field on the HD table definition does not make those fields required on their respective tables, even if the common field configuration type is No Changes Allowed. It simply means that if those fields are present in the header, they will be persisted to the detail(s).