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: Purchase Inquiry

Kathy Barthelt 0 83982 Article rating: No rating

In Baan IV Purchase Control, the purchase inquiry procedure enables the user to:

  • Request a specific supplier to submit a quotation on the purchase inquiry for the delivery of an item.
  • Compare the prices and discounts of the quotations that are submitted by different suppliers.
  • Copy the inquiry data to a purchase order.


In LN, you can:

  • Request multiple business partners to submit a quotation on a specific request-for-quotation for the delivery of an item.
  • Compare the received quotations based on the following criteria:
  1. Price
  2. Quantity
  3. Vendor rating
  4. Delivery dates
  5. RFQ subjective criteria
  • Copy the quotation data to a purchase order, a purchase contract, or a price book.

BPCS/LX Tip of the Week: Shop Order Release Date

Anthony Etzel 0 58213 Article rating: No rating

The shop order release date is the date that the shop order is scheduled to be released for production.

If you want to use the backward schedule method, make sure the release date is blank and the due date is maintained.

If you maintain the quantity on the shop order and the due date is prior to the system date, the due date and the release date are the same.

Baan/LN Tip of the Week: Plan Codes

Kathy Barthelt 0 59471 Article rating: No rating

In Baan IV, plan items exist within the context of a plan code. A plan code includes only items of the MPS Item item type. Planned orders are independent of a plan code. Users can compare plan codes by means of the Plan Code Performance Comparison (cprmp4504m000) session.

The scenario concept in Infor LN replaces the plan code concept in Baan IV.

In Infor LN, the basic data for plan items is the same for all scenarios. However, users maintain not only the master plan within a scenario, but the planned orders as well.

For example, for each scenario, Users can specify:

  • Special demand for an item.
  • The availability of resources (in the Scenario – Availabilities (cprpd4160m000) session).
  • The sourcing strategies and supply strategies.

Users can compare scenarios by means of the Performance Indicators (cprao2201s000) session.

Filtec Selects Crossroads RMC for Baan Data Collection

Kathy Barthelt 0 28764 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 63187 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 57338 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 60773 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 66948 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.

First107108109110112114115116Last

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

Infor LN & Baan Tips & Tricks for EXECUTIVES

FINANCE: Use of Electronic Bank Statements

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

  • Bank Statement Workbench (tfcmg5610m100)
  • Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

  1. Convert Electronic Bank Statements (tfcmg5202m000)
    Convert the received bank file to a format that LN can process. LN stores the converted bank statement files in the directory specified in the Path For EBS Archive field of the Bank Relations (tfcmg0510m000) session. In the Pathname EBS File field, you must add the file name. To add the current date to the file name, append a tilde (~) to the file name.

  2. Validate Bank Statements (tfcmg5202m000 / tfcmg5510m000 / tfcmg5511m000)
    Validate the converted electronic bank statement.

  3. Match Bank Statements (tfcmg5210m000)
    Automatically match as many of the imported statements (status Validated) as possible with open items. LN can match the statements with sales invoices, purchase invoices, and anticipated payment documents.

    Matching Options:

    • Match - Surplus on Aging / Unallocated (Default value)
    • Match - Surplus on Unallocated
    • Match - Surplus to be allocated Manually
    • Allow Underpayments
    • Use Payment Difference Tolerance
       
  4. Matching Results (tfcmg2500m100)
    Review the results of the matching process.

    To handle an unmatched amount, you can:

    • Manually add an unallocated payment or receipt line.
    • Reconcile the surplus with remaining open entries of the business partner.
       
  5. Post Bank Statements (tfcmg5210m100)
    Post the bank transactions to the General Ledger.

    Update the business partner’s bank account number and other details in the Bank Account by Pay-by Business Partner (tccom4115s000) session, based on the details read from the bank statement file.

OPERATIONS: What is Statistical Inventory Control (SIC) and How Does It Work?

