Errorcode: SOLAR_0001 Short description: The 'SYNCHELEMENT' item was skipped because an object definition with the 'SAP

ID' attribute exists more than once. Occurrence: The element which is about to be synchronized is checked against the consistencyrules. Cause: Projectelements in Solution Manager are identified in ARIS by the unique attribute SAP ID. While you cannot create duplicate SAP IDs in Solution Manager you can do so in ARIS by creating a definition copy. But having more than one item with the same SAP ID it is no longer possible to identify the one that has to be used by the synchronization. Therefore in ARIS it is not allowed to use definition copies of previous synchronized elements. Solution: You can delete the definition copy and create a new element using the function assistant or delete the attribute SAP ID (note that if you have an assigned model you have delete the SAP ID from the model attributes too). You also may wish to use shortcuts or shadows (occurrence copies ignored during the synchronization) instead of the definition copy.

Errorcode: SOLAR_0002 Short description: The 'SYNCHELEMENT' item was skipped because more than one object occurence to the identical 'SAP ID' attribute exists within the SAP project model. Occurrence: The element which is about to be synchronized is checked against the consistencyrules. Cause: Projectelements in Solution Manager are identified in ARIS by the unique attribute SAP ID. While you cannot create duplicate SAP IDs in Solution Manager you can do so in ARIS by creating more than one occurrence copies (having a synchrelevant symbol) in the synchronization model. But having more than one item with the same SAP ID it is no longer possible to identify the one that has to be used by the synchronization. Therefore in ARIS it is not allowed to use occurence copies with a synchronization relevant symbol of synchronizational elements. Solution: You can delete one occurence copy and create a new element using the function assistant to create a new element in Solution Manager. You also may wish to use shortcuts or shadows (occurrence copies ignored during the synchronization) by assigning the appropriate symbol instead of the definition copy.

Errorcode: SOLAR_0003 Short description: The 'SYNCHELEMENT' item was skipped because its SAP function type does not match its parent. Occurrence: The element which is about to be synchronized is checked against the consistencyrules. Cause: The structural hierarchy of the Solution Manager items is mapped in ARIS to project containing scenarios containing processes containing process steps using the attribute SAP function type and SAP model type. The assigned synchronization model to a function must have always the same SAP type. The SAP type of the functions used in the model must be of the containing type, because the structural order in ARIS must be the same as in Solution Manager. Solution: Change the SAP type of function depending on the SAP type of the model the function should belong to (Model type project requires function type scenario, model type scenario requires function type process, model type process requires function type process step). If the function type of your item is correct you have to place it in a model on the right level accordingly.

Errorcode: SOLAR_0004 Short description: The 'SYNCHELEMENT' item was skipped because its SAP component is not maintained. Occurrence: The process step which is about to be synchronized is checked against the consistencyrules. Cause: Process steps need in SAP Solution Manager a logical component assigned. The logical component is in ARIS maintained in the attribute SAP component and must match a component maintained in the system landscape of your project. This attribute is not maintained. Solution: Maintain the SAP component with one of the logical components you find in the system landscape. Note that the name must match one of the components in the system landscape exactly. In ARIS you find the system landscape in the FAD assigned to the project node. You can also use the function assistant to create new steps which let you choose the component via the ARIS GUI.

Errorcode: SOLAR_0005

Short description: The 'SYNCHELEMENT' item was skipped because the component that was assigned is not contained in the project. Occurrence: The process step which is about to be synchronized is checked against the consistencyrules. Cause: Process steps need in SAP Solution Manager a logical component assigned. The logical component is in ARIS maintained in the attribute SAP component and must match a component maintained in the system landscape of your project. This attribute is maintained with a value which does not match any logical component of your project. Solution: Maintain the SAP component with one of the logical components you find in the system landscape. Note that the name must match one of the components in the system landscape exactly. In ARIS you find the system landscape in the FAD assigned to the project node. You can also use the function assistant to create new steps which let you choose the component via the ARIS GUI.

Errorcode: SOLAR_0006

Short description: The item 'SYNCHELEMENT' was skipped because the link target does not exist in SAP Solution Manager or belongs not to the same project. Only shortcuts with valid link targets in the same project can be transferred to ARIS. Occurrence: (A) During a projectdownload or synchronization towards ARIS the shortcut is checked for consistency. (B) During a synchronization towards Solution Manager a shortcut should be created but the definition didnt exist. Cause: In SAP Solution Manager you can delete the definition of a shortcut without the implicit deleting of the shortcut. In ARIS it is not possible to have a shortcut or occurrence without having a definition. Another occurrence of this error is that while you can create a shortcut in SAP Solution Manager between different projects you cant do so in ARIS. The reason is that the synchronization can guarantee for the project that is about to be synchronized that the definition of the shortcut is available but not for other projects. Since you cannot create a shortcut without a definition such shortcuts are ignored by the synchronization. Solution: (A) None. if you could live without external shortcuts you should remove them from your project. (B) If the definition is also a new item synch from a common root node so that the definition is created first before the shortcut will be created. Otherwise you should delete the obsolete shortcut in ARIS.

