Primary keys on PeopleSoft tables - required for SQL Server replication

We would like to use SQL Server transactional replication to replicate some tables to another database, but primary key is required for sql replication so we can not easily do this since PeopleSoft records turn in to tables with unique clustered indexes (not technically a primary key at the database level).

I have seen others bring up this topic but have not seen any type of resolution.  I'm wondering if anyone has advice or creative ideas to solve this dilemma.  I suppose we could add a primary key at the SQL level since it can't be done via app designer, but, I have a feeling that could cause problems in general, not to mention would very likely be an issue during upgrades and we would have to remember to add the key again after any alters of table.