Default Schema in HINUCALC0

dear al,
hw to default schema our own schema into pc00_m40_calc ?
currently, IN00 is defaulted.
thnq.

curently, there are 8 payroll areas, and off cycles are also many.
so each time when client open this t-code, they have to change schema manually.
this is causing inconvienece to ppl. i thot, there if there is any scope to default own own schema,
so that no need to change.
i made, in00 as inactive (non executable), i think im right ?
thnq.

Similar Messages

Assigning a default schema to a user.

In Oracle can I assign a default schema to a user without using the later session command?
Is there a ALTER USER setting where I can assign a user a default schema?

Buddy,
To answer to your question.
1. First grant select any table or "grant select on all tables of user 'ELLIPSE' to the user "094137".
2. Later to access schema ELLIPSE's objects, from "094137" user, you ll have to create public synonym to all of the tables in ELLIPSE schema.
3. This way, the user "094137" can access all tables in SCHEMA ELLIPSE, with out specifying(prefixing) the schema name
Hope this helps
Thanks
I would like the user "094137" to logon and have access to the tables in another schema "ELLIPSE" with out qualifying the table name with "ELLIPSE".
The user "094137" has no objects of her own and only accesses the object of the schema "ELLIPSE".
Is there a direct way of assigning a user (with no objects) to have a default schema of another users (without the alter session default schema statement)

Default schema names in multi-tier landscape

Hi folks,
We have an interesting problem due to having different named default schemas in each of our 3 hana systems. For example lets say these are our default schemas in our development, staging, and production HANA systems;
DEV_SCHEMA
QA_SCHEMA
PROD_SCHEMA
Each of these replicating data from their corresponding SAP source systems.
Now, we have a view that is developed on DEV hana box and uses DEV_SCHEMA. When this view content is imported to QA or PROD we handle easily with schema mapping. All is well and good although we are not really a fan of this different naming and us developers did not choose this naming (self defense plea here for us brilliant developers whom never make such mistakes... PS: HI LARS! - Go Germany!)
Now we are setting up a connection from BW into HANA using system connection and inside this is a parameter called 'db user'. Although it's called db user it's actually looking for a SCHEMA name. If BW DEV is querying from HANA DEV this schema name would be DEV_SCHEMA. However if BW_QA is querying from HANA_QA then the name would need to be QA_SCHEMA but in our BW landscape we are locked in QA and PROD and normally can not and/or do not want to edit objects in non-native systems. Ideally what we need is our default schemas in HANA to have the same exact name throughout the HANA landscape.
All this said, I can see that it would be great to re-name our entire HANA landscape however that would be a HUGE monumental undertaking as all systems would need to be re-replicated again (at least I think).
Just curious if anybody else has named their schemas differently on each tier? What are most people doing? Naming the default schemas the same consistently or are you using schema mapping?
Thanks,
-Patrick

Hi Luke,
I am new to the project and there seems to be no original version. At some point a bunch of the destination field names were changed on the admin console and errors resulted from it both due to mismatched joins and the use of two word field names. I have documentation of the names for the set of tables in the function area but am having trouble with how everything matches up in the bottom half.. I'll keep working on it
Z

How to set default 'schema' in Pointbase?

I am using Netbeans EA2 with bundled appserv. I have tried creating a CMP entity bean from the Pointbase sample database (PBPUBLIC), which works. But when i created my own database (MYDATABASE) in Pointbase and a CMP bean for my test-table, i get a SQLException: Invalid table name "Mytable" specified at position 147.
This exception is thrown when i run "findByPrimaryKey" on my tablebean's home.
I think i have narrowed the problem down to this:
When I execute sql-commands on my db, I have to write
Select * from "MYDATABASE"."Mytable"
If i try to execute
Select * from "Mytable"
i get an error. (Invalid table name)
Whereas when i execute commands on the Pointbase sample db (PBPUBLIC), both these sql's work:
select * from "PBPUBLIC"."CUSTOMER_TBL"
and
select * from "CUSTOMER_TBL"
My questions are
1. How do i specify that "MYDATABASE" should the default schema in my database?
is it possible at all? I have tried searching the pointbase docs, and looked in Pointbase Commander, but have found nothing.
2. If I was going to fully qualify, that is, use "MYDATABASE"."Mytable" everytime i query the database, how and where do i specify that my entity bean should map betweed my dbschema and "MYDATABASE"."Mytable" ? Writing
<table-name>MYDATABASE.Mytable</table-name> in sun-cmp-mappings.xml did not work (but that was no suprise)
Is it not possible to fully qualify the tablename when using entity ejb's?
the error i get is similar to the one in this thread, except that my dbschema name is correct.
http://forum.java.sun.com/thread.jspa?threadID=586762&tstart=0
I have tried creating a new dbschema in Netbeans, and editing sun-cmp-mappings.xml to point to the new dbschema. But i still get the same error.
And btw, i know that my database is available, cause when i try to get the DataSource for my db directly, and execute a query, it works. But i have to fully qualify the tablename.
Any help would be appreciated
Thanks.

