ESS Configuration

[Former Member]

I got error like "Personnel number not yet assigned" on ESS webdynpro page (except Overview Page) after ESS configuration was completed. I did have my user id assigned to a PERNR and the connection test of system "SAP_WebDynpro_XSS ", "SAP_ITS_XSS" and "SAP_ITS_EBU" are successful. I do not really understand why Overview page can display and individual service page cannot be displayed.

Anyone has idea?

Thanks,

Rose

[Former Member]

Hi Rong Lin

Can you please guide me how you did the following system creation in the portal system configuraiton step of "System landscape editor"

SAP_WebDynpro_XSS ", "SAP_ITS_XSS" and "SAP_ITS_EBU"

I have problem in setting up the above systems and test their connections. Please help.

Regards

[Former Member]

Hi Dhina,

To create a system in the portal follow the below steps

Steps to connect an SAP R/3 system to SAP NetWeaver Portal using an iView

1) Go to System Administration

2) Go to System Configuration

3) Go to Portal Content (Right Side Panel), open that folder.

4) Right Click on Portal Content, a Panel is displayed select "System (from Template)".

5) That will display a new view on right side, now select "SAP system using dedicated application server" from

the existing templates. (Other templates are possible - for example, load balanced or through a SAProuter connection string).

For this exercise, we'll use the simplest type.

6) Choose next

7) Give the System Name and System Id (which are mandatory fields) incase you want to give any brief notes

about the system then give them in the "Description" field.

😎 Open the Newly Created System.

9) Now when you want to create a New System, you have to fill four Properties they are:

"Connector" - contains basic connectivty details

"Internet transaction Server (ITS) - if you wish to use SAPGUI for HTML and/or IACs",

"Web Application Server" - if you wish to access BSPs and/or Web Dynpro for ABAP and

"User Management".

You also need at least one "System Alias" has to be defined from the Display drop down menu.

Make sure you have set end user access in the Permissions drop down menu to all users who need to access the system

10) Select "Connector" property, now fill the required fields such as:

a) Application Host (should be fully qualified hostname) - Give the R/3 "Application Name",

which can be obtained from the SAP Logon Pad (check what R/3 system you are using, right click on it , go to the properties,

it will open a window which has the Application Server Name.

b) Logical System Name - Give the logical name as defined in the backend system

c) SAP Client - Check the Client in the backend system and give the appropriate number (3 digits)

d) SAP System ID(SID)* - Check the R/3 properties and give the check for System ID

e) System Type* - Since we are connecting to R/3, select SAP_R3 system.

f) System Number - This is a two digit number that you can find in the SAP Logon Pad

11) Select "Internet transaction Server (ITS)" property, now fill the required fields like

a) ITS Description à Give some Description

b) ITS Host Name - Same as "Application Host" of R/3 (when integrated ITS) and should be attached with the

port number of ITS Server (to get port number detailed description is given below). ex: hostname : port number

c) ITS Path - To get the path along with the port number you have to Log on to R/3 system. Use the

Transaction Code "SICF", it opens a new window go to:

default_host -> sap -> bc -> gui -> sap -> its -> webgui -> SAP GUI for HTML -> right click on

that and click "Test Service'. This will open a new window, on the address bar you will find the "port number", and

the path something like (/sap/bc/gui/sap/its/webgui). Use the path after the port number.

d) ITS Protocol - There are two protocols "http" & "https", select the appropriate protocol which is

visible when you opened "Test Service" window.

12) Select "Web Application Server" property , now fill the required fields like

a) Web AS Description -> Give some Description

b) Web AS Host Name - same as ITS Host Name

c) Web AS Path - usually /sap/bc/bsp/sapd)*

Web AS Protocol - should be same as the ITS Protocol.

13) Select "User Management" property, now fill the required fields like

a) Authentication Ticket Type - Since we are not using SSO leave the field

empty i.e. put in select mode. (Please note that longer term you will probably want to use SSO)

b) Logon Method - Select UIDPW.

c) User Mapping Type - In case you have administration rights then you choose "admin" or in case you

just have user rights then choose "user", better go for "admin/user".

14) Since all the required fields are filled appropriately now create a System Alias name, this can be done by following steps:

a) go to Display -> Select "System Aliases" give some Alias Name, let's call it "SAP_R/3"

