on 12-10-2008 1:41 PM
Hello,
We recently upgraded to E-Recruiting 603 (E-Recruiting 6.0 + EhP3, SP2) and we are using the WD4A technology for our applicant UIs.
We have a need to create multiple Application Wizards for our different Business Units, as some business units need fewer steps in their road map pattern. We have activated the BADI 'HRRCF00_DETERMINE_APPL_CONFIG'.
We are looking for some advise and help to proceed with task. Any help will be greatly appreciated.
Thank you
Louis R Joseph
Hello Louis,
Please check us out to get on-demand answers to all your SAP needs. We are launching shortly.
http://www.linkedin.com/e/gis/889747
http://www.twitter.com/spinact
Best,
Monty
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nidhi,
We are not ready to implement yet. But when we do, we will follow Roman's recommendation to call a specific application configuration based on the Business Unit's branch. This will work for us.
I will post my updates on this thread. Please keep us posted on how you implement this functionality.
Regards
Louis
Hi Louis,
Yes you can do that by context configuration. But please ensure you clone the candidates role and assign the relevant BSP parameters (with the right context) in the portal roles.
Best Regards
G Raj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Raj,
We have created a configuration id and defined the roadmap pattern specific to this id. The BADI has also been activated and corresponding entries maintained, but we don't see any results. Where will the recruiters have the option of picking the new App wizard for a specific posting?
Please advise.
Louis Joseph
Hi Louis,
the BAdI does not allow the recruiter to choose a configuratíon activly. The BAdI can be used to determine the correct application configuration depending on the runtime information. It gets key information which allows you to get the requisition key and based on this key you can get its information. So you can code a CASE statement that for a certain company, branch or target group a specifice application configuration shall be used.
If you really have a need for the active selection of the configuration you would have to reuse one of the requisition attributes or add customer one, but usually the determination based on standard attributes is more efficient and reduces error probability.
To integrate the roadmap pattern you defined in SPRO you have to create an application configuration for the application wizard WD4A applcations and set the ID as component condiguration key of the roadmap. You can add other component configurations for the other parts of the application if you have additional requirements concerning hiding fields, ... .
Best Regards
Roman Weise
Roman,
Thank you for your response.
One of our Business Units has a requirement to pick different application wizards based on the nature of the job postings. In SAP's IMG documentation (as mentioned below), it states that different configurations of the App Wizard can be called depending on the Job posting.
===================
Flexibilization Possibilities
On the front-end server, perform the IMG activity BAdI: Specify Application Configuration for Application Wizards (IMG node: Flexibilization -> Frontend) if you want to call different configurations of the application wizard depending on the relevant job posting.
==================
As per your mail, I assume that by different configurations, SAP means hiding fields or changing texts and not different road map patterns.
Please advise.
Thank you
Rita
Hi,
both requirements for the WD4A user interface of e-recruiting are linked. Defining customer roadmap patterns and hiding fields are both done using the application configuration of the web dynpro application.
For hiding fields you define a component configuration. For the roadmap you customize a customer roadmap pattern in the IMG. Both can then be then added to a application configuration. The component configurations are set to the components in the application and the id of your customer roadmap pattern is set as configuration id of the roadmap component in the application configuration.
To call the configuration you have to implement the business add in. In the easiest case you just return one configuration but as you get the application name and the posting information, information from which you can get the requisition data you can implement more complex dependencies. E.g. you get the requisition key, check the company of the branch set in the requisition and if it is your special business unit you set the special application configuration.
Best Regards
Roman
Roman,
Thanks again for your response.
We have already used the component configuration to hide a few fields, rename the labels of the fields and create custom fields.
Since we have implemented the BADI, we will follow your recommendation to call a specific application configuration based on the Business Unit's branch. I will keep this thread open until we are able to complete this successfully.
Thank you very much for your response.
Regards
Louis
User | Count |
---|---|
99 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.