3 days continous absence

Dear All,
I am doing an Implementation project.My client has this scenario.
IF AN EMPLOYEE IS CONTINUOUSLY ABSENT FOR 3 DAYS, ONLY HIS CONVEYANCE(only One WT should be deducted) SHOULD BE DEDUCTED.
WE HAVE created an absence type which will deduct only conveyance. but how to communicate the system to automatically deduct this WT
when there is a continuous absence for 3 days.
Please suggest me.
Thank you in advance!!!
Smitha

Hi Smitha ,
You have to approach abaper on this. Whenever there there is continuous absence for 3 days for an employee there should be a deduction of Conveyance Wage type
Take a help of abaper to meet your requirement
Hope you configured LOP
When we record absence type through date that is 01.01.2014 till 03.01.2014 that is continuous absence
when there is no continuous absence among dates the system shouldn't consider deduction of wage type
when there is continuous absent it should deduct conveyance wagetype, ABAPER can build a logic based on this

Similar Messages

Consecutive days of absence

Experts.
I have a query request using InfoSource 0HR_PT_2. (data volume is extremely large with this extractor.)
Business has 100k employees.
Client wants to see which persons have consecutive absences >= 20 days. (NOT 20 days or more total)
I have the restrictions on TYPES or ABSENCE and Users have not defined the periods of their search. (month to month, year to year?)
How can I count hours / days of data that sum up to 20 consecutive days?
Thanks for any suggestions, both backend or query based.
Steve

Experts.
I have a query request using InfoSource 0HR_PT_2. (data volume is extremely large with this extractor.)
Business has 100k employees.
Client wants to see which persons have consecutive absences >= 20 days. (NOT 20 days or more total)
I have the restrictions on TYPES or ABSENCE and Users have not defined the periods of their search. (month to month, year to year?)
How can I count hours / days of data that sum up to 20 consecutive days?
Thanks for any suggestions, both backend or query based.
Steve

Leave Req - workflow - leave days and absence hours

Hi,
For a leave request in workflow, how do i read the leave days (total number of leave) and absense hours from the workflow container? Which fields give that information?
Regards

Hi Partha Kar,
These Links are useful to You,
[Leave request example in workflow]
[Re: Employee Leave Request]
[Leave request auto approvals]
Regards,
Raghava Channooru

Auto Calculation of Calendar and absence day on 2001 screen.

dear gurus
I have half day absent type Z108, subtype of 2001.
i want to default calender days on 2001 screen.
I mean, when user select to create Half day leave/absent on 2001 and subtype z108,
calendar day and absence should be calculated 0.5 automatically.
I have worked with T554L,V_554S_G,V_T554E,V_T554C,T556 but didnt work
at this moment, I am getting this on 2001 screen
Absence hours                8,00
Absence days                 1,00
Calendar days                1,00
when select Z108.
I want above 3 as
Absence hours                4,00
Absence days                 0,50
Calendar days                0,50
kindly help in this scenario.

Hi Monam,
Can yuou check the view V_T554S for your absence type.
The minimum duration and maximum duration in 'Input Chceks' Box should be '000' and '999'.
Minimum duration in days
The Minimum duration in days defines the minimum permitted duration of
    an attendance or absence.
Attendances and absences that are allowed to last for less than one
    workday are assigned the indicator 000. Attendances and absences that
    are to be rejected by the system if they are shorter than one day are
    denoted by an indicator greater than or equal to 001.
Dependencies
In the Unit field, you determine which of the three durations in days
    should be used for the validation.
Thanks & Regards, Swapnil Mishra

More than one days absence

Dear all expert,
When we create absence for example from 2009.02.02's 12:30 to 2009.02.05' 17:15 , system will check with infotype 0007 and infotype 2003.For infotype 0007 is 08:30 to 17:15, for 2003 is empty.
But there is a problem that even though the employee only want to apply for absence from the first day's 12:30 and end of his absence at the last day's 17:15. But system think his absence is whole day absence, it is calculated as 4 whole days.

Hello,
For multiple days partial absence is not allowed.
So you need to separate partial days records.
R/3 system will not allow to input time for multiple days. Please check.
Regards

