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 LX / BPCS Tips & Tricks for OPERATIONS: Auto Calculate Vendor Delivery Date

George Moroses 0 134 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 104 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 28863 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.

Infor LN & Baan Tips & Tricks for OPERATIONS: Deleting Purchase Orders

Kathy Barthelt 0 28365 Article rating: 5.0
  • 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.

Infor LN & Baan Tips & Tricks for FINANCE: Cash Forecast Reports and Inquiries

Kathy Barthelt 0 20282 Article rating: 5.0

To produce the cash flow forecast, the combined information from the following is used:

  • Customer and supplier accounts
  • Open sales and purchase orders
  • Purchase quotations
  • Purchase requisitions
  • Standing orders
  • Projects
  • Financial budgets

You can use the bank balances of the bank relations that are maintained in the Bank Relations (tfcmg0510m000) session, to generate the reports with details of cash inflows and outflows of the company for a specified period of time.

You can also manually specify the Opening Balance for the cash forecast. Use the sessions below to print and generate the reports:

  • Cash Forecast Summary by Date Range/Currency (tfcmg3518s000)
  • Print Cash Forecast Details by Date Range/Currency (tfcmg3412m000)
  • Print Cash Forecast Summary by Period/Currency (tfcmg3410m000)
  • Cash Forecast Summary by Date/Currency (tfcmg3519s000)
  • Print Detailed Cash Forecast in Cash Forecast Currency (tfcmg3413m000)
  • Cash Forecast Components by Date/Currency (tfcmg3520m000)
  • Print Forecast Components by Date/Currency (tfcmg3420m000)

Infor LX/BPCS Tips & Tricks for OPERATIONS: Override inspection days lead time at item-facility

George Moroses 0 9922 Article rating: 5.0

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

Infor LX/BPCS Tips & Tricks for TECHNOLOGY: Improve WebTop Grid Support for MRP320D Master Schedule Detail Inquiry

George Moroses 0 9603 Article rating: No rating

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.

Infor LX/BPCS Tips & Tricks for FINANCE: IDF Ledger Book Journal Line Analysis

George Moroses 0 4643 Article rating: 5.0
  1. This enhancement added the IDF Ledger Book Journal Line Analysis business object for displaying reference information on summarized journal lines. This enhancement provided Ledger Book Journal Line Analysis business object and a bi-directional relationship to Ledger Book Journal Line Source.
  2. This enhancement provides the user with detailed reference information on summarized journal lines for analysis purposes.
245678910Last

Tips:  LX | BPCS | M3

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.

Last

Tips: LN | Baan

Kathy Barthelt

Infor LN & Baan Manufacturing Tip: Performance Problems in Generate Order Planning (cprrp1210m000)

When the Generate Order Planning (cprrp1210m000) session is run it can take minutes to days to finish the process.

The performance of this session depends on many settings, like the number of plan items, the number of orders, but it also depends on hardware and database setup.

Here are some guidelines on how performance can be improved.

  • Be sure you are always on the latest solutions with the planning sessions. We are constantly improving the software to gain more speed in the Enterprise Planning (EP) sessions.
  • The number of planned items is critical. Try to reduce the number of planned items. Is it necessary that all items be planned via EP? For shop floor stock the TPOP or SIC replenish systems are often more suitable.
  • When you use PCS, be sure to close the projects when they are finished. When a PCS project has status Closed, the customized items will not be planned.

It's better to run Remove Plan Items for closed Projects (cprpd1220m000). This session removes the item planning data for customized items of closed projects.

  • If you run EP with the option, Also Generate Item Master Plan and/or Online Update Item Master Plan, consider if you need an Item Master Plan for all plan items. An Item Master Plan is usually meant for global long-term planning. Again this is not very useful for shop floor stock. Reducing the number of master-planned items improves performance.
  • When you use Resource Master Plans; are all your resources really critical? If a work center is not critical do not create a Resource Master Plan for it.
  • When using Item Master Plans and/or Resource Master Plans, set in Scenarios (cprpd4100m000) the total scenario length as short as possible. For example, if your sales order horizon is 2 years, a scenario end date which is 3 years after the current date is sufficient. During the calculations of the Item Master Plan and the Resource Master, all periods defined in the scenario are checked and calculated. So if you have the end date of the scenario on 2038, EP will do the calculations (for every master-planned item) until 2038.

Defining a rolling scenario will keep your scenario length constant and you don’t have to worry that you run beyond your scenario's end date.

  • Updating the pegging relations has a serious impact on the EP performance. In EP Parameters (cprpd0100m000) you can set the Pegging Horizon in days. Keep this horizon as short as possible. The Update Signals by Item/Planner option also has some impact, but less than the pegging.
  • EP uses the so-called phase numbers to detect the lowest level in which an item is used within a BOM structure or in a supplying relation. If the phase numbers are not ‘up-to-date’, EP will correct the phase numbers during the planning. This takes time during the planning run. If there are loops in BOMs or in supplying relations, this recalculation has a big impact on the performance. Therefore you could run Compute Phase Numbers (cprpd6200m000) on a regular basis. For example once a month. Always run this session with the Generate Report option selected. If loops are detected these are reported. Be sure to solve all the reported errors.
  • When unexpected results occur, especially when the data is imported from external packages, always check the number of records in tables cprpd100 and cprpd120. The number of records should match! Remark: From 10.4 onwards the table cprpd120 has become obsolete so this point not applicable anymore.
  • The number of calendars also impacts planning performance. Then for every warehouse, work center, or BP, and so on, a different calendar is defined. Planning has to read all of these calendars from start to end. This can have a huge impact on performance.
    • If you link a calendar to a work center or warehouse, avoid defining a new calendar for every work center/warehouse. Try to link the same calendar to more than one department.
    • Define the start of the calendar close to the start date of the scenario. For example, the current date is 01-07-2014, the start date of the scenario is 365 days in the past. So a start date for your calendar could be 01-07-2012.
    • Define the end date of the calendar not too far in the future. Depending on the end date of the scenario you could use 5 years ahead.  For example, the current date is 01-07-2014, the end date of the scenario is 3 years in the future. So an end date for your calendar could be 01-07-2022. Do not define an end date past 19-01-2038, which is the last UTC date Infor LN can handle.

Also, the interaction with the database can have a big impact on performance. 
A commonly used way to improve the total run time of the EP run is to start the session in parallel processing. 
See also Knowledge Base Article 22881401 Performance, Tracing and tuning Guide, for more details.

These guidelines are just some hints, and a good starting point because performance is a complex issue.

Previous Article Infor LN & Baan Tip of the Week: Limitations of Customer Defined Fields (CDFs)
Next Article Infor LN & Baan Tip: Broadcast message to users
Print
66209 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories