<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: TYPICAL REPORT in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/typical-report/m-p/2924683#M688912</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Take this to your ABAPper and they should get it written within a day or so.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gareth&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 25 Oct 2007 23:13:54 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-10-25T23:13:54Z</dc:date>
    <item>
      <title>TYPICAL REPORT</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/typical-report/m-p/2924682#M688911</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi experts,&lt;/P&gt;&lt;P&gt;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?&lt;/P&gt;&lt;P&gt;please its urgent&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.1	Functions in Detail&lt;/P&gt;&lt;P&gt;The function of this report is to produce a summary buy organisational unit and Absence/Attendance type of staff utilisation during a preceding week.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;See section 3.2.7 &amp;#150; Processing logic for a full explanation of the calculation required&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.2	Processing&lt;/P&gt;&lt;P&gt;1.2.1	Trigger &lt;/P&gt;&lt;P&gt;·	Execution of Report by user&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.2.2	Frequency of Use&lt;/P&gt;&lt;P&gt;Transaction is to be run on a weekly basis&lt;/P&gt;&lt;P&gt;1.2.3	Data Volumes&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;1.2.4	Language considerations&lt;/P&gt;&lt;P&gt;English&lt;/P&gt;&lt;P&gt;1.2.5	Input Data&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Date Range selection is to use standard logical database &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The user selection options required except for Date Range are listed below along with the text we would like displayed:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Infotype Number	Field Text Description	Field Name	Display Text required	Selection Type&lt;/P&gt;&lt;P&gt;0000	Personnel Number	PERNR	Personnel Number	Multiple Selection&lt;/P&gt;&lt;P&gt;0001	Org. Unit	ORGEH	Organisational Unit	Multiple SelectionAnd Use of the Organisational Hierachy&lt;/P&gt;&lt;P&gt;0001	Cost Ctr 	KOSTL	Cost Centre	Multiple Selection&lt;/P&gt;&lt;P&gt;0001	Job Key	STELL	Job	Multiple Selection&lt;/P&gt;&lt;P&gt;0001	EE Subgroup	PERSK	Employee Subgroup	Multiple Selection&lt;/P&gt;&lt;P&gt;0001	CoCode	BUKRS	Company Code	Multiple Selection&lt;/P&gt;&lt;P&gt;2001	Absence Type	AWART	Absence Type	Multiple Selection&lt;/P&gt;&lt;P&gt;2002	Attendance Type	AWART	Attendance Type	Multiple Selection&lt;/P&gt;&lt;P&gt;0008	PS Group	TRFGR	Grade	Multiple Selection&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Selection Variants, we require the ability to create and save the selection parameters entered so that these can be easily selected again&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.2.6	Sourcing the Input data&lt;/P&gt;&lt;P&gt;The Date Range selection option is to be used to select data as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Active Employees within the selected employee master data where Employment Status (infotype 000 Actions) = Active&lt;/P&gt;&lt;P&gt;Absence Types and Absence Days within date range&lt;/P&gt;&lt;P&gt;Attendance Types and Attendance Days within date range&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The data required to generate the report is listed by infotype in the table below:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Infotype Number 	Fields Text	SAP Field name&lt;/P&gt;&lt;P&gt;0000	Employment Status	STAT2&lt;/P&gt;&lt;P&gt;0000	Personnel Number	PERNR&lt;/P&gt;&lt;P&gt;0001	Org. Unit	ORGEH&lt;/P&gt;&lt;P&gt;0001	Cost Ctr 	KOSTL&lt;/P&gt;&lt;P&gt;0001	EE Group	PERSG&lt;/P&gt;&lt;P&gt;0001	Job Key	STELL&lt;/P&gt;&lt;P&gt;0001	EE Subgroup	PERSK&lt;/P&gt;&lt;P&gt;0001	CoCode	BUKRS&lt;/P&gt;&lt;P&gt;0007	Weekly Work Days	WKWDY&lt;/P&gt;&lt;P&gt;2001	Absence Type	AWART&lt;/P&gt;&lt;P&gt;2001	Absence Days	ABWTG&lt;/P&gt;&lt;P&gt;2002	Attendance Type	AWART&lt;/P&gt;&lt;P&gt;2002	Attendance Days	ABWTG&lt;/P&gt;&lt;P&gt;0008	PS Group	TRFGR&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.2.7	Processing Logic &lt;/P&gt;&lt;P&gt;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. &lt;/P&gt;&lt;P&gt;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&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Only Employee Group 1 data is to be used.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Processing and calculations involved in output&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Employee X&lt;/P&gt;&lt;P&gt;3 days lost to Absence Type 320 (Sick)&lt;/P&gt;&lt;P&gt;Weekly Working Days = 5&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Where days lost = D&lt;/P&gt;&lt;P&gt;Weekly Working Days = W&lt;/P&gt;&lt;P&gt;Formula for utilisation for Absence type is:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Utilisation = D/W&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the above example this would be 0.6 for Employee X&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Employee Y&lt;/P&gt;&lt;P&gt;2 days lost to Absence Type 320 (Sick)&lt;/P&gt;&lt;P&gt;Weekly Working days = 2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the above example this would be 1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Output on the report.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;	Depots&lt;/P&gt;&lt;P&gt;Absence/ attendance type	ACTD&lt;/P&gt;&lt;P&gt;320 Sick	1.60&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Multiple Absence and attendance days.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sort Attendance or Absence Types in reverse alphabetical order&lt;/P&gt;&lt;P&gt;Deduct balance of days from Absence or Attendance that is alphabetically higher&lt;/P&gt;&lt;P&gt;Then divide Absence/Attendance days by Weekly Working Days&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Worked example:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Employee X who&amp;#146;s Weekly Working Days = 5&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Absence Attendance Type	Days Lost&lt;/P&gt;&lt;P&gt;Sick	4&lt;/P&gt;&lt;P&gt;Annual Leave	2&lt;/P&gt;&lt;P&gt;Total Days lost	6&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Conversion required is to deduct 1 days sick as alphabetically S is after A&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Therefore the following utilisation values should be reported against the Attendance/Absence type as follows&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Absence/Attendance Type	Days Lost	Utilisation&lt;/P&gt;&lt;P&gt;Sick	3	0.6&lt;/P&gt;&lt;P&gt;Annual Leave	2	0.4&lt;/P&gt;&lt;P&gt;Total Days lost	5	1.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This will ensure that an Employees utilisation in total will never exceed 1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.2.8	Output &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The output is to show the total employee utilisation by each absence type for each organisational unit (Infotype 0001) selected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Layout required for the report&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;	Depots&lt;/P&gt;&lt;P&gt;Absence/ attendance type	Org Unit Short Text 1	Org Unit Short Text 2	Org Unit Short Text 3	Org Unit Short Text 4&lt;/P&gt;&lt;P&gt;Type 1	10	2		&lt;/P&gt;&lt;P&gt;Type 2	5	3		4&lt;/P&gt;&lt;P&gt;Type 3			20	30&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The output of the report is to be limited to a maximum of 31 columns (including the &amp;#147;Absence/ attendance type&amp;#148; column).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;The Absence/Attendance type is to be sorted alphabetically in ascending order.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Further display options are required as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All Reports are to have the capability of exporting into Excel via the &amp;#147;Export&amp;#148; icon   which then copies the report directly into a workbook in Excel. This is more user friendly then the &amp;#147;Local File&amp;#148; option.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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 &amp;#147;Export&amp;#148; icon   from the drill down. See example below.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Defualt view&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Absence/ attendance type	Org Unit Short Text 1	Org Unit Short Text 2	Org Unit Short Text 3	Org Unit Short Text 4&lt;/P&gt;&lt;P&gt;Annual Leave	4	2		&lt;/P&gt;&lt;P&gt;Sick	5	3		4&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Drill down view by selecting the column of &amp;#147;Org Unit Short Text 1&amp;#148;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Absence/ attendance type	Org Unit Short Text 1&lt;/P&gt;&lt;P&gt;Annual Leave	Personnel Number	Name	Utilisation	Days Lost	Weekly Working Days&lt;/P&gt;&lt;P&gt;Annual Leave	123456	P Smith	1.0	5	5&lt;/P&gt;&lt;P&gt;Annual Leave	234567	J Smith	1.0	5	5&lt;/P&gt;&lt;P&gt;Annual Leave	345678	D Jones	1.0	5	5&lt;/P&gt;&lt;P&gt;Annual Leave	456789	P Jones	0.6	3	5&lt;/P&gt;&lt;P&gt;Annual Leave	567891	A Harris	0.4	2	5&lt;/P&gt;&lt;P&gt;Totals	4	20	25&lt;/P&gt;&lt;P&gt;Sick	Personnel Number	Name	Utilisation	Days Lost	Weekly Working Days&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.3	Error Handling&lt;/P&gt;&lt;P&gt;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&amp;#146; data prior to the conversion. The output required here is:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Employee	Org Unit	Absence Attendance Type	Days Lost	Weekly working Days&lt;/P&gt;&lt;P&gt;1234567	ACTD	Sick	4	5&lt;/P&gt;&lt;P&gt;1234567	ACTD	Annual Leave	2	5&lt;/P&gt;&lt;P&gt;Total	6	N/A&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Oct 2007 09:55:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/typical-report/m-p/2924682#M688911</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-24T09:55:53Z</dc:date>
    </item>
    <item>
      <title>Re: TYPICAL REPORT</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/typical-report/m-p/2924683#M688912</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Take this to your ABAPper and they should get it written within a day or so.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gareth&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Oct 2007 23:13:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/typical-report/m-p/2924683#M688912</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-25T23:13:54Z</dc:date>
    </item>
  </channel>
</rss>

