Jco Connections Required for Ess Mss Configuration

SAP NetWeaver Administrator: Step by Step process to establish JCO connections for ESS & MSS Configuration Posted by Nilutpal Sharmah Jul Jul 30, 2013

Hi, 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 :1. SAP_EC SAP_ECC_Fi C_Finan nancia cials ls 2. SAP_EC SAP_ECC_Fi C_Finan nancia cials_ ls_Meta MetaData Data 3. SAP_ SAP_R3 R3_F _Fin inan ancia cials ls 4. SAP_R3 SAP_R3_Fin _Financ ancials ials_Me _MetaDa taData ta 5. SAP_R3 SAP_R3_Hu _HumanR manReso esourc urces es 6. SAP_R3_HumanR SAP_R3_HumanResour esources_Me ces_MetaData taData 7. SAP_R3 SAP_R3_Se _SelfSe lfServi rviceG ceGene eneric rics s 8. SAP_R3_SelfSe SAP_R3_SelfServiceG rviceGeneric enerics_Meta s_MetaData Data 9. SAP_ SAP_R3 R3_T _Tra rave vell 10.SAP_R3_Travel_MetaData 11.WD_ALV_METADATA_DEST 12.WD_ALV_MODELDATA_DEST 13.WD_MODELDATA_DEST 14.WD_RFC_METADATA_DEST

Please note that before configuring JCO connections, make sure that SLD connection is working from EP server.

Generated by Jive on 2014-12-10+01:00 1

SAP NetWeaver Administrator: Step by Step process to establish JCO connections for ESS & MSS Configuration

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:// :

=> 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

.



Regards, Nilutpal. 4502 Views

Shakeel Samdani in response to Nilutpal Sharmah on page 6 Nov 6, 2014 12:12 AM Hi Niluptal, Our ESS version was 633 sp00,portal is 7.31,backend ecc was ecc6 eehp4,every thing wasworking good,but recently did a trail upgrade of ecc from ehp4 to ehp7, Now we are facing issue in ess portal...when we try to edit or delete a family member name in dependent and beneficiary it is giving java lang error,rest of the functionality is working properly,I have tried by upgading ess to sp01 but no luck...still giving the same error.

Let me know if u came across such error.

Thanks in advance Shakeel Richa Shrivastava in response to ashish vikas on page 4 Mar 26, 2014 2:26 PM Hi Thanks, SLD connection to Portal was not working . Once this was up and pinging fine in Portal , we were able to check this JCO connectiin maintained and up and runing in Solman. So no need to create this JCO in Portal. And this resolved the issue. Many Thanks, Richa ashish vikas in response to Richa Shrivastava on page 4 Mar 25, 2014 8:23 AM No, you don't need to create JCO RFC Connections in ABAP under TCP/IP Connections in SM59. with best regards ashish Richa Shrivastava in response to Nilutpal Sharmah on page 5 Mar 24, 2014 8:05 AM Hi Nitupal,



I understand that the 14 JCO connections you mentioned in your documents are to be created in Portal . Do we also need to create these JCO RFC Connections in ABAP under TCP/IP Connections in SM59? In our system I do not see any of these connections maintained neither in EP nor in ECC in SM59. Kindly advice. Many Thanks, Richa Nilutpal Sharmah in response to Graham Slater on page 5 Sep 4, 2013 3:48 PM Glad to know that Graham Graham Slater Sep 4, 2013 2:49 PM Nice work - just what I needed today! Thanks. Chen Miky Aug 28, 2013 3:36 PM very good, thanks you very much although we use NWBC instead of portal for MSS/ESS Lukáš Horváth Aug 5, 2013 10:30 AM Perfect & helpfull! Thank you Nilutpal Sharmah in response to SUJIT SHARMA on page 5 Jul 30, 2013 1:39 PM Hey Thanks Sujit !! SUJIT SHARMA Jul 30, 2013 12:27 PM Nice documentation Nilutpal.... Thank you for sharing..... added to Favorite in Twitter ..

!!

Regards-SUJIT Omkar Bhagwan Jul 30, 2013 10:42 AM Thanks, nilutpal aakash bhatter Jul 30, 2013 10:31 AM Hi Nilutpal,



Very Informative Regards, Aakash Bhatter. Nilutpal Sharmah in response to Ranjith Jacob on page 6 Jul 30, 2013 9:38 AM Thanks Ranjith ... JCO connection behaves as middleware component that enable a JAVA system (here it's EP) to communicate back-end ABAP SAP system (here it's ECC). Generally two types of JCOs are there : 1. Inbound (From JAVA to ABAP system), 2. Outbound (From ABAP to JAVA system). Above mentioned JCO connections are used to call ABAP system from JAVA system whereas to connect ABAP to JAVA , we create JCO RFC connection & the program name needs to be maintained in the TCP/IP RFC created in ABAP system. When we browse EP home page http::/irj , it contains various applications like Travel management, HR data fetch (Who am I ) etc. which are co-related with back-end system. So, in order to fetch data directly from EP frontend these JCO connections are required.

I hope this has cleared your query

.

Regards, Nilutpal. Ranjith Jacob Jul 30, 2013 8:31 AM Hi ,Nilutpal Good blog. Please share some light on the usage of these jco's. Thanks, Ranjith


Jco Connections Required for Ess Mss Configuration

Recommend Documents