ESS Debugging

Hi portal gurus,
Iam trying the blog
"Simple way to debug ESS and MSS Web Dynpro Java based applications - Very useful technique"
at Simple way to debug ESS and MSS Web Dynpro Java based applications - Very useful technique
In this blog by debugging for the ess screen by the link
http://<host>:<port>/webdynpro/dispatcher/sap.com/essinpdata/Per_Personal_IN?sap.xss.debug=
This link is checking the personaldata edit . by the extension "dispatcher/sap.com/essinpdata/Per_Personal_IN"
How can i check for another links in ess screens like the webdynprojava iviews in travel,working time etc
Thanks
Prasad

Simple option would be to add the application parameter in the corresponding iview as mentioned in the blog.
You can enable debugging option by passing sap.xss.debug=t as Application Parameters in the iView properties.
However, If you add it to the iView properties, all the users accessing this iView will be seeing additional debug information.
The other option is to access the applications directly via URL.
The format you will need to use is:
http://<host>:<port>/webdynpro/dispatcher/<Application Namespace>/<Application Name>?sap.xss.debug=t
You can find the properties application namespace and application name from the corresponding iview properties.
All the ESS iviews are present under:
Content Administration - Portal Content - Content provided by SAP - End User Content - Employee Self-Service - iviews
- Shanti

Similar Messages

Debugging Workflow in ESS/MSS module .

Hi,
I know the stpes to debugging simple workflow and trouble shooting the same, but now
I want to know the debuggibg workflow steps for workflow running with ESS/MSS module Framework,
The scenario is
Its actually Approving Forms in ESS/MSS module, The Employee applying medical leave from his Id, then it will go to first level approver inbox once he approve it goes to second level approver inbox once he approves then it will go to third level approver inbox and he is the final level approvel once he approve the proces will be done.
The problem is, After the second level approver approves the form its updating wrong third level approver so its not comming to third level approver inbox. The workflow is designed under Z class but I dont have update cone in Z class methods.
The updation part is comming under standard ess/mss framework code.
So please tell me the steps how i can debugg or execute worklow in background for all the steps,
like from first step I like pass the container to second steps and goes on.
Help really appreciated.
Thanks & Regards
James.

Hi James
In ESS/MSS leave request the employee will apply the leave from portal and the workflow will triggered based on the spro which workflow template is used. Has you said that updation my custom cone. What is meant by that. Has as has i know we need to update the infotype 2001. This can be done by std FM.
To degbug.
In the put a external break point of the std FM which screen it call. I hope its called the webdypro java screen which nothing but a std FM. You need to find that FM. Then put a external breakpoint. change the user name from goto menu. Once you approve button is clicked in the portal. The debugger will open.
Regards
vijay

ESS in debugging mode

Hi All,
When an employee logs in to ESS portal, need to know how this logging on takes place in the background (ABAP code, FM etc). Need to know what FMs/BAPIs are called right from the first step where it checks the userid info in infotype 0105.
In other words, the need is to see in debugging mode while the employee logs on.
Need to know what FMs are used and where to put the breakpoints etc.
Any help will be highly appreciated.
Thanks,
Mark.

Wow! You're really asking for it eh? haha You actually will have lots going on and not sure a trace will help you make sense of it all. Just from a high-level...
(1) login into portal => userid/pword are authenticated against whatever the portal uses as a source (ldap server, portal db, R3/ system, etc). If it passes this authentication, the portal then locates the user in it's own db to find what PORTAL roles to assign to build out the user's portal specific to them.
(2) Assuming single sign-on is set up, the portal issues a SAP Logonticket that is passed to the backend systems. This Logonticket is just a fancy non-persistent, encrypted cookie that contains (a) the userid (b) the portal's "key".
(3) when the user (via the portal) makes a request to the backend system, the portal "hands" the Logonticket to the other system. The other system checks the "key" and says "ok, yep this is the portal...I trust the portal...no need to check the userfurther such as password". The backend system then will take the userid (again, no password needed) and check that that userid actually exists. Let's assume it does. As with the portal, the backend system can now determine what security authorizations and roles (don't confuse with a portal role!) the user has.
(4) Now...that gets us to the "login" part of the backend. In the case of your ESS needs, we now could be playing with any number of possibilities.
   -ITS service which in turn is really running a SAP transaction (most common for ESS)
   -Webdynpro which is a Java app that calls SAP via BAPIs/RFCs
   -direct GUI access (via SAP WINGUI launched from portal)
   -other (custom apps that call RFCs/BAPIs)
   With all of the above there is usually some code in there that right off the bat will take the userid and try to find what employee it matches. Userid (ie. a system user record) is linked to employee records via infotype (kind of a HR table) 0105 (communication), subtype 0001 (SAP Userid). Given the current date, it will try to find which employee record has this userid assigned to IT0105 ST0001 (lots/most of HR records are date driven). If no employee record is found for the userid, you typically get an error that states something to the effect of "this userid does not match an employee record for this period".
From this point, all of the "what's going on" largely depends on what ESS service you are trying to perform (address change, benefits enrollment, etc).
Hope this helps.

Debugging and ESS

Hi Portal Gurus,
how can i able to debug the ess scenarios by keeping a break point in r3 backend i have already made the ep server on debuggable mode.
Thanks
prasad

Use "external breakpoint" in your function module....
You just then have to access ESS application from browser....which directly or indirectly calls that function module....
Thats it...nothing else you have to do.......

Debug ESS Application

Hi Frds,
I want to debug the ESS Application which was accessed through ITS. want to see how data was posted and displayed. we have an issue one of the user was unable to access the expense report after clicking the Create expenses report link. Please help me regadring how to debug the ESS Application..
Regards,
Narendra.

Hi Pavan,
Thanks for your quick reply but i tried previously as you said i put the external break point in the program, which was identified with the TRIP Tcode and when logged into the same userid into ESS after clicking the create expense report the break point was not triggering. The program that i found was SAPMP56T is it the correct program for navigating to expense report?
Regards,
Narendra.

Debugging ESS Transactions

I have checked out my ESS PDATA application and trying to debug the navigation (we want to make a read-only version).
It deploys and runs on my local server. When I try to create a debug session on the application, NWDS throws and error stating "no tab group defined for launch configuration type com.sap.ide.webdynpro.projectbrowser.launch.configtype.debug.
I know this works with local apps not checked from the DTR. Why can't I debug my app and what does this error mean?

Hi,
You should create a debug configuration.
Go to Run --> Debug. Create a debug configuration for Web Dynpro application. Then select WebDynpro Application in the tab. In that you will have to go and select the Debug server fromt he second tab to configure the Debug Server.
Which NWDS version are you using ?
Have you created Debug configuration for your Web Dynpro application ?
Regards,
Ashwani kr Sharma

Can ESS webdynpro debug?

Hi can we debug ESS webdyn pro DC components from NWDS just like normal web application?
Thanks
Praveen

Hi praveen,
Hope your WAS server is running in debug mode
Click on Run->Debug Dialog
Under the node Remote Java application
Right click select new
specify your debug port and server name add the Dc to the source.
Once this done, put the break point
Launch your debugger
Refer this link,
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/849170e3-0601-0010-d59e-ddfce735fac5
Regards,
Sunaina Reddy T

Weblog for Simple way to debug ESS and MSS Web Dynpro Java applications

Here is the link to the new Weblog topic "Simple way to debug ESS and MSS Web Dynpro Java applications"
/people/yugandhar.reddy/blog/2011/03/26/simple-way-to-debug-ess-and-mss-web-dynpro-java-based-applications--very-useful-technique

Thanks Siddharth. I was trying as you suggested, I was trying to add the link to the FAQ's but looks like the wiki is locked or I dont have permission to create a page in it. Is there any other way to do it?
Edited by: Yugandhar Reddy on Mar 28, 2011 5:04 PM

Debugging ESS applications

Hi All,
We are having ESS applications which brings Employees general data on portal. But in general data employees orgnisation unit is incorrect .
I want to know how to debug this application so as to check where exactly it is picking the wrong org.unit for an employee in R3-HR.
Regards,
Ganesh

