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

Baan/LN Tip of the Week: ERP Setup - Pros & Cons

You may have started your setup of your ERP system one way, and have discovered over time that maybe it no longer fits how you need to do business. Over the next few weeks, I’ll be providing some pros/cons to consider for different company setups.

Pros/Cons of Single Finance / Single Logistic Company Set-Up

Pros
Easy to implement and to maintain.
No risk of processing data for another company.
Data not visible across companies – pro if you do not want users to see other company’s data.
Cost Prices can be different for the same item in the different logistics companies.
Easy to add or remove companies when companies are bought or sold.
Accounting functions are all separate by company. – Pro if each finance company is managed separately.

 

Cons
Decentralized operations – purchasing, sales, manufacturing, planning, warehousing, etc.
User must go in and out of companies if there is a need to view or create transactions in more than one company.
Data not visible across companies – con if you do want users to see other company’s data.
 
Must set up routings and BOM’s separately for each site.
 
Accounting functions are all separate by company – Con if both finance companies need to be managed together, although centralized payments, cash receipt application, and display and printing of ledger transactions and trial balances are possible for both companies if both are linked to the same financial group company.
Previous Article 6 Manufacturing Trends to Watch Out for in 2016
Next Article BPCS/LX Tip of the Week: Getting the Most Out of the Shop Order Inquiry Program – Part 1
Print
47712 Rate this article:
No rating
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

This feature provides the ability to enter information in the shelf life days and retest days fields for non-QMS lot controlled items, even when the QMS product is installed. The purpose of this enhancement is to allow the user to enter information for non-QMS lot controlled items even when QMS is activated in Parameters Generation, SYS800D. In previous versions, when QMS was activated, the Shelf Life Days and Retest Days fields in Facility Planning Maintenance (MRP140) and Item Master Maintenance (INV100) were not maintainable for non-QMS lot controlled items. The user is now able to change non-QMS lot controlled items even when a QMS product is installed.

The Facility Period Close process, as introduced in Infor LX 8.3.4, was designed to function interactively. 

The expectation was that clients with a continuous or 24-hour worldwide operation in multiple facilities would submit the Period End Close jobs for each facility as daily operations ceased or shifts ended for each facility. This process was designed to function interactively so that validations of users performing transactions that conflicted with period end processing, and resulting messages, were immediately sent to the period end user. 

This enhancement provides a batch mode for the Facility Period Close (INV930) process and allows the Update IIM Inventory from IWI (INV931) process to be submitted from the INV930B program. The enhancement also provides a batch mode for the INV931 process. For example, a user has a 24-hour operation in facilities around the world, but a centralized IT operation. With this enhancement the user can submit the individual facilities to be closed to a batch process that can be managed by a scheduler, automatically releasing each facility to be closed at a predetermined time.

First6869707173757677Last

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.

12345678910Last

Theme picker

Categories