ESS portal request approval thru blackberry

Hi,
I have a requirement of sending a request for approval on Blackberry as soon as a requisition is raised from ESS. The requisitions are Z-development and connected to a workflow which triggers once the requisition is raised. I want a approval request to be flashed on black berry of the approver. Does any one know a Bapi which fits well.
Regards,
Dhiraj Mehta

HI,
Check if u have activated the workflow and agent assignments are done. If it is done then
Login to approvers ID and see if he has got the work item in SBWP. If not, go to requesters SBWP in R/3, open outbox -> started workflows. Check the log for the workflow.
Cheers!!
Ashutosh

Similar Messages

ESS Loan Request Approver side validations

Dear All,
I am using standard ess loan request service.Here I have to perform certail validations at MSS side(Loan Request Approver IView).
Here manager can edit the values of Granted Amount,payment date,payment amount and payment type.But without entering these values also the loan request is getting approved by clicking on Review button.
I want to validate the above mentioned fields in case any of thefields left blank and also I have to validate the granted amount(should not be greater than requested amount).
As we know we have following BADI's available thru which we can perform validations when employee is applying for a loan.
1.Eligibility check
2.Custom Validations
3.Determine Approver.
Is there any BADIs available to perform validations at MSS part(Loan Request Approver)
Please give some input!
Thanks,
Reddy.

Dear Roy,
Thanks for your response.
According to your reply I understand that I need to write my validations in the approval task(TS18900024).In the workflow Approval task there is a standard class CL_HRPBSIN_LOAN_REPAY_WF available.I cannot create a method under it since this is a standard class.Do I need to take a copy of it and create a method?
But how can I Import the parameters from approver screen like Granted amount,payment amount,payment date and payment type.
Please clarify...

ESS Leave Request Approval Not working

Hi All,
We here have ESS1.0, ECC 6 and EP 7 on NW2004s.
Problem which i am facing is in Leave Request.
An employee enter his leave details and send it to its boss.
and the boss check the same in his UWL uptil this its working fine.
But when the boss click on the Leave request in UWL to approve or reject the same then error comes.
The error is "<u><b>Application error occurred during request processing.
Details: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Wrong WebDynpro-URL: no application name specified
Exception id: [001125C556F8005400000500000B2052000432CAF4C7A0CF]</b></u>"
Kindly help me out on how can i resolve this issue.
Regards,
Sidhartha Chatterjee

Hi Sidhartha,
proove, if you use the following things:
In the portal under "Universal Worklist - Administration" you must fill out the parameter "Web dynpro launch system" for the binded ECC system you use. Use a portal system (the alias name for the portal system you have created) which links to the Web Application Server where you have deployed(!) your application (if web application server and portal is the same you also must create a portal system with the local web application data). In general, you create and named a portal system like SAP_WebDynpro_XSS and bind it as parameter.
If you do not use this system the Web Dynpro for Approve/ Reject leave request generates a wrong URL with the Web application data from ECC, not for web dynpro.
More information:
Configuring The Business Package For Employee Self Service (ESS)-mySAP ERP 2004
(to create the system SAP_WebDynpro_XSS)
http://help.sap.com/saphelp_nw04/helpdata/en/92/a88931f2dd4631b9e8d530697d89c9/content.htm
(to bind it into UWL)
Hope that helps,
Regards,
Frank

How to create iView for Leave Request Approval for ESS Tab in Portal

Hello ,
I am new to Enterprise portal. I got a requirement for creating iViews.
How to create iView for Leave Request Approval for ESS Tab in Portal.??
Please give me clearly or provide any document.
Thanks
Risha

Hi Risha,
is it customized application ?
If so in SWFVISU transaction maintaain the entry .
Use transaction SWFVISU to prepare standard setting for your Workitem in the UWL. --Parameters for Work Item Visualization in the UWL.
Have a look at below link
http://help.sap.com/saphelp_nw2004s/helpdata/en/59/d516690e854c7090ae15bf492a869f/content.htm

ESS Claim Advance Approval screen showing incomplete list of requests.

Hi Friends,
In ESS Claim Advance Approval screen we are facing this issue.
When approver opens the screen for approving the request.
The list of requests appear but its not the complete list.
There are also 2 sucess messages that get displayed.
112 records found for the selection
Only 10 of 112 records loaded which meet the selection criteria
Users are able to see the rest of the request at r/3,
also if they approve the first 10 request then they are able to view the next slot of requests.
Any guidance as where the configuration for this could be checked.
Regards.
Edited by: SAP Portal Deve on Sep 20, 2011 2:41 PM

