Define Scheduling Configuration

Explanation

This activity is used to configure the Planning and Scheduling Optimization Integration. The following parameters are configurable:

Parameter Description Parameter values
Planning and Scheduling Optimization Version

 

The Version of the Scheduling Engine on the Scheduling Server. Select a valid value from the list.
Planning and Scheduling Workbench Directory The address of the server where the Scheduling Workbench is installed. The value entered here will navigate by default to the Scheduling Workbench page in IFS Aurena. A valid web address where the Planning and Scheduling Workbench is installed, e.g. http://[PSO_SERVER_NAME]/IFSPSOWorkbench
Scheduling Workbench Directory The address of the server where the Scheduling Workbench is installed. The value entered here will be displayed by default in the Scheduling Workbench login dialog. A valid web address where the Scheduling Workbench is installed, e.g. http://[PSO_SERVER_NAME]/IFSSchedulingWorkbench.
Scheduling Workbench Login Dialog

If the parameter is set to 'Yes', the user has to use the login credentials to login to the Scheduling Workbench and it should not be configured for Active Directory.

If the Scheduling Workbench is configured for Active Directory this parameter has to be set as 'No'. Then the login dialog will be bypassed and the windows authentication is used to login to the Scheduling Workbench.

Default value is 'Yes'.
Dataset Prefix  Using a prefix makes it possible to use the same Dataset ID in many environments while using a single Planning and Scheduling Optimization installation by appending the Dataset Prefix with the Dataset ID. The combined value is used to create the Dataset ID used in Planning and Scheduling Optimization. Any value (e.g. COMP10), including a substitution variable (e.g. #DB_HOST#).
Dataset Default Time Zone

 

This parameter sets the default value for Time Zone when creating new datasets. Select a valid value from the list, for instance Africa/Algiers, Europe/Berlin, America/Chicago, Asia/Dubai, Australia/Sydney.
Dataset Schedule from Work Task Status This parameter sets the default value for Schedule from Work Task Status when creating new datasets. Select a valid value from the list, e.g. Released.
IFS Applications URL The base address that Planning and Scheduling Optimization (PSO) is using when communicating with IFS Applications. In most cases it is not necessary to change the default value in the scheduling configuration. This value represents the substitution variable #URL# used in other places in the scheduling configuration. The default value is same as the parameter Extended Server Url configured in Solution Manager/System Parameters
Broadcast URL Address of the Web Service (SOAP Gateway) in IFS Applications. It is recommended to use this value as a substitution variable for a scheduling broadcast. In most cases it is not necessary to change the default value in the scheduling configuration. It also allows using substitution variable #URL# (e.g., #URL#/int/soapgateway) and the #URL# will then be replaced by the value defined in IFS Applications URL The default value is same as the parameter Extended Server Url configured in Solution Manager/System Parameters with the addition "/int/soapgateway", e.g. http://servername:port/int/soapgateway.
Broadcast User Name Name of the user that is allowed to access the Planning and Scheduling Optimization Integration (user granted to the permission set SCH360_WEBSERVICE). Defining the Broadcast User Name in the scheduling configuration allows to use this value as a substitution variable when defining scheduling broadcasts. It is recommended to set this parameter here and use this value as a substitution variable for a scheduling broadcast.
Broadcast Password Password of the user that is allowed to access the Planning and Scheduling Optimization Integration (password of user granted to the permission set SCH360_WEBSERVICE). Defining the Broadcast Password in the scheduling configuration allows to use this value as a substitution variable when defining scheduling broadcasts. It is recommended to set this parameter here and use this value as a substitution variable for a scheduling broadcast.
Broadcast File Path The output path of the broadcast as seen from the Schedule Broadcast Manager service on the Planning and Scheduling Optimization (PSO) server, e.g. "C:\IFS\Scheduling\Output". The path should correspond to the file reader input folder in IFS Connect on the IFS Applications server for processing files from PSO. Defining the Broadcast File Path in the scheduling configuration allows to use this value as a substitution variable when defining scheduling broadcasts. It is recommended to set this parameter here and use this value as a substitution variable for a scheduling broadcast.
Load Transfer Method The default Transfer Method of the scheduling data for Load messages. Select a valid value from the list, Webservice or File.
Change Transfer Method The default Transfer Method of the scheduling data for Change messages. Select a valid value from the list, Webservice or File.
Instant Transfer Enabled If this parameter is set to 'Yes' changes are sent instantly to the Scheduling Engine so the user do not have to wait for the scheduled database task to run. Select a valid value from the list. Default value is 'Yes'
Schedule Receiver Makes it possible to define the data that should be included in outbound application messages, i.e. the messages which are produced for the scheduled tasks used to transfer data to the Scheduling Engine. The data entered in the value for this parameter will be shown on the Receiver field for each message.
  • #DATASET_ID# - The identity of the dataset entered on the scheduled task.
  • #INPUT_TYPE# - The input type entered on the scheduled task, e.g., LOAD, CHANGE and STOP.
  • #TRANSFER_ID# - The transfer ID which is generated when sending the messages to PSO.
  • #SUBMISSION_TYPE# - Valid values are CHANGE when timeline information is sent, TIMELINE when empty or the same value as #INPUT_TYPE#.
  • #RECORD_COUNT# - The number of records in the Sch360_Transfer table marked for transfer. Only applicable for CHANGE messages. For LOAD messages it will contain *.
  • #PROCESS_TYPE# - The process type from the dataset, i.e., DYNAMIC or STATIC.
  • #COMPANY# - The company from the dataset.
  • #BACKGROUND_JOB_ID# - The identity of the background job. Only applicable if running as a background job.
  • #URL# - The address of the application server, e.g., http://<server name>:<port>.
  • #DB_NAME# - The name of the database.
  • #DB_HOST# - The name of the server the database is hosted on.
  • #EXTERNAL_DATASET_ID# - The identity of the dataset used in Scheduling. This can be either :
    • Dataset Prefix-Dataset ID, if a dataset prefix has been defined or
    • The same as the dataset identity if no dataset prefix has been defined.
  • #ACTIVITY_ID# - This will display the Activity ID of for instance, an application message and will be quite useful when it comes to tracking application messages for Appointment Requests.
Schedule Information Makes it possible to define the data that should be included in outbound application messages, i.e. the messages which are produced for the scheduled tasks used to transfer data to the Scheduling Engine. The data entered in the value for this parameter will be shown in the Subject field for each message.
  • #DATASET_ID# - The identity of the dataset entered on the scheduled task.
  • #INPUT_TYPE# - The input type entered on the scheduled task, e.g., LOAD, CHANGE and STOP.
  • #TRANSFER_ID# - The transfer ID which is generated when sending the messages to PSO.
  • #SUBMISSION_TYPE# - Valid values are CHANGE when timeline information is sent, TIMELINE when empty or the same value as #INPUT_TYPE#.
  • #RECORD_COUNT# - The number of records in the Sch360_Transfer table marked for transfer. Only applicable for CHANGE messages. For LOAD messages it will contain *.
  • #PROCESS_TYPE# - The process type from the dataset, i.e., DYNAMIC or STATIC.
  • #COMPANY# - The company from the dataset.
  • #BACKGROUND_JOB_ID# - The identity of the background job. Only applicable if running as a background job.
  • #URL# - The address of the application server, e.g., http://<server name>:<port>.
  • #DB_NAME# - The name of the database.
  • #DB_HOST# - The name of the server the database is hosted on.
  • #EXTERNAL_DATASET_ID# - The identity of the dataset used in Scheduling. This can be either :
    • Dataset Prefix-Dataset ID, if a dataset prefix has been defined or
    • The same as the dataset identity if no dataset prefix has been defined.
  • #ACTIVITY_ID# - This will display the Activity ID of for instance, an application message and will be quite useful when it comes to tracking application messages for Appointment Requests.
Plan Information Makes it possible to define the data that should be included in the inbound application messages, i.e. the messages which are received from the Scheduling Engine. The data entered in the value for this parameter will be shown in the Subject field for each message. Any text including substitution variables (e.g. Plan ID: #PLAN_ID#, Dataset ID: #DATASET_ID#, Type: #PLAN_TYPE#, Broadcast ID: #BROADCAST_ID# ).

The available substitution variables can be found in the parameter value list for Plan Information. 

Trace Information If the parameter is set to 'Yes', additional trace information will be output when transferring scheduling data. This information will be displayed on the background job, or in the debug console if not executing as a background job. It is recommended that this parameter is only set to 'Yes' when additional information is required for investigation purposes. The additional trace information is stored on each background job and this may impact the processing time of the job. Default value is 'NO'.
Input Data Path Input Data Path can point to additional XML files conforming to this definition to be loaded. This file is merged with existing XML data set prior to processing. The XML file may itself also point to an additional file of XML to be loaded. This Input Data Path needs to point to an existing directory and file name on the Scheduling Server running the Schedule Input Manager service. The Input Data Path can be used for for defining an xml containing rules for the Schedule Dispatch Service (SDS). Valid values are a complete data path containing directory and file name, e.g. C:\IFS\Scheduling\SDS\rules.xml Substitution variables may be used when defining the input data path. For more information on substitution variables please refer to the activity Define Scheduling Configuration.
Implicit Breaks This parameter is used to define breaks as Implicit Breaks. When the DSE makes changes to a plan, it does not consider making changes to the implicit breaks. Instead, the implicit breaks are deterministically placed into the plan, based on a set of rules. Implicit breaks do not have an SLA or base value, but will always be scheduled if it is possible to do so. Default value is 'NO'.
Object Group Filter Controls whether object groups are to be transferred to scheduling or not. See documentation for Define Dataset for further information on object groups in scheduling. If this parameter is set to None, object groups will not be transferred to scheduling. If this parameter is set to Site, object groups will be transferred using site as the group. Default value is 'Site'.
Resource Detail Form Makes it possible to define the address link from the resource detail form in Scheduling Workbench to an IFS Applications form. The value may include substitution variables from the drop down list such as #URL# and #RESOURCE_SEQ#. The title of the address link is automatically fetched from the IFS Applications form name in the value in the address link. It is also possible to define the title of the address link by entering it within curly brackets {My Form Name} anywhere in the parameter value. Default value is the Resource Detail form (#URL#/client/runtime/Ifs.Fnd.Explorer.application?url=ifsapf%3AfrmResourceDetailHead%3Faction%3Dget%26key1%3D#RESOURCE_SEQ#)
Activity Detail Form Makes it possible to define the address link from the activity detail form in Scheduling Workbench to an IFS Applications form. The value may include substitution variables from the drop down list such as #URL# and #TASK_SEQ#. The title of the address link is automatically fetched from the IFS Applications form name in the value in the address link. The title of the address link is automatically fetched from the IFS Applications form name in the value in the address link. It is also possible to define the title of the address link by entering it within curly brackets {My Form Name} anywhere in the parameter value. Default value is the Work Task form (#URL#/client/runtime/Ifs.Fnd.Explorer.application?url=ifsapf%3AfrmJtTaskTab%3Faction%3Dget%26key1%3D#TASK_SEQ#)
Appointment Booking Layout Mode Makes it possible to define the appointment booking layout, i.e. grid layout, calendar layout or both. Possible values are "Calendar", "Grid", "Calendar,Grid" or "Grid,Calendar".
Request Timeout (Seconds) Makes it possible to set the timeout (in seconds) for an Appointment Request. If no offers are received from the ABE within the timeout then a warning message is raised.  Default is 30 seconds.
Offer Timeout (Seconds) Makes it possible to set the timeout (in seconds) for an Appointment Offer. If no offers are accepted within the timeout then the ABE releases the offered slots. The default value is 600 seconds.
Poll Rate (Seconds) Makes it possible to set the polling rate of the appointment window when an appointment request has been made and it is waiting for offers to be returned from the ABE. The default value is 1 second.
Cleanup Wait Time (Seconds) This is the parameter that tells the schedule task (Cleanup Scheduling) how often it should be carrying out its clean up job. Once it is triggered, the appointment request/ offers which are not handled will be removed. The value should be in seconds.

Note: The Parameter Scope can either be Global or Dataset. Parameters with scope Global can only be defined on the Scheduling Configuration form and will apply to all datasets. Parameters with scope Dataset can be defined on individual datasets as an override to the global setting. The global setting on the Scheduling Configuration form will apply if a parameter has not been configured on the dataset.

Prerequisites

N/A

System Effects

N/A

Window

Scheduling Configuration

Related Window Descriptions

Scheduling Configuration

Procedure

To configure the Planning and Scheduling Optimization Integration:

  1. Open the Scheduling Configuration window.
  2. In the Parameter Value field, enter a value for the parameter or select from the list.
  3. Save the information (F12).