LeasePak 6.1a Release Notes
Includes release information through build 6.10.2936
Release Bulletin
The updated list of LeasePak 6.1a enhancements and discrepancy fixes is now part of the Release Bulletin. You can also find a copy of the Release Bulletin (61a_release_bulletin.pdf) in the ReadMe folder.
Fixed Discrepancies Listing
The Fixed Discrepancies Listing contains an archive listing of dicrepancies fixed in LeasePak versions prior to 6.1a. For discrepancies fixed in LeasePak 6.1a, refer to the Release Bulletin.
Notices
End of Period Sequential Updates: Restart after Failure Issue
End of Period Sequential Updates: Restart after Failure Issue
Heat Ticket 525039
This issue pertains only to users on LeasePak 6.0a, 6.0b, or 6.1a builds prior to the indicated builds where NetSol has corrected this issue.
This issue has been fixed in versions:
- 6.0a, build 6.00.2271
- 6.0b, build 6.01.2685
- 6.1a, build 6.10.2905
Users who have not yet upgraded their production database to 6.0a, 6.0b, or 6.1a should use the latest builds to avoid this issue.
If this issue pertains to your current installation, request and upgrade to the appropriate LeasePak build on your server.
Workaround Available
NetSol has developed a workaround (see below) users can employ while waiting to upgrade to a corrected build.
Description of issue:
Whenever users restart Sequential Updates after an End of Period failure, LeasePak appends to the PAP/ACH Preauthorized Payments Bank File rather than deleting and recreating it. This can result in erroneous multiple withdrawals from a lessee's bank account. Payment posting in LeasePak, on the other hand, remains correct because the PAP/ACH Batch Payments File is always deleted and recreated whenever users restart End of Period after a failure.
NetSol has corrected this issue so that the PAP/ACH Bank File is deleted and recreated whenever users restart End of Period after a failure.
This issue has been fixed in versions:
- 6.0a, build 6.00.2271
- 6.0b, build 6.01.2685
- 6.1a, build 6.10.2905
Workaround
Use the following procedure to correct this issue in builds prior to the indicated corrected builds.
- If you run multi-process End of Period, use U0402 Status Review to determine the number of the process that failed. If you do not run multi-process End of Period, the process number will be 1.
- Locate the Bank File in the LeasePak server $top/env/environment/data directory, where environment is the name of the affected environment. This directory is also known as the $data directory. The file name format is:
pn_bank_xxxxxx_cN.dtl
where n is the portfolio number, xxxxxx is the date, and N is the process number. If you do not run multi-process End of Period, the process number will be 1. - Delete this file or move it to another directory for reference.
- Restart End of Period.
Sybase Only: Conversion Error on rpd.batch_num_s
Heat Ticket 525522
This issue pertains only to Sybase users who either: (1) converted their production database using release 6.0b MR2 or prior (any build prior to 6.01.2699), or (2) converted their production database using release 6.1a GA or prior (any build prior to 6.10.2906).
This issue has been fixed in version 6.0b, build 6.01.2699 and version 6.1a, build 6.10.2906. Users who have not yet upgraded their production database to 6.0b or 6.1a should use the latest builds to avoid this issue.
If this issue pertains to your conversion, install the appropriate LeasePak build on your server (for 6.0b users, 6.01.2699 or later; for 6.1a users, 6.10.2906 or later) and run the corrective scripts as described below.
This error and corrective patch pertain to Sybase users only.
As a result of the currently shipped conversions, users upgrading their databases from a pre-v60b release to v60b or later (e.g., v53a to v60b, or v60a to v61a, etc) and who have any records in the rpd (payoff quote), will show a failure in the procedure s60blpux_proc3resize.sql relating to rpd.batch_num_s not allowing null values. The result is that a vital modification of the new rpd.batch_num_s column is not performed. This can lead to further errors in the future and could contribute to system instability.
This patch consists of 4 files modified or created to correct this issue, both for future upgrades such that they will be performed without this error, and for previously upgraded databases to correct the error and perform the needed operation on rpd.batch_num_s.
Of the 4 files, the first 3 are part of the standard database upgrade procedure, sgenlpux_conversion, and are called when a database is upgraded through or to v60b:
- $uconv/s60blpux_proc3resize.sql - the previous, error prone handling of rpd.batch_num_s has been removed
- $uconv/s60blpux_proc2rpd.sql - the handling of rpd.batch_num_s has been relocated here
- $uconv/genconcfg - specifies that $uconv/s60blpux_proc2rpd.sql be called during a regular database conversion
The 4th file is to be executed by the database administrator on databases previously upgraded through or to v60b:
- $uconv/s60b_rpd_standalone - corrects the rpd.batch_num_s in previously upgraded databases
All 4 of these files will be present in all future shipments of v60b and v61a. For users who are in receipt of a build containing this patch prior to upgrading their databases through or to v60b, there are no special instructions; the upgrade process should complete successfully after a build containing the patch is installed.
For users who are in receipt of a build containing this patch after upgrading their databases through or to v60b, and the upgrade was performed with a build prior to v60b build 6.01.2699 or v61a build 6.10.2906, the user must install the build containing the patch and then execute the corrective s60b_rpd_standalone script as follows in each database upgraded prior to the builds stated:
Login as $MSIDBA that pertains to the release in question.
Execute:
$top/env/envname/conv/s60b_rpd_standalone envname [dbo-password]
The DBO password will be prompted for if it is omitted from the command line. The user should see a display such as the following:
> $top/env/prod/conv/s60b_rpd_standalone prod pwdprod 2008-11-23 19:13:02 s60b_rpd_standalone: Correct rpd.batch_num_s in v60b database (prod)lpr_prod 2008-11-23 19:13:02 s60b_rpd_standalone: Running commands as lpr_prod 2008-11-23 19:13:02 s60b_rpd_standalone: Start conversion of (prod)lpr_prod 2008-11-23 19:13:02 s60b_rpd_standalone: Step 1.0: Start 2008-11-23 19:13:02 s60b_rpd_standalone: Step 1.0 (Start) Set compat_id_s in rcg ... 2008-11-23 19:13:02 s60b_rpd_standalone: Step 1.0 (Start) Turn on bulkcopy ... 2008-11-23 19:13:03 s60b_rpd_standalone: Turning on bulkcopy option... 2008-11-23 19:13:03 s60b_rpd_standalone: Step 2.0: Handle column 2008-11-23 19:13:03 s60b_rpd_standalone: Step 2.0 (Handle column) Update batch_num_s ... 2008-11-23 19:13:04 s60b_rpd_standalone: Step 2.0 (Handle column) Modify batch_num_s ... 2008-11-23 19:13:04 s60b_rpd_standalone: Step 3.0: Finish 2008-11-23 19:13:04 s60b_rpd_standalone: Step 3.0 (Finish) Turn off bulkcopy ... 2008-11-23 19:13:05 s60b_rpd_standalone: Bulkcopy option has been turned off. 2008-11-23 19:13:05 s60b_rpd_standalone: Step 3.0 (Finish) Update compat_id_s to 60b.2162c.4 ... 2008-11-23 19:13:05 s60b_rpd_standalone: 3 task groups selected for this procedure 2008-11-23 19:13:05 s60b_rpd_standalone: 6 items attempted in this procedure 2008-11-23 19:13:05 s60b_rpd_standalone: 0 item failures recorded in this procedure 2008-11-23 19:13:06 s60b_rpd_standalone: End
The script is designed to tolerate being run on a database which does not contain the erroneous rpd.batch_num_s, such as one which converted without error because the rpd table was empty, or one which has already been patched with this procedure.
This issue has been fixed in version 6.0b, build 6.01.2699 and version 6.1a, build 6.10.2906.
Vertex SEQMAST File Discrepancy
Heat Ticket 524705
This issue pertains only to users on LeasePak 6.0a, 6.0b, or 6.1a builds prior to the indicated builds where NetSol has corrected this issue.
This issue has been fixed in versions:
- 6.0a, build 6.00.2271
- 6.0b, build 6.01.2690
- 6.1a, build 6.10.2905
Users who have not yet upgraded their production database to 6.0a, 6.0b, or 6.1a should use the latest builds to avoid this issue.
If this issue pertains to your current installation, request and upgrade to the appropriate LeasePak build on your server.
Description of issue:
Vertex SEQMAST file is including the county district tax twice if a city has a district tax and its county also has a district tax. As a result, Leasepak location table is overstating the county district tax twice, once in the county code, and then again in the city code for the county district tax.
Although Vertex are aware of this issue, they have stated that they will not include any future fixes related to the Sales Tax L Series.
Because of Vertex's decision not to make any future changes to the L Series, Netsol has decided to modify the LeasePak Vertex Interface program to delete the county district tax from the city's tax rate.
For example (from the SEQMAST file):
Contra Costa county: Use Tax rate = 2.0, District Tax = 1.0
El Cerrito: Use Tax rate = 1.5, District Tax = 1.5
We will update the El Cerrito, tax rate so that it is 0.5 since the county has 1.0 at the district tax level and it is charging 2.0 already at the county level today.
This issue has been fixed in versions:
- 6.0a, build 6.00.2271
- 6.0b, build 6.01.2690
- 6.1a, build 6.10.2905
"pstack" Installation Note for LeasePak Users on Red Hat Linux
Users of Red Hat Linux must insure that the "pstack" rpm from Red Hat is installed on their systems running the LeasePak server images. The pstack executable must be located in /usr/bin, /bin or /usr/local/bin. This program is vital to provide program stack traces when a LeasePak server error occurs; a stack trace is important for NetSol to understand the cause of a server error. If you need help determining whether you have this package installed or need help installing it, please contact Help Desk ([email protected]).
Vertex Interim Update 313.01
The following is a notice from Vertex Inc. for all users of Vertex Sales Tax L Series, which includes all those who use the Vertex functionality in LeasePak 6.1a:
Dear Vertex Sales Tax L Series Customer:
We are notifying you about a potential problem with Vertex Sales Tax L Series Update #313.00. Due to an error that occurred during the production process, a large number of change indicator flags in the update file were set unnecessarily. While there appears to be no impact on actual tax calculation, the impact of this issue in the near or long term is unknown at this time. Therefore, Update #313 has been replaced with Interim Update #313.01.
We strongly recommend that you apply the Interim Update #313.01 as you would a regular update.
Update 313.01 will be made available as follows:
- Customer Cafe Data Download site for customers who receive updates electronically.
- Customers who receive updates on CD-ROM can submit a support service request online through the Customer Café on the Vertex Web site at https://www.vertexinc.com/CustomerCafe/default.asp?action=login, or call Product Support at 1-800-281-1900, product code 4725, to log your request.
We apologize for any inconvenience this may cause, and we are examining the production process to ensure this does not occur again.
Sincerely,
Michael Russo
Manager
Contact Center
(Vertex Inc.)
20082509.STL
Contact NetSol Help Desk ([email protected]) if you need assistance.
City and County Name Lengths
The maximum length in LeasePak of a city name is 25 characters, and the maximum length of a county name is 34 characters. The city names are stored in the rnm and mlo_city tables, and the county names in the rnm and mlo_county tables.
Due to a discrepancy in the rnm and rlo triggers prior to v61a, the triggers did not copy the full length of the city and county names to the mlo_city and mlo_county tables. The triggers have been modified in v61a to update the mlo_city and mlo_county tables with the full length of the city/county names. As part of the v61a conversion, the mlo_city and mlo_county tables will be automatically rebuilt to restore the full city and county names.
In prior releases, the Location Update [U0701] allowed the entry of city names with up to 32 characters, 7 over the LeasePak maximum of 25 characters. In v61a the Location Update [U0701] has been modified to allow a maximum of 25 characters for the city name. The v61a conversion will print a report of the city names in the rnm table that exceed 25 characters. After the conversion, the user should examine the report and run the Location Update [U0701] to rename the cities (if any) which have lengths greater than 25 characters.
Linux: Permanent Note
My.sql /usr/bin/isql
Linux users: RedHat installs My.sql by default, including the executable /usr/bin/isql. Shell scripts naturally find
/usr/bin before finding the correct Sybase path. This will cause errors in any LeasePak shell script using isql.
Allowing a default installation of My.sql on a LeasePak server is inherently incompatible with the operation of Sybase.
NetSol strongly recommmends not installing My.sql on the LeasePak server. Where My.sql is installed alongside Sybase, users must remove,
rename, or relocate /usr/bin/isql so that LeasePak shell scripts will not find it when searching for the Sybase isql.
Additional Database Size Requirments for Asset Focus Module
Users adding Asset Focus assets or converting assets to Asset Focus will need approximately 3 K additional space per Asset Focus asset in the LeasePak database. Most of the additional space needed is used by the LeasePak reqp Asset Payment Schedule and rqr Asset Receivable database tables. The 3 K average will vary by the complexity of asset payment schedules.
Enhancement Summaries
- 517580 Client Based Billing
- Requires the optional module. Provides lessee-level assessment functionality, independent from lease or asset-level assessments, allowing users to assess fees to lessees that do not have leases or loans. User can set up to 3 lessee-level assessments through Assessment Customizations [U0212].
- 517587 EOP Suite III
- Provides additonal functionality to EOP Suite, which automates the submission of End of Period and assists the administrator
in monitoring the EOP process, whether from a terminal logged on the LeasePak server or from a LeasePak client computer.
- 518892 Add IDR2/IDR4 to Sales Tax on Assessments
- Adds IDR2 Registration Fee and IDR4 Opening Commission to the list of assessments
users can select or deselect through U0725 Sales Tax on Assessments.
- 519271 Like-Kind Exchange
- Requires the optional module. Provides the client with LeasePak update functionality supporting Like-Kind Exchange,
which is a method of replacing one asset with another of the same type in order to defer
tax gain or loss, per Section 1031 of the IRS code. Users can refer to IRS Publication 544
Sales and Other Dispositions of Assets and IRS Form 8824 Like-Kind Exchanges for
more information.
- 519335 Addition of Check Number Field to U0103 Payoff Group
- Adds the Check Number field to the appropriate updates within the U0103 Payoff group
and has LeasePak record the check number to the database rtx Monthly Transaction
table during the processing of the update.
- Affected U0103 updates include:
- Payoff (asset-level and lease-level)
- Sale of Asset in Inventory
- Termination (asset-level and lease-level)
- The check number field will appear in the same location on these screens as it
would for Cash Control.
- In the case Sale of Asset in Inventory, where even users with Cash Control do not
currently have a check number field, the developer can determine the best place to
put the check number.
- If the user inputs a suspense number, the check number will be filled in from the
suspense transaction and cannot be edited.
- As long as the payoff/sale/termination amount received is greater than 0, when the
user processes an asset or lease through one of these updates, the program will
save the check number (along with the rest of the appropriate transaction records)
to the LeasePak database column rtx.chk_num_s.
- From there, the check number will appear on R0411 Cash Receipts Journal, as
well as any other reports that include the check number.
- 519355 User Defined Fields Edit Check Enhancement
- Provides new fixed-decimal edit checks for user-defined fields and table columns setup,
as well as new input/display masks for the existing date ('D') and dollar amount ('$') edit
checks, making them easier to use.
- 519360 Maintenance for Inactive Leases
- Gives users the ability to update and modify U0202 Master Financial information on
inactive leases that have been either paid off or charged off (lease status 'NP**' or
'NC**'); includes the option to update lease, historical lease, and application tables with a
new lessee number; and provides users a new Client Search feature that will list all lessees
associated with a customer.
- 520256 Unused Funds Fee
- Requires Client Based Billing module. Allows users to assess a fee to unused credit line balances.
- 520390 Multi-Process LeasePak Utility 232: Master G/L Reconciliation
- Requires the optional High Volume module. Provides the client with multi-processing/multi-threading for running the U0460 Master
G/L Reconciliation through LeasePak Utility 232 Master G/L Reconciliation Report.
- 520899 Confidential Information Display Mask
- Provides the client with a display mask that will prevent unauthorized users from:
- Seeing all or part of the Social Security/Business ID (taxpayer ID) number whenever it appears in LeasePak updates or reports.
- Modifying any part of the Social Security/Business ID (taxpayer ID) number in LeasePak updates.
- Seeing all or part of the PAP Inst ID (bank routing), the PAP Account, the ACH Transit ID (bank routing), or the ACH Account number whenever it appears in LeasePak updates or reports.
- Modifying any part of the PAP Inst ID (bank routing), the PAP Account, the ACH Transit ID (bank routing), or the ACH Account number in LeasePak updates.
- 523281 Additional Fields for Web Services API (LinkIT)
- Requires the optional AcquireIT/LinkIT module.
Provide additional supported fields for the LinkIT Web services's MsiAppOriginator and MsiAppExtractor.
LeasePak Database Changes
ras: EOP Accrual System
- 517580 Client Based Billing
- Requires the optional module. Provides lessee-level assessment functionality, independent from lease or asset-level assessments, allowing users to assess fees to lessees that do not have leases or loans. User can set up to 3 lessee-level assessments through Assessment Customizations [U0212].
- 517587 EOP Suite III
- Provides additonal functionality to EOP Suite, which automates the submission of End of Period and assists the administrator in monitoring the EOP process, whether from a terminal logged on the LeasePak server or from a LeasePak client computer.
- 518892 Add IDR2/IDR4 to Sales Tax on Assessments
- Adds IDR2 Registration Fee and IDR4 Opening Commission to the list of assessments users can select or deselect through U0725 Sales Tax on Assessments.
- 519271 Like-Kind Exchange
- Requires the optional module. Provides the client with LeasePak update functionality supporting Like-Kind Exchange, which is a method of replacing one asset with another of the same type in order to defer tax gain or loss, per Section 1031 of the IRS code. Users can refer to IRS Publication 544 Sales and Other Dispositions of Assets and IRS Form 8824 Like-Kind Exchanges for more information.
- 519335 Addition of Check Number Field to U0103 Payoff Group
- Adds the Check Number field to the appropriate updates within the U0103 Payoff group
and has LeasePak record the check number to the database rtx Monthly Transaction
table during the processing of the update.
- Affected U0103 updates include:
- Payoff (asset-level and lease-level)
- Sale of Asset in Inventory
- Termination (asset-level and lease-level)
- The check number field will appear in the same location on these screens as it would for Cash Control.
- In the case Sale of Asset in Inventory, where even users with Cash Control do not currently have a check number field, the developer can determine the best place to put the check number.
- If the user inputs a suspense number, the check number will be filled in from the suspense transaction and cannot be edited.
- As long as the payoff/sale/termination amount received is greater than 0, when the user processes an asset or lease through one of these updates, the program will save the check number (along with the rest of the appropriate transaction records) to the LeasePak database column rtx.chk_num_s.
- From there, the check number will appear on R0411 Cash Receipts Journal, as well as any other reports that include the check number.
- Affected U0103 updates include:
- 519355 User Defined Fields Edit Check Enhancement
- Provides new fixed-decimal edit checks for user-defined fields and table columns setup, as well as new input/display masks for the existing date ('D') and dollar amount ('$') edit checks, making them easier to use.
- 519360 Maintenance for Inactive Leases
- Gives users the ability to update and modify U0202 Master Financial information on inactive leases that have been either paid off or charged off (lease status 'NP**' or 'NC**'); includes the option to update lease, historical lease, and application tables with a new lessee number; and provides users a new Client Search feature that will list all lessees associated with a customer.
- 520256 Unused Funds Fee
- Requires Client Based Billing module. Allows users to assess a fee to unused credit line balances.
- 520390 Multi-Process LeasePak Utility 232: Master G/L Reconciliation
- Requires the optional High Volume module. Provides the client with multi-processing/multi-threading for running the U0460 Master G/L Reconciliation through LeasePak Utility 232 Master G/L Reconciliation Report.
- 520899 Confidential Information Display Mask
- Provides the client with a display mask that will prevent unauthorized users from:
- Seeing all or part of the Social Security/Business ID (taxpayer ID) number whenever it appears in LeasePak updates or reports.
- Modifying any part of the Social Security/Business ID (taxpayer ID) number in LeasePak updates.
- Seeing all or part of the PAP Inst ID (bank routing), the PAP Account, the ACH Transit ID (bank routing), or the ACH Account number whenever it appears in LeasePak updates or reports.
- Modifying any part of the PAP Inst ID (bank routing), the PAP Account, the ACH Transit ID (bank routing), or the ACH Account number in LeasePak updates.
- 523281 Additional Fields for Web Services API (LinkIT)
- Requires the optional AcquireIT/LinkIT module. Provide additional supported fields for the LinkIT Web services's MsiAppOriginator and MsiAppExtractor.
LeasePak Database Changes
ras: EOP Accrual System
ras: EOP Accrual System
| Column Name | Description | Type Info | Initial Value |
|---|---|---|---|
| d_prev_cmplt_day_s | Day of previous EOD completion | date | NULL |
| t_prev_cmplt_day_s | Time of previous EOD completion | char/6 | NULL |
req: Asset 2
| Column Name | Description | Type Info | Initial Value |
|---|---|---|---|
| payoff_fee_ltd_d | Payoff/termination fee/penalty L-T-D | double/8.2 | 0.0 |
| d_taxbasis_s | Date of last tax depreciation basis update | date | NULL |
| opr_taxbasis_s | Operator who last updated tax depreciation basis | char/3 | NULL |
| lse_act_at_payoff_s | Lease activity status at payoff/termination (ACT code) | char/4 | NULL |
res: Equity Movement Status
| Column Name | Description | Type Info | Initial Value |
|---|---|---|---|
| inven_d | Inventoried value | double/8.2 | -1.0 |
rpay: Portfolio
| Column Name | Description | Type Info | Initial Value |
|---|---|---|---|
| unused_fee_assmt_code_s | Unused drawdown fee assessment code | char/4 | NULL |
rsc: Operator Security
| Column Name | Description | Type Info | Initial Value |
|---|---|---|---|
| ss_disp_mask_s | Mask type to apply to SSN/Business ID numbers (DISP.MASK code) | char/4 | 'ALL ' |
| pap_disp_mask_s | Mask type to apply to PAP/ACH transit ids and account numbers (DISP.MASK code) | char/4 | 'ALL ' |
rhi: Historical Monthly Interest Income for Lease
NEW TABLE
| Table Name | Description | Notes |
|---|---|---|
| rhi | Historical Monthly Interest Income for Lease |
| Index Name | Pieces | Description |
|---|---|---|
| rhi_idx0 | lse_s, ext_num_s, d_acc_s | Clustered, Unique, No Changes |
| Column Name | Description | Type Info | Initial Value |
|---|---|---|---|
| ext_num_s | Extension | char/2 | |
| lse_s | Lease | char/10 | |
| d_acc_s | Accrued to date | date | |
| timestamp | Record modification stamp | timestamp | |
| mth_int_d | Monthly interest amount | double/8.2 |
rlk: Like-Kind-Exchange
NEW TABLE
| Table Name | Description | Notes |
|---|---|---|
| rlk | Like-Kind-Exchange |
| Index Name | Pieces | Description |
|---|---|---|
| rlk_idx0 | exchange_id_s, relinq_unit_s | Clustered, Unique, No Changes |
| rlk_idx1 | relinq_lse_s, exchange_id_s, relinq_unit_s | Unique, No Changes |
| Column Name | Description | Type Info | Initial Value |
|---|---|---|---|
| exchange_id_s | Exchange ID | char/20 | |
| relinq_unit_s | Relinquished asset | char/10 | |
| relinq_lse_s | Lease of relinquished asset | char/10 | |
| timestamp | Record modification stamp | timestamp | |
| d_relinq_s | Relinquishment date | date | |
| d_ident_s | Identification date | date | |
| d_ent_s | Date entered | date | |
| d_last_s | Date of last update | date | |
| relinq_naics_s | NAICS for relinquished asset | char/6 | |
| replace_unit_s | Replacement asset | char/10 | |
| replace_lse_s | Lease of replacement asset | char/10 | |
| replace_naics_s | NAICS for replacement asset | char/6 | |
| exchange_stat_s | Exchange status | char/4 | |
| comment_s | Exchange comment | char/80 | |
| dfrd_gain_d | Deferred gain | double/8.2 | |
| pro_sale_d | Proceeds of sale | double/8.2 |
rmi: Monthly Interest Income
NEW TABLE
| Table Name | Description | Notes |
|---|---|---|
| rmi | Monthly Interest Income |
| Index Name | Pieces | Description |
|---|---|---|
| rmi_idx0 | lse_s, d_accs_s | Clustered, Unique, No Changes |
| Column Name | Description | Type Info | Initial Value |
|---|---|---|---|
| lse_s | Lease | char/10 | |
| d_acc_s | Accrued to date | date | |
| timestamp | Record modification stamp | timestamp | |
| mth_int_d | Monthly interest amount | double/8.2 |
rnm: Name
| Column Name | Description | Type Info | Initial Value |
|---|---|---|---|
| mm_key_s | Name key for each Name code: |
char/9 | n/c |
| nam_s | Name for each Name code |
char/36 | n/c |
rcc: Custom Codes
| rcc_flg_c | cd_type_s | cd_shrt_s | cd_long_s | security_1 |
|---|---|---|---|---|
| 1 | LKE.STAT | LIKE-KIND EXCH STAT | 7 | |
| 2 | LKE.STAT | UNMT | UNMATCHED | 0 |
| 2 | LKE.STAT | PRMT | PRELIMINARY MATCH | 0 |
| 2 | LKE.STAT | MTCH | MATCHEC (FINAL) | 0 |
| 2 | LKE.STAT | NLKE | NOT LIKE (FAILED) | 0 |
| 1 | DISP.MASK | DISPLAY MASK | 0 | |
| 2 | DISP.MASK | ALL | DISPLAY/ALLOW ALL | 0 |
| 2 | DISP.MASK | LST4 | DISPLAY ALLOW LAST 4 | 0 |
| 2 | DISP.MASK | NONE | DISPLAY ALLOW NONE | 0 |
LeasePak Documentation Suite
©
by NetSol Technologies Inc. All rights reserved.
The information contained in this document is the property of NetSol Technologies Inc. Use of the information contained herein is restricted. Conditions of use are subject to change without notice. NetSol Technologies Inc. assumes no liability for any inaccuracy that may appear in this document; the contents of this document do not constitute a promise or warranty. The software described in this document is furnished under license and may be used or copied only in accordance with the terms of said license. Unauthorized use, alteration, or reproduction of this document without the written consent of NetSol Technologies Inc. is prohibited.