Providing Calender option for dates in Leave Request form in ESS Portal

Hello All,
Can anyone tell me how to get the calender option for the From date and To date fields in the craete leave request iview in ESS ?
In the backend R/3 transaction, we are able to see the calender option. But it is not visible in the portal.
Thanks for your help...
Regards,
Bindu

Go to:
IMG > Personnel Management > Employee Self-Service (Web Dynpro ABAP) > Service-Specific Settings > Working Time > Leave Request > Processing Processes > Define Processing Processes for Each Rule Group
Select your Rule Group
Under Record Partial-Day Absences in you have three options: Hours and Clock Times / Hours / Clock Times
You should select Hours and save the record.
With this, you will only have the duration and clock times will not be displayed.
Regards,
Harshal

Similar Messages

Need multi level approval for Leave request workflow in ESS

Hi All,
Our requirement is for 5 levels of approvals for the leave request raised in ESS means After employee raises leave request ,it has to be approved by 5 managers one after the other. In standard system only 1 level of workflow and approval is available so please anybody suggest the solution . Thanks in advance.

in addition to the above content your workflow consultatn have to create this ask him to
refer this document
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMDEMO/BCBMTWFMDEMO.pdf
for multiple level of aproving the leave reqest and and orgstructure have to be well formed
ravindra

Select-options for date field.

Hi all,
i need to give select options for Date field.How can i give that.
Thanks & Regards
Ravi.

Hi Ravi,
Use the Component WDR_SELECT_OPTIONS to include select options in Web Dynpro ABAP. Follow these steps:
1. In your Component , "Used Componet" tab add Component WDR_SELECT_OPTIONS . Component Use can be any name that you want to give, eg SELECT_OPTIONS
2. Go to the View where you want to include the Date Select Options. I am assuming that you already have an Attribute of Type DATS in your context.
3. View: Properties Tab:Create Controller Usage and select
SELECT_OPTIONS     WDR_SELECT_OPTIONS
SELECT_OPTIONS     WDR_SELECT_OPTIONS     INTERFACECONTROLLER
4. View Layout Tab:Include a View Container. In this view container we will show the Date Select Options.
5. View Attributes Tab: Create Following two attributes:
M_HANDLER type IF_WD_SELECT_OPTIONS
M_WD_SELECT_OPTIONS type IWCI_WDR_SELECT_OPTIONS
6: View Methods Tab: Create a method eg CREATE_SELECTION_SCREEN. Call this method in the WDDOINIT of the view.
7:CREATE_SELECTION_SCREEN: Write following Code:
* Data Declaration
data:
        lt_range_table TYPE REF TO DATA.
data:
        lr_componentcontroller TYPE REF TO IG_COMPONENTCONTROLLER,
        lr_componentusage TYPE REF TO IF_WD_COMPONENT_USAGE.
* Execution
* Create Used Component
lr_componentusage = wd_this->wd_cpuse_select_options( ).
if LR_COMPONENTUSAGE->HAS_ACTIVE_COMPONENT( ) is initial.
    lr_componentusage->create_component( ).
endif.
* Get pointer to interface controller of select options
wd_this->M_WD_SELECT_OPTIONS = wd_this->wd_cpifc_select_options( ).
* initialize selction screen
wd_this->M_HANDLER = wd_this->M_WD_SELECT_OPTIONS->init_selection_screen( ).
* Create Range Table for: Date
CALL METHOD WD_THIS->M_HANDLER->CREATE_RANGE_TABLE
    EXPORTING
      I_TYPENAME     = 'DATS'
    RECEIVING
      RT_RANGE_TABLE = lt_range_table.
* Add Selection Field for: Date
CALL METHOD WD_THIS->M_HANDLER->ADD_SELECTION_FIELD
    EXPORTING
      I_ID                         = '<name of date attribute in the context>'
*      I_WITHIN_BLOCK               = MC_ID_MAIN_BLOCK
*      I_DESCRIPTION                =
*      I_IS_AUTO_DESCRIPTION        = ABAP_TRUE
      IT_RESULT                    = lt_range_table
*      I_OBLIGATORY                 = ABAP_FALSE
*      I_COMPLEX_RESTRICTIONS       =
*      I_USE_COMPLEX_RESTRICTION    = ABAP_FALSE
*      I_NO_COMPLEX_RESTRICTIONS    = ABAP_FALSE
*      I_VALUE_HELP_TYPE            = IF_WD_VALUE_HELP_HANDLER=>CO_PREFIX_NONE
*      I_VALUE_HELP_ID              =
*      I_VALUE_HELP_MODE            =
*      I_VALUE_HELP_STRUCTURE       =
*      I_VALUE_HELP_STRUCTURE_FIELD =
*      I_HELP_REQUEST_HANDLER       =
*      I_LOWER_CASE                 =
*      I_MEMORY_ID                  =
*      I_NO_EXTENSION               = ABAP_FALSE
*      I_NO_INTERVALS               = ABAP_FALSE
*      I_AS_CHECKBOX                = ABAP_FALSE
*      I_AS_DROPDOWN                = ABAP_FALSE
*      IT_VALUE_SET                 =
*      I_READ_ONLY                  = ABAP_FALSE
*      I_DONT_CARE_VALUE            =
*      I_EXPLANATION                =
      I_TOOLTIP                    = 'Select Date'.
8: To Fetch Data entered in the selection field, write following code on action of button click:
data:
        lt_date type REF TO DATA.
FIELD-SYMBOLS:
                 <fs_date> TYPE table.
* retrieve Date from Select Options
CALL METHOD WD_THIS->M_HANDLER->GET_RANGE_TABLE_OF_SEL_FIELD
    EXPORTING
      I_ID           = '<attrib_name>'
    RECEIVING
      RT_RANGE_TABLE = lt_date.
* assign Date Field Symbol
ASSIGN lt_date->* to <fs_date>.
9: Windows Window Tab: In the View Conatiner, embed the WND_SELECTION_SCREEN view from SELECT_OPTIONS component Usage of WDR_SELECT_OPTIONS component.
Regards,
Reema.

Select option for date

i want give default values in select option for date (for a period)
I used
SELECT-OPTIONS y_s_mnth FOR y_v_dt_month default first to last OPTION BT.
first and last are dates.
I am getting error dialog box....specify ranges...
Please give sample code..

Hi Suhas,
I hope this code will help you. Reward me if it is helpful.
select-options : y_s_mnth FOR sy-datum.
initialization.
y_s_mnth-sign   = 'I'.
y_s_mnth-option = 'BT'.
y_s_mnth-low    = sy-datum - 30.    "first_day
y_s_mnth-high   = sy-datum.         "last_day
append y_s_mnth.
clear y_s_mnth.
Regards,
Sagar

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

Preblem for Approver in Leave request

Hi All,
   Well i am facing a problem in Create leave Request For the Approver that is selected by default based on the organisation head.I don't now how it happens but thing that i noticed thta for an employee if i maintain a head position in the org it picks up that head position of org as default.
My consulatant want this value to be picked up as we require i.e fetch a particular employee through coding on the screen itself and default on the screen.Can this be done else if any body can provide any better alternative for this solution is most welcomed.
Well we can actually send or sellect the approver what he wants but what about the approver that comes as default on screen and if there is no approver workflow will not be triggered as it gives the error
Please reply soon.

1)   go to swdd tcode,give workflow name and then click on step which finds out the approver of the employee.u will find FM which is finding approver.
now u can go an change the FM in SE37 and put ur own logic to find the approver.
suppose u want to find approver by A002 relationship of employee then u have to write followign code in the concerned FM -
DATA: ls_sobid TYPE sobid.
SELECT SINGLE sobid FROM hrp1001 INTO ls_sobid
   WHERE otype = 'S'
   and   plvar = '01'
   AND   objid = i_plans
   AND   endda >= sy-datum
   AND   begda <= sy-datum
   AND   rsign = 'A'
   AND   relat = '002'.
e_objid = ls_sobid.
2) if not by A002 then u can create a new relationship say 'ZTV' and maintain this relationship for employees and find approver based on tht then as follows -
SELECT SINGLE sobid FROM hrp1001 INTO ls_sobid
   WHERE otype = 'S'
   and   plvar = '01'
   AND   objid = i_plans
   AND   endda >= sy-datum
   AND   begda <= sy-datum
   AND   rsign = 'A'
   AND   relat = 'ZTV'.