Absence day field in IT 2001

Hi All,
How to change the "Absence days field in IT 2001, bcz if i am taking Loss of pay it shoul take calender days ,
how to do thais
No if we taking 10 days it will deduct the week ends also ,
how we can manage in SAP
Thanks
SD

MVR.,
I followed the same, but coudlt able to fix
not what i have done is in DWS i make OFF days as paid (Unckecked the field "No Planned Working hours)I dont know more impact of this ..
not its is taking all teh calender days as absence for our LOP, LOP issue is fixed.
But the problem is
if EE is going on AL all days are picking , it should exclude thu and fri, even though i maintained uncheck in couting rule for AL it s tkng all the days
how we can
Appretiate immediate response
SD

Generate Absence Quota For Every 5 Years Service

Hi Expert,
First of all, I'm not familiar with PCR as I'm new with time management. Annual leave is generated via RPTQTA00 with no problem. But we have another absence quota (long leave) that is given to the employee every 5 years (22 days of leave). So every 5 years the employee would received 22 days of absence quota. Our problem is when Rptqta is executed, the deduction is start at 01.01.xxxx instead of hiring date. To make a better understanding
Expectation
Start Date | End Date | Deduction From | Deduction to
01.01.2010 | 31.12.2010 | 01.05.2010 (his hiring date) | 01.05.2014
Actual Result
Start Date | End Date | Deduction From | Deduction to
01.01.2010 | 31.12.2010 | 01.01.2010 | 01.01.2014
I have configure Validity period for default value to, Valid from date = date type : tech date of entry, Valid form date = Date type : tech date of entry.
What do i miss here? Thanks
Edited by: Hendri Salim on Nov 6, 2010 7:24 AM

Hi Semvladigo,
Acctualy we have set the validity period for default values to
Date Type : Technical Date of Entry
and validity interval to
Deduction from : Start of validity interval
and we have maintained 0041 for that employee, but still the start date is 01.01.2010 instead of 01.06.2010 (01.06 is date in the 41 and the years is 5 years after join). I hope i explained it clearly. Many Thanks

Create and Approve absence using BAPI's

Hello Experts,
I got to know that BAPI_EMPLOYEE_ENQUEE, BAPI_ABSENCE_CREATE & BAPI_ABSENCE_APPROVE. has to called in a sequence (test sequence) for creating and approving absence.
But when I test them I am getting the following error: "Attendance/absence type 0148 requires minimum of 1 attendance/absence days " for absence type 0148, when I try to use 425 it says fill in all required fields.
Please suggest,
Thanks,
Sandhya

Because of no relevant replies I am closing this question.....

Absence Request Workflow

Hello fellow Sap'ers.
I have an issue in a client which is the following. Due to an error in customizing for a few days, the absence requests created in ESS did not initiate the workflow for the request. We were able to find out the problem and fix it, but the problem is that meanwhile all absence requests created in this interval of days are "stuck" and don't appear in the task list for the aprovers. I have checked and the requests are created (PTREQ* tables) are all ok, the request is created with the status SENT and only has the version 1 record.
So my question is, how can i replicate the natural process, creating the workflow process for these requests ? I have tried with FM SAP_WAPI_START_WORKFLOW but i think i'm missing something in the containers, has i get an error.
The task we are using is WS90200027 which is probably a copy of the standard task for the Absence requests.
Thanks for all the help in advance.
Cheers.

Thanks for the reply, but we have solved this in another way. Using the program RPTARQUIATEST as a working base, i was able to find out that due to customizing when a request is in SENT status, a new send won't iniciate a workflow process, so i needed to reset the status to NEW and generate a EXECUTE_SEND event for these requests. Thanks for the help anyway.

How working days is treated and counted as leave day.

Q. What is working Days & How working days is treated and counted as leave day.
Case 1-suppose Absence is registered on 15.11.2010- 18.112010.but on 17.11.2010 is a public holiday.in as IT2001 it is showing as Absence hrs =24 days,Abs days = 3 days and Cal days = 4 days .Quota used= 4.
why it is not showing 32 hrs .
Thanks

The counting rule for absences takes care if the public holiday or non working days as to be counted when absence is entered or not.
If you tick on (not a public holiday) then only days which are not public holidays wll be counted in absence counting. If you dont check saturday sunday in the rule then sat sunday will be counted towards leave...Other options are also there for eg. Holiday classes. You can make appropriate settings and include or exclude the working/non working days from absence counting.

Salary increase with batch but exception

Hi everyone,
When you use a batch to create new IT0008 for annual salary increase, how do you deal with exceptions ? (i.e employee is in long absence and will be eligible to the salaray increase only at its return)
Most of my experiences when I was HR data analyst was to deal manually with these exceptions. Did any one found a great idea?
Thanks a lot on the behalf of my HR data collegue

Hi
Thats is the only way i also think.
Well on the techinical side i think if employee is in long absence in the program itself if condition is maintained like it should check first employee's time infotypes and according to the requirement let criteria is 20 days continous absent or 7 days continous absent then it should skip the upadation of it 8 otherwise update it.
Now those who are not selected keep a record of all those in other file and update it by same program with conditions.
less manual intervention is needed in this case but more program cost.
Manoj Shakya

BW-HR Reports (Time Management)

Hello Gurus,
Please help,I am new to BW and i was landed in BW-HR Projects
My reporting Requirment is
<u><b>TIME MANANGEMENT </b></u>
Organisational Unit
Date Selection
Absence Type
Staff ID
Staff Name
Absence Start Date
Absence End Date
Hours of Absence
Days of Absence
Please let me know how can i get this data from HR to BW...which BW Business content cube do i need to use and please please let me know the technical names of the respective fields that i can use in my report
Please don't give me link to help.sap.com...i already made a search......i can't understand exactly what it says
Please give me techical names of data targets 9Business Content) and the technical names of above fields that i can use
Thanks and will definitely assign points

