2009560 - en_note2009560_roughplan_v1.4

SAP Japan/Globalization Product Management JapanMarch 03, 2015

Legal Change of Social Security andTax Number System in SAP ERP HCM(Rough Plan)

2014 SAP AG or an SAP affiliate company. All rights reserved. 2CustomerThis presentation and SAPds strategy and possible future developments are subject to change and may be changed by SAP at any time for anyreason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, theimplied warranties of merchantability, fitness for a particular purpose, or non-infringement

Change History

Version Page Changes Date Author

1.2 English version created Jan 22, 2015 SAP Japan1.3 4 Required HRSP for Phase 1 Jan 30, 2015 SAP Japan

1.4 4 Target release for Phase 2 Mar 3, 2015 SAP Japan1.4 9 10 Planned dates for JSUG sessions Mar 3, 2015 SAP Japan


The information in this presentation is confidential and proprietary to SAP and may not be disclosedwithout the permission of SAP. This presentation is not subject to your license agreement or any otherservice or subscription agreement with SAP. SAP has no obligation to pursue any course of businessoutlined in this document or any related presentation, or to develop or release any functionalitymentioned therein. This document, or any related presentation and SAP's strategy and possiblefuture developments, products and or platforms directions and functionality are all subject to changeand may be changed by SAP at any time for any reason without notice. The information in thisdocument is not a commitment, promise or legal obligation to deliver any material, code orfunctionality. This document is provided without a warranty of any kind, either express or implied,including but not limited to, the implied warranties of merchantability, fitness for a particular purpose,or non-infringement. This document is for informational purposes and may not be incorporated into acontract. SAP assumes no responsibility for errors or omissions in this document, except if suchdamages were caused by SAPs willful misconduct or gross negligence.All forward-looking statements are subject to various risks and uncertainties that could cause actualresults to differ materially from expectations. Readers are cautioned not to place undue reliance onthese forward-looking statements, which speak only as of their dates, and they should not be reliedupon in making purchasing decisions.

Legal disclaimer


SAP ERP HCMRough plan for Social Security and Tax number system

2 different approaches would be assumed for this legal change and 3 phases deliveryare planned to adopt both approach.

Assumed Approach (1) Individual Numbers shall be store in SAP ERP HCM (2) Individual Numbers shall be handled by BPO service

Planned DeliveryPhase 1: Master Data relevant objects such as infotypes - May 2015 (Plan) Separate new Infotype to control authorization for individual numbers Mass download/upload function to manage infotype for individual number Access log, Middle name handling etc. For Access Log function, donwport to EHP4 and ERP 6.0 is planned. In EHP4, SAP_HR 604 SP20 is the prerequisite.

Phase 2: ESS relevant objects Aug 2015 (Plan) ESS scenario for collecting individual numbers from Employee if it could be reasonable according to regulations.

(EHP5 and later)

Phase 3: Reports Q4 2015 or later (Plan) For the existing statutory reports with multiple output option, such as use or no use of SAPScript like Withholding

Tax Statement, reduction of these output options will be considered. The government will finalize the detailed requirements for statutory reports depending on the necessary timing of

each reports. The delivery of corrections of each reports shall depend on their schedule. Output option without showing individual numbers should be considered based on the necessity in each report.


Approach to this Legal Change (1)Typical use case for customers

IndividualNumber Admin

Individualnumberhandling

func.

IT0002IT0021others....

Reports withoutIndividualnumbers

Reports withIndividualnumbers

output Output

Employee

PY Admin

HR Admin

submitHCM forms

withIndividualnumbers

Other ESSscenarios ESS

ScenariosAccess log

Access log

Individualnumbers

Access log ofIndividual numbers

Access control based onauthorization concept

Reduce workload of confirmation ofcorrectness and identity:1. Mass update function from data file2. Mass update function for ESS data

Mask individual numbers for:1. Unauthorized users2. Purposes which is not stipulated by

