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

Enterprise General Ledger (EGL) provides audit attributes to track journal entry changes and approvals.

To implement this enhancement, you can request and apply MR 81026.

This enhancement provides audit attributes for the last maintained user, date, time, and approval user, and date, and time on the Financial Journal Entry and Financial Journal Entry Lines. This audit function provides visibility to who and when the journal was last maintained and to who and when the journal was approved.

The programs or areas impacted include:

  • Financial Event
  • Financial Journal Entry
  • Financial Journal Entry Line
  • Financial Journal Entry Detail Line
  • Post Multiple Events

Did you know CLD provides you with the following benefits?

▪ You can journalize and post-transaction data from any third-party application or Infor LX subsystem to the Configurable Ledger (CLD).

▪ You can generate multiple journal entries across different charts of accounts, ledgers, and books within the CLD from one transaction line.

▪ You can automatically post transaction amounts across different books using an appropriate exchange rate between the batch transaction currency and target book currency.

▪ You can use validation reports to identify validation errors within the files that contain batch transaction data and then you can make any necessary corrections before resubmission.

▪ You can use standard CEA grouping and summarization options for journals created during Batch Transaction Processing.

▪ You can interface GLD journal entries into CEA for the BPCD version of Infor LX. This allows data to be interfaced into CEA without changing the way data is processed through Infor LX subsystems.

FirstLast

Tips: LN | Baan

Categories