Help with spec

Question

Hi,
I am actually learning HR and am trying to do this spec. Can anybody tell me something about this spec and how to proceed.
Points will be awarded.
thanks and regards,
bin
<u>Functional Specification ID</u>     IFS_016_01 and IFS_016_02
<u>Functional Requirements</u>
Objective
     This interface extracts data from different infotype in order to provide detailed information of the employees for Interface Id IFS_016_01 which will be run on daily basis and IFS_016_02 for the weekly basis.
Infotypes Extract        : 0000, 0001, and 0002, 0006,0041,0008,
Infotypes referenced   :  2006,
<u>Pseudo Logic</u>
•     Get employee number from PA0000 where End Date = ‘12319999’ and Status = active.
•     Check whether country grouping for the employee is belong to ‘US’.
•     If employee is under ‘US’ country grouping, then proceed with selecting necessary data from PA0002 for that particular employee with retail store position, else leave for that employee and proceed with next.
•     If the employee is in the retail store capture the details required for the output file.
•     Use the infotypes ‘0000’ for actions performed on that day.
•     Capture the additional infotypes ‘0002’, ‘0006’, ‘0041’ and ‘0008’
•     Select and store all Date Type and Data for Date Type from PA0041 for the employee inside internal table IT_PA0041.
•     Check on IT_PA0041 and find for Data Type for ‘Original Hire Date’ (U1), ‘Last Day Worked’ (UO), ‘First Working Day’ (40) and ‘Hire Date’ (71).
•     Convert date for ‘Original Hire Date’ (U1), ‘Last Day Worked’ (U5) and birth date into Julian date format.
•     The format of the Julian date is YYDDD; where - YY is the year for that date and DDD is the number of that day within that year.
For eg. Birth date = 28.02 1979. Therefore, in Julian date format, it will be 79059.
•     Concatenate date for ‘First Working Day’ (40) and ‘Hire Date’ (71) in CC, YY, MM and DD format.
•     Store records from internal table IT_RECORDS to detail structure IT_OUTFILE.
•     The outbound file layout is as described with no conversions.
•     Conversion of data is needed for century, Job code at store location which will have to be handled in middleware.
•     The file layout remains the same for daily and full but the data extracted for each of these files is different with days of information.
•     Produce output file.
<u>Interface Specification</u>
Interfaced System     
PA – IFS_016_01 Daily employee file to retail
PA – IFS_016_02 Full employee file to retail
<u>Output File Details</u>
Path and Filename     
Field No.     Field Name     Start Pos     Length     Format     Description
1     RETAIL-REC-TERR1     1     4     Char(4)     Territory
2     RETAIL-REC-CODE1     5     3     Char(3)     Space
3     RETAIL-REC-EMPNO     8     9     Char(9)     Employee Number (SSN #)
4     RETAIL-REC-F-NAME     17     15     Char(15)     First Name
5     RETAIL-REC-M-INIT     32     1     Char(1)     Middle Initial
6     RETAIL-REC-L-NAME     33     20     Char(20)     Last Name
7     RETAIL-REC-CODE2     53     1     Char(1)     C=Casual, E=Exempt,
N=Non-exemption
8     RETAIL-REC-TERR2     54     4     Char(4)     Space
9     RETAIL-REC-D-UNITS     58     5     Numc(9)     Value ‘0’
10     RETAIL-REC-M-UNITS     63     5     Numc(9)     Value ‘0’

Answer 1

Hello,
when you write a spec you have to take all the information you sent above and put it in a form that is easier for an ABAP Developer to understand and work with.
You should put in the specs the name of the fields that are need it.
For example in these two lines you wrote:
"Use the infotypes ‘0000’ for actions performed on that day.
• Capture the additional infotypes ‘0002’, ‘0006’, ‘0041’ and ‘0008’ "
which fields are need it, what is the Action code need it.
You have to write it down in more detail.
Maybe your ABAP-er can give you some example specs he already used, so you can see the format used.
Aranka