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 LX & BPCS Tip: System i Workspace AnyWhere information and Important Support Dates for IBM and Microsoft Products

George Moroses 0 27934 Article rating: 2.5

System i Workspace AnyWhere is a web application framework that provides a common user interface for Infor’s IBM i products.

*** We strongly recommend that you subscribe to this KB to receive automatic notification when it is updated ***

Latest Updates
System i Workspace AnyWhere - Feature Pack 22 is now available - see the Update History section below (as of January 4, 2024)

Infor LX / BPCS & Infor LN / Baan Tip: Time for the Notorious TRIO: Manual -  Physical -  Inventory

Crossroads RMC 0 22719 Article rating: 2.5

While it might be accurate (and I emphasize "might"), is a Manual Physical Inventory the optimal approach? Best practices unequivocally say otherwise!

A superior alternative is the adoption of Cycle Counting. Why choose Cycle Counting over a complete physical inventory? This method zeroes in on a selected stock range, allowing concurrent execution with a company's regular operations. Cycle Counts offers a streamlined approach to inventory management, minimizing disruptions to processes related to stock receipt, consumption, or dispatch.

The dreaded "freeze" is no longer a necessity, sparing your staff from extended holiday hours, and ensuring accurate inventory counts throughout the year! Crossroads RMC is poised to assist you in implementing Cycle Counting efficiently and effortlessly.

Contact us today to kickstart this transformative process at 800.762.2077.

Infor LX & BPCS Year-End Close Checklist

George Moroses 0 23877 Article rating: 5.0

As the year draws to a close, the hustle and bustle of year-end activities can sometimes lead to overlooking critical tasks within your Infor ERP system. Ensuring a proper year-end close is essential for setting the stage for success in the coming year. Here is a comprehensive checklist to guide you through the process:

Year-End Close Process Objectives:

Infor LX/BPCS Tip What are the differences between INV810 and INV015 for Cycle Counting updates?

George Moroses 0 23221 Article rating: 5.0

INV810 only deletes the sequence number from the ILI of the item so it is not selected again for counting and does not delete the ICY record.

The ICY Cycle Count sequential history file increases in size with each new cycle count session. Running INV015 will purge all the old ICY records up to the date entered on the set-up screen ‘Enter Cycle Count Ending Date’ field. Physically deleting the old ICY files.

In most cases, when you complete the cycle count posting and run the reports, you can reconcile the data as required. After you reconcile the data for a specific day (or group of days), you can run INV015 to purge the data for that day (or group of days).

Infor LN & Baan Tip: When is backflushing disabled in LN?

Kathy Barthelt 0 67765 Article rating: .1

There are restrictions for the use of the field Allow Backflushing:/ Item – Production by Site (tiipd0151m100)

The option is unavailable if the option Direct Initiate Inventory is set. Serialized items can only be backflushed if in the Items - Warehousing (whwmd4500m000) details session the Serials in Inventory check box is cleared, and the Register Serial Issue During As Built field is Yes. In all other cases, serialized items cannot be backflushed.

Unlocking Success: The Power of Staff Augmentation with Crossroads RMC

Infor LX, BPCS, Infor M3, Infor LN & Baan

Crossroads RMC 0 15743 Article rating: 5.0

Consider this...

Your team is currently engaged in a critical project for your top client. However, to ensure the project's timely completion and high customer satisfaction, it's imperative to expand your team. You're aware that the recruitment process is time-consuming, and finding highly qualified individuals who don't require extensive training, especially in your ERP system and your specific business, is a challenging task.

Or perhaps this situation sounds familiar...

Your ERP system is running sluggishly, and you're aware that there are updates available that could enhance system performance. Unfortunately, your IT specialist is currently occupied with other tasks, and there's uncertainty about when the upgrade can be executed.

Both of these scenarios reflect the challenges businesses face in our era of rapid technological advancement. To maintain competitiveness, it's essential to meet client demands and ensure the smooth operation of internal systems, preventing any hindrances to current production. The hard reality is that your success hinges on having expert staff who can make an immediate, positive impact on your business.

So, how can you consistently maintain the right team size and composition to address contemporary challenges when hiring new personnel is a costly, protracted process?

Crossroads RMC + Avalara…

The BEST way to handle tax compliance

Crossroads RMC 0 16130 Article rating: 5.0

A CASE STUDY

The Company:
A supplier of fabricated steel equipment to large food service firms such as Starbucks, Subway, and Walmart.

The Challenge:
This supplier needed to find a better way to handle tax compliance. The supplier’s legacy tax software was incompatible with their ERP. This led to:

  • The required upgrade to the latest Infor ERP version without having a pre-built, certified, fully-functional connector
  • The reliance upon labor-intensive, error-prone manual processes
  • Inaccurate customer addresses
  • Uncertainty around product and service taxability, as well as nexus
  • Increased audit risk


The Solution:

First2627282931333435Last

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

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories