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 Day: Cycle Counting Part 2

Anthony Etzel 0 78113 Article rating: No rating

Understanding: The Cycle Count Alternative

The best way to cycle count is to count the same number of items each day and at the same time each day. The goal is to count your “A” items 4 times a year. The “A” items should be those item that are about 80% of the total inventory value and 20% of the total items. Consider creating your own cycle count schedule then instead of using the cycle count transaction, use the inventory adjustment transaction. The item balance is changed at the time the transaction is keyed. The transaction list can be used for the reconciliation process.

Baan/LN Tip of the Day: Company Calendar

Kathy Barthelt 0 110116 Article rating: 5.0

Baan uses the company calendar in the following modules to determine the start and end dates for planned orders:

  • Master Production Scheduling
  • Material Requirements Planning
  • Capacity Requirements Planning
    (All three combined in a single planning module for Baan V and LN)
  • Shop Floor Control

The calendar provides the valid working days, number of shifts per day and the number of hours in a day.

Baan allows for a single calendar for the whole company or for a calendar for each work center.

BPCS/LX Tip of the Week: Cycle Counting Part 1

Anthony Etzel 0 84925 Article rating: No rating

Understanding: The Cycle Count Transaction

If you rely on BPCS to provide you with a cycle count list, the number of items could vary from day to day from a few items to count, to several. So the person doing the cycle counting may spend a few minutes to a few hours counting items. After the cycle count is complete, the balances are not changed until the reconciliation is complete. This process could take some time before the balances are changed.

The cycle count transaction process is similar to the physical inventory transaction process.

Baan/LN Tip of the Week: GRINYA

Kathy Barthelt 0 149854 Article rating: 3.0
GRINYA is one of the more complex issues in ERP Finance. GRINYA is the tracking via ledger account of the value of items received on a purchase order that have not been matched to a supplier invoice.

Baan solutions for Baan IV and V were incomplete. To take full advantage of the current GRINYA reconciliation process, check Infor solution #107147, which contains the GRINYA user manual and a link to download the software for your version of Baan. For ERP LN, look at Document Code U8942C US.

It is called User Guide for Reconciliation and Analysis. If you are not running the latest GRINYA solutions, patching will require a good amount of time in filling the Interim tables this solution runs from. Infor has posted several procedural write ups, so check the Support Site and read up before tackling this for the first time.

BPCS/LX Tip of the Week: Work Center & Machine Locations

Anthony Etzel 0 84500 Article rating: No rating
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.

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

Anthony Etzel 0 80345 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.

First126127128129131133134135Last

Tips:  LX | BPCS | M3

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

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories