I'm not clear on what you're trying to setup, ie, why you want a repdef/sub on a particular table ... ?
---------------
Some background on what the documentation is talking about ... for sake of discussion let's say we have a WS pair defined like the following:
ActiveDS.ActiveDB --> LogicalDS.LogicalDB --> StandbyDS.StandbyDB
The idea of creating a repdef/sub in a WS environment would be to have the entire WS pair act as the primary database for the repdef ... so that no mattter which direction the transactions are flowing ... left to right ... right to left ... the logical connection acts as a tap that allows a transaction to be routed to a 3rd database, eg:
ActiveDS.ActiveDB --> LogicalDS.LogicalDB --> StandbyDS.StandbyDB
|
|--> repdef -> sub --> OtherDS.OtherDB
Regardless of the direction in which the transactions are flowing in the WS setup (left to right, right to left), the repdef can be used to grab a copy of that transaction and send it to another database outside of the WS setup.
---------------
In your example your repdef is ok, but you're trying to define the subscription to point at the logical connection and as the error message states ... you cannot have the same database (the logical connection in your case) serve as both the primary and replicate database.
NOTE: Yes, I have created (database) repdefs with a WS/logical connection as the primary, but then the (database) subscription was pointing at yet another database (ie, the subscription was *not* pointing at the logical connection, was *not* pointing at the WS/active db, was *not* pointing at the WS/standby db).
So, at this point we need more details on what you're trying to accomplish. You could start by telling us which DS.DB's make up the active and standby portions of your WS configuration and the name of the DS.DB where you wish to send the subscription.
---------------
Another possibility ...
I notice that you only list 2 columns in the repdef, and those 2 columns also make up the primary key definition.
Are you trying to setup a PK-only repdef for performance reasons? If so, then all you need to do is create the repdef ... Repserver should automatically recognize/use the repdef for PK-only purposes without the need for the subscription; in fact, it's *NOT* even possible to create a subscription in this situation (PK-only, performance related) for use in a WS setup.