Define the schema in an Autonomous DB connection at the Mapping Level

Description

When referencing Stored Procedures in an Autonomous Database the schema is a mandatory field in the configuration.  The Schema is hard coded into the connection - it can not be varied by mapping.

We are trying to use one ATP Database across several non-prod environments, separating data sets by Schema.  However we also make use of a number of stored procedures in the database(for performing XML file merge operations and the like, as these are more efficient that record by record transformation).  When referencing a stored procedure the schema is hardcoded in the end-point, meaning we have to edit the integration flow to change from one schema to another.  If the schema could be defined in the end-point mapping we would be able to use a variable to define this, potentially holding it in an