Logical Repository to access a Content Server for Document Archiving

[MichaelGtn]

Hi Experts,

I wish to use Logical Repositories to access our Content Server. The idea being after a system refresh, no modification will be necessary in OAC0 or OAC3.
This works well for DMS and for Data Archiving objects, but this does not seem to the case for Document Archiving.

Transaction OAC3, field Cont.Rep.ID only sees selective repositories as per "2477262 - Content repository ID not listed in transaction OAC3".

Further investigation leads to table TOAAR which only accepts 2 CHAR on the ARCHIV_ID, which is my case is fine because the Logical Repositories have been created as such (ZX) and this will redirect to ZX_<SYSID>_<CLIENT>.
TOAAR however does not contain the logical repository entries. As soon as I switch from Storage Type "04 HTTP content server" to "09 Logical Repository", the entry is removed from TOAAR.
The repository ZX_DEV_100 isn't shown in TOAAR because it's longer than 2 CHAR (and this is can understand is normal), but the Logical Repository ZX which is defined in the Document Area as ARCHLINK, I can't understand why this is excluded.

I don't know how (and no, I didn't force it with SE16), but I've got an entry in TOAAR which is a Logical Repository. Yes, we'll call this a bit of luck for testing.
I've followed the test procedure in message "1792336 - Test if a Print List is being Archived", and this is a success.

So, I have a fluke entry in TOAAR which proves that a Logical Repository could and does work for Document Archiving, but I am incapable of repoducing this OAC0 entry with a resulting line in TOAAR that could then be used in OAC3.

Please advise how I can proceed to make use of Logical Repositories for Document archiving.

Many thanks