Alter System Currency Value

Dear all,
Is it possible to extract the exchange rate from a user-defined field in the row details of an invoice document to compute for the system currency value of the invoice journal entries, instead of using the rate maintained in the Exchange Rates and Indexes table? Please refer to the desired journal entries below.
To Illustrate:
   Exchange Rate Maintained in SAP B1 Table = 44.20
   Basic Initialization Settings:
             Local Currency = PHP
             System Currency = USD
Exchange Rate Maintained in User-defined Field (INV1) = 44.00
Invoice Details:
      Transaction Currency = Local Currency (PHP)
      BP Currency = Multicurrency
      Doc Total = PHP 30,000
     Journal Entries Posted from AR Invoice:
                                                                  Debit                                Debit (System Currency)
      BP Control Account                          PHP 30000                                 678.73 (PHP 30000/ 44.20)
       _Desired Journal Entries to be Posted from AR Invoice:_
                                                                 Debit                                 Debit (System Currency)
      BP Control Account                          PHP 30000                                 681.82 (PHP 30000 /44 )
Your feedback shall be very much appreciated.
Thank you,
Dona

It may be possible to achieve this using a crystal report to recalculate the vaues. My question though is why is this necessary?

Similar Messages

"Alter system set command" in a RAC database!!

Hi, all.
The database is (10.2.0.2.0) 2- node RAC database on 32-bit windows 2003
EE SP1.
I issued the following command on Node 1 database.
--> Alter system set db_block_buffers= xxx sid='rac1';
I was able to see "PE enqueue" in top 5 wait event section from an AWR report.
In addition, I was able to find "PZ99","PZ98" process dump file in BDUMP.
Soon later, I could find CKPT and DBWR hung.
Is there anyone who experienced this issue?
Thanks and Regards.
Message was edited by:
user507290

10.2.0.2 has some bug which is fixed 10.2.0.3
You check sequence cache. If it has less value, increase it to 10000.
select CACHE_SIZE from dba_sequences where SEQUENCE_OWNER='SYS' and SEQUENCE_NAME='AUDSES$';
SQL> alter sequence sys.audses$ cache 10000;
Ashok

Question about ALTER SYSTEM ARCHIVE LOG START

Good morning,
I'm trying (unsuccessfully) to get my database to be in archive log mode.
These are the steps I followed:
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 535662592 bytes
Fixed Size                  1375792 bytes
Variable Size             377487824 bytes
Database Buffers          150994944 bytes
Redo Buffers                5804032 bytes
Database mounted.
SQL> select log_mode from v$database;
LOG_MODE
ARCHIVELOG
SQL> show parameter log_archive_start;
NAME                                 TYPE        VALUE
log_archive_start                    boolean     FALSE
SQL> alter system archive log start;
System altered.
SQL> show parameter log_archive_start;
NAME                                 TYPE        VALUE
log_archive_start                    boolean     FALSE
SQL>I've gone thru that process twice but, I don't seem to be able to get the ARCH process to start. (newbie mistake I'm sure...)
Thank you for your help (again!),
John.

The parameter log_archive_start is no more needed John (as suggested already) and the best way to check the archive options is through the archive log list command.
[oracle@edhdr2p0-orcl oui]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Tue Aug 10 10:51:57 2010
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
SQL> archive log list
Database log mode              No Archive Mode
Automatic archival             Disabled
Archive destination            USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     11
Current log sequence           13
SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.
Total System Global Area 418484224 bytes
Fixed Size                  1336932 bytes
Variable Size             318769564 bytes
Database Buffers           92274688 bytes
Redo Buffers                6103040 bytes
Database mounted.
SQL> select process,status from V$archive_processes;
   PROCESS STATUS
         0 STOPPED
         1 STOPPED
         2 STOPPED
         3 STOPPED
         4 STOPPED
         5 STOPPED
         6 STOPPED
         7 STOPPED
         8 STOPPED
         9 STOPPED
        10 STOPPED
   PROCESS STATUS
        11 STOPPED
        12 STOPPED
        13 STOPPED
        14 STOPPED
        15 STOPPED
        16 STOPPED
        17 STOPPED
        18 STOPPED
        19 STOPPED
        20 STOPPED
        21 STOPPED
   PROCESS STATUS
        22 STOPPED
        23 STOPPED
        24 STOPPED
        25 STOPPED
        26 STOPPED
        27 STOPPED
        28 STOPPED
        29 STOPPED
30 rows selected.
SQL>
SQL> alter database archivelog;
Database altered.
SQL> alter database open;
archive log list;
Database altered.
SQL> Database log mode         Archive Mode
Automatic archival             Enabled
Archive destination            USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     11
Next log sequence to archive   13
Current log sequence           13
SQL>
SQL> select * from V$archive_processes where status <> 'STOPPED';
   PROCESS STATUS     LOG_SEQUENCE STAT
         0 ACTIVE                0 IDLE
         1 ACTIVE                0 IDLE
         2 ACTIVE                0 IDLE
         3 ACTIVE                0 IDLEHTH
Aman....

Question on alter system set cluster_database = true

11.2.0.2.0 windows 2008
doing a restore to a development RAC I noticed the following. I took the database out of cluster mode on one instance
alter system set cluster_database=false scope=spfile sid='PRD1';
shutdown, start up, do the restore, all good, I go to set cluster_Database=true but had issue instance would only start on one node, I reviewed my notes and found problem was when I set cluster_Database back to true I had typed
alter system set cluster_database=true scope=spfile sid='*';
instead of
alter system set cluster_database=true scope=spfile sid='PRD1';
So issue fixed.
I retested and confirmed '*' wont take. Ive seen many examples of '*' working online and I am sure I have used '*' many times so had just typed it off my head. Anyone explain? probably quotes or something.

Any chance there are multiple lines for cluster_database in the spfile ?I had thought maybe this, but confirmed no, it was a fresh build anyway that I was restoring to.
>
- Dump the spfile to a pfile ... edit ... recreate the spfile on all nodes.
>
Im not sure what this will achieve? the spfile is shared on the ASM.
>
As the cluster_database=true is a parameter to enable the RAC configuration. As you typed sid='*' it will try to enable the cluster_database parameter in all the instances(nodes) as it is RAC.
In your case as you did on a single node by specifiying the sid name it will work as it will look only for that sid and enable that particular node.
>
I find this hard to read but I think this misinterprets as well.
Thanks for the contribution. I think Ive found the solution
the asterisk doesnt apparently mean actually "all instances", from here
http://www.comp.dit.ie/btierney/oracle11gdoc/rac.111/b28254/admin.htm#BCEFICEE
and
"Setting SPFILE Parameter Values for Oracle Real Application Clusters"
-- this is a good example of what happened to me
>
*.OPEN_CURSORS=500
prod1.OPEN_CURSORS=1000
Note:
The value before the dot in an SPFILE entry identifies the instance to which the particular parameter value belongs. When an asterisk precedes the dot, the value is applied to all instances that do not have a subsequent, individual value listed in the SPFILE.
For the instance with the Oracle system identifier (SID) prod1, the OPEN_CURSORS parameter is set to 1000 even though it has a database-wide setting of 500. Parameter file entries that have the asterisk (*) wildcard character only affect the instances without an instance-specific entry. This gives you control over parameter settings for instance prod1. These two types of settings can appear in any order in the parameter file.
If another DBA runs the following statement, then Oracle updates the setting on all instances except the instance with SID prod1:
ALTER SYSTEM SET OPEN_CURSORS=1500 sid='*' SCOPE=MEMORY;
>
so when I was on node 1 and ran it for *, I was setting it for all the nodes except the node I was on which holds true from what Ive seen. I'll remember that one.

Query on ALTER SYSTEM SET

Hi,
I was under impression that
"PFILE has the limitation to change the initialization parameters dynamically.If any init parameter is to be changed,we can edit the pfile and the parameter changes will come into effect with the next reboot of the system.
To overcome this limitation,Oracle has come up with the concept of SPFILE ,where in the initialization parameters can be changed dynamically using ALTER SYSTEM SET statement."
But,today I started my test database using PFILE and executed the following command to change the memory_target parameter from 300M to 290M.
ALTER SYSTEM SET memory_target=290M;
And to my surprise,this statement executed fine without any errors and memory_target parameter has been set to the new value(of course,in memory).
Isn't it changing the init parameters dynamically using PFILE itself??
Please clarify my doubt and correct my understanding.
Regards,
Bharath

bharathDBA wrote:
Hi,
I was under impression that
"PFILE has the limitation to change the initialization parameters dynamically.If any init parameter is to be changed,we can edit the pfile and the parameter changes will come into effect with the next reboot of the system.
To overcome this limitation,Oracle has come up with the concept of SPFILE ,where in the initialization parameters can be changed dynamically using ALTER SYSTEM SET statement."
But,today I started my test database using PFILE and executed the following command to change the memory_target parameter from 300M to 290M.
ALTER SYSTEM SET memory_target=290M;
And to my surprise,this statement executed fine without any errors and memory_target parameter has been set to the new value(of course,in memory).
Isn't it changing the init parameters dynamically using PFILE itself??
Please clarify my doubt and correct my understanding.
Regards,
Bharath
You have a wrong interpenetration about the genesis of the SPFILE. Yes it is a binary file and all that but remember, its not the SPFILE that makes a parameter dynamic or a PFILE that makes it static but it's the very nature of the parameter itself that makes it happen. Yes, the difference in the PFILE and SPFILE parameter would be evident when you would change a dynamic parameter and would give a bounce to the db. Since teh PFILE wasn't updated (its a text file so has to be updated manually) , with the next restart, the parameter would take the same value as it has in the PFILE. But with the SPFILE, depending on what you have set in the SCOPE, the parameter would behave accordingly.
HTH
Aman....

Set currency value of pricing element in condition tab - VA21

Hi GURU,
Would you please help to identify the way to set the following currency values for pricing element in condition tab when creating system quote by va21:
Rate unit (RV61A-KOEIN)
SD document currency (KOMK - WAERK)
Thanks in advanced,
Regards,
Thang

Solved

Alter system set events Question

Version 10202 on AIX
sql> alter system set events '4030 trace name heapdump level 536870917; name errorstack level 3';
Questions about this statement..
what this command is doing, i guess creating tracefile for event 4030...& the location of trace file would be the current direcotry?
& how to setup same kind of event trace for other events, any tips....& what to check in tracefile for problem?

The values for level I have record are 1, 2, 3, 8, and 32 so I am guessing the number shown is the address of a specific heap to be dumped. The address of a heap would potentially change with a change in the shared pool storage parameters. Where did you get the address value?
The dump should go to the user background dump destination and not the current directory.
PS - if you have metalink look at document: #218105.1 Introduction to ORACLE Diagnostic EVENTS
HTH -- Mark D Powell --
Message was edited by: MDP add PS to Metalink Doc
mpowel01

ALTER SYSTEM SET SGA_TARGET

Hi,
in 10g R2 should I stop/start database when I change sGA_TARGET :
ALTER SYSTEM SET SGA_TARGET=value [SCOPE={SPFILE|MEMORY|BOTH}]
Thank you.

user522961 wrote:
OK.
When I query V$PARAMETER I have the OLD value for SGA_TARGET. It is normal because the value in V$PARAMETER comes from starting and spfile. How can I be sur that now oRACLE uses the new value for SGA_TARGET effectively ?
Thanks again.Not sure I understand your question. If you set SGA_TARGET with SCOPE=MEMORY or BOTH, it should be in effect immediately.
SQL> alter system set sga_target=253M scope=both;
System altered.
SQL> select value bytes, value/1048576 MB from v$parameter where name = 'sga_target';
BYTES              MB
268435456         256
SQL> show parameter sga
NAME                                 TYPE        VALUE
lock_sga                             boolean     FALSE
pre_page_sga                         boolean     FALSE
sga_max_size                         big integer 512M
sga_target                           big integer 256M
SQL> alter system set sga_target=257M scope=both;
System altered.
SQL> select value bytes, value/1048576 MB from v$parameter where name = 'sga_target';
BYTES              MB
272629760         260
SQL> show parameter sga
NAME                                 TYPE        VALUE
lock_sga                             boolean     FALSE
pre_page_sga                         boolean     FALSE
sga_max_size                         big integer 512M
sga_target                           big integer 260M
SQL>

"ALTER SYSTEM SET"

Hi
When a parameter is changed using "ALTER SYSTEM SET parameter=X" without the clause SCOPE, where will that parameter be changed? In memory or in spfile?
Thanks

In the memory and once you bounc the database, the value which you sent is gone. If you need to keep permanently, use scope=spfile.
SJH
OCP DBA

Can I execute "Alter System Disconnect Session" in a OLE VB Script?

Will this work? If not - How to do it?
The speadsheet contains a list of sid's and serial#. I want to highlight a cell containing a username, then run the kill session macro on it.
Sub Kill_Session()
Dim KillStatement As Object
DBPassword = "uuuu/pppppppp"
DatabaseName = "dddd"
Set objSession = CreateObject("OracleInProcServer.XOraSession")
Set objdatabase = objSession.opendatabase(DatabaseName, DBPassword, 0&)
objdatabase.Parameters.Add "SERIAL", 0, 2
objdatabase.Parameters("SERIAL").ServerType = 1
objdatabase.Parameters.Add "SID", 0, 2
objdatabase.Parameters("SID").ServerType = 1
Inputdata = ActiveCell.Value
RowNo = ActiveCell.Row
objdatabase.Parameters("SERIAL").Value = Worksheets("Sheet1").Cells(RowNo, 13)
objdatabase.Parameters("SID").Value = Worksheets("Sheet1").Cells(RowNo, 12)
Set OraSqlStmt = objdatabase.CreateSQL("ALTER SYSTEM DISCONNECT SESSION ':SID, :SERIAL' IMMEDIATE;", 0&)
MsgBox objdatabase.Parameters("SID").Value
MsgBox objdatabase.Parameters("SERIAL").Value
objdatabase.Parameters.Remove ("SERIAL")
objdatabase.Parameters.Remove ("SID")
End Sub

on 10gR1/10gR2, you can not use
ALTER SYSTEM KILL SESSION ‘115,9779,@1';that start from 11gR1
Only
* For integer1, specify the value of the SID column.
* For integer2, specify the value of the SERIAL# column.
ALTER SYSTEM KILL SESSION ‘115,9779';http://download.oracle.com/docs/cd/B14117_01/server.101/b10759/statements_2013.htm#SQLRF00902
http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_2013.htm#SQLRF00902
You may use crontab to help ....
Example about blocking (SID):
select 'ALTER SYSTEM KILL SESSION ''' ||sid||','||serial#|| ''' IMMEDIATE;' from gv$session s where sid in (
select distinct(l1.sid) from
gv$lock l1, gv$lock l2
where l1.block = 1 and l2.request > 0
and l1.id1=l2.id1
and l1.id2=l2.id2
) AND INST_ID = (select INSTANCE_NUMBER from v$instance )and ....
Good Luck

