2u00BA scenario E-Recruiting architecture without replicating users in back-end

[former_member233007]

Hi,

I know there are 3 scenarios in E-Recruiting architecture. We are going to the 2º scenario. We have installed a Front-End NW 7.01 with the E-Recruiting Module. In the back-end we have a ECC with the HR module. What I have seen is that the user candidates replicate themselves from the front-end to the Back-End. I want to know if in this scenario is there a way to not replicate the candidate users in the back-end

Best regards.

Pablo Mortera.

[NicoleGeischnek]

Hello,

I assume you have set the HR backend also as WD backend with parameter RECFA UI2BL and BL2UI in table T77S0. If you don't want to use a distributed WD scneario please delete the values.

Regards

Nicole

[Former Member]

Hi,

which note are you referring to, especially which scenario?

Are only internal candidate replicated in the HCM system or also external ones.

If also internal are created in the HCM system, you misunderstood the setting of the T77S0 switches. All switches and BADIs named in the IMG and notes must only be set / activated in the e-recruiting system, except of RECFA DTCBA, which needs to be set in the HCM-system only.

Best regards

Sebastian

[former_member233007]

Hi,

We are in the 2-A Scenario:

- NW 7.0 + E-Recruiting (Front-End)

- ECC 6.0 + HCM (Back-End)

Best regards.

[Former Member]

Hi,

either you have activated the BADIs in HCM and you are synchronising within the e-recruiting module installed in your HCM system, or you misunderstood the 2-A scenario.

Activating parameters like RECFA UI2BL and RECFA BL2UI has nothing to do with the 2-A scenario.

It only means, that the e-recruiting system gets an additional server for candidates.

If you set the RECFA UI2BL in e-recruiting to the HCM system you are running the one instance scenario.

Edit:

@Nicole: synchonous post

Best regards

Sebastian

Edited by: Sebastian Menger on Apr 26, 2011 2:29 PM