Ganesh,
Instead of debugging the ess application, go to PA30 and check the org unit in infotype 1 which is valid for current date.
It could be a possibility that you employee is assigned to a position which is in the incorrect org unit.
check in transaction ppose. Locate the org unit mentioned on ESS application and check if your employee holds any position in the org unit.
However, if you insist on debugging, you can put external breakpoint in the relevant BAPI to debug. List of RFCs called is mostly documented in SAP help. for eg:
http://help.sap.com/saphelp_erp60_sp/helpdata/en/f6/263359f8c14ef98384ae7a2becd156/frameset.htm
Find your service in SAP help and find out the relevant BAPI. Put external breakpoint for employee user ID and then login to ESS using same ID. You should be able to debug then
Regards,
Ashutosh

Debugging in ESS

Hello,
I am trying to debug the ESS Banks Application where i want to get to the ABAP code which is throwing messages on the portal ...like invalid bank key and others....I set an External break point in HRXSS_PER_P0009_US Function group ...but it does not stop there in R/3....
Please help.

please follow the steps
1. Run transaction sicf
2. press F8
3. Follow menu EDIT->DEBUGGING->ACTIVATE DEBUGGING
4. You will find a screen that has a check box "System Debgging" select that and click on activate
5. Most important "YOU NEED TO LOGON TO R/3 WITH THE USER THAT YOU ARE USING FOR ESS ACCESS"
6. Step 5 means to start session debugger you need to logon with the same in user respective in R/3 and Portal else nothing will work.

Portal Runtime Error in ESS iview

Hi All,
I have implemented ESS 50.4 on EP 6.0 SP9. For SAP IAC iviws i am getting following error.
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/AFDB/Role/ESSRole/Office/SAPInbox/SAPInbox
Component Name : com.sap.portal.appintegrator.sap.IAC
Error in executing a process for compilation.
Exception id: 03:10_06/05/06_0031_4156850
See the details for the exception ID in the log file.
In the log file i am getting following error message.
com.sap.engine.services.connector.exceptions.BaseResourceException: "ConnectionManager" is closed. Possible reasons: 1) connector "SAPEPPDB" is stopped or not started, 2) Connector service is stopped or has not been started.
Please help me to resolve the problem its very urgent.
Regards,
Vaishali

Hi Vaishali,
Nice to hear from you again.
Hope you are doing good.
I am not sure whether the error that you mentioned is the right one for this issue, but if this is the case, just to inform you that a new note has been released in this regard. Please check sap note: 1600085 as well and set the parameters accordingly.
Usually we need to see what kind of code is using the concerned connection.
Incase the issue persists, proceed as follows (it wil be better to do this when the value of the number of connections is really high, so that identifying the root cause can be easy.
1)
Set the severity of "com.sap.engine.services.connector.jca.ConnectionHashSet" to DEBUG.
You can change the severity of a location using the guide in the link below:
http://help.sap.com/saphelp_nwce72/helpdata/en/47/af551efa711503e10000000a42189c/frameset.htm
2)
- connect to the AS-JAVA via telnet
- then execute these commands:
> add connector
> switch_debug_mode SAPEPPDB (or the datasource name)
> jump (to go to the next servernode if you have multiple ones)
> add connector
> switch_debug_mode SAPEPPDB
... and so on on all the servernodes
- then wait for a few hours in order to see the connections not being
released
- go back to the telnet console and call:
> list_conn SAPEPPDB -showTrace > server0.txt
> jump
> list_conn SAPEPPDB -showTrace > server1.txt
... and so on on all the servernodes
The serverX.txt files will be generated in the ../j2ee/cluster/server directories. Just check them to get more info.
Thank you!
Kind Regards,
Hemanth
SAP AGS

Error in Creating Project in ESS.

