Now in time, all the big organisations are busy in implementing ESS & MSS. Though most of the third party HRMS systems are in place in a sound number of organisations, still in order to incorporate all the IT aka HR applications in one platform i.e. in SAP , ESS & MSS functionality are being implemented everywhere. In this blog, I am herewith mentioning the required JCO connections , which need to be created to fetch information/data from back-end R3 (ECC) system. Following are the list of major JCO connections for ESS / MSS configuration :-
Please note that before configuring JCO connections, make sure that SLD connection is working from EP server.
On clicking TEST CONNECTION, it should show following message :-
If any issue appears in SLD connection testing, then MAINTAIN JCO CONNECTION & CREATE JCO CONNECTION tabs get disabled.
Let’s proceed for JCO connection creation now . Follow the below link to get the JCO connection creation page :-
http://<FQDN of EP host name>:<port> => Click on WEB DYNPRO => Click on CONTENT ADMINISTRATOR => Then MAINTAIN JCO CONNECTION .
Now follow the below points for creating above mentioned JCO connections :-
1. Select the JCO connection to be configured & click on CREATE.
2. Then give the client number of ECC server (R3).
3. Then select “Local J2EE Connection”.
4. Now main thing is to select the type of data to be fetched :-
4.1. Select META DATA for any JCO connection named *Metadata* .
4.2. Select APPLICATION DATA for any JCO connection named *Model data* or *Application data*.
5. Now select the corresponding R3 system and on the next screen give login credentials :-
5.1. Mention login credential of R3 system for METADATA.
5.2. Mention SSO login ticket for MODEL DATA / APPLICATION DATA.
6. At last click on FINISH and test the connection by pinging and also by clicking on TEST button.
NB: In case you test through any UME ID (which is not existed in back-end), then it will give following error while TESTING Application Data / Model Data JCO connections :-
com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Ticket contains no / an empty ABAP user ID (see note 1159962)
You can ignore this error. Also make sure that the maintained login ID has enough authorization to fetch data from R3 system.
I hope this blog would add some positiveness in solving JCO issues 😎 .