Human Capital Management Blogs by Members
Gain valuable knowledge and tips on SAP SuccessFactors and human capital management from member blog posts. Share your HCM insights with a post of your own.
cancel
Showing results for 
Search instead for 
Did you mean: 
sahusamita
Explorer
Overview 

Plateau Report Designer (PRD) is a client tool to creates reports for use in SuccessFactors Learning.
Plateau Report Designer is also referred as BIRT. The content of this page is dedicated to the consultant's who face different kind of error either while connecting to PRD tool or errors while creating queries.

 

You will encounter many error while connecting PRD tool as well during creation of query.

Plateau Report Designer is a tool that customers will use to create their own custom reports or modify existing reports so they can import and publish them in the LMS. Mostly, they will be using admin side reports but customers can also overwrite existing LMS reports on the user side.
If a customer wishes to use their own report, say a custom Certificate of Completion report, they will need to import their custom report .zip file with the same exact name as the standard report .zip file and then un-publish the standard, and publish their newly imported custom report so that it overrides the standard. The LMS will then use their custom report instead.

1. Connection error -

Due to security and performance issue connecting to SuccessFactors Learning production instance is not supported.

 


Connection error


Details of error –

rg.eclipse.birt.report.data.oda.jdbc.JDBCException: There is an error in get connection, java.sql.SQLException: java.net.ConnectException: Connection timed out: connect
at java.net.DualStackPlainSocketImpl.connect0(Native Method)
at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl. ....
at org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager.doConnect(JDBCDriverManager.java:337)

 

Resolution –

 

Proxy Server Settings is required for users that are behind a Proxy Server. e.g., Corporate network. Due to client/company security layer or zscaler this kind of error will occur.

To configure PRD to connect through a Proxy, the PlateauReportDesigner.ini file will need to be modified. This file can be located in the root directory of PRD (e.g. C:\Program Files (x86)\PlateauReportDesigner). Or copy it in desktop if don’t have edit right to program files.
Firstly, open the file with a text editing program (Textpad, NotePad, Notepad++).

By default, you should see the following lines:

-vmargs
-Xms40m
-Xmx256m
-XX:MaxPermSize=128m

Add the following lines to the file (as appropriate – notations following each line describing when and if it should be included)

-Dhttp.proxySet=true<===Required - keep at http regardless if http or https is being used
-Dhttp.proxyHost=[value of proxy host]<==If using http
-Dhttp.proxyPort=[value of proxy port]<==If using http
OR
-Dhttps.proxyHost=[value of proxy host]<==If using https
-Dhttps.proxyPort=[value of proxy port]<==If using https

The following should be added is a user id/password combo is required to access the internet via the Proxy.

-Dhttp.proxyUser=[User ID]
-Dhttp.proxyPassword=[Password]
The final file should look like this:
-vmargs
-Xms40m
-Xmx256m
-XX:MaxPermSize=128m
-Dhttp.proxySet=true
-Dhttps.proxyHost=proxy.companyname.com
-Dhttps.proxyPort=1234
-Dhttp.proxyUser=TomUser
-Dhttp.proxyPassword=password
Save the file.

2. Commonly faced errors

• Plateau Report Designer (PRD) Tool version 4.4.1.2

Refer KBA - https://launchpad.support.sap.com/#/notes/2318900

• "Unknown user" error when connecting to PRD

Refer  KBA - https://launchpad.support.sap.com/#/notes/2318510

• How do I export the zip file for certificate from Learning to Plateau Report

Refer  KBA- https://launchpad.support.sap.com/#/notes/2186196

• Pipe export option in the Plateau Report Designer (PRD)

Refer  KBA -https://launchpad.support.sap.com/#/notes/2192625

Plateau Report Design Tool  - How to connect and start working after PRD installed in system

Plateau Report Designer is one client tool to creates reports for use in SuccessFactors Learning For hosted customer, We provide VJDBC url for connecting to SuccessFactors Learning stage instance. But it is not supported to connect to SuccessFactors Learning production instance as it will cause security and performance issue easily

1. Launch your locally installed instance of PRD.
2. In PRD, select File > New > New Report.
3. Change File Name if necessary and then click Finish button.
4. Right click on Data Sources in Outline panel and then select New Data Source.
5. Select option Create from a data source type in the following list, and then select JDBC Data Source.
=>In the Data Source Name box, type a name that will help you remember the source, such as the customer’s name (CompanyXYZ).
6. Click Next .
7. Enter the following info:
o Driver Class: de.simplicit.vjdbc.VirtualDriverBirtWrapper (v1.6)
o Driver URL: jdbc:vjdbc:servlet:https://<CompanyXYZ>-stage.plateau.com/vjdbc/vjdbc,db10g
=>Please replace <CompanyXYZ> with your Tenant ID.
=>Generally, Tenant ID could be found from SuccessFactors Learning stage instance URL like "https://<CompanyXYZ>-stage.plateau.com/learning/admin/nativelogin.jsp".
o User Name: one ADMIN account having REPORT_DEVELOPER role assigned
=>If this role doesn't exist in your SuccessFactors Learning stage instance, please create an incident to support.
o Password:
=>By default, it should be same as the password of the ADMIN account used to log in to SuccessFactors Learning stage instance.
8. Click button Test Connection.

Once test connection is successful.

SF Learning Report Designer - Installing Report Designer- short video by SAP -


Refer -  https://sapvideoa35699dc5.hana.ondemand.com/?entry_id=1_8uhz3p20

KBA - 2777238 - Learning Report Designer (a.k.a. Plateau Report Designer) Setup and  Troubleshooting Tips

9. Open file > New > New Report> Give report name and start building query

 

Error while creating query in PRD tool

  1. Memory allocation error while preview the result in PRD tool.



 

Resolution – If there is issue in the query logic this kind of issue comes. Need double check the query logic.

2. Invalid Column error – Check the alias.

3.Column ambiguity error – check if that column in used in the query or exist in the tables.

4.incorrect syntax near ")" – check if any comma (,) is used before where clause or from clause or in the query where is not required.


 5. Binding error


Resolution

Check the column bindings correct it. In my case I have used NOTACTIVE field in the layout that is not exist, or removed.

6. Data set error while importing query in sf lms -


Resolution - Correct the data set fields and layout and reimport

 

7. Security group missing error while importing query-


 

Resolution -  Correct the security in the PRD query


 

8.  Search selector is frizzed - the calendar didn't work


 

Resolution - Check the search selector section built in the query.


Conclusion:
Remember below points while taking requirement of PRD reports and building query
• After understanding the requirement. Think of what tables can be used to pull data.
• What are the foreign keys can be used to map the fields and tables.
• Use fresh query instead of using standard query.
• Refer latest Data dictionary.
• Every query have 3 sections
Select
From tables
Where clause with joins to map
• Union query can be used in certain conditions where data needs to be come from different tables.
• For double entries always check the where clause and joins how mapping has done. Same goes to missing data.
One thing to remember from my query building and testing that you need to have your vjdbc code and your REPORT_DEVELOPER role assigned to you admin id you use in PRD. I assumed for purposes of this post that most would have this information/setup. To get the vjdbc for your staging instance you simply put in a ticket to SF and make sure to request the REPORT_DEVELOPER role be in your instance if it is missing.
This post is a good first step in resolving errors while creating your own custom reports with clean SQL.
If you have questions or comments please feel free to add them into the comments.

Thanks for your attention and feedback,

Samita Sahu

 
1 Comment
Labels in this area