on 09-08-2011 9:35 AM
Hello guys.
How to debug script logic ?
So i can see if my scoping, calculation part, and commit are correct.
See the data of scoping just like i debug itab in abap program, see variable value, etc.
Thank you.
Hi all,
I guess there have been changes in BW regarding this topic in the last 2.5 years, because I am looking at Transaction UJKT and half of the fields you are talking about is not there.
I would also like to reiterate about a .pdf file: Any guides, tutorials out there?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Just to clarify what Gersh already laid out below.
There is NO Script Logic Debugger per se. There was a Script Logic Debugger in versions of OutlookSoft prior to the SAP acquisition of OutlookSoft however since then there has not been a Debugger that you can view your Script Logic Code in and step through a debugger like you can in ABAP.
However as Gersh laid out in his response you can Debug the ABAP that interprets your Script Logic coding. This is a bit more complicated as you need to understand the looping constructs and how the Script Logic Engine is interpreting the code in ABAP etc.
UJKT - is a transaction that you can use to run your Script Logic inside of SAPGUI so that you get -
1) Better error messaging
2) The capability to debug if you really in truly are able to dig into the code within the UJK Package.
3) The capability to test different Script Logic scenarios for specific users other than your own (which comes in handy if you are testing security and want to make sure that the Script Logic is being restricted during its reads appropriately)
So in summary,
1) There is no Script Logic Debugger.
2) You can debug the ABAP that interprets the Script Logic
3) There is a SAP Gui transaction that can help you do this (UJKT)
Hopefully this clarifies things a bit.
Cheers, Scott
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
You can try using the T-code UJKT.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
UJKT is the right first step, but then you have to put a break-point in the program that executes your script. Unfortunately data retrieval for different key words is done in different programs, but all of them are called from CL_UJK_RUN_LOGIC class.
Also, all of the transaction data retrievals go through SQE engine and you can put a break-point there, but it could be difficult to find out from what part of the script this call was made.
Regards,
Gersh
User | Count |
---|---|
6 | |
5 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.