Setting Up Shell Templates with Multiple Base Commit BPs with Multiple Payment Applications and SOVs

To accommodate multiple contract types or commitments in a project, you can now include more than one Base Commit BP wherein each Base commit BP is associated with a payment application and a distinct schedule of values (SOV).

Note:

With this setup, you are no longer limited to configuring only one Base Commit BP with a payment application and SOV in each project.

You can also watch the video: Using Multiple Payments in a Single Shell

Prerequisite

You have created one or more Base Commit BPs with payment applications and corresponding SOVs.

Business Process Setup Procedure for Shell Templates

To set up multiple Base Commit BPs with payment applications and corresponding SOVs in shell templates:

1. Select the Company Workspace tab, and switch to Admin mode.
2. In the left Navigator, select Templates, select Shells, and select Projects.
3. In the Project Templates log on the right pane, select a project/shell template.
4. In the left Navigator of the selected project/shell template, select Setup, and select Business Process.
   1. In the Business Process Setup - Current View log, select New.
   2. In the New Business Processes window, select a Base Commit BP with payment applications.
   3. Select OK to include the Base Commit BP in the Business Process Setup - Current View log.
   4. Repeat the above step sequence to add multiple Base Commit BPs.
   5. Select OK to confirm the alert message that displays when you add subsequent Base Commit BPs in the project/shell template.

      With this setup, the Schedule of Values log is relocated in the left Navigator. Contact your Company Administrator if you do not have access to the new SOV log location.

5. To set up a workflow for each Base Commit BP added in the Business Process Setup - Current View log:
   1. In the left Navigator, select Setup, select Business Process, select [Base Commit BP Name], and select Workflow Setup.
   2. In the <BP Name> Setup - Current View log, add or modify the workflow of the Base Commit BP.
6. To verify that a Schedule of Values (SOV) is created for each Base Commit BP in the project/shell template:
   1. In the left Navigator, select Cost Manager, select Schedule of Values, and select Payment Applications.
   2. Confirm you can view the new Schedule of Values node created for each Base Commit BP.
   3. Proceed to create a SOV structure for each Schedule of Values node. For more information, see Payment Applications (SOV Structure).
7. To update the above modifications from shell templates in individual shells, see Update Schedule of Values Structure.
8. To grant users with permissions to access and use multiple Base Commit BPs:
   1. If User Mode Navigator is not defined:
      1. In the left Navigator, select Access Control node in the selected shell template.
      2. In the right pane, select User Mode Access, select Financial Analysis, select Schedule of Values, and select Payment Applications (a new node listing multiple Base Commit SOVs)

         For example, the following nodes display in Access Control by default:

         Schedule of Values, followed by Payment Applications

         Schedule of Values, followed by Payment Applications, followed by [Base commit BP Name], followed by - SOV

   2. If User Mode Navigator is defined:
      1. In the left Navigator, select the Access control node in the selected shell template.
      2. In the right pane, select User Mode Access, and select [select the custom-defined node containing the multiple Base Commit SOVs].

         For example, the following nodes display in Access Control by default:

         Schedule of Values, followed by Payment Applications

         User Mode Navigator for project/shell displays [Base commit BP Name] - SOV

   3. In the Access Control log on the right pane, select Schedule of Values, and select Payment applications.
   4. Select each SOV node and set up permissions and user access. For more information, see Updating Shells - Access Control Node.

      Note:

      It is recommended to delete user groups that will no longer be used if all users have been given access to multiple Base Commit BPs.

9. Create and import a configuration package to include multiple Base Commit BPs with the associated BP setups, shell templates, shells, SOV structures, and change commits.

   For more information, see Creating Configuration Packages.