Error using view to limit data access between databases in SQL Server
A user must have a security context to access the ReplData database.  That can be their own account, an AD group of which they are a member, or the guest user (if the guest user is enabled in the ReplData database).

No permission need be granted on the ReplData.dbo.refData table as long as the ownership chain is unbroken.  Since the refData table is owned by dbo, the implication is the login that owns the ReplData database must be a database user in the Reporting database and that user must own the SourceA schema.  Alternatively, the Reporting could be owned by the same login that owns the ReplData database and the SourceA schema owned by dbo.  

You can change the schema or database owner with ALTER AUTHORIZATION, if needed:

ALTER AUTHORIZATION ON SCHEMA::SourceA TO &lt;ReplData-database-owner-user&gt;;
ALTER AUTHORIZATION ON DATABASE::Reporting TO &lt;ReplData-database-owner-login&gt;;


Also, the DB_CHAINING database option must be on in both the ReplData and Reporting databases.

In the case of stored procedures, you can get around the need for a user context by signing the module with a certificate that exists on both databases.  That's not an option with a view, though.