Starting the Production Scheduling System

This chapter covers the following topics:

System Startup Overview

You can start the Production Scheduling application from a Microsoft Windows desktop or from a command prompt, depending on your implementation. Starting the system from the Microsoft Windows desktop enables you to take advantage of the Production Scheduling desktop to create and evaluate scheduling scenarios.

Note: This only applies to "standalone" non-integrated versions of Production Scheduling. Startup for integrated versions with E-Business Suite (EBS) or the Process Integration Pack (PIP) occurs from the Workbench.

The Production Scheduling application can be started directly from the command prompt or from a batch routine that can be automatically run at a specific time. The command prompt provides a number of options that enable you to perform any or all of these functions:

Starting Production Scheduling

Note: The procedures in this section pertain to standalone installations only.

This section discusses how to:

Starting the System from the Microsoft Windows Desktop

To start the system from the Microsoft Windows desktop:

  1. Access the Microsoft Windows desktop.

  2. Click the Start button, and then go to Programs, Oracle Value Chain Planning <version number>.

  3. Select Production Scheduling.

Starting Production Scheduling from a Command Line Prompt

To start the system from a command line prompt:

  1. Access the command line.

  2. Navigate using the path: <PS install directory>\scp\<version>\ps\bin.

  3. Enter ps.

Viewing the Installed Production Scheduling Version Number

To view the version of Production Scheduling:

  1. Select About Production Scheduling from the Help menu.

  2. Click Version Information.

  3. Click OK to close Production information dialog box.

  4. Click OK to close About Production Scheduling screen.

Creating, Opening, and Importing a Scenario

This section explains how to:

Creating a New Scenario

To create a new scenario:

  1. Access the Production Scheduling desktop.

  2. From the File menu, select New.

    A new scenario is created in the Model Workspace.

Opening or Importing and Exporting an Existing Scenario

This section discusses how to:

Opening or Importing a Scenario

To open or import a scenario:

  1. Access the Production Scheduling desktop.

  2. From the File menu, select Open and browse to your directory.

  3. From the list of scenarios, select the one you want to open and click Open.

    Alternatively, if no scenarios are listed, browse to the location where you saved the scenario. The scenario can be an .xml, .xml.gz, .ops, .opz, or .dxt file. A .dxt file is a collection of scenarios. Files with the .ops or .opz extension are equivalent to xml and xml.gz files, respectively.

  4. If you have a scenario open and want to open another, the system will ask if you want to import the file into the existing model.

    Select one of these options:

    • Click Yes if you want the first scenario to remain open.

    • Click No if you want to close the first scenario. You are prompted to save the scenario.

If the scenario you are opening or importing is an XML file, the scenario opens along with the associated Gantt charts. If the file is a DXT file, the Gantt chart does not open until a scenario is opened.

Importing a Scenario

There are two options to importing a scenario. You can follow the instructions detailed in the Opening or Importing a Scenario section, or you can:

  1. Right-click on a scenario folder.

  2. Select Import Scenario.

Exporting a Scenario

To export a scenario:

  1. Right-click on the scenario.

  2. Select Export Scenario.

Sending Scenario via E-mail

To send a scenario file via e-mail directly from Production Scheduling:

  1. From the Model Workspace, right-click a scenario and select Send Scenario to Mail Recipient.

    Your e-mail application opens with the scenario file attached to it.

  2. Select the appropriate e-mail recipients and send the e-mail.

  3. To open the scenario file, double-click the e-mail attachment.

    The recipient must have the same version of Production Scheduling installed to view the file.