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

Infor News You Can Use: LN NAUG Face-to-Face Annual Meeting 2025

May 13-15, 2024 | Chicago Marriott - Naperville IL

Kathy Barthelt 0 10913 Article rating: 5.0

We are delighted to invite you to the 2025 Annual LN NAUG Face-to-Face Event —a special premier event for Infor LN and Baan users of North America. This is your chance to connect with fellow users, share experiences, and shape the future.

  • Learn from the Best: Engage with industry leaders and experts through keynote sessions and panel discussions.
  • Increase your Skills: Participate in collaborative breakout sessions to explore available solutions.
  • Network & Connect: Build relationships with other customers, potential collaborators, and industry pioneers.


Register today to claim Early Bird pricing through March 31, 2025.
https://www.lnnaug.org/events/2025-f2f-annual-meeting 

 

Crossroads RMC AI Business Models: Generative AI Using ChatGPT

Crossroads RMC 0 8662 Article rating: 5.0

The Future is Here: Are You Ready to Embrace AI?

According to Deloitte's State of AI in the Enterprise Report:

  • 94% of business leaders believe AI is critical to their success strategy in the next 5 years.
  • 79% of organizations expect Generative AI to transform their operations within 3 years.
  • 56% are already leveraging Generative AI to boost efficiency and productivity.

AI isn’t just the future—it’s happening now. Where is your organization on its AI journey? Whether you're just starting or looking to expand, we’re here to help you take the next step, together.

We’re excited to introduce our latest professional service, Implementing Generative AI Using ChatGPT. This new service is designed to help organizations effectively leverage the power of generative AI in their operations

Key Benefits of Implementing Generative AI Using ChatGPT by Department

It’s Mid-January, and IT’S GO TIME!

Infor LX | BPCS | Infor LN | Baan

Crossroads RMC 0 8232 Article rating: 5.0

The calendar is fresh, the resolutions are set, and the opportunities are endless!

But before you dive headfirst into tackling your to-do list, take a moment.

Pause.

Now is the perfect time to reflect and plan your ERP strategy.

What’s an ERP Strategy?

An ERP strategy is a roadmap for the steps you should take before, during, and after implementing an ERP system. It’s designed to ensure your ERP delivers on its promise of functionality and success—the backbone of running your business effectively.

Think of it like planning a road trip:

  • Which cities will you visit?
  • Where will you stay?
  • What landmarks do you want to explore?

Without a plan, you’re winging it. While spontaneity might work for a vacation, it’s risky when it comes to your ERP system.

A poorly executed road trip might waste time or cause frustration, but a poorly executed ERP strategy? That can hinder your business growth, create inefficiencies, and lead to costly mistakes.

What if:

Infor LN & Baan Tips & Tricks for Finance: Problem Invoices

Kathy Barthelt 0 52957 Article rating: 5.0

You can use a problem code to indicate that a problem exists for a sales invoice. If the invoice-to business partner notifies you about a problem with the invoice and does not pay it, you can link a problem code to the invoice.

In the direct debits procedure, problem invoices are automatically discarded. For each problem code, you can set an option to prevent linked invoices from being selected on reminder letters.

Infor LN & Baan Tips & Tricks for Technology: Using audit files in the Exchange module

Kathy Barthelt 0 50025 Article rating: 5.0

The audit server logs all database actions that change the contents of a table in so-called audit files. The Exchange module can use these audit files, which are useful in a multisite environment because the databases on all sites must have identical data. These audit files can also be used in data conversions.

Only the updates in a specific period are exchanged, which leads to an improvement in performance. Specify this period in the Export Data (Non-Regular) (daxch0233m000) and Export Data (on a Regular Basis) (daxch0234m000) sessions. Changes such as insert, update, and delete are processed and written into the ASCII files. Actions such as drop, clear, and create tables are ignored.

Audit control data is added to the resulting ASCII file. This data consists of a batchline ID, transaction ID, sequence ID, and an indicator. The control data is added at the beginning of each line and is formatted like other data fields such as the enclosing and separator characters.

An update writes two lines to the ASCII file. One line contains the key fields and old values of the updated fields. The other line contains the new values of the key fields and updated fields, even if a key field does not change.

The batchline ID is used for recognition when processing the ASCII files. The transaction and sequence IDs are used to ensure that the transactions are replayed in the same order as on the exporting site. The indicator defines the type of action that is executed on the table. Use the letter I to insert; use the letter D to delete; use the letter U to update with old values; and use the letter N to update with new values.

Infor LN & Baan Tips & Tricks for Operations: Copying EBOMs - Which copying method should I use?