Errorcode: SOLAR_0007 Short description: The shortcut 'SYNCHELEMENT' was skipped because the definition does not exist in ARIS. Make sure that the definition the shortcut is linked to is part of the synchronization. Occurrence: (A) During a synchronization towards Solution Manager the shortcut is checked for consistency. (B) During a synchronization towards ARIS the shortcut is checked for consistency. Cause: (A) Inside the synchronization project exists a shortcut occurrence but no occurrence with the defintion symbol. Since you cannot create a shortcut without definition you need to have a definition first from which the shortcut can be created in Solution Manager. In contrast to SAP it is in ARIS not possible to have a shortcut without its definition. (B) The definition was not created in ARIS. This can happen by synchronizing a part of your project where the definition does not belong to. You can also check the shortcut in Solution Manager to check if the link target is valid. Solution: (A) If you have deleted your definition occurrence you have to delete all shortcut occurrences too. If you accidently have chosen the shortcut symbol you can switch it to the definition (if it is new) or shadow symbol (if it shall be ignored). (B) If the link target is valid start the synchronization from a common root node including definition and shortcut. Otherwise you should delete the inconsistent shortcut.

Errorcode: SOLAR_0008 Short description: The shortcut 'SYNCHELEMENT' was skipped because more than one definition with the same target sapid does exist in ARIS. Occurrence: During a synchronization towards ARIS the shortcut is checked for consistency. Cause: A shortcut has exactly one definition. If a shortcut is created in ARIS an occurrence to an object definition has to be made which is looked up by the SAP ID. If there is more than one object to the SAP ID the shortcut cannot be created because it would have more than one defintition. Solution: Delete all object definitions except the one you would like to use in the synchronization. You can find the duplicate object defintions by searching for the SAP ID using the ARIS search functionality.

ErrorCode SOLAR_0009 Short description: Error while download project as test project. Scenarios used in test projects must not contain any processes. Occurrence: During a download from a project as test project. Cause: 1. You try to download a project as test project which has processes and/or process steps. A test project mustnt have any processes. The reason is that for the test project only processes and process steps from a not test project can be used for the test. Processes or process steps which would be created in SOLAR cannot be used in ARIS for the end to end tests. 2. If the project consists of processes and/or process steps which would be upload from ARIS to SOLAR the project cannot be used for a second Download as test project. The reason is that the information from which objects the elements would be copied cannot be restored in ARIS. Here the user should work with database which would be used by the first download.

Solution: 1. Choose another project which mustnt have any processes and starts the download again. 2. Delete all processes from all scenarios of the test project and starts the download again.

ErrorCode SOLAR_0010 Short description: The item '%1' was skipped because the attribute 'Test Source ID' is not maintained. Occurrence: During the upload of the test scenarios. Cause: In ARIS the test project contains processes or process steps where the attribute Test Source ID is not maintained. This can happen if the object wouldnt created by the Paste as test object function or the object would be created by yourself. The attribute Test Source ID must be filled with the SAP ID of the object which should be copied in the Solution Manager. Solution: 1. Use the function Paste as test object to copy objects from the normal project to the test project. 2. Maintain the attribute Test Source ID with the SAP ID of the object from the normal project which sould be copied.

ErrorCode SOLAR_0011 Short description: The item '%1' was skipped because the attribute 'Synchronization project' is invalid for the test project or the current project is not a test project. Occurrence: During the upload of the test scenarios. Cause: 1. There exist at least one element in the test project which would not be created with the Paste as test object function. Instead the function Paste as -> Definition copy or the function Paste as -> Occurrence copy would be used. 2. You start the Upload test scenarios function on a scenario of a normal project. Solution: 1. Delete the wrong object and copy it with the Paste as test object function. 2. Do not start the Upload test scenarios function in a normal project.

ErrorCode SOLAR_0012 Short description: The item '%1' was skipped because the source node to the attribute 'Test source id' could not be found on SAP Solution Manager. wurde bersprungen, Occurrence: During the upload of test scenarios Cause: 1. You filled the attribute Test Source ID with a SAP ID which does not exist in the Solution Manager 2. The object to the SAP ID in Test Source ID does not exist any longer in the Solution Manager. For example the to copied object would be deleted by the synchronization or by another user in the Solution Manager. Solution: 1. Fill the attribute Test Source ID with the SAP ID of the to copied object. 2. Delete the object where the Test Source ID is invalid.

