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: Data Sizing Moving to LN

Kathy Barthelt 0 57508 Article rating: No rating

The Infor LN database must be created with the appropriate size. For example, if at least 150 GB is required for a year, create the database with the required size from the beginning. Do not let the size increase to the required size and cause additional fragmentation in the database and the NTFS volume.  Set the autogrowth to a minimum of 10 percent or 1 GB (for each extent) to avoid fragmentation on file system level. Never use the default extent size of 1 MB.

BPCS/LX Tip of the Week: Work Center & Machine Locations

Anthony Etzel 0 60974 Article rating: 3.0

For either file, you must specify a valid location code as defined in the Location Master File.

If the machine master locations are blank, then the work center locations are used. There are cases where you may want to do a combination between the two in defining the locations.

Let’s say the end item has one operation. The operation is at work center 510 and Machine A is in the work center. You have locations setup in both the Work center file and the Machine master File. You report 100 complete at the work center without specifying the machine.

In this case, the inventory will be processed based on the locations defined in the work center file. If the transaction included the machine number, then the locations in the machine file would be used.

Baan/LN Tip of the Week: SIC Planning for MRP/MPS Planned Items

Kathy Barthelt 0 67294 Article rating: 3.0

If you have a parts warehouse and prefer to use SIC for planning (re-order point) but need to use MRP/MPS planning for production, create a non-nettable warehouse for the parts warehouse and run the SIC plan against that warehouse.

When running the SIC plan, be sure to set the Order System to “MPS to MRP” for Baan IV and to “Planned to Planned” for Baan V and LN.

Using this method you keep the parts inventory out of the production planning and in the hands of the parts warehouse planner.

BPCS/LX Tip of the Week: Indirect Time Reporting

Anthony Etzel 0 59679 Article rating: No rating

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

  • If you use SFC600 and enter a reason code for the indirect labor, the reason you entered is written to the Labor Ticket file.
  • 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.

Baan/LN Tip of the Week: Differences Between Constraint Planning in Baan IV and Enterprise Planning in LN

Kathy Barthelt 0 56154 Article rating: No rating

In Baan IV, a distinction is made between the actual ERP system and a separate planning tool which contains the Constraint Planning package. This tool was intended to work with any ERP system, not just with Baan IV. The Enterprise Planning package is now considered to be a package like any other package in Infor LN.

Users of Baan IV could choose whether they wanted to plan their supply in one of the following ways:

  • By using the MPS and MRP modules in the Manufacturing package.
  • By using the RPD and RMP modules in the Constraint Planning package.

Users of Infor LN can only use the Enterprise Planning package. The distinction between the MPS items and MRP items has been abandoned. In Infor LN, all items can be planned by using a combination of master-based planning methods and order-based planning methods.

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

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

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

Anthony Etzel 0 59613 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.

First109110111112114116117118Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

Anthony Etzel

How to Improve Customer Shipments With OTTO - A Case Study

Setting Industry Service Standards

Shenandoah Manufacturing, a $20 million producer of poultry-raising equipment (heaters and brooders), had been having difficulty for some time shipping orders to customers in a timely manner. They had successfully implemented a popular ERP system and had been using it for more than 3 years, yet the situation didn't improve. 

Customer Service Representatives were complaining about the frequent backorders and late orders. Employees were giving it their best effort, but were frustrated, and customers were threatening to take their business elsewhere.

The company considered installing an APS system as a possible solution, but found implementation would be difficult, expensive, and running the system might be a challenging task as a number of key business practices would have to be changed. A consultant familiar with OTTO suggested they look at that product as an alternative to APS. Several OTTO aspects cited by the consultant convinced them to consider a cursorily review. Specifically:

  • The non-intrusive nature of the product.
  • It's relative inexpensive initial investment.
  • The low overall total cost of ownership.
  • The integration with their ERP system.

The initial demonstration was impressive. OTTO was installed on Shenandoah's server within 45 minutes of arrival and, most impressively, it was fully functional with their real “live” data immediately. Needless to say, the demo was well received. Even more importantly Shenandoah was able to “test drive” the software to prove its applicability before making any dollar commitments.

According to Mark Shank, Information Systems Manager, some baseline measurements were made last year, and it was determined that approximately 50% of their customer orders had shipped on time. As they began using OTTO, on-time order performance rose to 90% for the month. And Shenandoah caught up on its entire backlog and started working ahead on February's orders. In February on-time shipment performance jumped to 92% and subsequently on-time performance has ranged somewhere between 98.3% and 99.5% — well above the 96% goal set by Management.

OTTO provides the means for keeping the whole production organization focused on the few things that have to happen as the ship date approaches to get each order shipped on time. Components that have the potential for delaying an order are identified so they can be managed. Shenandoah's staff, a precious and limited resource, now concentrates on analyzing information and managing the right things at the right time rather than digging out date. To quote one production control individual: “what use to take hours now takes seconds.”

According to Roy Hackett, Plant Manager: "Knowing the right things to pay attention to at the right time — information provided by OTTO — has allowed on-time shipping to be improved by 40 percentage points in less than one month and a lead time reduction from 3-4 weeks to 1-2 weeks on the most important products"

Guessing at what and how much of the work being processed is for real customer orders versus planned orders is eliminated which is especially important when capacity is short during the heavy portion of the business cycle. 

“By focusing on the right things at the right time, production expedites and interruptions are far fewer, production flow is much smoother and productivity is significantly improved.”

Print
31072 Rate this article:
5.0
Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Contact author

x

Categories