Statistical Inventory Control (SIC) is an inventory-controlled order system designed to maintain stock levels based on predefined thresholds, rather than being demand-driven like EP (Enterprise Planning). Since SIC relies on inventory levels, it may lead to higher stock levels. To minimize financial risks, SIC is best suited for:

  • Low-cost items.
  • Items with predictable demand or short lead times.


Applications of SIC

  • Low-Cost Items: Particularly effective for inexpensive goods.
  • Predictable Demand or Short Lead Time: Suitable when demand patterns are stable or lead times are minimal.
  • Warehouse-Specific Planning: Useful for planning by warehouse rather than across the supply chain.
  • Trading Industries: Commonly employed in sectors like supermarkets.
  • Immediate Demands: Effective for items required immediately by customers.
  • Ease of Use: Simple to implement and manage.


Limitations of SIC

  • Does not account for dependent demand from planned orders (e.g., MPS/MRP/INV).
  • Does not generate distribution orders.
  • Ignores time-phased planned orders.
  • Lacks forecast consumption techniques.
  • Uses both nettable and non-nettable warehouses.

How SIC Works

SIC operates based on the Reorder PointStock Levels, and Order Method.

Triggering SIC

When Economic Stocks (calculated as On-Hand Inventory + On-Order – Allocated Stocks) on the Horizon Date fall below the Reorder Point, SIC triggers the creation of:

  • Planned Purchase Advice.
  • Planned Production Advice.


Order Methods in SIC

The quantity for these advices is determined by the Order Method, which can be one of the following:

  • Replenish to Maximum Stock
  • Fixed Order Quantity
  • Economic Order Quantity (EOQ)
  • Lot-for-Lot

Example: SIC in a Supermarket

Scenario: Managing stock for Ice Cream (1 Kg Pack)

  • Current Stock: 10 PCs
  • Reorder Point: 5 PCs
  • Safety Stock: 2 PCs
  • Lead Time: 1 Day
  • Order Method: Replenish to Maximum (Maximum Stock: 20 PCs)
  • Maximum Anticipated Consumption: 3 PCs/Day

Process:

  1. Customer purchases reduce the stock.
  2. When stock reaches 5 PCs, SIC is triggered.
  3. A Purchase Advice is generated for 15 PCs to replenish stock to the maximum level (20 PCs).
  4. During the lead time (1 day), the remaining 3 PCs (excluding Safety Stock) meet customer demands.
  5. In emergencies, Safety Stock can also be utilized.

Statistical Inventory Control offers a practical approach for managing inventory levels, particularly in industries with predictable demand or fast-moving items. However, its limitations make it less ideal for complex or time-phased planning scenarios.

TECHNOLOGY: Archiving Data from tipcs300 and ticst300 Tables

1. Archiving tipcs300

  • Using Session tipcs2260m000:
    • When archiving PCS projects, selecting the "Archive Financial data" option ensures that:
      • Records in tipcs300 are archived to the archiving company.
      • Records are deleted from the original company.
    • If records remain in tipcs300:
      • They may belong to projects that have not been archived.
      • The project may have been archived without selecting "Archive Financial data."
    • Verify there are no errors during the archiving process.
  • Using Session tipcs3500m001:
    • The session "Delete Financial Transactions by Project" can delete records from tipcs300.
    • Note: This session is not for archiving; it removes records without copying them to the archiving company.

2. Archiving ticst300

  • Using Session ticst0250m000:
    • The session "Archive Production Orders" allows:
      • Archiving and deleting records from the original company.
      • Only deleting records from the original company.
    • When executed:
      • Records in ticst300 associated with archived orders are removed.
      • Remaining records belong to unarchived orders.

Previous Article Infor LN & Baan Tips & Tricks for TECHNOLOGY: Archiving Data from tipcs300 and ticst300 Tables
Next Article Infor LN & Baan Tips & Tricks: Action Required - Infor LN Cloud Edition - Fonts Update!
Print
56008 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories