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: Restricted User Access

Kathy Barthelt 0 70784 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.

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

Kathy Barthelt 0 73690 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.

Baan/LN Tip of the Week: Product Families

Kathy Barthelt 0 74535 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.

Baan/LN Tip of the Week: Company Calendar

Kathy Barthelt 0 71388 Article rating: No rating

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.

Baan/LN Tip of the Week: Setting Up New Employees in LN

Kathy Barthelt 0 72594 Article rating: No rating

In LN, the People package is used to register the employee’s hours and expenses. To support the People package, the Employees - General (tccom0101m000) session only contains the general employee data.

The title of the Employees - General (tccom0101m000) session was changed to Employees – General (tccom0101m000).

From the Employees - General (tccom0101m000) session, users can start the following sessions to define the more specific employee data:

  • Employees - People (bpmdm0101m000).
  • Employees - Project (tppdm8101m000).
  • Employees - Service (tsmdm1140m000).
  • Skills by Employee (tcppl0120m000).
  • Employees by Team (tcppl0150m000).
  • Roles by Employee (tcppl0170m000).

After users define the employees, users can also start the listed sessions from the Employees Dashboard (bpmdm0101m100) session in People.

Baan/LN Tip of the Week: Month End - Miscellaneous To-Do's

Kathy Barthelt 0 69932 Article rating: No rating
  • Print Sales Order History Information
    • all invoices processed through sales
  • Check Inventory Valuation
    • this should tie out to your inventory accounts
  • Print Integration Information
    • see all postings from WIP to finished goods
  • Print G/L Transaction Information
    • print specific transaction types for any GL account
  • Print Lot Control Information
    • will show where serial numbers were used

Baan/LN Tip of the Week: The Product Configurator

Kathy Barthelt 0 80283 Article rating: No rating

What is it?
The configurator consists of a set of features (questions). The options (answers) to these questions are used to generate the custom bill of material and routing. These questions may be answered at the time of order entry, prior to order entry (in a project or quote) or after order entry (in the project). The order of the questions do not need to have any relationship to the bill of materials. The configurator may also calculate the selling price, create a unique “smart” item number, custom description and text. Simple rules are used to interpret the answers.

Who uses the configurator?
Companies whose products have options. The configurator eliminates the need for part numbers for all combinations of options. The configurator ensures that the pricing and bills are correct. The configurator also keeps statistics on the frequency the options are selected.

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

Kathy Barthelt 0 92973 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.

First3637383940414244

Tips:  LX | BPCS | M3

Item Facility Master has a new attribute to define the override inspection days lead time CICP.ICINSD.

  • When an item facility has a defined override inspection days lead time, that value will be used instead of the system parameter inspection days lead time.

MRP exception report, MRP200B
Purchase planning report, PUR285B
Purchase order / Requisition maintenance, PUR500D3
Purchase order consolidation / release, PUR640B1
Vendor splits, PUR653B

This enhancement improved the subfile utilized in MRP320D Master Schedule Detail Inquiry -SCR001 by expanding the subfile with data rather than clearing the subfile as user pages. This change provides full support for the WebTop 4.8 Grid decorator.

This enhancement updated the approach used to populate the subfile to allow a deployed Webtop Grid to function correctly. There is no visible or user-impacted change to the way the program functions.

This enhancement provides improved functionality and full support of a Webtop grid applied to the subfile.

Last

Tips: LN | Baan

Users can personalize sessions and apply special formatting to the data displayed in sessions. The personalizations and formatting settings that are specified by the users are stored on the LN server. Administrators can maintain these settings.

  • Session personalizations

    Users can personalize sessions in various ways. users can, for example, hide fields, change labels, customize the toolbar, and move fields to another tab. Administrators can maintain the personalizations defined by the users. For example, an administrator can export personalizations to an XML file, import personalizations from an XML file, and copy personalizations to another user, to a DEM role, or to a company number.

  • Report personalizations

    You can use the Report Designer (ttstppersrep) to personalize the layouts and style of reports, without modifying the standard reports or using an external reporting solution. The changes are stored as personalizations.

    You can also generate new reports that are based on a selection of fields from the application data model. These reports are generated in the extensibility package. You can personalize these reports in the Report Designer (ttstppersrep), or modify them in Infor LN Studio.

    For details, see the Infor LN Report Designer Development Guide
     
  • Conditional formatting

    users can define conditions to apply special formatting to the data displayed in LN sessions. The users can define multiple conditions per session and different types of formatting, such as a specific color for particular fields or rows, and a warning symbol for particular rows. Administrators can maintain the formatting settings specified by the users and can define system-wide formatting settings.

  • If Finances 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.

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 is linked to the purchase order line, and for which an internal invoice must be sent from the purchase 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.

Categories