well, schema _SYS_BI actually belongs to user _SYS_REPO in standard installations, I just checked. Hence you cannot grant permission on that schema back to _SYS_REPO, but you shouldn't have to either.
Check:
select * from"PUBLIC"."SCHEMAS"where schema_name='_SYS_BI'
What user are you working with? I assumed it was the SYSTEM user, but the screenshot above doesn's show all the privileges a SYSTEM user normally has.
Please check the here listed "template modeling role" - it's SQL statements plus comments, why certain privileges are needed. This example constructs a role named MODELING_ROLE which you could then grant to your account. Note that there are data-specific privileges in there that you might have to adjust to your particular situation.
Best,
Richard
/* note: the drop role statement has side effects */
/* such as cascaded revoking of privileges */
drop role MODELING_ROLE;
create role MODELING_ROLE;
/* Required to read the repository tree */
/* (expand the "content" tree). */
/* Does not allow seeing the content of */
/* packages */
/* (SQL Privilege) */
grant execute on REPOSITORY_REST to MODELING_ROLE;
/* Allow reading all objects in all packages */
grant REPO.READ on ".REPO_PACKAGE_ROOT" to MODELING_ROLE;
/* allow creation of new packages inside of native packages */
/* (Package Privilege) */
grant REPO.MAINTAIN_NATIVE_PACKAGES on ".REPO_PACKAGE_ROOT"
TO MODELING_ROLE;
/* allow creation of new packages inside of imported packages */
/* this should normally not be granted for imported package */
/*
grant REPO.MAINTAIN_IMPORTED_PACKAGES on ".REPO_PACKAGE_ROOT"
to MODELING_ROLE;
*/
/* Allow saving the ana priv (required for creating a ana priv) */
/* Grant this for native packages. */
/* (Package Privilege) */
grant REPO.EDIT_NATIVE_OBJECTS on ".REPO_PACKAGE_ROOT"
TO MODELING_ROLE;
/* allow editing of objects inside of imported packages */
/* this should normally not be granted for imported package */
/*
grant REPO.EDIT_IMPORTED_OBJECTS on ".REPO_PACKAGE_ROOT"
to MODELING_ROLE;
*/
/* Activate the views underneath the given package (in this case the */
/* root node of the repository */
/* Grant this for all native and imported packages. */
/* (Package Privilege) */
grant REPO.ACTIVATE_NATIVE_OBJECTS on ".REPO_PACKAGE_ROOT"
to MODELING_ROLE;
grant REPO.ACTIVATE_IMPORTED_OBJECTS on ".REPO_PACKAGE_ROOT"
to MODELING_ROLE;
/* Allow the user to verify that the tables underlying the */
/* Information Models referred to in the Analytic Privilege */
/* do exist. */
/* Allow reading _all_ metadata in the system, but no */
/* table contents. */
/* (System Privilege) */
grant CATALOG READ to MODELING_ROLE;
/* For activation: need SELECT on data schema */
/* note: we include schema "SYSTEM" here as an example. */
/* the SELECT privilege should normally not be */
/* granted on the SYSTEM schema. */
/* But it _must_ be granted on all tables used in */
/* data models, so typically on all data schemas */
/* (SQL Privilege) */
grant select on schema SYSTEM to MODELING_ROLE;
/* For activation of time-based Attribute Views */
/* these are based on a table in schema _SYS_BI */
/* (SQL Privilege) */
grant select on _SYS_BI.M_TIME_DIMENSION to MODELING_ROLE;
/* Needed to deploy the run-time objects */
/* i.e. the consumption column views */
/* (SQL Privilege) */
grant create any on schema _SYS_BIC to MODELING_ROLE;
grant drop on schema _SYS_BIC to MODELING_ROLE;
/* if a SQL script calls a function, you need */
/* execute on the run-time object */
grant execute on schema _SYS_BIC to MODELING_ROLE;
/* Required for activation */
/* (System Privilege) */
grant CREATE SCENARIO to MODELING_ROLE;
/* required for activation of Calculation Views */
/* but not needed for attribute/analyitc views: */
/* Additionally required for reading from the */
/* activated model. */
/* (SQL Privilege) */
grant select on schema _SYS_BIC to MODELING_ROLE;
/* You always need some appropriate Analytic Privilege. */
/* Either create one, or grant the “SAP_ALL” privilege: */
/* Note: _SYS_BI_CP_ALL allows reading the content of */
/* all activated data models (in combination with */
/* SELECT on schema _SYS_BIC). */
/* (Analytic privilege) */
call GRANT_ANALYTIC_PRIVILEGE ('_SYS_BI_CP_ALL', 'MODELING_ROLE');
/* if modelers shall also be able to use front-ends */
/* such as Analysis for Office, SAP BusinesObjects */
/* Explorer or MS Excel for checking their data models, */
/* they also need SELECT privileges on the BIMC-tables */
/* in schema _SYS_BI. We blindly grant SELECT on the */
/* entire schema here, although this is strictly */
/* a little bit more than is required. */
grant select on schema _SYS_BI to MODELING_ROLE;