you mean number of requests in UWL?
Please specify
http://help.sap.com/saphelp_afs64/helpdata/en/56/15681955744ec8877931c56607ec35/frameset.htm
Edited by: Siddharth Rajora on Sep 20, 2011 8:08 PM

Error after second level approval in ESS leave request

Hi Experts
I am using custom workflow for Ess Leave request process which is copied from WS21500001.
I have added custom class methods to change status from approved to sent.
Then another method i have set next appovaer.
The problem i m facing is that I am getting an error on portal after second approval approves the request.
i.e Field syomol has not been assigned yet.
from st22 i found its generating from
Include LPT_ARQ_REQUEST_UIAF06 - Form   execute_approver_update
By debugging i found that Its not getting next approval with status T as there is only first approval with status 'A'
This results in unassigned field symbol. and then error.
Please help me resolve this issue.
Please confirm why next approver is not found in method.

Hi All
Thanks for your reply.
I checked why it was giving a dump.
This execute_approver_update subroutine takes approval data from table ptreq_approver .
I filled this with resp actor id after request is approved and status is changed to sent.
For every emp its unique actor id is saved in ptreq_actor table agaist his pernr.
   SELECT SINGLE actor_id FROM PTREQ_ACTOR INTO actor_id WHERE objid = nextApprover_pernr.
    wa_appr-mandt = sy-mandt.
    wa_appr-request_id = Request_ID. "Req.requestID ( from Workflow )
    wa_appr-version_no = version_no. "Req.Version ( from Workflow )
    wa_appr-seqnr = seqnr. "Same as version no but in char
    wa_appr-approver_ins = actor_id. "Employee actor id from ptreq_actor
    wa_appr-status = 'T'. "Manual
    append wa_appr to it_appr.
    INSERT PTREQ_APPROVER FROM TABLE it_appr .
    commit work and wait.
This resolved my issue.
Thanks

TRIP END DATE greyed out while creating Travel Request IN SAP ESS Portal

Dear Friends,
                           I am trying to create a Travel Request from my ESS Portal,when I am entering the trip details as follows:
General Trip Data (header)
Start: *    (Have to enter trip date)
End:        (greyed out)   **** problem with this field
First Destination: Country/Region:     open field
Reason for Trip:    open field
Activity:     open field
Estimated Cost:
Previous Step Review     Exit (these are all tabs)
The problem is that the END DATE is greyed out ,how do we enable it,is it a configuration setting or some code change in the function module
PTRA_UTIL_GENERAL_DATA_FIELDS
My portal consultant said that this FM is called in the backround R/3....please let me know ure views on this...
Thanks,
Best Regards,
Karthik

Hi Kartik,
We are getting the same problem. Can you please share how did you solve this. It is urgently required.
Thanks,
Vishal Patel

ESS leave request - Change Approver

Hi,
We have a situation in which a employees dotted line manager will approve the leave request instead of a direct manager. We have a custom relationship to establish the dotted line manager. Now, In the ESS leave request there is a Approver field which shows the Employees direct manager. Can we customize the logic using a BADI or User exit to show the dotted manager?. Please let me know which enhancement is to be used for this requirement.
Thanks in Advance for your assistance.
Ramesh

in the customizing for the definition of the processes per rule group
you set the selection for the next processor to "Manual Entry".
or for the BADI
Another way is to use the BAdI Control Processing Processes for Time
Management Web Applications (PT_GEN_REQ) and implement the methode
IF_EX_PT_GEN_REQ~FIND_RESP_AND_DEFAULT_NEXT_PRC.
Method FIND_RESP_AND_DEFAULT_NEXT_PRC of badi
PT_GET_REQ might be utilised here.
Please have a look at the method
CL_PT_REQ_SEARCH_NEXT_P~SEARCH_NEXT_PROCESSOR.
If you are implementing the badi then make sure you copy all the methods
and implement the one, as mentioned.

Next level approver in ESS leave request

hi friends
Am working in ESS leave request workflow. In my scenerio there are 4 level approver. I have function module SWX_GET_MANAGER i have copied and customized to ZSWX_GET_MANAGER with my logic to get the next level approvers. If i entered the PERNR it return all the approver for that employee. How do the workflow know he is the 2nd level approver, he is the 3rd level approver. How can i achieve it. kindly help me...
Regards
vijay

Hi Vijay,
I think you will need to use a loop and a counter so you know the approval level. You can use this to get the manager who belongs to the level.
Regards,
Martin
PS I hope you will show in the thread which solution you got so others will benefit. This forum is about sharing knowledge and one way is to give the solution in your thread, or value the appropriate answers.

ESS Leave Request - Customer fields default function not working

Hi,
a. SAP version being discussed
SAP ECC6.0
EP7.0
ESS/MSS
b. Here is the scenario
1. We are using ESS Leave Request application for employees to request leave. We are using the standard web dynpro java leave request application delivered by SAP.
2. Lately there has been a need to provide a customer field on the request form which will have a calculated value showing up when the employee opens the request
3.We used one customer field called customer01 as per configuration steps.
4. This field appears on the request form when it is opened.
5. Our need is to display a value in that field when the form is opened.
6. SAP/s documentation states that we can use BADI PT_ABS_ARQ to default a value to this field on the form. This value is calculated during runtime dynamically.
7. We have used the method IF_EX_PT_ABS_REQ~SIMULATE_VIA_BLOP for this purpose
8. After activating and coding this implementation, the system does not default anything on the request form when it is opened up.
9. Once the employee hits the review button, this field gets its defaulted value but this is not what we want. We want the system to display this when the form is OPENED, that means at the prepare stage. For this field to appear after hitting the review button is meaningless as the employee needs to make a decision based on the value in this field before hitting the review button.
It almost seems like this BADI is called when the review button is hit and not when the form is opened up. We may be wrong and missing something obvious which one of you can immediately point out, Hence this post.
10. I did go thru the forum at great length and seen that there has been discusion surrounding the need to populate R3 from a value entered into this field. My problem is different wherein, I wish to populate this upfront as display information when the form is opened and then send it back to R3, once the employee submits the request.
Would be grateful if anybody on this forum could point me in the right direction.
Thank you,
Rajesh

Please, can I take this question a little further.
Is it possible to add more fields to the leave request form on the ESS portal. For example, our customer wants additional fields like reason for leave, contact residential and telephone number during leave, Require leave entitlements (Yes/No).
Would appreciate if a reply can be given on if it is possible or not and what to be done if it is possible.
Cheers

ESS Portal Exception

Hi Folks
We have implemented leave requests in ESS Portal. Copy of WF12300111 is used. The WF works fine. The request is routed to the correct approver's UWL. However when the approver clicks on the work item to open it, the portal pop up window shows an exception is occured. How to fix this error. Can anyone guide how to remove this exception in the Approver's page.
Regards
Waz

Hi
@Barin: Thanx for the response but it didnt work.
the complete error from error trace is:
Error:
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Exception occured in layer CommonTopLayer
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     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:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     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(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Error 2
Content pass of Application Integrator failed.
Component Name:       com.sap.portal.appintegrator.sap.WebDynpro,
Context Name (iView): pcd:portal_content/every_user/general/uwl/com.sap.netweaver.bc.uwl.uwlSapWebDynproLaunch,
Top Layer:            WebDynpro/TopLayer,
Producer ID (FPN):    null,
System Alias:         SAP_WebDynpro_XSS,
Thanks & Regards
Waz

Conflict on ESS Portal

Hi
When employee apply or try to aprrove leaves on ESS portal conflict erro with other absence or attendace type is coming. this process working fine on R3 System but not on portal.
IT 0007 status os 0- No time evaluation.

Hi Vikrant,
The issue is because, the employee has applied for the leaves on portal and before it is approved, that particular date is updated via backend in IT2001.
To resolve this issue, you will have to delete the leaves that are still in the sent status in the portal buffer area.
You will have to use the reports RPTARQDBVIEW and RPTARQDBDEL using tcode SA38.
Run the first report by selecting upto today option and then check the leave request in sent status that are already updated in backend in IT2001 then using the second report, select upto date option and uncheck the test run field and delete those request that you identified from the first report. This will resolve ur issue.
Cheers,
Ayyaps

ESS Leave Request Workflow Issue

Hi Every one,
Our client is using ESS/Portal Leave Request workflow(ZWorkflow template which is configured to the portal) which is working fine up to the last month.Recently i developed 3 level Escalation functionaly which is working fine and we tested and finally transported to production in the last month .And recently i got an issue when the leave request is aproved after escallation is not setting the workflow status completed and keep on escalating to the next levels.
Note:When the 1st manager approves the leave request without escallation the workflow status is going to be completed which is fine and only there is an issue when escallated and approved the status of that specific leave request is approved but the workflow is not going to the status completed and keep on escalating to the next levels.
i checked the log and found there is condition based wait event step which have a condition when
Req.status = Approved&
Req.status = Withdrawn&
Req.status = Error.
must raise the event and complete the workflow only working fine when the escalation does'nt takes place and the direct manager reacted without escalating to another manager.
Please help e what might be the problem is.
Thanks,
Raja.

Hi,
Where is this event called? And more over is it an AND condition between those statements?
regards
Krishna

ESS Leave request workflow : ws12300111 : Customizing

Dear experts,
I need to customoze ESS leave request workflow WS12300111.
Can you please tell me do I need to Copy this to a NEW workflow generating a new WF no or can I simply generate a new version for this only ? What is ideal ?
1. Can anyone tell me step by step process(config) in ESS leave application workflow?.(SWFVISU????)
2. Is workflow WS12300111, the only workflow that I need to look for leave application ?.
3. If it is WS12300111 I dont see any start event for this workflow. So how is it getting triggered?
4. For the approval task TS12300097, agent determination is done by expression &Agent_0001.Agents&. How does it interact with Org.Structure.
5. In my scenario, approver should be supervisor of the employee applying for leave. If it is pending with this approver for 5 days it should go to the next up level manager.
For identifying first level approver is &Agent_0001.Agents& enough.? For identifying 2nd level approval do I need to write a rule ?
Kindly help.

Hi Sourav,
Try this step by step process(config) in ESS leave application workflow.
ESS Scenario
Workflow Process 20000081 u2013 Create Leave Request with HTML
Steps for triggering the workflow:
1) The employee logs with his user name in the ESS web page.
2) The employee creates a leave request with an optional note and sends it to the appropriate approver (usually his supervisor). The approveru2019s name is automatically displayed in the leave request form and the employee can replace him with another if such a change is needed.
3) The approver (us approver) logs on to sap system or to ESS
web pages and reads his mails in the SAP Business Workplace. The employeeu2019s leave request form appears in the workflow inbox with approve and reject options.
A) If the us approver approves the leave request, he pushes the
button approve from his mailbox (processing status A with
approve). A screen is appeared with a box (Table entry: 0001)
and the approver must push the button continue in order that
the workflow is continued. Then the form is sent to the
employeeu2019s mailbox in Sap. When the employee opens his mails, he receives a note in his inbox that u201Cthe absence from u2026. To u2026..has been approved byu2026.u201D.After that the absence is
automatically created in the sap system. Then the approver gets a mail (notification of completion & Return u2026u2026).
B) When the approver cancels a leave request, he pushes the
button reject and the processing status changes to u201CRu201D.
Then the same form appears
Realative OSS Notes:588262, 480103, 717560, 452841, 359197, 321439, 428394, 321439, 693368, 451998 (ITS), 197746 (ITS), 419297 (ITS)
ITS - ESS stand-alone solution for 4.7
This solution allows customers to schedule the 4.6C or 470
install / upgrade independently from the Enterprise Portal or
mySAP Workplace implementation and will be supported at least as long as SAP R/3 4.6C and R/3 Enterprise is supported.
This ESS stand-alone menu is intended solely to allow independent scheduling of the 4.6C or 470 upgrade and the Enterprise Portal / mySAP Workplace installation. To use this solution, you have to take the following steps:
1. If you do not already have R/3 4.6C, HR support package 8,
please import HR support packages to at least this level. From
HR support package 8 and above, the correct services are
implemented. For 470, the corresponding recommended HR SP is 16 (See note 621589)
2. Verify that the ITS you want to use does not contain a service or service-related files (HTML templates, MIME files) for the services PZLE, PZM3 or PZM3_start. If you find these files,
delete them.
3. Publish the services PZLE, PZM3 and PZM3_start from your R/3 4.6C system (or R/3 470 system whichever is the case) to your ITS using the SAP@Web Studio or the IACOR service.
4. Maintain the username-employeenumber assignment in your system by customizing Infotype 0105, Subtype 0001 of those employees, who should be able to use ESS.
5. Verify that your users have proper authorizations for
executing RFCs (that is, authorization object S_RFC) from the
function group EH08. If you run into problems, this is most
likely due to missing RFC authorizations to start the service
PZM3.
6. Your users should now be able to access ESS by starting the service PZM3. They can do this by entering a URL like
http://<ITS server>:<http port>/scripts/wgate/pzm3/!
(the ! at the end is essential).
7. ESS 4.70 Unicode System ITS 6.10 patch level 29 and above (With IE and Netscape). ITS 6.20, patch level 6 and above (With IE only).
The ESS development tested these ITS versions.
8. For Release 4.6C, ESS has the same browser requirements as the HTML (see also note 178788) and the mySAP Workplace 2.11 (if ESS is accessed through the mySAP Workplace 2.11).
Hope it helps.Do award points if found helpful.
Regards,
Gourav

