ERECRUITMENT 6.0 - Mass activation of BSP's in QA

[Former Member]

We have successfully completed unit testing EREC functionalities and are in the process of transporting configuration to QA.

Our Technical team activated all the standard EREC BSP's when we did the install, it did create a transport request. Works fine.

Issue: Technical team is concerned that if all the BSP's are migrated to QA, then, there would be potential issues.

I do not think it is a valid concern. Any one has pointers?

BTW: In SE80, I see that there are around 80 EREC and around 15 SP BSP's and there is no option to individually go into each of these BSP's and test it out..

Question: Is there any issue in transporting the change request containing all the BSP's with the user assignment to QA??

Thoughts appreciated.

[Former Member]

Sunil,

How r u, long time no talk...

Couple of things :

The activation of BSPs will not be included in transport request. Only any changes to BSP for example assigning service users in log on data will be included in transport request.

I dont see any issue transporting those BSP changes, also I hope there are no core modifications done to std delivered BSPs'.

Lastly, testing URLs is easy way to test the eRecruit services/applications.

regards

Sridhar

[Former Member]

Hi Sunil

During the initial configuration, you just have to activate the BSPs using

TCode SICF->default_host->sap-bc->bsp->sap . You need not go and activate individual BSPs through SE80 unless you wish to make any change sin the standard BSP applications. Also, remember there are a couple of BSP applications in EREC namely HRRCF_UNRG_SRCH that do not require login for this you will have to assign a Service User in SICF in your QA environment also. All these things will not generate a transportable request.

Regards

Vipul

[Former Member]

By default e rec bsps are active......

You activate the applications access in sicf transaction.............

You do not activate the bsp applications thru se80.......

because you are changing the applications itself and it creates a workbench request which you are not supposed to transport........

Regards,

Divya