physical data model using excel import is failing in SAP Power Designer

[sbs123]

I need assistance with importing relationships from an Excel file into the SAP PowerDesigner physical data model. The relationships are being created incorrectly because the foreign key name in the child table differs from the primary key name in the parent table. How can I resolve this issue? What mapping should I use to ensure that the correct foreign key name is applied, rather than creating a new column in the child table that matches the parent key?

below is the mapping used 

Table reference=Reference: Table Name =ChildTable, child foreign key=DefaultMapping, Parent Table Name =ParentTable, Parent Key Name=ParentKey, Reference Name =ForeignKeyConstraintName, Display Name=DisplayName

[Ondrej_Divis]

Hi, I tried it with PDM and it seems like a bug to me. George is right about Reference Joins. You have to import them as separate object (on separate excel sheet), but the import still doesn`t work properly. I am still getting "Error: Could not find parent object location with Name = Order.CustomerID". I tried many things (playing with Reference settings in Model Options, changing the order of excel sheets to import, modifying actual values to import, importing with/without ParentKey property on the Relationship,...) nothing helped. But I agree, that standard Excel Import should be capable of that.

You have several options now:

• debug and repair the Excel Import extension by yourself (thousands of lines of code, uncertain results)
• write your own import routine (quite easy if you know what you are doing, I`ve done it many times, I can help you with that)
• do manual repairs after each import

Which option is best for you depends on number of objects to be imported, whether it is one-time or repeated action, how quickly you need it, etc.

HTH and in case you need my help, let me know here (or on LinkedIn),

Ondrej Divis