Just to clarify: A Table cannot have "two primary keys" ([Highlander]There can only be one![/Highlander].) It can however have a single primary key which consists of two - or three, or even ten - fields, which jointly must be unique.
Your error message explains what is wrong: there already exist at least two records in the table with identical values of Plan and Description. Try creating a Totals query grouping by Plan and Description and counting records to find which records have duplicates.
Could you explain the logic of this table? It's ordinarily not necessary to have a "description" as part of a primary key. A PK should meet three desiderata: it MUST be unique (see Highlander above :-{) ); it should be stable, not something that will be changed often or at all; and ideally it should be short, such as a Long Integer or Autonumber which can be an efficient link to foreign key fields in other tables. How will this table be used, and what is the point of this two-field key?