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 8582 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 11553 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 8903 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 10392 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 8191 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 17190 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...

First567810121314Last

Tips:  LX | BPCS | M3

Anthony Etzel
/ Categories: Infor LX & BPCS Tips

BPCS/LX Tip of the Week: Work Center & Machine Locations

For either file, you must specify a valid location code as defined in the Location Master File.

If the machine master locations are blank, then the work center locations are used. There are cases where you may want to do a combination between the two in defining the locations.

Let’s say the end item has one operation. The operation is at work center 510 and Machine A is in the work center. You have locations setup in both the Work center file and the Machine master File. You report 100 complete at the work center without specifying the machine.

In this case, the inventory will be processed based on the locations defined in the work center file. If the transaction included the machine number, then the locations in the machine file would be used.
Previous Article BPCS/LX Tip of the Week: Inventory Control
Next Article BPCS/LX Tip of the Week: Shop Order Status
Print
76465 Rate this article:
4.0

Contact

Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Contact author

x

Tips: LN | Baan

Users can personalize sessions and apply special formatting to the data displayed in sessions. The personalizations and formatting settings that are specified by the users are stored on the LN server. Administrators can maintain these settings.

  • Session personalizations

    Users can personalize sessions in various ways. users can, for example, hide fields, change labels, customize the toolbar, and move fields to another tab. Administrators can maintain the personalizations defined by the users. For example, an administrator can export personalizations to an XML file, import personalizations from an XML file, and copy personalizations to another user, to a DEM role, or to a company number.

  • Report personalizations

    You can use the Report Designer (ttstppersrep) to personalize the layouts and style of reports, without modifying the standard reports or using an external reporting solution. The changes are stored as personalizations.

    You can also generate new reports that are based on a selection of fields from the application data model. These reports are generated in the extensibility package. You can personalize these reports in the Report Designer (ttstppersrep), or modify them in Infor LN Studio.

    For details, see the Infor LN Report Designer Development Guide
     
  • Conditional formatting

    users can define conditions to apply special formatting to the data displayed in LN sessions. The users can define multiple conditions per session and different types of formatting, such as a specific color for particular fields or rows, and a warning symbol for particular rows. Administrators can maintain the formatting settings specified by the users and can define system-wide formatting settings.

  • If Finances 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.

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 project that is not yet archived. When the PCS project is archived, the purchase data is also archived and you can delete the purchase order.
  • A consignment replenishment order is not yet consumed completely.
  • The invoice is yet to be completely matched and approved.
  • The invoice amount is not yet inserted as turnover history.
  • The sales order or service order that is linked to the purchase order line, and for which an internal invoice must be sent from the purchase office to the sales office or service office, is not yet invoiced. In this case, you cannot delete the purchase order line before the sales order or service order is invoiced.

Categories