Generate Request

Explanation

Use this activity to generate a Request using Recurring Service Request Generation assistant. The process will run as a background job.

Calendar-based Recurring Service Request Generation

Recurring Service Requests will be generated for a chosen date range or a selected schedule horizon. Schedule horizon is the no of days in advance from the current date, for which the recurring service requests will be generated.

However, request generation can be limited based on one or a combination of the following parameters.

Recurring Service Program
Service Organization
Customer
Contract
Recurring Service Package
Model
Service Object

Usage/Condition-based Recurring Service Request Generation

Recurring Service Request generation will pick up program schedule occurrences with a Recorded Value (latest measurement/ reading recorded) that has reached/passed the line Trigger Value for usage triggers (accumulate parameters) and Recorded Value that has met the condition limit or falls outside/inside the given range for condition triggers (limit parameters), and in status Generable to generate Requests. Request generation can be limited based on one or a combination of the following parameters.

Recurring Service Program
Service Organization
Customer
Contract
Recurring Service Package
Model
Service Object

It is possible to run only one generation type at a time.

Note: Request generation can be set up to run as a schedule job, using the database task Recurring Service Request Generation. User can set the parameters for which the database task should trigger. If both FROM_DATE_, TO_DATE and SCHEDULE_HORIZON_ values set, then priority will be given to the schedule horizon when calendar generation is triggered.

Prerequisites

Recurring Service Program should be valid and Active.
Recurring Service Program Occurrences should contain at least one Service Scope.
Calendar-based Recurring Service Program Occurrences should be in Generable state.
Usage/condition-based Recurring Service Program Occurrences should have a Recorded Value (latest measurement/ reading recorded) that has reached/passed the line Trigger Value for usage triggers (accumulate parameters) or Recorded Value that has met the condition limit or falls outside/inside the given range for condition triggers (limit parameters) and be in Generable state.
Recurring service package should be Valid and Active
Recurring service package occurrences should contain at least one Service

System Effects

As a result of this activity, Recurring Service Requests will be created in Released state and the origin (Source) of the Request will be set as 'Recurring Service Program'. It will then be available for further preparation along with other regular Requests.
Due Next of the respective calendar program occurrence on which the Request was generated will be considered as the SLA Base Date to calculate SLA Latest Start/Finish dates for corresponding SLA Orders. For usage/condition-based program occurrences on which the Request was generated, the Request creation date would be considered the SLA Base Date to calculate SLA Latest Start/Finish dates for corresponding SLA Orders.
When there is a Request Contract connected to the recurring service program, the Recurring Service Requests will only be generated when the contract is in Active state. For Recurring Scopes associated with a Contract Line, the Request SLA Template and Pricing Rule on the Contract Line will be applied on Request scopes on the generated Recurring Service Requests.
For Combined recurring programs, program occurrence can be a candidate for both calendar-based generation and usage/condition-based generation at the same time. However, the Request will be created depending on which generation method picks the program occurrence.

Note: Requests will be generated for Service Organizations where the logged in user is connected via the Service User Group.