LeasePak Utilities

250 Vertex O Conversion Update

The Vertex-O Conversion Update Utility is a LeasePak Utility which allows a user to convert non-Vertex leases, applications, assets, application assets and vendors to make them Vertex O leases and applications compatible with the LeasePak Vertex "O" module. The utility takes an input file to process non-Vertex applications, leases, and assets to Vertex O applications, leases, and assets. Users can prepare an input file with detailed records to process records with basic parameters required by the Vertex O module. The utility takes an input file, process it with required parameters and records, and generates output log file. Users must first purchase Vertex O Interface module. The portfolio whose records require conversion must have settings enabled for Vertex O from U0212 and U0712. Users must set permissions to work in the portfolio from U0706 Security update. The selected portfolio must not plan for EOP (see U0401 Update).

Input File

User must first create an input file and place it in $udata directory ($TOPDIR/env/(environment_name)/data) of the user's environment. The input file for the VOCUU must be an ASCII text file. Users can prepare this file either on the server using a utility such as vi or on the MS Window PC by using a utility such as Notepad or Wordpad. VOCUU accepts input file of four types and restricted to contain only appropriate data with respect to input file type. Users can also use an Excel and Access to create input files and the resulting file will contain an ASCII text.

• vnd -- Vendors,
• lse -- Lease and assets,
• app -- Application and assets, and
• ast -- Assets unattached to leases or applications

Users must name input file as:

"p" + (portfolio number) + "_vtxo" + (file-type abbreviation) + ".dat"

Example

p14_vtxolse.dat

Where p14 is a portfolio 14

p3_vtxovnd.dat

Where Vendors for p3

Once the input file processed successfully will be removed from the user $udata directory. It is recommended that users must keep copies of the input files in order to better understand and differentiate the output files contents, which refers to the location within the input file line number.

Input File Format

Each type of input file permits only certain data.

1) vnd -- Vendors

The vendor input file must contain only vendors as <vendor> ... and so on. The vendors listed in the input file are independent of each other. If one vendor fails to fulfill the requirements conversion will not affect the other vendors in the input file. Input file processed once will be removed from the $udata directory.

Sample "vnd" Input File:

<comment>Multiple vendor
<vendor>40
	<taid>12345678
	<county>ALAMEDA
	<city>BERKELEY
	<state>CA
	<addr1>Add1 Conversion Utill Vendor40
	<addr2>Add2 Conversion Utill Vendor40
	<zip>94609
<vendor>41
	<taid>12345679
	<county>ORANGE
	<city>ORLANDO
	<state>FL
	<addr1>Add1 Conversion Utill Vendor41
	<addr2>Add2 Conversion Utill Vendor41
	<zip>94609 

2) lse -- Lease with assets

The "lse" file is restricted to contain only lease and the assets tied to those leases. The format of the "lse" file is:

<lease>Lease number

<asset>asset number

<asset>asset number

...

If lease number is given than it must be followed by, all of the assets tied to that lease. If any of the asset tied to that lease is not mentioned in the input file, than the entire lease and all of its mentioned assets will remain unchanged in the database. Successfull processing of the input file will produce an output file and removes the input file from $udata directory.

Sample "lse" Input File:

<comment>Suspended Lease
<lease>53
	<asset>84
		<taid>1234567891
		<county>ALAMEDA
		<city>BERKELEY
		<state>CA
		<taxpmttype>UR
		<taxcode>NOUT

<lease>54
	<asset>85
		<taid>222222222
		<county>ORANGE
		<asset>86
		<taid>3333333333
		<county>ORANGE
		<city>ORLANDO
		<state>FL
		<taxpmttype>UR
		<taxcode>NONR

<lease>55
	<asset>87
		<taid>4444444444
		<county>KENT
		<city>GRAND RAPIDS
		<state>MI
		<taxcode>NOAP
		
	<asset>88
		<taid>5555555555
		<county>KENT
		<city>GRAND RAPIDS
		<state>MI
		<taxcode>NONR

	<asset>89
		<taid>6666666666
		<county>KENT
		<city>GRAND RAPIDS
		<state>MI
		<taxcode>NOUT

<lease>57
	<asset>92
		<taid>4444444444
		<county>KENT
		<city>GRAND RAPIDS
		<state>MI
		<taxpmttype>UR

3) app -- Application and assets

The "app" file is restricted to contain only applications and assets tied to those applications only. If any asset tied to an application is not mentioned in the input file than, that particular application and its entire assets will remain unchanged in the database. Regardless of the success of updating individual applications and their assets, all other applications and their assets in the input file will be processed and deletes the input file from users $udata directory. The format of the "app" file is as follows with example:

<application>###<asset>###...<appasset>###...

<application>###<asset>###...

Sample "app" Input File:

   
<comment>Application number 51
<application>50
	<appasset>78
		<taid>50010018
		<county>ALAMEDA
		<city>TEMESAL
		<state>CA
		<addr1>Add1 Conversion Utill appasset78
		<addr2>Add2 Conversion Utill appasset78
		<zip>94609
		<comment>Invalid Tax Payment Type and tax code
		<taxpmttype>UR
		<taxcode>NAOP

