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: Default Order Frequency

Kathy Barthelt 0 84278 Article rating: No rating

In Baan IV, requirements for an MPS item with the order method lot-for-lot result in daily planned MPS orders.

For example, if a plan period contains 10 working days and the net requirements for an item in that period is 2000 pieces, an MPS planning run generates one planned MPS order of 200 pieces for each working day in the plan period.

In Infor LN, requirements for a planned item with the order method lot-for-lot result in one planned order per plan period.

For example, if a plan period contains 10 working days and the net requirements for an item in that period is 2000 pieces, a master planning run will generate a single planned order of 2000 pieces for the first working day in that plan period. To influence the order quantity of the planned orders, enter appropriate values in the Maximum Order Quantity field and the Order Interval field in the Items – Ordering (tcibd2500m000) session or choose a fixed order quantity.

Crossroads RMC Releases NextTrack Sales – Sales Analysis Tool for Baan, Infor LN and IBM i

Kathy Barthelt 0 32715 Article rating: No rating

Crossroads RMC is proud to announce the official release of NextTrack Sales – a sales analysis tool for Baan, LN, and IBM i. NextTrack Sales allows you to get the “big picture”, or get down into the finer details. The tool provides a sophisticated pivot grid and charting functionality, export to Excel, PDF printing, and emailing capabilities to bring your sales data to life. Analyze your Baan Sales data to examine trends, identify market opportunities, and much more. Click here for more details.

Mount Olive Pickle Chooses Crossroads RMC for BPCS Data Collection

Anthony Etzel 0 29047 Article rating: 5.0

Mount Olive Pickle, a leading producer of pickles, peppers, and relishes in the United States, has chosen Crossroads RMC as their solutions vendor for data collection and manufacturing production reporting. In the first phase of the project, the Crossroads team will implement the Inventory Visibility Data Collection software connected to BPCS. The transactions to be implemented include PO Receipts, Transfers, Component Issues, Cycle Counting, and Production Receipts.  

CROSSROADS RMC MEMBERSHIP IN COMMON USER GROUP / EXHIBIT AT COMMON CONFERENCE

Crossroads RMC 0 28017 Article rating: No rating

The  Annual Meeting is COMMON’s largest educational event of the year, with four full days of in-depth IBM i, AIX, and Linux-related education that includes all-day pre-conference workshops, open labs, and a wide variety of regular-length sessions. It is the annual meeting of the COMMON membership and the largest gathering of the Power Systems user community. Come see us in Booth 203.

 

Crossroads RMC is also proud to announce our membership in COMMON for 2016. We look forward to partnering with COMMON and providing valuable content to their user community and sharing in dialogue with users across the country.

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

Kathy Barthelt 0 65926 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: Optionally Include Tax Amounts In Order Balance

Kathy Barthelt 0 81275 Article rating: No rating

In Baan IV, the order balance amount always includes the tax amount. Consequently, the tax amount must be recalculated every time an order line is modified in order to update the balance correctly. If the tax provider is activated, this requires an API call for every re-calculation of tax.

In Infor LN, users can select or clear the new Include Tax in Order Balance check box in the COM Parameters (tccom0000s000) session to indicate whether users want to include tax amounts in the order balance amount. This parameter has an effect on various sessions in Order Management.

BPCS/LX Tip of the Week: Changing the Master Schedule

Anthony Etzel 0 54042 Article rating: No rating

You can change your master schedule by specifying the type of master schedule update to perform. You can run a Net Change or Regenerative Schedule.

You also have the ability to clear the lower level requirements out of the Planned and Firm-Planned Order file.

First105106107108110112113114Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

[EasyDNNnews:IfExists:Event]
[EasyDNNnews:IfExists:EventRegistration][EasyDNNnews:EventRegistration:RegisterButton][EasyDNNnews:EndIf:EventRegistration] [EasyDNNnews:IfExists:Payment][EasyDNNnews:Price][EasyDNNnews:EndIf:Payment] [EasyDNNnewsLocalizedText:Eventdate]: [EasyDNNnews:EventDate] [EasyDNNnewsLocalizedText:ExportEvent] [EasyDNNnews:IfExists:EventLocation]

[EasyDNNnewsLocalizedText:EventLocation]: [EasyDNNnews:EventLocation]

[EasyDNNnews:EndIf:EventLocation] [EasyDNNnews:IfExists:EventRegistration]
  • [EasyDNNnewsLocalizedText:NumberOfAttendants]: [EasyDNNnews:EventRegistration:NumberOfAttendants]
  • [EasyDNNnewsLocalizedText:MaxNumberOfTickets]: [EasyDNNnews:EventRegistration:MaxNumberOfTickets]
  • [EasyDNNnewsLocalizedText:NotUsedTickets]: [EasyDNNnews:EventRegistration:NotUsedTickets]
  • [EasyDNNnews:IfExists:Payment]
  • [EasyDNNnewsLocalizedText:Price]: [EasyDNNnews:Price]
  • [EasyDNNnews:EndIf:Payment]
[EasyDNNnews:EventRegistration:InfoMessage] [EasyDNNnews:EndIf:EventRegistration] [EasyDNNnews:IfExists:EventSignUp]

[EasyDNNnewsLocalizedText:AreYouGoing]

[EasyDNNnews:SignUpActionBar]
[EasyDNNnews:EndIf:EventSignUp]
[EasyDNNnews:EndIf:Event]
Kathy Barthelt
/ [EasyDNNnewsLocalizedText:Categories]: [EasyDNNnews:Categories]

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

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories