Hi Muhammad,

I highly recommend requesting help from IBM support. As you have observed, IBM BAW LDAP user sync is be case-insensitive by default. So, you will have to update the LSW_USR_XREF table manually.

The steps for doing so would be along these lines: 
1.      Determine whether flushing WAS User Registry cache would make sense
2.      Shutdown BAW server
3.      Backup the server and also the table data (CREATE TABLE LSW_USR_XREF_BACKUP AS SELECT * FROM LSW_USR_XREF;)
4.      Update the records:
UPDATE LSW_USR_XREF
SET USER_NAME = UPPER(USER_NAME)
WHERE USER_NAME != UPPER(USER_NAME);
COMMIT;
5.      Start BAW server
6.      Check the data in LSW_USR_XREF table
7.      Refresh BAW cache if needed

Reference material: 
Based on your database and BAW version a good reference would be documentation that specifically talks about case sensitive variations. Such as here: https://www.ibm.com/docs/en/bpm/8.6.0?topic=sgmbg-configuring-bpm-handle-white-space-letter-case-variations-in-ldap-server

Additionally, a few APARs that are relevant to the username case-sensitivity issue: https://www.ibm.com/support/pages/apar/JR56655

https://www.ibm.com/support/pages/apar/JR58657

Also related to user group membership synchronization: 

https://www.ibm.com/support/pages/apar/JR53171

Note that BPM is long out of support. BAW (Business Automation Workflow) is today's product name.

Many "special treatments" have been added over time. When you sign in as a user ABC1234 and the code finds a user abc1234 in cache or the database, we'll use the lower case record. That is, even if your user's representation has changed, you continue to have the same permissions and task assignments as before.

Do you actually need the user to show up in upper case for cosmetic reasons?

Hi Jens,

The requirement for uppercase usernames in the BAW database is driven by custom code that expects query results to be returned in uppercase (e.g., ABC1234). Any deviation from this format will break the functionality.

Regards,

Haris

Note that BPM is long out of support. BAW (Business Automation Workflow) is today's product name.

Many "special treatments" have been added over time. When you sign in as a user ABC1234 and the code finds a user abc1234 in cache or the database, we'll use the lower case record. That is, even if your user's representation has changed, you continue to have the same permissions and task assignments as before.

Do you actually need the user to show up in upper case for cosmetic reasons?

In that case, I concur with Ajay's post above.

Hi Jens,

The requirement for uppercase usernames in the BAW database is driven by custom code that expects query results to be returned in uppercase (e.g., ABC1234). Any deviation from this format will break the functionality.

Regards,

Haris

Note that BPM is long out of support. BAW (Business Automation Workflow) is today's product name.

Many "special treatments" have been added over time. When you sign in as a user ABC1234 and the code finds a user abc1234 in cache or the database, we'll use the lower case record. That is, even if your user's representation has changed, you continue to have the same permissions and task assignments as before.

Do you actually need the user to show up in upper case for cosmetic reasons?

Hi Jens,

Please check my response to Ajay's post, as that does not apply to our scenario.

Regards,

Hais

In that case, I concur with Ajay's post above.

Hi Jens,

The requirement for uppercase usernames in the BAW database is driven by custom code that expects query results to be returned in uppercase (e.g., ABC1234). Any deviation from this format will break the functionality.

Regards,

Haris

Note that BPM is long out of support. BAW (Business Automation Workflow) is today's product name.

Many "special treatments" have been added over time. When you sign in as a user ABC1234 and the code finds a user abc1234 in cache or the database, we'll use the lower case record. That is, even if your user's representation has changed, you continue to have the same permissions and task assignments as before.

Do you actually need the user to show up in upper case for cosmetic reasons?

The good news is that the numeric id is the primary key of this table. Code should not refer to users by name, but by numeric id in all "serious places".
Of course there are exceptions, but they tend to not matter much, e.g. the "last modified" field of an artifact in authoring (process designer) users a by name reference.

Anyway, a support ticket should help you.

Hi Jens,

Please check my response to Ajay's post, as that does not apply to our scenario.

Regards,

Hais

In that case, I concur with Ajay's post above.

Hi Jens,

The requirement for uppercase usernames in the BAW database is driven by custom code that expects query results to be returned in uppercase (e.g., ABC1234). Any deviation from this format will break the functionality.

Regards,

Haris

Note that BPM is long out of support. BAW (Business Automation Workflow) is today's product name.

Many "special treatments" have been added over time. When you sign in as a user ABC1234 and the code finds a user abc1234 in cache or the database, we'll use the lower case record. That is, even if your user's representation has changed, you continue to have the same permissions and task assignments as before.

Do you actually need the user to show up in upper case for cosmetic reasons?

Hi Haris, 

You will have to weigh the effort (and timeline) for the two options you have: (a) update the username in the product table versus (b) change the custom code to accommodate the case difference. I recommend starting with a support ticket to get a realistic take on the first option. 

The good news is that the numeric id is the primary key of this table. Code should not refer to users by name, but by numeric id in all "serious places".
Of course there are exceptions, but they tend to not matter much, e.g. the "last modified" field of an artifact in authoring (process designer) users a by name reference.

Anyway, a support ticket should help you.

Hi Jens,

Please check my response to Ajay's post, as that does not apply to our scenario.

Regards,

Hais

In that case, I concur with Ajay's post above.

Hi Jens,

The requirement for uppercase usernames in the BAW database is driven by custom code that expects query results to be returned in uppercase (e.g., ABC1234). Any deviation from this format will break the functionality.

Regards,

Haris

Note that BPM is long out of support. BAW (Business Automation Workflow) is today's product name.

Many "special treatments" have been added over time. When you sign in as a user ABC1234 and the code finds a user abc1234 in cache or the database, we'll use the lower case record. That is, even if your user's representation has changed, you continue to have the same permissions and task assignments as before.

Do you actually need the user to show up in upper case for cosmetic reasons?