Professional Documents
Culture Documents
GDEVWR0007430: Development Specification
GDEVWR0007430: Development Specification
GDEVWR0007430: Development Specification
Development ID GDEVWR0007430
IT0220 – Superannuation Australia Data Loading
Brief development description
Program
Gap ID FITGAP0025200
584647706.doc Page 1 of 20
Development Specification
Version Control
Revision History:
Section Version Description of change (including the Reference Changed Date
Reference No. reason for the change) Change By
Request
FS 1.0 Document creation Francine 3.02.04
Hill
1.1
1.2
1.3
TS 1.0
1.1
1.2
1.3
UTP 1.0
1.1
1.2
1.3
FS – Functional Specification
TS – Technical Specification
UTP – Unit Test Plan
Sign-off
584647706.doc Page 2 of 20
Development Specification
IMPORTANT: All paragraphs titles have been marked with a 'code', defining which
stakeholder is responsible for completing the paragraph. Please find below explanation
of the codes, as well as their roles in the process flow
FO Functional Owner (Systems Analyst)
AS Application Specialist
TO Technical Owner – AD Development Coordinator (On-site and Off-
Site)
QA QA reviewer (for messaging: both Messaging and AD)
DEV Developer
MWTO Middleware Technical Owner
MWQA Middleware QA Reviewer
MWDEV Middleware Developer
TOM Technical Owner Messaging – Messaging Coordinator
TOD Technical Owner Development – AD Development Coordinator
FO TO FO + TO TO TO QA + MWQA
584647706.doc Page 3 of 20
Development Specification
Table of contents
6 Appendix N: Testing.....................................................................................17
6.1 FUNCTIONAL TEST CASES (FO)........................................................................................ 17
6.2 Technical Test Cases (TO)............................................................................................ 17
584647706.doc Page 4 of 20
Development Specification
This development specification describes the local data load of Infotype 0220 – Superannuation
Australia from the legacy system into the global SAP HR system for the Oceania Globe Implementation.
New employees to Nestle are entitled to Company sponsored Superannuation governed by the Australian
Superannuation Commission. The Nestle Superannuation Fund administers these payments to the
Commission. Employees may also contribute a percentage of their gross income to the fund.
The employee superannuation details will be retrieved from the legacy system into a flat file. After
cleansing and validation is performed, the data is ready for loading into the SAP HR system.
The data will be collected into a loading sheet designed from this development by the DC / GCAOA team.
The loading sheet will detail the target structure and field names of the infotype.
The data is loaded into SAP using the SAP transaction LSMW (Legacy System Migration Workbench).
The volume of data is approximately 4,500 records. Therefore, a manual loading process is not feasible.
584647706.doc Page 5 of 20
Development Specification
The Superannuation data will be loaded to the SAP HR system using this conversion program. This
development specification will cover the requirements of the upload program and mapping to relevant
tables in SAP.
IT0220– Superannuation
Data Migration to SAP
SAP
Flat File
Legac MS Data
IT0220
Legacy y Data Excel to Loading
System SAP Program
via LSMW
584647706.doc Page 6 of 20
Development Specification
The Data Conversion program needs to upload data from a flat file to an internal HR SAP table, PA0220
via transaction PA30. The data from this table is displayed in the local HR Infotype 0220, Superannuation.
The program needs to be run via the LSMW transaction in SAP.
Infotype Concepts:
Infotype - A screen containing a logical grouping of fields used to describe information about the
employee. From a technical perspective, the data structure of infotypes mirrors a logical set of data
records. Infotypes can be identified by their four-digit code, e.g. 0220 Superannuation and is accessed by
transaction PA30.
Infotypes can be common and shared by markets, common but contain screen differences per market
and local infotypes, which are country specific. Infotype 0220 is a Country Specific infotype for Australia.
Country specific infotypes are developed to meet legal requirements for data reporting and require a
specific output file structure.
Key Field:
The Personnel Number (PERNR) is a unique key ID for each employee, and links all the records for an
employee. The Personnel Number will be assigned externally by each market and is used to link the
uploaded data to the employees record.
There are multiple fields in one infotype. Each of these fields have been assigned (in the DOS) either
one of the following field status’ by country grouping:
· M – Mandatory
· O – Optional
· X – Not used (display or hidden)
584647706.doc Page 7 of 20
Development Specification
584647706.doc Page 8 of 20
Development Specification
Comments:
how many records can exist at one time (time constraint 1);
if periods of time are allowed between records (time constraint 2), or
if records of the same type can overlap (time constraint 3).
IT0220 is configured with a time contraint of 1. This means that only one record is valid and cannot overlap
with another 0220 record. For particular infotypes, it also means that once the first record is saved, it
cannot be deleted – only overwritten or delimitted (split). The first record for IT0220 can be deleted.
584647706.doc Page 9 of 20
Development Specification
General Information
Development ID is correct
Reference documents provided
Market has been clearly specified
Document contents
'Management Summary' complete and clear
Process Flow / Context complete and clear
Description of development complete and clear
'How the development will work' complete
Data volumes have been provided
Currency and UoM details have been specified
Language requirements have been specified
Security requirements have been specified
All assumptions have been documented
Security Spreadsheet has been completed
All Test Cases have been described in Appendix N
Comments
584647706.doc Page 10 of 20
Development Specification
584647706.doc Page 11 of 20
Development Specification
Output SAP Table Field IDOC / BI / Loading Field Desc. Format SAP Default Required SAP Conversion rules / SAP Check Table
File Field Name program field name (Type Value (M/O). logic Validation for
name and validation
Length)
PERNR PERNR Personnel M Range for Oceania: PA0000
Number 02300000 – 02399999
CCNTR CCNTR Cost Center Defaults PA0001
PERSG PERSG Employee Group Defaults PA0001
ENAME ENAME Name Defaults PA0002
PERSK PERSK Subarea Defaults PA0001
WERKS WERKS Personnel Area Defaults PA0001
INFTY INFTY Infotype CHAR-35 M NNNN PA0220
BEGDA BEGDA Start Date DATS-8 M YYYYMMDD PA0220
ENDDA ENDDA End Date DATS-8 31.12.9999 M YYYYMMDD PA0220
FCODE FCODE Fund Code CHAR-4 M Configured values PA0220
SUP_P220_SGC SUP_P220_SGC SGC CHAR-1 O Flag PA0220
MEMNO MEMNO Membership CHAR-20 O Numeric Value PA0220
Number
EXCLF EXCLF Exclusion Flag CHAR-1 O Flag PA0220
JONID JONID Date Joined DATS-8 O Date PA0220
Fund
SUPSC SUPSC Super Usage CHAR-1 O Used to tell program to PA0220
calculate super based
on amount in SUPES
field
SUPFR SUPFR Pro rata CHAR-1 O Configured values PA0220
MEDCL MEDCL Medical CHAR-2 O Configured values PA0220
Classification
SUPES SUPES Salary Amount CURR-15 O Numeric value PA0220
REASC REASC Reason Code CHAR-2 O Not used PA0220
If the duplicate record has a BEGDA with a later date than the first record, the first record will be
delimitted with the new date period, creating two records. For example:
Result: First record becomes 01.01.2005 to 19.10.2005 (the day before the second record commences)
If the duplicate record has a BEGDA with an earlier date than the first record, it will first validate againist
the Org Assignment BEGDA (IT0001) and provide a warning if the 0220 record is earlier than the IT0220
record. It will then overwrite the the first record if validated. Both scenarios will issue a warning message
which requires validation.
Severe Error Conditions: Need to be mindful of warning messages given when a validation is occurring
between field values, or any other validation messages. Program should replicate validation
requirements.
Post Execution notification details: Use SAP standard. Specify all records that error.
Restart/Recovery: The program will not be able to be re-run because external number assignment is used
for the PERNR. Correct errors by restarting BDC.
584647706.doc Page 16 of 20
Development Specification
A. Preparation steps
e.g. When using Idocs, describe which port, partner type, partner function, etc need to be set up.
e.g. When a new upload program has been developed, then this program needs to be built in LSMW.
Describe in this section, the entries required in the SAP tables SXDA0, SXDA1, SXDA2 and SXDA3.
584647706.doc Page 17 of 20
Development Specification
Functional Section
Technical Details
Comments
584647706.doc Page 18 of 20
Development Specification
6 Appendix N: Testing
In this section, the actual execution of the testing should be documented as well.
Test Case Description Steps Test Data Expected Result Actual Result/Remarks Executed By/Date
Test Case Description Steps Test Data Expected Result Actual Result/Remarks Executed By/Date