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

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.

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.
  
   

FINANCE: Override Warning in Invoice Entry PO Costing

OPERATIONS: Auto Calculate Vendor Delivery Date

TECHNOLOGY: User Provisioning

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.

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.

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

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.