Assigning Interface Attributes
In the Interface Attributes area, you can create assignments for the desired scenario by selecting attributes and corresponding field names.
In the Interface attributes table of the selected scenario, you can create new attributes or assign existing ones.
Use the value help to display a list of the interface attributes provided by the SolDoc Integrator. The associated field names correspond to the columns of the CSV file.
The following buttons are available in change mode:
Function | Description |
---|---|
![]() | Switch between display mode and change mode |
New Entries | Create new entries |
![]() | Copy interface attribute |
![]() | Delete interface attribute |
![]() | Undo Change |
![]() | Select All |
![]() | Select Block |
![]() | Deselect All |
Proceed as follows to assign interface attributes:
- Start transaction /N/SNP/SM_IICONF.
- The window Display View “Scenario”: Overview opens.
- In the Scenario table, select a scenario whose interface attributes you want to assign.
- In the Dialog structure area, double-click
Scenario >
Interface attributes.
- The window Display View “Interface Attributes: Overview opens.
- Click
Display -> Change to switch to change mode.
- Click New Entries to include a new mapping.
- The window New Entries: Overview of Added Entries opens.
- In the Field Name column, enter the corresponding assignment from the CSV file.
- Click
Save.
- The window Prompt for Customizing request opens.
- Click Own Requests.
- An overview of all created requests opens.
- Select the desired request.
- Click
Next.
- The request name and the request description are transferred to the prompt.
- Click
Next.
- An interface attribute with an associated field name has been created for the selected scenario.
The following attributes are necessary for a successful import:
- ID
- DESCRIPTION
- SENDER_CLIENT1
- RECEIVER_CLIENT1
- SENDER_SID1,2
- RECEIVER_SID1,2
- SENDER_SYSTEM_ROLE1,3
- RECEIVER_SYSTEM_ROLE1,3
1 This is not a mandatory attribute if the enhancement spot /SNP/SMII_LOG_COMP_GRP was implemented. For more information, see the Implementing a BAdI chapter.
2 This is only a mandatory attribute if no system role was maintained in the mapping.
3 This is only a mandatory attribute if no SID was maintained in the mapping.
The following attributes are supported in the SolDoc Integrator:
Interface attribute | Description |
---|---|
DELETE | Marks the interface as “to be deleted” |
DESCRIPTION | Title of the interface |
ID | Unique identification number of the interface |
MEMO | Description of the interface |
RECEIVER_CLIENT | Client of the receiving system |
RECEIVER_SID | SID of the receiving system |
RECEIVER_SYSTEM_ROLE | System role of the receiving system |
SENDER_CLIENT | Client of the sending system |
SENDER_SID | SID of the sending system |
SENDER_SYSTEM_ROLE | System role of the sending system |
TEAMMEMBERID | BP number of the creator HINWEIS If the field is empty, the person who performs the import process is used as the creator of the interface. |
TECHIFACETYPE | The technology type of the interface |
Finding Logical Component Groups
To successfully import the data into the solution documentation, you must specify the sending and receiving logical component groups of each interface.
If the mandatory attributes are not specified, the report runs successfully, but the interface is not created.
You can use the SolDoc Integrator to determine the logical component group in two different ways:
- By combining the client and SID of the interface
- By combining the client and system role of the interface
In the configuration of the interface attributes, at least one of the two combinations must therefore be present in the CSV file.
When creating the logical component group in the solution documentation, make sure that the logical component group can be found unmistakably within a branch using one of the above combinations.
If the logical component group cannot be identified, you must implement a BAdI to determine it. You can find further information in the Implementing a BAdl chapter.
If you cannot find or set a logical component group due to technical circumstances, we recommend creating a logical component that functions as a dummy.
This workaround makes it possible to map a system that is unknown in SAP Solution Manager. It is also possible to assign a logical component group, which ensures that the interface is imported into the solution documentation.