Symptom
- Import an ERwin model into PD as both logical and physical, the physical names from ERwin (which are created by a naming standard file) are not imported. The physical model has the same table names as the entities and column names as the attributes (with underscores in the PDM).
In example:
<User_Formatted_Name ReadOnly="Y" Derived="Y">PEOPLEYACHT</User_Formatted_Name><User_Formatted_Physical_Name ReadOnly="Y" Derived="Y">PEOPY</User_Formatted_Physical_Name>
- When the object is imported into PD 16.5.5.2, its name is PEOPLEYACHT and its code PEOPLEYACHT.
- The import seems to ignore the User_Formatted_Physical_Name attribute, use User_Formatted_Name for the object Name and apply the PowerDesigner default naming convention to set the object code (.convert_name(%Name%,"_")).
Read more...
Environment
SAP PowerDesigner (PD) 16.5 SP05 PL02 and previous versions
Product
SAP PowerDesigner 16.5 ; SAP Sybase PowerDesigner 15.3 ; SAP Sybase PowerDesigner 16.1 ; Sybase PowerAMC 16.5
Keywords
Er win, physical name, CR787476, 787476, CR#787476 , KBA , import , erwin , physical , BC-SYB-PD , PowerDesigner , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.