Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Infor LN & Baan Tip of the Week: Job Groups in LN

In a scenario where performing job A depends on the result of job B, it is hard to decide at what time job A must be scheduled, and how long job B runs. To handle dependent jobs, you can now create a job group. Use the Job Groups (ttaad5140m000) session to create a job group. A job group has a name, with the same characteristics as a job name, and a description. The Status and User of the job group are handled automatically.

After creating the job group, the jobs are added to the group, approximately in the order the jobs must be performed. The first job in the group (with the lowest Group Number) determines the handling of the whole job group, such as execution date and whether the job group is being repeated. If the job group is not repeating, the job group and all non-repeating jobs in the job group are deleted when the job group has run.

The dependencies of the jobs in the job group are also determined. A job in the job group can only depend on a job in the same job group with a lower job number.

You can use the specific options in the Job Groups (ttaad5140m000 andttams5640m000) sessions to change the status of the job group. The job group statuses have the same meaning as the status of the jobs and the same status changes are allowed.

Note: Job groups are only handled by the BSE service Job Scheduler Service.

Previous Article A/P Payment Update in LX 8.3.4
Next Article If you can't see everything that happens on your shop floor, you are at a competitive disadvantage
Print
40640 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

The Cycle Counting Sub-System Within Inventory Management

The system uses the following information as the basis for cycle counting selection:

  • Cycle Counts/Year: The system calculates the time between cycle counts based on your entry in this Item Master file field for each item (optional).
  • Last Cycle Count Date: This date is in the Location Inventory file, ILI, if you use locations, or in the Warehouse Inventory file, IWI, if you don't.

The system adds the time between cycle counts (calculated as described above) to this date. If the result is less than or equal to today's date, the item is selected for cycle counting. If it is greater than today's date, the item is not selected, it is not due yet for cycle counting.

There is another special condition that causes an item to be selected for cycle counting. If the ILI/IWI record of the item has a Y in the Cycle Flag field, the item is selected automatically. This flag indicates that the item's on-hand balance has gone to a negative value sometime since the last cycle count. That applies even if the value is not negative at selection time. The programs that can set this field are INV500D, INV510, and BIL540.

You can also limit the items selected for counting by specifying limits of the item numbers or warehouses to be searched.

First2526272830323334Last

Theme picker

Tips: LN | Baan

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

  • Bank Statement Workbench (tfcmg5610m100)
  • Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

1345678910Last

Theme picker

Categories