15) Now that System is created we have to create a iView which will display the given Transaction Code.

16) Go To "Content Administration".

17) Go To "Portal Content".

18) Go to Portal Content (Right Side Panel), open that folder

19) Right Click on Portal Content, a Panel is displayed select "New" -> iView

20) Select iView template, click next

21) Select "SAP Transaction iView" from the list of templates available. Click next.

22) Give the iView name and iView ID. Incase you want to give any brief notes about the iView then give it in "Description" field. Click next

23) Select "SAP GUI for HTML" radio button. Click next

24) Now select the system which you have create "SAP_R/3", give some Transaction Code, say SE12 (Dictionary Display). Click next and Finish.

25) Now Preview the iView

26) You will see a new Window where in SE12 Dictionary Display window is displayed.

if anything else pls let me know

rewards points if helpful / solved.

pls close the thread if "problem solved ".

Thank you,

With Regards

Vijai

[Former Member]

This problem is more related to backend configuration.

[Former Member]

hi rose,

i am a little confused with you question, can you please explain in details...thanks

rahul

[Former Member]

The ESS Overview Page can display correctly, however when I clicked each webdynpro service (e.g. who is who), page displayed error "Personnel number not yet assigned". I did have a valid PERNR assigned to my id. Please see java error below:

Personnel number not yet assigned:com.sap.pcuigp.xssfpm.java.FPMRuntimeException: Personnel number not yet assigned

at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:111)

at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:121)

at com.sap.pcuigp.xssutils.pernr.FcEmployeeServices.initPernr(FcEmployeeServices.java:267)

at com.sap.pcuigp.xssutils.pernr.FcEmployeeServices.onInit(FcEmployeeServices.java:222)

at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServices.onInit(InternalFcEmployeeServices.java:249)

at com.sap.pcuigp.xssutils.pernr.FcEmployeeServicesInterface.onInit(FcEmployeeServicesInterface.java:135)

at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface.onInit(InternalFcEmployeeServicesInterface.java:183)

at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface$External.onInit(InternalFcEmployeeServicesInterface.java:243)

at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)

at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)

at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)

at com.sap.xss.hr.wiw.FcWiwBusinessLogicComp.onInit(FcWiwBusinessLogicComp.java:217)

at com.sap.xss.hr.wiw.wdp.InternalFcWiwBusinessLogicComp.onInit(InternalFcWiwBusinessLogicComp.java:414)

at com.sap.xss.hr.wiw.FcWiwBusinessLogicCompInterface.onInit(FcWiwBusinessLogicCompInterface.java:115)

at com.sap.xss.hr.wiw.wdp.InternalFcWiwBusinessLogicCompInterface.onInit(InternalFcWiwBusinessLogicCompInterface.java:298)

at com.sap.xss.hr.wiw.wdp.InternalFcWiwBusinessLogicCompInterface$External.onInit(InternalFcWiwBusinessLogicCompInterface.java:358)

at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)

at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)

at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)

at com.sap.xss.hr.wiw.selection.VcWiwSelectionComp.onInit(VcWiwSelectionComp.java:212)

at com.sap.xss.hr.wiw.selection.wdp.InternalVcWiwSelectionComp.onInit(InternalVcWiwSelectionComp.java:206)

at com.sap.xss.hr.wiw.selection.VcWiwSelectionCompInterface.onInit(VcWiwSelectionCompInterface.java:162)

at com.sap.xss.hr.wiw.selection.wdp.InternalVcWiwSelectionCompInterface.onInit(InternalVcWiwSelectionCompInterface.java:144)

at com.sap.xss.hr.wiw.selection.wdp.InternalVcWiwSelectionCompInterface$External.onInit(InternalVcWiwSelectionCompInterface.java:220)

at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)

at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)

at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)

at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)

at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:748)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:283)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)

at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)

at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)

at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)

at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1246)

at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:354)

at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:547)

at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:591)

at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:822)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)

at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:313)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:684)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(AccessController.java:215)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

[Former Member]

thats strange...try checking the details of the personal number you assigned throught the transaction PA30 and check if the infotype 105 exists for that employee with your portal user name

cheers

[Former Member]

Hi,

Go to the transaction code : HRUSER

See if the pernr is assigned to the employee.

Reward points if handy!

Regards,

Sandeep Tudumu