smartform->ADS form conversion error

[Former Member]

Hello,

I have to migrate a Smartform to ADS form by using the embedded function in SMartforms transaction.

After I have converted the form I got the ADS interface and ADS form.

If I see the interface I can see the old parameters (i.e. printer options) present but in grey. If I acces the form these parameters are not visible and I canu2019t use some field from them.

I run transaction SFP with the converted form . In transaction SFP you have 2 sections: form and interface

When I go to interface section of this form I have

inside FORM interface->IMPORT->

ARCHIVE_INDEX TYPE TOA_DARA 1 1 ***

ARCHIVE_INDEX_TAB TYPE TSFDARA 1 1 ***

ARCHIVE_PARAMETERS TYPE ARC_PARAMS 1 1 ***

CONTROL_PARAMETERS TYPE SSFCTRLOP 1 1 ***

MAIL_APPL_OBJ TYPE SWOTOBJID 1 1 ***

MAIL_RECIPIENT TYPE SWOTOBJID 1 1 ***

MAIL_SENDER TYPE SWOTOBJID 1 1 ***

OUTPUT_OPTIONS TYPE SSFCOMPOP 1 1 ***

USER_SETTINGS TYPE TDBOOL 1 1 'X'

MKPF TYPE MKPF 0 0

MSEG TYPE MSEG 0 0

BUNDLE TYPE CHAR5 0 0

Parameters ARCHIVE_INDEX thru USER_SETTINGS are in grey and cannot be used

when I go to to form utility

On the left of the screen i have three folders:

ZGR002_RU (name of the form)

Import folder

MKPF Header: Material Document

MSEG Document Segment: Material

BUNDLE R/2 table

global data folder

system field folder

As youi can see the import parameters are less than the ones present in interface section.

if i activate the form I have the following error

Form ZGR002_RU, Node X2500_HEADING @0A\QError@

Conditions, row 1: Field OUTPUT_OPTIONS-BCS_LANGU does not exist

BCS_LANGU is a field of OUTPUT_OPTIONS structure present only in the interface section, but seems does not exist inside the form or the context.

Do you have any hint?

Thanks in advance

Fabrizio

[madhu_vadlamani]

Hi Fabrizio,

BCS_LANGU is a field of OUTPUT_OPTIONS structure present only in the interface section, but seems does not exist inside the form or the context

Have you seen in this message.

Regards,

Madhu.

[Former Member]

Hi Madhu.

Of course it is. and that's the problem

My question was, how is possible the auitomatic export function of smartforms creates this folders using a structure that causes error during form compiling?

OUTPUT_OPTIONS is a mandatory structure in smartform and was exported in INTERFACE sectionin ADS. So I guessed this has a meaning.

How can I solve it? should I replicate the structure in the global definition and move the original structure in "code initialisation" section?

BR

Fabrizio