Sap script name in STXH table saved with suffix SAP, Why?

[Former Member]

Hi,

• I created a new script and tested in development. It worked fine with expected output.

• But, when i moved it to quality, the program is giving error"Script not exist or not active" upon executing.

• This error is coming because the program is using function module "FORM_CHECK".

• This function module is checking table STXH for the form name.

• For example my form name is 'ZNEW_SCRIPT', In STXH table the in TDNAME field the form is saved as 'ZNEW_SCRIPTSAP'.

• In development the data is correct in STXH table, But in quality only it is happening like this. I tried in different ways to create script and moved to quality, every time it is giving same problem.

• In quality in SE71 also, in administrative data the details of changed by are coming as SAP not DDIC.

Please help me on this issue anyone?

[Former Member]

Hi Murali ,

I never saw this type of problem in past , Can you please explain how you are transporting the script into quality , Means including in TR .

Regards,

Shyam Sunder Goyal

[Former Member]

I created script and while saving creted new TR and saved. while transporting released it from SE01 the task and the TR as per process. Is there any other way of transporting script?

[former_member221827]

Just a thought, if you have multiple development clients, make sure you have the updated sapscript form in the one you plan to transport to quality.  Sapscript forms are client dependent unlike reports.

Otherwise you should be able to add it to a workbench request and transport the form like you would do any other object.

[Former Member]

Hi Chris,

Thanks for the reply. I have only one development and one test client. while testing in test client i did copied from development only. In test client it worked properly. But, when i moved to quality only the problem is coming like above.

[Former Member]

Can anyone help me on this issue to resolve?

[alexander_bolloni]

Hello,

the suffix ...SAP to form objects in STXH is created whenever you save a modified form without activating it: This suffix distinguishes inactive forms from active forms... Only active version can be used for printing.

Transport is also only possible for active forms. Ensure you have no inactive versions anywhere before you transport...

Regards,

  Alex

[Former Member]

Hi alexander,

When i was transporting the script to quality it was in active state in development and when i see the script in quality, the status in 'Active - Saved' in quality also. Still the name is saving with suffix SAP.

[kiran_k8]

Murali,

Check in which languages  'ZNEW_SCRIPT' and 'ZNEW_SCRIPTSAP' script is available in Dev and Quality.Did you copied any script to create your script with a new name ?

K.Kiran.

[Former Member]

Hi Kiran,

I copied an exsting script and created a new script with that to get different business.

In the copied script i changed main and footer windows and according logic in program for the script.

The original script is in 21 languages and i changed it in language 'EN' in my new script.

The language properties in Dev and quality in STXH table are same.

[kiran_k8]

Murali,

First things first.Did you downloaded the production version of the script to your desktop before proceeding with the changes in Dev ?If not,do it.In the worst case if you development changes have gone wrong very badly still you would be able to upload the production version back to DEV and keep them in synch.

As your Script is in 21 languages,Check if your changes are reflecting even in other langauge Script also ?

K.Kiran.

[Former Member]

Kiran,

I downloaded the production version on to the desktop first and uploaded in development and did changes to the script. it worked fine without any problem. But, after moving to quality only this problem is coming.

[Former Member]

Kiran, The changes are not reflecting in other languages. They are reflecting in only EN language.

[Former Member]

Hi,

The problem was, the font of one of paragraph format i have used was not available in quality.

After changing the it to available quality font it worked fine. Thank you guys for ur efforts.