Configure P&S Server
The P&S Server Settings (PSSRV) page contains the settings that configure the Planning and Scheduling Server.
Different sections within the P&S Server Settings (PSSRV) page contain settings that configure the server during different stages. The system, by default turns on or turns off the settings.
To configure the P&S server
-
Open the P&S Server Settings (PSSRV) page.
- Select Utilities > Company Setup > Module Setup > P&S Server Settings.
Or
- Search for PSSRV or Server Settings in the Navigation box and then select P&S Server Settings.
The P&S Server Settings (PSSRV) page appears.
-
Select or clear the check boxes that correspond to the required setting that’s in the following sections. Some check boxes, after selection, may show further values within a list.
| Section | Description | Default Value |
|---|---|---|
| Startup | Sync 2 ERP Select to invoke the M2MReceiving Handler, and have the MSMQ messages from Planning and Scheduling update the M2M ERP database. | Cleared |
| ERP 2 Sync Select to have any relevant updates in M2M ERP update the Planning and Scheduling Server so that the Planning and Scheduling memory model matches the ERP database. | Selected | |
| Use Auto Create Jobs | Cleared | |
| Completed By Qty To Go | Selected | |
| Set Completed Materials A job material that belongs to a job operation that’s already completed, but is not yet issued is marked with (C) on the P&S pages. If selected, these job materials consume On Hand inventory, if it exists, but are ignored otherwise. This logic accounts for a backflush situation in which the issue transactions are delayed until the job is completed. This situation can also occur when material is needed in a late operation but this is not specified in the job BOM. We recommend to fix this data issue. If you want these job materials to be considered as regular demand (until the BOM data is fixed), you can clear the check box. With the check box cleared, the job materials marked with (C) are considered as regular demands. | Cleared | |
| Runtime | Defer Completion Transactions [!Note] We strongly recommend not to change the default setting in environments where you use CTP. | Selected |
| Defer All Transactions Select to defer all ERP transactions and make them visible in the Planning and Scheduling system only when the user runs Planning, Scheduling, Re-scheduling, or Realign Schedule. | Cleared | |
| Limit Sim Ops By Qty To Go | Cleared | |
| Plan | Allow Negative On Hand | Cleared |
| Automatic Firming Upon Accept | Cleared | |
| Assembly Buffer For Use the assembly buffer in one of the following three options: | Stock | |
| Built To Upper Tolerance Select to have the Planning engine attempt to cover the requested SO release quantity inflated by the upper tolerance. However, the system considers the SO release as fulfilled, if the requested quantity was shipped. | Cleared | |
| Forecast Retention | Current Period | |
| Forecast Dep Demand | Selected | |
| Job Outstanding Qty By Operation | Selected | |
| Modify Firmed Job Due Dates Select to have Planning change the due date of a Firmed and Released job. Clear so that Planning cannot change the due date of a Firmed and Released job. | Selected | |
| Modify Firmed PPO Due Dates | Selected | |
| Modify Firmed ISO Due Dates | Selected | |
| Planning Preserve Make SO Split To preserve a customer’s job splitting, Planning doesn’t change existing jobs in case the total of the jobs’ quantity equals the demand quantity of the SO release. [!Note] Unlike Planning, the Balance command on the Material Availability (RPMAVL) page adjusts the quantities of the jobs according to the lot sizing parameters regardless of this setting. | Selected | |
| Safety Stock On LT | Selected | |
| Show Floor Stock Parts | Selected | |
| Max Low Level No The maximum number of BOM levels for planning. The BOM levels can be selected from a default value of 20 to the range between 1- 99. | 20 | |
| Schedule | Adjust Purchasing To Schedule | Cleared |
| Adjust IDO To Schedule | Cleared | |
| Adjust Child Schedule To Parent | Selected | |
| Horizon Factor The Scheduling Horizon defines the date range of jobs included in the schedule. Jobs are included in the schedule if their Due Dates are within the Scheduling Horizon. However, it’s not known how far the schedule will span. The Horizon Factor defines how far the schedule can span. The default is six times the Scheduling Horizon. | 6 | |
| Priority 1 Days The number of days by which the need time of a priority 1 job is advanced. By offsetting the need time, the operations of this job and the jobs that feed it have a better chance to be scheduled on time. The larger the offset, the earlier the job tends to end because it’s considered earlier in the schedule queue. However, ending too early increases inventory. | 20 | |
| Priority 2 Days The number of days by which the need time of a priority 2 job is advanced. By offsetting the need time, the operations of this job and the jobs that feed it have a better chance to be scheduled on time. | 10 | |
| Priority 3 Days The number of days by which the need time of a priority 3 job is advanced. By offsetting the need time, the operations of this job and the jobs that feed it have a better chance to be scheduled on time. | 5 | |
| Improvement Cycles The number of improvement cycles. Improvement cycles stop during one of the following cases: | 2 | |
| Restriction On Operation Overlap Select to prevent a short-duration operation from finishing before the previous operation. The end time of the short-duration operation (with negative move time) will always be greater than or equal to the previous operation’s end time. | Selected | |
| Schedule Open Jobs Inside Release Offset Clear to schedule the open job orders only beyond the Schedule start + Release Date Offset [defined in the Global Parameters (PSGLPARM) page]. Applicable in Scheduling, Rescheduling, and CTP. | Cleared | |
| Preserve Machine Usage On Reschedule This setting applies only to partitioned work centers. [!Note] We recommend that you select this setting only when using Sequence by Characteristic at the machine level. | Cleared | |
| Preserve Manual Sequence Changes Clear to preserve the manual sequence changes only inside the Time Fence, that are done by dragging on the Gantt in the full scheduling run. | Cleared | |
| Contiguous Operations On WC | All | |
| Frozen Logic Clear to turn off the freezing feature, and to ignore the Frozen property. | Selected | |
| High Priority For Released Jobs Select to schedule Released jobs with a higher priority than Open jobs. | Selected | |
| Multiply Additional Resources | Selected | |
| Multiple Bars Per Node | Selected | |
| Setup Reduction WC | CCR | |
| Sub Contract Purchase Buffer The size of the Sub-Contract Purchasing Buffer in days. | 1 | |
| Reschedule In Sequence By Characteristic [!Note] In this case, the user must invoke Rescheduling manually at the end of the Sequence By Characteristic process. Use the setting with the cleared check box if Sequence By Characteristic is done on multiple work centers. This ensures that Rescheduling is run only once. | Selected | |
| On Hold Off Set Increment Defines the time fence in which a job in On Hold status cannot be scheduled. This time fence is defined as: Current Date + Release Offset + On Hold Offset Increment On Hold jobs can be scheduled only behind this time fence. | 0 | |
- On the Toolbar, click Save.
A message, Planning and Scheduling Server Name configuration have been modified. Screen will auto refresh in <number> seconds. Do not Refresh appears.
Click Do not Refresh to prevent Made2Manage from refreshing.