<application>51
	<appasset>79
		<taid>50010019
		<county>ORANGE
		<city>ORLANDO
		<state>FL
		<addr1>Add1 Conversion Utill appasset79
		<addr2>Add2 Conversion Utill appasset79
		<zip>94609
		<taxpmttype>UR
		<taxcode>NOEX
		<comment>NOAP
		
	<appasset>80
		<taid>50010020
		<county>KENT
		<city>GRAND RAPIDS
		<state>MI
		<addr1>Addr1
		<addr2>Addr2
		<zip>94609
		<taxpmttype>UR
		<taxcode>NOEX

<comment>Application 52 with three assets
<application>52
	<appasset>81
		<taid>50010021
		<county>ALAMEDA
		<city>TEMESAL
		<state>CA
		<addr1>Add1 Conversion Utill appasset81
		<addr2>Add2 Conversion Utill appasset81
		<zip>94609

	<appasset>82
		<taid>50010022
		<county>ORANGE
		<city>ORLANDO
		<state>FL
		<addr1>Add1 Conversion Utill appasset82
		<addr2>Add2 Conversion Utill appasset82
		<zip>94609

	<appasset>83
		<taid>50010023
		<county>KENT
		<city>GRAND RAPIDS
		<state>MI
		<addr1>Add1 Conversion Utill appasset83
		<addr2>Add2 Conversion Utill appasset83
		<zip>94609

NOTE: The "app" file supports only two types of assets: pending assets and booked assets.

4) ast -- Assets unattached to leases or applications

The "ast" file must contain only assets that are not attached to any lease or application. The asset should not be tied to an application or a lease. All other asset(s) will process successfully. Any asset found in the input file attached to a lease or an application will remain unchanged in the database. Each asset listed in the input file is completely independent of each other. If one asset fails, the requirements of input file will not impact on the other assets of input file. Possessing successful completion of an input file will remove the input file from user $udata directory. The format of the "ast" input file is as follows with example:

<asset>

<asset>

<asset>

...

Sample "ast" Input File:

<comment> Batch of Assets
<asset>90
	<taid>1111111111
	<county>WAXAHOOTCHIE
	<addr1>Conversion Utill Asset#98
	<addr2>Conversion Utill Asset#98

<comment>Asset without taxt payment type and tax code
<asset>91
	<taid>2222222222
	<county>ALAMEDA
	<city>BERKELEY
	<state>CA
	<addr1>Conversion Utill Asset#99
	<addr2>Conversion Utill Asset#99

<comment>Asset with state CA
<asset>92
	<taid>3333333333
	<county>ALAMEDA
	<city>BERKELEY
	<addr1>Conversion Utill Asset#100
	<addr2>Conversion Utill Asset#100
	<state>CA
	<comment>Asset with state CA
	
<asset>93
	<taid>4444444444
	<county>ORANGE
	<addr1>Conversion Utill Asset#101
	<addr2>Conversion Utill Asset#101
	<city>ORLANDO
	<state>FL
	<zip>00625
	<comment>Asset with state FL

The input file tags syntax supported by the VOCUU is as follows with description of tags:

TAG	WHERE PERMITED	DATA
<comment>	Anywhere in the input	May contain any valid data. The comment text appears in the output file exactly as given, up to 58 characters. Characters beyond the 58th are lost.
<lease>	Top level of "lse" files only	Must be a valid lease # in the database; must be in the portfolio indicated by the input file; lease status must be not paid off; vendor must be enabled for vertex O; must not be an AFM contract; must not already be enabled for Vertex O; must not be extended, have midterm adjustments, or payoff quotes.
<application>	Top level of "app" files only	Must be a valid application # in the database; must be in the portfolio indicated by the input file; application status is immaterial; vendor must be enabled for vertex O; must not be an AFM contract; must not already be enabled for Vertex O.
<vendor>	Top level of "vnd" files only	Must be a valid vendor # in the database; must have as default portfolio. The portfolio indicated by the input file; must not already be enabled for Vertex O.
<asset>	As the second level "lse" and "app" files, and as the top level of "ast" files	Must be a valid asset # in the database; must be attached to the lease or application it falls under in the input if it's in "lse" or "app" file; must not be attached to any lease or application if in an "ast" file; must not already be enabled for Vertex O.
<appasset>	As the second level of "app" files, alternating with <asset> tags	Must be a valid pending asset in the database; must be attached to the application it falls under in the input file; must not already be enabled for Vertex O.
<taid>	As the third level of "lse" and "app" files, or as the second level of "ast" and "vnd" files.	One of the two required detail tags for each parent record indicates the "tax area ID" which is the central identifier for Vertex O. It is not validated by the conversion.
<county>	As the third level of "lse" and "app" files, or as the second level of "ast" and "vnd" files.	Second of the two required detail tags for each parent record, indicates the county in which the taxable item is located. It is not validated.
<addr1>	As the third level of "lse" and "app" files, or as the second level of "ast" and "vnd" files.	An optional detail tag, indicating the address where the taxable item is located. It is not validated by the conversion.
<addr2>	As the third level of "lse" and "app" files, or as the second level of "ast""and "vnd" files.	An optional detail tag, indicating the address where the taxable item is located. It is not validated by the conversion.
<city>	As the third level of "lse" and "app" files, or as the second level of "ast" and "vnd" files.	An optional detail tag, indicating a city name in which the taxable item is located. It is not validated by the conversion.
<state>	As the third level of "lse" and "app" files, or as the second level of "ast" and "vnd" files.	Must be a valid state in the rst state table; is an optional detail tag, indicating the abbreviation for the state in which the taxable item is located.
<zip>	As the third level of "lse" and "app" files, or as the second level of "ast" and "vnd" files.	An optional detail tag, indicating the zipcode of the address where the taxable item is located. It is not validated by the conversion.
<taxpmttype>	As the third level of "lse" and "app" files, or as the second level of "ast" files.	An optional detail tag, indicating the tax payment type of the item; must be a Vertex O allowed code.
<taxcode>	As the third level of "lse" and "app" files, or as the second level of "ast" files.	An optional detail tag, indicating the sales tax code for the item; must be a Vertex O allowed code.

