Page tree
Skip to end of metadata
Go to start of metadata


Index

KBA and Notes

  • KBA
  • KBA
  • KBA
  • KBA
  • KBA
  • KBA


IMPORTANT!

Solution described in following article is delivered in SAP_HR 6.08 SP73

To implement the solution, apply the HR Support Package.  In this case all the IMG steps, documentation and other objects are created in the system.


**Note 2822081 - Sickness payments in off cycle payroll runs


Sickness certificate payment business process and technical process

Sickness certificate payment process is divided for Credit Scheme and Direct Payments Scheme

Credit Scheme

Business process

1)      Submitting Sickness Certificate

2)      Sickness certificate Allowance calculation

3)      Sickness Certificate payment

4)      NDFL transfer

Technical Process

1)      Submitting Sickness Certificate – Infotype 0000 Action  UU FSS Application for SI Payment

Action infogroup includes

  • infotype 3330
  • infotype 2001
  • infotype 3273  with subtype Sick Pay via Credit Scheme (RUCS)


2)       Sickness certificate Allowance calculation Reason 0108 Off-cycle payroll will calculate sickness payments for sickness certificates for employees on the FSS credit scheme.

Infotype 3273 allows to record  sickness certificate submit date.

3)      Sickness Certificate payment Payroll run  using reason  0100, 0101, 0102

Monthly Advance off-cycle payroll runs will provide the sums of sickness certificate payments, calculated in earlier FSS Application off-cycle, and corresponding income tax for bank transfer.

4)      NDFL transfer – 0100, 0101, 0102 payroll result for allowance transfer and regular payroll for salary taxation

Off-cycle payroll runs will calculate the taxes and garnishment deductions considering previous off-cycle payroll runs of the same payroll period.



Sickness certificate payment business process for Direct Payments Scheme

Business process and technical process for direct payments scheme includes separation of process to pay first three days of sickness and overall absence and payment calculation.

1)      Submitting Sickness Certificate

2)      Sickness certificate Allowance calculation

3)      A. Sickness Certificate payment (3 days payed be employer) - Reason 0108 Off-cycle payroll

B. Forming XML Register for FSS Application

4)      A. NDFL transfer – 0100, 0101, 0102 payroll result for sickness payment transfer and regular payroll for salary taxation

B. FSS payment

Functionality Delivered in Note 2822081 Sickness payments in off cycle payroll runs

Back to the start 


Sickness Certificate payment status

Functionality works with option AP4LN (GENERATE APPLICATION FOR LN)  in table T5F99K2 

  IMG >Payroll Russia > Business Processes >  Social Insurance > Generate Application for Sickness Compensation

When the switch is activated, all sickness certificate records of the Absences (2001) infotype should be assigned to the Sickness Certificate (3330) infotype. Also the application for social insurance payments (Statement:Rules for SI Payments-RU (3273) infotype) should exist with the Sickness Certificate (3330) infotype assigned to the application.

This is valid for the FSS Direct Payment Scheme and the FSS Credit Scheme.

When off-cycle payments are activated, sicknesses must have a corresponding FSS application record in the Statement:Rules for SI Payments-RU (3273) infotype - see Customizing activity Assign Application Types to IT3273 Subtypes.

Subtype Sick Pay via Credit Scheme (RUCS) of infotype Statement: Rules for SI Payments-RU (3273) is used to store the calculation status for an absence related to any sickness certificate of employees on the FSS credit scheme. For any sickness certificate, calculation of the payment in Payroll Driver (Russia) will require an entry of infotype Statement: Rules for SI Payments-RU (3273).

Personnel action FSS Application for SI Payment can be used for both FSS payment schemes. This personnel action can be used to enter a Sickness Certificate (infotype 3330) along with Absences (infotype 2001) and Statement: Rules for SI Payments-RU (infotype 3273).

Required system settings:

  1. Subtype Sick Pay via Credit Scheme (RUCS) of infotype Statement: Rules for SI Payments-RU (3273)
  2. UU FSS infogroup to include infotypes 3330, 2001, 3273
  3. Assignment of application types to IT 3273 subtypes
  4. Assigning IT 3273 Subtypes to Disability Causes
  5. Dynamic events
  6. Absence Valuation Rule
  7. Group wage types

See details on required configuration of infotype Statement: Rules for SI Payments-RU (3273) in the file "Customizing_Description_for_SAP_Note_2822081.pdf" attached to the SAP Note 2822081

