An ACR system parameter allows you to specify whether to measure invoice age from the date on which you create the invoice, invoice date, or the date on which the invoice is due. You can set up a separate terms code for each customer on the system to set the basic terms of payment for that customer. For example, this term could specify the number of days an invoice can be due before it is considered past due and the number of days that a discount is available. The system uses the terms code data to...

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...

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...