SAP PowerDesigner PDM 7.5 to 16.x - Import - Cloud

Talend Cloud Data Catalog Bridges

author
Talend Documentation Team
EnrichVersion
Cloud
EnrichProdName
Talend Cloud
EnrichPlatform
Talend Data Catalog

Note: This bridge is not available in Talend Cloud Data Catalog by default. You need to set up a remote harvesting agent to import metadata from this source. For more information, see Deploying a remote harvesting agent in Talend Cloud Data Catalog Administration guide.

Bridge Requirements

This bridge:
  • is only supported on Microsoft Windows.

Bridge Specifications

Vendor SAP
Tool Name PowerDesigner PDM (Physical Data Modeling)
Tool Version 7.5 to 16.x
Tool Web Site https://www.sap.com/products/powerdesigner-data-modeling-tools.html
Supported Methodology [Data Modeling] Data Store (Physical Data Model, Stored Procedure Expression Parsing), Graphical Layout via PDM XML File
Data Profiling
Remote Repository Browsing for Model Selection
Incremental Harvesting
Multi-Model Harvesting

SPECIFICATIONS
Tool: SAP / PowerDesigner PDM (Physical Data Modeling) version 7.5 to 16.x via PDM XML File
See https://www.sap.com/products/powerdesigner-data-modeling-tools.html
Metadata: [Data Modeling] Data Store (Physical Data Model, Stored Procedure Expression Parsing), Graphical Layout
Component: SybasePowerDesignerPdm07 version 11.0.0

OVERVIEW
This bridge imports data models from a PowerDesigner .PDM (physical data model) file with Tables, Columns, Data Types. This bridge also imports all relationships and their implementation (e.g. PK/FK) as well as the graphical layout (diagrams).

REQUIREMENTS
n/a

FREQUENTLY ASKED QUESTIONS
Q: How do I handle PDM XML files which contain shortcuts to external tables?

A: PDM XML model files may contain relationships which refer to tables defined as 'shortcuts'. Shortcuts are references to external tables. Unfortunately, in this case the PDM XML file does not contain sufficient information to reconstruct the PK/FK relationships properly. If this is the case with the imported file, there will be a message in the log like:

This model may have shortcut dependencies on external model: 'file:///...'

and, by default, the bridge will not attempt to reconstruct those PK/FK relationships to shortcuts.

However, the source tool has the capability to merge these files together so that the shortcuts are resolved. To do so:

- Refer to the log for all the files with shortcuts
- Open the tool and go to the Tools -> Merge Models... menu option
- Create a new merged model
- Save the new model as a PDM XML and import.

Q: I see warnings or errors in the log. How can I validate the model before importing?
A: PowerDesigner allows examining the model for modeling inconsistencies.
Please use menu Tools -> Check Model... and take necessary, yet corrective actions to resolve detected issues.

Q: I imported my model, but the SQL View definitions are incomplete. How can I fix them?
A: PowerDesigner versions 7 and 8 have limited support for SQL Views. It is not possible to retrieve a valid definition of the source tables and columns. PowerDesigner versions 9 and later support the concept of 'View Reference' to associate a View with its source tables and columns. If you upgrade to a version that supports this concept, your models should import correctly.

LIMITATIONS
Refer to the current general known limitations at http://metaintegration.com/Products/MIMB/MIMBKnownLimitations.html or bundled in Documentation/ReadMe/MIMBKnownLimitations.html

PDM files in binary format are not supported.

SUPPORT
Provide a trouble shooting package with debug log. Debug log can be set in the UI or in conf/conf.properties with MIR_LOG_LEVEL=6


Bridge Parameters

Parameter Name Description Type Values Default Scope
File This bridge imports PDM XML files. If you do not have the model saved as a PDM XML file already, you may create a PDM file for import:

1. Physical Data Model is opened in SAP PowerDesigner.
2. Choose 'Save As' from the 'File' menu.
3. In the 'Save as type' list, select 'Physical Data Model (XML) (*.PDM)'.
4. Enter the file name and select a directory to save the file in.
5. Click 'Save'.

The bridge will use the generated PDM XML file as input.
FILE *.pdm   Mandatory
Apply binary characters filter Specifies if invalid binary characters should be filtered out of the file as a pre-process before parsing the PDM XML file. This option is a workaround for a bug in the PowerDesigner tool which sometimes generates a file that does not conform with the XML specification (contains binary characters).

Warning: Applying this filter may remove some unicode national characters.
BOOLEAN   True  
Import UDPs A User Defined Property (UDP) is usually defined with a property definition object that has a default value. The objects that the property applies to may have an explicit value for this property. They may instead have no value assigned at all in which case the default value of the property definition (implicit value) applies.

Control how property definitions and values are imported:

'As metadata'
Import the explicit value as the property value. Implicit values are not imported. The default value is kept on the property type only.

'As metadata, migrate default values'
Import the explicit or implicit values as property value.

'In description, migrate default values'
Append the property name and value, even if implicit, to the object's description property. This allows you to export the UDP values to another tool which does not support the notion of UDP.

'Both, migrate default values'
Import the UDP value, even if implicit, both as metadata and in the object's description.
ENUMERATED
As metadata
As metadata, migrate default values
In description, migrate default values
Both, migrate default values
As metadata  
Append volumetric information to the description field Import volumetric information (number of occurrences) and append it to the description field:

'True'
Append volumetric information to the description field.

'False'
Ignore volumetric information.
BOOLEAN   False  
Remove text formatting PowerDesigner versions 7.0 to 7.5 store annotations as plain text, while versions 8 and later use RTF. To remove Rich Text Formatting (RTF) from annotations:

'False'
The model was generated by PowerDesigner 7.0 or 7.5.

'True'
The model was generated by PowerDesigner 8.0 or greater.
BOOLEAN   True  
Reverse role names Swap relationship rolenames for each model:

'False'
Do not swap rolenames.

'True'
Swap rolenames.
BOOLEAN   False  

 

Bridge Mapping

Meta Integration Repository (MIR)
Metamodel
(based on the OMG CWM standard)
"SAP PowerDesigner PDM 7.5 to 16.x"
Metamodel
SybasePowerDesignerPdm07
Mapping Comments
     
Association Reference  
Aggregation   computed from migrated FK attributes.
Comment Comment Reference Comment.
Description Description Reference Description.
Name Name Reference Name.
NativeId   ObjectID
PhysicalName Code Reference Physical Name.
Stereotype Stereotype Reference Stereotype.
AssociationRole Reference  
ExtraConstraint Update constraint, Delete constraint  
Multiplicity Cardinality Cardinality of the reference
Source   Set to true for the association role on the parent table's side
AssociationRoleNameMap Columns/Reference Join Used when some Columns are renamed in a Reference Join.
Attribute Column, Business Rule  
Comment Comment Column Comments.
Description Description Column Description.
ExtraConstraint Business Rule The business rules attached to this column
InitialValue Default  
Name Name Column Name.
NativeId   Object ID
Optional Mandatory  
PhysicalName Code Column Physical Name.
Position   The attributes are ordered by position in the PDM file
Stereotype Stereotype Column Stereotype.
BaseType Domain, Attribute Data Type See DerivedType
BusinessRule BusinessRule  
Comment Comment  
Description Description  
Name Name  
NativeId   ObjectID
PhysicalName Code  
Stereotype Stereotype  
Value ServerExpression  
CandidateKey Key  
Comment Comment  
Description Description  
Name Name  
NativeId   ObjectID
PhysicalName Code  
Stereotype Stereotype  
UniqueKey   set to True
Class Table  
Comment Comment Mapped only if comment is empty.
CppClassType   Set to ENTITY
CppPersistent   Set to True
Description Description Table Description.
DimensionalRole Dimensional Type  
Name Name Table Name.
NativeId   ObjectID
PhysicalName Code Table Physical Name.
Stereotype Stereotype Table Stereotype.
ClassDiagram Physical Diagram, MultiDimensional Diagram  
Comment Comment Diagram Comment.
Description Description Diagram Description.
Name Name Diagram Name.
NativeId   ObjectID
PhysicalName Code Diagram Physical Name.
Stereotype Stereotype Diagram Stereotype.
DatabaseSchema User Tables and objects belonging to a User are linked to a schema
Comment Comment  
Description Description  
Name Name  
NativeId   ObjectID
PhysicalName Code  
Stereotype Stereotype  
DerivedType Domain, Attribute Data Type  
Comment Comment Domain Comments
DataType Data type See datatype conversion array
Description Description  
InitialValue Default  
Length Length  
LowerBound Minimum  
Name Name Domain Name. Computed from the datatype if no domain is defined
NativeId   ObjectID
PhysicalName Code Domain Physical Name. Computed from the datatype if no domain is defined
Scale Precision  
Stereotype Stereotype  
UpperBound Maximum  
UserDefined   Set to true for the Model Domains
DesignPackage Package A main package "Logical View" is also created to contain all the objects that are defined at the model level
Comment Comment Package Comments.
Description Description Package Description.
Name Name Package Name.
NativeId   ObjectID
PhysicalName Code Package Physical Name.
Stereotype Stereotype Package Stereotype.
ForeignKey Join  
Name Integrity Constraint Name  
Identity Identity Identity column
Index Index Indexes are also generated for foreign keys
Clustered Cluster This option available for some databases.
Comment Comment Index comments.
Description Description Index description.
Name Name Index Name.
NativeId   ObjectID
PhysicalName Code Index Physical Name.
Stereotype Stereotype Index Stereotype.
IndexMember Index Column  
Position   The index members are ordered by position in the PDM file
SortOrder Sort  
Note Notes:Description and Notes:Annotation When using MIMB, these RichTextFormat descriptions are converted into plain text
Projection Symbol Graphical Information
BackgroundColor fill color  
Bold bold  
FontColor font color  
FontName font  
FontSize font size  
Height heigth  
Italic italic  
LineColor line color  
Width width  
X x  
Y y  
PropertyElementTypeScope MetaClass Extended Model Definitions
Scope   based on MetaClass type
PropertyType Extended Attribute Extended Model Definitions
DataType Data type  
Description Comment  
Group Extended Model Definition  
InitialValue Default value  
Name Name  
PropertyValue Extended Attribute Extended Model Definitions
Value Value  
RelationshipProjection Symbol  
BackgroundColor fill color  
Bold bold  
FontColor font color  
FontName font  
FontSize font size  
Italic italic  
LineColor line color  
SQLViewAssociation View Reference  
Comment Comment  
Description Description  
Name Name  
NativeId   ObjectID
PhysicalName Code  
Stereotype Stereotype  
SQLViewAttribute View Column  
Comment Comment  
Description Description  
Expression SQL Query The expression is put in the SQL field of the SQLViewEntity.
Name Name  
NativeId   Object id
PhysicalName Code  
Position   The Columns are ordered by position in the PDM file
Stereotype Stereotype  
SQLViewEntity View  
Comment Comment View Comments.
Description Description View Description.
Name Name View Name.
NativeId   Object id
PhysicalName Code View Physical Name.
Stereotype Stereotype View Stereotype.
WhereClause SQL Query  
Sequence Sequence  
Comment Comment Sequence Comments.
DataType Datatype  
Description Description Sequence Description.
Name Name Sequence Name.
NativeId   ObjectID
PhysicalName Code Sequence Physical Name.
Stereotype Stereotype Sequence Stereotype.
Shape Shape Symbol Graphical Information
BackgroundColor fill color  
Bold bold  
FontColor font color  
FontName font  
FontSize font size  
Height height  
Italic italic  
LineColor line color  
ShapeType symbol type  
Strike strikeout  
Underline underline  
Width width  
X x  
Y y  
Z   Z order of the shape as reported by position in the PDM file
StoreModel Model  
Comment Comment Model Comments.
Description Description Model Description.
Name Name Model Name.
NativeId   ObjectID
PhysicalName Code Model Physical Name.
StoredProcedure Stored Procedure  
Comment Comment The Stored Procedure Comments.
CppAbstract   Not used
CppConcurrency   Not used
CppFriend   Not used
CppScope   Not used
CppStatic   Not used
CppVirtual   Not used
Description Description The Stored Procedure Description.
Name Name The Stored Procedure Name.
NativeId   Object id
PhysicalName Code The Stored Procedure Physical Name.
Postcondition   Not used
Precondition   Not used
Semantics Definition  
Synonym Synonym  
Comment Comment Synonym Procedure Comments.
Description Description Synonym Description.
Name Name Synonym Name.
NativeId   Object id
PhysicalName Code Synonym Physical Name.
Stereotype Stereotype Synonym Stereotype.
Trigger Trigger  
Comment Comment The Trigger Comments.
CppAbstract   Not used
CppConcurrency   Not used
CppFriend   Not used
CppScope   Not used
CppStatic   Not used
CppVirtual   Not used
Description Description The Trigger Description.
Name Name The Trigger Name.
NativeId   Object id
PhysicalName Code The Trigger Physical Name.
Position   The triggers are ordered by position in the PDM file
Semantics Trigger Code  
Stereotype Stereotype The Trigger Stereotype.
TriggerType Trigger Type  
TypeValue List of Values All the values are listed in one tag
Name Label  
Position   TypeValues are ordered by position in the PDM file
Value Value