Testing Logic Script UJKT

[Former Member]

Hi, this is simple document about the t-code UJKT and how can be useful to use this resource available in BPC NW.

Basically, UJKT it's a testing tool. Dispenses execute a package in data manager to execute a logic script, hence reduces the develop/testing time. Besides has a complete log about the logic execution.

The UJKT transaction is divided in three frames:

1. 1.    Settings;
2. 2.    Action;
3. 3.    Script code.

The Settings frame is used to determine the environment and the model, as the image below:

It is allowed also to simulate a variable created in data manager package. 

For that use the PARAM field to define Dynamic Script variables that will be used in the script

PARAM VAR1=MEMBER1;VAR2=MEMBER2

In the script text variables can be used like:

$VAR1$ and $VAR2$

The ability to pass PARAM's to the script make it easy to test real scripts with $$ variables.

The Action frame contains the execution buttons, there are three of them:

1 - VALIDATE, will just verify the code, but not execute it.

2 - EXECUTE, will validate, execute and write the records in the cube effectively.

3- EXECUTE(Simulate), will validate and execute the script,  but not write the result in the cube.

PS: In EXECUTE (Simulate), there is no detailed records list with values to be written, in opposite that occurs in EXECUTE.

In the Action frame, has also an input area, Data Region, where it determines variables of scope, simulating for example a package with the PROMPT statement selecting and restricting dimension members. This can be done with the dimension name, such as:

1. i.e.: TIME = 2012.JAN

CATEGORY = ACTUAL

The Script Code frame, placed on bottom of the transaction is divided into two. The first is an entry on the left side, where it is typed / pasted the logic script.

PS: If the script is saved on BPC Admin, you can also trigger it using the *INCLUDE statement to invoke it:

• *INCLUDE your_Script.LGF

On the right is the log area, where is showed the calculations and results logs, or in case, the syntax error.

Above the example uses the Data Region resource, in the scope *XDIM_MEMBERSET TIME = %TIME_SET%.