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: Negative Inventory

Kathy Barthelt 0 1101 Article rating: No rating

If Location Control is turned on in Baan IV, then inventory should never be negative.

If Location Control is not turned on in Baan IV, and the parameter “Negative Inventory Allowed” in INV Parameters is set to “NO”, then inventory should never be negative.

In Baan V and LN, the parameters in Inventory Handling Parameters determine whether you can have negative inventory. If these parameters are set to “NO”, then inventory should never be negative.

BPCS/LX Tip of the Week: Why define location fields in the work center file?

Anthony Etzel 0 568 Article rating: No rating

If you setup the “From” and “To” Location fields in the Work Center file, this will then determine the locations for material issue transactions and production reporting transactions.

The reporting of the transactions would happen through production reporting, JIT600, or using the Shop Floor labor posting, SFC600, or Shop Floor Posting from SFC650.

Remember, any location used in the work center file must first be set up in the location master file. Using an MES solution by-passes the need to key any of the data to ERP LX.

Baan/LN Tip of the Week: Negative Inventory

Kathy Barthelt 0 1143 Article rating: No rating

What should you do if you have negative inventory reflected in your system?

You should do a cycle count or inventory adjustment, but first, do a review of the inventory or location history to determine when this happened.

If a negative inventory is allowed, it most likely will be corrected upon receipt of the item. For example, assume that there is a PO that has not been received in Baan/LN, but the goods came in and got shipped out on a sales order. The inventory goes negative, but when the PO receipt is entered, the inventory would be corrected. In this case, no adjustment should be made.

A little due diligence will go a long way to ensure that you are only making an adjustment to your system when warranted.

BPCS/LX Tip of the Week: What is Lean Make to Order?

Anthony Etzel 0 261 Article rating: No rating

This is a simple way to go from the customer order to making the order and shipping the order. It involves a few simple steps:

  1. Receive and enter the customer order
  2. Automatic credit review
  3. Automatic release of the shop order tied to the customer order
  4. Issue material, report labor to the production order receipt
  5. Pick the order, ship the order, invoice the customer


With lean, you can skip processing the demand through MRP. You can go directly from the customer order to the shop order creation.

Baan/LN Tip of the Week: Optionally Include Tax Amounts In Order Balance

Kathy Barthelt 0 133 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 Day: Inventory Transactions

Anthony Etzel 0 586 Article rating: No rating

Define Inventory transactions for issuing components to the shop and receiving finished items. See the Inventory help text for examples of transactions.

  • Transaction type I - Single Issue to Shop Order. Use this transaction type to issue one component at a time. Use this for high-value items that are marked as Must Single Issue on the Item Master file.
  • Transaction type M - Multiple Issue to Shop Order. Use this transaction type to issue all the components as listed in the Shop Order, in one transaction. Note that this transaction type does not issue Must Single Issue items.
  • Transaction type S - Receipt from shop. Use this transaction type to receive the finished item into stock and update the shop order accordingly. 

The Shop Order Lot/Location Allocation program is an alternative to using the above Inventory transactions. Use this when the item is finished, and you want to review exactly what was used to make it. You can review the components as allocated, make any changes, and finally accept the finished order.

Baan/LN Tip of the Day: Multi-Company Warehousing 10.4

Kathy Barthelt 0 435 Article rating: No rating

You can define internal trade relationships between enterprise units or individual warehouses of the same logistic company for the transfer of material, labor, or other costs between warehouses, and to generate invoices for these without using sales orders and purchase orders. For example, you can use this to transfer goods between warehouses in different countries.


You can define warehouse surcharges, which are added to the actual costs of the goods either when the goods are issued from a warehouse or when the goods are received.

BPCS/LX Tip of the Day: MRP/MPS Simulation in LX

Anthony Etzel 0 785 Article rating: No rating

The system allows you to manipulate and maintain a simulated MPS and MRP. You can copy the simulation from the existing first cut, or you can create a totally new schedule. You can also perform a simulation of the rough-cut capacity plan. This allows a quick visual inspection by inquiry or menu of needed work center

loads for the proposed MPS. After you choose a suitable MPS and rough-cut capacity, the system allows you to transfer the simulated MPS to the live Master Production Schedule.

First109110111112114116117118Last

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 TECHNOLOGY: Data Sharing Methods (Advantages and Disadvantages)

Depending on the multicompany scenario you choose, an implementation team must decide whether or not tables must be logically linked or if data must be synchronized in another way to achieve availability of data across various companies. 

There are 3 ways in which data may be shared among companies. Here are some advantages and disadvantages of each:

  1. Logical Table Linking - If two companies use the same physical data, the physical table exists, or is used, in only one company: the physical company. Each piece occurs only once: one instance of the same data. If the term logical table linking is used, users from multiple companies use a single physical instance of the data. If the company tables are on the same server, this can be accomplished by logical table linking. Access to specific data can be restricted, if required.

    • Advantages: Logical Table Linking takes place in real time; therefore, the moment a record is created or modified in one company, a record becomes available in all other linked companies as well. The setup and maintenance of logical table linking is easier than the setup and maintenance of data replication. Logical table linking is extremely reliable because this type of linking is independent of network connections and user interventions. 

    • Disadvantages: Table sharing implies that all attributes for a record are the same in all companies. Therefore, suppose you share the item table and, for a particular item in a company, the product class is XXX. In this case, in all other companies, the product class for this item must be XXX as well.

  2. Data Replication - In this situation, each company has exactly the same data, but each company has a unique copy of the data. The same piece of data exists in multiple (physical) places: multiple instances of the same data. The process to copy the data is called data replication.

    • Advantages: Rather than using table sharing by means of the logical linking of tables, you can replicate the content of tables between companies. The advantage is that, on company level, some (non-key) attributes of a record can differ by company. For example, if the bills of materials are replicated instead of shared, for each company, you can link a different warehouse to the bill of material. As a result, the bills of materials can be the same across all companies and only the warehouses differ. Using replication, you can also make only a subset of the records available in other companies. For example, if you replicate items between companies, in a sales company, for example, by means of the item group, you can only make end items available. In addition, you can replicate only a subset of items, for example, depending on the item group. Note that replication also requires that the referenced tables are replicated or shared.

    • Disadvantages: Replication is not in real time, and therefore, for processes that require real-time integrated data as the financial integration processes, replication is not an option. For replication, you also must take into account the sequence in which you replicate. First, you must replicate the child tables and then the parent tables, and therefore first the business partners and then the purchase contracts. During the replication process, the data must be frozen. This point is of particular importance if the replication process takes a lot of time.

  3. Manual Syncronization - If only a small number of records are the same between some companies, you can enter, maintain, and keep the records synchronized manually. Note that the more dynamic data is, the more difficult this process is. This solution is strictly procedural. Therefore, depending on the discipline of the users, the solution is error sensitive: data can be forgotten, updated too late, or typing errors may occur.

  • Advantages - The main advantage is the flexibility so that only the data that really must be shared can be kept synchronized. By manually keeping data synchronized, not all attributes of a record need to have the same value.

  • Disadvantages - The main disadvantage is that this method depends on user interaction. Therefore, the method depends on the user’s time - because the method is not a real time procedure and the user may forget to update the data - and users can make mistakes.

Previous Article Infor LN & Baan Tips & Tricks for EXECUTIVES
Next Article Infor LN & Baan Tips & Tricks for FINANCE: Cash Flow Statements (tfgld 0123m100)
Print
32946 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories