ESS Leave Application - Custom Field - Validation

Hi,
We have added two fields that are being shown in ESS Leave. Fields which are added are KEPAU and EXPAU through SPRO.
We want to do validation on these fields.
KEPAU is Annual Ticket and EXPAU is Vacation Allowance
We have implemented BADI PT_ABS_REQ to do validation but in this BADI these fields are not being populated.
Anyone knows that why these both fields are not appearing in BADI?
Thanks,

You need to check in  PT_ARQ_REQUEST_CHECK.
and also read here
http://wiki.sdn.sap.com/wiki/display/ERPHCM/ValidationsforESSLeaverequest

Similar Messages

  • 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 Leave request customer fields customization

    Hi all,
    I'm wondering how can add or modify the Data Type of one customer fields. I mean on the ESS leave request I need a customer field check box, or list of value for example.
    I try to append a structure to table PTREQ_CUSTOMER_STRUC, but this table cannot be enchanced....
    So any ideas?

    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

  • Leave request customer field as checkbox in ui5 leave request page

    Hi,
    we are trying to put an additional field (customer field) in leave request page.
    we added this via customization.
    and we want this to be appeared as checkbox, in the leave request page. for this for WDA page, there is option to change at WD fpm configuration, so it is appearing properly.
    but same thing, when we access via ui5 application, via hr renewal page, it is showing as input field.
    is there any way to make the customer field appear as a checkbox in HR renewal ui5 leave application page.
    thanks,
    Madhu_1980

    Here are the details for one of the additional fields
    1. We have enabled Customer Field - 'CUSTOMER01' using PTRAQ ->Fields customizing.
    2. We have then enhanced the feeder class CL_HRESS_PTARQ_LEAVREQ_GUIBBF method  GET_DEFINITION - in post-exit we have assigned search help  HTNM_PERNR to field 'CUSTOMER01'
    3. So when we launch the web-dynpro it gives search help for the field 'CUSTOMER01'
    I guess since the custom logic is on the feeder class which gets called only from the webdynpro it works on webdynpro and not on the UI, but can we implement the same kind of logic for the UI application as well, do we have any class similar to this feeder which sets the UI field properties.
    Thanks much!

  • ESS leave request, additional field

    I need to add three additional fields in ESS leave request (HR). I was told i can do that using web dynpro. I like to know how can I do it.
    Thanks

    hi Jeroen,
    Can u please help me with my issue.......
    My issue is to add new fields in ess/leave request i.e...
    The component needs to be Checked-out through Net Weaver Development Infrastructure, make the necessary enhancements, and finally Check-it-in back to NWDI.
    Custom Function Modules are to be invoked apart from the standard ones that are already available in the Leave Request component – ess~lea inorder to accommodate the extra absence-type logic.
    can u please sujjest me where should i make changes in the given 14 components
    means in which view i have to add these fields.................

  • MDG-F Custom field validation

    Hello Expert,
    I have extended MDG-F data model 0G for GL account with addition custom fields as mandatory field.
    I have one change request to Change GL account . Now as I have some old accounts which doesn't have this custom fields have values.
    When I trying to create CR with change GL account -> don't change any value -> submit
    then this validation doesn't through any error.
    Custom mandatory field still doesn't have any data but rules badi doesn't through any error bcoz no data change .
    Any notes ? Reason ?
    Thanks in advance ,
    Varun

    Hi Sanjay,
    Custom field is mandatory and displaying with red mark.
    So during change request creation ( Change request type is meant for changing GL account ).
    Expected result is when user submit CR then mandatory error msg.
    This is working correct when user change any of the field at UI.
    Step 1. enter account no and COA
    Step 2. enter Explanation
    Step 3. Change any field at UI
    Step 4. Summit -> CR generated with error ( Custom mandatory field is blank )
    But
    When if user do this.
    Step 1. enter account no and COA
    Step 2. enter Explanation
    Step 3. No change
    Step 4. Summit -> CR generated with error ( Custom mandatory field is blank )
    Regards,
    Varun

  • Enterprise Portal ESS -- Leave application with attachment

    Hi Experts,
    My client is looking for following feature in EHP5:
    Employee should be able to apply for leave using enterprise portal. The leave application should allow the user to attach the scanned document in Leave application.
    Please let me know if this feature is available in EHP5.
    Please also let me know whether the leave application for the EHP5 uses Java Web Dynpro or ABAP Web Dynpro.
    Regards,
    Gary

    Good Day Gary
    I have assigned the same task to add the attchment functionality on the leave application.
    Can you please help me with the solution.
    Thanks in advance.
    Canisius

  • ESS Leave Request - Custom validations

    Hello all,
    As I understand SAP does not perform any custom validations (which we might have coded within the PBAS0001 enhancement OR the HRPAD00INFTY business add in) when requesting a absence from ESS~LEA leave request iView from the portal.
    Hence to validate the absence record, I attempted to insert the HR_INFOTYPE_OPERATION function module and run it in CHK operation mode to validate the data in the PT_GEN_REQ~START_WF business add in method.
    If the validation fails I return RETURN_CODE as non-zero from the business addin. However I keep getting a dump as a result.
    Can anyone advice if this has been tried successfully and any alternate if @ all?
    Thanks in advance.
    Regards,
    Aditya

    You can easily to do so with badi pt_abs_req or pt_gen_req
    you can call exits in badi, read here the steps
    http://wiki.sdn.sap.com/wiki/display/ERPHCM/ValidationsforESSLeaverequest
    http://wiki.sdn.sap.com/wiki/display/ERPHCM/LeaveRequestVariousConfiguraton+Steps
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/108c31e7-b6a7-2d10-3692-c1a9f7a5c4dc?QuickLink=index&overridelayout=true

  • Custom Field Validation

    Hello there
    Is it possible to use a Javascript function to validate a field, rather than use the “Validation Pattern” approach?  I am OK to write the function, however I also want to be able to use it with the Form Level Validation Settings (having the function run again when the form submits etc.).
    I have seen references to the “Run custom validation script” option on a Validate tab, however I don’t see these.
    I am using LiveCycle Designer 9. 
    Many thanks
    Geoff Olding

    Tried it here and it worked fine. Here is my code on the Validate event of the field I wanted to test:
    if (this.rawValue == "1111"){
    true
    } else {
    false
    If the user enters 1111 in the field then true is rturned and nothing will happen and the tab will put thecursor in the next field. If they eneter anything else then false is returned and the Validate script error message is displayed.
    Paul

  • ESS - Leave Request Display Fields

    Hi:
    On the leave request screen in ESS, the following fields are displayed at the bottom of the screen: 
    Type of Leave
    Date
    Time
    Duration
    Approver
    Note for Approver
    Does anyone know if it is possible to hide the Time fields? If so, where are the changes made? These fields will not be used as part of our leave request process.
    Regards,
    Brian

    Yes personalisation
    or
    Make sure in the counting rule you have defined this absense
    Condition < 1 day? Is this checked? if not checked you ll not
    see the Clock Times
    ALso check the T554s customisation for the absence?
    Minimum duration is given as ?
    Please check the configuration of the
    absence type does it allow the partial day to be booked?
    ie In the Counting Rule ( T556C) can you book only full day or partial
    day.
    Also
    Feature HRSIF had value '0'. So the system
    generated clock times itself. But when you set the feature to '1' then
    the probleme is solved.

  • ESS Leave Custom fields, how to update them using BADIs

    Hi There,
    We are trying to use custom fields provided in ESS leave application, and we want to update them using BADI. As these information is not available on the screen while requesting leave request.
    I did look at PT_ABS_REQ BADI and seems i can use Post_Vio_BLOP .. but its unable to update table PTREQ_ATTABSDATA .
    Can you please suggest what can be best approach here.
    Thanks a lot.
    Rgds,

    Sudhir wrote:>
    > I did look at PT_ABS_REQ BADI and seems i can use Post_Vio_BLOP .. but its unable to update table PTREQ_ATTABSDATA .
    Did you look at using the Implict Enhancement Options available at the beginning & end of the POST_VIA_BLOP Method? Or even better, enhance the Class CL_PT_ARQ_REQ_EXIT & replace the IF_EX_PT_ABS_REQ~POST_VIA_BLOP Method with an Overwrite Exit?
    ~Suresh

  • 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 don’t 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

  • Import leave application from NWDI to NWDS

    Hi,
    I want to modify the ESS leave application. I want to define default value in "duration" field of ESS leave webdynpro application.
    I have imported the ESS  buisness package into NWDI...  i was also able to import from NWDI into NWDS.
    I have imported ess/lea by right clicking on it and then choosed "create project" option...
    I want to ask whether is this the correct way or not..
    After creating project in NWDS i went into webdynpro perspective i checked all the component, but i did not find the main view of leave request which i want to modify..
    I checked in under application..it has leaverequest application.. but i need the view which i am not able to figure out exactly which one it is..
    Is there any way we can find easily the view we require...?
    Regards,
    Jigar Oza .

    Hi
    Too many thing are involved to reflect  changes in SLD
    You can follow a simple workaround
    1. Do what ever u want in your track (But with proper activity and its description also so that in future u will able to identify what is for what )
    2. U can deploy the DC and  check whether your changes is working or not.
    Now
    3.Stop all the activity (your activity not track ), and simply change the workspace.(and keep this safe with you)
    4. You have applied all the changes and seen the result also , By changing the workspace u can continue with your work but not in same place  but different .
    5. In future if you/client want to make those changes should migrate , Here u simply open the that workspace in your NWDS  NWDI will keep track of that , and will automatically ask for user id and password .once provided will able to work from there where u were left.
    Only thing to take care : Dont do anything like checkin ,activate ,remove etc.
    Best Regards
    Satish Kumar

  • SBL-DAT-00398 error msg for User Field Validation

    Hi All,
    I have created the following field validation on the User field "Division": Len([<Division>])>0 AND InStr([<ltValidation_OU_ITAG>],[<Division>])>0, As the "Division" field is free text, the porpuse of the validation is to prevent the user from entering in this field any value that is diffrent from the ones available in the custom field "Validation OU" via the User Owner Page Layout. The validation works OK for Admin Role via the User Admin Page Layout but a SBL-DAT-00398 error msg stating " Field '<Division>' does not exist in definition for business component 'Occam Current Employee' " appears when users with other roles are trying to update this field via the User Owner Page Layout.
    I have contacted OD Customer support and they validated this in several POD saying this "is most likely a defect in the application" and a CR will be submitted to dev team to fix it sometime in the future.
    I am wondering though if support isn't making life easy here stating the above...:
    1. Anyone encountered this error before? (couldn't find any trace for this on My Oracle Support)
    2. Anyone aware of field validation limitations for the 'User' entity?
    3. Workaround suggestions are welcomed
    10X for you help!
    Alex.

    Error(), fatal(), info() and warn() issue FacesMessages that get picked up by the MessageGroup component.
    By adding in the uicomponent you can target the facesMessage so that it gets picked up by the Message component associated with the field causing the error.
    But, to get the label to show the error as well, you need to throw a validationError. See this tutorial for more informaiton:
    http://developers.sun.com/prodtech/javatools/jscreator/learning/tutorials/2/customvalidator.html
    Lark

  • You are not a receiver of the work item in ESS Leave

    Hi,
    We are using standard ESS leave application in our portal, where employee can raise leave and his manager can approve/reject his leave. But I want in case manager rejects the leave, the rejected leave should not come into MSS UWL of employee, we will send a mail to employee and he can again login to ESS leave application and where he will see the rejected leave and he can re apply/change/delete  the rejected leave. We do not want rejected leave to come in UWL of employee as a work item.
    As of now when manager rejects the leave rejected leave of an employee , it is coming in UWL of the employee which we do not want, so what we did, we went to standard leave work flow template WS12300111, in that we double clicked on Task (TS12300116, Process Request by Employee) and in that  we clicked on agent assignment icon and than we clicked on attribute and we selected General forwarding not allowed radio button, by default general task radio button was selected.
    After selecting General forwarding not allowed radio button, even when manager rejects employee leave, rejected leave is not coming in UWL of employee which we want exactly, but another error is coming when employee goes to ESS leave application again and change or delete this rejected leave he is getting the error You are not a receiver of the work item .
    But if we select general task radio button in agent assignment in work flow , than eveything is working fine but employee is getting rejected leave in his UWL, that we do not want  at all, so why after selecting different radio button this error is coming ?
    Why employee is getting this error, why employee can not reapply/change his rejected leave. Is this portal error OR workflow error OR HR configuration error and  what is the solution for this..

    If you need this option then you need to change the WF Task.
    General Forwarding Not Allowed
    This indicator enables you to determine that work items for this task can only be forwarded to users who are agents for the task.
    If this indicator is not set, a work item for this task can be forwarded to all users.
    The best way to take care of User
    Forwaring authorization is the Task Classification (PFTC -> Additional
    Data -> Classification). Classify tasks with General Forwarding Not
    allowed, will give you the oppotunity to let the user allow to forward
    items JUST to the Possible Agents Assigned to the task
    (Additional Data -> Agent Assingment -> Maintain)...
    Clear that everything depends on How you have developed your workflows
    definitions. In that cases  the best think to do is
    create Different Tasks definition (TSxxxxxx) and let they start
    depending on Company Code (That can be driven via Conditions steps in
    the workjflow definition, for example). This will allow you to define
    Just the responsible Agents per each task, depending on the Companny
    Code. This definitively Resolve the Forwarding frelated Question.

Maybe you are looking for