I solved using the SET PATH statement.
SET PATH your_default_schema, PointBase;
Follow an extract from the PointBase Developer�s Guide:
If you never execute a SET PATH statement, then the CURRENT_PATH consists of the
schema POINTBASE, followed by your existing schema. When a SET PATH statement is
issued, it completely replaces the existing CURRENT_PATH, unless CURRENT_PATH is part
of the schemas being set in the path.
The order of the schemas in the path is generally crucial. When the database system is looking
for SQL objects, it looks for them in each schema (unless explicitly referenced otherwise),
starting with the first schema in the path, then the next, etc...., until an SQL object is found that
meets the criteria. One way to override the CURRENT_PATH is to explicitly reference the
SQL object. For example, to reference a table, you can specify schema_name.table_name. In
the above examples, the SQL object of table_name would be searched in the schema of name
schema_name.
I hope this helps,
regards,
armando croce

Specify Default Schema Name in HANA Connection string

Hi,
I have connection string like this.
DRIVER={HDBODBC32};UID=uid;PWD=pwd; SERVERNODE=x.com:30015;
I want to include default schema name in the connection string.
Please help me

Hi S V
there is no option for that available.
To change the current schema it's required to run SET SCHEMA <schema_name> after you logged on.
- Lars

Change default schema

HI All,
We are in process of deploying "SAP Business Intelligence Adoption rapid-deployment solution" and we have a schema which is already created and didn't use the option "Allow multiple usage" during the time of creation, once we import modules provided by SAP there are some models which are named by SAP predefined schema,
I need to know what is the role I need to grant to out BW developers to change the default schema of these models.
Thanks in advance,
Shanaka.

All of the application data is in one schema. e.g. APPDATA. however I don't have the password for the APPDATA user, it is controlled by the DBAs. As a developer, I have a DEVUSER account and password. And the DEVUSER is configured with the appropriate access to the APPDATA schema by the DBAs.
The way I work right now, I connect to the database using the DEVUSER username/password, and I can navigate to the APPDATA schema through the "Other Schemas". I would like an option in the Connection properties that I can specify that APPDATA is my default schema, and the DEVUSER schema would be accessible from "Other Schemas".
I see this field as optional. If it is not entered, then the user's schema is used.
I hope that better explains things.
Randy

Changing default schema

Hi:
I would like to know if there is a way to change the default schema a user references. For example, I login as user "bill" with a schema associated with that user. But I want to reference the tables in someone else's schema, maybe user joe's schema, as the default when I write my queries.
I can do it with something like...
select col1 from joe.tbl1 where col2 > 5;
Is there a way to change the default schema to "joe" so that I don't have to prefix every table name reference with "joe."?
Thanks in Advance

You can use
ALTER SESSION SET CURRENT_SCHEMA = joe
This will not give you any access to any object owned by joe that you could not already access by using joe.name, but you will not need to add the joe.
HTH
John

Changing Users default Schema

Hello,
I'm trying to add a new user to my DB giving him the Schema of an old user as his default Schema.
Can somebody tell me how to change User2's default schema to User1?
Thanks in advance,
Gregor

Coolhands_99 wrote:
I created all the users from the command line and I used -k legacy option for the calendar. At this point everything is working fine the user calendars I imported from Cal server 6.0 schema 1 all show up and work like they should. Once I assign a service package to a user account it changes their default calendar to the hosted format. Now my users have two calendars their default (hosted format) which is blank and their imported (legacy format) that has all the calendar entries. It sounds like you missed this step during your move to calendar server 6.2/schema 2:
http://docs.sun.com/app/docs/doc/819-2656/6n4ua512a?a=view
"Configuring Calendar Server for Hosted Domain Support"
I've changed /opt/SUNWcomm/data/WEB-INF/classes/sun/comm/cli/server/servlet/ resource.properties from switch-caltype=hosted to switch-caltype=legacy and restarted the web container but no luck.These settings control how UWC log's into calendar server, i.e. as uid (legacy) or [email protected] (hosted) - it sounds that your problem is related to how calendar server stores to data instead.
Regards,
Shane.

