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

Infor LN & Baan Tips & Tricks for TECHNOLOGY: Data Sharing Methods (Advantages and Disadvantages)

Depending on the multicompany scenario you choose, an implementation team must decide whether or not tables must be logically linked or if data must be synchronized in another way to achieve availability of data across various companies. 

There are 3 ways in which data may be shared among companies. Here are some advantages and disadvantages of each:

  1. Logical Table Linking - If two companies use the same physical data, the physical table exists, or is used, in only one company: the physical company. Each piece occurs only once: one instance of the same data. If the term logical table linking is used, users from multiple companies use a single physical instance of the data. If the company tables are on the same server, this can be accomplished by logical table linking. Access to specific data can be restricted, if required.

    • Advantages: Logical Table Linking takes place in real time; therefore, the moment a record is created or modified in one company, a record becomes available in all other linked companies as well. The setup and maintenance of logical table linking is easier than the setup and maintenance of data replication. Logical table linking is extremely reliable because this type of linking is independent of network connections and user interventions. 

    • Disadvantages: Table sharing implies that all attributes for a record are the same in all companies. Therefore, suppose you share the item table and, for a particular item in a company, the product class is XXX. In this case, in all other companies, the product class for this item must be XXX as well.

  2. Data Replication - In this situation, each company has exactly the same data, but each company has a unique copy of the data. The same piece of data exists in multiple (physical) places: multiple instances of the same data. The process to copy the data is called data replication.

    • Advantages: Rather than using table sharing by means of the logical linking of tables, you can replicate the content of tables between companies. The advantage is that, on company level, some (non-key) attributes of a record can differ by company. For example, if the bills of materials are replicated instead of shared, for each company, you can link a different warehouse to the bill of material. As a result, the bills of materials can be the same across all companies and only the warehouses differ. Using replication, you can also make only a subset of the records available in other companies. For example, if you replicate items between companies, in a sales company, for example, by means of the item group, you can only make end items available. In addition, you can replicate only a subset of items, for example, depending on the item group. Note that replication also requires that the referenced tables are replicated or shared.

    • Disadvantages: Replication is not in real time, and therefore, for processes that require real-time integrated data as the financial integration processes, replication is not an option. For replication, you also must take into account the sequence in which you replicate. First, you must replicate the child tables and then the parent tables, and therefore first the business partners and then the purchase contracts. During the replication process, the data must be frozen. This point is of particular importance if the replication process takes a lot of time.

  3. Manual Syncronization - If only a small number of records are the same between some companies, you can enter, maintain, and keep the records synchronized manually. Note that the more dynamic data is, the more difficult this process is. This solution is strictly procedural. Therefore, depending on the discipline of the users, the solution is error sensitive: data can be forgotten, updated too late, or typing errors may occur.

  • Advantages - The main advantage is the flexibility so that only the data that really must be shared can be kept synchronized. By manually keeping data synchronized, not all attributes of a record need to have the same value.

  • Disadvantages - The main disadvantage is that this method depends on user interaction. Therefore, the method depends on the user’s time - because the method is not a real time procedure and the user may forget to update the data - and users can make mistakes.

Previous Article Infor News You Can Use: Using AI to Stay Ahead of Customer Demands
Next Article Infor LN & Baan Tips & Tricks for FINANCE: Cash Flow Statements (tfgld 0123m100)
Print
33704 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

EGLi provides Infor LX Configurable Enterprise Accounting (CEA) functionality including Advanced Transaction Processing (ATP), a configurable ledger, and batch transaction processing in the IDF architecture.

EGLi is a complete replacement for CEA. Infor LX applications integrate with EGLi, and subsystem transactions generated in Infor LX are used to create journal entries in EGLi. The Infor LX integration system parameters allow you to specify whether CEA or EGLi is your primary financial product.

We recommend that you select CEA while you test the integration. The primary financial product flag and the CEA migration programs are designed to assist existing CEA clients with their implementation of EGLi. Journals are produced in both GL systems so you can verify that the data in both GL systems are the same. This integration includes migration programs that copy your existing CEA files to corresponding EGLi files. After you run the migration programs, EGLi should be configured and ready to use. If you are already running IDF via Ming.le or SiW, before you install EGLi, you will need to see the Ming.le integration guide for instructions on how to export EGLi tasks from IDF to SiW/Ming.le.

Learn More > Infor LX Integration Guide for Enterprise General Ledger

  • Control Date Lead Times – LX provides five separate Control Date Lead Time fields so you can specify additional lead time values for Shop Orders, Purchase Orders and Planned and Firm Planned orders. Each Control Lead Time Date represents additional time (days) required at each step in the process that needs more time (Quarantine, Stabilize), that is to say, when a component is due, and when it can be used. (working with an aerospace  precision bearing manufacturer, I had to account for the QA requirement that no measurements could be taken until the parts had been “soaked” (stored) in an atmospheric controlled environment (72 degrees, and controlled humidity) for 24 hours. This requirement added one full day of lead time between each machining operation) The MPS/MRP Generation program, as well as programs that Shop Order Material Allocation records use the five control date lead times to adjust component required dates to function in the same way as the BOM Offset Lead Time.
     
  • All programs that create MRP Planned Orders, MRP Firm Planned Orders, Shop Orders, and Purchase Orders call the Control Date Calculation program (MRP515B) to establish all five control dates. A Control Lead Time Date is used to adjust the component Required Dates data in the Material Requirements file (KMR), based on planned orders for a parent, and the FMA Required Dates data, based on shop order release dates for a parent.
FirstLast

Tips: LN | Baan

Categories