Infor ERP Tips and Infor ERP News for Infor LX, BPCS, Infor ERP LX, Infor LN, Infor ERP LN, Baan, Infor M3, and Movex

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

Filtec Selects Crossroads RMC for Baan Data Collection

Kathy Barthelt 0 30870 Article rating: No rating

Filtec, a leading provider of in-line inspection solutions for the food, beverage, and pharmaceutical industries, has selected the Web Collect, formerly RMC3 data collection solution from Crossroads RMC for their Baan IV system. Filtec plans to implement Labor Reporting and Report Operations Complete as part of this project with the goal of eliminating manual data entry and gaining better visibility to gap time. The project is scheduled to go live in early November 2015.

BPCS/LX TIP OF THE DAY: MATERIAL REQUIREMENT DATES AND LEAD TIME OFFSETS IN MRP

Anthony Etzel 0 67030 Article rating: No rating

The system automatically performs offsets for requirements dates for components in the MPS/MRP calculations. It also performs offsets for calculation of material need dates at the time that shop orders are released.

To calculate the offset, the system takes the parent lead time from the Item Master and adjusts it by the bill of materials offset (plus or minus) for the component. This gives the lead time days for that specific component. The system starts with the due date of the parent and backs up and skips all non-workdays in the shop calendar.

Note that the offset calculation uses only calendar records that have a blank work center (the calendar record applies to all work centers). See the information for the Shop Calendar Maintenance program, SFC140, in your Shop Floor Control documentation for shop calendar details.

Baan/LN Tip of the Week: Data Sizing Moving to LN

Kathy Barthelt 0 71266 Article rating: No rating

The Infor LN database must be created with the appropriate size. For example, if at least 150 GB is required for a year, create the database with the required size from the beginning. Do not let the size increase to the required size and cause additional fragmentation in the database and the NTFS volume.  Set the autogrowth to a minimum of 10 percent or 1 GB (for each extent) to avoid fragmentation on file system level. Never use the default extent size of 1 MB.

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

Anthony Etzel 0 63903 Article rating: 3.0

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.

Baan/LN Tip of the Week: SIC Planning for MRP/MPS Planned Items

Kathy Barthelt 0 74767 Article rating: 3.0

If you have a parts warehouse and prefer to use SIC for planning (re-order point) but need to use MRP/MPS planning for production, create a non-nettable warehouse for the parts warehouse and run the SIC plan against that warehouse.

When running the SIC plan, be sure to set the Order System to “MPS to MRP” for Baan IV and to “Planned to Planned” for Baan V and LN.

Using this method you keep the parts inventory out of the production planning and in the hands of the parts warehouse planner.

BPCS/LX Tip of the Week: Indirect Time Reporting

Anthony Etzel 0 62821 Article rating: No rating

In Infor LX, there are two ways to enter indirect labor. You can use either SFC600 or SFC650.

  • If you use SFC600 and enter a reason code for the indirect labor, the reason you entered is written to the Labor Ticket file.
  • If you use SFC650 and enter a reason code for the indirect, the reason code is not written to the labor Ticket file.

In either case, the reason code is not validated from the transaction file because there is no indirect transaction code. The indirect code that can be setup is machine downtime. If you need to validate and track indirect by reason and validate the reason code, then you may want to explore an MES solution that works with Infor LX.

Baan/LN Tip of the Week: Differences Between Constraint Planning in Baan IV and Enterprise Planning in LN

Kathy Barthelt 0 61354 Article rating: No rating

In Baan IV, a distinction is made between the actual ERP system and a separate planning tool which contains the Constraint Planning package. This tool was intended to work with any ERP system, not just with Baan IV. The Enterprise Planning package is now considered to be a package like any other package in Infor LN.

Users of Baan IV could choose whether they wanted to plan their supply in one of the following ways:

  • By using the MPS and MRP modules in the Manufacturing package.
  • By using the RPD and RMP modules in the Constraint Planning package.

Users of Infor LN can only use the Enterprise Planning package. The distinction between the MPS items and MRP items has been abandoned. In Infor LN, all items can be planned by using a combination of master-based planning methods and order-based planning methods.

Baan/LN Tip of the Week: Setting Up New Employees in LN

Kathy Barthelt 0 59990 Article rating: No rating

In LN, the People package is used to register the employee’s hours and expenses. To support the People package, the Employees - General (tccom0101m000) session only contains the general employee data.

The title of the Employees - General (tccom0101m000) session was changed to Employees – General (tccom0101m000).

From the Employees - General (tccom0101m000) session, users can start the following sessions to define the more specific employee data:

  • Employees - People (bpmdm0101m000).
  • Employees - Project (tppdm8101m000).
  • Employees - Service (tsmdm1140m000).
  • Skills by Employee (tcppl0120m000).
  • Employees by Team (tcppl0150m000).
  • Roles by Employee (tcppl0170m000).

After users define the employees, users can also start the listed sessions from the Employees Dashboard (bpmdm0101m100) session in People.

First119120121122124126127128Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

Crossroads RMC

End of Year E R P Checklist: Streamline Your Transition to the New Year

The end of the year is a busy time for everyone, but a little preparation can make the start of the next year smoother and more productive. Here's a checklist broken out by the department to help optimize your ERP system as you wrap up this year.

All Departments End of Year Checklist

_____1. Strategic ERP Review

  • Review and Update Reports and Dashboards
    • Evaluate standard reports and dashboards to ensure they align with current business requirements.
    • Adapt them to reflect changing priorities so the information remains relevant and actionable.

