Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Resources Infor ERP Tips & News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Subscribe to newsletter

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

George Moroses 0 16062 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.

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

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

George Moroses 0 8716 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

Read more

Infor LN / Baan Tips & Tricks for EXECUTIVES

Kathy Barthelt 0 16670 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
Read more

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

Kathy Barthelt 0 18372 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:

Read more

Infor LN & Baan Tip & Tricks for TECHNOLOGY: Using Table Boosters to Speed Up Sessions & Processes

Kathy Barthelt 0 19052 Article rating: 5.0

To increase the speed of sessions and processes slowed by large amounts of data, you can use table boosters. These speed up access to specific database tables by loading the table, or a specified part of it, into memory. Table boosters are defined in the Table Boosters (tcmcs0598m000) session.

Tables

Table boosters are implemented for tables. By default, table boosters are not active. When you access a table, LN builds a list of tables for which you can activate the boosters in the Table Boosters (tcmcs0598m000) session.

Note: You can only activate table boosters for tables that have been accessed at least once.

For more information, refer to the LN - Performance, Tracing, and Tuning Guide (U9357).

Read more

Infor LX / BPCS Tips & Tricks for Executives

Finance | Operations | Technology

George Moroses 0 13309 Article rating: 5.0

Finance: Cost Rollup by Effective Date
Allow the load standard cost from routing and cost rollup programs to process as of a specified effective date.  With the addition of an optional effective date parameter to prompt screens for cost rollup CST500 and load standards from routing CST600. If entered, only consider bill of material components and routing operations with effective and discontinue dates that make them effective as of the entered parameter effective date.


Operations: Outside Operation Purchase Order Include Vendor Item Number
Copy the vendor item number from the vendor quote to purchase orders created automatically from outside operations of shop orders. During the process of automatically creating purchase orders from outside operations of shop orders, copy the vendor item number from the vendor quote to the purchase order line. With this change, looking at a purchase order that was created automatically for an outside operation of a shop order, the vendor item number from the vendor quote will be visible on the purchase order line.


Technology: Group Security for ILM501 Inbound Delivery Maintenance
Add function key / action code security to control who is authorized to create/revise/delete functions in ILM501 Inbound Delivery Maintenance.  With added Group Security, managers can control which users are authorized to create, change and delete deliveries in ILM501 Inbound Delivery Maintenance.

Read more

Infor LX / BPCS Tips & Tricks for OPERATIONS: Outside Operation Purchase Order Include Vendor Item Number

George Moroses 0 12174 Article rating: 5.0

Operations: Outside Operation Purchase Order Include Vendor Item Number

Copy the vendor item number from the vendor quote to purchase orders created automatically from outside operations of shop orders. During the process of automatically creating purchase orders from outside operations of shop orders, copy the vendor item number from the vendor quote to the purchase order line. With this change, looking at a purchase order that was created automatically for an outside operation of a shop order, the vendor item number from the vendor quote will be visible on the purchase order line.

Read more
First1011121315171819Last

Tips:  LX | BPCS | M3

Item Facility Master has a new attribute to define the override inspection days lead time CICP.ICINSD.

  • When an item facility has a defined override inspection days lead time, that value will be used instead of the system parameter inspection days lead time.

MRP exception report, MRP200B
Purchase planning report, PUR285B
Purchase order / Requisition maintenance, PUR500D3
Purchase order consolidation / release, PUR640B1
Vendor splits, PUR653B

Read more

This enhancement improved the subfile utilized in MRP320D Master Schedule Detail Inquiry -SCR001 by expanding the subfile with data rather than clearing the subfile as user pages. This change provides full support for the WebTop 4.8 Grid decorator.

This enhancement updated the approach used to populate the subfile to allow a deployed Webtop Grid to function correctly. There is no visible or user-impacted change to the way the program functions.

This enhancement provides improved functionality and full support of a Webtop grid applied to the subfile.

Read more
Last

Tips: LN | Baan

Kathy Barthelt
/ Categories: Infor LN & Baan Tips, Technology

Infor LN & Baan Tips & Tricks for TECHNOLOGY: Archiving Concept

Companies are developing procedures for entering data into an ERP system and for archiving manuals, drawings, specs, and other hard-copy documents. However, in many cases there is no defined procedures to store historical electronic data. Archiving electronic data should be an integral part of your business processes. 

