2385919 - [Best Practice] How to solve dump LOAD_VERSION_LOST and dump LOAD_PROGRAM_LOST

The LOAD_VERSION_LOST dump and/or LOAD_PROGRAM_LOST dump is occurring in the system, but you don't know the detailed steps to solve it.

Normally in the ST22 dump log, we can find similar descriptions like:
Data type............................: "XXXX"
Time stamp of requested version......: 20140414193330
Time stamp of found version..........: 20160309162900
The request was made from the following object:
Object type..........................: "Type"
Object name..........................: "XXXX"
Time stamp of requesting object......: 20160309154319

Program name..............................: "XXXX".
Load format of the application server.....: "1981/9C7200BFFED2A984F4C5892B22785B92 | 56676".
Load format of the program in the database: "1981/2503F990BD80800796D7219E217C3C5C | 55476".
Program name..............................: "XXXX".
Time stamp of the requested version....: 20131219210357.
Time stamp of the version found........: 20160928103205

Object type..........................: "Prog"
Object name..........................: "XXXX"
Time stamp of requesting object......: 20160531134508

• ABAP system
• Upgrade scenario is not included

LOAD_VERSION_LOST, LOAD_PROGRAM_LOST, TYPELOAD_NEW_VERSION, PXA, $PXA, SYNC, SEGN, TOUCH, structure, change, transport, activation, repository, DDIC, load, generation, version, mismatch , KBA , saplrsodso , cx_sy_program_not_found , BC-ABA-LA , Syntax, Compiler, Runtime , BC-DB-DBI , DB Independent Database Interface , Problem