on 06-24-2013 9:57 AM
Hi experts,
I am having problem in this application : HRRCF_A_STARTPAGE_INT_CAND .
Webdynpro component : HRRCF_C_PERSONAL_DATA_UI .
For this component we have two applications :
External candidates : HRRCF_A_STARTPAGE_EXT_CAND
Internal Candidates : HRRCF_A_STARTPAGE_INT_CAND
I am attaching images for both applications :
External candidates : HRRCF_A_STARTPAGE_EXT_CAND
Internal Candidates : HRRCF_A_STARTPAGE_INT_CAND
Now in this application on portal i am not getting Address details and other details.
Even i have test this application manually by se80 , and getting same result .
So it is sure that , there is some problem with application only HRRCF_A_STARTPAGE_INT_CAND .
it may happen that it could be hidden somewhere at interface or personalization etc, but not getting how to correct it .
So , pls help .
Hi Pankaj,
Please check the two following method in the window WDW_MAIN
HANDLEEXTERNAL_CANDIDATE
HANDLEINTERNAL_CANDIDATE
Depending if it's an internal or external candidate, the code will change the visibilty flag for comm data, which is also used to display/hide the addresses
Best regards,
Mathieu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Guys,
Yes it was same problem..
Now its working absolutely fine...
Thanx for helping .
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Gerd and Msthieu,
thanx for replying .
Yes i checked methods .
HANDLEINTERNAL_CANDIDATE
here com_data was set to abap_false .
and for external candidate it was set abap_true .
So, I guess this is probably b the solution .
i have changed it, but my portal server is down and m not able to test it .
So , i will let u know after testing.
Regards,
Pankaj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Pankai,
in your case the UI Element Visibility is bound to the context. Check e.g. the UI element address in view VW_PERSONALDATA, the visible attribute is bound to context element UI.COMM_DATA_VISIBLE. In standard no configuration exists for component HRRCF_C_PERSONL_DATA_UI.
The value of the context element is set in window WDW_MAIN by the handler methods of the Inbound-plugs EXTERNAL_CANDIDATE and INTERNAL_CANDIDATE. That means the visibility of these elements depends on the type of candidate internal or external as usually the data for internal candidates should only be edited on the main HR system and not in eRec.
Best regards,
Gerd
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Pankaj,
Have you checked if there are any enhancements done to supress these sections from within the WDDOMODIFYVIEW method? Or may be the corresponding view sections have been marked for deletion in enhancement mode?
Regards,
Uday
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi UDAY,
I have checked the component HRRCF_C_PERSONL_DATA_UI .
VIEW : VW_PERSONLDATA .
Method : WDDOMODIFYVIEW .
wd_comp_controller->set_navigation_forbidden( iv_nav_forbidden = abap_false ).
endmethod .
Thats it .
And there is no enhancement for restricitng view and etc .
I think that it is somewhere hidden in application .
Because its working perfectly for HRRCF_A_STARTPAGE_EXT_CAND but not for
HRRCF_A_STARTPAGE_INT_CAND .
even i test this application in Quality which is totally untouched but same result there also .
SO , pls tell me how to look at it .
Regards,
Pankaj .
Hi Pankay,
in case what Uday already said doesn't apply; also check whether implicit personalization has been done to the corresponding applications via WDA-App WD_ANALYZE_CONFIG_USER. In case this does not apply either, check for explicit personalization, i.e. the particular settings in the component configurations (if there are any).
Cheers, Lukas
User | Count |
---|---|
84 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.