Negative quota deduction - ESS Portal and Backend (Complex problem)

[Former Member]

Hi experts,

This might be a complex problem.

We are having several employees getting an error when they try to book a leave that would deduct from quota 30 (which allows negative deduction to 4,48333- hours).

If we try to book on the backend the system works fine (gives you the info message regarding negative deduction), if we try through the Portal system gives you the error message HRTIM00REC 014 regarding insufficient quota.

Please find on the following link all the details (data, config and testing details).

http://dl.dropbox.com/u/7487637/Not%20enough%20quota%20in%20ESS%20Portal.pdf

Thanks in advance!

Best,

Andre Sousa

[siddharthrajora · Accepted solution]

When an employee send a leave request in ESS, the records will not be

real deducted from IT2006 in backend. The real deduction is after the

manager approve the request in MSS. In other words, the real records is

deducted from IT2006 and transfered to IT2001, after manager approve the

request in MSS. That does not depend on when the request sent by ESS

end user.

This is the standard functionality. A simulation run during quota

overview does not perform all the extensive checks which are performed

during posting. Hence there is no error in current standard release

version.

After using Rptarqpost you ll have corrct quota update or you can suppress the messages as explained below!!

http://wiki.sdn.sap.com/wiki/display/ERPHCM/LeaveRequestCustom+Messages

The function module which is called is HR_BLP_MAINTAIN_TIMEDATA.

It is called inside the following Leave request method:

CL_PT_ARQ_BLOP_ADAPTER -> MAINTAIN_TIMEDATA

In the BAdi PT_ABS_REQ, the method SIMULATE_VIA_BLOP takes care of all

quota calculation. It derives which quota types to be deducted during

simulation. Here you can have your custom code implementation to

influence the standard behavior as per your business requirements.

Its more of a simulation in ESS so no actual like backend!

Please read the note 1070831 on how tis works!

Also if you want to display this error as warning even this

can be congigured:

With our new Leave Request application, we've taken the approach to

display all messages the same way they are displayed in the Time

Manager's Workplace (TMW) transaction PTMW. In this case, the error

message HRTIM00REC 014 regarding the insufficient quota is displayed.

The customizing of the Leave Request application permits changing the

message type from error to warning so that the system behaviour observed

with the previous leave request can be retained.

The customizing View can be found in the Implementation Guide following

the path "Personnel Management > Employee Self-Service >

Service-Specific Settings > Working Time > Leave Request >

Processing Processes > Configure Output of Messages".

[Former Member · Accepted solution]

Thanks for your quick reply.

I guess you are saying that this is working as designed and it is not possible to customize a quota which allows negative deductions: "negative ammount" will not be considered as "remaining quota" and ESS will always give the HRTIM00REC 014 error message.

We cannot change HRTIM00REC 014 message to a warning message because that would change for all cases (when employee doesn't have any quota remaining).

Do you suggest any work around available?

Shouldn't this be considered as a genuine bug from SAP?

Thanks in advance.

Best,

AS

[Former Member · Accepted solution]

Hi,

The first thing I would look for is to see if there are any other leave request for this employee that results in the quota limit being exceeded. If you find any, delete them or try another employee. If there are no other leave requests, then you will have to look at the total quota that is available vs the about of time you are trying to request.

Remember if the value is greater than the limit by ANY amount over the limit, then the system will present this message. Another thing to look for is the deduction period for the specific set of quotas you are trying to test with.

I hope this gives you a couple of ideas.

Cheers

[siddharthrajora · Accepted solution]

Yes this is the standard behavior as no Negative Quota check is performed during the requesting of leave, these special checks are only carried out during the posting of the leave ie rptarqpost!

ALl these complex checks doesnt happen in portal

if you want these checks you need to implement above methods or use this

If your business requirement is as such that it is not acceptable to the

users then you can make the modification. In the BADI PT_ABS_REQ, the

method SIMULATE_VIA_BLOP takes care of all this calculation. It derives

which quota types to be deducted. Here you can have your custom code

implementation to influence the standard behavior.

[Former Member · Accepted solution]

Hi Rajora,

Thanks for your feedback. I did that in debug mode and I was able to submit the leave request and manager was able to approve.

Anyway that will not solve our problem because when I ran report RPTARQPOST system does not allow me to save this absence (which would deduct the quota 30 - to a negative ammount). Log returns the HRTIM00REC 014 error message when posting.

Thanks a lot for your help this is a complex requirement and I appreciate your suggestions.

Best,

AS

[siddharthrajora · Accepted solution]

if RPTARQPOST gives an error message then indeed your requested above your quota limit plus the Negative amount

so check all his leave request in Rptarqdbview of this employee, and ensure it doesnt exhaust the quota

The only option is to use a badi and check for this or make the message as warning unfortunately, this is the two options you have! You need to make the changes as above to realise this!

[Former Member · Accepted solution]

Following your hint I was looking at configuration for counting rule

013 (assigned to absence type 1301) and I figured out that no over

entitlement deduction rule was assigned to this counting rule.

I did assign the same counting rule for over entitlement and it seems

to be working fine.

Anyway I found out that this issue was not happening on the backend

because they only create absences of type 1301 in January and they

create them for specific dates of the year (usually on the week between

Christmas and New Year).

As on the Portal behavior is a little different because it does a re-

processing of future dated absences, it will always re-process those

absences of type 1301, assigned to counting rule 013 that didn't have

over entitlement deduction rule assigned.

I am doing final tests with the client to confirm everything is working

fine.

Best regards,

Andre Sousa