law (including WTS output forcertificate of salary purpose)

1. Correctness check against validationlogic when INPUT

2. Access control by authorization3. Masking for unauthorized users4. Masking for output after retention

period of each purpose5. Access Logging when the number is

shown without masking

ESS Scenario forcollecting Individualnumbers from EE andEEbs dependents


Approach to this Legal Change (2)Some customers may use BPO for Individual Number

Individualnumber

handling func.IT0002IT0021others....

Reports withPERNR and key

info of dependents

output

Employee

PY Admin

HR Admin

Other ESSscenarios

Individualnumbers

PY Admin willkeep theirexistingprocess

Output PERNR and key infoof dependents instead ofIndividual Number (Datafile output is required forthis output option)

HCM formswithout

Individualnumbers

BPO services

IndividualNumber withID cards etc

Reports withIndividualnumbers

output

Individualnumber DB

BPO service will collect EE and EEbsdependents individual numbers

No IndividualNumbers inERP HCM

Authorities

Convert PERNR andkey info of dependentsinto individual number

PERNR andnecessary info

Status updateof collection

Audit report

External

Provide EE anddependents info

Collection statusand audit reportshall beprovided.

Status ofcollectednumbers will beupdated


Planned options to collect Individual numbers

4. ESSevidencefile upload

3. ESS +evidence by

paper2. Mass updatevia file upload

1. Master dataupdate for each

Employee

Individualnumberadmin

Employee Employee

Individualnumberadmin

Individualnumber IT

Massupdate

Confirmidentity

Confirmedfile of EE

Confirmidentity

Number andstatus shall be

updated

Individualnumber IT

ESS

Numbersshall beupdatedvia ESS

Individualnumber admin

Copy ofevidence

Mail

Massupdate

Status shallbe updated

Individualnumber IT

Updatefunc.

Number andstatus shallbe updated

Employee

Individualnumber IT

ESS

Numbersshall beupdatedvia ESS

Individualnumber admin

PDFupload

Massupdate

Status shallbe updated

Upload

File

Mail or face-to-face

File shallbe

distributed

Attachmentsheet

Consideredin Phase2


Planned activities for LC

SAP

JSUG

Gov

2015 (H27) 2016 (H28)

WS

ESS Reports

Announce note update, E-mail newsletters

Notifynumbers

Preparation of details, such asCabinet orders, ministerial orders, etc

Individual number card shall beissued

Start using the numbers

2/24 9/1

5/30

JSUGJSUG

JISA WG

Master dataobjects

WS

9/1

10/24

ReviewWS

Infosession

Finalize the details of statutory reports

ReviewWS

Infosession

2014 (H26)

Pilot test (Plan)

* JSUG event like Infosessions shall be done

in Japanese.3/12 Aug-Sep

4/28 10/2


(Example) Assumed Timeline

SAP

JSUG

Gov

2016Individual number cardshall be issued

Start using the numbers

10/24Finalize the details of statutory reports

Preparation of details, such asCabinet orders, ministerial orders, etc

2014 2015 (H27)

ESS

Notifynumbers

Master dataobjects

ReviewWS

Infosession

ReviewWS

Infosession

Reports

Collect info

Plan

Note Impl. Master data (+ESS)

LC overview Release plan Timeline

Impact analysis based on theassumptions

Prepare draft plan Plan for apply note/SP Test plan

Customer

Impact analysis Bus. process Functions

Authorizations Corrections Test execution

Note Imple. Reports

Impact analysis Corrections Test execution

Announce note update, E-mail newsletters

Many object in PY-JP shall be affected especially in phase 3. Prerequisites for the LC notes mayinclude many notes. Considering the timeline by the authorities, the timeline in phase 3 shallbe so tight. It is recommended to install HRSP before phase 3.

Start operation

May Aug Oct -

3/12 Aug-Sep

4/2810/2