e_objid = ls_sobid.
3) reward poins if helpfull
amit

Which is better or 'standard' option for a Delta DTP request

Hi folks,
I am creating a delta DTP for loading HR Payroll data. While creating the DTP I see two options
a) Only Get Delta once
b) Get all new data request by request
which is a better option if I have a lot of records to upload for every delta upload.
Points waiting to be given to you...
Thanks
Sunil

U should go with Get all new data request by request
i. With Only Get Delta Once, define if the source requests should be transferred only once.
Setting this flag ensures that the content of the InfoProvider is an exact representation of the source data.
A scenario of this type may be required if you always want an InfoProvider to contain the most recent data for a query, but technical reasons prevent the DataSource on which it is based from delivering a delta (new, changed or deleted data records). For this type of DataSource, the current data set for the required selection can only be transferred using a full update.
In this case, a DataStore object cannot normally be used to determine the missing delta information (overwrite and create delta). If this is not logically possible because, for example, data is deleted in the source without delivering reverse records, you can set this flag and perform a snapshot scenario. Only the most recent request for this DataSource is retained in the InfoProvider. Earlier requests for the DataSource are deleted from the (target) InfoProvider before a new one is requested (this is done by a process in a process chain, for example). They are not transferred again by the DTP delta process. When the system determines the delta when a new DTP request is generated, these earlier (source) requests are considered to have been retrieved
ii. Define if you want to Get All New Data in Source Request by Request.
Since a DTP bundles all transfer-relevant requests from the source, it sometimes generates large requests. If you do not want to use a single DTP request to transfer the dataset from the source because the dataset is too large, you can set the Get All New Data in Source Request by Request flag. This specifies that you want the DTP to read only one request from the source at a time. Once processing is completed, the DTP request checks for further new requests in the source. If it finds any, it automatically creates an additional DTP request.
u201COnly get Delta Onceu201D
/people/community.user/blog/2007/06/21/sap-netweaver-70-bi-data-transfer-process-with-147only-get-delta-once148
u201CGet Data by Requestu201D
/people/community.user/blog/2007/06/21/sap-netweaver-70-bi-data-transfer-process-with-147get-data-by-request148

Adding new data to leave request DropDown

Hi,
We have deployed ESS 1.0 BP. In leave request application we select the leave request type(PL, CL, SL) from drop down menu.
Here privelige Leave is by default selected... but we need to remove PL from default and add hipen(-) so that user has to compulsory select the leave type from drop Down,
Now the problem is as this list comes from R3 .. so how can we add new item to this drop down menu. Whether its needed to be done R3 side or do i need to modify Leave request Application. If i need to modify this leave request application than h0w can append hipen to the already list coming in drop down menu...
Can any person specify in detail from where this configuration is needed to be done..?
Regards,
Jigar OZa

Check this thread
Re: Regarding control of leave types in the dropdown in ESS screen
Try this from thread
You can add the leave type that you want to get displayed in ESS in SPRO setting .
in Spro
Personnel Management --> Employee Self-service ---> Working Time -> Leave request> Processing Process ---> Specify Processing Process for Types of leave.

I need options for data replication within production db and dimensional db

Hi,
I'm looking for options on how to solve this issue. We've 2 databases, one is our production, operative database, used by around 400 users at a time, and another one, which is our dimensional model of the same info, used to obtain reports. We also have a lot of ETL's (extract, transform and load) processes running every night to update the dim model.
Mi problem is that we have some online reports, and nowadays, we're getting data from the operational database, causing a performance issue in online operations. We want to migrate this reports to the dimensional model, and we're trying to find the best options for doing this.
Options that we're considering are ETL's process running continuously every XX minutes, materialized views, ETL's on demand, and others.
Our objective is to minimize performance issues on transactional database.
We're using Oracle 8i (yes, the oldie one) and Reporting Services as report engine (reports just run a pkg to get data).
Any option is welcome.
Thx in advance.
Regards,
Adrian.

