E-Rec: RFC connections

[Former Member]

Hello Experts,

Using constellation 3, referring note 1017866, we have SAP ECC and E_REc on different SAP boxes.

We have two RFCs created:

ECC->E-Rec : A

E-Rec->ECC : B

Should I mantain "B" in following node:

SAP E-Recruiting->Technical Settings->User Interfaces->Candidate->Front-End Candidate->Enter RFC Destination of Receiving Backend System

  Please guide.

  Thanks,

SAP E-Rec Guy

[Former Member]

Hi,

I guess these RFC are to be maintained in case you front end application layer to be maintianed separately wrt the Database layer.

If you are applicable on this scenario then only you maintain these switches.

Regards

Vijay

[Former Member]

Hello All,

I am able to register as an external candidate using -> /sap/bc/webdynpro/sap/hrrcf_a_candidate_registration.

I am able to login using the alias of this new user, however get same internal error -

Category               ABAP Programming Error

Runtime Errors         UNCAUGHT_EXCEPTION

Except.                CX_WD_ABORT_MESSAGE_MANAGER

ABAP Program           CL_WDR_MESSAGE_MANAGER========CP

Application Component  BC-WD-ABA-RUN

Date and Time          10.04.2012 06:43:17

What happened?
    The exception 'CX_WD_ABORT_MESSAGE_MANAGER' was raised, but it was not caught
     anywhere along
    the call hierarchy.

    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program
     'CL_WDR_MESSAGE_MANAGER========CP' has to be
    terminated.

The same error comes up even when I directly test the link -> /sap/bc/webdynpro/sap/hrrcf_a_candidate_profile_ext friom SE80 -> package - PAOC_RCF_UI_SELF_SERVICES. However the user if I check in ST22 is different (its my user as compared to ALIAS user when logging after registration and using ALIAS.)

Please guide, what am I missing?

Regards,

SAP E-REC Guy

[Former Member]

Hello Experts,

Can anyone please help...? I am still experiencing the above mentioned error, when I click on Candidate Profile -> My Profile after registration.

Regards,

SAP E-Rec Guy

[dsharmak]

Hello,

Did you check :

Please check if there is any blank entry in the table v77RFC_RM_IDC, If so remove those entries.

Please apply the note 1467003 in your system.

[Former Member]

Hello Deepak,

Yes, I have already deleted entries from the mantain roadmap scenarios table (V77RCF_RM_IDC). Also, have consulted SAP Basis team and they have adviced that this note is not applicable as it is for lower level release.

Can you please help? There is something else which I am missing.

Thanks in advance!

Regards,

SAP E-Rec Guy

[dsharmak]

Hello,

Could you please check you have activated all the services of E-Recruiting through sicf.

Have you modified the WDA application, If yes there should be problem with your customization, Should check with your standard application.  Plesae check your salary ranges defiend in the spro should not have overlapping values.

Please review the note.

1017866    Consulting note: Candidate scenarios using Web Dynp 

[dsharmak]

Dear,

Yes you need the communication from

ERC -> ECC 'B', As you would be require that candiate data to be transferred on ECC, So communication from both the sides are required.

For more information you can check the note 997181, it contains all the documentation.

Best Regards,

Deepak.

[Former Member]

Hello Bharat/Deepak,

Thanks for your reply.

I am still experiencing problems with the connections. We are on EhP5, using third constellation. Maintained following settings in SAP E-Rec box:

Node -> SAP E-Recruiting->Technical Settings->User Interfaces->Candidate->Front-End Candidate->Enter RFC Destination of Receiving Backend System  ---- with RFC connection to Backend system B (RECFA UI2BL)

Node -> SAP E-Recruiting->Technical Settings->User Interfaces->Candidate->Backend Candidate ---- with following entries ---

B	01	LCT CSL Lock Activated (With Reference Follow-Up)
A	01	LCT CSL Lock Activated (With Reference Follow-Up)

