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

Infor LN & Baan Tips & Tricks for TECHNOLOGY: Authorization and Security - LN REST APIs

Kathy Barthelt 0 2341 Article rating: 5.0

In typical LN REST API integrations, permissions and authorizations are not implemented or rarely used. To ensure smooth data exchange and avoid errors, it is recommended to disable the authorization and security settings.

Recommendation:

  • In the Authorization and Security Parameters session (tcsec0100m000):

    • Clear the Authorization and Security Enabled check box.

    • Clear all check boxes under Authorization Enable for on the Enabling tab.

Why This Matters:

  • Enabling authorization and security without proper setup can lead to errors and blocked transactions during integration.

  • For example, work center permissions may interfere with:

    • Creating new shifts

    • Booking machine hours

    • Read more

Infor LN & Baan Tips & Tricks for OPERATIONS: Copy Customized Product Structure to Standard Structure (tipcs2232m000)

Kathy Barthelt 0 1610 Article rating: 5.0

This functionality allows you to copy the product structure of a customized item to a standard item.

Note: When a customized structure is copied to a standard structure, the Customized check box in the Items session (tcibd0501m000) is cleared.

Item Types:

  • Standard Items: Identified by a regular item code.

  • Segmented Items: Consist of a project code segment and an item base segment (i.e., the customized item’s item code). Segments are defined in the Item Code Segmentation session (tcibd0500m000).

Only components valid for the specified Effectivity Unit will be copied.

Copy Options:

  • Target Routing Code
    Enter the code of the standard routing to which the customized structure should be copied.

  • Copy Product Structure
    Choose whether to:

    • Copy the entire structure

    • Copy only the first level

    • Perform the copy interactively

  • Reference Date
    Only parts of the product structure valid on this date will be copied.

  • Copy E-Item Relationships
    If selected, related E-item records will be copied.

  • Copy All Components and Effectivity Statements
    If selected, unit effectivity is copied to the standard structure. You can specify the unit.
    Exceptions related to routings and operations (that meet date effectivity) are also copied.

  • Alternative Material
    If selected, alternative BOM components are included in the copy.

  • Use-Up Material
    If selected, use-up materials from BOM components are included.

Infor LN & Baan Tips & Tricks for FINANCE: Rebuild History for Account Matching (tfgld1218m000)

Kathy Barthelt 0 2044 Article rating: 5.0

Use this session to rebuild the ledger account history for account matching. This is particularly useful if you’ve recently defined a ledger account, on which transactions already exist, as a matchable account.

You can specify the fiscal year and period for which you want to rebuild the account matching history.

Note: This session can also be used to remove unmatched transactions if you decide to stop performing account matching for a specific ledger account.

Field Information

Selection Range

  • Use Job Reference Date
    If selected, Infor LN uses the Job Reference Date as the basis for rebuilding history data.

  • Job Reference Date
    Specifies the date and time used for the rebuild process.
    Enabled only if "Use Job Reference Date" is selected.

  • Financial Company
    The financial company for which you want to rebuild a ledger account history.

  • Ledger Account
    The specific ledger account to rebuild.

  • Fiscal Year
    The fiscal year for which you want to rebuild the ledger account matching history.


     

Infor LX/BPCS Tips & Tricks for FINANCE: Override Warning in Invoice Entry PO Costing

George Moroses 0 3162 Article rating: 5.0

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.

Infor LX / BPCS Tips & Tricks for OPERATIONS: Auto Calculate Vendor Delivery Date

George Moroses 0 697 Article rating: 5.0

Enhances purchase order efficiency by automatically calculating the Vendor Delivery Date based on user input.

  • When a purchase order line is created, the user enters the item, order quantity, and Due Date.

  • LX automatically calculates the Vendor Delivery Date, adding buffer time for quality control, testing, and inspection activities.

  • If the Due Date is revised, an informational message prompts the user to review and potentially update the Vendor Delivery Date.

Enhancements:

  • A new PUR820 system parameter enables automatic recalculation of the Vendor Delivery Date.

  • Instead of a manual reminder, PUR500 now issues a message: “Vendor Delivery Date recalculated,” showing the updated date.

Benefits:

  • Eliminates the need to manually review and update the Vendor Delivery Date.

  • Removes the need to delete and recreate PO lines to trigger automatic date calculation.