Kathy Barthelt 0 53668 Article rating: 5.0

To determine which copying method you must use, answer question 1 and follow the instructions.

Question 1: Is the source component a project item (that is, is a project defined in the first segment of the item code)?

  • If the answer is yes, proceed with question 3.
  • If the answer is no, proceed with question 2.


Question 2: Is the target component a project item?

  • If the answer is yes, select copy method NonProj Item to Proj Item.
  • If the answer is no, proceed with question 4.

Question 3: Is there a relationship with the same project?

  • If the answer is yes, select copy method EBOM to Production BOM Only.
  • If the answer is no, proceed with question 4.


Question 4: Is there a relationship with the target item?

  • If the answer is yes, proceed with question 5.
  • If the answer is no, select copy method No Copy Action.


Question 5: Does the item exist already?

  • If the answer is yes, select copy method EBOM to Production BOM Only.
  • If the answer is no, select copy method Copy E-Item to Item.
First1213141517192021Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

Kathy Barthelt

Infor LN & Baan Tips & Tricks for TECHNOLOGY & FINANCE: Archiving Finalized Transactions

TECHNOLOGY & FINANCE: Archiving Finalized Transactions

To support correct archiving in a multicompany structure, the following rules apply:

  • Each company must have its own archive company. Companies cannot share an archive company.
  • The structure of archive companies must be an exact copy of the live environment.
  • A company must keep the same archive company until the end of its lifetime. Once data has been archived, you cannot change the archive company.

If extra archiving capacity is required, it is recommended that you set up a second archiving environment, which must also be an exact copy of the live environment. Define the companies of the second archive environment as the archive companies of the companies of the first archive environment. If necessary, a third and more archiving environments can be set up. You must then archive the data from each archive company to its archive company in the second archiving environment, and so on.

When you archive the data, LN builds an array with all the companies of the group and the archive company linked to each company. If any of the companies in the group does not have an archive company, LN reports an error and aborts the archiving process.

Batches and batch lines are only archived and/or deleted if you perform archiving and deletion in the company in which they exist. This is always the source company. Any intercompany documents and related finalized transactions that belong to the batch are not archived and/or deleted until the target company is archived.

If the batch has been deleted from the live environment, such intercompany documents and transactions will then temporarily exist without a batch in the live environment until the target company’s transactions are archived. Therefore, it is recommended to archive all the companies of a group within a short time.

Finalization runs are also archived. A finalization run can only be deleted from the live environment if all the attached batches have also been deleted.

Financial documents are archived and/or deleted if you perform archiving and deletion in the company in which they exist. For each document, LN searches whether a related intercompany document exists.

If the document’s transaction type indicates that the document numbering does not have to be in a fixed sequence, the document is not deleted from the live environment, to avoid duplicate document numbers.

A finalized transaction is not deleted from the live environment if the fiscal year of the transaction does not equal the fiscal year of the batch and the fiscal year of the transaction cannot yet be archived. If the Archive option is selected, the related batch, batch line, and document are copied to the archive company and retained in the live environment.

If a transaction is still referenced by open sales orders or purchase orders, it is marked as Deleted but not actually deleted. The related batch, batch line, and document are copied to the archive company and retained in the live environment. They are deleted when the referenced open transactions are closed and archived, for example, when you run the Archive/Delete Fully Paid Purchase Invoices (tfacp2250m000) session

If the transaction’s ledger account is a matchable account, any related matching data is also archived.

During the archiving process, the originating company of the finalized transaction is replaced with the originating company’s archive company. In this way, the archive environment will not contain references to the live environment.

During archiving, intercompany document relations are also copied to the archive environment. In the archive environment, these relations are updated in such a way, that each document in the relation refers to the environment in which the document actually exists. In the live environment, the document relation is retained until all related finalized transactions are deleted. For invoice-related transactions, this only occurs during the removal of fully-paid invoices. The document relation is also updated in the live environment, in order to refer to the archived document if all related finalized transactions have been removed from the live environment.

After the normal archiving process, an additional archiving step is performed in which all transactions and documents in the live company that arise from intercompany postings, are archived. During this step, intercompany relations are archived and/or deleted as described earlier.

Batches, batch lines, and documents that have the Deleted status are deleted from the live environment, unless the document’s transaction type indicates that the document numbering does not have to be in a fixed sequence. Such documents are not deleted from the live environment, to avoid duplicate document numbers.

Previous Article Infor LN & Baan Tips & Tricks for EXECUTIVES
Next Article Infor LN & Baan Tips & Tricks for OPERATIONS: Simulated Purchase Prices (ticpr1170m000)
Print
497 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories