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

For years, repetitive manufacturing industries have been applying many of the principles in Just-in-Time philosophy. They have established balanced production lines that depend on a steady flow of material to each work station. They schedule production in daily or weekly rates rather than in discrete shop order lots. They track finished inventory by work center rather than by job. They typically backflush stock balances (decrement stock balances upon completion of specific manufacturing steps rather than issued at the beginning of each production run).

Costing is typically based upon a daily rate or hourly rate rather than being associated with specific shop orders. 

Repetitive manufacturers use MRP II software adaptable to their environments

in the following key areas:

▪ Product definition

▪ Inventory tracking

▪ MRP/Master Scheduling

▪ Shop Floor Control

▪ Purchasing

▪ Costing

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.