How to re-create dropped default schemas

Can any one please tell how to re-create schemas that are by default created when database is installed.
All the default schemas other then SYSTEM, SYS, PUBLIC, DBSNMP were dropped.
Now it is required to re-create them. where can I find the script to re-create them.
Thanks in adv.

Not the demo schemas but the ones that are used by oracle server (system) for activities like - taking export, supporting sql plus, or user connect, etc. etc.
Schemas like DMSYS, OUTLN, etc. etc.

Setting default schema with Schema Select extension

Has anyone tried to do this? The web site says to put the default schema name in square brackets at the end of the connection name. When I try to do that, SQL Developer says that square brackets are illegal characters for a conneciton name.
In essence I want to have users log in with their own individual accounts, but have their schema context automatically set to a different schema.

You'll need to contact the extension provider directly for support.
You could achieve the same result with a trigger - and you'd have more control over when this happened, what applications, etc.
If you want bracketed connection names, you'll need to run an older version of SQL Developer or manually edit the connections.xml file to add the brackets to the name.
Edited by: Jeff Smith SQLDev PM on Apr 24, 2013 10:43 AM

Example storing data in the default schema with a Web Dynpro application

Hi,
is there any example or tutorial for storing data in the default schema with a Web Dynpro application via SQLJ or Hibernate by using the default DataSource?
Thanks for Help,
Dirk

Hi,
When you create the TAB-Strip object you should be able to set the default displayed TAB against the properties of the TAB-Strip.
Gareth.

How to create Default Schema from within the application

Hi friends
I am creating users using the following within my application using this syntax
BEGIN
APEX_UTIL.CREATE_USER
(:P124_USER_ID, :P124_USER_NAME,:P124_USER_FIRST_NAME,:P124_USER_LAST_NAME,' ',:P124_USER_EMAIL_ID,'xxxx');
END;
The default workspace for the user is set as blanks. I would like to set it to be the default workspace as per the current logged in user.
Can you help me with the syntax for this
thank you in advance
Laxmi

Laxmi,
The subject of the post is "How to create Default Schema from within the application".
But your question asks how to set the "default workspace" for a newly created user.
Those are different questions and not the ones I think you need answered.
Let me answer this question "How can you set the default schema for an account when creating the account and set it to the same value used for the default schema attribute of the administrator account used to authenticate to the currently running application?".
In the apex_util.create_user call use named parameter notation and fetch the information about the currently logged-in user first, e.g.,declare
l_workspace               varchar2(256);
l_user_name               varchar2(256);
l_first_name              varchar2(256);
l_last_name               varchar2(256);
l_web_password            varchar2(256);
l_email_address           varchar2(256);
l_start_date              varchar2(256);
l_end_date                varchar2(256);
l_employee_id             varchar2(256);
l_allow_access_to_schemas varchar2(256);
l_person_type             varchar2(256);
l_default_schema          varchar2(256);
l_groups                  varchar2(256);
l_developer_role          varchar2(256);
l_description             varchar2(256);
begin
apex_util.fetch_user (
p_user_id                  => apex_util.get_current_user_id,
p_workspace                => l_workspace,
p_user_name                => l_user_name,
p_first_name               => l_first_name,
p_last_name                => l_last_name,
p_web_password             => l_web_password,
p_email_address            => l_email_address,
p_start_date               => l_start_date,
p_end_date                 => l_end_date,
p_employee_id              => l_employee_id,
p_allow_access_to_schemas => l_allow_access_to_schemas,
p_person_type              => l_person_type,
p_default_schema           => l_default_schema,
p_groups                   => l_groups,
p_developer_role           => l_developer_role,
p_description              => l_description);
apex_util.create_user(
p_user_id        => :P124_USER_ID,
p_user_name      => :P124_USER_NAME,
p_first_name     => :P124_USER_FIRST_NAME,
p_last_name      => :P124_USER_LAST_NAME,
p_email_address => :P124_USER_EMAIL_ID,
p_web_password   => 'xxxx',
p_default_schema => l_default_schema);
end;Scott

Accessing tables in other than default schema.