ErrorCode SOLAR_0013 Short description: The synchronization cannot be used on projects which will be used as test projects. Occurrence: During the upload of test scenarios Cause: You tried to use the Upload test scenarios function on a not test project. This function cannot be used by normal projects Solution: Use the Upload test scenarios function by the test project.

ErrorCode SOLAR_0014 Short description: Item 'SYNCHELEMENT' could not be created because it's parent has not been checked out. Occurrence: During the synchronization with the solution part of a maintenance project a new item item is found in ARIS and is about to be created but the parent item wasnt checked out in SAP Solution Manager. Cause: Before you can add new items to a solution via a maintenance project you have to check out the parent node from the solution. You cannot add new items to not checked out items in SAP so you are not allowed to do so with the synchronization. This can also happen if you create to a checked out scenario a new process with steps. The process is added in SAP but the step cannot, because the newly added process is not checked out in SAP. Solution: If you want to maintain your solution you have to allways check out the complete scenario where your changes are about to be made. If you want to add a new process containing steps, you have to add the process first, than have a checkin to make the process part of the solution before you have to checkout the scenarion again to add the step to the process. This restriction comes from the Solution Manager. If you want to add new scenarios, which is not possible when you are said to checkout on scenario level, you should consider that for adding whole scenarios a maintenance project is not the appropriate approach. You should then use an implementation project.

ErrorCode SOLAR_0015 Short description: The Role 'new role' was skipped because it is allready assigned to it's item. The same role cannot be assigned to one item multiply. Occurrence: You are synchronizing to Solution Manager and have added a new role to an item in ARIS which is about to be created in SAP. Cause: Since the SAP Solution Manager does not allow you to add the same role to an item more than once, the ARIS synchronization mustnt either. Solution: Delete the duplicate role occurrence from the FAD of the belonging item.

ErrorCode SOLAR_0016 Short description: The role 'role' is not available in your project. Occurrence: You are synchronizing to Solution Manager and have added a new role to an item in ARIS which is about to be created in SAP. Cause: The role you have assigned to the item does not exist anymore in SAP Solution Manager. This can happen when you have synchronized the pool roles to ARIS (see group roles under projectgroup) and have afterwards deleted a role in SAP. Even if you have synchronized the poolroles the definition is still remaining in ARIS and could have been used. Solution: Delete the definition manually from ARIS. If you use the reorg functionality from ARIS you should be careful, because dependend on the amount of roles not all roles may be occed into the poolrole models, but you can recreate them by synchronizing the pool roles towards ARIS. If you have reused the deleted role in other ARIS models and want to keep it, delete the occurrence from the synchronized FAD and move the definition from the role group to the place where it is used.

ErrorCode SOLAR_0017 Short description: The keyword 'new keyword' is not available in your project. Occurrence: You have added a keyword to the attribute Keywords and the keyword is tried to be added to the item in SAP Solution Manager. Cause: The added keyword does not exist or is not assigned to your project. You find the available keywords in SAP Solution Manager in the project administration under Project Standards in the Keywords tab. Note that you have to use the entry under Keyword and not under Name even if in your project you only see the Name. The reason is that the Keyword can be used as a unique identifier while you can have multiple keywords with the same Name. Note also that the keywords must be separated by semicolon. Solution: Check if the 'new keyword' is allowed in your project and correct the spelling or assign the keyword to your project.

ErrorCode SOLAR_0018 Short description: The 'tcode' transaction was skipped because the component that was assigned is not contained in the project. Occurrence: The transaction is checked against the consistency rules. Cause: Non URL transactions need in SAP Solution Manager a logical component assigned. The logical component is in ARIS maintained in the attribute SAP component and must match a component maintained in the system landscape of your project. This attribute is maintained with a value which does not match any logical component of your project. Solution: Maintain the SAP component with one of the logical components you find in the system landscape. Note that the name must match one of the components in the system landscape exactly. In ARIS you find the system landscape in the FAD assigned to the project node. Note also that transaction which are assigned to steps must match a logical component belonging to the product of the logical component of the step. You can also use the function assistant to create new transactions which let you choose the component via the ARIS GUI consistently.

ErrorCode SOLAR_0019 Short description: The 'tcode' transaction was skipped because its SAP component is not maintained. Occurrence: The transaction is checked against the consistency rules. Cause: Non URL transactions need in SAP Solution Manager a logical component assigned. The logical component is in ARIS maintained in the attribute SAP component and must match a component maintained in the system landscape of your project. This attribute is not maintained. In rare cases it could happen that you get this error when you synch BPR content with a project toward ARIS. Solution: Maintain the SAP component with one of the logical components you find in the system landscape. Note that the name must match one of the components in the system landscape exactly. In ARIS you find the system landscape in the FAD assigned to the project node. Note also that transaction which are assigned to steps must match a logical component belonging to the product of the logical component of the step. You can also use the function assistant to create new transactions which let you choose the component via the ARIS GUI consistently. If the error comes from Solution Manager check the parent, if it is a step, and the transaction for the logical component and maintain it.

ErrorCode SOLAR_0020 Short description: The 'tcode' transaction was skipped because its SAP component is not compatible with the SAP component of the assigned process step. Occurrence: The transaction is checked against the consistency rules. Cause: Non URL transactions to steps need in SAP Solution Manager a logical component assigned that matches the product of the logical component of the step. The logical component is in ARIS maintained in the attribute SAP component and is maintained with a value that does not belong to the step. Solution: Maintain the SAP component with one of the logical components you find in the system landscape. Note that the name must match one of the components in the system landscape exactly. In ARIS you find the system landscape in the FAD assigned to the project node. Note also that transaction which are assigned to steps must match a logical component belonging to the product of the logical component of the step. If you are not sure which component to use you can look in the Solution Manager and add temporary a transaction to the step to check which logical components are allowed there. You can also use the function assistant to create new transactions which let you choose the component via the ARIS GUI consistently.

ErrorCode SOLAR_0021 Short description: Error running synchronization.\nThe current method filter does not comply with the mySAP synchronization requirements. Please use the entire method or the ARIS for SAP NetWeaver filter. Alternatively an info about what is missing in the used filter is displayed. Occurrence: Before the synchronization starts the current configuration is checked against the filter. If you have no user defined configuration the default configuration is checked. Cause: Your filter does not allow all needed items for the synchronization. You are not allowed to use an incomplete filter because this may yield to unexpected behaviour. Imagine you have removed accidently the used function symbol for scenarios from your filter and synch towards Solution Manager with delete options active. The synchronization would delete your whole project because all scenarios are filtered. Note also that only the current configuration is checked against the filter. If you have changed your configuration during the synchronization process you have to ensure that the previous items of the old configuration are also part of the filter for the same reason. If you do not use the user defined configuration but the modeltypes as with 7.02 you may also get the effect, that, if you have choosen a userdefined model which is not allowed in the current filter you dont see the user defined name of the model, but the name of the base model only. The reason is that the user defined model does not exists on the server where the synchronization should be run. Solution: If you use no user defined items in the configuration you can use the ARIS for SAP NetWeaver filter, which contains all possible items needed by the synchronization. If you want to use a customized filter you can use the summary from the method wizard as template for the filter and if you have forgotten something use the info from the errormessage to add the missing part. If you dont use the method configuration and have user defined models you should check if you are on the right server where the user defined models exists. Besides you should change the modeltype to an existing one.

ErrorCode SOLAR_0022 Short description: You need additional privileges in the SAP system for this project. Please contact your system administrator. Occurrence: Immediatly before the synchronization starts the project in Solution Manager is checked if the user used for synchronization has the needed privileges. Cause: You are synching towards solar but you dont have change permission on the project or you are synching towards ARIS and have no display permission. Solution: Check the change permission in the Project Administration in the scope tab for your project. You can (un)lock your project against changes on that tab. The display permission is related to the SAP user profile. You should ask your SAP administrator if you have your project unlocked but get this error to check your user for the needed privileges.

ErrorCode SOLAR_0023 Short description: Unable to start synchronization on the function. Please make sure that the function either has a valid SAP ID and belongs to the selected project. Occurrence: Before the synchronization starts it is checked if the function where you did start the synchronization belongs to a project existing in SAP Solution Manager.. Cause: The function in ARIS has the attributes SAP ID or SAP function type not maintained, but they are required for the check. You cannot start the synchronization on items that do not exist in ARIS and SAP Solution Manager. If they are maintained you may have chosen a different project in the synchwizard. Solution: Start the synchronization always on an existing item. You can always use the project root node as start node. The synch wizard usually shows you the correct project to the selected startnode, so you should not change the project there and if you dont want to synch against the displayed project you may have chosen the wrong startnode.

ErrorCode SOLAR_0024 Short description: The element you are trying to synchronize was downloaded without using an user defined configuration. Do you want to use the current configuration ? Occurrence: The current configuration is compared to the one used for the last synchronization and differences are detected. Cause: You have downloaded a project from SAP Solution Manager without using a method configuration or using a project created with an ARIS version previous to 7.1. You currently have a method configuration selected and tried to synchronize a project without configuration with the selected configuration. You get this information because it is dangerous to change the configuration during your synchronization work. You must ensure that your filter matches not only your current configuration but also your previous configuration. If you e.g. change the functionsymbol from one userdefined symbol to the other and allow in the filter only the new one all previously synched functions are filtered which will cause dataloss if you synch to Solution Manager with delete options on. You should also be aware of the fact the changing a configuration does not update previous synched items. This means if you have already items of the type you have changed, they will remain and you will have a composition of different types in your project. If you change the object types for roles this can cause errors depending on the used filter. Since roles are reused from the pool the reused object type may not match the symbol and connection type configured. In that cases the synchronization tries to use the default symbol for the object but it must be available in the filter. Solution: To avoid any problems it is strictly recommended that you do not change your configuration. The configuration change is harmless if only items are affected that did not yet exist in your project. Click the No button if you want to synchronize with the previous configuration (recommended).

If you click the Yes button the current configuration is used for the synchronization and overwrites the previous configuration. You can then synch without getting this information until you again change your configuration. ErrorCode SOLAR_0025 Short description: The synchronization was previously done using a different method configuration. Synchronizing with different method configurations may lead to unpredictable results.The following elements have been changed: Occurrence: The current configuration is compared to the previous one and differences are detected. Cause: You have downloaded or synchronized a project from SAP Solution Manager using a configuration. You then have a selected another configuration or changed the used one. You get this information because it is dangerous to change the configuration during your synchronization work. You must ensure that your filter matches not only your current configuration but also your previous configuration. If you e.g. change the functionsymbol from one userdefined symbol to the other and allow in the filter only the new one all previously synched functions are filtered which will cause dataloss if you synch to Solution Manager with delete options on. You should also be aware of the fact the changing a configuration does not update previous synched items. This means if you have already items of the type you have changed, they will remain and you will have a composition of different types in your project. If you change the object types for roles this can cause errors depending on the used filter. Since roles are reused from the pool the reused object type may not match the symbol and connection type configured. In that cases the synchronization tries to use the default symbol for the object but it must be available in the filter. Solution:

To avoid any problems it is strictly recommended that you do not change your configuration. The configuration change is harmless if only items are affected that did not yet exist in your project. Click the No button if you want to synchronize with the previous configuration (recommended). If you click the Yes button the current configuration is used for the synchronization and overwrites the previous configuration. You can then synch without getting this information until you again change your configuration. ErrorCode SOLAR_0026 Short description: The project you are trying to synchronize was downloaded with a user-defined configuration. By synchronizing with the option "Use configuration" disabled the following changements will be taken into account: Occurrence: The current configuration is compared to the previous one and differences are detected. Cause: You have downloaded or synchronized a project from SAP Solution Manager using a configuration. You then have a deselected the usage of configurations and want to synchronize with the default settings. You get this information because it is dangerous to change the configuration during your synchronization work. You must ensure that your filter matches not only your current configuration but also your previous configuration. If you e.g. change the functionsymbol from one userdefined symbol to the other and allow in the filter only the new one all previously synched functions are filtered which will cause dataloss if you synch to Solution Manager with delete options on. You should also be aware of the fact the changing a configuration does not update previous synched items. This means if you have already items of the type you have changed, they will remain and you will have a composition of different types in your project. If you change the object types for roles this can cause errors depending on the used filter. Since roles are reused from the pool the reused object type

may not match the symbol and connection type configured. In that cases the synchronization tries to use the default symbol for the object but it must be available in the filter. Solution: To avoid any problems it is strictly recommended that you do not change your configuration. The configuration change is harmless if only items are affected that did not yet exist in your project. Click the No button if you want to synchronize with the previous configuration (recommended). If you click the Yes button the current configuration is used for the synchronization and overwrites the previous configuration. You can then synch without getting this information until you again change your configuration. ErrorCode SOLAR_0027 Short description: The symbol you have configured is not compatible to the existing modeltype and the default symbol for this model is not allowed in your filter. Please check your configuration. Occurrence: A new item is about to be created in ARIS. The method configuration is checked against the already existing parent item. Cause: You have configured for new items symbols which are not allowed in the already existing models. E.g. you have previously synched with VAD models and have switched them to EPC models. For EPC models you can only use different function symbols as for VAD models. If you now transfer a new item to ARIS you cannot create an EPC symbol in a VAD model. The synchronization would try to use the default symbol but this is not allowed in the filter. Solution: If you have already existing items (in this case models) you must ensure that all needed items are allowed int the filter. Here you have to add the SAP function symbol for the already existing model to the filter.

ErrorCode SOLAR_0028 Short description: The 'SYNCHELEMENT' item was skipped because an object definition with the same 'SAP ID' attribute already exists. Occurrence: The element is about to be created in ARIS and checked against the consistencyrules. Cause: Projectelements in Solution Manager are identified in ARIS by the unique attribute SAP ID. While you cannot create duplicate SAP IDs in Solution Manager you can do so in ARIS by duplicating the attribute SAP ID into another definition. But by having more than one item with the same SAP ID it is no longer possible to identify the one that has to be used by the synchronization. Here exists somewhere in the database a definition with a SAP ID belonging to the item which is about to be created. A new item cannot be created for the above reason and the item is not reused because it is not clear if its current use is compatible with the use in the synchronization models. You may also receive this error if you accidently removed already existing function symbols from your filter. Solution: If the existing defintion can be reused in the synchronization just create an occurrence in the right model. You can find it by using the ARIS search for the attribute SAP ID. If not just delete the attribute SAP ID from the existing definition.

ErrorCode SOLAR_0029 Short description: The 'tcode' transaction was skipped because this transaction code already exists in the selected component. Occurrence: The transaction is about to be synchronized and is checked against the consistencyrules. Cause: In the FAD you have assigned a transaction occurrence having the same values for transaction type, logical component and transaction code. Since you are not allowed to add the same transaction twice in the SAP Solution Manager you are not allowed to do so in ARIS. Note that you are allowed to add the same transaction in different logical components. Solution: If the transaction is added twice accidently you just have to delete it. Otherwise you have to correct the transaction type, transaction code or logical component of the transaction to the right value.

ErrorCode SOLAR_0030 Short description: The processmodel assigned to the 'SYNCHELEMENT' item was skipped because the SAP model type does not match the SAP function type. Occurrence: The element is about to be synchronized and is checked against the consistencyrules. Cause: Since it is in ARIS possible to assign more than one model of the same type to an ARIS function you have to tag the one you want use for the synchronization. You do so by giving the linked model a SAP model type which must match the SAP function type of the function the model is linked to. If you receive this error the model type does not match the one of the function. The following rules exist: SAP function type Project Scenario Process Assigned SAP model type Project Scenario Process Contains SAP function type Scenario Process Process step

Solution: Just change the SAP modeltype according to the above table to the one of the function the model is assigned to.

ErrorCode SOLAR_0031 Short description: The 'SYNCHELEMENT' item has more than one assigned model with the same 'SAP model type' attribute. Occurrence: The element is about to be synchronized and is checked against the consistencyrules. Cause: Since it is in ARIS possible to assign more than one model of the same type to an ARIS function you have to tag the one you want use for the synchronization. You do so by giving the linked model a SAP model type which must match the SAP function type of the function the model is linked to. If you receive this error you have done so for more than model. Solution: Check the models you have assigned to the 'SYNCHELEMENT' and delete the SAP model type attribute from the one you assigned accidently if it is not used elsewhere in your hierarchy. In that case just remove the assignment.

ErrorCode SOLAR_0032

Short description: The EPC assigned to the 'SYNCHELEMENT' item was skipped because the SAP ID of the model is not identical with the one of the 'SYNCHELEMENT' item. Occurrence: The element is about to be synchronized and checked against the consistencyrules. Cause: Since it is in ARIS possible to assign more than one model of the same type to an ARIS function you have to tag the one you want use for the synchronization. You do so by giving the linked model a SAP model type which must match the SAP function type of the function the model is linked to. If you synchronize for the first time the synchronization also writes the SAP Id of the 'SYNCHELEMENT' to the assigned model. If you receive this error you have assigned an already synched model to a function to which the model do not belong. Solution: If you have assigned the model accidentlly just delete the assignment to the exisiting model and create a new one. If you want to keep the model you can maintain the SAP Id attribute with the value from the corresponding function which the model is linked to or you can just delete the SAP Id and let the synchronization fill the attribute with the right value for you.

ErrorCode SOLAR_0033 Short description: The 'SYNCHELEMENT' item was skipped because no item exists in SAP Solution Manager that corresponds to its SAP ID. Occurrence: The element is about to be synchronized to SAP Solution Manager and is checked against the consistencyrules. Cause: You have in ARIS an item with a maintained SAP Id which does no exist in the Solution Manager. An item receives the SAP id through the synchronization as an identifier to match the ARIS SAP function to the corresponding SAP item. Since the SAP item does not exist any longer in the Solution Manager project the ARIS object is obsolet and can also not be used any longer. Solution: If the ARIS object is left over accidentally just delete the occurrence manually or let the synchronization do that by synchronizing from Solution Manager to ARIS with the option delete structural items activated. If you have accidentally deleted the item from your SAP project you have to delete the SAP Id from the ARIS object manually. The item will then be treated as a new object and will receive a new SAP Id belonging to the created one in SAP. Note that you also have to delete the SAP Id from its assigned model if it has one.

