Interfacing lease payment schedules

Use this procedure to import non-Lawson lease payment schedules into the Lease Management application and convert them to unreleased Lawson payments accessible through Payment Schedule (LM30.1).

You must interface leases before you can interface their associated lease payments. The lease and non-lease components (if applicable) must already exist in the Lease Management application. You must also set up your payment vendor in the Accounts Payable application. In addition, if you define an authority code, process level, handling code, or accrual code, then they must exist in the Accounts Payable application. If you specify a compute name, as well as a General Ledger company and range of accounts from which the compute name draws its data, then they must exist in the General Ledger application.

  1. Prepare the non-Lawson lease payment file. The file must be in an importable format such as a comma-separated value (CSV) file and the file fields must match the order, size, and file type of the fields in the LMPAYCNV (Unix/Windows) DBLMPCN (IBM i) interface file.
    Note: The Financial Management file layouts for LMPAYCNV (Unix/Windows) DBLMPCN (IBM i) are available in KB2218730 in Infor Customer Portal. See your Lawson representative for more information. Consider this very important field in your non-Lawson file.
    HISTORY-FL

    The history flag determines whether the payment is historical (fully processed already) or is yet to be processed. This is the only place where you can make this determination. All interfaced payment records that have the HISTORY-FL field set to Yes display in Historical Pmt Schedule Interface Adjustment (LM51.4). Although they can be adjusted, their historical status cannot be changed.

  2. Transfer the non-Lawson file to the machine running your Lawson environment.

    Unix/Windows:

    You can use a standard transfer utility such as ftp or the Lawson program winptxfr. You may have to rename the file to match your machine's requirements. For example, to transfer file cnvleasepmt.csv on your c: drive to a Unix machine and rename it cnvlsepmt, use this command:

    winptxfr -u cnvlsepmt c:\\ pathname \\cnvleasepmt.csv

  3. Load the transferred file into the LMPAYCNV (Unix/Windows) DBLMPCN (IBM i) file, using this command from your Lawson environment prompt:

    importdb productline LMPAYCNV filename

    where filename is the name of the non-Lawson attribute value file transferred to your machine in step 2.

  4. View and edit the unprocessed lease payment schedule records in LMPAYCNV (Unix/Windows) DBLMPCN (IBM i), using Payment Schedule Interface Adjust (LM51.1).
    1. Review and edit the header portion of the payment schedule.
      Run Group; Company, Lease; Payment Vendor

      These fields are required to identify a specific lease payment.

      Straight Line

      Select Yes in the Straight-line Payments field to indicate that you will record straight-line payments.

      Straight Line Amount

      Specify a straight line amount override value. The lease must be unreleased to changed the calculated straight line amount.

      Misc button

      Click this button to open the Miscellaneous Payment Interface Schedule (LM51.2) and edit or select a process level, accrual code, handling code, or AP vendor location. Accounts Payable will use these values when processing lease invoice payments.

      Historical button

      Click this button to open the Historical Payment Schedule Interface Adjustment (LM51.4) and view or adjust interfaced historical payments that have already been processed

    2. Review and edit the detail portion of the payment schedule.
      Payment

      The payment number is required.

      Note: If your payment includes non-lease components, then assign the same payment number to the regular payment and to the non-lease component payment. You can have more than one line of non-lease component payments; each must have the same payment number as the payment it is processed with.
      Exec Code

      If this payment line is for an non-lease component payment, then select one of the non-lease components that you assigned to the lease.

      Auth

      The Lease Management application requires approved invoices before they are released and interfaced to the Accounts Payable system. This is one of the forms where you can assign an authority code. You have other opportunities to assign an authority code during invoice processing.

      Due

      The payment due date is required. You can modify it.

      Payment Amount, Compute

      One of these fields is required. If you do not specify a payment amount, then you must specify a compute name representing a formula that will compute the payment amount. If you specify both a payment amount and a compute name, then the payment will be the sum of the amounts derived from both fields.

      If you use a compute name, then you must also click More to open Payment Interface Adjustment (LM51.2) and indicate the source of the data used by the compute name.

      Note: You can adjust any of the fields on the payment line, but you cannot change the historical status of the payments.
  5. Click Historical to open Historical Payment Schedule Interface Adjustment (LM51.4) and edit already processed payments.
  6. Run Payment Schedule Interface (LM551) to interface the lease payment records into the Lease Management application. All the fields are optional. You can run the program for all run groups, one run group, or one run group and company.
    Update

    It is recommended that you run LM551 with the N (Report Only) option first to generate a report of the lease records interfaced by this program, as well as an error report, before you actually interface the records using the Yes option in the Update field.

    Note: LM551 identifies data incompatibility errors and does not allow you to interface leases containing errors such as wrong company number or non-lease component, or wrong data type in a field. But it does not prevent you from interfacing leases that contain no data incompatibilities but may still contain data entry or other errors. This is why the Report Only option may save you from rework.
  7. View the report generated by LM551. If it contains errors:
    1. Correct the records, using LM51.1 or LM51.4.
    2. Run LM551.
    3. Repeat steps 4 to 6 until the report shows no errors.
Related topics