The best option for you if the performance is the
most important is ORACLE STREAMS. Also is the most
complex but the final results are very goodsAgreed. As User12345 points out, though, that requires Oracle 9.2 or higher.
Another option is the materialized views with Fast
Refresh , that need the materialized view logs in
the master site.
The first load is expensive but if you refresh each
15 minutes the cost is not high.I'd be careful about making that sort of statement. The overhead of both maintaining materialized view logs (which have to be written to synchronously with the OLTP transactions and which impose an overhead roughly equivalent to a trigger on the underlying table) and doing fast refreshes every 15 minutes can be extensive depending on the source system. One of the reasons that Streams came about was to limit this overhead.
For refresh i execute a cron shell that run the
DBMS_MVIEW.REFRESH package. my experience with group
refresh not was goodWhat was your negative experience with refresh groups? I've used them regularly without serious problems. Manual refreshes of individual materialized views against an OLTP system would scare the pants off me because you'd inevitably end up with transactionally inconsistent views of the data (i.e. child records would be present with no parent record, updates that affect multiple tables would be partially replicated until the next refresh, etc). Trying to move that sort of inconsistent data into a different data model, and trying to run reports off that data, would seem highly challenging at a minimum. Throwing everything into a single refresh group so that all the materialized views are transactionally consistent, or choosing a handful of refresh groups for those tables that are related to each other, seems like a far easier way to build a system.
Justin

A question on different options for data archival and compression

Hi Experts,
I have production database of about 5 terabyte size in production and about 50 GB in development/QA. I am on Oracle 11.2.0.3 on Linux. We have RMAN backups configured. I have a question about data archival stretegy. To keep the OLTP database size optimum, what options can be suggested for data archival?
1) Should each table have a archival stretegy?
2) What is the best way to archive data - should it be sent to a seperate archival database?
In our environment, only for about 15 tables we have the archival stretegy defined. For these tables, we copy their data every night to a seperate schema meant to store this archived data and then transfer it eventualy to a diffent archival database. For all other tables, there is no data archival stretegy.
What are the different options and best practices about it that can be reviewed to put a practical data archival strategy in place? I will be most thankful for your inputs.
Also what are the different data compression stregegies? For example we have about 25 tables that are read-only. Should they be compressed using the default oracle 9i basic compression? (alter table compress).
Thanks,
OrauserN

You are using 11g and you can compress read only as well as read-write tables in 11g. Both read only and read write tables are the candidate for compression always. This will save space and could increase the performance but always test it before. This was not an option in 10g. Read the following docs.
http://www.oracle.com/technetwork/database/storage/advanced-compression-whitepaper-130502.pdf
http://www.oracle.com/technetwork/database/options/compression/faq-092157.html

Missing "Add Records" and "Refresh Records" options for data sets post domain re-import

We recently had to re-install the Endeca server and as part of which had to export and re-import the data domains. Everything went fine except for the fact that newly re-imported data sets showcase just the "Manage Attributes" and the "Delete Data Set" options for an administrator login in. The previously available options to "Add Records" and "Refresh Records" beyond manage attributes/Delete Data Set are missing.
Thoughts? Is there a security setting to enable these?

So are you talking about the Add Records and Reload Records options for a data set in Studio?
There are no separate security settings for these options. If a user is an application administrator (is able to edit the application), then they should have access to these options.
The options are only available for data domains created using the Provisioning Service (created by uploading a file or from the JDBC or BI Server data source from the Data Source Library).
I don't know if the process of exporting and re-importing the data domains (not sure how you did that) could somehow cause the data sets to no longer know that they were created by the Provisioning Service, in which case those options would not be enabled.

Does Adobe provide bundle options for Creative Suite?

I currently use a version of Creative Suite that does not come with Premiere or After Effects. These are two major applications that are part of the CC Creative Suite bundle on offer now, but I don't need them.
Are Adobe planning to provide alternative options to users who don't need the whole package? It's very nice to have access to all the applications, but in reality I won't have the time to use all of them. I use the print and web page development applications.
In the same way, I imagine that companies who mostly use Premier and After Effects, won't need all their staff to have access to InDesign, Flash or Dreamweaver.
It would be more helpful if you could provide us with less expensive bundles which provide us with the tools we need rather than an excess of applications.
This would certainly take out some of the sting for people for people such as myself who find that your new system is going to be costing us a lot more for the same tools that we previously had.
I think you really need to set something up that is fair because the fact that we will not be able to open our files unless we have a current subscription is a big pill to swallow. It's really is outrageous that long time users of your products would have to fork out $74 simply to open up their old files.

