An XSD (XML Schema Definition) file defines the structure of the data, which a data object contains. You import an XSD file in your project if you want to set a data type that is different from the primitive ones to a data object.
The data mapping in the process composer does not support all data types. For more information about all limitations on data types, see the SAP Note 1468084 .
Your process model does not directly use the XSD documents that you import and are contained in your project. The documents are first imported into the Enterprise Service Modeling (ESM) repository, which saves the imported data in its own proprietary format. The repository is seamlessly integrated into your project and the import takes place in the background.
When you import or reimport XSD documents into your project, it is possible that one and the same entity, meaning an entity with the same qualified name has a different definition in the document that you are trying to import, compared to the definition already existing in the project and defined by other documents. Such different definitions of the same entity are not allowed because of the qualified name uniqueness concept. If such a conflict occurs, you have the following options in the dialog comparing the two definitions:
Update the files
If you choose the Update Files >> pushbutton, the entity definition that comes from the document you are trying to import overrides the old entity definition both in the repository and in the files of the already imported documents. The new document is imported. You must use this option carefully because it can have a severe impact at runtime. Choose this option only if you are sure that all existing documents that contain this entity have changed and use the new entity definition. If you are not sure, get the latest versions of these documents, reimport them, and if you still get this conflict, reject the import.
Reject the import
If you choose the Reject pushbutton, the document that you are trying to import is not imported into the repository and appears only in your project with an error marker. If you still want to use this document, you must import it into another project.
You can check all the documents that define a conflicting entity when you choose the Show/Hide Affected Schemas button, located in the top-left corner of the dialog.
You have opened the Process Development perspective in the SAP NetWeaver Developer Studio and have expanded your project in Project Explorer view.
Expand Process Modeling , then expand Data Types .
In the context menu of the XSD Files folder, choose Import XSD... .
Choose the Browse pushbutton to define an output folder for the XSD source file. Choose the OK pushbutton.
We recommend that you select the src\wsdl folder in your project for an output folder.
Select Remote Location / File System from the Available XSD sources and choose the Next pushbutton.
Select an XSD file to import.
To do that, choose one of the following options:
Choose the Browse pushbutton and navigate through the file system to select the XSD file you want to import.
Enter a URL to import the XSD file from.
Choose the Finish pushbutton.
The XSD file appears in your project, infolder. The XSD source file appears in the output folder you defined.
If you paste an XSD file into your project (that is, if you do not use the import wizard), you must switch on the automatic build option in the Developer Studio . Otherwise, the file is not imported into the ESM repository and appears in your project with a warning marker. To switch on the automatic build option, choose in the Developer Studio .
You may need to reimport into the repository an XSD document which you have already used in the process and you have defined data mappings for the data objects that use this XSD document. A reimport is necessary because the process model may become invalid if the XSD document has been subsequently modified and, for example, a type has been changed.
To trigger the reimport, from the context menu of the XSD document choose Reimport and accept the changes shown in the dialog that appears. The new version of the document is imported in the repository and overrides the old one. Thus, you reimport the modified XSD file from your project into the ESM repository. If you want to reimport the file from its original location, you have to use the option Import XSD... , described in the procedure above.
If you choose to reject the changes, the new version of the document is not imported into the repository and, therefore, the document file and the repository are not in sync. In this case, it is recommended that you either make some additional changes and reimport the document, or revert it to its previous version.
For more information about configuring the reimport preferences, see Configuring WSDL and XSD Reimport Preferences .
You can use the Show/Hide Transitive Differences button to see all entities that are not directly changed, but also depend on changed entities. After the reimport, the mapping editor preserves the data mappings for unchanged parameters and removes the data mappings which have become invalid.