Hi,
I hope, you need 0PT_C01 cube.
http://help.sap.com/saphelp_nw2004s/helpdata/en/93/3e1e3c6a2fc036e10000000a114084/frameset.htm
Organisational Unit---0ORGUNIT
Date Selection------0CALDAY
Absence Type-----TIME TYPE
Staff ID----0EMPLOYEE
Staff Name
I hope,the follwing things you can get by filter on Time type:
Absence Start Date
Absence End Date
Hours of Absence
Days of Absence
With rgds,
Anil Kumar Sharma .P

UWL refresh problem for ABAP BOR custom attributes

Hi all,
we are facing an issue with an UWL iView. We wanted to display custom attributes from an ABAP Business Object (ABAP_BOR).
The feature is working but when an end-user receives a new task in his UWL view, he needs to click on the refresh button in order to have all the custom attributes correctly displayed.
We have only the problem with custom attributes, for the columns containing standard workflow decision task attributes, the data are displayed directly without the need to push the refresh button.
We are on EP 7 SPS11 and the back-end is an ECC6 version.
We have followed the methodology described in the How to configure and customize the Universal Worklist pdf document:
ABAP BOR
<CustomAttributeSource id="ABAP_BOR"
objectIdHolder="externalObjectId"
objectType="FORMABSENC"
cacheValidity="final">
<Attribute name="COSTCENTER" type="string"
displayName="Cost Center"></Attribute>
<Attribute name="FIRSTDAYOFABSENCE" type="date"
displayName="First day of absence"></Attribute>
<Attribute name="LASTDAYOFABSENCE" type="date"
displayName="Last day of absence"></Attribute>
</CustomAttributeSource>
Do you have an idea where this problem come from and how it could be solved?
Thanks in advance and regards,
Sébastien BODSON

