Defining the Product Routing first requires the items to be setup in the Item Master file. Other master files also need to be defined prior to creating the routing.
These include:

• The Facility defined with a SYS program
• The Warehouses defined with an INV program
• Locations defined with an INV program
• The Machines (required if using capacity planning or an MES interface) defined with an MDM program

After the above data is set up, the Department file and Work Center files can be setup in MDM. Now you are ready to define a product route.

• Print Sales Order History Information
  • all invoices processed through sales
• Check Inventory Valuation
  • this should tie out to your inventory accounts
• Print Integration Information
  • see all postings from WIP to finished goods

• Print G/L Transaction Information
  • print specific transaction types for any GL account

• Print Lot Control Information
  • will show where serial numbers were used

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.

In Baan IV, the order balance amount always includes the tax amount. Consequently, the tax amount must be recalculated every time an order line is modified in order to update the balance correctly. If the tax provider is activated, this requires an API call for every re-calculation of tax.

In Infor LN, users can select or clear the new Include Tax in Order Balance check box in the COM Parameters (tccom0000s000) session to indicate whether users want to include tax amounts in the order balance amount. This parameter has an effect on various sessions in Order Management.

In ERP LX, this function is called Backward Scheduling. This is a simple, easy way to create and release shop orders associated with the end item.

The result is a shop calendar with the associated order start dates. Setting up ERP LX properly with correct Queue Times, Setup and Run Times, along with Move Times, will result in accurate shop order start dates.

Cycle Count Orders cannot be directly “back dated” in Baan IV, Baan V or LN, however, there are some work-arounds.

Establishing the Quantity On-Hand and the Quantity Available.

LX maintains buckets for information associated with the following inventory transactions for each item:

• Opening Balance
• Issues
• Receipts
• Adjustments
• Allocations for the Customer
• Allocations for Manufacturing

The on hand quantity does not include any allocations. To arrive at the on hand quantity, start with the opening balance, less any issues, plus any receipts, then add or subtract any adjustments. Available inventory is the on-hand less any allocations.

Zero sublevel accounts are posting level accounts. All others are parent accounts. Once the balances have been updated in the child ledger accounts, the parents are automatically updated.

Inquiries and reports can be printed or displayed either by child accounts or by parent accounts. On line drill-down is possible from either child or parent.