Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News, Crossroads Connection

In the Financial Statements module, you can:

• Define financial statements, and link a structure of child statement accounts and parent statement accounts to these financial statements.
• Link ledger accounts and/or dimensions to the statement accounts.
• Link cash flow reasons to cash flow statement accounts.
• Export financial data to FST reporting tables.
• Print reports directly, or use the BIRT report functionality to print to PDF, HTML, and export to Excel or Word.

Data drill down in financial statements - You can...

The planning data for the method of manufacturing is defined in Routing. A routing consists of operations, with each operation identifying the last to be carried out in a work center and/or on a certain machine defined for a specific site.

Routings can be as follows:

• Standard Routing - A generic routing that can be attached to multiple items
• Item specific - A routing that is applied to one item
• Network routing - A routing containing sequentially ordered operations and parallel operations
• Order quantity dependent routing - A routing that is defined for a specific quantity of items

You use the Routing module to record routings for manufactured items. You can define the following:

Operations are automatically backward scheduled at shop order release time. The backward scheduling algorithm starts with the shop order due date and schedules each operation based upon the standard move and queue times in the routings and the number of days the job is expected to run at standard. The system calculates and stores the operation scheduled start date. The dates may be modified by the shop order maintenance program. The number of days that a job is expected to run an operation is dependent upon the available capacity for that work center and the total hours scheduled for that operation.

The backward scheduling algorithm also considers...

The Infor Development Framework (IDF) re-architects the way a user interacts with the application. IDF provides an efficient, task-oriented process to view application information that is contained within Infor LX. IDF enables users to configure their view of the application data without modifying the core application and its supportability.

The examples below describe how users can configure their display of data and maximize overall productivity:

• Arrange application information into multiple groupings and sequences that make sense for the job.
• Hide information that does not apply to a particular job or task.
• Filter records to show only the information that applies to the job or task that the user is performing.
• Customize the information for an individual user, for a group of users, or for all users.
   

To improve performance and reduce database growth, deleting records is highly effective. The disadvantage of deleting records is that data is no longer available. Usually, however, not all records need to be saved. For example, line activities are stored by warehouse. Normally, you do not need to keep these records. Therefore, after closing a warehouse order, line activities can be removed. The User's Guide for ERP LN Archiving and the corresponding Baan IV/V Guides describe several sessions you can use to delete old data. Other data such as items and business partners can be reviewed once in a while, after which you can delete the data you no longer need. For every order and contract table, a session is available to archive and delete old orders. In these sessions, you can specify several characteristics to select the orders to be removed, such as date or status. Run these sessions on a regular basis.