Additional Information About the SOV Line Picker Log

For use only within the Payment Application, the SOV Line Picker Log supports the inclusion of additional columns to be displayed within a Change Commit line item detail form when using the Commit Line Item Picker (uuu_sovlinum) to select the line of a Base Commit to be updated by a change.

Because the picker is selecting from the Payment Application SOV, the configuration is performed within the associated Payment Application BP. To configure the BP, you must create an SOV Line Picker Log within the Payment Application BP design. After you open the BP design, access Log from the left Navigator, select Picker, select New, and select SOV Line Picker Log, the system pre-populates the log with several system-defined data elements (DEs) that cannot be removed. The DEs include Item #, Ref., Cost Code Description, and Cost Code. Although they are not required for inclusion on the Detail Form for a Payment Application BP, the system also automatically includes Scheduled Value and Commit Remaining Balance. You cannot remove any of these columns, however, you can rename them using the Column Heading field, change the order in which they are listed, and update the width.

Notes:

When adding columns, any supported DEs present in the System section on the Detail Form for the Payment Application are available for selection. However, because only DEs that are configured in the Base Commit to use the Auto-populate on Payment Application option will contain values at run time, only these DEs are displayed.
If the DEs added to the commit line item picker log exist within the SOV structure or are one of the additional text columns that have been configured to display in the SOV, the source of the value displayed in the log will reflect the value within the SOV. However, if you add a column to the log that is not present in the SOV, the value displayed will reflect the value of the commitment line item that created the SOV line.
After the picker log is created and the design is deployed, you cannot delete the picker log.

See Also