cancel
Showing results for 
Search instead for 
Did you mean: 

SAP Support Package Implementation (SAPKB70111)

former_member280874
Participant
0 Kudos

Hi,

We are busy implementing SAP Support Packages in our Production

Environment. We are patching the components from 70105 to 70113.

everything went well and we got all components on 70110. The problems

started with importing SAPKB70111. We could not get pass Check

Requirements. Now we receiving a syntax error massage every time we try

to use SPAM transaction code.

------------------------------------------------------------------------------------------------

Short text

    Syntax error in program "SAPLSDB1 ".

What happened?

    Error in the ABAP Application Program

    The current ABAP program "SAPLOCS_EXTIF" had to be terminated because it has

    come across a statement that unfortunately cannot be executed.

    The following syntax error occurred in program "SAPLSDB1 " in include "LSDB1$24

     " in

    line 9:

    "Type "DDTRIGGERNAME" is unknown"

    " "

    " "

    " "

    The include has been created and last changed by:

    Created by: "SAP* "

    Last changed by: "SAP* "

    Error in the ABAP Application Program

    The current ABAP program "SAPLOCS_EXTIF" had to be terminated because it has

    come across a statement that unfortunately cannot be executed.

---------------------------------------------------------------------------------------------------------------

Looks like all other transaction codes are fine and only SPAM is not working, thus

we cant continue with the import.

Please let us know if you require more information.

thanks you in advance

regards

Steven

Accepted Solutions (1)

Accepted Solutions (1)

former_member185239
Active Contributor
0 Kudos

Hi Steve,

Checked the below sapnotes

1809597 - Syntax error in SAPLSDSB or SAPLSDB2

1749824 - Treatment of SLT triggers during transport

With Regards

Ashutosh Chaturvedi

former_member185239
Active Contributor
0 Kudos

Hi Steve,

Did you face any issue while applying in QAS and DEV

Also check the below error and also paste the error its showing in SPA M/SAINT

1839881 - SPAM/SAINT error during CHECK_REQUIREMENTS regarding open conversion request still existing

With Regards

Ashutosh

former_member280874
Participant
0 Kudos

Hi Ashutosh

Thanks for information, the notes were very helpful. i implemented SAP Note 1749824 and that coursed the errors i had. after reading SAP note 1809597, i reset note 1749824.

i am now able to use spam and started an import queue successfully

thanks

Steven

former_member185239
Active Contributor
0 Kudos

Hi steven,

Great!!! Thank you.

With Regards

Ashutosh Chaturvedi

Answers (0)