Use the Production Register Listing screen, JIT610D1-01, to print an edit list of the labor tickets that you added or updated. Use this report to see the data to post before you actually perform the update. After you print the edit list, you can go back to Production Reporting (JIT600) and change the data before you post the batch. The program assigns a number to each production report that you posted in JIT600. You can use JIT600 to reference the production report that you want to update. Access: Specify Post on Production Reporting, JIT600D1-01.

This program generates an uncosted items listing for the specified facility and cost set. You can use this report as an exception listing to identify those items that are currently maintained at zero cost or new items that require entry prior to cost rollup in Cost Set Rollup, CST500.

If a facility-specific component cost does not exist for a parent being rolled up, zero cost is rolled up for the component. When a new parent item is being rolled up for the first time, the audit report for Cost Rollup, CST500, displays a warning wherever a component cost is zero. Rolling up the parent cost again does not display a message for zero component costs.

Access: Menu CST01

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