Auto-populate on Payment Application from a Base Commits BP

You can populate a classic Payment Application with line items from a Base Commit BP and Change Commit BP by using the method described in Auto-Populating Fields. You can also complete the mapping when you design a Base Commit BP. To do this, use the Options tab to map the fields when you launch the Base Commit BP.

Note:

If you select the Auto-populate on Payment Application option on the Options tab, the fields are available as columns in the SOV sheet. If any picker fields reference other sources, you cannot add those fields as columns.

You can use this feature only on:

  • SOV-type Payment Applications
  • SOV-type classic Payment Applications (Base Commits BP)
  • SOV line item-type individual commit line items

For the standard Payment Applications BP and associated Base Commit and Change Commit BPs, the Data Elements From Detail Form dialog box includes a Show in SOV option. Use this option to display additional columns in the SOV for text-based Data Elements (DEs). This gives users more information, which helps them distinguish between similar items and sort and filter results.

Note:

  • The DEs for which you select the Show in SOV option must also exist on the Standard tab of the Detail Form for the Payment Application. If you want a Change Commit to populate the DEs when it creates a Schedule of Values (SOV) line, the DEs must also be included in the Standard tab of the Detail Form of the Change Commit.
  • Because SOV values are populated after the Base Commit and Change Commit reach the defined terminal status, column values are not populated within the SOV for in-flight commitments. However, values can be populated within the SOV grid.
  • If the data source is present in both the SOV Line Picker Log and the Detail Form for the Change Commit, the value from the picker log is auto-populated from the Payment Application SOV to the Change Commit Detail Form and does not require auto-population configuration.
  • This feature only applies to the standard Payment Application BP and associated Base Comment and Change Commit BPs. It does not apply to General Spends BPs or the Summary Payment Application.

How Auto-Population Works

The Base Commit, Change Commit, and Payment Application BPs work as a set. The Payment Application reflects the Base Commit and Change Commit line items. When you design the Base Commit BP to auto-populate the Payment Application automatically, Unifier checks for Change Commit fields with the same names at runtime and includes those values on the Payment Application.

The runtime Payment Application Detail Form grid receives the auto-populated values from Base Commit source in both costed and summary lines.

You can configure the DEs in the Payment Application to receive auto-populated values from:

  • Base Commit BP
  • Schedule of Values (SOV)
  • Other sources, such as the Upper Form, Detail Form, Constant Value, Single Record BPs, and so on

If a DE on the Payment Application is configured to receive auto-populated values from the Base Commit BP and from other sources within the Payment Application, Unifier overrides the values from the Base Commit BP. This override applies to the auto-populated values in the costed and summary lines.

When a DE is set to auto-populate from a Base Commit, Change Commit, or SOV, the auto-populated values take precedence when a value of 0 is sent for those DEs in CSV, Microsoft Excel, or the REST API. Any value specified in the input request is ignored and the auto-populated values from the Base Commit, Change Commit, or SOV are used.

When the auto-populated values come from the Base Commit and populate the costed lines values, other columns may be generated in the Payment Application (PayApp) grid. The formulas for those columns are based on the auto-populated costed column.

Auto-populated values are completed despite any merge from the Change Commit SOV and new lines.

All DEs in the Summary Payment Application grid accept auto-population, and the costed rows receive auto-populated values from Base Commit source in all cases.

Note:

  • For auto-populating a Payment Application, the DE names must match.
  • If you configure specific DEs to auto-populate from a Base Commit BP, do not configure the same auto-population by using CSV, Excel, or the REST API in an SOV sheet for General Spends, Payment Applications, or Summary Payment Applications.

Caveats

  • If the Payment Application is auto-populated using both methods, the "usual" method will override this method.
  • You cannot auto-populate the following fields on a Payment Application:
    • amount
    • uuu_quantity
    • bitemid
    • any picker, except a date picker
    • short_desc
    • uuu_unit_price
    • any DE that is part of a dynamic data set on the Base Commit or Change Commit BP