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: Company Calendar

Kathy Barthelt 0 74482 Article rating: No rating

Baan uses the company calendar in the following modules to determine the start and end dates for planned orders:

  • Master Production Scheduling
  • Material Requirements Planning
  • Capacity Requirements Planning (All three combined in a single planning module for Baan V and LN)
  • Shop Floor Control

The calendar provides the valid working days, number of shifts per day and the number of hours in a day.

Baan allows for a single calendar for the whole company or for a calendar for each work center.

BPCS/LX Tip of the Week: SFC600 & SFC650

Anthony Etzel 0 86771 Article rating: No rating

These programs are used to capture and post shop floor information. Labor reporting, machine time, etc. can be captured by either program. The key difference is that one will also capture the production receipt and backflush components. Based on your company information / transaction process, one of these programs will most likely be used daily to capture current shop floor data. You can use the shop packet labor ticket for the manual recording, and the keying of the data. Alternatively, you can incorporate an automated method like an MES solution to capture the data and streamline the process.

Crossroads RMC to Exhibit at Manufacturing Matchmaking 2014

Crossroads RMC 0 45033 Article rating: No rating
Crossroads RMC will exhibit at the inaugural Illinois Manufacturing Excellence Center (IMEC) Manufacturing Matchmaking Event 2014 on September 23, 2014. Manufacturers from across the state of Illinois will come together at this event to discuss ways to improve the productivity and competitiveness of Illinois' small and mid-sized manufacturing firms.

BPCS/LX Tip of the Week: What is the bubble number and how do I maintain it?

Anthony Etzel 0 78913 Article rating: No rating

The bubble number is maintained at the component level for each component defined on the Bill of Material. It is an extra user-defined reference number that you can use to re-sequence the maintenance screen display or bills of material listings.

In Infor LX, the system displays the bubble number for the existing child items. Engineering drawings often use a bubble number at the component level on the drawing so that same bubble number can be used on the Bill of Material for a link of the component to the drawing. Alternatively, you may use it simply as a method to sequence the BOM.

Be careful of how you assign the number. It is a good idea to assign the number with a consecutive count by 10 leaving room to allow for component additions to the Bill of Material.

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

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

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

Kathy Barthelt 0 71904 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: Why Define Location Fields in the Work Center File

Anthony Etzel 0 73906 Article rating: No rating

If you setup the “From” and “To” Location fields in the Work Center file, this will determine the locations for material issue transactions and production reporting transactions.

The reporting of the transactions happen through production reporting, JIT600, or using the Shop Floor labor posting, SFC600, or Shop Floor Posting from SFC650.

Remember, any location used in the work center file must first be set up in the location master file. Using an MES solution by-passes the need to key any of the data to Infor LX.

If ERP is plumbing for the Enterprise; How do we unplug it and keep it from making a huge mess?

David Dickson 0 55623 Article rating: 5.0

I have been working with ERP in various roles for over 30 years, directly involved in over a hundred implementations, while my company has been involved with over 300 more. Of course, in many ways the systems we use today are completely different from what we used in the ‘80s – back then it was green screens, simple transaction entry forms, and cumbersome updates (at best) to link what one department did with all the other areas that needed access to that information. Then there were those planning programs that took all the information along with various parameters the users needed to set and told us what to do.

The More Things Change, the More They Stay the Same

First120121122123124125127129

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
/ Categories: Infor LN & Baan Tips

Infor LN & Baan Tip: Cost Component Setup

To break down an item’s standard cost, sales price, or valuation price, use cost components. With cost components, you can compare estimated and actual costs, calculate production variances, and analyze costs in Standard Cost Calculation.

If cost components are set up in a detailed way, detailed records exist in the Item - Calculated Valuation Prices (ticpr2540m000) session and the Item - Standard Valuation Prices (ticpr3540m000) session. Additional financial integration transactions are created because integration transactions are logged by cost component. A detailed cost component setup also causes additional cost details in domains such as Sales and Warehousing. This increases database growth and makes performance worse, especially during production completion and the item receipt process.

Reduce the number of cost components in the effective cost component structure, which is displayed in the Effective Cost Component Structure (ticpr0112m000) session, as much as possible. The minimum number is three aggregated cost components: one for material, one for operation, and one for surcharges. From a performance point of view, the following is advised:

Reduce the number of cost components

  • One operation cost component for all operation rates.
  • One cost component for all subcontracting rates.
  • One cost component for item and warehouse surcharges.
  • One cost component for actual labor rates (in People). Ensure you only use cost components that are required.

Use aggregated cost components
The standard cost is calculated by (detailed) cost component for a multilevel BOM. A similar calculation of valuation prices (actual prices) would result in a price structure with many cost components, especially for manufactured items. In case of a warehouse transfer, issue to WIP, and so on, postings are made for every cost component. However, this detailed cost information does not add functional value in Warehousing. If you aggregate cost components, the number of cost components in financial transactions is reduced. Therefore, aggregate operation cost, material cost, and surcharges to the three cost components that are defined in the Item - Costing (ticpr0107m000) session

If you do not enter a Standard Cost Component Scheme in the Item - Costing (ticpr0107m000) session, production order costs, production order variances, and surcharges are posted by aggregated cost component. This improves performance and decreases database growth.

Previous Article Infor LN & Baan Tip: Project Status Options
Next Article Infor ERP Tip: Top 5 Ways Modern Analytics Reduces Spreadsheet Risk & Inefficiency
Print
57563 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories