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

Previously, Material Requirements Planning (MRP) preferred practices meant that the component's due date was the same as the parent's shop order release date. Because MRP trends have changed, the preference for this due date is the day before the release date of the parent. Although Infor LX already has this functionality in Shop Order Maintenance programs (SFC500), users could not change how due dates were determined for lower-level shop orders in Multi-Level Shop Order Release, SFC530D.

This enhancement provides an additional parameter for Multi-Level Shop Order Release. This parameter allows the user to change how the due date of the child components is determined. The Multi-Level Shop Order Release, SFC5302, has a new parameter for shop orders. The Due Date of Children = Release Date of Prent (Due Date of Children) field allows the user to set the due date determined for multi-level shop orders.

This feature uses different exchange rates in the user's inventory processes by using new macros in Post Inventory to G/L, INV920D. INV920 used macros limited by the Override Exchange Rate parameter set on the book in Book Definition, CEA105D3. If the Override Exchange rate parameter is set to No, the macro uses the Rate Type of the Book. If the Override Exchange parameter is set to Yes, the macro uses the Rate Type of the Order Company. This enhancement provides macros that use the Rate Type of the Order Company. This enhancement provides macros that use the Rate Type of the Warehouse Company, Order Company, or the Book regardless of the Override Exchange Rate parameter in the Book.

12345678910Last

Theme picker

Tips: LN | Baan

The planning data for the method of manufacturing is defined in Routing. A routing consists of operations, with each operation identifying the last to be carried out in a work center and/or on a certain machine defined for a specific site.

Routings can be as follows:

  • Standard Routing - A generic routing that can be attached to multiple items
  • Item specific - A routing that is applied to one item
  • Network routing - A routing containing sequentially ordered operations and parallel operations
  • Order quantity dependent routing - A routing that is defined for a specific quantity of items

You use the Routing module to record routings for manufactured items. You can define the following:

To improve performance and reduce database growth, deleting records is highly effective. The disadvantage of deleting records is that data is no longer available. Usually, however, not all records need to be saved. For example, line activities are stored by warehouse. Normally, you do not need to keep these records. Therefore, after closing a warehouse order, line activities can be removed. The User's Guide for ERP LN Archiving and the corresponding Baan IV/V Guides describe several sessions you can use to delete old data. Other data such as items and business partners can be reviewed once in a while, after which you can delete the data you no longer need. For every order and contract table, a session is available to archive and delete old orders. In these sessions, you can specify several characteristics to select the orders to be removed, such as date or status. Run these sessions on a regular basis.

First3536373840424344Last

Theme picker

Categories