Algorithms Used in Deferred Revenue Recognition
The following table lists the algorithms which are used in the lifecycle of the business object:
Status | System Event | Algorithm | Algorithm Type | Description |
---|---|---|---|---|
C1-REVRECSCH | C1-REVRECSCH | This algorithm is invoked when the status of the bill segment
and adjustment financial transactions created against the contracts
(of the contract type to which the algorithm is attached) is set to
Frozen. It checks whether an active deferred revenue recognition template
exists for the distribution code and contract type combination. If
so, it creates a deferred revenue recognition using the template and
sets the status of the deferred revenue recognition to Draft. It then
checks whether the type of the corresponding financial transaction
is Bill Segment or Adjustment. If the type of the corresponding financial
transaction is Bill Segment, it sets the valid until date of the deferred
revenue recognition to the bill segment end date. However, if the
type of the corresponding financial transaction is Adjustment, it
checks whether the Use Contract Expiration Date (Y or N) parameter
is set to Y or N. If the Use Contract Expiration Date (Y or N) parameter
is set to Y, it sets the valid until date of the deferred revenue
recognition to the contract expiration date. However, if the Use Contract
Expiration Date (Y or N) parameter is set to N, it sets the valid
until date of the deferred revenue recognition to the financial transaction
arrears date. In addition, on creating the deferred revenue recognition,
an appropriate log entry is added which you can view in the Deferred
Revenue Recognition Log zone. It contains the following parameter:
|
||
C1-REVRECITM | C1-REVRECITM |
This algorithm creates schedule for the deferred revenue recognition. It considers the valid until date and accordingly creates the recognition lines within the schedule. If the recognition schedule is Weekly, by default, the recognition day is set to Mon (which means Monday of each week). However, if the recognition schedule is Monthly, by default, the recognition date is set to the last day of the month (i.e. 28, 29, 30, or 31) It contains the following parameters:
|
||
C1-REVRECADJ | C1-REVRECADJ |
This algorithm creates deferred revenue recognition adjustment using the adjustment type defined on the respective deferred revenue recognition template. Before creating the deferred revenue recognition adjustment, it checks whether the contract for which the deferred revenue recognition is created is cancelled. If so, the status of the deferred revenue recognition is set to Canceled. If all lines in the recognition schedule are recognized, the status of the deferred revenue recognition is set to Closed. |
||
C1-REVITMREC | C1-REVITMREC | If this algorithm is attached in the deferred revenue recognition
template, it is invoked while executing the C1-RRADJ batch. It contains
the following parameter:
|
||
C1-DRRTM-INF | C1-DRRTM-INF | This algorithm generates the deferred revenue recognition
template information string which appears throughout the application.
It concatenates the following fields separated by a comma in the specified
order:
|
||
C1-DRRTMPVAL | C1-DRRTMPVAL | This algorithm validates the deferred revenue recognition
template. It checks the following:
In addition, it does not allow you to:
|
||
C1-DRRSC-INF | C1-DRRSC-INF | This algorithm generates the deferred revenue recognition
information string which appears throughout the application. It concatenates
the following fields separated by a comma in the specified order:
|
||
C1-REVMON | C1-REVMON | This algorithm is invoked when the C1-DRRMO batch is executed. It checks whether there are any deferred revenue recognitions in the Draft status. If there is any deferred revenue recognition in the Draft status, it checks whether the recognition schedule generation type in the respective deferred revenue recognition template is set to Automatic or Manual. If the recognition schedule generation type is set to Automatic, the status of the deferred revenue recognition is changed to In Progress. However, if the recognition schedule generation type is set to Manual, the status of the deferred revenue recognition remains as Draft. | ||
C1-REVRECINP | C1-REVRECINP | This algorithm creates an appropriate log entry when the status of the deferred revenue recognition is changed to In Progress. It invokes the algorithm attached to the Create Deferred Revenue Recognition Schedule system event of the respective deferred revenue recognition template. Once the recognition schedule is successfully created, the status of the deferred revenue recognition is changed to Active. | ||
C1-REVRECACT | C1-REVRECACT | This algorithm transitions the current status to the specified
status. You can specify the status to which you want the business
object to transition in the following parameters:
At a time, you can specify value for either the Next Status or Next Transition Condition parameter. If you don’t specify any value for these parameters, the system will transition the business object to the default next status specified in its lifecycle. This algorithm creates an appropriate log entry when the status of the deferred revenue recognition is changed to Active. |