Alter System Kill Session Not Working

I'm not certain as to what the problem may be, but the following code does not work in that the session is not being disconnected.
The attempt is to have this trigger kill a user's logon session if the user is attempting to run a program named 'ex_oc.exe'
I've tested the code (getting the values back to the table as expected) and it appears to be working but it doesn't execute.
I've also tried ''ALTER SYSTEM DISCONNECT SESSION'.
Database is 11g.
Any ideas?
Thanks
CREATE OR REPLACE TRIGGER SYS.DENY_MSB_TRIGGER_UPDATEDD
AFTER LOGON ON Database
DECLARE
v_programname varchar2(64);
v_logontime date;
v_process varchar2(24);
v_machine varchar2(64);
v_sid number;
v_serialnum number;
v_username varchar2(30);
v_stmt2run VARCHAR2(327);
cur INTEGER;
ret INTEGER;
v_string VARCHAR2(500);
BEGIN
SELECT PROGRAM, PROCESS, MACHINE, SID, SERIAL#, USERNAME
INTO v_programname, v_process, v_machine, v_sid, v_serialnum, v_username
FROM V$SESSION
WHERE PROGRAM = LOWER('ex_oc.exe');
INSERT INTO SAUDIT.DENYMSB (PROGRAM, PROCESS, MACHINE, SID, SERIALNUM, USERNAME)
VALUES (v_programname, v_process, v_machine, v_sid, v_serialnum, v_username );
v_string := 'ALTER SYSTEM KILL SESSION' || CHR(39)||v_sid||','||v_serialnum|| CHR(39)||' IMMEDIATE';
EXECUTE IMMEDIATE v_string;
END;
Edited by: user12451703 on Jan 14, 2010 8:57 AM
Edited by: user12451703 on Jan 14, 2010 8:58 AM

