For anyone interested, here's what I found.  In $LAWDIR/system there is a file rqc_config.xml.  In this file you can make a few changes (hide fields, make fields required, make fields view only).  I think is the field Kat was referring to.

Buried deep into WebSphere, in a directoty with a name similar to /lawson/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/vlawapptst01Cell01/RQC.ear/rqc.war/xFiles/xml/language are your translation files.  I was able to make static changes to on-screen field names here by editting the English file (enus.xml).

(duplicate post)

When we were onprem version 9, I could RDP to the Websphere appserver hosting the RQC.ear file and go directly to W:\IBM\WebSphere\AppServer\Profiles\installedApps\Cluster02Cell01\RQC.Ear\rqc.war\xFiles\xml\language\default.xml

Later (v9.x/v10) multiple language support was introduced, default.xml was gone ,and in its place were 4 files: enus.xml (english US), arsa.xml (arabic Saudi Arabia), eses.xml (spanish. Espainia), or ptbr.xml (portuguese, Brasil) and I would update enus.xml.

Now we are in the cloud.

In the cloud there are two ways.
One way is to open a ticket with Infor Support and request a current copy of the enus.xml file, update it send it back and ask them to deploy it.
If you have LID access you may be able to login to your lsapps, and go to (you may need to poke around to find the RQC.ear file)
D:\IBM\WebSphere\AppServer\profiles\lawsonapps\installedApps\xxxxxxxxxxxxCell01\RQC.ear
RQC.Ear\rqc.war\xFiles\xml\language\enus.xml
And update it there. I always copy the old one before changing, (cp enus.xml cp enus.xml.20200601),
if you make a mistake with html you will break RQC!

You may need to update the file after every RQC upgrade. I've had to update mine about 30 times in the last 10 years.

[N.B.: We also move fields around in profile.xsl.
Caveat for cloud, files may need to be included in an agreement for supported customizations. ]