_____2. ERP Support and Maintenance

  • Address Outstanding Support Issues
    • Reach out to Crossroads RMC for unresolved support concerns or system issues.
    • Collaborate to resolve lingering problems and clear your to-do list before the year ends.

_____3. Training and Consulting Services

  • Assess Team Training Needs
    • Conduct a skills gap analysis to identify areas where your team may require additional ERP training.
    • Allocate resources for consulting services to help your team remain efficient and effective with the ERP system.

_____4. Future Investments

  • Evaluate New ERP Features or Modules
    • Review potential ERP investments to support business growth.
    • Align new features or modules with the organization’s current and future needs to maximize ROI and operational efficiency.


IT/Technology Checklist

_____1. Data Cleanup

  • Perform data deduplication to eliminate redundant entries.
  • Validate existing data to ensure accuracy and reliability. This reduces errors and boosts confidence in reporting.

_____2. Archive/Remove Obsolete Data

  • Archive or delete outdated data to improve system performance and reduce database clutter.
  • Streamlined data management enhances system usability and reduces search inefficiencies.

_____3. Monitor System Performance

  • Review system logs and performance metrics to identify bottlenecks.
  • Address any recurring lags or slowdowns to improve overall system efficiency.

_____4. Review User Access Controls

  • Audit user roles, permissions, and access rights for accuracy.
  • Remove or update access for users with altered responsibilities or those no longer with the organization.
  • This step mitigates cybersecurity risks and ensures compliance with data governance policies.

_____5. Test Emergency Recovery Procedures

  • Perform a test run of backup and recovery protocols to verify their effectiveness.
  • Ensure all critical data can be restored in the event of a disaster.

_____6. Prepare for Date-Dependent Processes

  • Audit scheduled jobs, scripts, and automation with hard-coded dates.
  • Update these dates to reflect the upcoming year to avoid disruptions in processes.

_____7. Bonus IT Tasks

  • Communicate planned system downtimes with all stakeholders in advance.
  • Document any changes made to the system during this period for future reference.
  • Encourage feedback from end-users on potential system improvements.

Operations Checklist

_____1. Critical Data Accuracy

  • Ensure critical data, such as inventory levels and customer information, is up-to-date and accurate to support efficient facility operations.
  • Remove discontinued items.
  • Delete sold purchase receipts.
  • Clear lot attributes for sold lots.
  • Non-Manufacturing Environments: Update the standard cost field based on current cost.

_____2. Inventory Management

  • Conduct a full physical inventory and update quantities before year-end or establish a cycle-counting program to maintain accuracy.
  • Prepare users for year-end completion of all inventory adjustments, receipts, and invoicing.
  • Determine processes for handling new-year transactions without immediate posting.

_____3. Purchase Orders & Contracts

  • Close out all purchase contracts and purchase orders (POs) to prevent further receipts against any contract line items.

_____4. Costing & Manufacturing Tasks

  • Decide on new standard costs for the upcoming year (for Manufacturing environments).
  • Establish cutoff dates for removing archived BOMs and closed/canceled manufacturing orders.

_____5. LX-Specific Tasks

  • Run PRF900 to update performance measurements and purge closed shop orders.

_____6. Fixed Assets & Depreciation

  • Review and update the depreciation schedule for fixed assets.
  • Verify depreciation expenses for the year have been accurately recorded.
  • For any new assets added during the year, ensure they are included in the depreciation schedule.

Finance Checklist

_____1. Period Closing & Reconciliation

  • Close financial periods and reconcile accounts to ensure financial data consistency and readiness for audits, tax filings, and other financial processes.
  • Set up financial periods for 2025 before the year begins.
  • Open the January 2025 period.
  • Finalize all outstanding transactions from 2024.

_____2. LN-Specific Tasks:

  • Perform a soft-close for any open periods in 2024.

_____3. LX-Specific Tasks:

  • Copy the CEA Book for the new year, ensuring all Journal Sources are set up. This ensures all required records are in place.
  • Run ACP920 (1099 Report) before ACP910 (Year End Close), as the Close Program clears 1099 Payments History.

_____4. Financial Cleanup

  • Address any old sales invoices and ensure they are properly closed.
  • Rectify any outstanding financial integration errors.
  • Set up and test new integration mappings for 2025 in a test environment.
  • Review and update jobs to ensure they are configured correctly for 2025 processing.
  • Identify purchase invoices for cash-flow management that won’t be paid until 2025.

_____5. Payroll Review

  • Verify employee payroll records and reconcile them with financial statements.
  • Ensure all employee information is up-to-date, including unpaid sick leave and vacation time, and carry over or adjust as necessary.

_____6. Accounts Receivable & Payable

  • Resolve any outstanding issues or unpaid invoices in customer or vendor accounts.
  • Record all payments and receipts to maintain accurate financial data.
  • Review outstanding receivables for potential bad debts.
    • Decide whether to carry them over into the new year.
    • Adjust the allowance for bad debts as necessary.

_____7. Bonus Financial Tasks

  • Verify that ERP calendars are set up for the new year with holidays correctly indicated.
  • Ensure proper mapping and testing of financial processes to avoid disruptions in the new year.

Taking these proactive steps will set your ERP system up for success in the coming year.

Print
9271 Rate this article:
5.0
Crossroads RMC

Crossroads RMCCrossroads RMC

Other posts by Crossroads RMC

Contact author

x

Categories