Setting password limits on SYS, SYSTEM, DBSNMP

We are having a security audit conducted and the auditors want us to set password limits for system accounts (SYS, SYSTEM, DBSNMP). They're asking us to set PASSWORD_LIFE_TIME, PASSWORD_GRACE_TIME, PASSWORD_REUSE_MAX, PASSWORD_REUSE_TIME. I have not been able to find any documentation that discusses the implications of doing this, if any. I'm wondering what will happen if these accounts become locked and/or expired because of invalid login attempts and not changing the password in time. I need something definitive one way or the other to show the customer. Please help!
Thanks,
Susan

Which operating System and which database release?
In AIX you can define password limit on OS level (using smitty for it) very straight forward.
You can also use OEM to do the password configuration which includes your assignment.
DN

Similar Messages

Default Connections (SYS, SYSTEM, DBSNMP, SYSMAN) Unavailable When SQLOpens

I installed the 32-Bit version of Oracle 11gR2 on my Windows 7 x64 system because the x64 version wouldn't install. I downloaded the 32-Bit version of SQL Developer with JRE, but when I run SQL Developer, the default connections (SYS, SYSTEM, DBSNMP, and SYSMAN) are not available.
I have entered the tnsnames directory on the Database:Advanced Preferences screen, and restarted my PC, but there's obviously something I'm missing.
Suggestions?
Thanks.

Hi Paul,
Once I connect to the Network Adapter, will the default ids show up?The SQL Developer Help says (and I believe this procedure works even if you cannot "connect" to the local database):
To create (automatically generate) a database connection for each unlocked user account in the Oracle database instance
on the local system, right-click the Connections node and select Create Local Connections. The connections are placed in
a folder named Auto-Generated Local Connections. Note that for these autogenerated connections (except for the one
named system-<database-name>), you will always be prompted for the password when you connect, and you cannot edit
the user name or password in the connection properties dialog box.Next, if this what you are actually asking, and you have a local database installed, then you need to make sure your database listener is up and running. Open a command line and try these commands:
lsnrctl statusIf it is not already started, either start it with
lsnrctl startor otherwise from your Windows Administrator Tools -> Services -> Oracle<home>Listener (right-click: Start)
Hope this helps,
Gary

RMAN Backup job fails after changing sys, system passwords

Hello Oracle community,
11.1g
After we changed the passwords for sys, system and sysman the backup jobs fails. this is my error log:
Recovery Manager: Release 11.1.0.7.0 - Production on Mo Aug 30 11:16:29 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-12532: TNS: Ungültiges Argument
RMAN>
Echo einstellen ein
RMAN> set command id to 'BACKUP_MEGALON.INT_083010111617';
Befehl wird ausgeführt: SET COMMAND ID
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: Fehler bei set Befehl auf 08/30/2010 11:16:29
RMAN-06171: Nicht bei Zieldatenbank angemeldet
RMAN> backup device type disk tag 'BACKUP_MEGALON.INT_083010111617' database;
Starten backup um 30.08.10
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: Fehler bei backup Befehl auf 08/30/2010 11:16:29
RMAN-06171: Nicht bei Zieldatenbank angemeldet
RMAN> backup device type disk tag 'BACKUP_MEGALON.INT_083010111617' archivelog all not backed up;
Starten backup um 30.08.10
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: Fehler bei backup Befehl auf 08/30/2010 11:16:29
RMAN-06171: Nicht bei Zieldatenbank angemeldet
RMAN> exit;
Recovery Manager abgeschlossen.
Ikrischer

Hello Tychos,
I am able to make a sqlplus connection, but your hint send me in the correct direction. I had a special character "@" in the password and I think that was the reason for my problems with RMAN.
Ikrischer

Oracle SYS/SYSTEM shared passwords

Unfortunately we have a requirement not to have the sys/system passwords shared even among the DBA staff. Someone mentioned an Oracle article which details not having shared passwords. The problem is that security perceives this issue as a threat. I have argued until I am blue in the face that these two accounts are needed by the dba team. Does anyone have any information on this subject to pass along? Things that worked and even those that didnt? The real issue comes into play when you start looking at cron jobs on the oracle account which have most of the privileged passwords visible.
Thanks!

You could argue that with me - a DBA - until you are blue in the face and you would still loose. You DO NOT need the sys and system accounts to do your job as a DBA.
Here is what we do...
1. create a role, or set of roles something like DBA_SENIOR, DBA_SECURITY, DBA_USERADMIN, etc. Give them all of the privileges they need for their specific jobs.
2. create user accounts for each DBA - we use externally identified but they need not be.
3. grant each DBA his appropriate role.
4. create a password file.
5. grant sysdba to the DBAs - so that they can become SYS on those times when it is the only way to do what needs to be done.
6. give sys and system impossible passwords.
7. DO NOT grant DBA role to anyone.
Now you have met the requirement and your dba's can do their jobs. And if you create scripts, then it is easy to make this routine for whenever you create a database.

View and change passwords for sys, system, sapr3

Dear All
1.I need to view the password the for account :
sys, system, sapr3
2. I need to know for how long passwords have not been changed?
. and how can i change these passwords?
Any sugestions??
Regards
Rajesh
Edited by: rajesh sharma on Oct 15, 2008 1:51 PM

Hi Rajesh,
1.I need to view the password the for account :
sys, system, sapr3
Its not possible to view the password, password is always encrypted format stored, if the default has not been changed for SYS, SYSTEM then their password are CHANGE_ON_INSTALL and MANAGER respectively.
2. I need to know for how long passwords have not been changed?
. and how can i change these passwords?
For knowing what date they were changed last,
- connect /as sysdba;
- SQL> select name, ptime from user$;
ptime will give you the last password change date.
you can view at what date the password will be expired by
- select username, account_status, expiry_date from dba_users;
change the password by brtools menu options or directly by chpass.
http://help.sap.com/saphelp_nw70/helpdata/EN/4f/c3883989676778e10000000a11402f/frameset.htm
Note -
Always recommended to use brtools for changing password rather than using the sql commands.
Regards,
Debasis.
Edited by: Debasis Sahoo on Oct 16, 2008 1:09 AM

Change the SYS & SYSTEM Oracle passwords with BRTOOLS, any concerns ?

Hello, I would like to change both the SYS and SYSTEM Oracle passwords with BRTOOLS :
(1) Can I use BRTOOLS to change them, or, I have to change them through SQLPlus ?
(2) Any concerns, will this password change affect my SAP normal operations ?
(3) Do I need to re-start the whole SAP UNIX system when I complete the password changing ?
(4) Or changing these 2 passwords is totally an Oracle RDBMS issue, it will not have any effect on SAP ?

