ABAP WDP version of Leave Request under ESS

Dear Expert,

We are currently using the Java WDP version of the ESS Leave Request and plan to migrate to ABAP WDP version. However, we check that there are more than 200 OSS notes fixes for the ABAP WDP version. Also new fixes are kept on creating in April and May.

What is the reason for such a large volume of fixes? Is the ABAP WDP version of Leave Request mature ? Our management has concern on the risk for the migration.

Please share your experience and advice.

Thanks

Ivan

SAP Managed Tags:
SAP ERP,
HCM Employee Self-Service

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (2)

try once above those r wrking f9 for me i am also using wdabap leave requests

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Jwala,

Not exactly understand the message you are going to deliver with your screen dump.

hi ivan ,

exactly we want to know where your problem is getting in wdabap leave requests ...do u configured or or else you facing any issue once i suggest you to configure WDABAP leave request with all above sap notes i mentioned above and apply in ur system and proceed further and if you face any issue regarding wdabap leave request...repost here with exact screen shots or the issue you are facing .... i also recently configured wdabap leave request ..i am not facing any problem

Hi Jwala,

We are preparing a proposal on migrating to ABAP WDP. However, our management is challenging on the stability of the function in view of the volume of OSS notes released since 2013.

The problem is how to provide concrete evidence to our management that the function is stable.

its a continuing process this is not end ....it will be getting updated depending on each patch .level if its ehp8 next or any upper version again u have to update the sap notes also based on each ehp level ....convey to ur management my reply ...hope they will understand ....like we updates our mobile companies release android version ...android is not permanent version it will updating monthly may be like that ....hope u understand now.....like this u have to update our sap notes also

It's not that much oss notes released for fixes.

Currently your at which version of ECC and EHP ?

And for which version your planning to upgrade EHP ?

We have implemented for many customers this WDABAP based leave application. All working fine with out any issue.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

We are currently at ECC 6.06 and plan to upgrade to 6.07. Please advise how I can pass the list of 200 notes that we have identified for you to comment.

It seems your currently at ECC 6.0 with EHP6 and planning to upgrade to EHP7 . Correct me if my understand is not correct.

What's the Portal version your using ?

Where do you find that 200 OSS notes and did you check that notes are applicable for your ECC versions. The list may contain older notes also if you search in service market place with words leave request.

can you place some screen shot of that list which have seen the oss notes.

Yes, we are planning to upgrade to EHP7.

For Portal, we are at NW7.31 SP5 and will upgrade to the latest version to be finalised.

Below screen shot of OSS notes for reference.

These all notes looks like related to EHP6 & EHP7 versions. Your already in EHP6 and if your going for EHP7 with SP's n-1 level these all fixes will come automatically.

And some notes yes we have to implement if it's not released in SP's level.

Yes, we know, but the worry is that why there are more than 200 OSS fixes from Sep 2013 to May 2015.

If the function is stable, there should not be so many fixes. Also there are new fixes kept on releasing in Mar to May this year. What is happening to the Leave Request function? Is the function stable and mature?

Our management is very concern on this and challenge if it is a good choice to migrate to ABAP WDP Leave Request. Please help to address this.

You can upgrade and use the WDABAP based leave application with out any issues. And the list 200 OSS fixes are from Sep 2013 to May 2015 are belongs to EHP6 and EHP7 versions at different SP's Levels.

And those all will come automatically in next SP's Level release which ever they have released as fix in this current level of SP.

Your planning to upgrade to EHP7, so all those fixes are will come automatically. And few notes we have to implement if your not planning to upgrade to latest SP level.

well when you upgrade, you ll be getting all the notes in your SP> You dont have to apply them individually. So typically, whenever you patch your system in this case EA HR would be 607, you ll be also getting latest SP, and all the notes above would be redundant and wont matter Also, Leave request is there for 4 years now, and most of it will not apply to you and its stable, Please go ahead.

Dear Experts,

We are not concerned how to apply the notes, but we concern the volume of notes in this function since it is released. Why are there so many fixes and the fixes are still kept on releasing in the past few months. If the function is stable or issue free, why are there still notes being applied?

Please kindly help to explain this.

application is stable, as it was released 3 years ago and also some notes are for newer version of leave request which is based on SAPUi5 typically most notes wont apply to you as there might be errors unique to few customers. anyhow, this application is used by many customers i can attest to this

Dear Rajora,

Thanks for your reply.

May I ask if Rajora is member of the support team for the Leave Request function?

When you check the screen dump of the OSS notes, they are not UI5 related. In fact I have already excluded those UI5 related notes, but there are still substantial amount of notes.

I attach here for more notes released in June.

How I can assure to our Management that the Leave Request function is stable and there is no issue?

Can SAP officially reply the function is stable and there is no issue to migrate to this function?

Thanks

Ivan

yes i have been working on this for quiet a while both with support/product development/implementation. Its stable appication, i havent seen any major issues with it.

Dear Rajora,

You said it is stable, how would you explain OSS notes fix are kept on releasing even in this year.

How would you assure to our management that the function is stable with no issue, with the OSS notes kept on releasing this year?

reason being we released new enhancement packages till ehp7 ie new functionality for attachment and multiple approvers etc. most of the notes above are seeing from Clock in out. have you used leave request in Java earlier?

Hi Rajora,

We have been using Java Leave Request.

You mentioned "reason being we released...seeing from Clock in out".

Do you mean that these notes are not bug fixes? Also seeing from Clock in out, how is this related to the stability of the function?

Also for those notes from Mar to May, they are not related to CICO.

Thanks Rajora for your patience in answering my query. But we need to have more concrete evidence to our management that the function is stable. Can you help to provide?

what i meant is new functionality is being released for leave request and most of the bug were due to that, and no more enhancement is done As i said, a typical customers will not see all the bugs. Since you are applying latest SPs, you ll not see these issues I can only assure as i have been involved in many customers using this functionality, its upto you to decide and yes its stable solution as per perforamnce and stability wise

Hi Rajora,

You mentioned "most of the bug were due to new functionality", also "typical customers will not see all the bugs".

DO you mean that those bugs are not reported by customer?

What are those new functionalities?

Also do you have any statistics on the ratio of customer using Java and ABAP version of the LEave Request?

Are there any measurement within SAP on the stability of a particular function after being released?

Thanks

The reason, some bugs will be encountered depedending upon which functionality customer is using, I can only see 1000s of customer using ESS/MSS, but cant how much they use it, but i have been involved with many customers having more than 100,000 employees and havent seen much issues Most of the notes you listed above, are for different fucntionality and not specific to leave request. Search by WDA ESS LEA. Anyhow, i leave the decision to you, if there is a bug SAP will support you so not sure you have so many doubts Also i dont see any major bugs in the core functionality as its been there for quiet a while. http://scn.sap.com/community/erp/hcm/employee-self-service/blog/2014/04/18/hcm-ehp5-ehp6-and-hr-rene... http://scn.sap.com/community/erp/hcm/blog/2015/01/17/hr-renewal--information-and-useful-links http://scn.sap.com/community/erp/hcm/blog/2013/01/09/how-to-add-and-track-attachments-to-leave-reque... MULTIPLE APPROVERS ETC

Ask a Question

Top Q&A Solution Author

User

Count

100