Generally, archiving is the process of moving historical data from the operational environment to a special archive environment. At home, you might move old bank statements from a closet in your study to a box in the attic. At the office, you might store old hard copies of purchase orders in a room far from your own desk. Just because you no longer need the information in your daily work, does not mean you can dispose of the information. In terms of electronic data in your ERP system, archiving means moving historic data from the operational company to a special archive company; in that way, the historic data will be out of your way and safely stored. To free up disk space on your machine after you have archived the data, you can also move the historic data to an external medium.

Archiving strategy:
Archiving historical data is an irreversible process. After data is moved to the archive company, the data can no longer be uploaded back into the operational company. Archiving has a direct effect on the accessibility and availability of information; therefore, you must define a robust archiving strategy which addresses three major topics: What, When, and Who.

Business requirements:
Your business requirements determine what must be stored and for how long. For example, if you have a warranty situation on your projects for five years, you might be required to keep your project open during this time, or you may keep the project in an archive company. Therefore, if the project must remain open, no project-related information, including orders and integration transactions, can be archived.

Every business manager must decide how long what data must be stored in an operational environment for quick access. Reporting requirements must also be listed.

Legal requirements:
In most countries, legal requirements apply to financial data. Tax authorities may require financial data to be stored for a minimum number of years. Additionally, in specific lines of business such as food and beverages or aerospace, governments maintain specific legal requirements, which impact your archiving strategy.

User requirements:
Users rely on historical information. For example, a customer service employee may need to have shipment information of up to one year in the past to accurately address customer queries. These requirements must also be taken into account when you define what can be archived.

Data to be archived or deleted:
Various parties related to your company use information based on logistical and financial transactions occurring in the past. Before you archive or delete this information, you must investigate the need for the information.

Your ERP system contains standard archiving sessions in all major modules. These sessions are designed to copy historical data to the archive company, and then delete the data from the operational company. 

You have three options in archiving sessions:

  1. Archiving and deleting: Data is transferred to the archive company and then deleted in the operational company.

  2. Deleting: Data is deleted in the operational company, but not archived.

  3. Archiving: Data is transferred to the archive company, but not deleted in the operational company.

Using option 1 or 2 makes archiving irreversible. If you archive only because you want to preview the results, the archiving can be done a number of times.

Usually, in archiving sessions, you can also specify:

  • The date up to which the data must be archived
  • If texts must also be archived
  • If texts that already exist in the archive company must be replaced

In addition to archiving logistical and financial data, you can archive general data. 

Delete sessions:
In all major modules, your ERP system contains delete sessions. These sessions only have delete functionality, no archive functionality. Consequently, they are used to clean up data in the operational company, not to transfer data to the archive company. For more information about these delete sessions, see the "Delete sessions" sections under the various modules. For example, see Delete sessions under Procurement.

After data is deleted using delete sessions, the data is no longer available in the operational company. However, parameter settings may determine whether history data is logged when you remove specific data. If required, you can archive the history using the appropriate archiving session.

When can data be archived?
Based on the answers to the previous question, you can now set a term of retaining relevant historical data in your operational environment, and a term of keeping data available in the archive environment.

Who can archive data?
Because archiving is an irreversible process, a certain risk is involved. For example, what if one of your employees starts up an archiving session by mistake? For this reason, you must determine who is authorized to archive and delete data, and then set up these authorizations with the functionality your ERP system offers.

Because no further changes must be made to archived data, access to the archive company must also be restricted to read-only authorization for most users.

Match strategy with ERP functionality: 
After you list all your requirements, the next step is to verify whether the standard ERP functionality is sufficient to facilitate your needs. Usually, your ERP system provides the functionality to meet all of your needs, but must not force you to compromise. We recommend that you avoid customizing your software, however, because we are looking for long-term operational-data storage, customizations must not be ruled out entirely. An example is the requirement to show, in one report, the data from the operational company and archive company. In the current version, this is not standard functionality, but this can be important to manage your business. What can be even more important, if you are using customized software, is the question of whether the archiving sessions have been included. Do you take into account the fields and tables you have customized? Customized tables and fields may have to be included when performing delete/archive runs.

Archiving plan:
After you define an archiving strategy that suits your requirements, you can define the archiving plan. In this plan, you translate the strategy to a more operational level.

Contact Crossroads RMC— Let's take the next step together to execute your archiving plan.

800.762.2077

Previous Article Infor LN & Baan Tips & Tricks for OPERATIONS: Blocking or Unblocking Warehouses
Next Article Infor LN & Baan Tips & Tricks for FINANCE: Remap Posted Integration Transactions (tfgld4282m100)
Print
12646 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt
Contact author

Contact author

x

Categories