SP13 technical SCAs (J2EE, JTECHS, BUILDT) don't appear in CMS inbox

[Former Member]

Hi all,

I have to modify ESS Web Dynpros. I already did this on ESS SP7 (working with NW SP11). But the customer has applied ESS SP9 (and NW SP13) so I need to redo my modifications on the new Web Dynpro sources.

We copied ESS_SP9.sca and PCUIGP009.sca in CMS inbox, and also the NW SP13 technical SCAs (SAP-JEE, SAP_BUILDT and SAP_JTECHS) which have by default dependecies with any Software Component.

The problem is when I click on the dropdown list in the "Check-in" tab, I can check-in the SP9 SCAs (ESS and PCUIGP), but the 3 SP13 SCAs do not appear !

And I am afraid I will need them when I wan't to create my Web Dynpro projects on the DCs I wan't to modify...

Does someone have explanation or advice ?

Thank you very mucj in advance.

Best Regards,

Julien

[russell_scherbarth]

In case no one has found the answer for this, here is what I did for 6.40 level JAVA components.

On service marketplace, download the appropriate SAPBUILDT*.SCA file (ex. SAPBUILDT21P_1-20000950.SCA). Open up the SCA in a compression program (like WinRAR) and extract the CBSplugins.sda. Open CBSplugins.sda file and extract the SAP_BUILDT.SCA, SAP_JTECHS.SCA, and SAP-JEE.SCA files. Place these SAP files in usr\sap\trans\CMS\inbox of your NWDI server. Now when you refresh the Check-In tab in NWDI it should show the components.

Hope that helps.

Russ.

[joachimvanpraet]

Hi Julien,

I have the same problem in SP15. I can import SAP_ESS, SAP_MSS and SAPPCUI_GP but I can't find the files SAP-JEE, SAP_JTECHS and SAP_BUILDT, although I copied them to the CMS inbox-directory:

ESPUX037:root:/> pwd
/usr/sap/trans/CMS/inbox
ESPUX037:root:/> ls -al
total 1316742
drwxr-xr-x   2 root     sapsys      1024 Jun 27 19:23 .
drwxr-xr-x   3 root     sapsys        96 Jun 27 19:13 ..
-rw-rw-r--   1 hrdadm   sapsys   264140413 Jun  8 23:30 ESS10P_1-10002965.SCA
-rw-rw-r--   1 hrdadm   sapsys   40729755 Jun  8 23:18 LMTOOLS15_0.SCA
-rw-rw-r--   1 hrdadm   sapsys   25618727 Jun  8 23:30 MSS10P_1-10002964.SCA
-rw-rw-r--   1 hrdadm   sapsys   29774554 Jun  8 23:18 NWMADMIN15_0.SCA
-rw-rw-r--   1 hrdadm   sapsys   14554012 Jun  8 23:28 PCUIGP010P_1-20000568.SCA
-rw-rw-r--   1 hrdadm   sapsys   110091485 Jun 20 13:32 SAPBUILDT15_0-20000950.SCA
-rw-rw-r--   1 hrdadm   sapsys   12213578 Jun 20 13:37 SAPDEVINF15P_4-20000267.SCA
-rw-rw-r--   1 hrdadm   sapsys   2142404 Jun 20 13:34 SAPDEVINFF15_0-20000268.SCA
-rw-rw-r--   1 hrdadm   sapsys   31522607 Jun  8 23:05 SAPJEE15_0.SCA
-rw-rw-r--   1 hrdadm   sapsys   37518763 Jun  8 23:03 SAPJEECOR15_0.SCA
-rw-rw-r--   1 hrdadm   sapsys   51875077 Jun  8 23:05 SAPJTECHF15_0.SCA
-rw-rw-r--   1 hrdadm   sapsys   53949659 Jun  8 23:11 SAPJTECHS15_0.SCA

[Former Member]

Did you specify the appropriate Usage Dependencies for your SC in the SLD?

[Former Member]

Hi Joachim,

have you checked note 891223? The size of the SAP_BUILDT archive is much too large, the real SAP_BUILDT.SCA for import should be ~30MB, definitely not larger than 100MB.

Regards,

Marc

[Former Member]

Let me know , if you find a solution to your problem. I am presently in similar situation. Thanks in advance

[Former Member]

Hi,

I have same issue, CMS check in not showing any of technical SCAs (J2EE, JTECHS, BUILDT) and I checked at OS level there is no CMS directory under /usr/sap/trans.

I have /usr/sap/trans/EPS/in not /usr/sap/trans/CMS/in in our NWDI.

Can you please tell me shall I need to create CMS/in under /usr/sap/trans and then import all sca files??

I went through our installation steps document and realized that we haven't created /usr/sap/trans/CMS/in file system,

Please suggest me does we need both /usr/sap/trans/EPS/in and /usr/sap/trans/CMS/in ??

Thanks & Regards

Srinivas.

[Former Member]

Create /usr/sap/trans/CMS/inbox and put the SCA files in there. You should then be able to check them into the track. If not, use the 'Configure Check-In...' button to specify an additional directory to watch (/usr/sap/trans/CMS/inbox).

[former_member1191927]

Hi Pascal,

I also have the same situation like "Srinivas a". We are on EP 7 SP13. We also do not have \usr\sap\JTrans\CMS\inbox\ folder. We have /usr/sap/trans/EPS/in.

So, as you suggested, I tried creating new folder /usr/sap/trans/CMS/inbox and moved "SAPJTECHF13_0-10003468.SCA

SAPJTECHS13_0-10003467.SCA

SAPJEE13_0-10003469.SCA

SAPBUILDT13_0-10003479.SCA" files to that folder.

But still, I cannot see these files under the Check-in tab of the Transport Studio. So I cannot check-in these files. I cannot proceed without this and I am getting build erros if I try to create a DC in a SC under this track. Can you please help me in this?

thanks,

Hari

[Former Member]

I have another question :

A Patch Level 1 exists for ESS SP9. Do I have to import ESS patch0 and THEN ESS patch1 ? Or importing directly ESS patch1 is OK ?

Regards,

Julien

[Former Member]

Java Patches are cumulative, you can directly apply patch1.

Cheers!!

[Former Member]

Hi Julien,

Do you have any design/technical documents pertaining to Web Dynpro XSS/ESS Code? Looks like SAP’s XSS/ESS code seems to follow a certain design principals and standard naming convections like Cc.., Fc.. , Vc.. Do you happen to have any documentation on any of these naming convections and design principles behind this code?

XSS Web Dynpro code uses all the advanced Web Dynpro programming, like Guided Procedures and Floor Manger Patterns. Kind of hard to get documentation/tutorials in this area, do you have any documentation in this?

Please let me know if you want me to start a thread on this topic, kind of deviating from your issue.

Cheers!!

[Former Member]

Hi Phani,

unfortunately I didn't have much time to make reverse engineering on how ESS was developped. For sure it may help to understand the concept of floor plan manager.

Concerning the modifications I made my work was the following :

- Identify the Development component containing the view I needed to modify. For this I just used the URL of the page.

- Find the view in the Development component. By the way almost (yes, there are exceptions) all the views are stored in a Web Dynpro component named 'Vc...'

- Add the models I needed.

- Try and find in the context the data that I needed.

- Add hook methods in the standard events and customer-specific UI elements calling my own coding.

I didn't manage to get useful documentation on this. My best help were the SDN tutorials and SDN Web Dynpro forum.

Cheers,

Julien