Solution Documentation Assignment Block

The Solution Documentation assignment block contains references to solution documentation elements that are assigned to the message, change transaction, business requirement, or IT requirement. Additionally for change documents, the changed solution documentation elements in the context of the present change document are displayed.

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; with Multiple Elements, you can add several items at once.

Note Note

In Change Request Management and Requirements Management, the pushbuttons to assign solution documentation elements are active depending on the status of the change transaction or IT requirement and whether the change transaction or IT requirement is in change mode. Customizing per transaction type controls the active status of the pushbuttons.

End of the note.

You can search for solution documentation elements that are added to the Solution Documentation assignment block.
Prerequisites

You have established the connection of the Embedded Search with TREX or SAP Hana by calling transaction SOLMAN_SETUP (SAP Solution Manager Configuration). Choose the Process Management scenario and go to Step 7 Configure Embedded Search.

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 references to solution documentation elements.

Requirements Management

You can add and remove references to solution documentation elements. When you create change documents in the context of IT requirements, the assigned references to solution documentation elements of the IT requirement are copied to the change document.

Requests for Change

You can add and remove references to solution documentation elements. When you create change documents in the context of a request for change, the assigned references to solution documentation elements of the request for change are copied to the change documents.

Change Documents

You can add and remove references to solution documentation elements. If you create the change document in the context of a request for change or an IT requirement, the referenced solution documentation elements from the request for change or IT requirement are copied into the change document upon creating the change document.

Note that also these “inherited” solution documents at the change documents can be removed. When a change document is assigned to a branch in which Change Control is activated, you can use change documents to record changes in solution documentation elements.

Preconditions for recording changes in a change document:

You must assign your business partner at any business partner function to the change document.
The change document must have a defined status. If references of solution documentation elements can be added, it is possible to use the document also for change recording. The changed solution documentation elements can be activated into the production branch with a defined change document status change.
The status values are displayed in the following table:

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

If Change Control is activated for a branch, solution documentation elements in this branch can only be changed using change documents.

On the Solution Documentation user interface, you can select only those change documents for which you are entered as a business partner and that do not have a “final” status. 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. For more details, see the table of default status values above.

If a change document is set to Withdrawn, the recorded changes of the solution documentation elements are not activated. You must reset the changed documents manually. Otherwise, you might have inconsistencies in the solution documentation between the maintenance branch (or development branch) and the production branch.

Caution Caution

If changes in solution documentation elements are recorded in several change documents, and the first of the change documents is assigned to a status that activates the changed solution documentation elements, the system does not issue the warning that the elements are also assigned to other change documents.

End of the caution.

More Information

Solution Documentation