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

BPCS/LX Tip of the Week: The Item Master Requirements Code

Anthony Etzel 0 75901 Article rating: No rating

In the Item Master File, the requirements code is used to specify the type of demand for the item. Planned order requirements are determined from the type of demand. If the requirements code is left blank, the planning systems treat the item as a sum code (3).
 

Other options for the field are:


1 = Dependent demand that is indirectly generated from the parent item requirements.

2 = Independent demand generated from customer orders and forecasts.

3 = The Sum of both independent and dependent demand.

Grindmaster Cecilware Selects Crossroads RMC For Baan IV / Davisware Integration

Crossroads RMC 0 40919 Article rating: No rating

Grindmaster Cecilware, a leader in the development of products for the food and beverage industry, has selected Crossroads RMC to integrate their Baan IV system to Davisware Global Warranty. Davisware is an electronic customizable online solution that fits almost any warranty process. Grindmaster’s customers will be able to access the Davisware software online and process warranty claims which will then automatically feed back into the Baan IV system for further review and processing. The integration is expected to go live in Q1 of 2015.

Huf North America Goes Lives With Next Phase of RMC3 Data Collection

Crossroads RMC 0 42148 Article rating: No rating

Huf North America, a global leader in the production of mechanical and electronic key systems, lock sets, steering locks, and remote control systems for the automotive industry, has gone live with phase 2 of their Crossroads RMC data collection implementation. This go-live included Report Orders Complete, Labor Reporting, Material Issue, Inventory Transfers, barcode label modifications, as well as custom applications for their Paint / Polishing operations. This go-live was paired with the expansion of Huf’s Plastic Injection Molding and Paint Facility in Greeneville, TN. The next phase of this project will include the extension of the Crossroads RMC solution into Huf’s facility in Mexico.

Baan/LN Tip of the Week: Product Configurator - Part 2

Baan Tips

Kathy Barthelt 0 107592 Article rating: 3.0
Who gets involved?
  1. Most commonly Engineering is involved in writing the rules, creating the bills and routings.
  2. Sales or Customer Service determines the questions and the order they are asked in.
  3. Sales or Customer Service determines the rules for the pricing.
  4. Sales, or Customer Service, and Engineering work together in determining the part number, description and text.

What are the steps?

  1. You must start by defining the features and options (questions and answers) and the order in which these are asked. We work this out first using sticky notes and large easel paper. Normally during the process we find that we want to move these questions around. Setting them down on paper makes the process of getting the data into Baan much more efficient. We also then have a record of what decisions were made prior to entering the data. This is normally a joint effort of Engineering and Sales. This is required and must be the first step.
  2. Constraints for features and options. These are the rules for determining what questions are asked and which options are allowed. This is generally done by Engineering or whoever is responsible for the configurator. This is required.
  3. Generic Bill of Material. All possible bill options are entered here and constraints are written to determine which options are selected based on the answers to the questions. This is generally done by Engineering or whoever is responsible for the configurator. This is a required step.
  4. Generic Routing. Similar to the bill of material, but used for generation of the routing steps. This is generally done by Engineering or whoever is responsible for the configurator. This is optional.
  5. Generic Item Data. This consists of creating custom item numbers, descriptions, text, material, size or standard fields in the custom item master. This is generally done by Engineering or whoever is responsible for the configurator though Sales may have some involvement. This is optional.
  6. Generic Pricing. This is used to calculate the selling price based on the answers to the questions. This is normally a responsibility of Sales or whoever determines the pricing. This group is also trained on writing the constraints for this section only. This is optional.

BPCS/LX Tip of the Week: How To Capture Re-Work Time (Part 1)

Anthony Etzel 0 86370 Article rating: No rating
In SFC600, there is no code to capture the time spent on re-work. Re-work is usually at a specific operation, or when the part is finished and QC determines that re-work is required in order to pass inspection. You are faced with deciding on how to report the additional labor time.

Do you continue to report it against the operation, or create a re-work shop order?

If you are re-working through a specific operation you can capture the time as run labor with the SFC600 program. Now you need to deal with the variance of actual to standard time and what impact this has on costing.

BPCS/LX Tip of the Week: Configuration Management

Anthony Etzel 0 81382 Article rating: No rating

Make to Order? No problem if you use the Configuration Management System. This LX product allows you to define and configure a make to order product during Customer Order Entry. Basically, you have the option to create different products under the same common product item. You will get two completely different common end items that are configured from the same common parent.

The customer orders are planned and turned into shop orders for each end item with all the associated components. With an MES solution in place, the shop order side is easy to schedule and allows you to manage the shop floor.

Baan/LN Tip of the Week: Product Configurator - Part 1

Kathy Barthelt 0 73237 Article rating: No rating
What is it?
The configurator consists of a set of features (questions). The options (answers) to these questions then are used to generate the custom bill of material and routing. These questions may be answered at the time of order entry, prior to order entry (in a project or quote) or after order entry (in the project). The order of the questions need not have any relationship to the bill of materials. The configurator may also calculate the selling price, create a unique “smart” item number, custom description and text. Simple rules are used to interpret the answers.

Who uses the configurator?
Companies whose products have options. The configurator eliminates the need for part numbers for all combinations of options. The configurator ensures that the pricing and bills are correct. The configurator also keeps statistics on the frequency the options are selected.
First117118119120122124125126Last

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: All About Invoicing Methods

Invoicing Methods are a set of parameters that define the types of orders and order lines that can be collected on an invoice, the type of invoice to be generated and the costs to be aggregated on Project invoices and Service invoices.

If options to combine tax codes, departments, sales representatives' line of business area, etc... are checked, LN will combine all available transactions ready to be invoiced that have different tax codes departments, sales representatives, etc...into only one invoice.

If options to combine sales orders, sales order types, and shipments are checked then all sales orders that are created for the same business partner where the shipment and/or sales order type is different will be combined into one invoice.

For example:

  1. If sales order SLS001 is created for BP BP1000 with 2 lines where each line has a different shipment number, and the invoice method is combining shipments, both lines will be part of the same invoice. If the option to combine shipments is not checked then LN will create an invoice per shipment.
  2. If sales order SLS001 is created for BP BP1000 with 2 lines and 2 different shipment numbers and sales order SLS002 is created for the same BP with a cost item, LN will create one invoice for both orders if the option to combine sales orders and shipments is checked. If only the option to combine sales orders is checked then 3 different invoices will be created as all 3 lines will have different shipment numbers. If they have different sales order types and this option is not checked on the invoice method session then also 3 invoices will be created but if it is checked along with sales order and shipment number then only one invoice will be created.
  3. If we take scenario 1 again and both lines have different tax codes and the option to combine tax codes is not selected then LN will create a separate invoice for each line based on the tax code.
     

Note: In the case that the Business Partner Tax Country is different, even if we select combine tax codes, the system will create a separate invoice based on the Business Partner Country to full the statutory compliances for that BP country.

Previous Article Infor LN & Baan Tip: Cash Flow Functionality and Setup
Next Article Infor LN & Baan Tip: Why was the session "General Ledger Diagnostics Workbench" built?
Print
58389 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories