Locked Profile Status

Hi,
We are testing on search functionality on recruiter role. Searching for a profile of a candidate who has locked profile status. Expectation is only candidates who have released their profile will appear in the talent pool search. But we are able to see even candidates who have locked profile status.
Please let us know if I have missed out any customizing setting?
Thanks in Advance.
Savitha

Hi Sally,
Thanks for your reply.
I have verfied if the correction mentioned in the sap note you've mentioned has been incorporated in the system, and I observe that it has been modified per the note.
I have already added the TREX attributes as below:
ls_hidden_info-ses_attr_name = me->gc_hidden_info_cand_status. ('hidden_info.candidate_status.key')
ls_hidden_info-ses_attr_value = me->gc_cand_status_released. ('RELEASED')
for the iv_search_task EQ 'quicksearch' and appended it to the exp. internal table et_hidden_info.
After this am getting the error message 'The syntax of your entries in the full text search is incorrect'.
Many Thanks,
Wincy

Similar Messages

EREC: Qucik search functionality for locked profiles of candidates

Hi Experts,
Normally when a candidate register themselves in e-Recruiting application, they have two option to set their profile status i.e. 'Locked' and 'Released'.
Locked - Applicant is inactive or not looking for change. So when recruiter do a search, they won't see 'Locked' profiles.
But in our case, recruiters are able to see the Locked profiles. which is not correct.
Could you please let me know how it can be restricted. So that recruiters will not be able to see the locked candidate profiles.
Please suggest some hints.
Thanks in advance.
Regards,
Anil

Hello,
This is how the standard e-recruiting quick search works. It does not take into account the attachments of objects nor the candidate profile status. It searches for the structured free text data only and also searches for candidates with both released profiles and candidates with locked profiles.
If you want the recruiters to be able to search for released candidates then they have to use either the TRM search for candidates (Candidate Search service), the search for candidates in the context of a requisition (Search and Proposed Candidates link), and the search for candidates in the context of a talent group. These three searches take into account candidates with released profiles only.
Regards,

Error: Lock profile for approval procedure not maintained in Customizing

Hi,
We are working on the CHARM approval process. I have noticed that without selecting an approval procedure, I select the status (Awaiting business approval) on which the approval workflow is triggered, the system gives below error:
Select an approval procedure first
Lock profile for approval procedure not maintained in Customizing
Approval procedure and approval steps are locked automatically
This locks the approval procedure and the RFC can no longer be processed further. Why is that happening ? Anyone can select the status by mistake and lose the RFC, is there a way to stop this or at least reset it ? the lock procedure is already maintained in approval procedure customizing.
Best Regards.

Hi Karthik,
Thanks for the quick reply, however the settings mentioned on page 38 are already in place i.e. the approval procedure gets determined correctly based on change category (rule policy) and also is locked after putting it to 'Awaiting Approval'
But the problem exists - setting the status 'Awaiting App.' without selecting app.proc, will result in a total lock of the RFC.

Process order profile status

Hi Guru,
i am preparing a report in which in selection screen we have selection profile status (same as cooispi) .Now the process orders has to be filtered on the baisi of this profile status. I have debug the tcode COOISPI but could not get the logic.
have checked through tables JEST, TJ49.JSTO ect but could not get the right logic . please help
Regards
Aditya Shrivastava

Hello
Use follow logic:
1. Select records from AUFK
2. Call function 'STATUS_READ' with OBJNR = AUFK-OBJNR. You will have table with all status for this order.
If any status of order in selection-screen, then put this into final table, else delete this.

Need details about "Lock Profiling" tab of JRockit JRA

Hi,
I'm experimenting with the JRockit JRA tool: I think this is a very useful tool ! It provides very valuable information.
About locks ("Lock Profiling" tab), since JRockit manages locks in a very sophisticated manneer, it enables to get very important information about which monitors are used by the application, helping for improving the performances.
Nevertheless, the BEA categories (thin/fat, uncontended/contended, recursive, after sleep) are not so clear. A short paper explaining what they mean would greatly help.
Fat contended monitors cost the most, but maybe 10000 thin uncontended locks cost the same as 1 fat contended lock does. We don't know.
So, there is a lack of information about the cost (absolute: in ms, or relative: 1 fat lock costs as N thin locks) of each kind of monitor. This information would dramaticaly help people searching where improvements of lock management are required in their application.
Thanks,
Tony

great explanation! Thanks
"ihse" <[email protected]> wrote in message
news:18555807.1105611467160.JavaMail.root@jserv5...
About thin, fat, recursive and contended locks in JRockit:
Let's start with the easiest part: recursive locks. A recursive lock
occurs in the following scenario:synchronized(foo) { // first time thread takes lock
synchronized(foo) { // this time, the lock is taken recursively
}The recursive lock taking may also occur in a method call several levels
down - it doesn't matter. Recursive locks are not neccessarily any sign of
bad programming, at least not if the recursive lock taking is done by a
separate method.
The good news is that recursive lock taking in JRockit is extremely fast.
In fact, the cost to take a lock recursively is almost negligable. This is
regardless if the lock was originally taken as a thin or a fat lock
(explained in detail below).
Now let's talk a bit about contention. Contention occurs whenever a thread
tries to take a lock, and that lock is not available (that is, it is held
by another thread). Let me be clear: contention ALWAYS costs in terms of
performance. The exact cost depends on many factors. I'll get to some more
details on the costs later on.
So if performance is an issue, you should strive to avoid contention.
Unfortunately, in many cases it is not possible to avoid contention -- if
you're application requires several threads to access a single, shared
resource at the same time, contention is unavoidable. Some designs are
better than others, though. Be careful that you don't overuse
synchronized-blocks. Minimize the code that has to be run while holding a
highly-contended lock. Don't use a single lock to protect unrelated
resources, if that lock proves to be easily contended.
In principle, that is all you can do as an application developer: design
your program to avoid contention, if possible. There are some experimental
flags to change some of the JRockit locking behaviour, but I strongly
discourage anyone from using these. The default values is carefully
trimmed, and changing this is likely to result in worse, rather than
better, performance.
Still, I understand if you're curious to what JRockit is doing with your
application. I'll give some more details about the locking strategies in
JRockit.
All objects in Java are potential locks (monitors). This potential is
realized as an actual lock as soon as any thread enters a synchronized
block on that object. When a lock is "born" in this way, it is a kind of
lock that is known as a "thin lock". A thin lock has the following
characteristics:
* It requires no extra memory -- all information about the lock is stored
in the object itself.
* It is fast to take.
* Other threads that try to take the lock cannot register themselves as
contending.
The most costly part of taking a thin lock is a CAS (compare-and-swap)
operation. It's an atomic instruction, which means as far as CPU
instructions goes, it is dead slow. Compared to other parts of locking
(contention in general, and taking fat locks in specific), it is still
very fast.
For locks that are mostly uncontended, thin locks are great. There is
little overhead compared to no locking, which is good since a lot of Java
code (especially in the class library) use lot of synchronization.
However, as soon as a lock becomes contended, the situation is not longer
as obvious as to what is most efficient. If a lock is held for just a very
short moment of time, and JRockit is running on a multi-CPU (SMP) machine,
the best strategy is to "spin-lock". This means, that the thread that
wants the lock continuously checks if the lock is still taken, "spinning"
in a tight loop. This of course means some performance loss: no actual
user code is running, and the CPU is "wasting" time that could have been
spent on other threads. Still, if the lock is released by the other
threads after just a few cycles in the spin loop, this method is
preferable. This is what's meant by a "contended thin lock".
If the lock is not going to be released very fast, using this method on
contention would lead to bad performance. In that case, the lock is
"inflated" to a "fat lock". A fat lock has the following characteristics:
* It requeries a little extra memory, in terms of a separate list of
threads wanting to acquire the lock.
* It is relatively slow to take.
* One (or more) threads can register as queueing for (blocking on) that
lock.
A thread that encounters contention on a fat lock register itself as
blocking on that lock, and goes to sleep. This means giving up the rest of
its time quantum given to it by the OS. While this means that the CPU will
be used for running real user code on another thread, the extra context
switch is still expensive, compared to spin locking. When a thread does
this, we have a "contended fat lock".
When the last contending thread releases a fat lock, the lock normally
remains fat. Taking a fat lock, even without contention, is more expensive
than taking a fat lock (but less expensive than converting a thin lock to
a fat lock). If JRockit believes that the lock would benefit from being
thin (basically, if the contention was pure "bad luck" and the lock
normally is uncontended), it might "deflate" it to a thin lock again.
A special note regarding locks: if wait/notify/notifyAll is called on a
lock, it will automatically inflate to a fat lock. A good advice (not only
for this reason) is therefore not to mix "actual" locking with this kind
of notification on a single object.
JRockit uses a complex set of heuristics to determine amongst other
things:
* When to spin-lock on a thin lock (and how long), and when to inflate it
to a fat lock on contention.
* If and when to deflate a fat lock back to a thin lock.
* If and when to skip on the fairness on a contended fat lock to improve
performance.
These heuristics are dynamically adaptive, which means that they will
automatically change to what's best suited for the actual application that
is being run.
Since the switch beteen thin and fat locks are done automatically by
JRockit to the kind of lock that maximizes performance of the application,
the relative difference in performance between thin and fat locks
shouldn't really be of any concern to the user. It is impossible to give a
general answer to this question anyhow, since it differs from system to
system, depending on how many CPU:s you have, what kind of CPU:s, the
performance on other parts of the system (memory, cache, etc) and similar
factors. In addition to this, it is also very hard to give a good answer
to the question even for a specific system. Especially tricky is it to
determine with any accuracy the time spent spinning on contended thin
locks, since JRockit loops just a few machine instuctions a few times
before giving up, and profiling of this is likely to heavily influence the
time, giving a skewed image of the performance.
To summarize:
If you're concerned about performance, and can change your program to
avoid contention on a lock - then do so. If you can't avoid contention,
try to keep the code needed to run contended to a minimum. JRockit will
then do whatever is in its power to run your progam as fast as possible.
Use the lock information provided by JRA as a hint: fat locks are likely
to have been contended much or for a long time. Put your effort on
minimizing contention on them.

Lock/IMport Status - Object Locked

Hi Folks
I have a Custom BAPI, which has two structures associated with it. The BAPI is attached to a Workbench Request.
In the Display Request (SE01) of the Task ID of the request, it is seen that the 'Lock/IMport Status' has the value 'Object Locked'.
1) Why is it so?
2) Do I need to unlock it before releasing the TR?
3) If yes, how to unlock it?
Regards
Rajvat

check these links
link:[http://help.sap.com/saphelp_nw04s/helpdata/en/b6/8a3627f8534613af4d82d046a2d644/content.htm]
link:[https://cw.sdn.sap.com/cw/docs/DOC-111738;jsessionid=kNabg59s92_EBm1toQRcwFncrkv_kDDJIwEacYgA_SAP;saplb_*=(J2EE8941720)8941750]
use stms_import to open the queue

OIM 9.1 DB Recon Changes Locked Account status in OIM back to Provisioned

Hi,
I have a scheduled task that runs the OIM DBAccessReconTask but am seeing some unexpected behavior. Here are the steps to produce the error:
1. Provision a DB account to a user in OIM (this creates an account in the target database and the account shows in the user's resource profile with a status of "Provisioned")
2. Disable the DB account in OIM from the User's Resource profile screen (this successfully disables the account in the database and changes the account status to "Disabled")
3. Run the DBAccessReconTask
4. After the DBAccessRecon task completes the status of the DB account in the database is still disabled but in OIM on the user's resource profile screen it is marked as "Provisioned"
I did not expect this to be changed to provisioned in OIM since it is disabled in the database. Has anyone seen similar issues when running the DBAccessReconTask or know a way to fix this?

Hi Suren,
Thanks for the reply. Originally I thought your solution would work but after analyzing it closer there is a more fundamental problem we are having with the DBReconTask. We only want the reconciliation to take place going from OIM to the database and not vice versa (i.e. changes to an account in OIM should be pushed to the database but not from the database to OIM). However, currently if a change is made in the database (a role is added, the profile is changed, etc...) and the DBReconTask is run then it will be updated in OIM. Do you know how this can be achieved? These are the properties we currently use when creating the task:
Properties props = new Properties();
props.put("Target System Login Recon - Resource Object name:", ro.getName());
props.put("Target System User Recon - Resource Object name:", ro.getName());
props.put("Trusted Source Recon - Resource Object name:", "Xellerate User");
props.put("Server", itResource.getName());
props.put("Record Size", "ALL");
props.put("isTrusted", "NO");
props.put("DBName", "nodata");
props.put("ExcludeSystemUsers", "nodata");
props.put("ReconcileLockedUser", "YES");
props.put("Login Name", "nodata");

Table for process order &Selection profile status details -reg

Hi ,
From which tabel we can get the link between the process order and selection status profile (like SAP001 etc..
When we input the process orders we should get the selection status profiel linked to it
Regards,
Madhu Kiran

Hi,
The tables JEST and JSTO are related to status profile .
What i need is of Selection Profile
You can see this field in COOIS or COOISPI just above the Sys Status field
We need this urgently
Can any one help ?
Madhu Kiran

Status Profile : Status not changing in CRM

Hi Gurus
Created order with header status as as " In process" , item status is defaulted to " open" and order replicatd to ECC , billed aswell . But when I checked in CRM still status not changing to completed but retains with In process at header level & open at item level.
I would expect order status should be completed at header level & Item level.
Is there any thing wrong with status profile settings at header & Item level? , I have created status profiles with following settings.
I have copied standard status profile " CRMORDER" and assigned to trasaction type and made following settings:
Under Open :   following transactional contorl selected
To be distributed   : Selected options "Forbidden " & No active
Under In process:
In process : Selected options " Allowed " & Set
Undo Rejection : Selected options " No infulence " & Set
Under Completed:
Complete : Selected options " Allow " & Set
Created status profile for Item i.e. copied standard CRMORD_i and made following changes:
Under Open : No transaction control selected
Under In Process :
Edit : Seleted options " No influence" & Set
Undo Rejection : Selected options " No Influence & Set
Under Completed:
Completed : Selected options " Allowed & Set"
Rejected : Selected options " Allowed & Set"
Actually we are using material which is non deliverable but should be billed, while creating order , I can see staus at item level is open and remains open even after billed in ECC. And also we are mapping Business activity reasons to order reasons in ECC.
Is any thing i am selecting wrong options in status profile at header level & item level? Much appricieated for solution.
Thanks
shash

Hi Gurus
Created order with header status as as " In process" , item status is defaulted to " open" and order replicatd to ECC , billed aswell . But when I checked in CRM still status not changing to completed but retains with In process at header level & open at item level.
I would expect order status should be completed at header level & Item level.
Is there any thing wrong with status profile settings at header & Item level? , I have created status profiles with following settings.
I have copied standard status profile " CRMORDER" and assigned to trasaction type and made following settings:
Under Open :   following transactional contorl selected
To be distributed   : Selected options "Forbidden " & No active
Under In process:
In process : Selected options " Allowed " & Set
Undo Rejection : Selected options " No infulence " & Set
Under Completed:
Complete : Selected options " Allow " & Set
Created status profile for Item i.e. copied standard CRMORD_i and made following changes:
Under Open : No transaction control selected
Under In Process :
Edit : Seleted options " No influence" & Set
Undo Rejection : Selected options " No Influence & Set
Under Completed:
Completed : Selected options " Allowed & Set"
Rejected : Selected options " Allowed & Set"
Actually we are using material which is non deliverable but should be billed, while creating order , I can see staus at item level is open and remains open even after billed in ECC. And also we are mapping Business activity reasons to order reasons in ECC.
Not sure whether i am selecting wrong options in status profile at header level & item level?
Plz help me on this.
Thanks
shash

STS: Why data can't be locked when status is sent to approval.

Hi All,
I'd like to ask about STS, I have a problem on it. I'm working in IP.
Why data can't be locked though the status is already in "send to approval" ?
I've setup data slice under the corresponding cube based on exit class: CL_UPS_LOCK_DATASLICE.
Is it because I've yet to assign R_STS_PT authorization to the planner ? So when I'm opening the data using planner user id, data is still not locked yet.
Could you kindly help me to resolve this problem please ?
Thanks a lot all,
Have a good day,
Best regards,
Daniel N.

Hi Daniel,
Thanks for the response, much appreciated, a bit of good fortune that I ran into someone in April 2010 who is having the same problem as me on the obscure STS!
I have some queries about your response;
1) You say to create planning a function within a sequence to copy the status., did you mean to copy the version?
2) So the basic principle is, when a user submits data for approval, they use the STS monitor's 'Approval' button, this then triggers the planning sequence to copy data which they just planned to a certain version, this version is hard coded into the data slice, is this correct?
3) What happens then when the higher level manager approves the data, is this then unlocked by copying to another version?
If you could please break it down for me.
Appreciate your time & help.
Regards
SS
Hi Sulman,
You can create function and planning sequence to copy the status.
Then you create dataslice based on particular status to block data from data entry.
You can embed the planning sequence to STS using t-code: BPS_TC.
Thanks a lot .
Best regards,
Daniel N.

Change Profile Status

I have a project e.g OT/83009 which has an incorect WBS Status Profile.
The profile was initially set as YPS00003 - should have been YPS00004.
I have changed the profile on the project definition to YPS00004 but the WBS elements are still showing YPS00003 in them and are all grayed out so i cant change them...
It has set the User status on the WBS elements attached as appv and will
not let me change it in order to set to QACP.
Is it possible to set the user status of the WBS elements to YPS00004??
Thanks
Ishy

hi,
Once a user status is set, you cannot change the status profile of the WBS.
Muraleedharan.R
091 9880028904

Locked Work Status doesn't work

Hi
This is a new case.
I have original work status like this. I show MAN only in this example
Unlock    MAN=unlock
Submitted MAN=owner
Approved MAN=locked
Then I add a new work status line as the intial state
Start     MAN=locked
Unlock    MAN=unlock
Submitted MAN=owner
Approved MAN=locked
The purpose of the Start work status is to prevent the user submit something at the initial state.
But the Start work status doesn't lock anything, user is freely to submit data on this work state.
My analysis,
I changed the current work status from Start to Unlock and switch it back to Start and the lock does its job.
Anybody has the same issue?
Halomoan
Edited by: Halomoan Zhou on Aug 26, 2008 11:50 AM

It is logical that it works only after you upgrade to unlocked and downgrade again. The workstatus mechanism makes use of a table called tblFINANCElock (or what name your application has). In the beginning there are no records in this table which indicates that the data is unlocked. Once you update the status for the first time a record is generated with a status. From now on the system can link the records to the work status setting that you have defined and see that status "start" should lock the data. I think this functioality works as it is intended, and the only workaround for you is to lock and unlock the data before the users start entering data for that period.
-Joost

Project Profile Status Definition

Hi,
I would like to understand the impact and difference on the below 3 options for specifying status profile for Project Definition:
1. if it is left blank
2. if PS000001 is specified
3. if 00000001 is specified
Thanks!
Regards,
Vivian

Hi
1. if it is left blank- There will not be any user status for PD. Hence all the transaction control will be by the system status.U can add profile later.
2. if PS000001 is specified- User status control for PD will be from profile PS000001.
3. if 00000001 is specified- User status control for PD will be according to the profile 00000001
For details of status profile check T code OK02.
Regards

HT204387 how to check lock unlock status

hello all
how can i check status of iphone lock or unlock by imei
if any one know help me me please

Call AppleCare and give them the serial number.

"Firefox is already runing..." error. (It's not a locked profile.)

When I'm trying to open a new window from an external program, i.e, from the taskbar (right-clicking on the FF icon), open a link in an email from Thunderbird, open a local html document, etc. I get the "FF is already running..." error. This only occurs when FF is already open and I just want another window; if FF is not open, the external program fires up a new instance of FF with no problem. Further, it does not happen if I click File -> New Window.
Also, I have 3 machines that upgraded from Firefox 3.6.whatever (the latest before 4.0) and 2 machines that have FF 4 as their first installations of FF. This issue only comes up on the machines I upgraded.
I have tried disabling all add-ons. I've even tried starting completely over with fresh profiles. I always get the issue.

Bonjour,
Je ne peux pas ouvrir Firefox. Voici le message que je reçois : " Firefox est déjà en cours d'exécution mais ne répond pas. Pour ouvrir une nouvelle fenêtre, vous devez d'abord arrêter le processus Firefox existant ou redémarrer votre système." Je ne vois pas de processus existant.
Si je me sers de copie de documents PDF et qu'il y a des liens dans le document, les liens ne fonctionnent pas.
Armande

Locked Profile Status

Similar Messages

Maybe you are looking for