Hi María and Ralf,
First of all SAP deliver sources and archives for both the ESS/MSS business package and the PCUI_GP framework to enable you to change the sources. This is why the JDI is a reflection on how the backend applications have previously been delivered.
Having said that, it is not at first clear how to view or change dependent development components.
You can get a head start by following the SAP note 872892 JDI cookbook for ESS customers. This assumes you have setup a JDI.
When creating a development track for example to change the standard ESS content you have to specify in the CMS Landscape configurator exactly which SAP software component you want to change. The list of software components actually come from the SLD... its called the CIM list.
When you select SAP_ESS (verison 100) from the list, a default distribution of Source & Archive is selected. After closing the selection window, you should also see 4 dependent components SAP-JEE, SAP_BUILDT, SAP_JTECHS, SAPPCUI_GP with archive selected. Unfortunately you cannot change this!
SAPPCUI_GP contains the framework used by ESS. However if we want to browse the source code of say the floor plan manager, then we need the source code! Incidently we also need the source code if we want to debug ESS and MSS!
A trick I found to obtain the source code was while selecting SAP_ESS, also to select SAPPCUI_GP. That way you automatically get the default source & archive selection. However the trick has a side effect, or what I consider to be a bug with the CBS. Namely, SAPPCUI_GP is no longer considered a dependent of SAP_ESS. While you can import into development, checkout the source code, debug etc, when you come to make changes and use the JDI to activate changes through to consolidation, you find that the build breaks. Or more specifically in the CBS request log you receive messages saying that the public dependent development component cannot be found... build is "BROKEN". This is because the CBS has not checked the dependencies given in the SLD! Further still the SAPPCUI_GP software archive is not moved to the import queue of consolidation.
A temporary work-around is to define two tracks: One where SAPPCUI_GP is a dependent of SAP_ESS where you only receive the archive, but can make changes and activate changes etc. The second track contains then both SAP_ESS and SAPPCUI_GP as main line software components with source and archives. The 3 dependent libraries JEE, BUILDT and JTECHS are also loaded. With the second track you should be able to look at the framework source code and debuf to find out what is going on.
Perhaps someone else has another work-around, but so far I have not seen anything on this forum or in the SAP notes.
So far we have added a translation in dutch which was missed from the standard ESS content and also removed the team calendar button from the leave reqest application as my client has not configured this is ECC-R/3.
I found the WebDynPro source code hard to follow as there is no documentation or training on how the framework actually works. Luckily I did find from a link on SDN a pdf describing ESS & WebDynPro. It was originally from the rampup kit. It is called ESS & WebDynPro, by Ralf Halbedel and Christain Wiele. If you can't find it, send me your email address and I'll post it to you.
Hope that helps,
Jonathan.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.