But I failed. I was going to change the password of SYSTEM, but why SAP asked me to enter the password of SAPDEV ?
Why ? OK, then I entered the SAPDEV password (it is the same as SYSTEM's old password).
Then, I called SQLPlus and entered login name : SYSTEM, but why its correct password was still the old one, the new one failed. Why ?
I just wanted to change the password of SYSTEM, why it was related to SAPDEV ?
Here is the screen message :
BR*Tools main menu
1 = Instance management
2 - Space management
3 - Segment management
4 - Backup and database copy
5 - Restore and recovery
6 - Check and verification
7 - Database statistics
8 - Additional functions
9 - Exit program
Standard keys: c - cont, b - back, s - stop, r - refr, h - help
BR0662I Enter your choice:
8
BR0280I BRTOOLS time stamp: 2010-01-15 10.22.46
BR0663I Your choice: '8'
BR0280I BRTOOLS time stamp: 2010-01-15 10.22.46
BR0656I Choice menu 2 - please make a selection
Additional BR*Tools functions
1 = Show profiles and logs
2 - Clean up DBA logs and tables
3 - Adapt NEXT extents
4 - Change password of database user
5 - Create/change synonyms for DBA tables
6 - Reset program status
Standard keys: c - cont, b - back, s - stop, r - refr, h - help
BR0662I Enter your choice:
4
BR0280I BRTOOLS time stamp: 2010-01-15 10.23.14
BR0663I Your choice: '4'
BR0280I BRTOOLS time stamp: 2010-01-15 10.23.14
BR0657I Input menu 59 - please check/enter input values
BRCONNECT options for changing password of database user
1 - BRCONNECT profile (profile) ............... [initDEV.sap]
2 - Database user/password (user) ............. [/]
3 ~ Database owner to change password (owner) . []
4 - Message language (language) ............... [E]
5 - BRCONNECT command line (command) .......... [-p initDEV.sap -l E -f chpass]
Standard keys: c - cont, b - back, s - stop, r - refr, h - help
BR0662I Enter your choice:
2
BR0280I BRTOOLS time stamp: 2010-01-15 10.28.56
BR0663I Your choice: '2'
BR0280I BRTOOLS time stamp: 2010-01-15 10.28.56
BR0681I Enter string value for "user" [/]:
SYSTEM
BR0280I BRTOOLS time stamp: 2010-01-15 10.29.08
BR0683I New value for "user": 'SYSTEM'
BR0263I Enter password for database user 'SYSTEM' (maximum 8 characters):
BR0280I BRTOOLS time stamp: 2010-01-15 10.29.32
BR0657I Input menu 59 - please check/enter input values
BRCONNECT options for changing password of database user
1 - BRCONNECT profile (profile) ............... [initDEV.sap]
2 - Database user/password (user) ............. [SYSTEM/*******]
3 ~ Database owner to change password (owner) . []
4 - Message language (language) ............... [E]
5 - BRCONNECT command line (command) .......... [-p initDEV.sap -l E -f chpass]
Standard keys: c - cont, b - back, s - stop, r - refr, h - help
BR0662I Enter your choice:
c
BR0280I BRTOOLS time stamp: 2010-01-15 10.29.41
BR0663I Your choice: 'c'
BR0259I Program execution will be continued...
BR0291I BRCONNECT will be started with options '-p initDEV.sap -l E -f chpass'
BR0280I BRTOOLS time stamp: 2010-01-15 10.29.41
BR0670I Enter 'c[ont]' to continue, 'b[ack]' to go back, 's[top]' to abort:
c
BR0280I BRTOOLS time stamp: 2010-01-15 10.29.49
BR0257I Your reply: 'c'
BR0259I Program execution will be continued...
BR0801I BRCONNECT 6.40 (39)
BR0280I BRCONNECT time stamp: 2010-01-15 10.29.52
BR0263I Enter password for database user 'SAPDEV' (maximum 8 characters):
BR0280I BRCONNECT time stamp: 2010-01-15 10.34.58
BR0263I Reenter password for database user 'SAPDEV' (maximum 8 characters):
BR0280I BRCONNECT time stamp: 2010-01-15 10.35.57
BR0482W The passwords entered must be identical
BR0280I BRCONNECT time stamp: 2010-01-15 10.35.57
BR0256I Enter 'c[ont]' to continue, 's[top]' to cancel BRCONNECT:
c
BR0280I BRCONNECT time stamp: 2010-01-15 10.36.31
BR0257I Your reply: 'c'
BR0259I Program execution will be continued...
BR0280I BRCONNECT time stamp: 2010-01-15 10.36.31
BR0263I Enter password for database user 'SAPDEV' (maximum 8 characters):
BR0280I BRCONNECT time stamp: 2010-01-15 10.37.03
BR0263I Reenter password for database user 'SAPDEV' (maximum 8 characters):
BR0280I BRCONNECT time stamp: 2010-01-15 10.38.08
BR0482W The passwords entered must be identical
BR0280I BRCONNECT time stamp: 2010-01-15 10.38.08
BR0256I Enter 'c[ont]' to continue, 's[top]' to cancel BRCONNECT:
BR0280I BRCONNECT time stamp: 2010-01-15 10.38.11
BR0256I Enter 'c[ont]' to continue, 's[top]' to cancel BRCONNECT:
c
BR0280I BRCONNECT time stamp: 2010-01-15 10.38.14
BR0257I Your reply: 'c'
BR0259I Program execution will be continued...
BR0280I BRCONNECT time stamp: 2010-01-15 10.38.14
BR0263I Enter password for database user 'SAPDEV' (maximum 8 characters):
BR0280I BRCONNECT time stamp: 2010-01-15 10.38.16
BR0263I Reenter password for database user 'SAPDEV' (maximum 8 characters):
BR0280I BRCONNECT time stamp: 2010-01-15 10.38.18
BR0829I Password changed successfully in database for user SAPDEV
BR0830I Password changed successfully in table OPS$DEVADM.SAPUSER for user SAPDEV
BR0280I BRCONNECT time stamp: 2010-01-15 10.38.18
BR0803I BRCONNECT completed successfully with warnings
BR0292I Execution of BRCONNECT finished with return code 1
BR0668I Warnings or errors occurred - you can continue to ignore them or go back to repeat the last action
BR0280I BRTOOLS time stamp: 2010-01-15 10.38.18
BR0670I Enter 'c[ont]' to continue, 'b[ack]' to go back, 's[top]' to abort:
c
BR0280I BRTOOLS time stamp: 2010-01-15 10.38.44
BR0257I Your reply: 'c'
BR0259I Program execution will be continued...
BR0280I BRTOOLS time stamp: 2010-01-15 10.38.44
BR0656I Choice menu 2 - please make a selection
Additional BR*Tools functions
1 = Show profiles and logs
2 - Clean up DBA logs and tables
3 - Adapt NEXT extents
4 + Change password of database user
5 - Create/change synonyms for DBA tables
6 - Reset program status
Standard keys: c - cont, b - back, s - stop, r - refr, h - help
BR0662I Enter your choice:

Silent install of Ora9.2+DB: how to avoid (sys, system) password dialog?

Hi,
I used a modified personal.rsp and dbca.rsp to install Oracle 9.2 personal and a DB on Win2k/XPp, but despite the "-slient" flag, I get a dialog prompting for the sys, system passwords in the end.
How can I avoid this? Are there (undocumented) parameters for dbca.rsp which allow to avoid the dialog?
Thanks for any help.

Hi,
Use below command and you no need to pass userid/password. It works for all versions.
imp \'/ AS SYSDBA\' full=Y CONSTRAINTS=Y FILE=V:\exp_test20090729.dmp
Regards,
Satishbabu Gunukula
http://oracleracexpert.blogspot.com
Edited by: Satishbabu Gunukula on Aug 10, 2009 4:34 PM

Password for Oracle user , sys , system , saprpd

Hi All ,
I just join a new company as sys admin . I tried to search password for Oracle user sys , system and saprd in my company password file . Those users password are not stored.
Am I supposed to know those oracle user password ? If yes , Can I find them in my Unix system or sap application ?
Please help !
Felix

It is not possible to determine the passwords if you don't know them. But perhaps note 562863 and the described default passwords are useful. Furthermore you can always change passwords if you have SYSDBA privilege using "alter user ... identified by ..." or "brconnect -f chpass".
Regards
Martin

What is step reset sys,system,sysman password

Dear Expert,
Due to security issue, company request to change sys,system,sysman and ASM sys password running on RAC DB 11.2.0.3
What is a proper way to change above power user login and does it efffect ORACLE ENTERPRISE MANAGE 11g user login. Please advise
Regard
LIANG

1.recreate the password file to reset sys password for DB/ASM
2.for system ,you may change it by alter user system identified by .....
3.check metalink...for sysman How to Change the Password of SYSMAN User in 10g and 11g Grid Control? [ID 270516.1]
Please close the thread after marking it helpful or correct if you feel you have the answer and keep the Oracle forum clean.
https://forums.oracle.com/forums/ann.jspa?annID=885
Thanks
Kuljeet Pal Singh

Set Tolerance Limits

In this step, you specify the tolerance limits for each tolerance key for each company code.
When processing an invoice, the R/3 System checks each item for variances between the invoice and the purchase order or goods receipt. The different types of variances are defined in tolerance keys.
The system uses the following tolerance keys to check for variances:
u2022     AN: Amount for item without order reference
If you activate the item amount check, the system checks every line item in an invoice with no order reference against the absolute upper limit defined.
u2022     AP: Amount for item with order reference
If you activate the item amount check, the system checks specific line items in an invoice with order reference against the absolute upper limit defined. Which invoice items are checked depends on how you configure the item amount check.
u2022     BD: Form small differences automatically
The system checks the balance of the invoice against the absolute upper limit defined. If the upper limit is not exceeded, the system automatically creates a posting line called Expense/Income from Small Differences, making the balance zero and allowing the system to post the document.
u2022     BR: Percentage OPUn variance (IR before GR)
The system calculates the percentage variance between the following ratios: quantity invoiced in order price quantity units : quantity invoiced in order units and quantity ordered in order price quantity units : quantity ordered in order units. The system compares the variance with the upper and lower percentage tolerance limits.
u2022     BW: Percentage OPUn variance (GR before IR)
The system calculates the percentage variance between the following ratios: quantity invoiced in order price quantity units: quantity invoiced in order units and goods receipt quantity in order price quantity units : goods receipt quantity in order units. The system compares the variance with the upper and lower percentage limits defined.
u2022     DQ: Exceed amount: quantity variance
If a goods receipt has been defined for an order item and a goods receipt has already been posted, the system multiplies the net order price by (quantity invoiced - (total quantity delivered - total quantity invoiced)).
If no goods receipt has been defined, the system multiplies the net order price by (quantity invoiced - (quantity ordered - total quantity invoiced)).
The system compares the outcome with the absolute upper and lower limits defined.
This allows relatively high quantity variances for invoice items for small amounts, but only small quantity variances for invoice items for larger amounts.
You can also configure percentage limits for the quantity variance check. In this case, the system calculates the percentage variance from the expected quantity, irrespective of the order price, and compares the outcome with the percentage limits configured.
The system also carries out a quantity variance check for planned delivery costs.
u2022     DW: Quantity variance when GR quantity = zero
If a goods receipt is defined for an order item but none has as yet been posted, the system multiplies the net order price by (quantity invoiced + total quantity invoiced so far).
The system then compares the outcome with the absolute upper tolerance limit defined.
If you have not maintained tolerance key DW for your company code, the system blocks an invoice for which no goods receipt has been posted yet. If you want to prevent this block, then set the tolerance limits for your company code for tolerance key DW to Do not check.
u2022     KW: Variance from condition value
The system calculates the amount by which each delivery costs item varies from the product of quantity invoiced * planned delivery costs/ planned quantity. It compares the variance with the upper and lower limits defined (absolute limits and percentage limits).
u2022     LA: Amount of blanket purchase order
The system calculates the sum of the value invoiced so far for the order item and the value of the current invoice and compares it with the value limit of the purchase order. It then compares the difference with the upper percentage and absolute tolerances defined.
u2022     LD: Blanket purchase order time limit exceeded
The system determines the number of days by which the invoice is outside the planned time interval. If the posting date of the invoice is before the validity period, the system calculates the number of days between the posting date and the start of the validity period. If the posting date of the invoice is after the validity period, the system calculates the number of days between the posting date and the end of the validity period. The system compares the number of days with the with the absolute upper limit defined.
u2022     PP: Price variance
The system determines by how much each invoice item varies from the product of quantity invoiced * order price. It then compares the variance with the upper and lower limits defined (absolute limits and percentage limits).
When posting a subsequent debit/credit, the system first checks if a price check has been defined for subsequent debits/credits. If so, the system calculates the difference between (value of subsequent debit/credit + value invoiced so far) / quantity invoiced so far * quantity to be debited/credited and the product of the quantity to be debited/credited * order price and compares this with the upper and lower tolerance limits (absolute limits and percentage limits).
u2022     PS: Price variance: estimated price
If the price in an order item is marked as an estimated price, for this item, the system calculates the difference between the invoice value and the product of quantity invoiced * order price and compares the variance with the upper and lower tolerance limits defined (absolute limits and percentage limits).
When posting a subsequent debit/credit, the system first checks whether a price check has been defined for subsequent debits/credits, If so, the system calculates the difference between (value of subsequent debit/credit + value invoiced so far) / quantity invoiced so far * quantity to be debited/credited and the product quantity to be debited/credited * order price. It then compares the variance with the upper and lower tolerance limits defined (absolute limits and percentage limits).
u2022     ST: Date variance (value x days)
The system calculates for each item the product of amount * (scheduled delivery date - date invoice entered) and compares this product with the absolute upper limit defined. This allows relatively high schedule variances for invoice items for small amounts, but only small schedule variances for invoice items for large amounts.
u2022     VP: Moving average price variance
When a stock posting line is created as a result of an invoice item, the system calculates the new moving average price that results from the posting. It compares the percentage variance of the new moving average price to the old price using the percentage tolerance limits defined.
Variances are allowed within predefined tolerance limits. If a variance exceeds a tolerance limit, however, the system issues a message informing the user. If an upper limit (except with BD and VP) is exceeded, the invoice is blocked for payment when you post it. You must then release the invoice in a separate step. If the tolerance limit for BD is breached, the system cannot post the invoice.
Note that if you set all limits for a tolerance key to Do not check, the system does not check that tolerance limit. Therefore any variance would be accepted. This does not make sense particularly in the case of the tolerance key Form small differences automatically.
Activities
Configure the tolerance limits for the individual tolerance keys.
             Lower limit             Upper limit
             Absolute    Percentage Absolute    Percentage
AN          -           -           X           -
AP          -           -           X           -
BD          X           -           X           -
BR          -           X           -           X
BW          -           X           -           X
DQ          -           -           X           -
DW          -           -           X           -
KW          X           X           X           X
LA          -           -           X           X
LD          X           -           X           -
PP          X           X           X           X
PS          X           X           X           X
ST          -           -           X           -
VP          -           X           -           X

1) "Powered by Jive Software" ....
2) 我看看有没有机会通过什么渠道反映这个问题..

Set password for code / no display

hi all
i have written some report 'z1'. i don't want other to view my code . is there any way to set password for my code ? is there any other solution.
thanks
bala

If you hide the source as described in this posting, the program cannot be regenerated. If any dictionary object that your program uses gets changed, then the system will mark your program as needing to be regenerated. The next time it is executed, the system will attempt to regenerate, will fail to find the source code and therefore your program is unusable.
You may also lose the ability to debug the program.
You may also lose the ability for the dump manager to point out the line of code where a failure occurred.
As long as you are okay with these restrictions, then go for it and let us know how it goes.

Setting password for Autologon Default user in registry

Hi friends
I don't know is this the right forum to ask this question:
me along with my colleges are doing some exercises to improve our learnings, so we have setup a test lab which has a test DC & 10 test client computers running windows 8.1
as we know, when computers join to domain, the item related to Autologon is removed from netplwiz.
I know that to be able to use Autlogon feature in joined computers, we can restore the above item by creating the required items via any method like the following:
$regpath="HKLM:\software\Microsoft\Windows NT \CurrentVersion\Winlogon "
New-ItemProperty -path $regpath -Name AutoAdminLogon -PropertyType String -Value "1" -Force
$regpath="HKLM:\software\Microsoft\Windows NT\CurrentVersion\Winlogon"
New-ItemProperty -path $regpath -Name DefaultDomainName -PropertyType String -Value %USERDOMAIN% -Force
$regpath="HKLM:\software\Microsoft\Windows NT \CurrentVersion\Winlogon "
New-ItemProperty -path $regpath -Name DefaultUsername -PropertyType String -Value “administrator” -Force
the above lines provide required info for Autologon, except the password of the user.because of this we have to sit at every test client & open up netplwiz & manually enter the password for default Autologon user.
is it possible to define the password for this user as well in the registry? so that we add it to above lines & save them as a PS script & run that PS script on our test systems so that we don't have to sit at each test client
& manually set password for default user for Autologon.
I mean I need when we power on our test clients, they automatically login via domain administrator credentials & be ready to use
thanks

The documentation for this might prove helpful:
http://technet.microsoft.com/en-us/library/cc939702.aspx
According to the above:
If you disable automatic logon by setting the value of AutoAdminLogon to 0, delete the value of
DefaultPassword, which is stored and displayed in the registry editor in plain, unencrypted text.
(Hint: I found this very quickly by searching for "autoadminlogon" using a search engine.)
-- Bill Stewart [Bill_Stewart]

How to set password in obiee delivery content reports (pdf format)

Hi
Dear All
i Need your help on the Obiee !
i hvae one Requirement how to set password in obiee delivery content (pdf format) its possible. what are the things i to do
Kindly Advice me
Advance Thanks
satya

933154 wrote: My profile says PDF, config, report, settings says PDF and I get an Excel when I run screening reports. Very odd.You may want to make sure that the file where the system setting gets stored can be updated. In your <Intradoc_Dir>\urm\data\reportpublisher\config\config.hda file, there is a result set named "RPAdminConfigInfo". The third column of that result set should match the value being shown on the configuration settings page. I've changed the format value in the UI, and this file gets updated (and thus I'm getting my screening reports in the format specified in this config file.)
933154 wrote: Also, I wasn't clear on the second part of the question. The Screening Reports appear to use the template INTERNALITEMDETAILRPTTEMPLATE. Is that configuration set somewhere? Is there any way to have the screening reports use a different template or is changing that template the only way to change the screening report layout?Templates are not configurable in that respect - the template name values being called for a service are hardwired in the code (you'd need to override in a component - just not worth the hassle). I'd either edit the existing rtf file, or just check in a new revision to the existing one if the differences are that profound. You'd still need to conform to the BI Publisher standards/methodology in either case.

How to set Password protection in excel using java

Dear all,
I have no idea to write a java program that how to set password protection in excel. Please give me some solution using java tools. Thank a lot!
Regards,
kzyo

Dear Bamkin ,
I used your code and paste it in my program. The error is as the follow:
Code:
     stmnt = c.createStatement();
               String query = "select StudentNumber, Email, New_Email_Address from [Sheet1$] where Len(New_Email_Address) > 0";
               System.out.println(query);
               rs = stmnt.executeQuery(query);
               stmnt.executeUpdate("SET PASSWORD=PASSWORD('Test')");
Error:
(Remark: Invalid SQL statement)
java.sql.SQLException: [Microsoft][ODBC Excel Driver] ��I SQL ��q��G�a��'DELETE'�A'INSERT'�A'PROCEDURE'�A'SELECT' �� 'UPDATE' �B
     at sun.jdbc.odbc.JdbcOdbc.createSQLException(JdbcOdbc.java:6958)
     at sun.jdbc.odbc.JdbcOdbc.standardError(JdbcOdbc.java:7115)
     at sun.jdbc.odbc.JdbcOdbc.SQLExecDirect(JdbcOdbc.java:3111)
     at sun.jdbc.odbc.JdbcOdbcStatement.execute(JdbcOdbcStatement.java:338)
     at sun.jdbc.odbc.JdbcOdbcStatement.executeUpdate(JdbcOdbcStatement.java:288)
     at hk.gov.edb.util.ExcelHandle.updateNewEmail(ExcelHandle.java:414)
     at hk.gov.edb.core.AppMain.doUpdate(AppMain.java:369)
     at hk.gov.edb.core.AppMain$7.construct(AppMain.java:584)
     at hk.gov.edb.util.SwingWorker$2.run(SwingWorker.java:127)
     at java.lang.Thread.run(Thread.java:595)

Set Tolerance Limits for Price Variance when PO-based Purch.Requisition

We must garanty that Price from Purch.Requisition will be the same at PO.
IF some variance occur a error messag must be sent to user and PO could not be saved.
I found at customzing under SPRO > Materials Management > Purchasing > Purch.requisition > Set Tolerance Limits for Price Variance .
Reading the help of customizing it mean the system consists what we need..
I have created tolerance limit NB, and set limits for all checks as 0,01.
When I will activate messages as recommended on help no messages 601 and 602 have the text that guide us to correctly setting.
The help mention that after create tolerance limit we must set this tolerance by document type..but I didnt find this field at customzing
Does anyone can help me ?
See the help on customizing below
Set Tolerance Limits for Price Variance
In this step, you can define percentage-based and value-based (absolute) tolerance limits for price variances between purchase orders and purchase requisitions. Variance types are mapped out in the SAP system by tolerance keys.
You define the tolerance limits for each tolerance key and assign your tolerance key to the document types for purchase requisitions. The tolerance limit then applies for all documents of this document type.
When processing a purchase order, the system checks whether the unit price of a purchase order item differs from the unit price of a purchase requisition item. If you have configured, activated and defined tolerance limits in document types, variances are permitted in the tolerance limits. If the variance exceeds the tolerance limit, the system issues a warning. If you have defined a percentage-based and a value-based absolute tolerance limit, the strictest of the two variances will apply for this check.
Note
You can determine whether the system messages (601 and 602) appear as warnings or error messages in step "Define Attributes of System Messages".
To do this, go to the Materials Management IMG and choose Purchasing -> Environment Data -> Define Attributes of System Messages.
Requirements
The tolerance key must be defined in step Define Tolerance Key.
Activities
1. Define tolerance limits for each tolerance key.
2. Define the tolerance key in step Define Document Types.
Thx and best regards,
Ale

HI
SET TOLERANCE LIMITS FOR PURCHASE REQUISITION UNDER THE DEFINE DOCUMENTS FOR PR
AFTER SETTING TOLERANCE LIMITS WHILE CREATING PURCHASE U WILL GET BASED ON TOLERANCE LIMITS THERE FOUR WAYS TO SET TOLERANCE LITS
1
ABSOLUTE VALUE
2
PERCANTAGE
3
TOTAL PO VALUE
4
QUANITY BASED PRICE PER UNIT
OK BYE

Setting password limits on SYS, SYSTEM, DBSNMP

Similar Messages

Maybe you are looking for