GL190 Job schedule

Can someone provide an example of how they are running their GL190 job on a daily basis? How many periods, etc. Thank you!

Find more posts tagged with

Infor Lawson Financials Group - Discussion

Comments

Legacy Contributor

We schedule as a batch job to run at 4am and then again at 7pm for most of the month. During month-end close (+1 through +4 working day) we add an additional run at mid-day and after that (+4 through +6 working day of month-end close) we do ad-hoc postings in between our allocations jobs. For the most part, we are running for the current period and during month-end close, it is for the period we are closing but update the 4 am on +4 to run only for the new period. The first time it runs, it will run long since it hasn't run for the new period for a few days. Once the old period is in limited close, all posting jobs post for the new current period.

Tammy Law Waters

Fiscal Year C

Period 10

Posting Date 9/30/2017

Legacy Contributor

We run multiple jobs every night: current year per 1, CY per2, CY per3... thru CY per 12, and then we run next year per1 and next year per2 so that future entries are posted when the GL is in period 11 or 12. Users also run this job on demand (usually current year, current period) as needed during the day.

Legacy Contributor

Ok that sounds like the route we will be going. We were told to schedule it sequentially to run CY per1 - 12 to run every night. Hadn't thought about the Next year P1 and P2 though so will need to incorporate those as well. Do you run this through a Multi-Step job definition or through IPA?

0911060553270289.pdf

Legacy Contributor

We have one daily GL190 that runs overnight for the current period. It is part of a multi-step job that loads non-Lawson files into the system, then the GL190 will post all of those along with entries from all Lawson subsystems that were interfaced in during the day. We come in the next morning and "balance", or verify, the results of the GL190 - compare actuals to expected totals, confirm there were no errors, etc.

For anything other than that - during period close, for example, when we need entries posted during the day, we have one person who manages any non-scheduled GL190s, just to make sure we are coordinating everything that needs posted and to ensure that we are running only one GL190 at a time.

Legacy Contributor

It's a multi-step job def that also runs MA126, AP175, CB175 and AP109.

Legacy Contributor

fyi - Our setup on GL01.2 is that only 2 periods can be open at any given time for GL system code. This is why our GL190's are set up the way they are.

Legacy Contributor

So how do you run jobs through Ming.le that require variable dates? Such as the CB175 which wants a Post Through Date but this date will need to change daily.

Legacy Contributor

We bypass Ming.le right now. Our IT staff developed some jobs to update the parameters and some are manually changed using a custom form. The form will only show the fields that can and should be manually updated. The jobs that change parameters are scheduled to run just prior to the job or scheduled to run earlier in the day. We use single-threaded job queues to submit jobs or schedule jobs that need to run in sequence. Across our enterprise, this work is centralized and maintained by one team so no chance of running into other job submissions.

Legacy Contributor

Our CB175 is set up to post everything through 12/31/19... same for AP175.

Copyright © 2025 Infor. All rights reserved.