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 LN & Baan Tip of the Week: What is the LN Report Designer and what is required to use it?

Kathy Barthelt 0 1430 Article rating: 5.0

The main purpose of the Report Designer is to enable changes to the design of a 4GL application report, without modifying the standard report or using an external reporting solution. The changes are stored as personalizations. Therefore, the effort that is required to implement changes, after the standard is updated, is reduced.

You can also generate new reports that are based on a selection of fields from the application data model. These reports are generated in the extensibility package. You can personalize these reports in the Report Designer, or modify them in LN Studio.

  • The Report Designer is available with LN 10.5 and later.
  • Enterprise Server 10.6 is required.
  • The Report Designer is only supported in LN UI.

Note:  On LN 10.5 you must re-compile the reports once with Enterprise Server 10.6 to enable them for the Report Designer.

OTTO - On-Time Ordering: Q&A with an MIS Manager from a metal fabrication manufacturer

George Moroses 0 429 Article rating: 5.0

OTTO  A Q&A with an MIS Manager from a metal fabrication manufacturer:

1. How difficult was it to initially install OTTO?

"We loaded OTTO on our AS/400 on a Friday morning and demonstrated OTTO's capabilities with our own data that afternoon. That really impressed me from an IS perspective because it was so easy to load and run."

2. Would you install it on a test system or on the production system?

"We installed on the production system in order to use live data. OTTO resides outside of the ERP system and builds its own databases so it is not detrimental to any other system."

3. How difficult was it to implement OTTO, was there a negative impact on daily operations?

"Some reports were being used on the first day of the evaluation. There was only positive impact on our operation. For example, shortages in our final assembly area were eliminated within 30 days of the demonstration."

4. Comments?

"I was greatly surprised OTTO fit so well with our operation. OTTO has worked well in our company (we substantially increased on time shipments at the same time our business was seeing a 3 fold increase), but each company has to judge for themselves how well OTTO fits in with their organization."

Contact us to learn how OTTO can help your company!

Analytics Dashboard News: What is a CFOs Biggest Concern?

Crossroads RMC 0 388 Article rating: 5.0

If you ask CFOs about their biggest concerns, most of them will tell you that increasing cash flow is a high priority.

In order to succeed at this, you have to keep an eye on your accounts receivable. Many companies, however, do not have the means or data to find out where they currently stand.

What if you could have that information at your fingertips?

Learn more about Analytics Dashboard for Infor LN/Baan >

Learn more about Analytics Dashboard for Infor LX/BPCS/M3 >

Your Enterprise Resource Planning software lies at the heart of your business

Infor LX & BPCS

George Moroses 0 13842 Article rating: 5.0

How Infor LX & BPCS is utilized is critical to operating a stable, well understood and effective business system. Knowing the current state of your system will enable you to make decisions to either better utilize your current ERP version or upgrade.

Crossroads RMC’s Utilization Review helps you flush out issues and areas for improvement. Our findings have resulted in minor procedural changes to a full reimplementation, or system upgrade to Infor LX.

If your business requirements and your resources have undergone major change since your original implementation, it is time to take a look at your ERP system to see if it is being utilized properly. The Crossroads RMC Utilization Review is designed to work with your people to identify the best way to apply the powerful capabilities within the Manufacturing, Supply Chain and Financial modules within the LX/BPCS software to best suit the needs of your business, not only today, but in years to come.

Learn more>

Infor LX & BPCS Tip of the Week: How do I restrict over-shipments to customers - LX 8.4?

George Moroses 0 1289 Article rating: 5.0

This enhancement prevents over-allocations and resulting overshipments to customers. Attempted over-shipments can present an error message to the user, or there is an option to automatically adjust the user’s request to the allowed quantity.

Since over-shipments result from over-allocations, Infor LX provides an optional validation during the four processes where a user can attempt to over-allocate. Note: Infor LX never over-allocates or over-ships; this always results from a user’s action. This enhancement provides three options regarding over-allocations and over-shipments:

  • Continue current process with warning message.
  • Show error message.
  • Automatically change allocation quantity to match quantity available for shipment.

If the over-ship quantity change is acceptable, internal procedures may require that the order quantity be revised so that pricing, promotions, credit checking, load planning, and other processes reflect the actual quantity.

The programs or areas impacted include:

  • ORD820D, Order Entry System Parameters
  • ORD720D2, Order Allocations
  • ORD725D, Order Entry Allocations
  • ORD570D5, Pick Confirm Inventory Confirmation
  • ORD700D2 / ORD700DA / ORD710B, Order Line Validation

Your Enterprise Resource Planning software lies at the heart of your business

Friedman | MAPICS | XA and more

George Moroses 0 28475 Article rating: 5.0

How your ERP is utilized is critical to operating a stable, well understood and effective business system. Knowing the current state of your system will enable you to make decisions to either better utilize your current ERP version or upgrade.

Crossroads RMC’s Utilization Review helps you flush out issues and areas for improvement. Our findings have resulted in minor procedural changes to a full reimplementation, or system upgrade.

If your business requirements and your resources have undergone a major change since your original implementation, it is time to take a look at your ERP system to see if it is being utilized properly. The Crossroads RMC Utilization Review is designed to work with your people to identify the best way to apply the powerful capabilities within the Manufacturing, Supply Chain and Financial modules within your ERP software to best suit the needs of your business, not only today, but in years to come.

Learn more>

First5859606163656667Last

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