error dump while updating support packs

[Former Member]

Hi everyone,

We are in the middle of updating our support packs (SAPKA70011 to 12) when it suddenly stopped and displayed an ABAP error. See part of the dump below.

-

---

Short text

Syntax error in program "SAPLSCP2 " ....

What happened?

Error in the ABAP Application Program

The current ABAP program "SAPLOLEA" had to be terminated because it has come across a statement that unfortunately cannot be executed.

The following syntax error occured in program "SAPLSCP2 " in include "CL_SALV_FORM_ELEMENT==========CU " in line 13:

"The type "IF_SALV_FORM_CONFIG" is unknown."

-

---

I can't even save it to file to show you the entire error because everytime I press any button or execute any transaction, it would give me this error dump... it would just vary on the program.

Do you think updating the kernel would solve the issue? Our current kernel patch level is 75.

Would appreciate your response.

regards all!

[Former Member]

Hi, Im giving the phases of Suport packages for an overview.

But i think you can delete the hanged support packages from the tables PAT01 & PAT03 logging in as SYSDBA through OS level.

Experts plz some comment on this weather it is possible or not.

Also try doing kernel upgrade to 114

Phases of the Support Package Manager

The Support Package Manager runs through a series of phases when it imports Support Packages. If you want to know which phases were performed for which scenario (test scenario or standard scenario), execute program

RSSPAM10.

The following list provides an overview of all the modules and phases and lists them in the order in which they are executed by the Support Package Manager:

Module: Preparation

1. PROLOGUE

This phase checks if you are authorized to import Support Packages.

2. CHECK_REQUIREMENTS

This phase checks various prerequisites for importing Support Packages such as the tp logon to your system.

3. DISASSEMBLE

This phase disassembles, or unpacks, the data files from the relevant EPS parcels and copies them to the transport directory.

4. ADD_TO_BUFFER

This phase copies the queue to the transport buffer of your system.

5. MODIFY_BUFFER

In this phase, the transport buffer is prepared for correct processing of the following import phases.

6. IMPORT_OBJECT_LIST

This phase imports the object lists of the Support Packages in the queue into the system.

7. TEST_IMPORT

This phase performs a test import for the current queue using tp. It checks if there are objects that are in open repairs and will be overwritten during the import, or if any other circumstances are preventing an object from being imported successfully.

8. OBJECTS_LOCKED_?

This phase checks if there are objects that will be overwritten by the Support Package, and that are still in requests that have not yet been released.

9. ADDON_CONFLICTS_?

This phase checks if there are conflicts between the objects in the queue and the installed add-ons.

10. SCHEDULE_RDDIMPDP

This phase schedules the transport daemon (program RDDIMPDP).

Module Import 1

11. CREATE_VERS_BEFORE

This phase generates versions of the objects in the Support Packages that are in the queue.

12. SPDD_SPAU_CHECK

This phase checks if a modification adjustment is necessary (Transactions SPDD/SPAU).

13. DDIC_IMPORT

This phase imports all ABAP Dictionary objects in the queue.

14. AUTO_MOD_SPDD

This phase checks if modifications to ABAP Dictionary objects can be adjusted automatically.

15. RUN_SPDD_?

This phase prompts you to adjust your modifications to ABAP Dictionary objects with Transaction SPDD.

16. LOCK_EU (For Import Mode Downtime-Minimized Only)

This phase locks the development environment.

17. INACTIVE_IMPORT (For Import Mode Downtime-Minimized Only)

This phase imports program code and program texts in an inactive state.

Module Import 2

18. DDIC_ACTIVATION

This phase activates the imported Data Dictionary objects.

19. IMPORT_PROPER

This phase imports all Repository objects and table entries, provided they have not already been imported during the phase INACTIVE_IMPORT. This is preceded by actions such as table conversion and activation of the name tabs.

20. PREPARE_XPRA

This phase prepares the XPRAs and after-import methods to be executed.

21. UNLOCK_EU (For Import Mode Downtime-Minimized Only)

This phase unlocks the development environment.

22. AUTO_MOD_SPAU

This phase checks whether modifications can be adjusted automatically.

23. XPRA_EXECUTION

This step executes the XPRAs and the post-import methods.

24. ABAP_GENERATION

This phase generates runtime objects for the imported Repository objects (ABAP source texts and screens).

Module Cleanup

25. RUN_SPAU_?

This phase prompts you to adjust your modifications to Repository objects with transaction SPAU.

26. CLEAR_OLD_REPORTS (For Import Mode Downtime-Minimized Only)

This phase deletes obsolete versions of the program code and program texts in the database.

27. EPILOGUE

This phase completes the import of the Support Package. It also checks if the queue was processed completely.

[Former Member]

Hi

Try to apply support packs at OS level.(in the background)

If not this case then

Go trough this note:-

822379 Problems with Support Packages

Try to apply some notes

[Former Member]

Hi Prabhakar,

The support packs were not at all applied when I checked at OS level since I can no longer transact from SAP. It's stucked somewhere. I would like to try importing the support packs at OS level instead. I just don't know how it is done. Kindly share the steps how to do this.

Also, anyone who can help me out on this would be very much appreciated.

Thanks in advance!

[Former Member]

Hi

Try this :

[Former Member]

Hi Prabhakar,

Thanks! But the link you gave does not contain the commands how to move the import at OS level. But I was able to move it anyway and gave you points since you gave me the idea of moving sps at OS level.

For those who faced the same issue and would like to try importing at OS level, this is what I did that worked for me. Check first if its applicable to your system.

command is:

tp r3i SAPKXXXXXX SID pf=D:\usr\sap\trans\bin\TP_DOMAIN_SID.PFL tag=spam

[Former Member]

Hi,

check using se24 that class CL_SALV_FORM_ELEMENT having interface IF_SALV_FORM_CONFIG

check sysntax of class,

also check whether SAP BASIS SP12 SAPKB70012 is applied or not

regards,

kaushal

[Former Member]

Hi Kaushal,

I mention that I could not do nor execute any transaction when I logged in to SAP. I don't think it's possible to execute SE24. If it is, pls let me know how.

However, I was able to check that SAPKB70012 is not yet applied. It seems it's stucked somewhere. Any idea?

Thanks!