user12451703 wrote:
I'm not trying to kill my own session.
Trigger written by Sys and running it as a generic user.You completely misunderstand triggers. Same as SP/SF trigger is always executed in invoking session on behalf of trigger owner. Below is a slighly modified version of your trigger that does not allow user U1 to connect by killing user U1 session:
SQL> connect scott as sysdba
Enter password: *****
Connected.
SQL> CREATE OR REPLACE TRIGGER SYS.DENY_MSB_TRIGGER_UPDATEDD
2 AFTER LOGON ON Database
3 DECLARE
4 v_programname varchar2(64);
5 v_logontime date;
6 v_process varchar2(24);
7 v_machine varchar2(64);
8 v_sid number;
9 v_serialnum number;
10 v_username varchar2(30);
11 v_stmt2run VARCHAR2(327);
12 cur INTEGER;
13 ret INTEGER;
14 v_string VARCHAR2(500);
15 BEGIN
16 SELECT PROGRAM, PROCESS, MACHINE, SID, SERIAL#, USERNAME
17 INTO v_programname, v_process, v_machine, v_sid, v_serialnum, v_username
18 FROM V$SESSION where username = 'U1';
19 EXECUTE IMMEDIATE ('ALTER SYSTEM KILL SESSION ''' || v_sid || ',' || v_serialnum || '''');
20 EXCEPTION
21 WHEN OTHERS THEN
22 RAISE_APPLICATION_ERROR(-20001, 'Execution of this program not allowed', TRUE);
23 END;
24 /
Trigger created.
SQL> create user u1 identified by u1
2 /
User created.
SQL> grant create session to u1
2 /
Grant succeeded.
SQL> connect u1/u1
ERROR:
ORA-00604: error occurred at recursive SQL level 1
ORA-20001: Execution of this program not allowed
ORA-06512: at line 20
<font color=red size =2>ORA-00027: cannot kill current session</font>
Warning: You are no longer connected to ORACLE.
SQL>
Also, user not that keen to change the name of the exe.Is cex_soc.exe client side executable? If so what prevents user from renaming it?
SY.

Alter system inside a Stored procedure

We have a stored proc (owned by a dba id) that accepts the sid and serial# and executes an "alter system.." to kill the session based on the passed values. We granted execute on this proc to a monitor account that monitors for any blocking sessions and wants to kill the offending ones. Trying to run this proc from that monitor account (which has execute on the proc) returns the following error --
ERROR at line 1:
ORA-01031: insufficient privileges
ORA-06512: at "ORACLE.KILLSESSION", line 43
ORA-06512: at line 4
The line returning the error is this --
execute immediate 'alter system kill session '''||c_sid||','||c_srl||'''';
Any ideas why the alter system doesn't work although the monitor account has execute on this proc?
We've successfully used this technique to trucate tables (which needs the powerful "drop any table" priv and it has worked fine there).
Thanks!

Thanks for reply Kamal.
The owner of the proc (called "ORACLE") had the DBA role granted to it. After doing a "set role none", I tried the alter system from that id and it didn't work. I then granted the ALTER SYSTEM priv directly to the owner and this worked!
The lingerning question though is why does the same priv not work via the dba role.
SQL > select * from dba_sys_privs where grantee='DBA' and privilege like 'ALTER SYSTEM%';
GRANTEE PRIVILEGE ADM
DBA ALTER SYSTEM YES

Alter system trigger - substitution

Hello.
By the documentation, there is restriction for trigger on alter command: "The trigger will not be fired by an ALTER DATABASE statement".
I'm trying to use BEFORE SHUTDOWN and AFTER STARTUP triggers to database and I'd need also cover situations:
- alter system quiesce restricted
- alter system suspend
- alter system enable restricted session
- alter system unquiesce
- alter system disable restricted session
- alter system resume
I'm using ALTER SYSTEM command (not ALTER DATABASE), but trigger isn't fired too. Is there any way how to catch and do some PL/SQL pre/post processing events described above?
Thanks.

Oracle Version ?
if ur on 10.x.x.x.x
Check
sql> select space_limit/1024/1024 "Limit MB",round(space_used/1024/1024) "Used MB"
2* from v$recovery_file_dest
SQL> /
Limit MB Used MB
2048 1681
If limit and used field equal then increase db_recovery_file_dest_size parameter size
SQL> show parameter db_recovery_file_dest_size
NAME TYPE VALUE
db_recovery_file_dest_size big integer 2G
SQL> alter system set db_recovery_file_dest_size = 3g;
System altered.
Also check below link.
>>>Re: Switch logfile hangs
[b]>>>SQL> alter system switch logfile;

Alter system set db_2k_cache_size=10m

Hi All,
I am using 11gR2 and try to create db_2k_cache_size when the execute the below command throwing error like..
alter system set db_2k_cache_size=10m
ERROR at line 1:
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-00384: Insufficient memory to grow cache
Could you please let me know what is the cause of the issue?
Regards
Narender B

Can anyone help on this...
Regards
Narender B

ALTER SYSTEM

I'm fairly new to Oracle, but i'm enjoying learning these new tips and tricks. When i need to change a parameter which will affect the whole database, what I used to do is to edit the pfile and restart the database. However, lately I got to know that I can do the same thing without restarting the database by using the ALTER SYSTEM technique. Then why we don't all use this technique? Are there some disadvantages? In a particular forum there was also stated that when using this technique on Oracle9i/Oracle10g one must set scope to both. Can someone explain me what this means please? Thanks.
(Ah, my ultimate scope is to be able to set the archive redo log to on, and the 07_DICTIONARY_ACCESSIBILITY parameter to true to be able to use sys - and i want to change these parameters without possibly restarting the database)

There are two types of initialization parameters 1. Dynamic and 2. Static.
Only with the dynamic parameters you don?t have to restart the Database.
For static parameters you have to restart the Database. Moreover the technique of ALTER SYSTEM can be used only with spfile.
Scope = SPFILE: means that the change is effective at the next startup
SCOPE = MEMORY: means that the change is applied in memory only
SCOPE = BOTH: is the default value. The change is applied in both the server parameter file and memory
For static parameters SCOPE = MEMORY and SCOPE = BOTH are not allowed.
Following are the steps to enable archiving.
1. Shut down the database instance.
SHUTDOWN
2. Start the instance and mount, but do not open, the database
STARTUP MOUNT
3. Switch the database's no archiving mode. Then open the database for normal operations.
ALTER DATABASE ARCHIVELOG;
ALTER DATABASE OPEN;
4. Shut down the database.
SHUTDOWN IMMEDIATE
5. Back up the database
To change O7_DICTIONARY_ACCESSIBILITY parameter
ALTER SYSTEM SET O7_DICTIONARY_ACCESSIBILITY = true SCOPE=spfile
Manu

Alter System Currency Value

Similar Messages

Maybe you are looking for