Hi Chintan,
This parameter has no impact on the problem we face. I found an exact description of our problem on SAP Help portal, in the UWL pages:
CustomAttributes, CustomAttributeSource and Attribute
Extract from SAP Help portal:
Every item type can have custom attributes defined, which can be filled from Business Object or Provider Data Containers like the Business Workflow Container or the Alert Container. These attribute sources are defined within the CustomAttributeSourcetag, which contains information on which attribute connector brings the custom attributes, how to identify these custom attributes in the provider system and how long the cache is valid.
Note that once an item arrives, these custom attributes are retrieved in additional calls to the backend. For performance reasons, in order to minimize responses times to the end user, this may happen while the item is displayed to the end user - causing such attributes to be empty initially and only to appear in subsequent requests.
The display names of the attributes for column headers and labels are defined in the display attributes of the default view of the item type.
Does anyone know a workaround in order to have directly the complete information displayed?
Sébastien BODSON

TYPICAL REPORT REQUIREMENT

hi experts,
Below there is a function spec so please can anybody send me the code for this requirement?can anybody send me the steps for thsi atleast?
please its urgent
1.1 Functions in Detail
The function of this report is to produce a summary buy organisational unit and Absence/Attendance type of staff utilisation during a preceding week.
The user is to select the date range for the week and delimit the report by key employee master data such as organisational unit, jobs and Absence/Attendance type. The report is to then calculate each employees utilisation by Absence/Attendance types and output the utilisation by Organisational unit and Absence/Attendance type.
See section 3.2.7 Processing logic for a full explanation of the calculation required
1.2 Processing
1.2.1 Trigger
· Execution of Report by user
1.2.2 Frequency of Use
Transaction is to be run on a weekly basis
1.2.3 Data Volumes
The primary group of staff involved will be Train Operators and this equates to approximately 3,600 Employees and their weekly Attendance and Absence data. We require columns for organisational units and this is currently 25, but a maximum of 30 should allowed.
1.2.4 Language considerations
English
1.2.5 Input Data
Date Range selection is to use standard logical database
The user selection options required except for Date Range are listed below along with the text we would like displayed:
Infotype Number Field Text Description Field Name Display Text required Selection Type
0000 Personnel Number PERNR Personnel Number Multiple Selection
0001 Org. Unit ORGEH Organisational Unit Multiple SelectionAnd Use of the Organisational Hierachy
0001 Cost Ctr KOSTL Cost Centre Multiple Selection
0001 Job Key STELL Job Multiple Selection
0001 EE Subgroup PERSK Employee Subgroup Multiple Selection
0001 CoCode BUKRS Company Code Multiple Selection
2001 Absence Type AWART Absence Type Multiple Selection
2002 Attendance Type AWART Attendance Type Multiple Selection
0008 PS Group TRFGR Grade Multiple Selection
Selection Variants, we require the ability to create and save the selection parameters entered so that these can be easily selected again
1.2.6 Sourcing the Input data
The Date Range selection option is to be used to select data as follows:
Active Employees within the selected employee master data where Employment Status (infotype 000 Actions) = Active
Absence Types and Absence Days within date range
Attendance Types and Attendance Days within date range
The data required to generate the report is listed by infotype in the table below:
Infotype Number Fields Text SAP Field name
0000 Employment Status STAT2
0000 Personnel Number PERNR
0001 Org. Unit ORGEH
0001 Cost Ctr KOSTL
0001 EE Group PERSG
0001 Job Key STELL
0001 EE Subgroup PERSK
0001 CoCode BUKRS
0007 Weekly Work Days WKWDY
2001 Absence Type AWART
2001 Absence Days ABWTG
2002 Attendance Type AWART
2002 Attendance Days ABWTG
0008 PS Group TRFGR
1.2.7 Processing Logic
In general terms this is about reporting upon active employees headcount in terms of Employment Status (from Infotype 0001) during the preceding week and comparing it to their Absence (infotype 2001) and attendances (infotype 2002) during the same week. This data is then summarised by Organisational Unit and absence and attendance type.
The output is to show the total employees utilisation by each absence type for each organisational unit (Infotype 0001) selected. This is a calculation for each employee where the days lost for that time type compared to the weekly working days (infotype 0007). The example output is can be found in 3.2.8 Output and the calculations required are below
Only Employee Group 1 data is to be used.
Processing and calculations involved in output
Employee X
3 days lost to Absence Type 320 (Sick)
Weekly Working Days = 5
Where days lost = D
Weekly Working Days = W
Formula for utilisation for Absence type is:
Utilisation = D/W
In the above example this would be 0.6 for Employee X
Employee Y
2 days lost to Absence Type 320 (Sick)
Weekly Working days = 2
In the above example this would be 1
Output on the report.
If the report were just run for these two Employees both at organisational unit ACTD then it would be the sum of the utilisation (1+0.6= 1.60) and the report output would be as follows:
Depots
Absence/ attendance type ACTD
320 Sick 1.60
Multiple Absence and attendance days.
There will be a few instances where the Absence and Attendance days data for the week exceeds the Employees Weekly Working Days figure in this instance the rule that is applied is as follows:
Sort Attendance or Absence Types in reverse alphabetical order
Deduct balance of days from Absence or Attendance that is alphabetically higher
Then divide Absence/Attendance days by Weekly Working Days
Worked example:
Employee X whos Weekly Working Days = 5
Absence Attendance Type Days Lost
Sick 4
Annual Leave 2
Total Days lost 6
Conversion required is to deduct 1 days sick as alphabetically S is after A
Therefore the following utilisation values should be reported against the Attendance/Absence type as follows
Absence/Attendance Type Days Lost Utilisation
Sick 3 0.6
Annual Leave 2 0.4
Total Days lost 5 1.0
This will ensure that an Employees utilisation in total will never exceed 1.
Please see the section on error handling. We would like the option of being able to view the instances where the above conversion has been applied.
If employees have moved during the week then their Absence/Attendance utilisation should be shown against the appropriate organisational unit valid at the time. If that organisational unit was not within the user selections
1.2.8 Output
The output is to show the total employee utilisation by each absence type for each organisational unit (Infotype 0001) selected.
Layout required for the report
Depots
Absence/ attendance type Org Unit Short Text 1 Org Unit Short Text 2 Org Unit Short Text 3 Org Unit Short Text 4
Type 1 10 2
Type 2 5 3 4
Type 3 20 30
The output of the report is to be limited to a maximum of 31 columns (including the Absence/ attendance type column).
The columns listed under Depot are the Short Text of the Organisational Units selected. Organisational units are to be sorted alphabetically from left to right by the Orgnisational Unit Short Text.
The Absence/Attendance type is to be sorted alphabetically in ascending order.
Further display options are required as follows:
All Reports are to have the capability of exporting into Excel via the Export icon which then copies the report directly into a workbook in Excel. This is more user friendly then the Local File option.
We require the ability to drill down and expand the report to see the individual employee details and absence Attendance days used to make up the utilisation figure used on the report. This is the figure actually used on the report and therefore if there have done any conversions due to multiple Absence/Attendance days exceeding the Weekly Working Days, then the figure after the conversion should be used. We require the ability for a user to select a column first and then drill down via a button. The drill down will be displayed via a pop-up screen. We also require the ability to export the data into Excel via the Export icon from the drill down. See example below.
Defualt view
Absence/ attendance type Org Unit Short Text 1 Org Unit Short Text 2 Org Unit Short Text 3 Org Unit Short Text 4
Annual Leave 4 2
Sick 5 3 4
Drill down view by selecting the column of Org Unit Short Text 1
Absence/ attendance type Org Unit Short Text 1
Annual Leave Personnel Number Name Utilisation Days Lost Weekly Working Days
Annual Leave 123456 P Smith 1.0 5 5
Annual Leave 234567 J Smith 1.0 5 5
Annual Leave 345678 D Jones 1.0 5 5
Annual Leave 456789 P Jones 0.6 3 5
Annual Leave 567891 A Harris 0.4 2 5
Totals 4 20 25
Sick Personnel Number Name Utilisation Days Lost Weekly Working Days
1.3 Error Handling
As referred to in 3.2.7 Processing logic, specifically where the data has had to be converted due to Absence or Attendance Days exceeding Weekly Working Days we would like the ability to see the exact details of the employees data prior to the conversion. The output required here is:
Employee Org Unit Absence Attendance Type Days Lost Weekly working Days
1234567 ACTD Sick 4 5
1234567 ACTD Annual Leave 2 5
Total 6 N/A

