Solution Documentation Assignment Block
The Solution Documentation
assignment block contains the elements that are assigned to the message, change transaction, business requirement, or IT requirement. It shows how the message, change transaction, business requirement, or IT requirement is integrated in the solution.
Features
You assign solution documentation elements to a transaction, using Single Element
or Multiple Elements
. Using Single Element
, you add an item to the Solution Documentation
assignment block, and with Multiple Elements
, you can add several items at once.
Note
In Change Request Management and quality gate management, these pushbuttons are active only if you have specified a change cycle in the transaction.
To update the assigned elements, choose Refresh
. You can update data in Solution Documentation and directly show these updates in the Solution Documentation
assignment block.
Depending on the transaction type, the Solution Documentation
assignment block provides the following features:
IT Service Management
You can add and remove solution documentation elements.
Requirements Management
You can add and remove solution documentation elements.
Requests for Change
You can add and remove solution documentation elements. However, you cannot change the solution documentation elements in the request for change.
Change Documents
If you create a change document directly, you can add and remove solution documentation elements in the Solution Documentation
assignment block.
If the change document is based on a request for change or IT requirement that already contains solution documentation elements, the elements are automatically assigned to the change document. You can maintain the solution documentation elements in the change document independently of those in the request for change or IT requirement. The solution documentation elements do not have to be scoped for you to make a change.
Note
In the Solution Documentation
assignment block, you can view only those change documents for which you are entered as a business partner and that do not have a “final” status.
When change documents are assigned to a branch for which Change Management Integration
is enabled, the solution documentation in the branch can be changed only using change documents.
When solution documentation elements are changed using a change document, the change is recorded. You can activate the change by setting a certain status for the change document. The default statuses are as follows:
Transaction Type | Status That Activates Solution Documentation Elements |
|---|---|
Administration change | Confirmed |
General change | Confirmed |
Urgent change | Imported into Production |
Normal change | Imported into Production |
Defect correction | Confirmed |
Once the change list has been activated, it is closed. If the change document has a status that is not “final”, a new SBOM is created that you can use to record and activate further changes.
If a change document is set to Withdrawn
, the changed solution documentation elements are not processed. You must reset the changed documents manually.
Caution
If solution documentation elements are assigned to multiple change documents, and one of the change documents is assigned a status that activates the changed solution documentation elements, the system does not issue a warning that the elements are also assigned to other change documents.