Production Scheduling

This chapter covers the following topics:

Production Scheduling Implementation

The procedures described in this section are only required if you implement Production Scheduling Integration V2 with E-Business Suite.

Source Side:

Apply the following patches only if you are using Production Scheduler integrated with Complex Maintenance Repair Overhaul (CMRO):

The following patches are required for Oracle Process Manufacturing (OPM) users when implementing Production Scheduling:

9319734:R12.GMP.B (with the following pre- requisites)
- 8486861:R12.GMA.B (with the following pre- requisites)
  - 7587155:R12.INV.B
  - 7627262:R12.INV.B
- 7015717:R12.GMP.B

Set the following Profile option settings after Production Scheduling is installed:

"MSC: PS/SNO API Version" should be set to 3.5 at Site Level.
"MSC: PS/SNO Data Store Path" should be set to the value of $APPLCSF environment variable at Site Level. This variable is defined in "APPLSYS.env".
"MSC: PS/SNO Use DB for Integration Data" should be set to YES if Concurrent Tier and Web Tier are on different machines.
"MSC: PS/SNO Download XML Files" should be set to YES if users want to download the xml files to the client machine for debugging purpose. The default value is NO.
"MSC: Collect CMRO Work Order Demand for PS" to "Yes" to enable the collection of CMRO Work Order demands when running the VCP collections process.

For users using Windows server for PS V2 integration, the system variables below need to be set in the server. This is a one-time mandatory step.

SCP_ROOT_DRIVE has to be set with the drive where the Oracle product is installed. For example, C:
SCP_MSC_TOP has to be set with the MSC_TOP value with forward slash.
```
C:/oracle/VIS/apps/apps_st/appl/msc/12.0.0
```
Restarting the machine is needed to make these environment variables take effect.
Profile option "MSC: PS/SNO Data Store Path" should be set with the forward slash.
```
C:/u01/oracle/viscomn/admin
```

Review the following when implementing Production Scheduling:

If RMO (Oracle Repetitive Manufacturing Optimization) option is licensed along with Production Scheduling application, the profile option "MSC: PS Enable CRO Scheduling" must be set to "YES". RMO and CRO are synonymous.
Please un-install Production Scheduler application from your client machine and re-install again through the Workbench. This step helps to get the latest Production Scheduler build on the client.
Production Scheduler is English only. The EBS translations can be downloaded from My Oracle Support as they become available.
As part of your setup, you should ensure that you assign the Production Scheduler responsibility to the appropriate user.
Please ensure that Organization security is enabled for Production Scheduler responsibility.
After patch application it is recommended to restart the application server.