Transaction Interface Maintenance (SL65.1)
Use Transaction Interface Maintenance (SL65.1) to view and maintain journal entry data you are converting from a non-Lawson environment (a spreadsheet, for example) to the Lawson Strategic Ledger application. Use this to verify the information being transferred to the Lawson system.
More information
To transfer the non-Lawson file to the target machine, use a transfer utility program (such as the winptxfr or ftp command). When you transfer the non-Lawson file, you rename the file for use in the Lawson system. For example, if you are transferring from Excel, use
winptxfr -u filename c:\\Data\\Excel\\excelfilename
where filename represents the Lawson file.
Use an import utility, such as importdb (importdb productline SLTRANSREL) (UNIX/WIndows) to load the transactions file into the Strategic Ledger Transaction Interface file (SLTRANSREL (UNIX/WIndows) or DBSLSTR (IBM i)) , where filename is the name you assigned when you transferred the file to the Lawson system. After you run the import, use SL65 to view your data.
You may associate the transaction information in this form with an Organization and Account Code. The organization code identifies the Lawson company and accounting unit where the converted transaction information is stored. The account code identifies the Lawson account and subaccount where converted transaction information is stored. Use Organization Relationship (GL08.1) to define the organization code and Account Relationship (GL09.1) to define the account code.
Run Transaction Interface (SL165) to load the journal entry transaction information from this form into Strategic Ledger.
Run Transaction Interface Listing (SL265) to list transaction records before running SL165.