Hi All,
I have a requirement where in , there is change in the personal data screen of ESS package. We configured the NWDI server. But when i am trying to extract the ess/in/pdata dc from the ESS SC. It is failing during the project Build and throwing the below error.
Mar 8, 2009 12:12:17 PM /userOut/Development Component (com.sap.ide.eclipse.component.provider.listener.DevConfListener) [Thread[ModalContext,5,main]] ERROR: ess/in/pdata: Build failed for sap.com/ess/in/pdata(sap.com_SAP_ESS_1) in variant "default": [Error]   Generation failed!
Build log -
Development Component Build (2009-03-08 12:11:23)
Component name: ess/in/pdata
Component vendor: sap.com
SC compartment: sap.com_SAP_ESS_1
Configuration: NDI_ESS2_D
Location: NDI_ESS2_D
Source code location: http://sapdev:50200/dtr/ws/ESS2/sap.com_SAP_ESS/dev/inactive/DCs/sap.com/ess/in/pdata/_comp/
DC root folder: C:\Documents and Settings\sk46196\.dtc\0\DCs\sap.com\ess\in\pdata\_comp\
DC type: Web Dynpro
Host: HIC-PCS31092
DC Model check:
   All used DCs are available locally
   validating dependency to build plugin "sap.com/tc/bi/bp/webDynpro"
   validating dependency to public part "default" of DC "sap.com/tc/cmi"
   validating dependency to public part "default" of DC "sap.com/tc/ddic/ddicruntime"
   validating dependency to public part "default" of DC "sap.com/tc/ddic/metamodel/content"
   validating dependency to public part "default" of DC "sap.com/tc/wd/webdynpro"
   validating dependency to public part "default" of DC "sap.com/tc/logging"
   validating dependency to public part "default" of DC "sap.com/tc/wdp/metamodel/content"
   validating dependency to public part "default" of DC "sap.com/com.sap.aii.proxy.framework"
   validating dependency to public part "default" of DC "sap.com/com.sap.aii.util.misc"
   validating dependency to public part "default" of DC "sap.com/com.sap.exception"
   validating dependency to public part "default" of DC "sap.com/com.sap.mw.jco"
   validating dependency to used DC "sap.com/pcui_gp/xssfpm"
   validating dependency to used DC "sap.com/pcui_gp/xssutils"
   validating dependency to used DC "sap.com/ess/per"
   DC model check OK
Start build plugin:
   using build plugin: sap.com/tc/bi/bp/webDynpro
   starting build plugin from : C:\Documents and Settings\sk46196\.dtc\0\DCs\sap.com\tc\bi\bp\webDynpro\_comp\gen\default\public\webDynpro\
Build Plugin 'WebdynproPlugin', Version 7.00 SP 9 (645_VAL_REL, built on 2006-08-23 19:48:09 CEST)
   development component: ess/in/pdata (sap.com)
      software component: SAP_ESS (sap.com)
                location: NDI_ESS2_D
                    type: Web Dynpro
           build variant: default
         source location: http://sapdev:50200/dtr/ws/ESS2/sap.com_SAP_ESS/dev/inactive/
       plugin start time: 2009-03-08 12:11:39 GMT+05:30 (IST)
                 Java VM: Java HotSpot(TM) Client VM, 1.5.0-b64 (Sun Microsystems Inc.)
