JCO connections required -- ESS BP

[Former Member]

Hi All,

I have a question regarding the JCO connections to be maintained after installation of the ESS BP

SAP_R3_HumanResources

SAP_R3_HumanResources_MetaData

SAP_R3_Financials

SAP_R3_Financials_MetaData

SAP_R3_SelfServiceGenerics

SAP_R3_SelfServiceGenerics_MetaData

SAP_R3_Travel

SAP_R3_Travel_MetaData

Why cant we connect to the backend using only one JCO ?

Also how does it recognize which JCO's r required ? I mean is it based on the type of iviews or roles ?

Thanks,

Veena.

[Former Member · Accepted solution]

Hi Veena ..

In a pure layman language ..

consider all vehicles (data) travelling from one location (portal) to another (ECC) using one road (one Jco) and consider having 8 different options..

Manageble, good load balanced connections...

Cheers!!

AShutosh

[Former Member]

Hello Veena,

In addition to a what Ashutosh mentioned, the ESS/MSS apllications contains different web-dynpro applications. Each of them is grouped into different catagory and a specific JCO is used for them which is encoded into the code.

So if you want to use Travel related applications you have to maintain

SAP_R3_Travel

SAP_R3_Travel_MetaData

Regards

Deb

[Former Member]

Hi,

Each application being part of the Business package uses these predefined JCo names thus it is mandatory to same JCo names as given in the guide.

If you create your own applications then you can use your own created JCo with different names but for the standard ones you have to use the ones specified as the appln will not identify JCo's other than these.

Regards,

Akshay

Reward if helpful.

[Former Member]

hi Veena,

sent a config guide to your id.....refer page 7.

that is what I used while establishing JCO connections.

it works

cheers......