cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

E-Recruiting and SAP ECC 6.0 on 2 separate instances

Former Member
0 Kudos
183

Hi Expert,

I have a strange case where customer is requested to implement eRec and ECC on a separate instance,

but eRec servers will take much time to be shipped and be ready for configuration.

so they suggested to do eRec config. In ECC server to save time then move these config. later to eRec server once servers landed.

I’m worry about ECC server as we have to activate Business functions and apply SAP notes for erec on ECC server.

my question is this scenario a practical!!

Accepted Solutions (1)

Accepted Solutions (1)

dsharmak
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello,

Yes this scenarion is practical, We have lot of customers who have applied the EREC on the same as on ECC system. but in separate EREC performance would be fast. and in Integrated a bit slow.

For more claification . Please check the note 997181 it contains both the instances.

Best Regards,

Deepak..

Former Member
0 Kudos

Hi ,

Thanks for reply,

Hope you have read my message well.

My question is working with configuration in ECC and move theses configuration to eRec server later is a practical scenario !!

and what can be done in ECC and move later to ERE server ?

Thanks.

Former Member
0 Kudos

Dear,

actually in theory it is possible as long as you make sure that Netweaver SPS and E-Rec SPS will be the same on the E-Rec Server afterwards.

Activation of BF for E-Rec on ECC will have no effect on other parts of ECC:

The only thing which is really important is the employee integration part.

If you activate that on ECC for each employee a candidate will be created. If you want to do just your developments on ECC make sure that this part will not go to ECC production.

Additionally the employee integration on a separate instance will work completely different. You need to do that part again.

Besides that customizing and developments can be transferred via transport to a separate instance. But that's it.

My recommendation is, get an old machine from somewhere to start implementation on a separate instance and then just switch the physical server if it is available. The scenario above is possible but bearing risks.

Best regards


Sebastian

Answers (0)