Recommendation
PeopleSoft advises that removing run control ids is not recommended as they are referred to throughout the system from many other places so further corruption could occur. Further, they state that it is not recommended that application run controls be deleted because it may be used by more than one process or may be part of a recurring process or may contain default settings used by more than one user. For these reasons, VCCS advises against removing run control ids.
Background
When a user creates a run control id, it’s created in many places in the database.
Process Run Controls are created automatically by the system when a user creates a process request. The process run controls are stored in multiple PeopleTools tables. User ID and Run Control ID are keys to each of these tables.
Application Run Controls are created by a user when he/she submits a process to run. It holds parameters required and specific to the process/program. When the Application Run Control is created, it triggers the system to create the Process Run Controls as well using the same Run Control ID as the key.
From the end-user perspective, there's no distinction between Process and Application Run Controls. The Process Run Control is assigned the exact same name/id as the Application Run Control. However, it's important for application developers to distinguish between the two when creating new application process/program. Process run control and application run control are stored in different tables. PeopleTools delivers the table to store only the process run control. Application developer is responsible for creating the application run control table to store the application run control information.
Application run control tables may be delivered or custom tables and it is extremely difficult to identify every run control table a specific run control id has been used. As a result, deleting a run control id can cause corruption which could result in unexpected behavior for users.