The error is reported during SAP® synchronization. A conflict occurred while checking consistency rules.
Error message
Transaction <name of transaction> was skipped because no value is specified for attribute type SAP component.
Cause
Attributes that are appropriate for the transaction type must be specified for transactions (screens). The SAP component must be defined in your SAP® project (system landscape).
The attributes Transaction code and SAP component must be unique. For example, if you want to run the transaction VA02 and use different SAP® systems, you must assign the executing SAP® system.
Please ensure that the spelling is identical. In ARIS, the system landscape is located in the function allocation diagram assigned to the project node.
Non-URL transactions must be assigned to logical components (SAP component attribute type).
For transactions (screens) that are assigned to process steps, the SAP component attribute of the Screen object and of the process step must be identical.
If you create transactions using the wizard, all attributes are automatically specified correctly. If necessary, enable the Open supporting dialog and Run transactions with SAP® Solution Manager check boxes on the SAP® options > Solution Manager options page.
You may have transferred a project from SAP® Solution Manager in which you are using BPR items with incorrectly specified attributes.
Solution
Ensure that valid values are specified for the SAP component attribute type. If BPR items are incorrect, specify the logical component for the process step and transaction in SAP® Solution Manager.