Ansicht
Dokumentation
RCF_UI_PARAMS - Assign Parameters to Parameter Types
ROGBILLS - Synchronize billing plans ABAP Short ReferenceThis documentation is copyright by SAP AG.
In this IMG activity, you assign parameters to the interface parameter types for each scenario.
Parameter Types
CautionNote that you must always enter the technical names of BSP applications in lowercase.
The following parameter types are available:
| BSP Application | Parameter Type | Description | Scenarios | |
|---|---|---|---|---|
| hrrcf_appl_hist | APPL_POL_EXT | URL Application Guidelines for External Candidates | Talent Warehouse | |
| hrrcf_appl_hist | APPL_POL_INT | URL Application Guidelines for Employees | Talent Warehouse | |
| hrrcf_cand_reg | PRIV_EXT | URL Data Privacy Statement | Talent Warehouse | |
| hrrcf_cdcy_proc | MAX_VISIBLE_ITEMS | Maximum Number of Visible Tab Pages | Applicant Tracking | |
| hrrcf_cdcy_proc | VISIBLE_ROWS | Rows in List of Assignments for Requisition | Applicant Tracking | |
| hrscp_cdcy_proc | MAX_VISIBLE_ITEMS | Maximum Number of Visible Tab Pages | Applicant Tracking/Succession Planning | |
| hrscp_cdcy_proc | VISIBLE_ROWS | Rows in List of Assignments for Requisition | Applicant Tracking/Succession Planning | |
| hrrcf_searchhelp | REFCODE_CUR_PUBL | Current Publications Only | Reference Code Search (Recruiter) | |
| hrrcf_searchhelp | REFCODE_LINES_HITLIST | Rows in the Hit List | Reference Code Search (Recruiter) | |
| hrrcf_qa_screen | MAX_RDB | Number of Responses with Radio Buttons | Questionnaire | |
| hrrcf_qa_screen | HIDE_NO_ENTRY_RDB | Suppress No Entry Radio Button | Questionnaire | |
| hrrcf_qa_pview | HIDE_NO_ENTRY_RDB | Suppress No Entry Radio Button | Questionnaire | |
| hrrcf_tpi_reql | ENABLE_COPY_POSTINGS | Copy Job Postings with Requisitions | Requisition Maintenance (Requester) | |
| hrrcf_search | UNICODE_CHKS_IN_SRCH | Language-Independent Search in Non-Unicode System | Search | |
| hrrcf_act_proc | BUTTON_REFRESH | Display Refresh Button for Activity Lists | Applicant Tracking | |
| hrrcf_req_mnt | ORGACC | Tab page Account Assignment | Requisition Maintenance | |
| hrrcf_req_mnt | ORGJOB | Tab page Organizational Unit and Job | Requisition Maintenance | |
| hrrcf_req_mnt | ORGPOS | Tab page Positions | Requisition Maintenance |
Notes on Parameter Types APPL_POL_EXT and APPL_POL_INT
The application guidelines are included in the BSP application hrrcf_appl_hist.
Notes on Parameter Type PRIV_EXT
The data privacy statement is integrated in the following BSP pages:
- hrrcf_cand_reg (External Candidate: Registration)
- hrrcf_unrg_appl (Unregistered Candidate: Application Wizard)
- hrrcf_profile (Candidate Profile (-> Release of Profile Internal / External Candidate))
You can store different data privacy statements for the various BSP pages if you need to.
For example, you may require a different data privacy statement for a candidate who registers in the Talent Pool from the one you use for an external candidate who applies with the help of the application wizard. This data privacy statement should say that data entered by an unregistered candidate is retained in the system even if the candidate cancels the application.
Notes on Parameter Type MAX_VISIBLE_ITEMS
You can use this parameter type to specify the maximum number of visible processes in the form of tab pages in the Assigned Candidates for Requisition/Application Group view or the Assigned Candidates for Succession Plan view.
Notes on Parameter Type VISIBLE_ROWS
You can use this parameter to specify the number of rows in the list in the Assigned Candidates for Requisition/Application Group view or the Assigned Candidates for Succession Plan view. SAP recommends the value 25, as higher values are performance-intensive when structuring the BSP page.
Notes on Parameter Type REFCODE_CUR_PUBL
You can use this parameter to prefill the Current Publications Only checkbox on the user interface for the reference code search. If the parameter is set (parameter = X), then the checkbox is also set on the user interface. In this case, only publications with the status Released are selected for which the current date lies in the publication period.
If you want to use this parameter type, you must assign it to the BSP application hrrcf_searchhlp.
Notes on Parameter Type REFCODE_LINES_HITLIST
You use this parameter type to determine the number of lines in the hit list of the reference code search.
If you want to use this parameter type, you must assign it to the BSP application hrrcf_searchhlp.
Notes on Parameter Type MAX_RDB
You use this parameter type to determine the maximum number of response options for questions that are to be displayed in the questionnaire using radio buttons. If the specified number is exceeded, the system displays a dropdown list box instead of radio buttons.
The parameter type is not included in the Characteristics of Questionnaire view. When the parameter type is used, radio buttons are also displayed here to present an overview of all response options with assigned attributes.
If you want to use this parameter type, you must assign it to the BSP application hrrcf_qa_screen.
Notes on Parameter Type HIDE_NO_ENTRY_RDB
For questions in questionnaires, where radio buttons are used to depict the responses, the system displays the No Entry radio button as the first response option. In this way, it is possible for the user to leave a question unanswered.
You can use the parameter type HIDE_NO_ENTRY_RDB (parameter value X) to hide this radio button.
You can assign the parameter type to the BSP applications hrrcf_qa_screen (Display of a questionnaire) or hrrcf_qa_pview (Display of technical characteristics of a questionnaire).
Notes on Parameter Type ENABLE_COPY_POSTINGS
When copying requisitions by the requester, it can be useful to copy the requisitions together with the assigned job postings.
You can use the parameter type ENABLE_COPY_POSTINGS (parameter value X) to enable this behavior.
In the standard system, this parameter type is not set so that only the requisitions themselves are copied.
Notes on Parameter Type UNICODE_CHKS_IN_SRCH
All SAP E-Recruiting search scenarios enable a language-independent search in a non-Unicode system if the value All is selected for the language on the user interface in the General Search Settings. This is the default setting (parameter has the value 'X').
You can switch off the language-independent search by assigning the value ' ' to the parameter type. The All selection option for the language is then no longer possible in the General Search Settings.
Notes on Parameter Type BUTTON_REFRESH
You can use the parameter type to specify whether a pushbutton is displayed above the Overview of Activities list so that you can refresh the list when processing activities in Activity Management.
The following parameter values are possible:
X: Pushbutton is displayed
' ': Pushbutton is not displayed (default setting)
If you want to use this parameter type, you must assign it to the BSP application hrrcf_act_proc.
Parameter Types ORG* (Container element Organizational Data in Requisition Maintenance)
Parameter Type ORGACC
You can use this parameter type to specify whether the Account Assignment tab page is hidden or displayed when creating organizational data for a requisition.
The following parameter values are possible:
X: Tab page is not displayed
' ': Tab page is displayed (default setting)
Parameter Type ORGJOB
You can use this parameter type to specify whether the Organizational Unit and Job tab page is displayed or hidden when creating organizational data for a requisition.
X: Tab page is not displayed
' ': Tab page is displayed (default setting)
Parameter Type ORGPOS
You can use this parameter type to specify whether the Position tab page is display or hidden when creating organizational data for a requisition.
X: Tab page is not displayed
' ': Tab page is displayed (default setting)
Note
If you set the parameter X for all three parameter types, then these settings are ignored and all three tab pages are displayed. To hide all three tab pages, you must delete the corresponding container element from the container sequence. To do this, you must redefine the container sequence delivered in the standard system using the IMG activity Modify Container Sequences.
Parameter Types SF* (Smart Forms)
E-Recruiting uses a series of Smart Form forms to display data overviews and job postings. The corresponding forms are part of the standard system and are used automatically by the system if you do not make any alternative Customizing settings.
You can replace the standard forms with your customer-specific Smart Form forms. You can use the following combinations of BSP applications and parameter types, which are available in table T77RCF_UI_PARAM for this.
Standard Forms for Job Postings:| BSP Application | Parameter Type | Standard Form | Job Posting |
|---|---|---|---|
| hrrcf_pinst_pbl | SF_PUBL_EXT | HRRCF_PUBLICATION_EXT | External |
| hrrcf_pinst_pbl | SF_PUBL_INT | HRRCF_PUBLICATION_INT | Internal |
Standard Forms for Data Overviews:
| BSP Application | Parameter Type | Standard Form | Data Overview |
|---|---|---|---|
| hrrcf_req_dovr | SF_VIEW_PINST | HRRCF_DATA_SUMMARY_POST_INST | Posting Instance |
| hrrcf_req_dovr | SF_VIEW_POST | HRRCF_DATA_SUMMARY_POSTING | Job Posting |
| hrrcf_req_dovr | SF_VIEW_REQ | HRRCF_DATA_SUMMARY_REQUISITION | Requisition |
| hrrcf_cand_dovr | SF_VIEW_CAND | HRRCF_CANDIDATE_PREVIEW | Candidate |
| hrrcf_appl_dovr | SF_VIEW_APPL | HRRCF_DATA_SUMMARY_APPLICATION | Application |
| hrrcf_cdcy_dovr | SF_VIEW_CDCY | HRRCF_DATA_SUMMARY_CANDIDACY | Candidacy |
| hrrcf_oi_sovr | SF_VIEW_POS | HRRCF_DATA_SUMMARY_POSITION | Position |
| hrrcf_oi_covr | SF_VIEW_JOB | HRRCF_DATA_SUMMARY_JOB | Job |
| hrrcf_oi_oovr | SF_VIEW_ORG | HRRCF_DATA_SUMMARY_ORGUNIT | Organizational Unit |
| hrrcf_dec_dovr | SF_VIEW_DDOVR | HRRCF_DECISION_OVERVIEW | Decision Process |
| hrrcf_wiza_dovr | SF_VIEW_APPL | HRRCF_APPL_WIZAPREVIEW | Candidate from Application Wizard |
| hrrcf_tg_dovr | SF_VIEW_TG | HRRCF_DATA_SUMMARY_TG | Talent Group |
| hrrcf_rpact_ovr | SF_VIEW_RP_ACT | HRRCF_DATA_SUMMARY_RC_PLAN | Process Template |
| hrrcf_audt_dovr | SF_VIEW_AUDIT | HRRCF_DATA_SUMMARY_AUDIT_TRAIL | Audit Trail |
| hrscp_cand_dovr | SF_VIEW_CAND_SCP | HRSCP_SUCCESSION_PROFILE | Candidate (Succession Planning) |
| hrscp_req_lst | SF_VIEW_PLAN_SCP | HRSCP_SUCCESSION_PLAN | Candidate List Succession Plan (Succession Planning) |
| hrscp_req_dovr | SF_VIEW_REQ_SCP | HRSCP_DATA_SUMMARY_REQUISITION | Succession Plan (Succession Planning) |
| hrrcf_act_dovr | SF_VIEW_ACT | HRRCF_DATA_SUMMARY_ACTIVITY | Activity |
| hrrcf_sgr_ovr | SF_VIEW_SGR | HRRCF_DATA_SUMMARY_SGR | Support Group |
You can choose to display the forms in HTML or PDF format (Adobe Portable Document Format). To do so, assign the parameter type DISPLAY_PDF in table T77RCF_UI_PARAM to the BSP applications that display a form. If the parameter is set, the form is displayed in PDF format. Otherwise, it is displayed in HTML format.
In the standard system, the parameter type DISPLAY_PDF is assigned to the following BSP applications and is active (form display in PDF format):
| BSP Application | Parameter Type | Standard Form | Data Overview | |
|---|---|---|---|---|
| hrrcf_appl_dovr | DISPLAY_PDF | HRRCF_DATA_SUMMARY_APPLICATION | Application | |
| hrrcf_cand_dovr | DISPLAY_PDF | HRRCF_CANDIDATE_PREVIEW | Candidate | |
| hrrcf_cdcy_dovr | DISPLAY_PDF | HRRCF_DATA_SUMMARY_CANDIDACY | Candidacy | |
| hrrcf_req_dovr | DISPLAY_PDF | HRRCF_DATA_SUMMARY_REQUISITION | Requisition | |
| HRRCF_DATA_SUMMARY_POSTING | Job Posting | |||
| HRRCF_DATA_SUMMARY_POST_INST | Posting Instance | |||
| hrrcf_pinst_pbl | DISPLAY_PDF | HRRCF_PUBLICATION_EXT | External Job Posting | |
| HRRCF_PUBLICATION_INT | Internal Job Posting | |||
| hrrcf_dec_dovr | DISPLAY_PDF | HRRCF_DECISION_OVERVIEW | Decision Process | |
| hrrcf_wiza_dovr | DISPLAY_PDF | HRRCF_APPL_WIZA_PREVIEW | Candidate from Application Wizard | |
| hrrcf_tg_dovr | DISPLAY_PDF | HRRCF_DATA_SUMMARY_TG | Talent Group | |
| hrrcf_rpact_ovr | DISPLAY_PDF | HRRCF_DATA_SUMMARY_RC_PLAN | Process Template | |
| hrrcf_sgr_dovr | DISPLAY_PDF | HRRCF_DATA_SUMMARY_SGR | Support Group |
- In the SAP Form Builder (transaction SMARTFORMS), copy the relevant standard form to a customer-specific form. Refer to the tables mentioned above for the names of the possible copy templates.
- Adjust the layout of the copied form to suit your requirements. The data that can be output in this form is specified on the form interface.
- Caution:
- You may not change the form interface of the copied Smart Form from that specified on the standard form.
- In table T77RCF_UI_PARAM, create a new entry for the relevant combination of BSP application and parameter type and assign the name of your customer-specific form as the parameter. Refer to the tables above to find out what combinations of BSP application and parameter type are recommended.
The system uses your customer-specific form instead of the standard form to display a job posting or a data overview.
Caution:- Smart Form forms are not automatically activated in the target system when they are transported, for example from a test system to a productive system. Therefore, activate your customer-specific Smart Form forms manually after a transport using transaction SMARTFORMS. If the Smart Form forms are not activated, the relevant BSP applications display error messages instead of the job posting or data overview.
Parameters for Reports
The Recruiter can send the results of reports on the dataset to his or her e-mail address.The list output can be in either PDF or HTML format.
The parameter DISPLAY_PDF is assigned by default to the BSP application HRRCF_QUERY and is not set. In other words, the default format is HTML.
You can integrateCrystal Reports on the standard report page. This enables the Recruiter to access and start reports on the Crystal Report initial page by means of a link in E-Recruiting. To do so, enter the URL for the BSP applications as the parameter value for CRYSTAL_URL.
The parameter CRYSTAL_URL is assigned to the BSP application HRRCF_QUERY by default. No URL is stored there, in other words, Crystal Reports are not integrated.
CPI1466 during Backup Vendor Master (General Section)
This documentation is copyright by SAP AG.
Length: 24713 Date: 20240523 Time: 205857 sap01-206 ( 233 ms )