General options:
convert *.xlf to *.properties: yes
include sources for debugging: yes
Used compilation public part does not exist: C:\Documents and Settings\sk46196\.dtc\0\DCs\sap.com\pcui_gp\xssutils\_comp\gen\default\public\FPMUtils\
Used compilation public part does not exist: C:\Documents and Settings\sk46196\.dtc\0\DCs\sap.com\ess\per\_comp\gen\default\public\InternationalPersInfo\
Warning: Source folder does not exist, will be ignored: META-INF
Warning: Source folder does not exist, will be ignored: src/mimes
Warning: Source folder does not exist, will be ignored: src/configuration
Plugin initialized in 1.625 seconds
Preparing data context..
No 'default' JDK defined, will use running VM.
Data context prepared in 8.89 seconds
Executing macro file..
Using macro file:     C:\Documents and Settings\sk46196\.dtc\0\DCs\sap.com\tc\bi\bp\webDynpro\_comp\gen\default\public\webDynpro\macros\build.vm
Creating output file: C:\Documents and Settings\sk46196\.dtc\0\DCs\sap.com\ess\in\pdata\_comp\gen\default\logs\build.xml
Macro file executed in 1 second
Starting Ant..
Using build file:     C:\Documents and Settings\sk46196\.dtc\0\DCs\sap.com\ess\in\pdata\_comp\gen\default\logs\build.xml
Using build target:   build
Generation folder:    C:\Documents and Settings\sk46196\.dtc\0\t\7F9C993F9CD60BA2D12EBC39ED1E9345
Using Ant version:    1.6.2
compile:
      [echo] Starting dictionary generator
     [ddgen]
     [ddgen] [Info]    Property deployment is true: Deployment information is provided!
     [ddgen] [Info]    Property sourcepath: C:\Documents and Settings\sk46196\.dtc\0\DCs\sap.com\ess\in\pdata\_comp\src\packages
     [ddgen] [Info]    Property targetpath: C:\Documents and Settings\sk46196\.dtc\0\t\7F9C993F9CD60BA2D12EBC39ED1E9345\gen_ddic
     [ddgen] [Info]    Property archivename: sap.comessin~pdata
     [ddgen] [Info]    Property vendor: sap.com
     [ddgen] [Info]    Property dcname: ess/in/pdata
     [ddgen] [Info]    Property projectlanguage: en
     [ddgen] [Info]    Property language: Available languages are automatically determined!
     [ddgen] [Info]    Property addpaths ...
     [ddgen] [Info]       SapMetamodelWebdynproContent.zip - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/tc/bi/extwd/_comp/gen/default/public/def/lib/model
     [ddgen] [Info]       SapMetamodelDictionaryContent.zip - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/tc/bi/extddic/_comp/gen/default/public/def/lib/model
     [ddgen] [Info]       SapMetamodelDictionaryContent.zip - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/tc/ddic/metamodel/content/_comp/gen/default/public/default/lib/java
     [ddgen] [Info]       sap.compcui_gpxssfpm~FloorplanManager.jar - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/pcui_gp/xssfpm/_comp/gen/default/public/FloorplanManager/lib/java
      [ddgen] [Info]    Initialize generation templates from configuration jar:file:/C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/tc/bi/extddic/_comp/gen/default/public/def/lib/java/SapDictionaryGenerationCore.jar!/DictionaryGenerationConfigurationCompiled.xml
      [ddgen]
     [timer] Dictionary generator finished in 14.733 seconds
      [echo] Starting WebDynpro generator
     [wdgen]
     [wdgen] [Info]    Property deployment is true: Deployment information is provided!
     [wdgen] [Info]    Property sourcepath: C:\Documents and Settings\sk46196\.dtc\0\DCs\sap.com\ess\in\pdata\_comp\src\packages
     [wdgen] [Info]    Property targetpath: C:\Documents and Settings\sk46196\.dtc\0\t\7F9C993F9CD60BA2D12EBC39ED1E9345\gen_wdp
     [wdgen] [Info]    Property archivename: sap.comessin~pdata
     [wdgen] [Info]    Property vendor: sap.com
     [wdgen] [Info]    Property dcname: ess/in/pdata
     [wdgen] [Info]    Property projectlanguage: en
     [wdgen] [Info]    Property language: Available languages are automatically determined!
     [wdgen] [Info]    Property addpaths ...
     [wdgen] [Info]       SapMetamodelWebdynproContent.zip - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/tc/bi/extwd/_comp/gen/default/public/def/lib/model
     [wdgen] [Info]       SapMetamodelDictionaryContent.zip - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/tc/bi/extddic/_comp/gen/default/public/def/lib/model
     [wdgen] [Info]       SapMetamodelDictionaryContent.zip - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/tc/ddic/metamodel/content/_comp/gen/default/public/default/lib/java
     [wdgen] [Info]       sap.compcui_gpxssfpm~FloorplanManager.jar - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/pcui_gp/xssfpm/_comp/gen/default/public/FloorplanManager/lib/java
     [wdgen] [Info]       webdynproruntime_repository_pmr.jar - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
     [wdgen] [Info]       webdynproservices.jar - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
     [wdgen] [Info]       jrfc.jar - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/com.sap.mw.jco/_comp/gen/default/public/default/lib/java
     [wdgen] [Info]       cmiapi.jar - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/tc/cmi/_comp/gen/default/public/default/lib/java
     [wdgen] [Info]       logging.jar - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/tc/logging/_comp/gen/default/public/default/lib/java
     [wdgen] [Info]       logging.perf.jar - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/tc/logging/_comp/gen/default/public/default/lib/java
     [wdgen] [Info]       SapMetamodelWebdynproContent.zip - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/tc/wdp/metamodel/content/_comp/gen/default/public/default/lib/java
     [wdgen] [Info]    Initialize generation templates from configuration jar:file:/C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/tc/bi/extwd/_comp/gen/default/public/def/lib/java/SapWebDynproGenerationCore.jar!/WebDynproGenerationConfigurationCompiled.xml
     [wdgen] [Info]    Generating packages/com/sap/xss/hr/per/in/pdata/model/HRXSS_PER_P0002_IN.java
     [wdgen] [Info]    Generating packages/com/sap/xss/hr/per/in/pdata/model/Hrxss_Per_Edit_P0002_In_Output.java
     [wdgen] [Info]    Generating packages/com/sap/xss/hr/per/in/pdata/model/Bapiret2.java
    [wdgen] [Info]    Generating packages/com/sap/xss/hr/per/in/pdata/model/Hrxss_Per_F4_Value.java
     [wdgen] [Info]    Generating packages/com/sap/xss/hr/per/in/pdata/model/Hrxss_Per_Modify_P0002_In_Output.java
     [wdgen] [Info]    Generating packages/com/sap/xss/hr/per/in/pdata/model/Hrxss_Per_Delete_P0002_In_Output.java
     [wdgen] WARNING: Metadata of component VcPerPersonalINOverview is not valid! ComponentUsage "//WebDynpro/Component:com.sap.xss.hr.per.in.personal.overview.VcPerPersonalINOverview/ComponentUsage:FcPersInfo", Role "UsedComponent": A minimum of 1 object(s) is required
     [wdgen] WARNING: Metadata of component VcPerPersonalINReview is not valid! ComponentUsage "//WebDynpro/Component:com.sap.xss.hr.per.in.personal.review.VcPerPersonalINReview/ComponentUsage:FcPersInfo", Role "UsedComponent": A minimum of 1 object(s) is required
     [wdgen] WARNING: Metadata of component FcPerPersonalIN is not valid! ComponentUsage "//WebDynpro/Component:com.sap.xss.hr.per.in.personal.fc.FcPerPersonalIN/ComponentUsage:FcPersInfo", Role "UsedComponent": A minimum of 1 object(s) is required
     [wdgen] WARNING: Metadata of component VcPerPersonalINDetail is not valid! ComponentUsage "//WebDynpro/Component:com.sap.xss.hr.per.in.personal.detail.VcPerPersonalINDetail/ComponentUsage:FcPersInfo", Role "UsedComponent": A minimum of 1 object(s) is required
     [wdgen] [Error]   com.sap.xss.hr.per.in.personal.overview.VcPerPersonalINOverview --> Component VcPerPersonalINOverview: Has invalid component usage 'FcPersInfo'
     [wdgen] [Error]   .Subtypes: The mapping definition is inconsistent, the mapped context element does not exist.
     [wdgen] [Error]   com.sap.xss.hr.per.in.personal.overview.VcPerPersonalINOverview --> ContextModelNode Subtypes [modelClass]: The context model node has not been bound to a model class (Hint: A Context model node has to be bound to a model class or mapped to a model node of another controller.)
     [wdgen] [Error]   .Subtypes.Subtype: The mapping definition is inconsistent, the mapped context element does not exist.
     [wdgen] [Error]   .Subtypes.Case: The mapping definition is inconsistent, the mapped context element does not exist.
     [wdgen] [Error]   .Subtypes.Stext: The mapping definition is inconsistent, the mapped context element does not exist.
     [wdgen] [Error]   .Subtypes.Del_Button: The mapping definition is inconsistent, the mapped context element does not exist.
     [wdgen] [Error]   .Subtypes.Disp_Only: The mapping definition is inconsistent, the mapped context element does not exist.
     [wdgen] [Error]   .Subtypes.Cre_Button: The mapping definition is inconsistent, the mapped context element does not exist.
     [wdgen] [Error]   .Default_Begda: The mapping definition is inconsistent, the mapped context element does not exist.
     [wdgen] [Error]   com.sap.xss.hr.per.in.personal.overview.VcPerPersonalINOverview --> ContextModelAttribute Default_Begda [referencedProperty]: The context model attribute has not been bound to a model property
     [wdgen] [Error]   com.sap.xss.hr.per.in.personal.overview.VcPerPersonalINOverview --> ContextModelAttribute Default_Begda: Context model attributes which are defined as top level attributes have to be mapped to attributes of other controllers.
     [wdgen] [Error]   com.sap.xss.hr.per.in.personal.overview.VcPerPersonalINOverview --> Component VcPerPersonalINOverview [FcPersInfo]: Component usage has no used component
     [wdgen] [Error]   com.sap.xss.hr.per.in.personal.overview.VcPerPersonalINOverview --> Component VcPerPersonalINOverview [FcEmployeeServices]: Component usage has no used component
     [wdgen] [Info]    com.sap.xss.hr.per.in.personal.overview.BizCardsView --> TransparentContainer rootContainer [Children]: Container does not contain children
     [wdgen] [Info]    Catching throwable null
     [wdgen] [Info]    com.sap.webdynpro.generation.ant.GenerationAntTaskError
     [wdgen] ERROR: Unknown exception during generation null (com.sap.webdynpro.generation.ant.GenerationAntTaskError)
     [wdgen] ERROR: Generation failed due to errors (6 seconds)
Ant runtime 22.31 seconds
Ant build finished with ERRORS
[Error]   Generation failed!
Error: Build stopped due to an error: [Error]   Generation failed!
Build plugin finished at 2009-03-08 12:12:17 GMT+05:30 (IST)
Total build plugin runtime: 38.606 seconds
Build finished with ERROR
This is coming when i am trying to create project. Though the prooject is getting created in the local NWDS but still i is not recognizing many things internally and throwing error in the code.
One thing is this partiuclar DC which i am tring t Create project isshown as a Broken DC in the CBS, Will this be any problem??
Please help me andin this regards with your suggesion., this is really important and critical for us.
Regards
Sai Sharan Kalla

Hi ,
You need to check the activity in DTR, it seems that its not active.
Also make sure that all the URL DTR and CBS have FQDN.
Regards,

Debugging a web dynpro application

Hi,
I need to debug a abap web dynpro application from the internet browser. I only have the application URL and i don't know the component name and application name. So i can't put a break point in the methods.
I there a way by which we can call a debugger dynamically from the browser without knowing the WD component.
Thanks & Regards,
Ravi Aswani

Hi Pooja,
First of all, I am not sure about the more fieldinfo authority thing, I'm only guessing
I think you got your answer to your original post answered from Patrick and my earlier post (about what application is used in URL etc)
About the More Field-Info:
I checked the said scenarios again:
User with only my Basis ESS Roles: No Field Info available.
User with SAP_ALL: Field Info Available
User with my Basis ESS Roles and Content-Admin and System-Admin: No field Info available
It seems to be dependant on some authority from R3, and since you say it works for you if the user has sysadmin and content-admin roles, I would take a look at the identity management in portal for your sysadmin and content admin portal roles. Take a look at the assigned R3-Roles and look within these which authorities are given. Maybe this will unveil something. I cannot check this in my system since our portal identity management works differently.
Alternatively, maybe somebody with deeper knowledge pops up and delights you with the sample solution )
Cheers, Lukas

