I have a very specific problem. When I execute an initial load for an object in transaction R3AS, the system sends this correctly to the SMQ2 queue. However, it stays there until it's manually executed.
Once this is done, there are no further problems or errors in the information that is being replicated from ECC.
It seems I'm missing a job configuration in this client so that when I execute an object replication en R3AS, the queue gets automatically activated.