Infor LX/BPCS Tips & Tricks for TECHNOLOGY: User Provisioning

George Moroses 0 782 Article rating: 5.0

Enables integration between LX and Infor OS Federation Services (IFS) to automate user provisioning.

  • Bi-directional user synchronization between Infor OS and LX:

    • Infor OS user creation or changes automatically create or update users in LX.

    • IBM i user profiles can be created if needed.

    • Updates to SYS600 user data are reflected in Infor OS.

  • Security Role Integration:

    • LX Security Roles and Units are published as IFS Security Roles via SyncSecurityRoleMaster BODs.

    • LX receives inbound SyncSecurityUserMaster BODs from IFS to create or update user records in SYS600.

    • SYS600 Exit Points trigger ProcessSecurityUserMaster BODs to request user creation or updates in IFS on behalf of LX.

Available Versions: 8.3.5, 8.4.1, 8.4.2

Infor LN & Baan Tips & Tricks for TECHNOLOGY: Application Personalization

Kathy Barthelt 0 30890 Article rating: 5.0

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.

124678910Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

Infor LN & Baan Tip: The ABC’s & 123’s of Serialized Items
Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Infor LN & Baan Tip: The ABC’s & 123’s of Serialized Items

A serialized item is a physical occurrence of a standard item that is given a unique lifetime serial number. This enables tracking of the individual item throughout its lifetime, for example, through the design, production, testing, installation, and maintenance phases. A serialized item can consist of other serialized components.

In Service, a serialized item can be a customer-specific or owner-specific installation. Installation groups are a group of installations/serialized items such as photocopiers, computers, air conditioners, forklifts, lathe machines, and even aircraft.

A serialized item is identified by both the item code and serial number. You can set up the mask used to generate the serial numbers so the serial number includes some fields of the item data, such as the item group and the manufacturer.

In a multi-company structure, the companies can share the serialized item data. All the service departments in the various companies can refer to the same serialized items.

The serialized item can originate from a sales order or a project. The details of a serialized item indicate their origin, for example, by using specific sets of serial numbers for items that originate from sales orders and from projects. Serialized items can also originate from an as-built structure or directly from the production bill of material in Manufacturing.

In Service, serialized items can start their respective life cycles in As-Built mode or As-Maintained mode. Each serialized item, with or without its installation group, can be covered by a service contract or a warranty.

The serialized item status

Serialized items can be status controlled. Each serialized item can have the following status:

  • Startup - The serial number has been assigned, but the item is not yet included in a service order or contract. You can only change the status to Active.
  • Active - The serialized item is part of a service order or contract. You can only change the status to Revision.
  • Revision - You can only change the status to Active.


Serial numbers

A unique serial number is assigned to every manufactured item or purchased item. The serial number is assigned to track the item in its life cycle. You can define a dummy serial number for an item. The dummy serial number is a temporary number and can be used to monitor the item until a permanent number is assigned. For each serialized item, you can define an alternative serial number for customer reference. You can use the alternative serial number to search for items when you register calls, create service order activities, or register parts lines for a maintenance sales order.


Serialized item groups

You can group serialized items by serialized item groups. A serialized item group is a group of serialized items with similar features. You can define the serialized item groups that you need, for example, to categorize the skills required for the maintenance of the items, or as a basis for enquiries and reporting. For example, you can select service engineers on the basis of their skills for a specific serialized item group.


Serialized items in physical breakdown structures

Serialized items are the building blocks of physical breakdown structures. A physical breakdown structure is the relationship definition of a set of serialized items with their underlying parts and assemblies. Some serialized items, such as a photocopier, have a simple structure whereas other serialized items such as a ship or an aircraft have a complex structure.

A top serialized item occurs at the highest level in the physical breakdown structure, while the underlying structure consists of assemblies that are either effective or outdated. Use the Tree View option to display a graphic view of the structure.

Each serialized item in the breakdown can be linked to a functional element, with a common function across the entire structure, and can be used to group serialized items based on the functional importance.

Previous Article Infor LN & Baan: Customizing Shipping Labels for All Customers
Next Article Infor LN & Baan Tip: Outbound Order Lines
Print
23283 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories