Infor ERP Tips and Infor ERP News for Infor LX, BPCS, Infor ERP LX, Infor LN, Infor ERP LN, Baan, Infor M3, and Movex

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: Indirect Labor Reporting

Anthony Etzel 0 83654 Article rating: No rating
In the Shop Floor Control Module, you have the ability to key in both direct labor and indirect labor. However you want to establish specific types (reasons) for the indirect labor. The SFC600 labor entry program shows a reason code field, but it is designed for reject quantity and machine downtime reasons, not indirect labor reasons.

There is a way around this. With an MES solution you have the ability to setup and report indirect time against a specific reason code.

Baan/LN Tip of the Week: Configuring Items in Infor LN

Kathy Barthelt 0 94673 Article rating: No rating

In Infor LN, the configuration of a generic item not always results into a customized item. Configured items can now be customized items as well as standard items. If users configure items without PCS projects, standard items are generated instead of customized items.

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

Kathy Barthelt 0 83959 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 Week: Shop Order Status

Anthony Etzel 0 87443 Article rating: No rating

You can see the status of the Shop Order when using SFC300 Shop Order Inquiry. You want to be sure that your shop orders are at the correct status in order to report against them.

The following are the shop order status codes:

04 = The Shop order has been entered.

05 = The Shop order has been released and printed.

14 = The Shop order has been released, but not printed. If a shop order is at this status, you have released it and it is not printed due to a system failure, or the order has been put on hold.

XX = The Shop order is closed.

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

Anthony Etzel 0 90328 Article rating: 4.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: What could go wrong with GRINYA?

Kathy Barthelt 0 85451 Article rating: No rating
One common GRINYA issue would be incorrectly entered Integration Setups.

Check the Baan/LN manual for recommended Integration setups. If such a mistake were to occur, it is important to know for what period of time the Integration was in error. It is recommended that the Integrations Setup tables be audited either through Baan or Database Auditing. Corrections can be quickly calculated when an exact timeframe can be determined.

Baan/LN Tip of the Week: Differentiating An Item By Supplier - LN

Kathy Barthelt 0 84328 Article rating: No rating

In LN, you can differentiate between items at various suppliers:

  • Locations (warehouses),
  • Purpose (planning, purchase)
  • Origin (supplier, warehouse)

Example

An item is supplied by two different suppliers. Supplier A ships in lots of 100 pieces due to how the item is packed. Supplier B ships the goods in units of 60 pieces.

You can define specific parameters for each supplier. The following sessions can be used to define these characteristics:
 
  • Items - Planning (cprpd1100m000)
  • Check Item Data by Warehouse (whwmd2210m000)
  • Item Supplier Plan (cpvmi0530m000)
These sessions define entities that have an n-to-1 relationship with the general item data.

 

BPCS/LX Tip of the Week: Inventory Control

Anthony Etzel 0 94410 Article rating: No rating

In Infor LX you need to determine how inventory will be moved in and out of warehouse storage locations, and which of the following transactions to use for inventory control:


  • A transfer transaction can be used to move inventory from one warehouse location to another warehouse location.
  • A production receipt transaction is used to add inventory to a warehouse location.
  • A material issue or backflush is used to reduce inventory from a warehouse location.
First130131132133135137138139Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

Infor LN / Baan Tips & Tricks for EXECUTIVES

Finance: Propagating Unused Sub-Accounts

You can use this procedure to find accounts that have a valid sub-accounts group but no corresponding general ledger chart account records. This action creates the general ledger chart account record for the account and sub-account combination. This action does not add the accounts to charts.

  1. Select Financials > Global Ledger > Setup > Finance Enterprise Group > Maintenance.
  2. Open the finance enterprise group and click the Sub Account tab.
  3. Select Actions > Propagate Unused Sub Accounts.
  4. Select the finance enterprise group and click OK.

Sub-accounts are added according to group if they have been defined on the accounts. The resulting account can be added to the charts.

Operations: Best Practices for Purchase Order Archiving / Deleting

Here are some best practices to follow if you are considering archiving or deleting purchase order data:

  • If Financials is implemented, we recommend that you do not delete order data in a fiscal year that has not yet been fully closed. This is because the GRINYA process uses information that would be deleted by this action. For best results, check whether the logistical balance for non-invoiced receipts matches the balance of the GRINYA accounts for the periods up to which you want to delete purchase order data.
  • When a purchase order is canceled, you can only delete the purchase order and the related tables. If only a purchase order line is canceled, the line can be deleted and archived.
  • Purchase contracts must be archived before purchase orders can be archived.

You cannot delete a purchase order (line) if:

  • The linked warehouse order is closed but cannot be removed.
  • The purchase order is linked to a PCS project that is not yet archived. When the PCS project is archived, the purchase data is also archived and you can delete the purchase order.
  • A consignment replenishment order is not yet consumed completely.
  • The invoice is yet to be completely matched and approved.
  • The invoice amount is not yet inserted as turnover history.
  • The sales order or service order that's linked to the purchase order line, and for which an internal invoice must be sent from the purchas office to the sales office or service office, is not yet invoiced. In this case, you cannot delete the purchase order line before the sales order or service order is invoiced.

Technology: Using Table Boosters to Speed Up Sessions & Processes

To increase the speed of sessions and processes slowed by large amounts of data, you can use table boosters. These speed up access to specific database tables by loading the table, or a specified part of it, into memory. Table boosters are defined in the Table Boosters (tcmcs0598m000) session.

Tables

Table boosters are implemented for tables. By default, table boosters are not active. When you access a table, LN builds a list of tables for which you can activate the boosters in the Table Boosters (tcmcs0598m000) session.

Note: You can only activate table boosters for tables that have been accessed at least once.

For more information, refer to the LN - Performance, Tracing, and Tuning Guide (U9357).

Previous Article Infor LN & Baan Tip & Tricks for OPERATIONS: Best Practices for Purchase Order Archiving / Deleting
Next Article Infor LN & Baan FINANCE Tip: Is it possible to upload accounts receivable invoices into LN using Excel?
Print
23296 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories