E-Recruiting "Read-Only" Transactions

We would like to make some for the E-Recruiting functionality that is available to recruiters from the recruiter start page available to support staff in a "read-only" mode. Our immediate need is for read-only version of the Candidate Overview available from Application Management, although a read-only version of the Requisition Maintenance and Candidate Shortlist would be helpful as well. I have tried to create a read-only role for the Candiate Overview by playing with the standard authorization objects P_RCF_APPL, R_FCF_VIEW, P_RCF_POOL and P_RCF_STAT but have had no luck.
Does anyone have any suggestions?
Thanks!

This cannot be handled via authorizations in e-recruiting, because it is a non-exspected behaviour.
You can only realize this by development or modification.
regards

Similar Messages

Select in read only transaction mode / insert in write mode

hello,
i have a following question: i have 2 db, one is rdb and one oracle
im extracting data out of table out of rdb and inserting them into oracle via OWB;
however this is run in read-write mode and causes locks in rdb; the only way to prevent locks is to run a select statement that accesses rdb in 'read only' transaction mode;
my question is: is this possible to split up the select and insert statements of oracle into 2 different transaction modes, so that select statement is run in 'read-only' mode and insert in 'write' mode?
i appreicate tips on how this could be achieved
thx
rgds

Hello,
is this something like:
insert into oracle_table (select * from rdb_table@rdb_link);
Then it is easy, you just need to use an sql init file for your OCI Service. Create a file, e.g. sql_init.ini that contains this line:
declare transaction read only;
Then alter your service so that it sees the sql init file, e.g.:
SQLSRV> alter service <your OCI service> sql_init_file sql_init.ini
The service owner must have the privileges to read the file. You need to restart the OCI service.
Then a statement of the above kind results in a read only transaction on Rdb side, and the insert on Oracle side is done.
I hope your SQL/Services version is a recent one (actual version is 7.3.1), because of this (from the SQL/Services Release Notes 7.2.0.1):
5.4.25 Declare Transaction in SQL Init File Being Overridden
In releases of OCI Services for Oracle Rdb prior to 7.2.0.1, if a DECLARE
TRANSACTION statement was executed in the SQL initialization file of a service, it would
be overridden by a DECLARE TRANSACTION statement executed later by OCI Services
for Oracle Rdb. Toward the end of the connection setup, OCI Services for Oracle Rdb would
execute a DECLARE TRANSACTION statement to set the default transaction
characteristics to be close to Oracle default transaction characteristics. This would supersede
any DECLARE TRANSACTION statement in the SQL initialization file. Starting with
release 7.2.0.1, OCI Services for Oracle Rdb recognizes that a DECLARE TRANSACTION
statement has been executed and will not execute another one.
Regards
Wolfgang
P.S.: It is always better to place Rdb related questions in our communities at https://communities.oracle.com/portal/server.pt/community/rdb_product_family_on_openvms . Those are watched by Rdb Engineering and Support. It was by pure chance that I saw this forum thread.

How to ensure read only transaction mode

I am using Oracle73 driver version 2.00.03.01 against Oracle
7.3.4.5.
2 Questions:
1) I am using Microsoft Access 97 to attach to Oracle tables
via the aforementioned ODBC driver. Is there a way to ensure
that queries using these attached tables run on the Oracle
server in read only mode (equivalent to "set transaction read
only")? The solution cannot be using pass-through queries or
VBA code.
2) Where can I find a reference for all valid ODBC.INI entries
for this driver?
Any help would be greatly appreciated ...

If you are able to upgrade the clients to use the Oracle 8
driver, there's a check-box to set a DSN as read-only.
Unfortunately, I have no idea whether this option was available
in the old driver you're using.
Justin

Is it possible to have access to PU12 in read only to avoid SOD issues?

Hi
We would like to provide PU12 to a small number of users for troubleshooting purposes with our payroll interface, however PU12 transaction is one that is a SOD issue, namely: 'Modify payroll master data and then process payroll. Potential for fraudulent activity'
Is there an equivalent read only transaction that SAP has to view the export history data possibly, or else a way to change the settings of PU12 to make it read only via a custom tcode?
Any advice would be very helpful.
Thanks
Nicola

Hi,
Make the variant of the screen and provide the separate Tcode using SE93.
Good Luck
Om

Database open for read-only access ORACLE

while building a universe with a dblink betweens oracle databases, i try to create a derived table in the form
select field1 from table@db_to_db2
but i get the following message:
Exception: DBD, ORA-16000: database open for read-only acces State N/A.
I understand the statement "Set Transaction for read only" must be set before any transaction during the session, but still dont know how to trigger it in bo universe designer.
Can someone know how to solve it?

I suggest you fill-in the BEGIN_SQL parameter on the Universe to turn on the read-only transaction.
Here is an excerpt from the Universe Designer guide:
The BEGIN_SQL parameter allows you to prefix SQL statements with the same parameters each time a SQL statement is generated.
1. Open the "Universe Parameters" dialog box in Designer.
2. Click the Parameter tab.
3. In the "Parameter" list, select the BEGIN_SQL parameter and enter the
appropriate prefix commands.
4. Save the settings.
5. Save the universe.

Using BC4J on a read-only database?

Is it possible too configure BC4J to run against a read-only database?
I only have query-based view objects (no Entity objects) and the data is updated by another application. The user I use to atatch to the DB only has read-only access, and when trying to run my BC4J app I get the following errors:
Error Message: JBO-28006: Could not create persistence table PS_TXN
Error Message: ORA-01950: no privileges on tablespace 'USERS'
Is this PS_TXN table required even if I only want read-only transactions?
thanks
Brigette

Thanks Shay,
In conjunction with http://otn.oracle.com/products/jdev/howtos/bc4j/howto_dynamic_jdbc.html (which showed me how/were to set the property), this has solved the problem!
keep smiling
Brigette

Usage Tracking - Cant perform insert operation inside a READ ONLY trans

Hello,
I have been experiencing the following error message when trying to install a row in our s_nq_acct table for USAGE TRACKING:
[nQSError: 16001] ODBC error state: S1000 code: 1456 message: [Oracle][ODBC][Ora]ORA-01456: may not perform insert/delete/update operation inside a READ ONLY transaction.
- I am able to manually insert rows via SQL*Plus whilst logged on as the same user as the Connection Pool
- The Read Only option is not ticked for the ODBC
Can anyone please help me with this?
Thanks,
Rhys

Hi rnm1978,
You were right!
I was being a bit retarded and had to simply switch the call interface on the connection pool to use the OCI and ensure the dta source name was that of the TNS names entry and not the system DSN.

How can we make SAP system READ ONLY !!!!!

Hi, we have an SAP R/3 4.6 C Application. We need to take the system for read only state means we dont want the users to allow any update for the system but they should be able to view the data what they have created. Mean while we dont want the database to be taken in read only mode as we the administrators or the users might want to update their password information.
It would be a big help if some one can through some tips on how we achieve this.
Thanks much in advance.
Guru

Hi
Please make the database in READ ONLY MODE. This will help. If it is an oracle database then.
Open a Database in Read-Only Mode
You can open any database in read-only mode to prevent its data from being modified by user transactions. Read-only mode restricts database access to read-only transactions, which cannot write to the datafiles or to the redo log files.
Disk writes to other files, such as control files, operating system audit trails, trace files, and alert files, can continue in read-only mode. Temporary tablespaces for sort operations are not affected by the database being open in read-only mode. However, you cannot take permanent tablespaces offline while a database is open in read-only mode. Also, job queues are not available in read-only mode.
Read-only mode does not restrict database recovery or operations that change the database's state without generating redo data. For example, in read-only mode:
Datafiles can be taken offline and online
Offline datafiles and tablespaces can be recovered
The control file remains available for updates about the state of the database
One useful application of read-only mode is that standby databases can function as temporary reporting databases
Opening a Database in Read-Only Mode
Opening a database in read-only mode enables you to query an open database while eliminating any potential for online data content changes. While opening a database in read-only mode guarantees that datafile and redo log files are not written to, it does not restrict database recovery or operations that change the state of the database without generating redo. For example, you can take datafiles offline or bring them online since these operations do not effect data content.
If a query against a database in read-only mode uses temporary tablespace, for example to do disk sorts, then the issuer of the query must have a locally managed tablespace assigned as the default temporary tablespace. Otherwise, the query will fail. This is explained in "Creating a Locally Managed Temporary Tablespace".
Ideally, you open a database in read-only mode when you alternate a standby database between read-only and recovery mode. Be aware that these are mutually exclusive modes.
The following statement opens a database in read-only mode:
ALTER DATABASE OPEN READ ONLY;
You can also open a database in read-write mode as follows:
ALTER DATABASE OPEN READ WRITE;
However, read-write is the default mode.
Regards

Fields in read-only mode for BP transaction in upgrade from 4.72 to ECC6.0

Hello,
This is regarding the query for BP transaction in upgrade from 4.72 to ECC 6.0.
While creating BP / Changing BP system is disabling the fields in compnay code & sales area option. There is a SAP not provided 907860; and specified that the proplem is because of the delta customizing.
All the customization settings are as per the note. And the Synchronization Control is also activated. But still the fields are disabled only.
I have checked the field settings also in Cross-Application-Components & Logistic-Genral.
But these are not working for compnay code & sales area data.
please let me know if anyone has faced this type of problem / found any solution on this.
Best Regards,
Shubhada

SAP IMG -> Cross Application Components -> Master Data Synchronization  Synchronization Control -> Synchronization Control -> Activate Synchronization options
This setting allows you to activate synchronization of BP with R/3. Not maintaining the values may result in certain fields being read-only in BP.
Suggested Values:
Source Object: BP | Target Object: CUSTOMER | Active Indicator : X
Source Object: BP | Target Object: VENDOR | Active Indicator : X
Source Object: CUSTOMER | Target Object: BP | Active Indicator : X
Source Object: VENDOR | Target Object: BP | Active Indicator : X
Have you set all of the above settings??
BHARATH

Data Type field read only in Data source for transaction data (PC_FILE)

Hi folks,
I need to change Data Type for some of the fields in "Field" tab in data source for transactional data. It became read only after I activate the data source. Need help in making it editable. All fields now have Data type=CHAR.
Thanks

Nevermind folks. I got it.

Check a condition and then put the transaction as read-only

Hello people,
I need to make a check in Purchase Order (ME21N and ME23N), so that when the user enter in transaction, I will check if the invoice was registered and then put the purchase order in "read only" state.
How do you suggest me to do it?
Loop at screen? Is there a state flag to set?
Thanks a lot!!!

Hi,
I didn't get your requirement correctly. When using ME21N, your purchase order is not yet created. What is the meaning of set the T-code in display mode only for the PO? ME23N is already display only T-code. If you are refering to ME22N, then probably you can think of a custom T-code where you can call ME22N/23N based on the check.
Thanks,
Vinod.

Read-only version of transaction FBL5N.

Hello Everybody,
I have to create a GOTO report from a query, where the jumping target should be the read-only version of transaction FBL5N.
Please let me know what is the read-only version of transaction FBL5N.
Thanks in advance
Shameem

Hi Siggi,
If I am right, I would be able to create the GOTO report, by specifying the jump target as the Transaction FBL5N.
And whenever the user uses the GOTO option, he would be able to only view the invoice details and not change anything.
Thanks,
Shameem

OracleCommand.Transaction property is read only

Does anyody know what's wrong with this:
VB Code:
Imports Oracle.DataAccess.Client
Dim oraCn As New OracleConnection(ConString)
Dim oraCmd1 As New OracleCommand(oraString1, oraCn)
Dim oraTrans As OracleTransaction
oraTrans = oraCn.BeginTransaction(IsolationLevel.ReadCommitted)
oraCmd1.Transaction = oraTrans --> gives me error said that the property is read only
Does anyone know how to solve this issue?
Thanks in advance

Hi,
Access rights are proper. In fact, I am using Admin ID with full access.
Regards,
Kapil

Toad read only sessions open a transaction in DB?

Hi,
When I check v$transaction, I see all TOAD and sqldeveloper sessions which are read only accounts. If I use the same user in sqlplus it won't appear in v$transaction. I am puzzled why these tools create a transaction for even select queries. How can i avoid these tools creating transaction(may be they are running begin trasaction for each session causing a transaction).
Thanks
Anand

SAP IMG -> Cross Application Components -> Master Data Synchronization  Synchronization Control -> Synchronization Control -> Activate Synchronization options
This setting allows you to activate synchronization of BP with R/3. Not maintaining the values may result in certain fields being read-only in BP.
Suggested Values:
Source Object: BP | Target Object: CUSTOMER | Active Indicator : X
Source Object: BP | Target Object: VENDOR | Active Indicator : X
Source Object: CUSTOMER | Target Object: BP | Active Indicator : X
Source Object: VENDOR | Target Object: BP | Active Indicator : X
Have you set all of the above settings??
BHARATH

Making a transaction read-only for a particular user status

Hello,
I have a requirement wherein I need to make an opportunity read-only if it is saved with the user status set to 'Lost'. I tried setting the 'Forbidden' flag for 'Change Document' for this status but the problem is that the transaction gets locked even before saving it.
I have a 'Reason' field where I have dropdown values for the 'Lost' status. But when I try to select a reason, error message appears as: 'no changes possible in document'.
Is it possible via configuration to have the transaction locked only after it is saved with user status 'Lost' and not immediately on setting the status?
Regards,
Aditya Mishra

2 ways to achieve it...
1. the document editing can be controlled based on its status i.e. standard auth objects exist to control so that user is not able to make changes with this status.
2. implement BADI CRM_ORDER_AUTH_CHECK
put your logic to check the document status and accordingly reutrn FALSE if you do not want user to open it in edit mode.
hope this helps.
rgds

E-Recruiting "Read-Only" Transactions

Similar Messages

Maybe you are looking for