Back to the start 


A specific organization can be assigned to either FSS direct payments or FSS credit scheme.

The assignment can be done using infotype Legal Properties (Russia) (1655) (for Concurrent Employment solution) or customizing activity Enter Data About Organization (without Concurrent Employment solution).

How to set Sickness Certificate and Application assignment:

Single Employment organization settings recomendations

Transaction SPRO > Payroll: Russia > Reporting > General Tool > Enter Data About Organization

or transaction SM30 > V_T7RU9A Enter Data About Organization

Organization type 05 - Social Insurance Fund can be used

Concurrent Employment organization settings recomendations

Transaction pp01 > Choose your OR - Legal Entity object > Infotype 1655 > Social Insurance Tab > Payment Scheme to FSS

Field FSSSC specifies if the organization or its part uses the FSS Direct Payment or the FSS Credit Scheme.

Note that infotype 1655 can be hidden. Go to settings > Country-Specific Infotypes > All country-specific infotypes OR for RU country


Important:

As described in SAP Note 2841238 - Output Data Processing in Sickness Certificates Management all reporting areas of report type Sickness Certificates Processing (LN) must be configured as relevant for RMS processing.
These settings can be made in the view cluster Report Management System Organization Data (VC_T77PAYRU_RMS_O). The field not in RMS (NORMS) must be cleared.

Back to the start 


Off-Cycle calculation for sickness certificates

Functionality works with option FSSCS (OFF-CYCLE FOR SICKNESS CERTIFICATES)  in table T5F99K2

IMG STEP payroll Russia > Business Processes > Social Insurance > Sickness Compensation Payments in Off-Cycle > Activate Off-Cycle Payments for Sickness Certificates


System supports the calculation of FSS Applications in off-cycle for compensation payments for sickness certificates when the employer uses the Credit Scheme for mutual settlement with FSS (FSSCS).

Off-cycle payroll runs will calculate the taxes and garnishment deductions considering previous off-cycle payroll runs of the same payroll period.

Monthly Advance off-cycle payroll runs will provide the sums of sickness certificate payments, calculated in earlier FSS Application off-cycle, and corresponding income tax for bank transfer.

This activates the following:

  • Payroll
    • Calculation of social insurance payments for applications to the FSS in off-cycle with reason 0108 Calculation for FSS Application
    • Payment of earlier calculated FSS applications via off-cycle with reasons 0100, 0101 and 0102 (see Customizing activity Set Up Off-Cycle Reasons).
    • Calculation of income tax separately for every income, taking into account income tax calculated and deducted in previous off-cycle runs.

    • Calculation of garnishments taking into account balance for garnishments in previous off-cycle runs.
    • Maximum Recurring Payments/Deductions amount is displayed in payroll with “/GTO - OC GarnTotal per period” wage type

Note: Off-cycle 0109 Maternity Leave Payment is deactivated when you activate the functions in this Customizing activity.

Note: You should activate option FSSCS from the beginning of the month which does not contain results calculated when option FSSCS was not activated.



Required system settings:

1)       Specific Wage types

2)       Wage type Grouping


Payroll function Process Infotype 3273 - Russia (P3273) processes the required data. It must be called in the used payroll calculation scheme in accordance with the standard approach. In the standard payroll calculation scheme it is called near the end of calculation of the payments valuated by averages.

See details on required configuration of infotype Statement: Rules for SI Payments-RU (3273) in the file "Customizing_Description_for_SAP_Note_2822081.pdf" attached to the SAP Note 2822081

See also information on changes in standard payroll objects related to sickness certificates payroll calculation in the file "PY_objects_SAP_Note_2822081.pdf" attached to the SAP Note 2822081. Probably, some customer-specific processing used in your payroll calculation solution should also be changed correspondingly.


Back to the start 


Payment with Zero Advance

  • Wage Type MO0C - Zero Adv. - OC Sick Pay.
  • Zero Valuation Basis
  • Ability to create InfoType record 0267 - Additional Off-cycle payments
  • Advance off-cycle payment will only process sickness certificates, that were calculated earlier

Back to the start 



Infotypes dates approach in standard delivery

  • IT 3330 - date of issue (when the sickness certificate was created) LN_DATE in xml file.
  • IT 2001 - dates taken from periods of treatments (TREAT_DT1 ...) , or period in hospital (HOSPITAL_DT1 ...)*
  • IT3273 - date from when Employer has been notified by employee ( he/she has provided ELN number of sickness certificate) and to date when received
    the ELN and registered in the system.



  • In delivered functionality IT3273 date cannot be earlier than IT3330 date.
  • Some cases happen when date of issue ( IT3330 date) can be later than sickness start date, for example:
    employee was placed in hospital 07/06/2020, but later, on 14/06/2020 his/her doctor has created ELN with LN_DATE = 2020-06-14).
    It can look as below:




<ns1:PRIMARY_FLAG>1</ns1:PRIMARY_FLAG>
<ns1:LN_DATE>2020-08-14</ns1:LN_DATE>
...

<ns1:REASON1>01</ns1:REASON1>

<ns1:HOSPITAL_DT1>2020-08-07</ns1:HOSPITAL_DT1>

<ns1:HOSPITAL_DT2>2020-08-14</ns1:HOSPITAL_DT2>..

...

<ns1:TREAT_FULL_PERIOD>

<ns1:TREAT_PERIOD>

<ns1:TREAT_DT1>2020-06-07</ns1:TREAT_DT1>

<ns1:TREAT_DT2>2020-06-14</ns1:TREAT_DT2>

</ns1:TREAT_PERIOD>

</ns1:TREAT_FULL_PERIOD>

....

<ns1:DT1_LN>2020-06-07</ns1:DT1_LN>

<ns1:DT2_LN>2020-06-21</ns1:DT2_LN>


  • Some cases include same start date in IT0000, IT3330 and IT3273.
    For example it may be possible for LN with reason = 05 ( maternity leave) , for example:

05 Maternity Leave


<ns1:PRIMARY_FLAG>1</ns1:PRIMARY_FLAG>

<ns1:REASON1>05</ns1:REASON1>

<ns1:LN_DATE>2020-06-10</ns1:LN_DATE>

...

<ns1:TREAT_PERIODS>
<ns1:TREAT_DT1>2020-06-11</ns1:TREAT_DT1>
<ns1:TREAT_DT2>2020-06-12</ns1:TREAT_DT2>
...

<ns1:TREAT_DT1>2020-06-13</ns1:TREAT_DT1>
<ns1:TREAT_DT2>2020-06-13</ns1:TREAT_DT2>

...

<ns1:TREAT_DT1>2020-06-14</ns1:TREAT_DT1>
<ns1:TREAT_DT2>2020-06-14</ns1:TREAT_DT2>
</ns1:TREAT_PERIODS>

<ns1:RETURN_DATE_LPU>2020-06-15</ns1:RETURN_DATE_LPU>



  • By default the IT 3273 depends on date of execution of the UU action in the delivered functionality. Action UU is used to link together 3330, 2001, 3273 .
    Sometimes it is possible not to use the UU action, for example when you create entry in 3330 using Load Sickness Certificate button and so on.



Detailed description in IMG step in Payroll: Russia-> Business Processes-> Social Insurance -> FSS Direct Payments ->


FSS Application Processing -> Define Absences Suggestions based on Data from Sickness Certificate



"...
In standard delivery, four types of events corresponding to the data of the Sickness Certificate (3330) infotype are available:
1. Regime breach – Field Regime Breach Date (HSBRD) is filled.


2. Stationary treatment – Fields From (HSDT1) and To (HSDT2) in section Stay in the Hospital are filled.


3. Spa treatment – Fields Date1 (DATE1), Date2 (DATE2) and Ref.Doc.No. (VONUM) are filled.


4. Ambulatory treatment – Covers the whole period of the sickness certificate. Intended to have lower priority than the types above


to cover the part not filled by those types.
..."



Back to the start 


How to report an incident on this topic

  • Customer Interaction Center: Hotline numbers & E-mail addresses # 560499

  • Support Center: Phone & Fax numbers # 38373

  • Priorities of problem incidents # 67739

  • Structure of components for customer incidents # 36677

  • Customer incident – customer logon data # 508140

  • 24-hour support not possible in this language # 32736

  • What is consulting? What is support? # 83020

  • Processing of customer incidents in English # 873046

  • LOP - Line Opener Program # 797124

  • Several queries in an incident # 50048

  • SAP Message Escalation Procedure # 90835

  • How to speed up customer incident processing # 1281633 # 984434

  • How to efficiently report a problem # 1228776

Back to the start  

   

  • No labels