cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Runtime Errors SYNTAX_ERROR while importing the SPAM

Former Member
0 Likes
3,085

Hi Techies,

We have encountered the below dump while appyilying the SPAM (SAPKD70051). i am able to open all the transcation expect SPAM and

SAINT

========================DUMP=========================================

Syntax error in program "SAPLOCS_EXTIF ".

What happened?

    Error in the ABAP Application Program

    The current ABAP program "SAPLOCS_CRM" had to be terminated because

it has

    come across a statement that unfortunately cannot be executed.

    The following syntax error occurred in program "SAPLOCS_EXTIF " in

include

     "LOCS_EXTIFU43 " in

    line 468:

    "The data object "LS_STACKHEADR" does not have a component

called "GEN_"

    "VERS"."

    " "

    " "

    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_CRM" had to be terminated because

it has     come across a statement that unfortunately cannot be

executed.

========================================================================

a. Intially it terminated at IMPORT_PROPER phase.

b. Ran the below command at os level.

idsadm> tp R3I SAPKD70051 IDS pf=/usr/sap/trans/bin/TP_DOMAIN_IDS.PFL

tag=spam -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8

This is tp version 380.08.41 (release 720, unicode enabled)

This is R3trans version 6.23 (release 720 - 15.05.12 - 20:12:03).

unicode enabled version

R3trans finished (0004).

tp finished with return code: 4

meaning:

  A tool used by tp produced warnings

Then the above dump stated.

Please adivse the steps to over come the error as we have no

backup of the present system.

I see the SPAM patch still in the buffer.

idsadm> tp showbuffer IDS pf=/usr/sap/trans/bin/TP_DOMAIN_IDS.PFL

tag=spam

This is tp version 380.08.41 (release 720, unicode enabled)

IDS buffer:

TASK |PROJECT |P|CMD Im|DD Im |DD

Act|MainIm|ADO Im|VersFl|Deploy|XPRA |ChkDpl|Gener |UMODE|TAGS

--------------------+--------------------+-+------+------+------+------

+------+------+------+------+------+------+-----+----

SAPKD70051 | | |*0004 |*0004 |*0004 |*0004

| | | |7 | | | |D

that makes 1 transport to be imported.

tp finished with return code: 0

meaning:

Everything OK

Regards,

Sandeep Singh

View Entire Topic
Former Member
0 Likes

Hi,

Check the below steps .

Goin Se38 -> LOCS_EXTIFU43 and display

then check if it is active.

Goto line 486 and see

IF ls_stackheadr-gen_vers(1) = 'U'.

when you double click on gen_vers it would take to to one table STACKHEADR. I think that you having issue due to this.

Have you tried to restart the system an rerun spam.

As the below commnad completed with warning .

dsadm> tp R3I SAPKD70051 IDS pf=/usr/sap/trans/bin/TP_DOMAIN_IDS.PFL

tag=spam -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8

This is tp version 380.08.41 (release 720, unicode enabled)

This is R3trans version 6.23 (release 720 - 15.05.12 - 20:12:03).

unicode enabled version

R3trans finished (0004).

tp finished with return code: 4

Should only run when sap suggests you

tp r3i <SP> <SID> pf=e:\usr\sap\trans\bin\tp_domain_sid.pfl tag=spam

I dont think you should have issues.

But usually we don't run the below command till sap suggests.

Another thing that you don't have backup is bit worrying for me.

Thanks

Rishi Abrol


Former Member
0 Likes

Hi Rishi,

What 's the next step once i go the below line?

when you double click on gen_vers it would take to to one table STACKHEADR. I think that you having issue due to this.

Regards,

Sandeep Singh

Former Member
0 Likes

hi,

is it active.

Thanks

Rishi abrol

Former Member
0 Likes

YES

Former Member
0 Likes

Can you provide screenshot for STACKHEADR from SE11?

Former Member
0 Likes

Hi Roman,

Pls find se11 screen shots

-sandeep

Former Member
0 Likes

Hi Rishi,

Apologies,

The table STACKHEADR does not exist in database, when i tried to create in via SE11 its errored out.


with below error

Request: Create Table STACKHEADR (SAPUSER/15.11.13/20:10)

Process: lsinm013sape_3

sql:

CREATE TABLE "STACKHEADR"

("ID" SAPDB6VARCHAR(000020)

DEFAULT ' ' NOT NULL,

"QUEUE_ID" SAPDB6VARCHAR(000040)

DEFAULT ' ' NOT NULL,

"TYPE" SAPDB6VARCHAR(000010)

DEFAULT ' ' NOT NULL,

"PROD_ID" SAPDB6VARCHAR(000020)

DEFAULT ' ' NOT NULL,

"DESCRIPT" SAPDB6VARCHAR(000072)

DEFAULT ' ' NOT NULL,

"INSTSTATUS" SAPDB6VARCHAR(000001)

DEFAULT ' ' NOT NULL,

"INST_DATE" SAPDB6VARCHAR(000008)

DEFAULT '00000000' NOT NULL,

"INST_TIME" SAPDB6VARCHAR(000006)

DEFAULT '000000' NOT NULL,

"RESPONSIBL" SAPDB6VARCHAR(000012)

DEFAULT ' ' NOT NULL)

IN "IDS#STABD"

INDEX IN "IDS#STABI"

LONG IN "IDS#STABD COMPRESS YES"

SQL0107N The name "IDS#STABD COMPRESS YES" is too long. The maximum

length is "18". SQLSTATE=42622

DDL time(___1): .........1 milliseconds

The SQL statement was not executed

Statements for Table STACKHEADR could not be executed

Request for STACKHEADR could not be executed

Regards,

Sandeep Singh

Former Member
0 Likes

Hi,

Did you try to use se14 as i can see in the above screen shot that the table is showing.

Also one more thing go in SE09 and give the details of the patch and click display.

Then double click on the patch no and see if you can see this table in the list and all the object are generate .

Thanks

Rishi Abrol

Former Member
0 Likes

Hi Rishi,

I tried to activate via SE14, giving the same error.

When i checked SE09 i can see the patches and i cannot see all the table but few of them are in implemented/active state.

Regards,

Sandeep Singh

Former Member
0 Likes

Hi,

I think why this issue is happening as the

LONG IN "IDS#STABD COMPRESS YES"

SQL0107N The name "IDS#STABD COMPRESS YES" is too long. The maximum

length is "18". SQLSTATE=42622

What i think that the table has go a field lenght of 18 characters and we have 23 here and that is the reason why it is failing.

Can you please take the help of any developer and see if you can increase the length or reduce the characters and then try to create it.

Or

Try to create a message to sap that you are not ale to create the table at DB level using SE14.

And see if they can provide a code fix . Just tell that you want the table to be created at DB leavel and its not getting created due to this issue.

I have see similar issue was sap program was not passing the correct details and the tablespace name was more.

eg:1846770 - DB6: NLS Impl. - SQL0107N tablespace name is too long

It can be issue with sap standard code as its recent release and no one would have identified it and you are the first one to get it as the patch was released by 25.10.2013.

Thanks

Rishi abrol

Former Member
0 Likes

Hi Rishi,

The Problem has been resolved by when i followed the instrustion followed in the SAP Note 1126127.

went to SE13 -> database object -> remove Longspace and reactivated the table the issue got resolved.

Regards,

Sandeep