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

Analytics Dashboard: Reports are great, but only provide a snapshots of a specific moment

Don’t you need to know what’s happening right NOW?

Crossroads RMC 0 37734 Article rating: 5.0

Get up-to-date views of your data, graphs, charts, you name it!

All the way YOU want it!  All without touching your ERP!

Learn how Analytics Dashboard for Infor LN & Baan works in your unique environment.
Learn how Analytics Dashboard for Infor LX, BPCS, & M3 works in your unique environment.

The Top 5 Benefits of a Manufacturing Execution System (MES)

by PlanetTogether

Anthony Etzel 0 39491 Article rating: 5.0

MES provides the right information at the right time to show the floor manager how to optimize current conditions to improve production output.

Need 5 more reasons why you should invest in an MES system?
Read the full article by PlanetTogether:

https://www.planettogether.com/blog/the-top-5-advantages-of-a-manufacturing-execution-system

Clearly, an MES does more than simply track the amount of product coming off of your production lines. Improving your facility's efficiency begins with accurately recording production, material usage, and personnel time. Crossroads MES accomplishes this feat with ease and precision.

Infor LX & BPCS Tip of the Week: Trim Leading Zero

George Moroses 0 63453 Article rating: 5.0

In LX 8.4, an enhancement has been included to allow for the expanded Company fields to have the leading zero truncated.

To trim leading zeros, CEA515B is called during macro resolution to trim the leading zero based on the position in the Zero Trim file (GZT). The Zero Trim file contains all the company number fields currently defined in the CEA Cross Reference fie (GXM).

This enhancement provides year over year comparison in financial reports and eliminates the need to setup new companies in programs such as Alias Definition. Financial programs trim the leading zero on Company fields, such as Company 010, on subsystem transactions to process as Company 10 during CEA macro resolution. Clients who prefer to retain the Company value as 010 on financial reports can clear the GZT file.

Infor LN & Baan Add-ons: Need a reason why you should barcode your inventory? How about 8 reasons!

Kathy Barthelt 0 35838 Article rating: 5.0

Top Eight Benefits of Barcodes

Barcodes are often overlooked as a method for cutting costs and saving time. A valuable and viable choice for businesses looking to improve efficiency and reduce overhead, barcodes are both cost-effective and reliable.

Crossroads RMC offers RMClabel which can be tied to any data collection system, or run stand-alone. Create barcode labels with 1D

Infor LN & Baan: Data Collection

Be honest. Does your business REALLY operate in real time?

Kathy Barthelt 0 42073 Article rating: 5.0

Do you have up-to-date real-time information on labor, machine time, and parts consumed? How accurate is your data? Can you get an accurate picture of what is going on across your operations at any time?

If not, Crossroads data collection solution should be considered. By combining sessions, eliminating duplicate entries and using available information to complete a transaction, Web Collect, formerly RMC3 extends the Infor LN and Baan applications to ensure efficiencies and timely information flow and reporting. 

Consulting News: Are you familiar with your Infor LN / Baan System Log?

Kathy Barthelt 0 40151 Article rating: 5.0

Data about the system and the application is stored in a system log. The system data includes information about:

  • The application environment
  • Any reorganization of tables
  • The available free disk space
  • The back-up schedule
  • The user data reports
  • The updates
  • Changes in the system
  • The error messages and solutions

Are you comfortable with reading your ERP system log? Have you checked it lately? Need help interpreting if your system may have a problem? Contact Kathy Barthelt today and one of our expert technical consultants can help to put your mind at ease and make sure your system is running as it should.

Infor LN & Baan Tip of the Week: Warehouse Blocking – LN 10.7

Kathy Barthelt 0 76331 Article rating: 5.0

The functionality to block a warehouse for inbound or outbound transactions has been enhanced. A check for blocks is performed not only during receipt and shipment confirmation, but at multiple stages in the process. In addition, you can specify these blocking options for the inbound and outbound processes:

• No

• Yes

• Interactive

For example, if Blocked for Inbound is set to Yes, no inbound actions are allowed in the warehouse. Consequently, users cannot confirm receipts, generate and put away inbound advice or storage lists, and perform inbound inspections. 

If Interactive is set, during a non-automatic warehouse inbound procedure, warnings are displayed which offer the user a choice to either cancel the action or continue. Batch or automatic inbound processes continue, but the corresponding reports and logs make note of the blocking. However, in all scenarios, receipt confirmation is not allowed.

The same rules are applicable for the warehouse outbound procedure steps. The restriction for receipt confirmation also applies to shipment confirmation.

For warehouse transfer orders, not only the ship-from warehouse is checked for outbound process blocks, but also the ship-to warehouse. This prevents situations in which goods get stuck in transit due to inbound procedure blocks that apply to the destination warehouse. Now, the transfer process is already blocked during outbound.

First6667686971737475Last

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
564 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories