SOLMAN Sync of a definition – ends with an ERR

Mr. Eli Green:

You are correct, duplicate SAP ID's will cause an error during synchronization.  However, when creating a definition copy keep in mind that the integrity of the attributes is maintained to allow for one to "reuse" the object (along with the maintained attributes) and "define" it as required/needed.  This means, YES the SAP ID attribute is kept intact (along with the other populated attributes).  I see the definition copy is an "accelerator" of sorts....if in fact you intend to reuse the information in the populated attributes (less room for error).  BUT, when using a object that has been synchronized you must delete the SAP ID to successfully synch to SolMan.  The end result is an object element in the SolMan structure that shares the same name (not sure why one would have a definition object with the same name in the structure....) or different name if you changed the name attribute (net value:  all other required mandatory attributes for synchronization are maintained and synch success is achieved).  Example below shows using a definition copy of a SAP function: