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 22776 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 40015 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 37728 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.

RSS
First137138139140142144145146Last

Theme picker

Tips:  LX | BPCS | M3

TECHNOLOGY: Facility Security Ranges

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

FINANCE: Expiration Date for Quotes and RMAs

A Cancel-by-Date has been added to the Quote Header and RMA Header panels. This optional field can limit how long a quote or authorization to return items for credit is valid.  

For quotes, this enhancement provides an optional end date for the quote. For RMAs, it provides an optional date by which the customer must return the items to receive the credit listed on the RMA.

The Cancel-By-Date prints on the Order Acknowledgement and RMA Acknowledgement to inform the customer of this important limitation to the quote or return authorization. 

An Order Entry user cannot copy the quote to create a new order if the Cancel By Date has caused the quote to expire.

OPERATIONS: Default Split Salesperson to Customer Orders

Sales commissions are based on combinations of the Primary, Split, and Line-Level salesperson and the commission codes defined for the customer and item. You can now define the Split Salesperson in the same master files as the Primary Salesperson. While the Primary Salesperson is mandatory, the Split Salesperson is optional. It defaults during Order Create using the identical hierarchy as Primary Salesperson. Using Split Salesperson provides more flexibility in the calculation of sales commissions. The ability to define a default Split Salesperson improves the accuracy of sales commission qualification and calculation and reduces maintenance and adjustments necessitated by corrections.

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

12345678910Last

Theme picker

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
20508 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

x

Categories