Editing Additional SOV Column Values

Users with Edit Data permission on the SOV sheet can update the added columns, provided that the SOV is not locked by a pending transaction.

When the user saves an edited SOV value, the system displays a confirmation message that new line items in future Payment Application and Change Commit records use the updated values. Existing BP records do not update.

SOV data updates are captured in the SOV audit log.

Important Considerations

• Values populate into the SOV when the Base Commit or Change Commit reaches the configured terminal status. Existing in-flight commitments do not update automatically.
• Additional SOV columns apply to SOV lines. They do not apply to cost breakdown lines.
• After you create the SOV Line Picker Log and deploy the design, you cannot delete the picker log.
• Use the same DEs consistently across the Base Commit, Change Commit, and Payment Application detail forms to support end-to-end population.