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

1. Eliminate paper shop packet and distribution of the paperwork to the shop floor.     

2. Eliminate manual (paper-based) recording activities and the need to key in the transactions.

3. Easy electronic scheduling by sequence and changing job priorities.

4. Evaluate differences using actual times compared to standards.

5. Improve data accuracy and eliminate the need to chase and fix errors.

6. Practice Real-Time data reporting to monitor efficiencies and identify problems as they occur.

If the item being received needs to be inspected prior to being available for use, there are two schools of thought.The first is to receive the item to a QC hold location. The downside is the item will show up in on hand inventory.

A better method would be to do a PO receipt to inspection. Both Inv500 and Pur550 support this method. Now you have received the item without showing it in inventory. Only the PO quantity in inspection is updated. This method also allows you to create an Inspection Dispatch Report. After the QC process for the item is complete, then the transaction Receipt from Inspection to Stock is processed. That transaction then updates the PO quantity received field and the Item on hand field in inventory.

 

First117118119120122124125126Last

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