SMARTFORM short dump

[Former Member]

I've made few changes to SMARTFORM in development and imported to quality.

when I tried to display same form in quality, getting short dump with below message

Error when importing object "T_NTOKENS"

and the error is coming in standard FM SSF_READ_FORM at below code..

import t_ntokens from database stxfcont(xx) id i_formname

Please suggest me how can I fix this error.

Thanks

[vijaymanikandan]

Hi Perez,

Refer the Note 1087385 - Smart Forms with error 'CONNE_IMPORT_CONVERSION_ERROR'

It might help you if you are getting the same problem.

Regards,

Vijay V -

[Former Member]

Did the form name change? Does the data exist in table stxfcont? Is the table/structure imported into exactly the same as it was prior to your changes? Are you missing the step that exported the tokens to STXFCONT(xx)....? This is "semi-persistent" data intended to store values for use by any program in the instance/client on any apps server, but the data has to be put there first with export, then you need to import it back into exactly same structure or table with the keys named (XX) and Formname.

[Former Member]

No Form name has been changed. data is there in stxfcont table.

In fact this dump is coming in standard function module. What I did was modified SMARTFORM in development and imported corresponding transport request into quality. export/import contents to stxfcont table is not in our hand ..right?

[vijaymanikandan]

Hi

Can you paste your runtime error ? Did the OSS note help you?

Regards,

Vijay V

[Former Member]

OSS note is not relevant to my issue.

Runtime Errors IMPORT_ALIGNMENT_MISMATCH

Exception CX_SY_IMPORT_MISMATCH_ERROR

Date and Time 21.02.2012 14:12:34

-

-

---

-

-

---

Short text

Error when importing object "T_NTOKENS".

-

-

---

-

-

---

What happened?

Error in the ABAP Application Program

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

come across a statement that unfortunately cannot be executed.

-

-

---

-

-

---

Error analysis

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was

not caught in

procedure "SSF_READ_FORM" "(FUNCTION)", nor was it propagated by a RAISING

clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

When importing object "T_NTOKENS", the structure did not match the

structure of the target object. The error occurred in component

no. 2.

This may be due to one of the following reasons:

- the structure is actually different (the next field has, for

example, a different data type) or

- the same sequence of components were exported and imported,

but the fields were from other include units.

-

-

---

-

-

---

Source Code Extract

-

-

---

Line

SourceCde

-

-

---

20
21	data: l_stxfadm type stxfadm.
22
23	Test, ob das Formular überhaupt existiert
24	Lesen der Verwaltungsdaten
25	select single * from stxfadm into l_stxfadm
26	where formname = i_formname.
27	if sy-subrc = 0.
28	o_admdata = l_stxfadm.
29	else.
30	raise no_form.
31	endif.
32
33	Lesen des Formulars gemäß der geforderten Fassung
34	falls die gesicherte Fassung nicht existiert, wird die aktive Fassung
35	gelesen
36	perform init_datatabs.
37
38	o_active = i_active.
39
40	if i_active = space. " gesicherte Fassung
41	import t_ntokens t_objt t_ltext
42	from database stxfconts(xx) id i_formname
43	ignoring conversion errors.
44	if sy-subrc <> 0.
45	select * from stxfobjt into table t_objt
46	where formname = i_formname.
47	select * from stxftxt into table t_ltext
48	where txtype = c_text_form
49	and formname = i_formname.
>>>>>	import t_ntokens from database stxfcont(xx) id i_formname
51	ignoring conversion errors.

[Former Member]

Here's the cause....something obviously changed...

When importing object "T_NTOKENS", the structure did not match the | | structure of the target object. The error occurred in component | | no. 2. | | This may be due to one of the following reasons: | | - the structure is actually different (the next field has, for | | example, a different data type) or | | - the same sequence of components were exported and imported, | | but the fields were from other include units. |