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 Tips & Tricks for TECHNOLOGY: Update User Security in IDF

George Moroses 0 17682 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 18301 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 9992 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 19022 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 22067 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:

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

Kathy Barthelt 0 25024 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).

Infor LX / BPCS Tips & Tricks for Executives

Finance | Operations | Technology

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

First1213141517192021Last

Tips:  LX | BPCS | M3

New IDF Inquiries 

Infor LX has a long history of providing IDF inquiries over most critical business areas, but there are still some areas that lack this capability.
The following IDF inquiries are now available in 8.4.2:

  • Customer Quote
  • Customer Quote Line
  • RMA (Return Material Authorization)
  • RMA Line

Benefits

  • Ability to sort, subset, filter, and view information in a modern and intuitive way
  • Point and click navigation to related information – 360 views
    • Exceptional personalization and extensibility capabilities

New IDF Inquiries 

Infor LX has a long history of providing IDF inquiries over most critical business areas, but there are still some areas that lack this capability.
The following IDF inquiries are now available in 8.4.2:

  • Customer Quote
  • Customer Quote Line
  • RMA (Return Material Authorization)
  • RMA Line

Benefits

  • Ability to sort, subset, filter, and view information in a modern and intuitive way
  • Point and click navigation to related information – 360 views
    • Exceptional personalization and extensibility capabilities
Last

Tips: LN | Baan

Kathy Barthelt

Infor LN & Baan Tips & Tricks for EXECUTIVES

FINANCE Tip: Remap Posted Integration Transactions (tfgld4282m100)

Use this session to remap Posted transactions that were mapped incorrectly.

To remap integration transactions successfully, several conditions must be fulfilled. For details, refer to To remap integration transactions.

Enter the ranges of selection criteria for the integration transaction or range of integration transactions to be remapped. You can select the integration transactions of a range of business objects or of a specific business object.

You must select a specific integration document type or an integration document type group.

To evaluate the remapping before you perform the actual remapping, you can select the Simulate check box and the Error Report check box. After you solve the errors, you can run the session again and clear the Simulate check box.

After remapping the integration transactions, you can use the Post Integration Transactions (tfgld4282m000) session to create the postings in the General Ledger.

OPERATIONS Tip: Using Country of Origin for Purchase Orders

For purchase orders, information about the COO allows you to track the related import duties, tariffs, and compliance with sourcing requirements. You can maintain the COO of an item when creating an order or the release level of a purchase order.

When you create a purchase order line in the Purchase Order Lines (tdpur4101m000) session, the COO related details are defaulted based on the item-purchase data defined in the Items - Purchase (tdipu0101m000) session. To view this data, you can use the Country of Origin option from the References menu in the Purchase Order Lines (tdpur4101m000) session.

After the order line is released to Warehousing, an inbound line is created in the Inbound Order Lines (whinh2110m000) session with the COO information. A receipt line is created in the Warehouse Receipt Lines (whinh3512m100) session when the inbound order line is received. To view the actual COO for the item specified on the receipt line, you can use the Country of Origin option from the References menu in this session.

You can view the country of origin (COO) data for the inventory received in a warehouse in the Item - Country of Origin Inventory (tcitu6600m000) session based on the data specified in the header section such as, warehouse, item, and so on.

In the Inventory Tracking Receipt (tcitu2610m000) session, you can view the information related to the purchase order, inventory quantity, and actual COO of the item. You can use the Intrastat Transactions (tccom7171m000) session to view the COO that is reported for an order line and is used for the Intrastat declaration.

TECHNOLOGY Tip: Impact of Configuration Changes on Audit Trails:

Impact of Configuration Changes on Audit Trails

The impact of changes in the audit settings varies depending on the specific circumstances. The issues typically arise when changes made to audit settings are implemented at runtime without requiring all users to exit the system (LN). As a result, some users may continue to generate audit trails using the old configuration, while those who log in after the changes take effect will create audit trails based on the new configuration.

Changes in User Profiles

Below is a summary table that illustrates the effects of these changes for a specific table within a company:

Change Description Impact
Add a table Users that still use the old settings do not audit some transactions.
Remove a table Some transactions that must not be audited with the new settings are still audited by users that use the old settings.
Change the audit type for a table or field Some transactions are audited according to the old settings, and other transactions are audited according to the new settings.
Add or remove a field After you audit transactions in the table with the new settings, users that use the old settings can no longer perform transactions on this table. Therefore, users with the old settings can be forced to restart LN.

Note on Changes in Field-Specific Auditing:
When you toggle field-specific auditing on or off for a table, which alters the number of fields being audited, the effect is analogous to adding or removing a field. However, not every modification to the audit settings impacts the runtime settings. Converting the new settings to runtime might result in no net change for the entire configuration if the overall effect of the adjustments neutralizes each other.

Previous Article Infor LN & Baan Tips & Tricks for TECHNOLOGY: Impact of Configuration Changes on Audit Trails
Next Article Infor LN & Baan Tips & Tricks for EXECUTIVES
Print
36072 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories