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 83536 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 94593 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 83874 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 87404 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 90163 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 85324 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 84123 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 94302 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

Kathy Barthelt

Infor LN & Baan Tips & Tricks for TECHNOLOGY: Load Audit Tables for Profile (ttaud3220s000)

Use this session to load tables for an audit profile.

Usually, this session is run from the Specific menu of the Audit Tables by Profile (ttaud3120m000) session. The selected profile in that session is displayed in the first line of the current session.

The result of loading the tables depends on the selection level you use in the current session. For each element on the lowest selection level, a line is created in the Audit Tables by Profile (ttaud3120m000) session. For example, if you select a package and a number of modules, a line is created for each module. Because you did not specify the tables, the All check box is selected.

Field Information

  • Profile: The audit profile for which the tables are loaded.
    Note: If you start the current session from the appropriate menu of the Audit Tables by Profile (ttaud3120m000), the profile displayed is the profile that is selected in that session.
  • Package: The package that contains the tables you want to load.
  • Module: The module that contains the tables you want to load.
  • Table: The tables you want to load.
  • Audit Type: The audit type that must be set for the tables that are loaded.
    Note: You can either select: Always, or Changed. However, it is also possible to determine the audit type per field. This is the Not Applicable option in the Audit Tables by Profile (ttaud3120m000) session. If you want to set the audit type per field, you must change the audit type to Not Applicable after the tables are downloaded, and then specify the audit type per field in the Audit Fields by Table (ttaud3125m000) session.
Previous Article Infor LN & Baan Tips & Tricks for OPERATIONS: Pegging Material Supply Lines for Operation and Product Subcontracting
Next Article Infor LN & Baan Tips & Tricks for EXECUTIVES
Print
6898 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories