How Contract Renewal Source Data Is Processed

You can renew eligible expired recurring promised detail lines by running the Create Contract Renew Source Data process.

The process:

• Scans the existing promised detail lines of your performance obligations to determine which lines have reached their plan end date.

• Determines renewal eligibility of the promised detail line and contract.

• Locates the latest source document header and line version for the eligible promised detail line.

• Creates new source document headers and lines by using the latest source document version line, and then updates the data to reflect the new plan period and amount or termination.

• Writes the new source document header and lines to the source document tables for further processing.

After the process is complete, submit the Validate Customer Contract Source Data and Identify Customer Contracts processes to process any newly received source documents.

Settings That Affect Contract Renewal Source Data

When you run the Create Contract Renewal Source Data process, the process considers only the promised detail lines of valid accounting contracts. Valid accounting contracts have the following settings:

• The allocation status is one of the following:

  • Allocated

  • Not Required

  • Exempted

• The freeze date is earlier than or the same as the system date.

For valid accounting contracts, recurring promised detail lines with the following conditions are eligible for renewal:

• Termination date is blank or later than the system date.

• Promised detail lines aren't tagged as discarded.

• Revenue has been fully recognized.

• Promised detail lines weren't already processed for renewal.

• Data Transformation Status is processed.

• Promised detail lines have no outstanding unprocessed return lines.

How Contract Renewal Source Data Is Processed

Using the original (parent) source document header and line of the recurring promised detail line as a basis, the process generates a new source document to reflect the new service period. The new source documents are copies of the latest version of the source document lines used to create the promised detail lines with the following modifications:

• The following columns in the SOURCE_DOCUMENTS table are updated as follows:

  Field	Value
  Document Date	Earliest plan start date
  Recurring Header Sequence Number	Incremented by one on each copy

• The following columns in the SOURCE_DOC_LINES table are updated as follows:

  Field	Value
  Document Date	Satisfaction plan end date plus one day
  Quantity	Recurring amount divided by the unit selling price
  Line Amount	Recurring Amount
  Satisfaction Plan Start Date	Satisfaction plan end date plus one day
  Satisfaction Plan End Date	Satisfaction plan end date is incremented by the recurring frequency and recurring pattern
  Version Number	1
  Version Indicator	N
  Contract Modification Date	Blank
  Revision Intent Type	Blank
  Add to Contract Indicator	Blank
  Add to Contract Action Code	Blank
  Recurring Line Sequence Number	Incremented by one on each copy
  Contract Group Number	If blank, the line document number is concatenated with the customer contract number. Otherwise, the original contract group number is used.
  Line Creation Date	System date

The Identify Customer Contract process processes the newly created recurring source document line using the original recurring source document line identification value, and bypasses the Contract Identification Rule logic. The contract is then assigned a freeze date equal to the document date plus one day, regardless of the freeze rule of the original contract identification rule.

When a contract is first renewed, if no contract group number is assigned to the original accounting contract, the Identify Customer Contract process assigns a contract group number to the contract. The system-generated contract group number consists of the document number concatenated with the contract number of the parent accounting contract. The same contract group number is used for subsequent renewals.