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
37917 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

Role-Based Security introduces Role type profiles and allows combining the use of Role profiles with the traditional LX User type security profile functionality. The new Role type profile can be defined to allow or deny access to All Products, Attention Key, Products, Programs, and Transaction Effects. Facility, Warehouse, and Company securities are still defined solely by the User profile settings and are not affected by the assignment of a Role. Where applicable, the Role authority is displayed alongside the User authority on the security profile maintenance screens making it easy to see where there are differences in authority between the User and the assigned Roles. 

When Users are assigned to Roles, security access in LX becomes a combination of authorities granted or denied by the Role, plus any User Exceptions. User Exceptions override authorities set by the Roles. A User can also be assigned to more than one Role.

12345678910Last

Theme picker

Tips: LN | Baan

There has been a recent porting set change due to Infor’s Product Life Cycle Policy.  

How to determine the maintenance stage of an Infor LN product version and release

Before a customer starts deploying Porting Set 9.4a or a later release, they must determine the actual maintenance stage of their Baan / Infor LN product. The definition of the maintenance stages for the product versions and releases of all versions of Baan and Infor LN are outlined in the Product Support schedule as published in the PLC policy. The maintenance stage of the ERP version is either “Mainstream Maintenance”, “Extended Maintenance” or “Sustaining Maintenance”.

How to manage Porting Set updates

The following conditions apply to customers who intend to upgrade to Porting Set 9.4a or later Porting Set releases:

Don’t laugh! I know, I know…many of our customers say that after 7-10 years they are finally settling in after the implementation! We have seen many a customer stretch out the lifespan of their ERP system to 20+ years. That sounds great for the company’s bank account, but is it good for the business?

An outdated ERP system hurts your business in many ways, not just with slow performance. The best-of-breed functionality is now 2 decades old, and obsolete technology can't leverage newer technology. Lack of integration leads to siloed data that hurts communication and your internal teams feel the pain, and your customers are noticing. Poor visibility into your operations makes it nearly impossible to achieve industry-based regulatory compliance and meet financial auditing requirements. Not to mention the sheer size of Big Data that is being collected today vs. 2 decades ago or the fact that your vendor is no longer supporting your ERP version.

Let’s scrap it all and start over!...

First2728293032343536Last

Theme picker

Categories