Saving YSL Reports

After creating a new YSL report from an existing YSL report, you must save the report (.xls) file for future editing, viewing, or printing.

Both YSL Classic and YSL.Net reports require the authorship of a companion Yardi Script (.txt) file when they are to be processed by either YSL report generating engine.

The structure and scope of a Yardi script file is completely fixed for a YSL.Net report and cannot be adjusted.

A YSL Classic report has significantly more leeway at the script level; however, if a YSL Classic script deviates from the YSL.Net fixed structure, it can only be generated through the YSL Classic engine. For more information, including the requirements for a Yardi script, see the Voyager SQL Scripting Guide.

If you are designing with YSL.Net, see “To author a companion script (.txt) file automatically: YSL.Net”. If you are designing with a YSL Classic .xla, or if you choose not to use the automatic script authoring procedure, see “To save the Excel (.xls) file and the script (.txt) file”.

To author a companion script (.txt) file automatically: YSL.Net

The following procedure is illustrated using Excel 2010. If you use a version of Excel other than 2010, the commands and screens may be different from those described in this procedure.

1	From the Excel top menu, click the Add-Ins tab.

2	Click Create Matching Script File for Service Manager.

a	If you open a YSL report that has already been saved to a specific location on your computer, the following graphic appears.

b	Select the platform used by your Voyager database. YSL remembers these settings after the first usage.

c	If your YSL report employs functions with parameters set to return values broken down by G/L segmentation, select the Include GL Segments in the filter and in the selects box.

d	YSL.Net creates estimates for the name and title of the script based on the name of the YSL report.

You can modify the script (.txt) file name. The following naming convention should be adopted so that the script file is recognized and exposed from Reports > SQL Reports. For more information, see “Generating YSL Reports in Voyager Service Manager”. Platform First 3 characters of the file name SQL Server rs_ or rx_ Oracle ro_ or rx_ Subsequent characters in the file name should match (case insensitive) one of the character sequences that have been defined in the Voyager System Administration > Accounts and Options > SQL Reports Prefixes setup dialog.

You can modify the title that appears in the filter display within the Yardi program. You cannot change the folder location; this location is the same as your saved YSL report.

3	After creating the script (.txt) file, move both it and the .xls file as a pair into the reports path of your Yardi product.

To save the Excel (.xls) file and the script (.txt) file

1	From Excel, create a new YSL report from an existing report; for example, from rs_YSL_Balance.xls. For more information, see “Creating YSL Reports”.

2	From the Excel top menu, select File.

3	From the side menu, select Save As. The Save As screen appears.

4	Select a location and a name for the modified YSL report; for example, rs_YSL_Balance02.xls.

The prefix rs_ or ro_ denotes the database platform type, SQL or Oracle, respectively.

5	Click Save.

6	Locate and open the companion script (.txt) file of the existing Excel YSL report that you used to create your new .xls file; for example, rs_YSL_Balance.txt.

7	In the //Title section of the script, type a title name (in this example, Balance Sheet 2). This title becomes the label on your YSL report filter and is also passed to cell A1 of your .xls file when you generate the YSL report.

As shown in the preceding graphic, YSL requires that the first item of the first Select statement be the token: '#@@UserLogin#'. If you are authoring a YSL script from scratch, '#@@UserLogin#' must be the first item of the first Select, otherwise the YSL report will not generate.

8	In the //Database section of the script, enter the name of the YSL .xls report that you want the program to reference when the YSL report is generated.

YSL assumes that the .xls file specified in the //Database section is located in your defpath (the reports path in Voyager). If the .xls file is in a different location, you must specify the complete alternate path in the //Database section. For example, if the .xls file is located in a sub-directory of the defpath named YSL, you would enter the complete path: Y:\Yardi\defpath\YSL\rs_YSL_Balance02.txt.

9	Select File > Save As. The Save As dialog screen appears.

10	Enter a name in the File name field. Each file name should have the prefix rs_ (denoting a SQL report) or ro_ (denoting an Oracle report). For example, rename the script (.txt) file (rs_YSL_Balance02.txt) to correspond with its companion .xls report file.

11	Click Save. After you save the Excel workbook and its corresponding script file, you can generate the YSL report in Enterprise or Voyager. For more information, see “YSL Report Organization in Voyager: YSL.Net”.