Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Resources Infor ERP Tips & News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Subscribe to newsletter

Baan/LN Tip of the Week: Aborted Finalization Run

Kathy Barthelt 0 76889 Article rating: No rating
When a finalization run is aborted and in the batches selected for this finalization run are transaction types having the update mode finalization, you must use the Restart Finalization Run session. This session can be found in the Transaction Processing menu of the General Ledger Module of the Finance Package.
Read more

BPCS/LX Tip of the Week: SFC600

Anthony Etzel 0 80202 Article rating: No rating
In addition to SFC650, this ERPLX program is also used to capture and post shop floor information.

The key difference between the two is that SFC600 only captures Labor (run time) reporting, machine time, downtime and indirect time.

If you use SFC600, then all shop order material receipts and issues would be captured using INV500.

Both Inventory and Shop Floor Transaction entry is keyboard dependent, unless you incorporate an automated method like an MES solution to capture the data.
Read more

BPCS/LX Tip of the Week: Downtime Reasons

Anthony Etzel 0 79147 Article rating: No rating

Using SFC600 to enter downtime.

You are tracking downtime and using SFC600 to enter the downtime, but you don’t know where to go to setup downtime reasons. You can set up the downtime reason codes in the INV application by selecting the reason code maintenance program INV140D1.

Once you are in the reason code maintenance program, position to the transaction effect code “D”. Using the transaction effect code “D” you can now setup as many downtime reason codes as needed. The reason code field is alpha numeric, so be creative with your reason code assignments.

Read more

Baan/LN Tip of the Week: Restricted User Access

Kathy Barthelt 0 73641 Article rating: No rating
Administrators are able to restrict access in Baan in several ways – including Companies, Packages, Modules, Sessions, and Tables – using the Authorization capabilities of the system.

In Baan IV, access can be given or denied on a user by user basis.

In Baan V and LN, the Authorization Management System can provide or deny access based upon roles to which users are assigned.

Read more

BPCS/LX Tip of the Week: Work Center - Cells

Anthony Etzel 0 61335 Article rating: No rating
The LMP module (Lean Manufacturing Process) uses work centers but refers to them as production cells.

A cell is one or more work centers that produces an end item. So when a company decides to adopt the lean manufacturing philosophy, the concept of work centers takes on a new meaning.

In lean terms, the work center, or group of work centers, becomes a production cell. In other words, a mini-factory producing end items with similar characteristics.
Read more

Baan/LN Tip of the Week: Closed, Final Closed, Provisional Close – What’s The Difference?

Kathy Barthelt 0 77962 Article rating: No rating

Fiscal, Reporting and Tax Periods can have status Open, Closed or Final Closed. If a period is Closed or Final Closed, you cannot post entries to those periods. If a period is Closed, you can re-set it to Open and post entries. If a period is Final Closed, you cannot post and you cannot set it back to Closed or Open.

A Provisional Close is run at year-end to bring the balances forward for the new year without having to close the previous year. A Provisional Close can be run as many times as you like. After a Final Close, a Provisional Close cannot be run.

The Provisional Close allows you to continue into the new year with all financial reporting and not have to rush with the Final Close until all adjusting entries are made and any final signoffs have been completed.

Read more

Baan/LN Tip of the Week: Product Families

Kathy Barthelt 0 77740 Article rating: No rating

In Baan IVC, plan items on the lowest plan level were automatically actual items (not product families). All plan items on higher plan levels were product families.

The relationship between a product family and items on lower plan levels was defined in a planning bill of material.

In Infor LN, every family item must be defined in the Item Base Data module. A family item can exist on any plan level. The relationship between a family item and items on lower plan levels is defined in aggregation relationships.

Aggregation relationships in Infor LN are much more flexible than the planning bills of material in Baan IV. For example, users can define aggregation relationships between items on the same plan level.

Read more

BPCS/LX Tip of the Week: Create the Master Schedule

Anthony Etzel 0 79886 Article rating: No rating

In the master schedule creation, you have the flexibility to enter a planning start date, or default to the facility planning start date. Infor LX uses the planning date to plan both orders with forecasts and customer orders as demand.You can create your master schedule from the Master Production Scheduling module (MPS).

Read more
First124125126127128130132133

Tips:  LX | BPCS | M3

Tips: LN | Baan

Kathy Barthelt
/ Categories: Infor LN & Baan Tips, Executive

Infor LN & Baan Tips & Tricks for EXECUTIVES:

Operations: Copying EBOMs - Which copying method should I use?

To determine which copying method you must use, answer question 1 and follow the instructions.

Question 1: Is the source component a project item (that is, is a project defined in the first segment of the item code)?

  • If the answer is yes, proceed with question 3.
  • If the answer is no, proceed with question 2.


Question 2: Is the target component a project item?

  • If the answer is yes, select copy method NonProj Item to Proj Item.
  • If the answer is no, proceed with question 4.

Question 3: Is there a relationship with the same project?

  • If the answer is yes, select copy method EBOM to Production BOM Only.
  • If the answer is no, proceed with question 4.


Question 4: Is there a relationship with the target item?

  • If the answer is yes, proceed with question 5.
  • If the answer is no, select copy method No Copy Action.


Question 5: Does the item exist already?

  • If the answer is yes, select copy method EBOM to Production BOM Only.
  • If the answer is no, select copy method Copy E-Item to Item.

Technology: Using audit files in the Exchange module

The audit server logs all database actions that change the contents of a table in so-called audit files. The Exchange module can use these audit files, which are useful in a multisite environment because the databases on all sites must have identical data. These audit files can also be used in data conversions.

Only the updates in a specific period are exchanged, which leads to an improvement in performance. Specify this period in the Export Data (Non-Regular) (daxch0233m000) and Export Data (on a Regular Basis) (daxch0234m000) sessions. Changes such as insert, update, and delete are processed and written into the ASCII files. Actions such as drop, clear, and create tables are ignored.

Audit control data is added to the resulting ASCII file. This data consists of a batchline ID, transaction ID, sequence ID, and an indicator. The control data is added at the beginning of each line and is formatted like other data fields such as the enclosing and separator characters.

An update writes two lines to the ASCII file. One line contains the key fields and old values of the updated fields. The other line contains the new values of the key fields and updated fields, even if a key field does not change.

The batchline ID is used for recognition when processing the ASCII files. The transaction and sequence IDs are used to ensure that the transactions are replayed in the same order as on the exporting site. The indicator defines the type of action that is executed on the table. Use the letter I to insert; use the letter D to delete; use the letter U to update with old values; and use the letter N to update with new values.

Finance: Problem Invoices

You can use a problem code to indicate that a problem exists for a sales invoice. If the invoice-to business partner notifies you about a problem with the invoice and does not pay it, you can link a problem code to the invoice.

In the direct debits procedure, problem invoices are automatically discarded. For each problem code, you can set an option to prevent linked invoices from being selected on reminder letters.

Previous Article Infor LN & Baan Tips & Tricks: Action Required - Infor LN Cloud Edition - Fonts Update!
Next Article Infor LN & Baan Tips & Tricks for Operations: Copying EBOMs - Which copying method should I use?
Print
50992 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt
Contact author

Contact author

x

Categories