Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Release <2012-10> SAP HR Slovenia (HR-SI) Reports Customizing Documentation CUSTOMER Document Version: 1.0 – October 22, 2012 Copyright © Copyright 2012 SAP AG. All rights reserved. SAP Library document classification: PUBLIC No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the United States and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries. Oracle and Java are registered trademarks of Oracle and its affiliates. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems Inc. HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc. IOS is a registered trademark of Cisco Systems Inc. RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited. Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc. INTERMEC is a registered trademark of Intermec Technologies Corporation. Wi-Fi is a registered trademark of Wi-Fi Alliance. Bluetooth is a registered trademark of Bluetooth SIG Inc. Motorola is a registered trademark of Motorola Trademark Holdings LLC. Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company. Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. Icons in Body Text Icon Meaning Caution Example Note Recommendation Syntax Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more information, see Help on Help General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library. Typographic Conventions Type Style Description Example text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Cross-references to other documentation. Example text Emphasized words or phrases in body text, graphic titles, and table titles. EXAMPLE TEXT Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE. Example text Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. <Example text> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER. 1. Purpose and scope of this document .............................................................................. 6 2. Customizing for monthly/after payroll reports .................................................................. 7 2.1. iREK-1 2008 – XML and iREK-2 2008 - XML ........................................................... 7 2.1.1. 2.2. 3. 4. Special contracts and REK-2 (from SAP note number 1016576) ................... 7 Obr1-ZAP/M and Form Recourse for yearly vacation ............................................. 10 Customizing for Yearly payroll reports........................................................................... 12 3.1. Income tax (dohodnina) – data mining + changing ................................................. 12 3.2. M4-data mining + changing ................................................................................... 14 3.3. Yearly card ............................................................................................................ 16 Customizing for Master data reports ............................................................................. 17 4.1. M-1, M-3, M-D .................................................................................................... 17 4.2. Leave entitlement .................................................................................................. 24 1. Purpose and scope of this document This document describes customizing that is needed for preparation of some of the reports that are provided by SAP HCM CEE SI localization. Document concentrates on reports that need some specific customizing to be able to get correct results from them. 2. Customizing for monthly/after payroll reports 2.1. iREK-1 2008 – XML and iREK-2 2008 - XML Technical name: HSICRK18 and HSICRK28 Menu path: Human resources Lists/statistics Payroll Europe Slovenia iREK-1 2008 – XML Subsequent Activities Po obra unu Human resources Lists/statistics Payroll Europe iREK-2 2008 - XML Subsequent Activities Po obra unu Slovenia Form name: / Short description: Reports are used to show and send REK-1 and REK-2 report to tax office (DURS). The report includes the calculation of taxes and social insurance made by company for incomes paid to employees. Recipient: Tax administration of the Republic of Slovenia (DURS) Frequency: After every payroll run: Monthly and for every off-cycle Customizing for the report: For this reports the customizing is done on the wage type level in the table T512W. Model wage types (M*) are customized for those reports to reflect allowed combination matrix of REK and dohodnina income types, as listed in technical instructions provided by DURS. Be sure to verify correctness of those combinations in your customizing of wage types. In iREK context, following settings are important for each wage type (table T512W): Evaluation class 09 - income type for REK-1 Evaluation class 04 - income type for REK-2 Evaluation class 06 - income type for dohodnina (former annual report). For an overview of these settings, one can find report HSIU512W very convenient; report is in menu PC62 under Tools branch. 2.1.1.Special contracts and REK-2 (from SAP note number 1016576) Scope Template wage types M71* show which types are supported. There are restrictions to calculation of special contracts. In one payroll run for one personal number only one type of special contract can be calculated (example: M710 and M711 together are not allowed, M710 and M710 together are allowed). Technically speaking - wage types used in the same payroll run for one EE have to have the same cumulation to tax base (/17*). Existing rules for person-specific rates and tax-free are still valid (see LCP SI 26 +33 point N05 for details): /435 - additional percentage of normed costs (increases /43A) /434 - percentage of additional costs (stored into /43B) /433 - person-specific tax rate. It has to be accompanied with information in P0267ZUORD about the reason Additionally (due to reporting reasons in REK-2) gross wage types of special contracts have to be assigned to evaluation class 04, (analogically to REK-1 and evaluation class 09). Please have in mind that assignment off particular wage type to class 04 does not trigger any special calculation (e.g. normed costs ...) - calculation algorithms are dependent on cumulations. The purpose of EVCLS 04 is mainly to group wage types in the report and display the proper type of income in field 010 in the report. It may happen that due to the reporting requirements (displaying the right DURS code) you will have to have several wage types to achieve proper reporting. Example: Original you used one wage type for special contract "Pogodbeno delo" which was automatically reported on different REK reports depending on whether person-specific tax rate is used or not. Now this wage type has to be reported via the same REK-2 report but with code 1501 if the person-specific tax rate is used or 1502 if the person specific tax rate is not used. Solution: you have to have two wage types for this purpose with the same settings in T512w (cumulations, processing classes...) with the only difference - the one which will be used with person specific tax rate has to have EVCLS 04 = 51 (=1501), the second which will be used without person specific tax rate has to have EVCLS 04 = 52 (=1502). Limit of tax During all off-cycle calculations with payday in 2007 and later the calculation program checks if the tax for one EE and one run exceeds minimal tax (20 EUR valid at 1.1.2007). If the minimal tax is not exceeded, the tax is set to zero. The value of minimal tax is stored in payroll constant (T511K) FTSPD. “Boniteta” There are new wage types (M73*) that should be used if “Boniteta” is to be given to the EE together with special contracts. These wage types are related 1:1 to existing M* wage types for special contracts and they have to be used together = if you want to pay “boniteta” related to M710, you have to use M730 for “boniteta”, if you want to pay “boniteta” related to M711, you have to use M731 for “boniteta”, etc. Technically speaking, the wage type for “Boniteta” has to be cumulated to the same tax base (wage types /17*) as the wage type of special contract. The value of M73* wage types only increases tax base but does not influence calculation of normed costs. “Boniteta” without gross income If you run the calculation only with “boniteta” but without gross amount, the calculation program will calculate the tax and the netto will be lower than 0 and debt (/561) will be created and deducted in next payroll runs. There is no automation provided e.g. for gross-up of the “boniteta”. REK-2 report The report HSICRK28 can be run for one off-cycle, you cannot use it for From/To periods. Based in information from UL and tax office groupings of income had to be re-designed. All payroll results are reported summarized together if following data are identical: assignment of primary gross wage type (M7*) to new evaluation class 04 percentage of normed costs in field 106 individual tax rate in fields 203 or 204 To make the REK-2 work you have to assign your customer copies of M7* wage types to values of evaluation class 04 in T512W. All “boniteta” related to special contracts have to be assigned to Class04, value 5A no matter if they are paid alone or together with the special contract. Determination of accounts The existing algorithm remains: it is expected that in T7SIBT, section C, field WGRUP you specify also the primary wage type (M7*). There is no change to existing 2.2. Obr1-ZAP/M and Form Recourse for yearly vacation Technical name: HSICO1ZM_XML and HSICO300_XML Menu path: Human resources Lists/statistics Payroll Europe Slovenia Subsequent Activities Po obra unu PC00_M62_CO1ZM_XML (technical name for the transaction) Human resources Lists/statistics Payroll Europe Slovenia Subsequent Activities Po obra unu PC00_M62_CO300_XML (technical name for the transaction) Form name: / Short description: Each month after payroll, together with bank transfer, companies must report salary data for specific salary categories to AJPES for statistical purposes. Reporting period equals payroll period. Recipient: Statistic office of the Republic of Slovenia (AJPES) Frequency: Monthly Customizing for the report: Table T7SI1P extended Organizational structure and all corresponding data are normally taken from table T7SI1P, where personnel areas and subareas are defined. For reports purposes from year 2008, table T7SI1P was extended for two fields. Please, check that all relevant data is filled in this table, for each company code/personnel area/subarea: tax number T7SI1P-PTXNO activity code T7SI1P-PACTI statistical key T7SI1P-PMATS name and address (T7SI1P-CMPNA, PSTLZ, STRAS, ORT01) code of budget user (T7SI1P-PRORA); only for public sector Region T7SI1P-OBCINA (list of codes available) Subunit status T7SI1P-STATUS (list of codes available) Last two fields are new in table T7SI1P and are used specially for statistical reporting (data used in XML file). User exit to derive statistical key and activity code from alternative organizational structure If you want to define report structure based on different organizational structure than personnel area and personnel subarea (for example based on organizational units), user exit can be activated. Open program ZSICO1ZM_UI for Obr1-ZAP/M HSICO1ZM_XML and program ZSICO300_UI for Regres za letni dopust HSICO300_XML; create form ret7si1p_ue in mentioned program (most likely you'll need user exit only in HSICO1ZM_XML). Create your own logic to build organizational structure and use it to replace values in T7SI1P internal structure. Program will use newly populated data in T7SI1P. Passed arguments: t7si1p: internal table with organizational structure p0001: internal table with EE organizational assignment data pn-endda: end date of period (from selection screen) User exit to derive planned working hours with alternative method If your employees are working in different work schedules with different planned hours per day, parameter Normal working hours on selection screen might not be sufficient to report correct data. In this case you'll need to implement user exit, which should provide planned hours for each individual employee based on company specific rules. You define name of the program and form to derive planned hours in customizing table T596F; save it under symbolic name 62CO1ZH. Program is called during payroll result processing. We suggest creating a logic, which will change monthly planned working hours for processed employee (variable pln_hrs). This will ensure precise calculation. Passed arguments: p_whours: normal working hours (from selection screen) p0001: internal table with EE organizational assignment data pn-endda: end date of period (from selection screen) pln_hrs: number of planned working hours in a month 3. Customizing for Yearly payroll reports 3.1. Income tax (dohodnina) – data mining + changing Technical name: HSICDOH0 Menu path: Human resources Payroll Europe Income tax - preparation obdelave Slovenia Subsequent Activities Letne Form name: / Short description: Data mining tool that summarize all payroll data in selected tax year for your employees. You have also possibility to change existing payroll and master data or even add completely new person who is not your employee for tax purposes. Data are stored and changed in special designed tables T7SIA0, T7SIA1 and T7SIA2 for income tax. Changes have no influence on real master data and payroll data! Recipient: Internal use Frequency: Yearly report Prerequisites: Before you are starting to use income tax – data mining report you have to set some settings that you will get results as you want. In first step you have to check if evaluation class (EC) is created. Use transaction sm31 and enter table name V_T52D3. In table you will found created EC (code 6) for M4. In second step you have to create evaluation class values within EC for income tax. Use same transaction sm31, but different table. Enter V_T52D4. You will find already created evaluation class values (ECV) under codes: 09-62 – valid for dohodnina up to 2004 X0-X1 – valid for dohodnina up to 2004 and after that year A1-N1 – valid for dohodnina from 2005 Evaluation class 06 in T512W table is used to define the „Oznaka vrste dohodka“. The value of evaluation class 06 is „translated“ by the program HSICDOH0 into the 4 digit code required by the law. The relationship between the 2 digit code (used still in T512w) and 4 digit code (used in „dohodnina“) is in table T52DB (maintenance via V_T52D4) where first 4 characters is taken from the text of the value from evaluation class 06. Those values are defined by tax office and they should not be changed. Codes X0 for self-contribution and X1 for additional pension insurance must also stay unchanged. Customer codes are Z0-ZZ. You could use them to define special categories that you want to see on report like ZZZS (health insurance), unions. If you have your own customer values (Z*), the 1st 4 digits in the text will be also displayed on the report for employee. On the contrary to the ECV A1-N1, when defining customer evaluation class values you can use any letters in the 4 digit code (letters, numbers). In last step you have to determine which WT belongs to which evaluation class values. To define this use transaction sm31 and table with name V_512W_D. Chose WT and in section evaluation classes (razredi obdelav) find evaluation class 6. In right part of table enter appropriate evaluation class value. In this way each wage type has its own property in evaluation class 06 (table T512W), which decides whether and how it is included into M-4 reporting. Property is read during data mining (and not during payroll). Assign also the /4A* and /4B* technical wage types (normirani stroški) to ECV which is used for equivalent special contract (avtorski, pogodbeno …) After this customizing is done everything is ready to run report HSICDOH0 to prepare the data for „dohodnina“. For more information see Income tax – data mining + changing in “SID7000_EN Reports.pdf”. 3.2. M4-data mining + changing Technical name: HSICEM40 Menu path: Human resources Payroll obdelave M4 - preparation Europe Slovenia Subsequent Activities Letne Form name: / Short description: Data mining tool summarize all payroll data in selected year for your employees. You have also possibility to change existing payroll and master data or even add completely new person who is not your employee. Data are stored and changed in special designed table T7SIA3 for M4. Changes have no influence on real master data and payroll data! Recipient: Internal use Frequency: Yearly report Prerequisites: Before you are starting to use M4 – data mining report you have to set some settings that you will get results as you want. In first step you have to check if evaluation class (EC) is created. Use transaction sm31 and enter table name V_T52D3. In table you will found created EC (code 7) for M4. In second step you have to check if evaluation class values are filed. Use same transaction sm31, but different table. Enter V_T52D4. You will find already created evaluation class values (ECV) under codes 00-11. Those values are used to decide whether and how amount and hours are included into M-4 reporting and they should not be changed. Code „blank“ is determined for not included items and also must stay unchanged. Possible values for evaluation class 07 are: 07 Not included 07 01 Regular work Money + Hours 07 02 Regular work Money 07 03 Regular work Hours 07 04 Overtime Money + Hours 07 05 Overtime Money 07 06 Overtime Hours 07 07 Illnesses Company 07 08 Illnesses Refunded 07 09 Maternity protection (Maternity leave) 07 10 Benefits 07 11 Waiting for work Note The value 11 corresponds to business case, described in ZPIZ-1 UPB4, paragraph 41, section 2. In last step you have to determine which WT belongs to which evaluation class values. Where to define this? Use transaction sm31 and table with name V_512W_D. Chose WT and in section evaluation classes (razredi obdelav) find EC 7. In right part of table enter appropriate ECV. In this way each wage type has its own property in evaluation class 07 (table T512W), which decides whether and how amount and hours are included into M-4 reporting. Property is read during data mining (and not during payroll). After this customizing is done everything is ready to run report HSICEM40 to prepare the data for „M4“. For more information see M4 – data mining + changing in “SID7000_EN Reports.pdf”. 3.3. Yearly card Technical name: HSICLEK0 Menu path: Human resources Payroll Europe obdelave Annual analytic card Slovenia Subsequent Activities Letne Form name: / Short description: Monthly sorted summarization of money earned by employees. Report is described by following features: evaluation class values, hours, gross pay, social contributions, tax and net pay. At the end of report you have summarization line. Recipient: Internal use Frequency: Yearly/monthly report Prerequisites: Before you are starting to use yearly card report you have to set new evaluation class and its values that you will get results as you want. In first step you have to create new evaluation class for yearly card. Use transaction sm31 and enter table name V_T52D3. SAP recommends using user allowed codes (18, 19, 20), because other codes are reserved for SAP. In second step you have to create evaluation class values within new evaluation class for yearly card. Use same transaction sm31, but different table. Enter V_T52D4. Evaluation class values should represents categories like basic pay, overtime, illnesses, etc. In last step you have to determine which WT belongs to which evaluation class values. Where to define this? Use transaction sm31 and table with name V_512W_D. Chose WT and in section evaluation classes (razredi obdelav) find EC that you created for yearly card. In right part of table enter appropriate ECV. Now is everything ready to run report HSICLEK0. For more information see Yearly card in “SID7000_EN Reports.pdf”. 4. Customizing for Master data reports 4.1. M-1, M-3, M-D Technical name: HSILM100 Menu path: Human resources Payroll Poro ila Izpis M obrazcev Europe Slovenia Environment Master data Form name: / Short description: Report used for printing the M1, M3 and MD forms. Recipient: Health insurance institution (ZZZS) Frequency: When employee data changes Prerequisites: You have to customize and maintain all necessary master data in Personnel Administration before you can use the report HSIILM100. For more information about usage for report HSILM100 see M-1, M-3, M-D in “SID7000_EN Reports.pdf”. On the following pages there are two lists of fields that are used in this reporting. For each field there is additional information for customizing if it is needed. Note Form of M reports changed significally in 2011. Program for new reporting is in preparation. M1 Field name MS Word Data source Technical Field Data source Comment M_0 PERNR personal number 1 Vrsta prijave M_1 X - parameter "Datum spremembe RŠZ" is empty 1 M_2 X - parameter "Datum spremembe RŠZ" is entered 2 Ime in sedež - name M_3 P0001-BUKRS -> company name Data taken from table T7SI1P It takes T7SI1P->CMPNA if not empty according based on infotype 1 data of the to BUKRS+WERKS+BTRTL (T7SI1P) employee 2 M_4 T7SI1P-STRAS+ORT02 - ''- 2 M_5 T7SI1P-PSTLZ+ORT01 - ''- 3 Mati na številka M_6 T7SI1P-PMATS - ''- 4 Reg.št. M_7 T7SI1P-PSTAT - ''- 5 Šifra dejavnosti M_8/ M_45 T7SI1P-PACTI / T7SI1P-PACTI+2(3) - ''- 6 Reg.št.potrebe M_9 P0016-CTNUM – digits before ‚/‘ IT 16 - „Št.prij.PD/Podlaga M“ – characters before slash sign. 7 EMŠO M_10 P0002-PERID IT 2 – „EMŠO“ 8 Državljanstvo M_11 P0002-NATIO -> T7SI05-LANDA IT 2 – „Državljanstvo“ 9 Priimek M_12 P0002-NACHN IT 2 - „Priimek“ 10 Ime M_13 P0002-VORNA IT 2 – „Ime“ 11 Stalno: Ulica M_14 P0006-STRAS+HSNMR+POSTA (SUBTY=1) IT 6, subtype „Permanent stay“ fields „Ulica/hišna št.“ 12 Stalno: Kraj M_15/ M_46 P0006-PSTLZ / T7SI51-XNP IT 6 – field „Pošt.št/mesto“ -> text 13 Stalno: Ob ina M_16 M_47 IT 6 – field „Regija“ -> text 14 Stalno: Država M_17 P0006-LAND1 -> T7SI05-LANDA IT 6 – field „Klju države“ 15 Za as: Ulica M_18 P0006-STRAS+HSNMR+POSTA (SUBTY=2) IT 6, subtype „Temporary stay“ 16 Za as: Kraj M_19 M_48 / P0006-PSTLZ / T7SI51-XNP IT 6 – field „Pošt.št/mesto“ -> text 17 Za as: Ob ina M_20 M_49 / P0006-STATE / T005U-BEZEI IT 6 – field „Regija“ -> text 18 Za as: Država M_21 P0006-LAND1 -> T7SI05-LANDA IT 6 – field „Klju države“ M_22 P0006-ENDDA, SUBTY=2 IT 6 – end date of the subtype „temporary stay“ 20 Podlaga zav. M_23 If there is EE specific „podlaga“ it has to be entered to the field P0016-CTNUM – digits after ‚/‘ or parameter „Št.prij.PD/Podlaga M“ after the Podlaga zavarovanja slash. If not the parameter from selection screen is used. 21 Datum pri etka M_24 key date = hire date 19 Iztek za .pr. veljavnosti / P0006-STATE / T005U-BEZEI - Vzrok prenehanja not supported - Datum prenehanja not supported 24 Del/zav. as M_25 P0007-WOSTD 25 Del.razmerje M_26 IT 1 “Del.razm.” can be used to identify the Delovno razmerje. If you use the field already for company-speficif purposes you have to use infotype 16 (see below). The value of ANSVH is P0001-ANSVH or P0016-CTTYP -> T7SI42Aconverted via table T7SI42A into DERAZ value of Delovno razmerje. IT 16 “Vrsta pogodbe” can be used to identify the Delovno razmerje. The value is converted via table T7SI42A into value of Delovno razmerje. 26 Št.del.dov. M_27 P0185-ICNUM, subtype DD IT185 „ID number“ – subtype specified on selection screen 27 Dat.izteka dd M_28 P0185-EXPID, subtype DD IT 185 „Valid to“ – subtype specified on selection screen 28 Izmensko delo M_29 P0007-SCHKZ-> T508A-KKRKH IT 7 – „Ted. Delovne ure“ Field in customizing related to work schedule of EE in infotype 7. Code table is: 1-Ena izmena, 2-Dve izmeni, 3-Tri izmene, 4-Ve izmen, 5-Delo v turnusu. 29 Šolska izobr. M_30 P0607-FACCD IT 607 – „Tip šole“ 30 Naz.poklic.izobr. M_31 P0607-AUSBI+3(5) IT 607 – „Izobrazba“ from 4th character 31 Stopnja š.izobr M_32 P0607-STSIZ IT 607 – „Stopnja šol.izobr“ 32 St.strok.usp. M_33 If the required educational level is not specified in infotype 607 program reads required ed.level P0607-SLABS or (if empty)->PD->T7SI0W- from PD qualification profile SLABS=conversion table releated to the POSITION of the EE. The achieved proficency is translated to SI values in table T7SI0W 33 St.strok.izobr. M_34 P0607-SLART ->(if empty)-> T7SI0V-ABART(1) IT 607 – „Dej. st. Izobrazbe“ translated via table T7SI0V 34 Naz.del.mesta M_35 P0001-STELL -> T513S-STLTX If PD is integrated – text from PD JOB. If not, text from T513S M_36/ M_37 P1002-TLINE - lines 1 / 2 Read from PD infotype 1002 related to either POSITION (1st priority) or JOB. The subtype of IT1002 that is used in the company has to be specified in T7SI1PM1OPI 34 Poklic ki ga opr. M_38 P0607-DPTMT(7)->(if empty)->P1051-JCODE If the job description is not specified in infotype 607 program reads PD infotype 1051 related to the JOB of the EE. The subtype of IT1051 that is used in the company has to be specified in T7SI1PM1JOB. 35 Poslan v državo M_39 P0603-REZID -> T7SI05-LANDA IT 603 – „V državo“ – translated via T7SI05 36 Prostovolno not supported 34 Opis dela 37 Vrsta invalidnosti M_52 P0604-ITYPE (Vrsta invalidnosti M) x Kraj M_42 parameter "Kraj" (p_kraj) x Dne M_43 parameter "Dne" (p_dne) x Vložnik M_44 parameter "Vložnik" (p_vlznik) Vrsta invalidnosti M - New field introduced in LCP 28 M-D Field name Ime in sedež 1 1 1 MS Word Field Data source Technical Data source Comment M_0 PERNR Personal number M_1 P0001-BUKRS -> company name It takes T7SI1P->CMPNA if not empty according to BUKRS+WERKS+BTRTL (RET7SI1P) Data taken from table T7SI1P based on infotype 1 data of the employee M_2 T7SI1P-STRAS+ORT02 - ''- M_3 T7SI1P-PSTLZ+ORT01 - ''- ''- 2 Reg.št. M_4 T7SI1P-PSTAT 3 Datum pri etka M_5 key date = hire date 4 Podlaga zav. M_6 P0016-CTNUM – digits after ‚/‘ or parameter Podlaga zavarovanja If there is EE specific „podlaga“ it has to be entered to the field „Št.prij.PD/Podlaga M“ after the slash. If not the parameter from selection screen is used. 5 EMŠO M_7 P0002-PERID IT 2 – „EMŠO“ 6 Priimek in ime M_8 P0002-NACHN SNAME) Family member Even/Odd 7 EMŠO M_9/27 P0021-PERID IT 6 – „EMŠO“ 8 Državljanstvo M_11/46 P0021-FANAT -> T7SI05-LANDA IT 21 „Državljanstvo“ 9 Priimek in ime M_12/28 P0021-FANAM + P0021-FAVOR IT 21 „Priimek“ and „Ime“ 10 Vrsta dogodka M_13/29 1 hard coded for HIRE 11 Datum dogodka M_14/30 key date Begda from IT21 for the family member 12 Podlaga zav. M_15/31 P0021-KDSVH (obvezno zdrav.zavarovanje) IT 21 „Obvez. zdrav. Zavarovanje“ – check table V_T577 13 Sorodstvo M_16/32 P0021-KDUTB IT 21 „Sorodstvo“ 14 Stalno: Ulica M_17/33 P0006-STRAS+HSNMR+POSTA (via P0021-SI_ADRP)I IT21 „Naslov stalni“ -> Infotype 6 15 Stalno: Kraj M_18+47 /34+51 P0006-PSTLZ / T7SI51-XNP Like in M1 16 Stalno: Ob ina M_19+48 /35+52 P0006-STATE / T005U-BEZEI Like in M1 17 Stalno: Država M_20/36 P0006-LAND1 -> T7SI05-LANDA Like in M1 18 Za as: Ulica M_21/37 P0006-STRAS+HSNMR+POSTA (via P0021-SI_ADRT)IT21 „Naslov za asni“ -> infotype 6 19 Za as: Kraj M_22+49 /38+53 P0006-PSTLZ / T7SI51-XNP Like in M1 20 Za as: Ob ina M_23+50 /39+54 P0006-STATE / T005U-BEZEI Like in M1 21 Za as: Država M_24/40 P0006-LAND1 -> T7SI05-LANDA Like in M1 22 Iztek veljavnosti za asnega prebivališ a M_25/41 P0006-ENDDA, SUBTY= acc to P0021-SI_ADRT IT 21 „Naslov za asni“ -> infotype 6 – End date of the record + P0002-VORNA (or P0001- IT 2 – „Priimek“ and „Ime“ Potrdilo o šolanju do M_26/42 P0021-FASDT x Kraj M_43 parameter "Kraj" (p_kraj) x Dne M_44 parameter "Dne" (p_dne) x Vložnik M_45 parameter "Vložnik" (p_vlznik) 23 IT21 – „Kon.izobr.“ Additional customizing To be able to do print of the M3 and MD changes, it is necessary to activate logging of changes in the relevant infotypes. Because the SAP standard logging is more extensive than is needed for purpose of the reports, there is special program for capturing the infotype changes HSILLOG0. It contains code that saves changes of: Exactly specified fields of specified infotypes or All fields in specified infotypes into table T7SIA7 from where the changes are printed out. The program should be called from „dynamic event“ – in table T588Z. The simplest is to activate it for the whole infotypes – example of the settings in table T588Z: INFTY SUBTY FNAME OPERA SEQNO KENNZ VINFO ---------------------------------------------------------------------------0001 06 301 F LOGIT(HSILLOG0) 0002 06 301 F LOGIT(HSILLOG0) 0006 06 301 F LOGIT(HSILLOG0) 0007 06 301 F LOGIT(HSILLOG0) 0016 06 301 F LOGIT(HSILLOG0) 0021 06 301 F LOGIT(HSILLOG0) 0185 06 301 F LOGIT(HSILLOG0) 0603 06 301 F LOGIT(HSILLOG0) 0607 06 301 F LOGIT(HSILLOG0) ---------------------------------------------------------------------------- This general approach may slow down the response of your system – if it happens it is necessary to assign the call of the program only to required fields. Customer exit in M1 and MD forms You can use new customer exit (Enhancement ID = HRSIM100, component EXIT_HSILM100_001) that gives you possibility to change content of any field of the M forms. The exit is called after all data from SAP system are retrieved and before the call of MS Word is performed. For more information see User exit to change T7SI1P organizational data in reports in “SIC1000_EN Payroll in SAP System.pdf”. 4.2. Leave entitlement Technical name: RPTQTA00 Menu path: Human resources Payroll Europe Slovenia Environment Generiranje kontingentov odsotnosti (PT_QTA00) Time data Poro ila Form name: / Short description: Report used for calculation of absence quotas for annual leave. Recipient: Internal use Frequency: Yearly report Prerequisites: Before starting using calculation of leave please check following standard algorithms, which are part of localization. Those are customizing that have to be customized in addition to standard customizing for absence/attendance quota accrual using report RPTQTA00, that you can set in standard IMG. Table T7SIL1 contains following standard algorithms: A Working age (Delovna doba) B Achieved level of education (Dejanska st. izobrazbe) C Required educational level (Planirana st. izobrazbe) D Night shift (No no delo) E Type of disability (Invalidnost – kategorija) F Body injury percentage (Invalidnost – odstotek) G Age of a child for mothers (Otroci – Mati) H Age of a child for fathers (Otroci – O e) I Infotype 0014 (IT 14) J Age of employee (Starost zaposlenega) K Age and Gender of employee (Starost zaposlenega M/Ž) Z Summary and Limit from T7SIL3 (C) SAP AG 24 Algorithm A – Working age (Delovna doba) Enter the number (1-6) of Enter theworking numberage (1-6)inofthe field selected selected field choose which „Variable key“to (T7SIL2–VARKY) field you will use field as base to choose which you for will use calculation working age. as base for of calculation of working age. In the field T7SIL2-VARKY there should be the selected working age type (1 to 6). The algorithm A will calculate number of years and then it will find the number of days from T7SIL3. Algorithm B – Achieved level of education (Dejanska st. Izobrazbe) The algorithm B will get achieved level of education from IT 0607 field SLART and then it will find the number of days from T7SIL3. Algorithm C – Required educational level (Dejanska st. Izobrazbe) The algorithm C will get required educational level from IT 0607 field SLABS and then it will find the number of days from T7SIL3. Algorithm D – Night shift (No no delo) There are two options to get the number of night hours: If you leave field T7SIl2-VARKY empty the algorithm D will check employees Work schedule from previous year and try to find the number of hours from night shift (10 pm-6 am). The second option is to enter evaluation class (first two charactes) and value for evaluation class (characters from 3 to 4) into the field T7SIl2-VARKY. Notice: for this option you have to customize special EC for night shift and assign special WT that represents night shift. The algorithm D will go to previous year’s payroll result and try to find the number of hours from wage types with customized EC value (night hours). Regardless of the option that was used the algorithm D will use the night hours from the first step to find the number of days from T7SIL3. Algorithm E – Type of disability (Invalidnost – kategorija) The algorithm E will get type of disability from IT 0604 field NTYPE and then it will find the number of days from T7SIL3. Algorithm F – Body injury percentage (Invalidnost – odstotek) The algorithm F will get body injury percentage from IT 0604 field NBINJ and then it will find the number of days from T7SIL3. Algorithm G – Age of a child for mothers (Otroci – Mati) The algorithm G will calculate age of a child from IT 0021 only for mothers and then it will find the number of days from T7SIL3. Algorithm H – Age of a child for fathers (Otroci – O e) The algorithm G will calculate age of a child from IT 0021 only for fathers and then it will find the number of days from T7SIL3. (C) SAP AG 25 Algorithm I – Infotype 0014 (IT 14) In the field T7SIL2-VARKY there should be the wage type to be used in IT 0014. The algorithm I will read infotype 0014 with the BEGDA and ENDDA of the year of the new leave entitlement (current year). The value entered in field NUMBER in the record of infotype 0014 is taken directly as proposed leave entitlement quota. The record in table T7SIL3 is not needed for this algorithm. Algorithm J – Age of employee (Starost zaposlenega) The algorithm J will calculate age of employee and then it will find the number of days from T7SIL3. Algorithm K – Age and Gender of employee (Starost zaposlenega M/Ž) The algorithm K will calculate age of employee at the 1st day of the period (quota for year 2012 = age for 1.1.2012) in format "YYMM" and this string is used to search in table T7SIL3 together with the gender of the employee. Algorithm Z – Summary and Limit (Skupaj) The algorithm Z will summarize all previously calculated quotas and apply the limit for quota with algorithm Z. The customizing is as follows: Customer must setup a new quota with HIGHER ID than quotas that should be summarized New algorithm "Z" - Skupaj was defined in T7SIL1 Table T7SIL2 was extended by new field QTOTL which indicates which quotas are to be used for summarizations. During proposal calculation the algorithm "Z" sums up all proposed values of quotas specified in T7SIL2. This sum is a key using which a record in T7SIL3 is searched. If not found, the total remains unchanged (= no upper limit defined) If such line was found and total is higher than value in T7SIL3 then the total is cut on this value. If lower, the total remains unchanged. To implement customer specific upper limit of quota it is possible to use subsequent customer exit (009) of the standard calculation. User definable algorithms (user exit) There are 12 values for user definable algorithms N, O, P, Q, R, S, T, U, V, W, X and Y. These algorithms are defined for customer needs in domain PSI_QTALG. In this way customer can prepare own rules for quota generation. Function module HR_CHANGE_QUOTAS_GEN_62 was also prepared to be able use this user exit in order to process customer values. (C) SAP AG 26 Table/View T7SIL1 – Algorithms for leave entitlement The fields used are as follows: T7SIL1–QTALG Quota algorithm T7SIL1–TEXT30 Name of the algorithm Table/View T7SIL2 – Quotas and algorithms – You have to set all quota types in this table. (C) SAP AG 27 The fields used are as follows: T7SIL2–GRVA1 Employee subgroup grouping for leave entitlement calculation from table V_T7SI03 T7SIL2–GRVA2 Personal subareas grouping for leave entitlement calculation from table V_T7SI01P T7SIL2–QTTYP Absence Quota Type T7SIL2–SEQNR Two digit number T7SIL2–BEGDA Start Date T7SIL2–ENDDA End Date T7SIL2–QTALG Quota algorithm T7SIL2–VARKY Variable key T7SIL2–QTOTL Summarization of quotas (C) SAP AG 28 Table/View T7SIL3 – Ranges for algorithms - Table has purpose to define ranges for different algorithms with days of leave for each range. The fields used are as follows: T7SIL3–GRVA1 Employee subgroup grouping for leave entitlement calculation from table V_T7SI03 T7SIL3–GRVA2 Personal subareas grouping for leave entitlement calculation from table V_T7SI01P T7SIL3–QTALG Quota algorithm T7SIL3–QTFIX Output options T7SIL3–GENDE Gender key T7SIL3–SEQNR Sequence number T7SIL3–BEGDA Start Date T7SIL3–ENDDA End Date T7SIL3–QTLOW From T7SIL3–QTHIG To T7SIL3–QTRES Number of the days for quota (C) SAP AG 29