User Interface

Users can run this utility from command line same as other LeasePak Utilities. After users log on to the LeasePak server, start the LeasePak Utilities, and select the Vertex O Conversion Update utility, the program displays:

  
This utility option will update leases, applications, assets, application assets, and vendors in a given portfolio, converting 
them to Vertex O using input data files which will include tax area IDs selected by the user.


Do you wish to continue (Y/N)?

Enter Y to proceed. The program will display:

 Client Password? 

Enter the correct LeasePak client string password to proceed. The program will display:

 
Enter the portfolio you want to process; leave portfolio blank to exit this utility.

Portfolio:

Enter valid portfolio number to process non-Vertex records conversion to Vertex-O records. The program will display:

1 => p2_vtxovnd.dat                               
2 => p2_vtxolse.dat        
3 => p2_vtxoapp.dat        
4 => p2_vtxoast.dat

The above files are available for processing for this portfolio. Enter the numbers corresponding to the files you want to process for this 
portfolio in this session. Enter the selected numbers all on one line, separated by commas. Leave file numbers blank to select a different portfolio.

File numbers:

Enter the number of files to process for this portfolio. For multiple files enter the numbers of files separated by commas in one line or leave blank to select a different portfolio.

1 => p2_vtxovnd.dat        
2 => p2_vtxolse.dat        	
3 => p2_vtxoapp.dat        
4 => p2_vtxoast.dat

The above file(s) have been selected for processing for this portfolio in this session. Do you want to process these files now? (Y/N)

Enter Y to proceed. The program will display:

p2_vtxovnd.dat - Checking input
p2_vtxovnd.dat - Checking eligibility and updating
p2_vtxovnd.dat - Formatting reports

Processing of the p2_vtxovnd.dat file is now complete. The audit report/home/username/p2_vtxovnd20120714_2315.log documents the results of this update.
p2_vtxolse.dat - Checking input
p2_vtxolse.dat - Checking eligibility and updating
p2_vtxolse.dat - Formatting reports
Processing of the p2_vtxolse.dat file is now complete. The audit report/home/username/p2_vtxolse20120714_2315.log documents the results of this update.
p2_vtxoapp.dat - Checking input
p2_vtxoapp.dat - Checking eligibility and updating
p2_vtxoapp.dat - Formatting reports
Processing of the p2_vtxoapp.dat file is now complete. The audit report/home/username/p2_vtxoapp20120714_2315.log documents the results of this update.
p2_vtxoast.dat - Checking input
p2_vtxoast.dat - Checking eligibility and updating
p2_vtxoast.dat - Formatting reports
Processing of the p2_vtxoast.dat file is now complete. The audit report/home/username/p2_vtxoastd20120714_2315.log documents the results of this update.
Processing of the selected files for portfolio 2 is now complete.

Processing of selected files for conversion has been completed successfully. Press Enter to exit.

Output

The utility produces an output audit file located in the user's home directory. To keep the output audit files separate from each other when records of one portfolio are batched in multiple input files, the output audit files contain the date and time in their file name, and will have the portfolio and input file type in their file names, same as input files.

Following are the output audit files names:

Input Type	Input File Name	Audit File Name
vnd	p#_vtxovnd.dat	p#_vtxovndYYYYMMDD_HHMM.log
lse	p#_vtxolse.dat	p#_vtxolseYYYYMMDD_HHMM.log
app	p#_vtxoapp.dat	p#_vtxoappYYYYMMDD_HHMM.log
ast	p#_vtxoast.dat	p#_vtxoastYYYYMMDD_HHMM.log

Where p# is portfolio number,

vtxoFileNameCYYYYMMDD_HHMM.log is Vertex O file type. FileName will be replaced by the type of file. YYYYMMDD_HHMM is the date and time the output file created.