There hasn't been any mention of creating sub-bundles of the CC apps in the same way that the Creative Suite bundles are packaged. Due to how Adobe is marketing that "you have accesss to all the CC apps with one subscription" I really doubt they'll create other bundles other than a single app or all of them.

Wrong agent picked if manager not maintained for employee in leave request

Hi All
We are using std. workflow WS12300111 for leave request approval which is run from the EP side.
It is working all fine, but the problem arises when there is no manager maintained for an employee. Idealy it should have given a error message; but here the workflow runs and the agent is the manager of the previous leave request.
Is there any setting that is missing anywhere? Or there is someother reason that I can't forsee?
Please help me out in this

Hi Varsha,
who the agent is getting selected for that step of wrkflow.... r they using any rule or they are referring and org structure..
if they are referring org structure then it will take the next line manager of that employee...
so if the picking agent is next line manager then it is working fine .............
Regards Dev

"ORA-02248: invalid option for ALTER SESSION" -- Urgent request

Hi All,
We use Discoverer 3.1.36.06 and are in middle of a 3i to 10g upgrade for Discoverer for a data warehouse setup. Our databases where upgraded to 10g from 9i and now we get the error message saying:
"ORA-02248: invalid option for ALTER SESSION"
I got some very helpful info abt the prob from the link below.
Discoverer 3i Issue with 10.2.0.3 - ORA-02248
We are mid way through the 3i to 10g upgrade and just need a quick fix for the next 2-3 weeks while the upgrade is finished.
Does any one know if changing the NLS language and applying the post longon trigger on Database id's would help in resolving this connection issue temporarily.
Any advice is deeply appreciated.
Thanks.
Edited by: Paul S on Dec 15, 2008 3:01 PM Corrected the link

Hi,
There are two types of trigger you can use: database triggers and discoverer triggers. You probably want to use a database trigger.
If you are using an APPS mode EUL (ie. logging using Applications username/passwords) then you will be logging in as the APPS database user and the syntax is:
create or replace trigger APPS.disco_logon_trigger after logon ON APPS.SCHEMA
begin dbms_session.set_nls('nls_date_format', '''DD-MON-YYYY'''); end;
If it is a database EUL and the database user is gl_inq then the syntax would be
create or replace trigger gl_inq.disco_logon_trigger after logon ON gl_inq.SCHEMA
begin dbms_session.set_nls('nls_date_format', '''DD-MON-YYYY'''); end;
Rod West

ESS Error in EP for Working time -- Leave Request.

Hi,
We are on ESS 600 and EP 7.0. We have configured for the leave request and hence using the standard one. We are able to see the process succesully till steps as followed:-
1) Employee can apply to leave from ESS on EP.
2) Approver gets mail in the UWL.
3) Approver can Accept the leave.
4) We run the program to Post the leave.
5) Leave gets updated in infotype 2001.
6) We run program to send mail.
But the employee doesnt get any mail of approval from the approver in his UWL on EP. Any thing needs to be done to make this whole process successful. Kindly let me know.
Also kindly let me know whether the above steps are right and how do we make it automatic without any manual intervention. We need to schedule the jobs, if i am not wrong, but what programs need to be run at what time do let me know.
Thanks and regards,
Gaurav J.

Hi Gaurav,
The mails will be sent to the user's mail box. If you want it to appear in UWL, you need to set uo the SONIC connector. By default, UWL only reads workitem tasks. If you install SONIC, then this connector will enable UWL to read the sap r3 inbox as well.
You can go this link https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8525afd0-0d01-0010-aaa0-ac6b9e3a2907. You can try searching for SONIC in sdn forums also.
If you want to send mailos to external mail id's then configure SCOT and SOST.
Hope I am clear.
Regards
Reshma

Providing Calender option for dates in Leave Request form in ESS Portal

Similar Messages

Maybe you are looking for