on ‎2014 Feb 08 1:39 PM
Request clarification before answering.
Hello Carmen,
powl queries are partly configuration (found in transactions named POWL*) and partly implementation in form of the so called Feeder class. Could you go more into detail what you want to change?
Kind Regards
Roman
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Roman.
The issue was that on query "My Planned Activities" there were several entries on the query results which had the candidate name blank. When trying to edit those activities which were showing the
related candidate's name as blank, the activity pop-up was opening a lready with an "Internal Error" message. This generates an entry on SLG1.
I checked in the t.code SLG1 and this is log:
I created a message OSS and SAP indicated that is because of a central person having multiple candidates associated to it.
The report HRALXSYNC created object duplicated NA. This occurs in the year 2011.
I have checked in the table HRP1001 and for a CP is associated several NA.
SAP indicated that for solve this inconsistency the solutions is delete the object NA(00085313) and expand the relationship of the objetc NA 00070303 to 31129999, however this can generate inconsistency with the index.
My solution is modify the query "My Planned Activities" and filtering out data that candidates in blank.
Thanks
Regards
Dear Roman
I found the following link:
http://scn.sap.com/thread/2098034
My Planned TRM Activities? The name of this query is ERC_WORKCENTER_QRY_PLAN_TRM
and the associated feeder class is CL_HRRCF_M_ACTIVITY_POWL_UI.
For solve my issue I should modify the feeder class?
Thanks
Regards
Hello Carmen,
in your case I would not change anything in the POWL feeder at all as the problem is purely data based.
Before adjusting the data as described by SAP I would investigate the following. First I would check if it is a single case or if there are more candidates which have this issue in the database. If it is a single case I'd just tidy up the data as a single case would from my perspective not be worth the time to spend much effort in it. What can't be reproduced is filed under "SAP e-rec system hickup" . If there are more candidates with this scenario I would try to find out what happend on 12/12/2011 to narrow the issue. Perhaps this leads to a setup issue which has to be fixed or it might be a bug in the SAP HR - ERec integration. Once this is investigated and you are at least in the process of fixing it in a way it will not happen in future I would cleanup the data (if it is a setup error) or request a cleanup report together with the fix (if it was an SAP bug).
Kind Regards
Roman
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.