ErrorCode SOLAR_0034 Short description: Element 'SYNCHELEMENT' was skipped either because its context does not match the selected project, or because the element has a function type that differs from that in the BP repository. Occurrence: You have tried to synchronize a BPR element into the SAP Solution Manager which is not compatible with your project. Cause: Usually there are two reasons for this error. You took an item from a BPR belonging to your project but you decided to change its SAP function type and use it as a process instead of a step or vice versa. Since a BPR item has a fixed SAP function type this is not possible. You took an item from a BPR which does not belong to your project. Since BPR items are related to the context (a set of conflictfree logical components of the systemlandscape of the project the BPR belongs to) a logical component is required for the BPR item that is missing in your current project. Imagine you have downloaded a BPR from a project containing SAP ECC only and use it in a project not containg a SAP ECC. If you really want to use the item you have to add ECC to your system landscape. Solution: If you have changed the function type you cannot use the item but must create a non BPR item instead. If you took a BPR item from a different project you have to add the missing components to your system landscape in SAP Solution Manager. Otherwise you should replace the BPR item with a newly created one. In general it is the best approach to download always a BPR which belongs exactly to your project, because then each item can be used for the upload. Note that you can check an item if it matches your project with the functionallity proof context available on function objects. These functionallity will tell you also what components are missing.

ErrorCode SOLAR_0035 Short description: Unable to transfer element 'SYNCHELEMENT' because it does not exist in the BP Occurrence: You synchronized towards SAP and tried to upload an item from Business Process Repository but it couldnt be uploaded in your project Cause: The item does not exist for this SAP function type in the repository. This can happen if you change manually the SAP function type of a BPR item from process to process step or vice versa which is not allowed or if the ICO release in your SAP system differs from the one you used for download the BPR. You can check for the BPR item by using the Find functionallity of the BPR Selection Help in SAP Solution Manager. Solution: In such a case you can only replace the BPR item with an userdefined one. If your ICO release differs you should also replace your BPR download with a new one belonging to your current release to look for an alternative.

ErrorCode SOLAR_0036 Short description: Unable to transfer element 'SYNCHELEMENT'. Please add the 'LOG. COMP.' logical component to the system landscape of the project, and start synchronization again. Occurrence: You synchronized towards SAP Solution Manager and tried to upload a BPR element that does not match your system landscape. Cause: The BPR item you tried to upload requires a certain logical component that misses in your projects system landscape. Usually this happens when you use elements from a BPR which does not belong to your project. Solution: Download a BPR belonging to your project and use only elements from that one. Alternatively you can add the missing logical component to your project in SAP Solution Manager.

ErrorCode SOLAR_0037 Short description: Unable to transfer element '%1'. Please add the missing logical components to the system landscape of the project. Due to the large number of possible combinations, the required logical components cannot be determined here. Please check the context of the element using the 'Check context' pop-up menu, add the determined logical components to the system landscape, and restart synchronization. Occurrence: You synchronized towards SAP Solution Manager and tried to upload a BPR element that does not match your system landscape. Cause: The BPR item you tried to upload requires a certain logical components that are missing in your projects system landscape. Usually this happens when you use elements from a BPR which does not belong to your project. Solution: Download a BPR belonging to your project and use only elements from that one. Alternatively you can add the missing logical component to your project in SAP Solution Manager. To do so, select the BPR item in ARIS for which the upload fails and choose the context menu entry Check context. (Link to help for check context).

ErrorCode SOLAR_0038 Short description: Unable to find enterprise areas for the BPR language update in the selected group. Occurrence: You made a BPR language update but the group you selected does not contain any object with a maintained SAP function type enterprise area Cause: The enterprise areas are the top level items of the BPR which are placed during the download of the BPR in a group having the name of the project the BPR belongs to. Since the language update starts the update on enterprise areas the group on which you start the update must contain any. Solution: Just select the group which contains the enterprise areas (items which have the SAP function type maintained with enterprise area) of your BPR. Note that you also can do the update on a subset of enterprise areas. The language update will consider only the existing items found in the selected group. It will not create new ones. (link to help for language update.)

ErrorCode SOLAR_0039 Short description: Unable to change the scope of the node. Please change the global attribute of the node to a type that allow to change the scope. Occurrence: You synchronized towards SAP Solution Manager and tried to change the scope of a node that has set the global attribute type on global or standard complete. Cause: It is not allowed to change the sope of a node that has set the global attribute type on on global or standard complete. Solution: Change the global attribute of the node on a type that allow to change the scope. The global attribute must not set (initial value) or have to set on the types harmonized, local or standard partial that it is allowed to changed the scope of the node. Note that the global attribute can only set inside the SAP Solution Manager and only on template projects on which the project with the relevant node is based.

ErrorCode SOLAR_0040 Short description: Unable to edit the locked node. Please unlock the node and restart the synchronization. Occurrence: You synchronized towards SAP Solution Manager and tried to change or delete a locked element. It could appear as well if you tried to add child element to a locked element (e.g. process steps to a locked process) or you tried to move a node under a locked element. Cause: It is not allowed to change or delete a locked element/node/shortcut and it is not allowed to add elements to a locked node. Furthermore it is not allowed to move a node node a locked element(e.g moving of a process step from one element to a locked element). Solution: Just unlock the locked element/node that you allow to change or delete the element or add and move elements to this element.

