In order to generate requests from the Recurring Service Program a program schedule need to be generated based on the Service Triggers and that at least one Service Scope exist.
The Requests can be generated using the Recurring Service Request Generation assistant which will run as a background job.
Calendar-based Recurring Service Request generation will generate Requests for a chosen date range or a selected schedule horizon (no of days in advance from the current date). The usage/condition-based Recurring Service Request generation picks 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. Also, the generation could be limited by specifying which recurring service program, service organization, customer, contract, recurring service package, model and service object on the recurring service program requests should be generated for recurring service programs that fulfill these criteria will generate requests.
Request generation can be set up to run as a schedule job.
This method of request generation can be run as often as required. Also, requests could be generated up to a future date (in calendar-based generation) as you wish. Longer planning time allows to analyze future resource requirements and plan with other service activities.
Requests can also be manually generated directly from the Recurring Service Program/Schedule tab by selecting the corresponding program occurrence and using Generate Request command.
When you run a recurring program with Floating Schedule = 'Yes', only one Request will be allowed to be generated at a time.
However, it is important to make sure the program schedule occurrences are up-to-date at the time of request generation. The Regenerate the Schedule flag in the recurring service program header would indicate if the schedule is required to be regenerated.
Requests will only be generated from programs in Active state and program occurrences in Generable state. Additionally 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.
When a request is generated, information on recurring service program is included in the generated request, such as description, service organization, customer, models, objects, service scopes and all its connections such as standard tasks, resource/material requirements etc. Additionally, Due Next of the respective 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-based program occurrences on which the Request was generated, the Request creation date will be considered the SLA Base Date to calculate SLA Latest Start/Finish dates for corresponding SLA Orders.