Team Calendar in ESS Leave Request (Error)

Hello,
we are configuring the Leave request in ESS and MSS in the portal (EP 7.0, ECC 6.0, latest release). The Leave Request process and application, Time accounts and Workflows all working fine and the customizing is done in the IMG.
Only under ESS -> Leave Request -> Team Calendar we are getting this Error:
java.lang.Exception: No Views found: Missing customizing
     at com.sap.xss.ser.tecl.fc.FcTeamCalendar._checkData(FcTeamCalendar.java:799)
     at com.sap.xss.ser.tecl.fc.FcTeamCalendar._getData(FcTeamCalendar.java:751)
     at com.sap.xss.ser.tecl.fc.FcTeamCalendar.initialReadData(FcTeamCalendar.java:385)
     at com.sap.xss.ser.tecl.fc.wdp.InternalFcTeamCalendar.initialReadData(InternalFcTeamCalendar.java:319)
     at com.sap.xss.ser.tecl.fc.FcTeamCalendarInterface.initialReadData(FcTeamCalendarInterface ....etc.
I have maintained the Customzing in IMG for Team Calendar as the following:
00000001     SAP Standard     01.01.1800     31.12.1999     Approval Mode     View Group (MSS)     MSS_LEA_EE
00000001     SAP Standard     01.01.1800     31.12.1999     Attendance Overview     View Group (MSS)     MSS_LEA_EE
00000001     SAP Standard     01.01.1800     31.12.1999     Administrator Mode     View Group (MSS)
00000001     SAP Standard     01.01.1800     31.12.1999     Request Mode     View Group (MSS)     ESS_LEA_EE
00000001     SAP Standard     01.01.1800     31.12.1999     Team View Mode     View Group (MSS)
Would you please help?
Many Thanks and Regards,
Nazih

Hi Bryan,
1. First of all make sure that the Internet Graphic Server is activated + up and running on your SAP ERP System (see also SAP Note 704604)
2. Then you have to set the Customizing Parameters for the Team Calendar in IMG (SAP ERP System):
a. Tcode: PTARQ -> Customizing
b. Working Time -> Team Calendar
c. Node Create Rule Group -> Example: 00000001 (SAP Standard)
d. Node Adjust WEBMO Feature -> Assign all Nodes to your Rue Group
e. Node Spec. Absecne to be displayed -> Here i assume you have set up the Leave Request Process and WF already, so you only need to assign this to your Rule Group:
Example.
00000001     SAP Standard     01     0100     Leave     01.01.1800     31.12.9999
f. Node Select Employee -->
Here you need to set the Group of your Employee which should be displayed in the team calendar:
Example.
00000001     SAP Standard     01.01.1800     31.12.9999     Approval Mode     View Group (MSS)     MSS_LEA_EE
00000001     SAP Standard     01.01.1800     31.12.9999     CATS Approval     View Group (MSS)     MSS_LCA_EE
00000001     SAP Standard     01.01.1800     31.12.9999     Attendance Overview     View Group (MSS)     MSS_LEA_EE     PPOME_P
00000001     SAP Standard     01.01.1800     31.12.9999     Administrator Mode     View Group (MSS)     MSS_LEA_EE     PPOME_P
00000001     SAP Standard     01.01.1800     31.12.9999     Request Mode     View Group (MSS)     ESS_LEA_EE
00000001     SAP Standard     01.01.1800     31.12.9999     Team View Mode     View Group (MSS)     MSS_LEA_EE     PPOME_P
---> Tipp: Check all Settings and Leave Types also with an HR Consultant before maintaing these in the ESS Customizing...
Regards,
Nazih

ESS portal request approval thru blackberry

Similar Messages

Maybe you are looking for