wtf?
you're aksing us paid consultants/inhouse developer who try to do the job as best as they can to do the work for you, for free?
I really hope the client who hired you finds out about this and fires you. In my contract I can be fined for a considerable amount if I lied in my CV.

TYPICAL REPORT

hi experts,
Below there is a function spec so please can anybody send me the code for this requirement?can anybody send me the steps for thsi atleast?
please its urgent
1.1     Functions in Detail
The function of this report is to produce a summary buy organisational unit and Absence/Attendance type of staff utilisation during a preceding week.
The user is to select the date range for the week and delimit the report by key employee master data such as organisational unit, jobs and Absence/Attendance type. The report is to then calculate each employees utilisation by Absence/Attendance types and output the utilisation by Organisational unit and Absence/Attendance type.
See section 3.2.7 Processing logic for a full explanation of the calculation required
1.2     Processing
1.2.1     Trigger
·     Execution of Report by user
1.2.2     Frequency of Use
Transaction is to be run on a weekly basis
1.2.3     Data Volumes
The primary group of staff involved will be Train Operators and this equates to approximately 3,600 Employees and their weekly Attendance and Absence data. We require columns for organisational units and this is currently 25, but a maximum of 30 should allowed.
1.2.4     Language considerations
English
1.2.5     Input Data
Date Range selection is to use standard logical database
The user selection options required except for Date Range are listed below along with the text we would like displayed:
Infotype Number     Field Text Description     Field Name     Display Text required     Selection Type
0000     Personnel Number     PERNR     Personnel Number     Multiple Selection
0001     Org. Unit     ORGEH     Organisational Unit     Multiple SelectionAnd Use of the Organisational Hierachy
0001     Cost Ctr      KOSTL     Cost Centre     Multiple Selection
0001     Job Key     STELL     Job     Multiple Selection
0001     EE Subgroup     PERSK     Employee Subgroup     Multiple Selection
0001     CoCode     BUKRS     Company Code     Multiple Selection
2001     Absence Type     AWART     Absence Type     Multiple Selection
2002     Attendance Type     AWART     Attendance Type     Multiple Selection
0008     PS Group     TRFGR     Grade     Multiple Selection
Selection Variants, we require the ability to create and save the selection parameters entered so that these can be easily selected again
1.2.6     Sourcing the Input data
The Date Range selection option is to be used to select data as follows:
Active Employees within the selected employee master data where Employment Status (infotype 000 Actions) = Active
Absence Types and Absence Days within date range
Attendance Types and Attendance Days within date range
The data required to generate the report is listed by infotype in the table below:
Infotype Number      Fields Text     SAP Field name
0000     Employment Status     STAT2
0000     Personnel Number     PERNR
0001     Org. Unit     ORGEH
0001     Cost Ctr      KOSTL
0001     EE Group     PERSG
0001     Job Key     STELL
0001     EE Subgroup     PERSK
0001     CoCode     BUKRS
0007     Weekly Work Days     WKWDY
2001     Absence Type     AWART
2001     Absence Days     ABWTG
2002     Attendance Type     AWART
2002     Attendance Days     ABWTG
0008     PS Group     TRFGR
1.2.7     Processing Logic
In general terms this is about reporting upon active employees headcount in terms of Employment Status (from Infotype 0001) during the preceding week and comparing it to their Absence (infotype 2001) and attendances (infotype 2002) during the same week. This data is then summarised by Organisational Unit and absence and attendance type.
The output is to show the total employees utilisation by each absence type for each organisational unit (Infotype 0001) selected. This is a calculation for each employee where the days lost for that time type compared to the weekly working days (infotype 0007). The example output is can be found in 3.2.8 Output and the calculations required are below
Only Employee Group 1 data is to be used.
Processing and calculations involved in output
Employee X
3 days lost to Absence Type 320 (Sick)
Weekly Working Days = 5
Where days lost = D
Weekly Working Days = W
Formula for utilisation for Absence type is:
Utilisation = D/W
In the above example this would be 0.6 for Employee X
Employee Y
2 days lost to Absence Type 320 (Sick)
Weekly Working days = 2
In the above example this would be 1
Output on the report.
If the report were just run for these two Employees both at organisational unit ACTD then it would be the sum of the utilisation (1+0.6= 1.60) and the report output would be as follows:
     Depots
