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.
   

Did you know?  Product interface list, SYS635D

This program creates a report that contains all interface program call records that were created for the Infor LX programs specified in the range on this screen. The report contains a line for each record found. The line displays the following information:

• The name of an Infor LX program that contains a user exit to an add-on program
• The interface point in the Infor LX program, that is, an identifier of the point in the program code where the user exit is requested
• The execution sequence number of the record, because more than one add-on program can exist that can run from the same interface point
• The add-on program to call at the interface point. The Add-on Product Interface file, ZXI, stores the records.

Access: Menu SYS

You can use job management to schedule jobs based on your organizational requirements. For example, you can schedule jobs at non-peak hours to improve the overall system performance in a heavily loaded environment. A job consists of one or more sessions or shell commands, or both, that run without user interaction. The sessions and shell commands in a job can be started while you are not logged on to the ERP system. You can schedule jobs to start processes periodically, at a defined interval, or immediately. Typically, you use job management for print and processing sessions.

Job data  - To create a job, you must specify basic job data and link sessions or shell commands, or both, to the job. In the basic job data, you specify whether the job is periodical. For periodical jobs, you specify how the job will be scheduled.

Shared job data tables  - Typically, each company stores its own basic job data. As a result, a job runs for a particular company. However, in a job, you can also run sessions in more than one company. You can run sessions in multiple companies when the job data tables of the associated companies are physically mapped to a single main company.

Job execution - Jobs can be started in multiple ways. The job’s status defines how you can start the job. You can start the job if the job’s status is In Queue or Free.

Job history -  When the execution of a job stops, for example, when the job completes successfully or when a runtime error occurs, information is written to a history log. The job history contains information, such as the date and time of the execution and the reasons why the job and its associated session ended.

Sales quotations are used to supply a sold-to business partner with the required details to make a purchasing decision.

You can create a sales quotation in response to a request for quotation (RFQ) from a business partner, or as a sales tool to initiate the sales process with potential business partners. A quotation includes the dates, terms, items, or item descriptions to be sold, and a success percentage, which reflects the level of certainty that the quotation will be accepted. Sales quotations are included in the planning modules based on their success percentages. Quotations with a high success percentage are considered as sold.

You can print and send quotations to business partners. You can specify the results of the returned quotations in Sales. If the quotation is not accepted, you can...