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

What does OTTO do that finite scheduling doesn’t?

Anthony Etzel 0 32564 Article rating: 5.0

Finite scheduling identifies what constraints need to be overcome and it provides the best schedule given the constraints. But the objective is not only to overcome or remove the constraint but to prevent the constraint from even occurring. Only people can anticipate and overcome current constraints, and this requires time for analysis and people to apply their knowledge to the data. OTTO removes the non-value-added tasks of extracting and manipulating data and provides visibility to support people in solving near-term, complex problems. 

Crossroads RMC welcomes MBL (USA) Corporation

Anthony Etzel 0 31763 Article rating: 5.0

Crossroads RMC welcomes MBL (USA) Corporation as our newest Data Collection and Warehouse Management client.

MBL (USA) Corporation, with headquarters located in Ottawa, Illinois, manufactures all types of V-Belts, V-Ribbed Belts, Timing Belts, and Variable Speed Belts for both original equipment and service parts in the automotive, recreational, and industrial markets. In addition to supplying North, Central and South America markets, products are exported to countries worldwide. Their corporate parent is Mitsuboshi Belting LTD located in Japan.

MBL (USA) Corporation’s objective was to improve inventory visibility, eliminate paperwork, and use a bar code scanning solution to manage warehouse inventory and eliminate the manual process for inventory warehouse transactions.

Our discovery was able to highlight improvements to streamline the process in the warehouse and improve inventory visibility. Crossroads RMC is a reseller and support partner for TouchPath Warehouse Management which is integrated to MBL (USA) Corporation’s ERP/LX software. TouchPath Warehouse Management provides the insight into your inventory and the warehouse management tools to help you increase customer satisfaction and reduce costs.

We are proud to have MBL (USA) Corporation as our newest client and look forward to being a strategic partner and support their company growth and success.

Infor LX & BPCS Tip of the Week: Inventory Transfers for Outside Operations

Anthony Etzel 0 59185 Article rating: 5.0

This enhancement allows users who currently perform outside operation processing in shop floor programs to manage the transfer of components used in the outside operations to the vendor’s designated warehouse.

This enhancement provides modified and new INV511D screens and adds new logic to allow the user to identify all shop orders that have components linked to outside operations or to identify all the components linked to an outside operation on a shop order. The shop orders can be filtered by either a date range or by a specific vendor.

Inventory Transfers for Outside Operations enhances the management of external operations by providing screens that simplify the selection of the shop orders or items to transfer to a vendor.

Transfers to the vendor warehouse are performed in the Inventory Transfers, INV511D, screens.

Infor LX / BPCS Tip of the Week: Optional Authority to Maintain Reason Codes

Anthony Etzel 0 55165 Article rating: 5.0

This enhancement allows users to update Reason Code Maintenance, INV140D1, for Transaction Effects that they are not authorized to in any other programs. A new system parameter was added to Inventory Parameters, INV820D. The enhancement allows users who do not actually perform transactions in Infor LX to maintain the reason codes for the transactions.

Infor LN / Baan Tip of the Week: Deleting Records

Kathy Barthelt 0 81809 Article rating: 5.0

To improve performance and reduce database growth, deleting records is highly effective. The disadvantage of deleting records is that data is no longer available. Usually, however, not all records need to be saved. For example, line activities are stored by warehouse. Normally, you do not need to keep these records. Therefore, after closing a warehouse order, line activities can be removed. The User's Guide for ERP LN Archiving describes several sessions you can use to delete old data. Other data such as items and business partners can be reviewed once in a while, after which you can delete the data you no longer need. For every order and contract table a session is available to archive and delete old orders. In these sessions, you can specify several characteristics to select the orders to be removed, such as date or status. Run these sessions on a regular basis.

Explore your IDF programs

Anthony Etzel 0 34029 Article rating: 5.0

If you haven't already, you may want to start to explore your IDF programs. Currently they provide the replacement for the 300 series inquiry programs. In addition, navigation drill downs are far superior to any green screen presentation of the data.

Consistently meet customer commitments without last minute surprises

George Moroses 0 23912 Article rating: 5.0

What if you had a solution that allowed you to consistently meet customer commitments without last-minute surprises and unexpected extra effort and cost?

We do this by preventing slippage — slippage is any break in the plan that disrupts both normal material flow and the rhythm of the plant that is preventable by timely key user intervention.
Click here to learn more about OTTO, On-Time Orders.

First7071727375777879Last

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

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories