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

George Moroses

Infor LX & BPCS Tip of the Week: Production History Purge

Did you know that you can clear production history?

JIT900 - Production History Purge

To clear field values from Production History Inquiry (JIT300). Run monthly as Day End Run and Month End Run which clears M-T-D fields.  There is an option to clear the average per hour and maximum per hour fields. This program can be run as often as you wish.

Previous Article Infor M3 Tip: Personalization Tools in M3: Setting a field to be mandatory
Next Article Infor M3 & Movex Tip: What is a Start Page?
Print
32478 Rate this article:
5.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

This is a simple way to go from the customer order to making the order and shipping the order. It involves a few simple steps:

  1. Receive and enter the customer order
  2. Automatic credit review
  3. Automatic release of the shop order tied to the customer order
  4. Issue material, report labor to the production order receipt
  5. Pick the order, ship the order, invoice the customer

With lean, you can skip processing the demand through MRP. You can go directly from the customer order to the shop order creation.

If you setup the “From” and “To” Location fields in the Work Center file, this will then determine the locations for material issue transactions and production reporting transactions.

The reporting of the transactions would happen through production reporting, JIT600, or using the Shop Floor labor posting, SFC600, or Shop Floor Posting from SFC650.

Remember, any location used in the work center file must first be set up in the location master file. Using an MES solution by-passes the need to key any of the data to ERP LX.

First129130131132134136137138Last

Theme picker

Tips: LN | Baan

Instead of sharing tables through logical linking, you can replicate table content between companies. This approach allows certain non-key attributes of a record to vary by company. For example, if you replicate bills of materials rather than sharing them, each company can associate a different warehouse with the same bill of material. This way, the bills of materials are consistent across companies, while the warehouses can differ.

Replication also enables selective availability of records in other companies. For instance, when replicating items, you might limit which items are available in a sales company based on their item group, only including end items. You can further refine replication to specific subsets, such as particular item groups.

Keep in mind that replication requires any referenced tables to be either replicated or shared as well.

12345678910Last

Theme picker

Categories