SAP ERP HCMPlanned statutory reports 1/3

# Report name Program name IndividualnumberCorporateNumber

1 () RPLDTDJ0 EE, DEP ER2 RPLLIDJ2 EE, DEP ER3 RPLLIDJ3 EE, DEP ER4 ) RPCEADJ0 EE, DEP ER5 HR-J : RPCRTSJ0 EE ER6 RPCWTSJ0 --- ER7 RPCNRPJ0 --- ER8 ) RPCPRTJ0 --- (ER)9 RPCRESJ0 EE (ER)

The authorities have not finalized the details of statutory reports yet. However, some of theplanned changes are provided in the website of NTA and MHLW.

NTA: http://www.nta.go.jp/sonota/sonota/osirase/mynumberinfo/MHLW: http://www.mhlw.go.jp/stf/seisakunitsuite/bunya/0000063273.html

Besides the reports below, Health Insurance Union and Job-Placement Office shall requirethe individual numbers from the existing employees and employeesb dependents.Corrections in SAP ERP HCM for these reports, including output options such as use ofSAPScript, shall be considered depending on the details of the LC finalized.

Tax relevant reports: Start from 2016




10 -) RPCUEMJ0 EE ---11 RPCEIAJ0 EE ---12 RPCEILJ0 EE ---13 RPCELVJ0 EE ---14 RPCEIBJ0 EE ---15 /() RPCEICJ0 EE ---16 60 RPCEWCJ0 EE ---17 RPLCLBJ0 EE, (DEP) ---18 RPLNLBJ0 EE, (DEP) ---


19 ) RPLDQOJ1 EE ---20 () RPLSHOJ0 EE ---21 ) RPLHUOJ0 EE ---22 () RPLPFOJ0 EE ---23 ) RPLDQLJ1 EE ---24 () RPLSHLJ0 EE ---25 ) RPLHULJ0 EE ---26 () RPLPFLJ0 EE ---

Employment Ins: Start from 2016 Jan

Health Ins and Pension Ins: Start from 2017 Jan




27 RPCSILJ0 EE ---28 ) RPLDQAJ0 --- ---29 () RPLSHAJ0 --- ---30 ) RPCSICJ0 (EE)* ---31 () RPCSHSJ0 (EE)* ---32 ) RPCHUSJ0 (EE)* ---33 () RPCPFSJ0 (EE)* ---34 ) RPCSIEJ0 (EE)* ---35 () RPCSHGJ0 (EE)* ---36 ) RPCHUGJ0 (EE)* ---37 () RPCPFGJ0 (EE)* ---38 / RPCSIPJ0 EE, (DEP) ---39 () RPCSHBJ0 (EE)* ---40 ) RPCHUBJ0 (EE)* ---41 () RPCPFBJ0 (EE)* ---42 RPCSHAJ0 --- ---43 / () RPLMLNJ0 EE, (DEP) ---44 / RPLCLNJ0 EE, (DEP) ---45 () RPLDHIJ0 EE, DEP ---46 () ) RPLDHDJ0 EE, DEP ---47 RPLSTFJ0 EE, (DEP) ---

Health Ins and Pension Ins: Start from 2017 JanFor Santei/Geppen and Shoyo paymentreports, individual numbers from normal

EE shall not be required.

2014 SAP AG or an SAP affiliate company. All rights reserved. 13Customer

2014 SAP AG or an SAP affiliate company.All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG or anSAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG(or an SAP affiliate company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additionaltrademark information and notices.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP AG or an SAP affiliate company for informational purposes only, without representation or warranty of any kind,and SAP AG or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP AG orSAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products andservices, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP AG or its affiliated companies have no obligation to pursue any course of business outlined in this document or any relatedpresentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP AGs or its affiliatedcompanies strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may bechanged by SAP AG or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment,promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertaintiesthat could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-lookingstatements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

2009560 - en_note2009560_roughplan_v1.4

Documents