Procee Control 2.5 - Organizational Structure

Question

Hello All,
we have just installed the PC 2.5 in QA.
after finishing all post-implementation activities, we saw that the HR structure was created automatically in the PC also.
why is that ? how can we prevent it form happening when we install in PROD ?
what can we do now if we want another structure ?
Thansk

Answer 1

Yudit,
Run the HR table cleanup locally in your QA environment and this will fix the problem.  There are specific changes you have to make locally when you bring up a new system and the HR data cleanup is one of them.  This does not transport.
Most of the following configuration changes are not transportable and must be performed locally when a new system or client is created.  After transports are imported, some or all of the following steps need to be performed.  Steps will vary depending on whether you are creating a new client in an existing system or creating an entirely new system. 
1)  GRC Process Control=>Workflow=>Perform Automatic Workflow Customizing
             - Make sure everything under "Maintain Runtime Environment" and "Classify Tasks as General"
               is activated.
2) GRC Process Control=>Workflow=>Perform Task Specific Customizing
             - Including SA38=>RS_APPL_REFRESH (if necessary)
             - Make sure everything under this activity is performed including "classifying all tasks as
               general" and that event linking" is properly activated.
3) GRC Process Control=>Workflow=>Manage Event Queue
             - Maintain Background Job tab "Number of events per read access to 12u201D. Reschedule job if
               necessary.  Changing this value deletes the bckgrnd job.
4) GRC Process Control=>Workflow=>Transfer Work Items to Replacement
             - Schedule job per IMG / Page 17 of Ops guide
             - Schedule or transfer job execution to BATCHUSER ID
5) GRC Process Control=>Workflow=>Email Notifications=>Schedule job for sending email
             - Schedule job per IMG / Page 17 of Ops guide (every 15 mins)
             - Schedule or transfer job execution to BATCHUSER ID
6) GRC Process Control=>Workflow=>Specify Fallback User for Work Items
             - Review for appropriateness
7) GRC Process Control=>Cases=>Copy Cases to New Timeframe After Signoff
             - Schedule job per IMG / Page 17 of Ops guide
             - Schedule or transfer job execution to BATCHUSER ID
8) GRC Process Control=>Cases=>Copy Documents After Carryforward into New Timeframe
             - There is an ERROR in the IMG setup for this job.  IMG is incorrect.
             - Schedule or transfer job execution to BATCHUSER ID
9) GRC Process Control=>Structure Setup=>Cleanup HR Data=>Delete Table Entries     
10) GRC Process Control=>Structure Setup=>Cleanup HR Data=>Rebuild Directory     
11) GRC Process Control=>Reporting=>Maintain Reporting Buffer
             - Set up Background job according to IMG and NOT Ops Guide
             - Schedule or transfer job execution to BATCHUSER ID
12) GRC Process Control=>Reporting=>Enter Role for Determining Responsible Person for an Object 
     (Optional)
13) GRC Process Control=>Assessment and Test=>Automated Testing and Monitoring=>Register
      Connectors            
             - Review for appropriateness
If you plan on having more than 1 client in a system, include the client number in the job name.  If not, you won't be able to distinguish which job is running in which client (by the job name alone) when viewing jobs in SM37.
I hope this helps.
Matt