Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Data Engineering Quality 10.2.1
  • All Products

Table of Contents

Search

  1. Preface
  2. Informatica Developer
  3. The Model Repository
  4. Searches in Informatica Developer
  5. Connections
  6. Physical Data Objects
  7. Flat File Data Objects
  8. Logical View of Data
  9. Viewing Data
  10. Application Deployment
  11. Object Import and Export
  12. Data Type Reference
  13. Keyboard Shortcuts
  14. Connection Properties

Developer Tool Guide

Developer Tool Guide

Back Next

SAP PowerDesigner OOM 9.x to 15.x Import Properties

SAP PowerDesigner OOM 9.x to 15.x Import Properties

Configure the import properties when you import a logical data object model from SAP PowerDesigner OOM 9.x to 15.x.
When you import a logical data object model from SAP PowerDesigner OOM, the Developer tool imports the classes and attributes but leaves out other entities. To import a logical data object model, export the model from SAP PowerDesigner in the UML 1.3 - XMI 1.0 XML format.
The following table describes the properties to configure when you import a model from SAP PowerDesigner OOM:
Property
Description
Target Tool
Specifies which tool generated the model you want to import.
Select one of the following options:
  • Auto Detect. The Developer tool detects which tool generated the file.
  • OMG XMI. The file conforms to the OMG XMI 1.0 standard DTDs.
  • Argo/UML 0.7. The file was generated by Argo/UML 0.7.0 or earlier.
  • Argo/UML 0.8. The file was generated by Argo/UML 0.7.1 or later.
  • XMI Toolkit. The file was generated by IBM XMI Toolkit.
  • XMI Interchange. The file was generated by Unisys Rose XMI Interchange.
  • Rose UML. The file was generated by Unisys Rose UML.
  • Visio UML. The file was generated by Microsoft Visio Professional 2002 and Visio for Enterprise Architects using UML to XMI Export.
  • PowerDesigner UML. The file was generated by Sybase PowerDesigner using XMI Export.
  • Component Modeler. The file was generated by CA AllFusion Component Modeler using XMI Export.
  • Netbeans XMI Writer. The file was generated by one of applications using Netbeans XMI Writer such as Poseidon.
  • Embarcadero Describe. The file was generated by Embarcadero Describe.
Default is Auto Detect.
Auto Correct
Fix and import an incomplete or incorrect model in the XML file.
Model Filter
Model to import if the XML file contains more than one model. Use a comma to separate multiple models.
Top Package
The top-level package in the model.
Import UUIDs
Import UUIDs as NativeId.
0 COMMENTS
We’d like to hear from you!