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 | The business case for moving your ERP to the cloud and choosing MT deployment

Kathy Barthelt 0 11844 Article rating: 5.0

As more companies invest in cloud computing for their business software and migrate their ERP systems to the cloud, many are considering whether single-tenant or multi-tenant cloud deployment is the best choice.

In this executive brief, Infor outlines insights from the analyst community on the growth of cloud technology, key distinctions between single- and multi-tenant deployments, and why the multi-tenant option for ERP may be the best move for your business.

Learn more>

Tick-Tock... It's time to get more out of your ERP

Crossroads RMC 0 9899 Article rating: 5.0

As crazy as it sounds, we’re about to enter the 2nd half of 2024. How are you doing on your 2024 goals? Planning for 2025 projects?

Maybe it's time to get more out of your Infor ERP system.

⇒⇒ TIME TO UPGRADE?

Is an upgrade to the latest version of your ERP the goal for 2024/2025? If so, Crossroads RMC brings 40 years of industry experience to the table to ensure that your upgrade achieves the results you’re looking for and does so on time and within budget.

Crossroads RMC's team of expert consultants will:

  • Review your custom components to see what can be eliminated
  • Provide an analysis of the specific benefits that your company can achieve by upgrading
  • Train your users on the latest functionality
  • Support your users on the old version while the project team focuses on the upgrade project
  • Handle the entire upgrade project from start to finish
  • Supplement your existing project team with 1-2 key resources
  • Develop the integration to that 3rd party system that is a MUST-HAVE when you upgrade


⇒⇒ NOT UPGRADING?

Infor LX/BPCS Tips & Tricks for FINANCE: Prevent Voiding of Selected Invoices

George Moroses 0 16461 Article rating: 5.0

This enhancement prevents users from voiding invoices after they have been selected for payment. If a user selects an invoice for payment and another user voids the invoice during the payment process, it can produce erroneous and duplicate records. The ACP500 programs were modified to check the status of an invoice before it can be voided. If the invoice has been selected for payment, a message is generated, and the invoice cannot be voided.

Infor LX/BPCS Tips & Tricks for TECHNOLOGY: Update User Security in IDF

George Moroses 0 18694 Article rating: 5.0

Automatically synchronize security changes from LX to IDF, replacing CPYSECIDF. This new process synchronizes users in IDF with those in core LX security whenever a user’s security settings are changed. When a user is deleted from an LX environment, they can also be automatically removed from the IDF environment. Changes to a user’s access to programs in LX are mirrored in IDF. Access to Companies, Facilities, and Warehouses are also synchronized. Additionally, when Business Roles or Business Units access is changed, all users assigned to those roles or units are updated in IDF security.

Infor LX/BPCS Tips & Tricks for OPERATIONS: Copy Shop Order

George Moroses 0 19378 Article rating: 5.0

In the Shop Order Selection program, action 3=Copy is available. This action allows copying any shop order except for flow orders or campaign orders. Instead of copying from the parent item's bill of material and routing, the new shop order’s materials and operations will be copied from the selected shop order. Note that if the existing shop order is linked to a customer order or line, this linkage will not be copied to the new shop order.

Infor News You Can Use | Have you upgraded to Infor LX 8.4.2 yet?

George Moroses 0 10749 Article rating: 5.0

Unlock industry capabilities

The latest version of Infor LX, release 8.4.2, provides core enhancements, an expanded database, and global modernization to meet market changes.

  • IDF serves as a rapid development platform with extensibility that enables release transparency and allows your IT team to eliminate legacy queries and custom reports

  • Advanced functions like embedded warehouse management, collaboration with logistics server providers and suppliers, and vendor-managed inventory are all included as standard and designed to support all of your supply chain needs

  • Embedded tools like document management, notifications, and workflows improve collaboration and productivity across teams

Infor LN / Baan Tips & Tricks for EXECUTIVES

Kathy Barthelt 0 20218 Article rating: 5.0

Finance: Propagating Unused Sub-Accounts

You can use this procedure to find accounts that have a valid sub-accounts group but no corresponding general ledger chart account records. This action creates the general ledger chart account record for the account and sub-account combination. This action does not add the accounts to charts.

  1. Select Financials > Global Ledger > Setup > Finance Enterprise Group > Maintenance.
  2. Open the finance enterprise group and click the Sub Account tab.
  3. Select Actions > Propagate Unused Sub Accounts.
  4. Select the finance enterprise group and click OK.

Sub-accounts are added according to group if they have been defined on the accounts. The resulting account can be added to the charts.

Operations: Best Practices for Purchase Order Archiving / Deleting

Here are some best practices to follow if you are considering archiving or deleting purchase order data:

  • If Financials is implemented, we recommend that you do not delete order data in a fiscal year that has not yet been fully closed. This is because the GRINYA process uses information that would be deleted by this action. For best results, check whether the logistical balance for non-invoiced receipts matches the balance of the GRINYA accounts for the periods up to which you want to delete purchase order data.
  • When a purchase order is canceled, you can only delete the purchase order and the related tables. If only a purchase order line is canceled, the line can be deleted and archived.
  • Purchase contracts must be archived before purchase orders can be archived.

You cannot delete a purchase order (line) if:

  • The linked warehouse order is closed but cannot be removed.
  • The purchase order is linked to a PCS pr

Infor LN & Baan Tip & Tricks for OPERATIONS: Best Practices for Purchase Order Archiving / Deleting

Kathy Barthelt 0 23721 Article rating: 5.0

 Here are some best practices to follow if you are considering archiving or deleting purchase order data:

  • If Financials is implemented, we recommend that you do not delete order data in a fiscal year that has not yet been fully closed. This is because the GRINYA process uses information that would be deleted by this action. For best results, check whether the logistical balance for non-invoiced receipts matches the balance of the GRINYA accounts for the periods up to which you want to delete purchase order data.
  • When a purchase order is canceled, you can only delete the purchase order and the related tables. If only a purchase order line is canceled, the line can be deleted and archived.
  • Purchase contracts must be archived before purchase orders can be archived.

You cannot delete a purchase order (line) if:

First1819202123252627Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

Kathy Barthelt

Infor LN & Baan Tips & Tricks for EXECUTIVES

FINANCE: Clear Rounding Differences for Documents with Period Change (tccri7214m000)

Use this session to adjust the rounding difference transactions, calculated during the internal conversion, for inter-period postings.

Inter-period postings are the postings made to the ledger accounts defined in the Finance Company Parameters (tfgld0503m000) session for fiscal and reporting period changes.

If inter-period postings exist, very big rounding differences are calculated . If you run this session, those rounding differences are replaced with values that properly deal with an observed period change.

If inter-period postings exist, during the internal conversion rounding differences can be calculated for the wrong period. If you run this session, those rounding differences are deleted and the rounding differences are created for the correct period.



OPERATIONS: Sales Contract Linked Documents (tdsls3506m000)

Use this session to view the documents linked to a sales contract. You can view these documents only when a sales order line or a sales schedule line is linked to a sales contract line.

Note: 

  • You can view this session only if the Contracts check box is selected in the Sales Parameters (tdsls0100s000) session.
  • You can use the Linked Document option from the References menu to view the details of a specific linked document.


Field Information

Contract: The code of the sales contract.

Description: The description of the sales contract

Line: The sequence number of the sales contract line.

Sales Office: The code of the sales office.

Description: The description of the Sales Office

Linked Document: The document type that is linked to the sales contract line.

Note: This field can be set to Sales Order Line or Sales Schedule Line only.

Linked Document Company: The company in which the document is linked to the sales contract line.

Linked Document: The code of the document that is linked to the sales contract line.

Note: 

  • The code of the sales order is defaulted from the Order Line field in Sales Order Lines (tdsls4101m000) session.
  • The code of the sales schedule is defaulted from the Schedule field in the Sales Schedule Lines (tdsls3107m000) session.

Linked Document Reference: The reference number of the linked document.

Note: 

  • The line number of the sales order line is defaulted from the Line field in the Sales Order Lines (tdsls4101m000) session.
  • The line number of the sales schedule line is defaulted from the Line field in the Sales Schedule Lines (tdsls3107m000) session.

Link Sequence: The sequence number of the linked document.


TECHNOLOGY: Audit Fields by Table (ttaud3125m000)

Use this session to to define which fields must be audited, and when they must be audited.

Note: 

  • It is not required to define the fields that must be audited. Only if not all fields in a table must be audited, you must specify the fields that must be audited. You can only specify fields for a table for which you selected Specified in the Field Selection field of the Audit Tables by Profile (ttaud3120m000) session. If you selected All in that field, all fields in the table are audited, and no fields can be specified.

  • For a detailed explanation of the relation between audit type and field specification, refer to the section How to determine the net result of the audit configuration in the Audit Configuration Management topic.

  • The audit functionality uses the positive approach, which means that you can only specify which tables and fields must be audited, but not which tables and fields must not be audited. Therefore, through the appropriate menu, commands are available to load all (key) fields. You can then delete the fields you do not require.
     

Previous Article Infor LN & Baan Tips & Tricks for TECHNOLOGY: Load Audit Tables for Profile (ttaud3220s000)
Next Article Infor LN & Baan Tips & Tricks for FINANCE: Clear Rounding Differences for Documents with Period Change (tccri7214m000)
Print
574 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories