Error code - SOLAR_0018
The error is reported during SAP® synchronization. A conflict occurred while checking consistency rules.
Error message
Transaction <name of transaction> was skipped because the logical component that was assigned does not exist in your project.
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 .
You can create transactions/executables so that they can be started in SAP® Solution Manager. The modeling convention defines that every transaction/executable must be modeled exclusively in models of type Function allocation diagram (FAD) on an object of type Screen. The FAD must be assigned to an SAP function. The Transaction code attribute can be specified by one transaction code only. Entering multiple transaction codes is not allowed. Therefore, an object of the Screen type must be created for each transaction.
On the SAP® options > Solution Manager options page, you can enable the Open supporting dialog check box to specify that you want to be supported when creating new SAP functions, transactions, and documents. This ensures that the data is automatically specified consistently when created and can be synchronized between ARIS and SAP® Solution Manager.
If you have enabled the check box, you can specify transactions only via screens. The Transactions dialog enables you to manage transactions only if the call was started for an SAP function with an assigned function allocation diagram. If this is not the case, the specified functionality is not available. If the attribute is specified on other elements, the transaction is ignored.
If you disable the check box, transactions can still be specified on the Transaction code attribute of models and objects. These transactions cannot be started in SAP® Solution Manager and are not included in the SAP® synchronization.
Solution
Ensure that the points described under Causes are resolved.