Hi Experts,
I am using an Enterprise Bean (Stateless) that uses Common JDBC
to connect to the Java Schema of the WAS. I have created a
DataSource alias (created on Default Datasource) and using it for connection.
My requirement is to <b>get a list of all tables created in the Default schema</b>.
But when I use DatabaseMetadta.getTables() method, for this type of connection
it throws out the following exception:
<b>java.lang.UnsupportedOperationException: Method getTables() not supported by Common JDBC</b>
I have even tried using the query "Select * from USER_TABLES", but with this one,
an SQL Exception is thrown saying:
<b>com.sap.sql.log.OpenSQLException: The SQL statement "SELECT "TABLE_NAME" FROM "USER_TABLES"" contains
the semantics error[s]: table "USER_TABLES" unknown</b>
Please tell my how can I use tables in other than the default schema.
Regards,
Alka.

Hi Alka,
from your post, it is not entirely clear to me what you are atempting to do.
1) Do you need help with accessing tables in a non-default schema?
2) Do you want to determine all tables in the default schema?
If 1), please follow the hints given by Vladimir Pavlov.
If 2), currently, the method DatabaseMetaData.getTables() is unfortunately not supported in Open SQL/JDBC. We are currently preparing a new download of the NetWeaver Java EE 5 edition. In this version, the getTables() method will be supported.
Or do you just want to check for the existence of a specific database table in the default schema?
I hope this helps,
Best regards,
Adrian

Oracle Default Schema?

Hi Folks,
Can you please help in finding whether the below given schemas belong to default schemas?
1.Oracle 9i
Schema: ENTRDBA
2.Oracle 11GR2
Schema: BSCHLANDER, PWELLINSKI
Thanks
KSG

KSG wrote:
Hi Folks,
Can you please help in finding whether the below given schemas belong to default schemas?
1.Oracle 9i
Schema: ENTRDBA
2.Oracle 11GR2
Schema: BSCHLANDER, PWELLINSKI
I think that they are names picked up based on someone's initial and last names and are not the shipped schemas which come with the database.
Aman....

Confused about the default schema

Hi,
I am a little bit confused about the schema concept.
I want to create a new schema called APP and then create several users and roles based on the schema APP. The default schema for the users should be APP achema.
How can I make the schema APP the default schema for the new users that I am creating?
I feel that there are some schema design concepts that I have to learn. Is there any resource on the internet that I can read and learn more about oracle schema design best practices?
Any help would be appreciated,
Ali

A schema holds object definitions, and in the case of table & index objects the schema also holds the data.
A user owns the schema.
Therefore the user 'owns the definitions (including any functions, procedures, sequences, tabels, etc.)
Other users may be granted access to some, or all, of the objects in a schema. This is done through the 'GRANT ...' command. For example, consider the following steps:
1) create user app_owner
2) create table object test owned by the app_owwner
3) create user app_user
4) grant select, update, insert and delete on app_owner's test table to app_user
5) add synonyms to avoid needing to qualify the table's schema name.
done as follows:
oracle@fuzzy:~> sqlplus system
SQL*Plus: Release 10.2.0.1.0 - Production on Mon Apr 3 20:07:32 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Enter password:
Connected to:
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
Create the app owner userid. Note there is no need to ever log in to that user, even to create tables.
SQL> create user app_owner
2 identified by xyz
3 account lock
4 quota unlimited on users
5 default tablespace users
6 temporary tablespace temp;
User created.
Creating objects in a schema can be done by providing the schema name, or by switching schema in newer versions of Oracle
SQL> create table app_owner.test ( t number );
Table created.
Create a userid that will access the table. Set that userid up to access the database and (for future) give it the capability to create it's own synonyms
SQL> create user app_user
2 identified by xyz
3 temporary tablespace temp;
User created.
SQL> grant create session to app_user;
Grant succeeded.
SQL> grant create synonym to app_user;
Grant succeeded.
Now give the user access to the objects
SQL> grant select, update, insert, delete on app_owner.test to app_user;
Grant succeeded.
Let's test it out. Insert by qualifying the schema name on the object, then create a synonym to avoid using schema, and try it all using the synonym
SQL> connect app_user/xyz
Connected.
SQL> insert into app_owner.test values (4);
1 row created.
SQL> create synonym test for app_owner.test;
Synonym created.
SQL> insert into test values (3);
1 row created.
SQL> select * from test;
         T
         4
         3
SQL> Note that some people want to use PUBLIC grants and PUBLIC synonyms. This is a real bad idea if you want to ensure long term security of the data and want to host several different applications in the same Oracle instance.
This, and a whole lot more, is in the 'Concepts' manual for your version of the database at http://docs.oracle.com

Default Schema in HINUCALC0

Similar Messages

Maybe you are looking for