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 -Join Us for an Exclusive Insight into Data Collection Streamlining

Webinar: 10/15/2024 at 1PM Eastern

George Moroses 0 11850 Article rating: 5.0

Discover how the Crossroads RMC team can help you improve data collection at the point of execution.

In this session, we'll cover key benefits that transform your shop floor:

  • Modern Mobility: Experience a contemporary interface designed for today’s devices, offering improved usability and flexibility.
  • Real-Time Visibility: Gain access to live data, enabling rapid response to changes and boosting overall efficiency.
  • Digital Shop Packets: Go paperless with digital packets, reducing waste and minimizing clutter.
  • Flexible Scheduling: Schedule tasks directly at the machine level to maximize productivity and adaptability on the shop floor.


Don’t miss this chance to elevate your shop floor operations with NextTrack MES. Learn how streamlined processes, enhanced mobility, and real-time insights can help you achieve more. Secure your spot now!

Register Today!

Infor LX/BPCS Tips & Tricks for OPERATIONS: Multi-Level Shop Order Release Due Dates

George Moroses 0 13527 Article rating: 5.0

Previously, Material Requirements Planning (MRP) preferred practices meant that the component's due date was the same as the parent's shop order release date. Because MRP trends have changed, the preference for this due date is the day before the release date of the parent. Although Infor LX already has this functionality in Shop Order Maintenance programs (SFC500), users could not change how due dates were determined for lower-level shop orders in Multi-Level Shop Order Release, SFC530D.

This enhancement provides an additional parameter for Multi-Level Shop Order Release. This parameter allows the user to change how the due date of the child components is determined. The Multi-Level Shop Order Release, SFC5302, has a new parameter for shop orders. The Due Date of Children = Release Date of Prent (Due Date of Children) field allows the user to set the due date determined for multi-level shop orders.

Infor LX/BPCS Tips & Tricks for FINANCE: Override Exchange Rate

George Moroses 0 10960 Article rating: 5.0

This feature uses different exchange rates in the user's inventory processes by using new macros in Post Inventory to G/L, INV920D. INV920 used macros limited by the Override Exchange Rate parameter set on the book in Book Definition, CEA105D3. If the Override Exchange rate parameter is set to No, the macro uses the Rate Type of the Book. If the Override Exchange parameter is set to Yes, the macro uses the Rate Type of the Order Company. This enhancement provides macros that use the Rate Type of the Order Company. This enhancement provides macros that use the Rate Type of the Warehouse Company, Order Company, or the Book regardless of the Override Exchange Rate parameter in the Book.

Infor LX/BPCS Tips & Tricks for TECHNOLOGY: Change SyncBillofMaterial BOD

George Moroses 0 13763 Article rating: 5.0

This enhancement provides the ability to enable setting facility-specific bill of material BOD's accounting entity from the facility's stocking warehouse's company. The bill of material BOD can be consistent with the bill of resources BOD which sets its accounting entity from the company associated with the facility's stocking warehouse.

Crossroads RMC Presents 4 Must-Attend Sessions at inPOWER 2024

September 23-26, 2024

George Moroses 0 11491 Article rating: 5.0

Crossroads RMC Presents 4 Must-Attend Sessions at inPOWER 2024
Empower Your Business with Innovation

September 23-26, 2024

As a Gold Sponsor, Crossroads RMC is thrilled to present four impactful LX Track sessions this year, designed to inspire and empower attendees to drive success within their organizations:

Infor LN & Baan Tips & Tricks for TECHNOLOGY: Adding a Timestamp to LN Standard Tables

Kathy Barthelt 0 32347 Article rating: 5.0

Table Timestamp Definitions (ttadv4136m000)

Use this session to define timestamps for Infor LN tables. A timestamp is an additional column that stores the date and time of the last change for each record.

Timestamps are utilized by features like the extraction logic of CPM Enterprise Analytics. They enable CPM to perform incremental data extractions. For example, CPM can use the timestamps to extract records that were changed during the last week in a weekly extraction process.

To Create Timestamps...

First1213141517192021Last

Tips:  LX | BPCS | M3

Anthony Etzel
/ Categories: Infor LX & BPCS Tips

BPCS/LX TIP OF THE WEEK: 6 POWERFUL STEPS TO WIN WITH AUTOMATION:

  1. Eliminate paper shop packet and distribution of the paperwork to the shop floor.     
  2. Eliminate manual (paper-based) recording activities and the need to key in the transactions.
  3. Easy electronic scheduling by sequence and changing job priorities.
  4. Evaluate differences using actual times compared to standards.
  5. Improve data accuracy and eliminate the need to chase and fix errors.
  6. Practice real-time data reporting to monitor efficiencies and identify problems as they occur.
Previous Article BPCS/LX Tip of the Week: Vendor Maintenance Security Option for Company or Program
Next Article BPCS/LX Tip of the Week: Why Would You Buy a BMW, But Use a Scooter?
Print
32756 Rate this article:
No rating

Contact

Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Contact author

x

Tips: LN | Baan

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.

Categories