BMXAA4187E error message on Maximo Mobile

Symptoms:
Selecting any Work Order, under My Schedule app on the Mobile device (works fine on the Technician Roled Based Application), one of these two error messages are displayed:

BMXAA4187E - The relationship WOBYLOCATION does not exist for business object WORKORDER. Verify that the relationship specified in parameter WOBYLOCATION exists in the Max relationship table.

BMXAA4187E - The relationship WOBYASSET does not exist for business object WORKORDER. Verify that the relationship specified in parameter WOBYASSET exists in the Max relationship table.

One other symptom is the Work Order list remaining empty and in the Maximo logs, these messages are displayed:
BMXAA6713E - The MBO fetch operation failed in the mboset with the SQL error code -104.
The record could not be retrieved from the database. See the log file for more details about the error.com.ibm.db2.jcc.am.SqlSyntaxErrorException: An unexpected token "order by statusdate desc" was found following "value not in ('CAN'))". Expected tokens include: "<space>". SQLCODE=-104, SQLSTATE=42601, DRIVER=4.29.24

[ERROR] [WORKORDER] BMXAA6714E - The data for the next record in the mboset could not be retrieved for the SQL query:

Select * from workorder where location= 'LOCATION' and siteid= 'SITEID' and istask=0 and status in (select value from synonymdomain where domainid ='WOSTATUS' and maxvalue not in ('CAN')) order by statusdate desc order by statusdate desc for read only. See the log file for more details about the error.

Note: note the 2 “order by” clause in the query.

Fixing the issue:
The two offending relationships WOBYLOCATION (from the LOCATIONS object) and WOBYASSET (from the ASSET object) both have "order by" clauses in the Where clause on the relationship tab of Database configuration.

The resolution is to remove the “order by” clause from the where clause entry. In doing so, the issue is resolved on the device. Both (WOBYLOCATION and WOBYASSET) must be cleared:

Mobile for EAM 8.8 and MAS 8.8 with Manage 8.4 don't have that "order by" clause anymore.
The script that fixes that relationship is the v7613_244.