Normally we would recommend to delete the old configuration referring to that source system, which was created as 1:1, and start from scratch with 1:N. A switch between 1:1 and 1:N replication is not recommended! It might create some inconsistencies if part of the tables were initially selected for replication in an 1:1 context and later it is switched to 1:N or vice versa. So please only do this if absolutely indispensable! If there is a need to switch between 1:1 and 1:N replication, some more steps are required. In this case, proceed as follows:
1. Add the following authorization to the rfc user in the source system:
Authorization object S_DEVELOP (ABAP Workbench)
Field Activity: Value 42
Field Devclass: Value $TMP
Field OBJNAME: /1CADMC/* and /1LT/*
Field OBJTYPE: TABL
Field P_GROUP:
2. Set, for the corresponding mass transfer, field MULTI_LOGTAB_USE in table IUUC_MT_HEADER and field REUSE_SENDER of table IUUC_REPL_CONFIG to X (if you switch to 1:N) or to space (if you switch to 1:1) in the SLT system. If you switch to 1:N, make sure that in table IUUC_MT_HEADER, for the corresponding mass transfer, field SCENARIO_GUID contains the GUID of the configuration (otherwise, enter this GUID value, which you can get, for example, from table IUUC_REPL_MAP).
3. Stop the replication jobs
4. In transaction iuuc_sync_mon, or ltrc, use expert function "Reset Status of Tables and Synonyms" and activate checkbox "Reset Table/Syn. Receiver" In the same transaction, also execute expert function "Reset Replication Object Definition"
5. Execute report IUUC_REDEFINE_DB_TRIGGERS in the SLT system and specify the corresponding mass transfer ID
6. For tables DD02L, DD02T, and DD08L (and possibly other data dictionary tables chosen for replication), stop and restart the replication. 8. revoke the authorization added before
8. restart the replication jobs