Professional Documents
Culture Documents
Development ID GDEVWR0007432
IT0313 – Tax New Zealand Data Loading
Brief development description
Program
FITGAP FITGAP0025204
584647687.doc Page 1 of 19
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 7.02.05
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
584647687.doc Page 2 of 19
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
584647687.doc Page 3 of 19
Development Specification
Table of contents
6 Appendix N: Testing.....................................................................................18
6.1 FUNCTIONAL TEST CASES (FO)........................................................................................ 18
6.2 Technical Test Cases (TO)............................................................................................ 19
584647687.doc Page 4 of 19
Development Specification
This development specification describes the local data load of Infotype 0313 – Tax New Zealand from
the legacy system into the global SAP HR system for the Oceania Globe Implementation.
New employees to Nestle are required to submit their New Zealand Taxation Details as a legal
requirement to the Internal Revenue Department (IRD), and for Nestle to establish the correct taxation
deduction from salary.
The employee tax data is 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 1,000 records. Therefore, a manual loading process is not feasible.
584647687.doc Page 5 of 19
Development Specification
The Tax New Zealand 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.
IT0313 – Tax NZ
Data Migration to SAP
SAP
Flat File
Legac MS Data
IT0313
Legacy y Data Excel to Loading
System SAP Program
via LSMW
584647687.doc Page 6 of 19
Development Specification
The Data Conversion program needs to upload data from a flat file to an internal HR SAP table, PA0313
via transaction PA30. The data from this table is displayed in the local HR Infotype 0313, Tax New
Zealand. 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. 0313 Tax New Zealand 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 0313 is a Country Specific infotype for New
Zealand. 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)
584647687.doc Page 7 of 19
Development Specification
584647687.doc Page 8 of 19
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).
IT0313 is configured with a time contraint of 1. This means that only one record is valid and cannot overlap
with another 0313 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 IT0313 can be deleted.
584647687.doc Page 9 of 19
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
584647687.doc Page 10 of 19
Development Specification
584647687.doc Page 11 of 19
Development Specification
584647687.doc Page 12 of 19
Development Specification
Outpu SAP IDOC / Field Format SAP Require SAP SAP Check
t File Table BI / Desc. (Type Default d Conversion Validatio Table for
Field Field Loading and Value (M/O). rules / logic n validatio
name Name program Length) n
field
name
PERNR PERNR Personnel M Range for PA0000
Number Oceania:
02300000 –
02399999
CCNTR CCNTR Cost Defaults PA0001
Center
PERSG PERSG Employee Defaults PA0001
Group
ENAM ENAM Name Defaults PA0002
E E
PERSK PERSK Subarea Defaults PA0001
WERK WERK Personnel Defaults PA0001
S S Area
INFTY INFTY Infotype CHAR- M NNNN PA0313
35
BEGD BEGD Start Date DATS- M YYYYMMD PA0313
A A 8 D
ENDD ENDD End Date DATS- 31.12.999 M YYYYMMD PA0313
A A 8 9 D
TAXC TAXC Tax Code CHAR- M M PA0313
D D 6
TAXEE TAXEE Extra DEC-5 O Numeric PA0313
Emolumen
t Rate
SURCD SURCD Surcharge CHAR- O Not used PA0313
Code 3
TAXPC TAXPC Tax DEC-5 O Numeric value PA0313
Percentage
EPINC EPINC Add CHAR- O Flag PA0313
584647687.doc Page 13 of 19
Development Specification
Earner 1
Prem
STLPC STLPC Student DEC-5 O Numeric PA0313
Loan
Percentage
IRISS IRISS Year NUMC- O Numeric PA0313
Issued 4
584647687.doc Page 14 of 19
Development Specification
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 0313 record is earlier than the IT0313
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.
584647687.doc Page 15 of 19
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.
584647687.doc Page 16 of 19
Development Specification
Functional Section
Technical Details
Comments
584647687.doc Page 17 of 19
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