No lock modes adjustment P -> X needed. No tables with lock mode P found.

What causes this issue?

During a ZDM upgrade, some database tables can be accessed by both the
productive application and the after-import methods (AIM) in parallel.
For these tables, it must be ensured that the productive application
does not write data into the key areas accessed (read or write access)
by the after-import method. To ensure this, the AIM author declares in
which way these key ranges are blocked in the productive application.
The most important options are the lock modes "P" = "Write access to the
relevant key ranges is blocked" and "X" = "Write access to the complete
table is blocked".
In cases where the key ranges accessed by the AIM are blocked by special
locking mechanisms (such as lock mode = "P") in the application code
(which exist from a particular application release and support package
level (R/SPL)), it may happen that the source release of the current
upgrade is lower than R/SPL. In this case, the particular locking
mechanisms are not in place. This can cause data inconsistencies after
the upgrade.
To avoid these inconsistencies, the upgrade tool sets these tables as
read-only for the productive application on database level. For example,
the upgrade tool changes the classification provided by the AIM author
from "P" to "X".
For the AIM inspected here, no re-classification is necessary since the
AIM does not access a table with lock mode "P".

System Response

The upgrade tool informs you about this fact by writing this message to
the upgrade log.

How to fix this error?

No action required.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.