Update Descriptive Attributes without Invoking Contract Modifications

You can update descriptive attributes on revenue contracts without invoking contract modifications using the Revenue Basis Data Import template.

There's no impact on existing contracts or performance obligations when you revise the descriptive attributes that are used in setups such as contract identification rules and performance obligation rules. The application uses only the revised attributes if the existing contract is discarded and reprocessed.

When you use the descriptive attributes to derive account segment values, the application applies descriptive attribute revisions only from that point forward and not retrospectively. Any final accounted entries stay the same.

The template contains these record types:

Record Type	Description
U	Updates or deletes descriptive attributes that are stored in the extensible attributes for source document lines. Record Type U applies to these attributes on the VRM_SOURCE_DOC_LINES worksheet: Extensible Line Character Attribute 1 to 60 Extensible Line Number Attribute 1 to 20 Extensible Line Number Date 1 to 10
V	Updates or deletes descriptive attributes that are stored in the extensible attributes for source documents. Record Type V applies to these attributes on the VRM_SOURCE_DOCUMENTS worksheet: Extensible Header Character Attribute 1 to 60 Extensible Header Attribute Number Attribute 1 to 20 Extensible Header Number Date 1 to 10

To update or delete the descriptive attributes using the Revenue Basis Data Import file:

• Enter record type V to update the descriptive attributes in the VRM_SOURCE_DOCUMENTS worksheet. Provide the unique identifiers to identify the source document on which you are updating descriptive attributes.
• Enter record type U to update the descriptive attributes in the VRM_SOURCE_DOC_LINES worksheet. Provide the unique identifiers to identify the source document line on which you are updating descriptive attributes.
• Enter the value #NULL in the descriptive attribute to remove existing values from attributes.

The Validate Customer Contract Source Data process performs certain key validations for lines with record types U and V. The update record returns an error in these circumstances:

• The unique identifiers provided are invalid.
• The unique source document or unique source document line doesn't exist.
• The extensible attributes to be updated belong to a contract that was automatically renewed.

You must use the record types U and V to update the extensible attribute columns.

When you run the Validate Customer Contract Source Data process, it automatically generates the Validate Customer Contract Source Date Execution Report. The report:

• Displays the summary of the records that aren't updated due to validation errors.
• Lists the records that aren't updated along with the error messages.
• Uses the Revenue Basis Data Import file to correct the errors and import the revised lines for further processing.