Setting up a Base Commit Business Process

A Base Commit classification of a Cost Type Business Process (BP) can create a schedule of values; a General Spends classification can create an invoice at the CBS level.

Use the Base Commit BP for:

For monies committed to be spent; for example, a contract or purchase order.
For creating a Schedule of Values (SOV) sheet for a General Spends, Payment Applications, or Summary Payment Applications.

Note: In Standard Cost Manager, the Base Commit BP creates a Schedule of Values (SOV) sheet.

With the Base Commit type of BP, you can:

Reference against a company-level commit BP
Enforce the line items against a company-level commit amount
Create a commitment summary when the BP is in a terminal status
Consolidate line items

From this type of BP, you can:

Select only a General Spends type of commitment summary
View commitment summary line items only by individual line items, or grouped by commit codes

To set up the for a Base Commit BP:

Go to the project and switch to Admin mode.
In the left Navigator, click the Setup node.
In the left Navigator, click Business Process to open the Business Process Setup - Current View/log.
Select the business process that you want to set up and open.
In the Business Process Setup window, General tab, enter values.
Continue on with entering values in the Settings, Notifications, Auto Creation, and Record Copy tabs.
When finished, click Apply and OK.

Removing Restrictions Related to the Multiple Payment Application Submissions (Remove SOV restrictions)

When you create a Workflow BP record, the BP record shall remain in progress (in-flight) until the record reaches its terminal stage.

You can set up a Base Commit type of BP that is based on an existing Schedule of Value (SOV), and in progress (in-flight), to accommodate:

Multiple Payment Application records can be created for the same commit record.
Multiple Negative Change Orders can also be created for a given Base Commit.
Payment application when a negative change order is in-flight.
A negative change order refers to a Change Commit (change order) that has been issued to deduct the original committed contract amount. This means that a user has created a record of Change Commit BP type with negative line item amounts.

In the Business Process Setup window, General tab, you have the option of applying or removing restrictions on multiple payment applications or multiple negative Change Commit in the Base Commit BP. This enables users to create:

Create and submit a Payment Application when another Payment Application is in progress.
Create and submit a Payment Application when a Change Commit (change order), with a negative line item, is in progress.
Create and submit a Change Commit (change order), with a negative line item, when a Payment Application is in progress.
Create and submit a Change Commit (change order), with a negative line item, when another Change Commit (change order), with a negative line item, is in progress.

Create and submit a Payment Application when another Payment Application is in progress.
Create and submit a Payment Application when a Change Commit (change order), with a negative line item, is in progress.
Create and submit a Change Commit (change order), with a negative line item, when a Payment Application is in progress.
Create and submit a Change Commit (change order), with a negative line item, when another Change Commit (change order), with a negative line item, is in progress.
Note: The options listed above are available for Base commits of SOV type = Payment Applications or Summary Payment Applications.

Additional information about Removing SOV restrictions

Users can modify this option (Remove SOV restrictions) at any time except when all the Payment Applications and Negative Change Orders that refer to the BP have reached the terminal step.

When you select or deselect this option (Remove SOV restrictions) in an existing Workflow template that you plan to use for updating existing Workflow schema in the destination Project/Shell, then the selected SOV restriction option (existing in the BP setup level) will get updated in the Project/Shell instance.

When you select or deselect this option (Remove SOV restrictions) in an existing Workflow template that you plan to use to create new Workflow schema in the destination Project/Shell, then the selected SOV restriction option (existing in the BP setup level) will not get updated in the Project/Shell instance.

When you select or deselect this option (Remove SOV restrictions) in an existing Workflow template that you plan to use to create new Workflow schema in the destination Project/Shell, and if this new Workflow schema are used in the Auto Creation tab of the BP setup, then the selected SOV restriction option (existing in the BP setup level) will get updated in the Project/Shell instance.

When the SOV restriction option setup is ready and you include the BP in the Configuration Package, if there are any in progress (in-flight) records for the Payment Application, or Change Commit (change order), then the import will be successful but the system does not update the setup information for that BP.

If the user does not select the Remove SOV restrictions option, then:

Multiple payments cannot be created.
Multiple negative Change Commits cannot be created.
Positive Change Commit will not effect the in transit payment and Merge message will not be shown.

If the user selects the Remove SOV restrictions option, then:

Multiple payments can be created.
Multiple negative Change Commits can be created.
Merge message is shown only when another payment or Change Commit is created, while the first payment is in-flight.
Positive Change Commit impacts the SOV Sheet and not the multiple payments. In order to support multiple payments, merge needs to occur.

Last Published Monday, August 28, 2023