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 Shop by Site Changes in LN 10.7

The Job Shop by Site parameter has been added to the Implemented Software Components (tccom0100s000) session. If this parameter is activated, multisite production for job shop is enabled.

Almost all new planning and production functionality in LN depends on the activation of this parameter.

Previous Article Have you seen what’s new with Infor LX 8.4?
Next Article Infor LN Extensibility Methodology for Cloud and On Premise
Print
46880 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

Automatically synchronize security changes from LX to IDF, replacing CPYSECIDF. This new process synchronizes users in IDF with those in core LX security whenever a user’s security settings are changed. When a user is deleted from an LX environment, they can also be automatically removed from the IDF environment. Changes to a user’s access to programs in LX are mirrored in IDF. Access to Companies, Facilities, and Warehouses are also synchronized. Additionally, when Business Roles or Business Units access is changed, all users assigned to those roles or units are updated in IDF security.

In the Shop Order Selection program, action 3=Copy is available. This action allows copying any shop order except for flow orders or campaign orders. Instead of copying from the parent item's bill of material and routing, the new shop order’s materials and operations will be copied from the selected shop order. Note that if the existing shop order is linked to a customer order or line, this linkage will not be copied to the new shop order.

First34568101112Last

Theme picker

Tips: LN | Baan

Instead of sharing tables through logical linking, you can replicate table content between companies. This approach allows certain non-key attributes of a record to vary by company. For example, if you replicate bills of materials rather than sharing them, each company can associate a different warehouse with the same bill of material. This way, the bills of materials are consistent across companies, while the warehouses can differ.

Replication also enables selective availability of records in other companies. For instance, when replicating items, you might limit which items are available in a sales company based on their item group, only including end items. You can further refine replication to specific subsets, such as particular item groups.

Keep in mind that replication requires any referenced tables to be either replicated or shared as well.

123456810Last

Theme picker

Categories