3536612 - Error in LONGPOST.LOG after upgrade because of the phase MAIN_SHDIMP/SUBMOD_SHD2_RUN/XPRAS_SHD_AIMMERGE

There are errors reported by SUM in LONGPOST.LOG related to phase XPRAS_SHD_AIMMERGE after an upgrade. 

The log file LONGPOST.LOG has the following entries:

### CURRENT PHASE: MAIN_SHDIMP/SUBMOD_SHD2_RUN/XPRAS_SHD_AIMMERGE
2 EPU122XPost-import method "SACMDT_AFTER_IMP_DCL" started for "DCLS" "L", date and time: "20241028102538"
1PEPU203X--> Messages extracted from log file "SAPRxxxXPRAxxxxxxxx.SID" <--

    CAUSE
    During the upgrade, a message relevant for follow-on actions was written to a log file. This message is not handled until the end
    of the upgrade. The upgrade continues.
    
    SYSTEM_RESPONSE
    The upgrade stops in phase CHK_POSTUP. To create the reference to the original log file, this message is generated by SAPup.
    
    WHAT_TO_DO
    Note the messages following this message and proceed according to the instructions.

A3PEACM_SYNTAX 145 Start transaction SACMDCLS to review the status of access control "C_PPM_UPCMILESTONESPROJECTS""PPM-PRO"

    CAUSE
    The activation of CDS access control C_PPM_UPCMILESTONESPROJECTS failed.
    
    SYSTEM_RESPONSE
    Access to the CDS entity which was protected by this access control might fail with runtime error ACM_UNEXPECTED_VALUE and text
    "No runtime data for CDS entity ...".
    
    WHAT_TO_DO
    
    SYS_ADMIN
    Rework is required.
    Check with transaction SACMDCLS the status of the access control(s).
    For multiple access controls:
    Enter the names of access controls into the field "Access Control Name" using the select options ("Multiple Selection for Access
    Control Name"). Press "Execute". On the overview screen press "Show Overall Status". Afterwards check the status in column
    "Object status monitor result" (on the very left side) for every access control. If status is not "Object is consistent" with a
    green icon, mark the specific access controls and press the button "Generate". When generation returns with a syntax error for
    the given access control, create a ticket on component PPM-PRO.
    Access controls may depend from each other. In that case a correct order of regeneration is necessary. The tool SACMDCLS does not
    calculate the dependencies by itself but generate from the top to the bottom of the marked access controls. In that case, retry
    to generate all broken access controls and refresh the list until the status in column "Object status monitor result" remains
    unchanged for all access controls. Create a ticket on component PPM-PRO if the status of the object is not "Object is consistent".
    For one access control:
    Enter the name of the access control (C_PPM_UPCMILESTONESPROJECTS) into the field "Access Control Name" and press "Execute".
    Check that "Overall Status" of the access control is "Object is consistent" with a green icon. Press the button "Generate", if
    status is different. When generation returns with a syntax error for the given access control, create a ticket on component
    PPM-PRO.

* Here is an example, the error could happen on other CDS views.

Software Update Manager 2.0

XPRAS_SHD_AIMMERGE, C_PPM_UPCMILESTONESPROJECTS, C_PPM_MYPLANNEDPROJECTS, C_PPM_PROJECTELEMENTPROGRESS, C_PPM_TASKPREDECESSOR, C_PPM_TASKSUCCESSOR, C_PPM_MEASSUBSTITUTEPROJECTS, C_PPM_MEASSUBSTITUTEPROJOVP, I_PPM_PROJECTSUMMARYTASK, P_PPM_PROJECTLIST , KBA , BC-UPG-TLS-TLA , Upgrade tools for ABAP , Problem