2024 Jan 03 9:47 AM
Hi experts,
I have a sapscript when I call a new page with the following sentence to pint a different information in this new page:
CALL FUNCTION 'CONTROL_FORM'
EXPORTING
command = 'NEW-PAGE NEXT2'
EXCEPTIONS
unopened = 1
unstarted = 2
OTHERS = 3.
In development environment it works perfectly, however when I transport the modifications to the quality environment it doesn't work. Both SapScripts are identical, so the modifications are transported correctly.
Do yo have any idea what is happened?
Thanks in advanced!
2024 Jan 03 11:41 AM
I guess the culprit is NOT this command. The data you print is probably different between dev and quality, it's probably the reason. You should debug your program in quality.
2024 Jan 03 11:55 AM
Hi Sandra,
The information in both, dev and quality, are exactly the same.
We change the information in dev with the same information as in quality and in dev the new page is created but in quality no.
Thanks!
2024 Jan 03 12:33 PM
2024 Jan 03 12:37 PM
are there translations involved? Is the operating language the same in both environments?
2024 Jan 03 1:47 PM
Hi Andrea,
Yes, there are translations in different languages in dev all works correctly and in qualitity none of them work.
Thanks!
2024 Jan 03 3:51 PM
Difficult to understand.
Are you just repeating that "new page doesn't work", or are you saying that "translations don't work"?
Is it only a problem of new page, or nothing is printed at all?
2024 Jan 03 3:56 PM
my guess, without further info I can't really say, is that the translations are not present and the two modules are running with different languages, one of which does not have that control command in place.
a sapscript debug session would show that quite clearly.
2024 Jan 03 4:25 PM
Hi Sandra,
The NEW-PAGE doesn't work.
I print FIRST -> NEXT -> NEXT2. In quality only print FIRST -> NEXT, the NEW-PAGE NEXT2 is not printed.
Hi Andrea,
I try to print the form in different languages and in all of them I have the same result, that is to say, the page NEXT2 is not printed.
Thanks!
2024 Jan 03 4:56 PM
2024 Jan 03 6:58 PM
Thanks, so the issue is not related to translations.
If you can't find the issue by debug, please provide information about the debug/trace information, about your SAPscript form, and so on.
Either it's a SAP bug
or a difference due to data or different SAPscript form
or a bug in your SAPscript form.
I doubt that it is a SAP bug.
Don't forget that SAPscript is client-dependent (just in case you don't know).