Errorcode: CONN_0001 Short description: Unable to find the 'sapjco.jar' file. You will obtain further information in the Administration Guide. Occurrence: The ARIS client or ARIS server tries to connect to a sap system and cannot find the needed library. Cause: The sapjco.jar is a library from SAP which must be available for the ARIS client and server to establish a RFC connection and is missing. Since SAP does not allow the redistribution of this library each customer has to download it from SAP and install it by himself. Solution: You find all needed information in the ARIS administration guide in the ARIS for SAP NetWeaver chapter. Note that you have to make the 'sapjco.jar' available on server and client. Please consider also that your SAP system must have the RFC port open.

Errorcode: CONN_0002 Short description: Error while calling a Web service.\nPlease maintain the Web service URL ('View/Options/SAP options/Select server/Properties') and use an SAP Server as the default server. Occurrence: You tried to download the business process repository or the sceanrio pool but the web service URL set for this functionality couldnt be used. Cause: Either the webservice URL is not maintained at the default server correctly or the webservice is not activated in the SAP system. Solution: You find all needed information in the ARIS administration guide in the ARIS for SAP NetWeaver chapter.

Errorcode: GEN_0001 Short description: You have started an action for a definition that has not been saved yet. Please save the model and restart the action. Occurrence: You have started an action which requires an ARIS server call on a not saved object in the ARIS designer. Cause: Since the object is until now only available on the client the server call will fail because the object is not known there. The server can only access objects that are made persistent. Solution: Just save the model to make the object persistent.

ErrorCode ESR_0001 Short description: Error starting the WSDL editor: [FILE.WSDL]. Make sure that you have an associated editor for your WSDL. Occurrence: A WSDL was associated to a service interface and you want to display it. Cause: The WSDL was tried to open with an associated editor but such an association does not exist. Solution: In your Javaclient directory a folder ESR_WSDL should exist containing the wsdl you want to display. Go to this directory and right click the wsdl. Select Open from the context menu and choose a programm you want to associate with your wsdl. After this the association is made and you can display your WSDL using ARIS in your chosen editor.

ErrorCode ESR_0002 Short description: Unable to transfer WSDL.\nPlease make sure that a valid ESI link is maintained and the WSDL exists in the ESR. Occurrence: You selected assign WSDL on a service interface but no WSDL was transferred from the ESR server. Cause: To successfully transfer a WSDL in ARIS on a service interface the service interface must have a valid ESI link, that means the ARIS service interface object has in ESR an ESR object service interface assigned and the ESR service interface has a WSDL maintained. Solution: If you have no ESI link open the ARIS model in ESR containing your service interface and right click it. Choose Service Interface Assignment -> Create Assignment. If the WSDL is missing just assign one to the ESR service interface. You can navigate from the ARIS object from the model containing the service interface by using the context menu Service Interface Assignment -> Open Assignment

ErrorCode ESR_0003 Short description: Unable to transfer WSDL. ESI links may not have been maintained correctly for some of the service interfaces, or the WSDL is missing in the ESR system. You can open the WSDL in the editor by double-clicking on the WSDL symbol assigned to the service interface in the model. Occurrence: You multiselected assign WSDL on service interface objects but for some items no WSDL was transferred from the ESR server. Cause: To successfully transfer a WSDL in ARIS on a service interface the service interface must have a valid ESI link, that means the ARIS service interface object has in ESR an ESR object service interface assigned and the ESR service interface has a WSDL maintained. You can easily check the serviceinterfaces in the ARIS models. Service interfaces where the transfer was successful have a minisymbol on the bottom right which you can also doubleclick to open the WSDL. Solution: If you have no ESI link open the ARIS model in ESR containing your service interface and right click it. Choose Service Interface Assignment -> Create Assignment. If the WSDL is missing just assign one to the ESR service interface. You can navigate from the ARIS object from the model containing the service interface by using the context menu Service Interface Assignment -> Open Assignment.

ErrorCode ESR_0004 Short description: The selected Service Request was already implemented. Occurrence: You tried to assign a service request to a process component in the SAP service viewer. Cause: The service request has the state implemented. Since you maintain the relation to a process component to give a suggestion in which process component your request should be realized, it makes no sense to do so with an already implemented one. Solution: You cannot assign an implemented service request. If you find that your request is not fulfilled or incomplete and want to have it reworked you can create a new request or reset the state using the report to export the requests. (link to the proceeding in ARIS help)

ErrorCode ESR_0005 Short description: There are more than one service requests with the same service request id '%1'. None of them were edited. Occurrence: If you trigger a ESR merge on a database that contains more than one service requests with the same service request id. Cause: The operations is assigned to the service request by using the service request id. Therefor the service request id have to be unique that the operation can assign exactly to one service request. Solution: Find the service requests with the non-unique service request id and change the non-unique id with keys which are unique.