Absence/ attendance type     ACTD
320 Sick     1.60
Multiple Absence and attendance days.
There will be a few instances where the Absence and Attendance days data for the week exceeds the Employees Weekly Working Days figure in this instance the rule that is applied is as follows:
Sort Attendance or Absence Types in reverse alphabetical order
Deduct balance of days from Absence or Attendance that is alphabetically higher
Then divide Absence/Attendance days by Weekly Working Days
Worked example:
Employee X whos Weekly Working Days = 5
Absence Attendance Type     Days Lost
Sick     4
Annual Leave     2
Total Days lost     6
Conversion required is to deduct 1 days sick as alphabetically S is after A
Therefore the following utilisation values should be reported against the Attendance/Absence type as follows
Absence/Attendance Type     Days Lost     Utilisation
Sick     3     0.6
Annual Leave     2     0.4
Total Days lost     5     1.0
This will ensure that an Employees utilisation in total will never exceed 1.
Please see the section on error handling. We would like the option of being able to view the instances where the above conversion has been applied.
If employees have moved during the week then their Absence/Attendance utilisation should be shown against the appropriate organisational unit valid at the time. If that organisational unit was not within the user selections
1.2.8     Output
The output is to show the total employee utilisation by each absence type for each organisational unit (Infotype 0001) selected.
Layout required for the report
     Depots
Absence/ attendance type     Org Unit Short Text 1     Org Unit Short Text 2     Org Unit Short Text 3     Org Unit Short Text 4
Type 1     10     2
Type 2     5     3          4
Type 3               20     30
The output of the report is to be limited to a maximum of 31 columns (including the Absence/ attendance type column).
The columns listed under Depot are the Short Text of the Organisational Units selected. Organisational units are to be sorted alphabetically from left to right by the Orgnisational Unit Short Text.
The Absence/Attendance type is to be sorted alphabetically in ascending order.
Further display options are required as follows:
All Reports are to have the capability of exporting into Excel via the Export icon   which then copies the report directly into a workbook in Excel. This is more user friendly then the Local File option.
We require the ability to drill down and expand the report to see the individual employee details and absence Attendance days used to make up the utilisation figure used on the report. This is the figure actually used on the report and therefore if there have done any conversions due to multiple Absence/Attendance days exceeding the Weekly Working Days, then the figure after the conversion should be used. We require the ability for a user to select a column first and then drill down via a button. The drill down will be displayed via a pop-up screen. We also require the ability to export the data into Excel via the Export icon   from the drill down. See example below.
Defualt view
Absence/ attendance type     Org Unit Short Text 1     Org Unit Short Text 2     Org Unit Short Text 3     Org Unit Short Text 4
Annual Leave     4     2
Sick     5     3          4
Drill down view by selecting the column of Org Unit Short Text 1
Absence/ attendance type     Org Unit Short Text 1
Annual Leave     Personnel Number     Name     Utilisation     Days Lost     Weekly Working Days
Annual Leave     123456     P Smith     1.0     5     5
Annual Leave     234567     J Smith     1.0     5     5
Annual Leave     345678     D Jones     1.0     5     5
Annual Leave     456789     P Jones     0.6     3     5
Annual Leave     567891     A Harris     0.4     2     5
Totals     4     20     25
Sick     Personnel Number     Name     Utilisation     Days Lost     Weekly Working Days
1.3     Error Handling
As referred to in 3.2.7 Processing logic, specifically where the data has had to be converted due to Absence or Attendance Days exceeding Weekly Working Days we would like the ability to see the exact details of the employees data prior to the conversion. The output required here is:
Employee     Org Unit     Absence Attendance Type     Days Lost     Weekly working Days
1234567     ACTD     Sick     4     5
1234567     ACTD     Annual Leave     2     5
Total     6     N/A

Hi
Take this to your ABAPper and they should get it written within a day or so.
Regards
Gareth

3 days continous absence

Similar Messages

Maybe you are looking for