5
http://scn.sap.com/docs/DOC-31043 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: t 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 n 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:

Testing Logic Script UJKT | SCN

Embed Size (px)

Citation preview

Page 1: Testing Logic Script UJKT | SCN

13-05-13 9:21Testing Logic Script UJKT | SCN

Página 1 de 5http://scn.sap.com/docs/DOC-31043

Getting Started Newsletters Store

Solutions Services & Support About SCN Downloads

Industries Training & Education Partnership Developer Center

Lines of Business University Alliances Events & Webinars Innovation

Login RegisterWelcome, Guest Search the Community

Activity Communications Actions

Browse

0 TweetTweet 1

created by Lucas Gabriel Corrêa da Costa on Aug 20, 2012 3:23 PM, last modified by Lucas Gabriel Corrêa da Costa on Aug 23,2012 9:36 PM

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, hencereduces 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 scriptPARAM 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:

Testing Logic Script UJKT

ShareShare Like 0

Version 3

Page 2: Testing Logic Script UJKT | SCN

13-05-13 9:21Testing Logic Script UJKT | SCN

Página 2 de 5http://scn.sap.com/docs/DOC-31043

Average User Rating

(8 ratings)

0 TweetTweet 1

Products: SAP Business Planning and Consolidation

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 inEXECUTE. In the Action frame, has also an input area, Data Region, where it determines variables of scope, simulating for examplea package with the PROMPT statement selecting and restricting dimension members. This can be done with thedimension name, such as:

i. 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%.

1414 Views Tags: script_logic, ujkt, script_logic_tester, bpc_nw, t-code

ShareShare Like 0

Page 3: Testing Logic Script UJKT | SCN

13-05-13 9:21Testing Logic Script UJKT | SCN

Página 3 de 5http://scn.sap.com/docs/DOC-31043

Follow SCNSite Index Contact Us SAP Help PortalPrivacy Terms of Use Legal Disclosure Copyright

7 Comments

Like (0)

Fabio Tomaz Aug 21, 2012 9:12 PM

Great doc.

Like (0)

Alan Valenzuela Aug 23, 2012 6:36 PM

Thank you for this document, I am new in BPC NW.

Like (4)

Vadim Kalinin Aug 23, 2012 9:09 PM

Hi Lucas, Please add to your very good document the explanation how to use the PARAM field in the Settingsframe: In the PARAM field you can define Dynamic Script variables that will be used in the scriptPARAM 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. For 3- EXECUTE(Simulate) - it can be mentioned, that opposite to 2-EXECUTE there is no detailedrecords list with values to be written. B.R. Vadim

Like (1)

Lucas Gabriel Corrêa da Costa Aug 23, 2012 9:30 PM (in response to Vadim Kalinin)

Thank you Mr. Vadim. Always with good inputs. Regards,Lucas

Like (0)

Surender Miryala Oct 6, 2012 10:19 PM

I am new in BPC NW.Thank you for dis Doc. Regards,SRM

Like (0)

Dietmar Gessler Jan 29, 2013 2:55 PM

Thank you, really good document

Like (1)

Pedro Santiesteban Jan 29, 2013 10:31 PM

Hi Lucas, Nice document. Just be careful when using pretty print on your web interface and then taking yourscripts to UJKT cause sometimes i get an error like this: UJK_VALIDATION_EXCEPTION:Line 52: Unknown or unimplemented keyword "" Even if the script validates correctly on the web. To solve it i just eliminate Tabs or additional spacesgenerated by the pretty print and it should work. Kind regards, Pedro

Page 4: Testing Logic Script UJKT | SCN

13-05-13 9:21Testing Logic Script UJKT | SCN

Página 4 de 5http://scn.sap.com/docs/DOC-31043

Page 5: Testing Logic Script UJKT | SCN

13-05-13 9:21Testing Logic Script UJKT | SCN

Página 5 de 5http://scn.sap.com/docs/DOC-31043