Non-Lawson Payroll Transaction Processing (GM500)

Run Non-Lawson Payroll Transaction Processing (GM500) to import payroll transactions into Lawson when you process payroll using a non-Lawson payroll system.

Before you run GM500, you must load all transactions related to the payroll run into the Payroll Transaction Import (GMDISTREL) file under the same run group.

Note: To make sure subsequent data imports do not damage any records for which processing may be pending, Lawson recommends you uniquely identify each run group. Suggestions include:

Use a date/time stamp as the run group identifier (for example, use 051604164022 for an import file created on May 15, 2004 at 2:40:22 p.m.)
Use the pay cycle and date (for example, use SEMI051504 for a semi-monthly payroll for the pay period ended May 15, 2004)
Use the company, pay cycle and date

For employees not subject to labor distribution:

When you run GM500, payroll expenses post to the grant activity and General Ledger account (department) in the imported transaction. (This also applies to employees subject to labor distribution but for whom no eligible labor distribution template can be found.)

For employees subject to labor distribution:

GM500 relieves any existing encumbrances for the payroll cycle from and General Ledger, then creates and posts labor distribution transactions for the entire payroll cycle to Lawson General Ledger, , and Grant Management.

Processing Effect

Non-Lawson Payroll Transaction Processing (GM500) performs three phases. Phase 1 occurs when a job is added, changed, or submitted. Phases 2 and 3 occur after the job is submitted. Each phase is contingent upon successful completion of the previous phase.

Phase 1 - batch validation performed when job is added, changed, or submitted.
Phase 2 - data validation and error report.
Phase 3 - labor distribution, salary encumbrance relief, transaction update, and transaction report.