Manually Generate Request
Explanation
Use this activity to manually generate a Request from a Recurring Service
Program. Go to the Schedule tab of the Recurring Service
Program, select the required program occurrence and use the Generate
Request command.
Users have the option to use the request grouping mechanism.
Request
grouping can be performed by selecting a grouping criterion from the Request
Generation dropdown in the Recurring Service Program header. The available grouping
options are as follows:
- Object Based: Requests are grouped based on the objects within the recurring
scope.
- Location Based: Requests are grouped based on the recurring scope's
location.
- Consolidated: All recurring scopes are consolidated into a single request,
with multiple scopes.
Depending on the selection, the system will group the generated requests
accordingly and if no grouping criteria is selected, the default grouping criteria
is Consolidated.
When you run a recurring program with Floating Schedule = 'Yes', only
one Request can be generated at a time.
Prerequisites
- Recurring Service Program should be valid and Active.
- Recurring Service Program Occurrences should contain at least one
Service Scope.
- Recurring Service Program Occurrences should be in Generable
state.
- If the Standard Task related to the Recurring Service Scope has planned
material lines which will generate Purchase Requisitions, the user generating
the Request must have access to the Logistics Site.
System Effects
- On the selected program occurrence, a Recurring Service Request 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.
- The Due Next of the respective calendar program occurrence
on which the Request was generated will be considered as the SLA
Start Date to calculate the SLA Commitment Due Date for SLA Commitment
Lines, unless a Triggering Entity and Event has been specified on the SLA
Template Line. For usage/condition-based program occurrences on which the
Request was generated, the Request creation date would be used.
- When there is a Request Contract connected to the recurring
service program, the Recurring Service Requests will be generated when the
contract is in Active or Planned state.
But the contract valid from date should not be a future date unless it is
specified to ignore contract valid from date when creating the recurring
service program.
For Recurring Scopes associated with a Contract Line, the SLA Template and
Pricing Rule on the Contract Line will be applied on Request scopes on the
generated Recurring Service Requests.
- If object-based or location-based grouping is selected, a single schedule
line will accommodate multiple requests. Conversely, if consolidated grouping
is selected, the system will create one request per program schedule. The
Request column within the schedule line will indicate multiple requests
by displaying an asterisk (*), and the selected request grouping criteria
will be displayed by the "Request Generation" label in the program
header.
- In cases of multiple requests within the schedule line, the completion
date of the last finalized request will be displayed in the "Request
Completed" field.