This chapter covers the following topics:
For information on installing Production Scheduling on Microsoft Windows in a standalone environment that is not integrated with E-Business Suite (EBS), refer to the Oracle Production Scheduling Installation Guide.
The procedures described in this section are only required if you implement Production Scheduling with E-Business Suite.
Apply the following patches only if you are using Production Scheduler integrated with Complex Maintenance Repair Overhaul (cMRO):
9413058:R12.EAM.B - EAM patch
9138126:R12.EAM.B - EAM patch
In release 12.2, there are two files systems (FS1 and FS2) due to the new online patching tech stack. If you upgraded Value Chain Planning to 12.2.0 using 12.2.0 Rapid Install, perform the following procedure after the upgrade is complete:
Note: If you continue upgrade to 12.2.1, these actions are no longer needed. They are required to upgrade to 12.2.0, but not to 12.2.1 and higher.
Source to the FS2 file system on apps tier, and change directories to $MSC_TOP/bin.
Run the following commands:
$perl install_PS.pl $perl install_SNO.pl
Set the following profile option settings after Production Scheduling is installed:
Set "MSC: PS/SNO API Version" to 3.8 at Site Level.
Set "MSC: PS/SNO Data Store Path" to the value of $APPLCSF environment variable at Site Level. This variable is defined in "APPLSYS.env".
If Concurrent Tier and Web Tier are on different machines, set "MSC: PS/SNO Use DB for Integration Data" to "YES".
If users want to download the xml files to the client machine for debugging purpose, set "MSC: PS/SNO Download XML Files" to "YES". The default value is "NO".
To enable the collection of CMRO Work Order demands when running the VCP collections process, set "MSC: Collect CMRO Work Order Demand for PS" to "YES".
If you are using a Windows server for Production Scheduling integration, set the system variables below. This is a one-time mandatory step.
Set SCP_ROOT_DRIVE to the drive where the Oracle product is installed (for example, C:).
Set SCP_MSC_TOP with the MSC_TOP value using forward slash (/).
C:/oracle/VIS/apps/apps_st/appl/msc/12.0.0
Restart the server to apply your environment variable changes.
Set "MSC: PS/SNO Data Store Path" using the forward slash (/).
C:/u01/oracle/viscomn/admin
Review the following when implementing Production Scheduling:
If Oracle Repetitive Manufacturing Optimization (RMO) option is licensed along with Production Scheduling application, then the profile option "MSC: PS Enable CRO Scheduling" must be set to "YES". RMO and CRO are synonymous.
Uninstall Production Scheduling application from your client machine and reinstall again through the Workbench. This step ensures that the latest version of Production Scheduling is applied to client machines.
Production Scheduling is English only. The client application is deployed with translations available. Select Tools from the menu bar, select Language, and choose a language.
As part of your setup, ensure the Production Scheduler responsibility is assigned to the appropriate user.
Ensure that Organization security is enabled for Production Scheduler responsibility.
After applying software patch, restart the application server.