How to put a break point while creating a travel request in ess

Hi to all experts,
My requirement is to put a break point in the badi while creating a travel request in Ess.
The badi name is TRIP_WEB_CHECK
i tried both external and session bps
i also tried this.
break uname
break-point
and it is i check whether is triggering by throwing dump like ( divide by zero) it is triggering
how to stop it while triggering

Hi Bhanu,
Please go through these links:
How to debug abap code in update rules...routine?
debug abap routine in infopackage
Debugging of global transfer and update routine
Debugging Start/Transfer routine
And have a look at this demo video to know how to set up break points and how to debug an ABAP program in NW2004s:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9cbb7716-0a01-0010-58b1-a2ddd8361ac0?prtmode=navigate
Hope it helps..
Cheers,
Habeeb

ESS is not working properly after upgrade from 4.7 to ECC6.0

ESS Scenario in 4.7
4.7 Scenario:
The IMG configuration u201CWork and Life Eventsu201D is done to map them with the PZM3 service (Home Page) to get them as different folders/links on the home page as given below:
List of Services used to set up ESS:
Sl.No     Functionality     Service/EWT/URL Name     Standard/ Customized     Type
1     Home Page     PZM3                                          Standard                 Service
2     Inbox                     BWSP                                          Standard                 Service
3     Calendar                     BWCA                                          Standard                 Service
4     Whou2019s Who     PZ01                                          Standard                 Service
5     CPF Display     http://192.168.0.2:7070/omcpf             NA                                  URL
6     Payslip Display     ZPAYSLIP_USER                          Customized                Service
7     Section 80C     PZ88                                          Standard                EWT
8     Section 80                     PZ80                                          Standard                EWT
9     Form 16                     HRESSIN_F16                          Standard                EWT
10     Address                     PZ02                                             Standard                EWT
11     Bank Information     PZ03                                          Standard                Service
12     Open Appraisals     Not Available                           NA                                 Service
13     Emergency Address     PZ05                                           Standard                 EWT
14     Family/Dependents     PZ12                                           Standard                 EWT
15     Personal Data     PZ13                                               Standard                  EWT
16     Previous Employers     PZ28                                           Standard                 EWT
17     Apply Leave     WS20000081                           Standard               Service
18     Leave Overview     WS01000109                           Standard              Service
19     Leave Balance     PZ09                                             Standard              Service
20     Loan Application     ZLOAN                                          Customized              Service
ECC6.0 Scenario:
In ECC6.0, flow based services are no more supported by ECC6.0 and Dynpro based services are supported.PZM3 (Home Page) is a flow based service.
There is no replacement provided for PZM3 service, so the IMG configuration is not possible for u201CWork and Life Eventsu201D.
OSS ticket raised, but no solution for IMG u201CWork and Lifeu201D events.
List of Services would be used to set up ESS:
Sl.No     Functionality     Service/EWT/URL Name     Standard/ Customized    Type
1     Home Page     PZM3                                       Standard                           service
1)this service is not available
2)SAP does not provide any replacement.
3)PZM3 is not supported in Integrated ITS. No direct solution proposed.
4)Given reference of few notes.
5) A dynpro (module pool screen) based IAC needs to be created and links need to be provided on that screen. Generated HTML page is modified to access the services via URL or by OKCODE.
Screenshot attached below.
2           Whou2019s Who                 PZ01                                      Standard                             Service
1)this service Available
2)Not Working properly.
3) The problem may be because of the dependency with SAP Query. Either Query is missing in the new system or not having the proper authorization. Needs to be debugged and finalized.
7     Section 80C     PZ88      Standard     EWT     Available
8     Section 80      PZ80     Standard     EWT     Available
9     Form 16                HRESSIN_F16     Standard     EWT     Available
10     Address                PZ02     Standard     EWT     Available     Only EWT Available.          Service needs to be created to access the EWT.
11     Bank Information     PZ03     Standard     Service     Available     EWT Available.           Service needs to be created to access the EWT.
12     Open Appraisals     Not Available     NA     Service          EWT Available.           Service needs to be created to access the EWT.
13     Emergency Address     PZ05     Standard     EWT     Available     EWT Available.           Service needs to be created to access the EWT.
14     Family/Dependents     PZ12     Standard     EWT          EWT Available.           Service needs to be created to access the EWT.
15     Personal Data     PZ13     Standard     EWT          EWT Available.           Service needs to be created to access the EWT.
16     Previous Employers     PZ28     Standard     EWT          Service Available
17     Apply Leave     WS20000081     Standard     Service     Available, but not working                                                                               No solution is proposed yet.
18     Leave Overview     WS01000109     Standard     Service     Available, but not working               No solution is proposed yet.
19     Leave Balance     PZ09     Standard     Service     Available, but not working               No solution is proposed yet.

Ya ramakrishna,
Even easier is for you to send us the mail ID of your client. We will do the work, then send them an idoc of message type INVOICE and for you a post card of course.
Please do the needfull,
Julius

ESS Debugging

Similar Messages

Maybe you are looking for