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

Baan/LN Tip of the Week: Optionally Include Tax Amounts In Order Balance

Kathy Barthelt 0 94683 Article rating: No rating

In Baan IV, the order balance amount always includes the tax amount. Consequently, the tax amount must be recalculated every time an order line is modified in order to update the balance correctly. If the tax provider is activated, this requires an API call for every re-calculation of tax.

 

In Infor LN, users can select or clear the new Include Tax in Order Balance check box in the COM Parameters (tccom0000s000) session to indicate whether users want to include tax amounts in the order balance amount. This parameter has an effect on various sessions in Order Management.

BPCS/LX Tip of the Week: Product Routing

Anthony Etzel 0 68617 Article rating: No rating

Defining the Product Routing first requires the items to be setup in the Item Master file. Other master files also need to be defined prior to creating the routing.
These include:

  • The Facility defined with a SYS program
  • The Warehouses defined with an INV program
  • Locations defined with an INV program
  • The Machines (required if using capacity planning or an MES interface) defined with an MDM program

After the above data is set up, the Department file and Work Center files can be setup in MDM. Now you are ready to define a product route.

Baan/LN Tip of the Week: Month End – Miscellaneous To-Do’s

Kathy Barthelt 0 97355 Article rating: No rating
  • Print Sales Order History Information
    • all invoices processed through sales
  • Check Inventory Valuation
    • this should tie out to your inventory accounts
  • Print Integration Information
    • see all postings from WIP to finished goods
  • Print G/L Transaction Information
    • print specific transaction types for any GL account
  • Print Lot Control Information
    • will show where serial numbers were used

BPCS/LX Tip of the Week: What is Lean Make to Order?

Anthony Etzel 0 74831 Article rating: No rating

This is a simple way to go from the customer order to making the order and shipping the order. It involves a few simple steps:

  1. Receive and enter the customer order
  2. Automatic credit review
  3. Automatic release of the shop order tied to the customer order
  4. Issue material, report labor to the production order receipt
  5. Pick the order, ship the order, invoice the customer

 

With lean, you can skip processing the demand through MRP. You can go directly from the customer order to the shop order creation.

Baan/LN Tip of the Week: Optionally Include Tax Amounts In Order Balance

Kathy Barthelt 0 168080 Article rating: No rating

In Baan IV, the order balance amount always includes the tax amount. Consequently, the tax amount must be recalculated every time an order line is modified in order to update the balance correctly. If the tax provider is activated, this requires an API call for every re-calculation of tax.

In Infor LN, users can select or clear the new Include Tax in Order Balance check box in the COM Parameters (tccom0000s000) session to indicate whether users want to include tax amounts in the order balance amount. This parameter has an effect on various sessions in Order Management.

BPCS/LX Tip of the Week: Top Down Shop Order Schedule

Anthony Etzel 0 75123 Article rating: No rating

In ERP LX, this function is called Backward Scheduling. This is a simple, easy way to create and release shop orders associated with the end item.

The result is a shop calendar with the associated order start dates. Setting up ERP LX properly with correct Queue Times, Setup and Run Times, along with Move Times, will result in accurate shop order start dates.

Baan/LN Tip of the Week: Back Dating Cycling Counting Orders

Kathy Barthelt 0 102592 Article rating: No rating

Cycle Count Orders cannot be directly “back dated” in Baan IV, Baan V or LN, however, there are some work-arounds.

In Baan IV you can do an inventory adjustment and back date. Just set all dates on the adjustment to the date you want and Baan will post the adjustment in that period.

In LN you can do a Cycle Count/ Adjustment and again back date and Baan will post to that period.

 

Unfortunately, there is no work-around for Baan V.

First115116117118120122123124Last

Tips:  LX | BPCS | M3

Improves control over PO costing changes during invoice entry by replacing passive warnings with an intentional override action.

  • In ACP500D3 (Invoice Entry PO Costing), users previously could unintentionally accept changes by pressing ENTER, even when quantity to cost or amount to cost values had changed.

  • A new “F14 to Override” warning message replaces the old message:
    “Details have changed. Press enter again to accept data.”
    This ensures users acknowledge and confirm significant changes explicitly.

New System Parameter:

  • “Apply GRN Costing Tolerance for PO Costing” (optional):

    • Within tolerance: Displays the original message —
      “Details have changed. Press enter again to accept data.”

    • Outside tolerance: Triggers the new override requirement —
      “F14 to Override”

Benefits:

  • Enhances oversight and reduces unintentional cost acceptance.

  • Enables better control of PO costs when invoice details differ from expectations.

Last

Tips: LN | Baan

Kathy Barthelt

Infor LN & Baan Tips & Tricks for TECHNOLOGY: 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 OPERATIONS: Using Country of Origin for Purchase Orders
Next Article Infor LN & Baan Tips & Tricks for EXECUTIVES
Print
28448 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories