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

BPCS/LX TIP OF THE WEEK: Remembered Keys

Anthony Etzel 0 1918 Article rating: No rating

Infor LX remembers certain key values, such as item number, salesperson,

or container, in your workstation memory as you process information in certain

programs. You can assign one of the following values to each field:

 

0  -Infor LX automatically retrieves this value from remember key memory. Infor LX updates this value on a continual basis.

 

1  -Infor LX automatically retrieves the value you specify in Display Remembered Keys, SYS080. It does not update the value from any other program.

 

2  -Infor LX does not retrieve or update remembered key fields. Use the Display Remembered Keys program, SYS080, to set up remembered keys.

Baan/LN Tip of the Week: Sales Order Acknowledgements

Kathy Barthelt 0 3109 Article rating: No rating

Sales Order Acknowledgements in Baan IV:
After a sales order is entered in Baan IV, users can print an order acknowledgement in Print Sales Order Acknowledgements/RMAs (tdsls4401m000), after which it can be sent to the customer.

Sales order acknowledgements in ERP LN:
In Infor LN, users can still use the Print Sales Order Acknowledgements/RMAs (tdsls4401m000) session to print order acknowledgements, however, the following functionality is added to this session:

  • In the Documents to Print field users can select whether to print order acknowledgments and/or return material authorizations.
  • With the Promotions check box users can indicate whether to print promotions on the order acknowledgement, if promotions apply to the order.
  • Users can control the printing of order acknowledgements based on the order amount and/or the delivery date.

These conditions only apply for order types that do not have the Print Sales Order Acknowledgements/RMAs (tdsls4401m000) linked as a mandatory activity to the order type in the Sales Order Type - Activities (tdsls0560m000) session.

BPCS/LX Tip of the Week: Operational Inefficiencies

Anthony Etzel 0 393 Article rating: No rating

Two big sources of inefficiencies in manufacturing are paper and spreadsheets. I know that you love ‘em, but they are the cause of more problems than you probably realize. Think of how long it takes you to get paper based data into the hands of those who can do something valuable with the data. Are you capturing all of the information correctly? Timely? What about those spreadsheets? Can everyone access that information across your organization? Is that data married with all of the related data regarding your operations to give your executive and middle management the information they need when they need it?

Make your shop floor paperless and put in place systems that talk to one another and automatically pull and push data to and from your ERP so that you can look in one place for all the information you need to run your business effectively.

If you’re not doing this today, you might as well be burning money.

Baan/LN Tip of the Week: Use of Correction Period

Kathy Barthelt 0 173 Article rating: No rating

There can only be one correction period, and it must be the last period in the period table.

There can only be a correction period for Fiscal periods and not for Reporting or Tax. This period is used for the posting of the Automatic Balancing of Profit and Loss entries as well as any auditor adjusting entries that may be made outside the normal year. This allows you to print a trial balance and financial statements of period 1-12, for example, eliminating any of those adjusting entries.

If you have the Company Parameter (Balancing of Profit & Loss) set to Individual Accounts, then it is critical to have a 13th period to post those entries to. With this setting, the Automatic Balancing will zero out each individual P&L account in the last period. You want this to be period 13 and not period 12.

BPCS/LX Tip of the Week: Understanding What Goes On – Out on the Factory Floor

Anthony Etzel 0 346 Article rating: No rating

Ok… so you want to know the status of a specific shop order that was released two days ago.

What do you do?

It’s a sure bet that you have a manager, supervisor, or planner who can walk the floor and find the order at whatever work center it happens to be at. He/she can then answer “what operations have been completed and how many were completed?” All this requires leg work, and of course, a fair amount of time.

Now, if you have setup your BPCS master files properly, and you report transaction activity, you should be able to get those shop order statuses much faster using the SFC300 Shop Order Inquiry Screen.

At your fingertips you can see:

  • Release date & due date
  • How many hours remain in total and at each operation
  • The quantity required, what was finished and the remaining quantity
  • What components (materials) have been issued

Pretty basic information, right? Are you getting what you need to know? If not, then you may want to reexamine how your BPCS files are setup and what transactions along with their frequency are captured.

Baan/LN Tip of the Week: Default Order Frequency

Kathy Barthelt 0 178 Article rating: No rating

In Baan IV, requirements for an MPS item with the order method lot-for-lot result in daily planned MPS orders.

For example, if a plan period contains 10 working days and the net requirements for an item in that period is 2000 pieces, an MPS planning run generates one planned MPS order of 200 pieces for each working day in the plan period.

In Infor LN, requirements for a planned item with the order method lot-for-lot result in one planned order per plan period.

For example, if a plan period contains 10 working days and the net requirements for an item in that period is 2000 pieces, a master planning run will generate a single planned order of 2000 pieces for the first working day in that plan period. To influence the order quantity of the planned orders, enter appropriate values in the Maximum Order Quantity field and the Order Interval field in the Items – Ordering (tcibd2500m000) session or choose a fixed order quantity.

BPCS/LX Tip of the Week: Indirect Time

Anthony Etzel 0 1002 Article rating: No rating

In Infor LX, there are two ways to enter indirect labor. You can use either SFC600 or SFC650.
 

  1. If you use SFC600 and enter a reason code for the indirect labor, the reason you entered is written to the Labor Ticket file.
  2. If you use SFC650 and enter a reason code for the indirect, the reason code is not written to the labor Ticket file.

 

In either case, the reason code is not validated from the transaction file because there is no indirect transaction code. The indirect code that can be setup is machine downtime. If you need to validate and track indirect by reason and validate the reason code, then you may want to explore an MES solution that works with Infor LX.

 

First112113114115117119120121Last

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