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

BPCS/LX Tip of the Week: Shop Order Release Date

Anthony Etzel 0 33140 Article rating: No rating

The shop order release date is the date that the shop order is scheduled to be released for production.

If you want to use the backward schedule method, make sure the release date is blank and the due date is maintained.

If you maintain the quantity on the shop order and the due date is prior to the system date, the due date and the release date are the same.

Baan/LN Tip of the Week: Plan Codes

Kathy Barthelt 0 43360 Article rating: No rating

In Baan IV, plan items exist within the context of a plan code. A plan code includes only items of the MPS Item item type. Planned orders are independent of a plan code. Users can compare plan codes by means of the Plan Code Performance Comparison (cprmp4504m000) session.

The scenario concept in Infor LN replaces the plan code concept in Baan IV.

In Infor LN, the basic data for plan items is the same for all scenarios. However, users maintain not only the master plan within a scenario, but the planned orders as well.

For example, for each scenario, Users can specify:

  • Special demand for an item.
  • The availability of resources (in the Scenario – Availabilities (cprpd4160m000) session).
  • The sourcing strategies and supply strategies.

Users can compare scenarios by means of the Performance Indicators (cprao2201s000) session.

Filtec Selects Crossroads RMC for Baan Data Collection

Kathy Barthelt 0 22132 Article rating: No rating

Filtec, a leading provider of in-line inspection solutions for the food, beverage, and pharmaceutical industries, has selected the Web Collect, formerly RMC3 data collection solution from Crossroads RMC for their Baan IV system. Filtec plans to implement Labor Reporting and Report Operations Complete as part of this project with the goal of eliminating manual data entry and gaining better visibility to gap time. The project is scheduled to go live in early November 2015.

RSS
First134135136137139141142143Last

Theme picker

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

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 Infor LN & Baan Tip of the Week: Credit Checks for Business Partners
Next Article Infor LN & Baan Tip of the Week: Customer requested delivery date
Print
37881 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

x

Categories