In the SAP ECC box, have maintained switch in T77S0 - RECFA BL2UI with connection to frontend - A.

Now when I test the link from SE80 for external candidate profile, link ->

http://XXXXXXXXXX/sap/bc/webdynpro/sap/hrrcf_a_candidate_profile_ext?sap-language=EN&sap-client=100

I get internal error with termination type as RABAX_STATE and when I check ST22, I see following errors:

Category               ABAP Programming Error

Runtime Errors         UNCAUGHT_EXCEPTION

Except.                CX_WD_ABORT_MESSAGE_MANAGER

ABAP Program           CL_WDR_MESSAGE_MANAGER========CP

Application Component  BC-WD-ABA-RUN

I have not asssigned any service user in the backend system (SAP ECC). Is it the reason? or am I missing something more that needs to be mantained in the front-end (E-Rec) box? Please guide the next step to quell this internal error.

Regards,

SAP E-Rec Guy

[dsharmak]

Dear,

please check the slg1 log, what is the error you are facing, that needs to be corrected.

Best Regards,

Deepak.

[dsharmak]

If possible attach the logs here also..

[Former Member]

Hello Deepak,

I dont see any entries in SLG1, however, runtime errors in st22. Below is the error which is displayed in the portal:

• The following error occurred in system ERD : Internal Error
• The error occurred on application server vdhserdci_ERD_60 and in work process 1 .
• The termination type was: RABAX_STATE
• The ABAP call stack was:
  Method: REPORT_MESSAGE of program CL_WDR_MESSAGE_MANAGER========CP
  Method: IF_WD_MESSAGE_MANAGER~REPORT_T100_MESSAGE of program CL_WDR_MESSAGE_MANAGER========CP
  Method: INITIALIZE of program /1BCWDY/0AXWG9ARMJEAAV0DG5Z6==CP
  Method: WDDOINIT of program /1BCWDY/0AXWG9ARMJEAAV0DG5Z6==CP
  Method: IF_WDR_COMPONENT_DELEGATE~WD_DO_INIT of program /1BCWDY/0AXWG9ARMJEAAV0DG5Z6==CP
  Method: DO_INIT of program CL_WDR_DELEGATING_COMPONENT===CP
  Method: INIT_CONTROLLER of program CL_WDR_CONTROLLER=============CP
  Method: INIT_CONTROLLER of program CL_WDR_COMPONENT==============CP
  Method: INIT of program CL_WDR_CONTROLLER=============CP
  Method: INIT of program CL_WDR_CLIENT_COMPONENT=======CP

ST22 lists below details:

What happened?

    The exception 'CX_WD_ABORT_MESSAGE_MANAGER' was raised, but it was not caught

     anywhere along

    the call hierarchy.

      Since exceptions represent error situations and this error was not

    adequately responded to, the running ABAP program

     'CL_WDR_MESSAGE_MANAGER========CP' has to be

    terminated.

What can you do?

    Note down which actions and inputs caused the error.

    To process the problem further, contact you SAP system

    administrator.

    Using Transaction ST22 for ABAP Dump Analysis, you can look

    at and manage termination messages, and you can also

    keep them for a long time.

Please let me know what other details I can provide to you for help.

Regards,

SAP E-Rec Guy

[dsharmak]

Hello,

Please check if there is any blank entry in the table v77RFC_RM_IDC, If so remove those entries.

Please apply the note 1467003 in your system.

Best Regards, Deepak..

[Former Member]

Hi,

Are you using a user with a candidate object assigned?
For testing purpose you can use program: RCF_CREATE_USER and create a candidate for your own user.

BR
Christian

[Former Member]

Hi there,

I presume that you are working on EHP5. Coming to your scenario- front-end (only external candidates), back-end internal candidates + database.

The node says to enter RFC destination of backend system for database (where external candidate data is saved). Since ERC database and ERP are on single back-end system we obviously denote

ERC->ECC  -  'B'.

Regards,

Bharat