If the Remove SOV restrictions option is selected in the Business Process Setup window of the Base Commit (General tab), then multiple Payment Application type BPs and Negative Change Commits can be configured for a Project/Shell.
At the time of creating the Payment Application record, upon selecting the reference commit, the system will check for any existing negative change orders for the selected reference commit. Unifier displays a message if there any negative change orders.
After the record has been created, subsequently, when you open Payment Application record, the system checks to see if there are any pending payments, or negative change orders. If detected, Unifier displays a message.
Payment Grid which has negative line items
When you open the Payment Application grid, the line items which will be modified because of a pending Negative Change order will have an yellow alert in the Scheduled Value cell. You can click on the cell to view the details of the Change Order. The details include the BP name, BP record number, Line Number, and the Amount fields.
Line items from negative Change orders which are in draft status will not be seen in the Payment Application grid, but if a line item has been modified or removed from an existing record which is in draft status, the line item from negative change order can be seen in the Payment Application grid.
In case of Summary Payment Application, the alert will be seen in the Summary line, if the summary line item amount is negative. Similar alert will be seen if the costed line item is negative.
The sort order in the window begins by Business Process, then by Record Number, then by Line Number, and finally by Costed Line Number.
Creating negative change orders when the Payment Application is in progress (in-flight)
Example
First, the user creates the contract record CON-001 and sends the contact to a step that creates Schedule of Values.
Then, the user creates a Payment Application BP record PA-001 and sends the BP record to the next step for approval. At this point the BP record is in progress (in-flight).
Then, the user creates a Change Order (Change Commit) BP record to modify the committed line with a line item with a negative amount (a Negative Change Order CC-001) and sends it to the next step for approval.
The creation is successful.
Creating multiple negative change orders
Note: The following is applicable to Change Orders (Change Commits) that point to the Base Commit that does not have any SOV restrictions.
Example
First, the user creates the contract record CON-001 and sends the contact to a step that creates Schedule of Values.
Then, the user creates a Change Order (Change Commit) BP record to modify the committed line with a line item with negative amount (a Negative Change Order CC-001) and sends it to the next step for approval.
Then, the user creates another Negative Change Order for the same contract record CON-001.
The creation is successful.