Define Inventory transactions for issuing components to the shop and receiving finished items. See the Inventory help text for examples of transactions.

• Transaction type I - Single Issue to Shop Order. Use this transaction type to issue one component at a time. Use this for high-value items that are marked as Must Single Issue on the Item Master file.
• Transaction type M - Multiple Issue to Shop Order. Use this transaction type to issue all the components as listed in the Shop Order, in one transaction. Note that this transaction type does not issue Must Single Issue items.
• Transaction type S - Receipt from shop. Use this transaction type to receive the finished item into stock and update the shop order accordingly. 

The Shop Order Lot/Location Allocation program is an alternative to using the above Inventory transactions. Use this when the item is finished, and you want to review exactly what was used to make it. You can review the components as allocated, make any changes, and finally accept the finished order.

You can define internal trade relationships between enterprise units or individual warehouses of the same logistic company for the transfer of material, labor, or other costs between warehouses, and to generate invoices for these without using sales orders and purchase orders. For example, you can use this to transfer goods between warehouses in different countries.

You can define warehouse surcharges, which are added to the actual costs of the goods either when the goods are issued from a warehouse or when the goods are received.

The system allows you to manipulate and maintain a simulated MPS and MRP. You can copy the simulation from the existing first cut, or you can create a totally new schedule. You can also perform a simulation of the rough-cut capacity plan. This allows a quick visual inspection by inquiry or menu of needed work center

loads for the proposed MPS. After you choose a suitable MPS and rough-cut capacity, the system allows you to transfer the simulated MPS to the live Master Production Schedule.

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.

The challenge in cost accounting is tracking your manufacturing to the levels needed for useful management information. You need feedback for corrective action; but, you need to minimize the cost of collection. Some parts of your operation require specific job-cost tracking while the Just-in-Time areas require

costing in terms of cost per process hour or day. Apply overhead in different ways to different processes and products. Segregate costs into enough detail

to provide management with an accurate picture of the contents of your product. Material, material overhead, labor, fixed overhead, variable overhead, outside processing, outside processing overhead, and so forth all have to be considered.

LX meets your cost accounting needs with the following functionality:

▪ Four sets of costs: actual, standard, frozen standard, and simulated

▪ Nine user-defined elements per set

▪ Full and partial cost roll-up and simulation

▪ Cumulative in-process cost tracking

▪ Cost summaries by item

▪ Cost definition tied to work centers or material type

▪ Process hour costing