As mentioned, the Transport Form can be used to associate the technically-oriented transport request with the corresponding ticket or requirement to which it relates. Within ActiveControl, this ticket referred to as a Business Task.
Although it is optional, it is strongly recommended that all Transport Forms be associated with Business Tasks, as this:
- Groups together technically separate but functionally-related transport requests that collectively implement the changes necessary to add the business requirement or ticket.
- Allows for the progress and testing of the solution to a business issue or requirement throughout the system landscape to be monitored and reconciled as the solution makes its way through one or more development streams (such as in the case of branched development systems).
- Provides the business context for business users and team leaders involved in the change process (for example, from an approval perspective).
Similar to the Transport Form screen, the Business Task screen is a simple screen that can typically be completed in 10-15 seconds in either the SAPGUI or in the Web Platform, or indeed via an Integration with ITSM tools such as Jira or ServiceNow.
The Business Task screen consists of several standard subscreens, each containing various standard fields and other functionality.
It is possible to add custom fields to the Business Task via configuration. Custom tabs can also be defined if required, if there are a lot of custom fields and it is preferred to have them on seperate screens rather than on the default General subscreen where they will otherwise appear.
It is also possible to make most of the standard fields or custom fields optional or mandatory via configuration. Mandatory fields will show with a red asterisk *.
Figure: The ActiveControl Business Task screen in the Web Platform.