SAP ABAP IMG Activity PAY_ES_DT_PROD (Steps to follow for production start up)

Hierarchy

☛ SAP_HRCES (Software Component) Sub component SAP_HRCES of SAP_HR
   ⤷ PY-ES (Application Component) Spain
     ⤷ P04C (Package) HR Customizing: Spain

IMG Activity

ID	PAY_ES_DT_PROD	Steps to follow for production start up
Transaction Code	S_PH0_48000555	(empty)
Created on	20000207
Customizing Attributes	PAY_ES_DT_PROD	Steps to follow for production start up
Customizing Activity	PAY_ES_DT_PROD	Steps to follow for production start up

Document

Document Class	SIMG	Hypertext: Object Class - Class to which a document belongs.
Document Name	PAY_ES_DT_PROD

This IMG activity describes the steps to follow for transfering payroll results from an old system before production startup.

Activities

Wage types

In the following steps you must fill in table T558A with the wage types listed below and afterwards run the payroll program using schema ELK0 'Transfer payroll results from T558A', so that the wage types in table T558A become payroll results:

1. Load the total number of overtime hours worked during the calendar year previous to the startup for all personnel, month by month, for their repercussions on temporary incapacity (TI). SAP automatically calculates the yearly overtime average.
1. Depending on the setting chosen in function ESV00, you must fill in the following wage types:

• - Parameter 3 = 1
  /340: with the amount field = ATEP basis - ATEP basis without overtime
• - Parameter 3 = 2
  /103: with the amount field : Unstructured overtime - rest
  /104: with the amount field: Structured overtime - force majeure

1. Depending on the constant SPHEX:

• - Value = 0
  /3AC: with the number field: Active days acc. to Social Ins. (Contr.)
  /3BC: with the number field: Leave days acc. to Social Ins. (Contr.)
• - Value = 1
  /3AC: with the number field: Active days acc.to Social Ins. (Contr.)
• - Value = 2
  Nothing

  You store this average in wage type /346.

1. To calculate the regulatory basis for those persons who become temporarily incapacitated (TI) during the start up, you must load the following wage types:
• /3CA: with the number field = Social Ins. contribution days (30 days)
• /3AC: with the number field = Social Ins. registration days (30 days)
• /3CH: with the number field = Unpaid absence days do not contr. - SI
• /344: Regulatory basis Contribution Account (CA) amount = value day
• /343: Contribution basis Premium type (PT) amount = value month
• /340: with the amount field = ATEP basis - ATEP basis without hours
• /346: Overtime daily basis PT amount = value day
• /102: Planned contribution basis CA
• /3Z0: CA basis TI period
• /341: Pro rata
• /105: Planned contribution basis PT
• /103: Unstructured overtime - rest
• /104: Structured overtime - force majeure
• /3Z1: PT basis TI period
2. Load the same wage types from the month previous to the absence for TI for those personnel numbers in a state of TI that began prior to startup day. Take into account that you need a payroll result for the month in which the temporary incapacity started.
3. As well as points 3 and 4, in the case of part-time contracts, you must know the contribution bases for the last three months before TI. The wage types to load are:
• /3CA: with the number field = Social Ins. contrib. days (30 days)
• /342: Contribution basis CA amount = monthly value
• /343: Contribution basis PT amount = value month
• /3CS: Number field = number of hours worked in the period
4. Have table SV in the payroll results for the 12 months previous to production startup.
5. Load the quota for special payments that need it (such as benefit payments) in December, with the program 'Transfer of entitlement to special payment from table T558A' (RPCSPUE0).
• Loading of data in table T558A; that is, for each personnel number, loading of the special payment quotas paid up until December 31st of the year previous to the startup.
• Run program RPCSPUE0, variant U (Update), to maintain the special payment quotas in table SP. This program only runs the update of table SP, without affecting the other results tables. Results from December must therefore exist previously.

Maintenance of master data

1. Bear in mind that at the start of the year some data generally changes. For example, you must take into account the fact that the 'Fiscal data' infotype (0062) shows the tax basis for the current year. List of necessary infotypes:
• 'Copy Measures' (0000)
• 'Organizational Assignment' (0001)
• 'Create Planned Work Time' (0007)
• 'Create Basic Pay' (0008)
• 'Social Insurance Data' (0061)
• 'Fiscal Data' (0062)
• 'Absences' (2001)
2. Maintain the infotype 'Modify Payroll Staus' (0003), leaving empty the retroactive accounting dates for each person.
3. Delete the management record for the payroll area and place it with the values of the current month and year.
4. Activate the line CHECK ABR of the payroll schema you are using (E000/ED00).

All these considerations refer to the event of a production startup at the start of the year. Should the startup take place in a month other than January, you must take into account other additional considerations:

1. The customer must decide whether retroactive accounting calculations will be necessary for periods prior to the production startup date. For example, one reason could be an increase in the agreement valid from January 1st. If the answer is yes, then for these retroactive calculations the system must have available all those wage types that flow to the Gross amount and to the Net, i.e., all the payment items, Social Insurance contributions, employment tax deductions (IRPF), payments and deductions to the Gross and Net amounts, etc., for all periods up until the retroactive accounting date limit (in the example, January 1st).
   Although in theory you can load all these wage types in table T558A and run the payroll program with the schema ELK0, it is recommended that you run the payroll program with the normal schema for the months up to the retroactive accounting limit, parallel to the old system. If you want, you can correct the possible calculation differences between the two systems through auxiliary wage types. For example, in the 'Create Additional Payments' infotype (0015).
   You must bear in mind that in this case that you apply the information in points 2 to 7 substituting the word 'startup' for 'retroactive accounting limit'.
2. You must decide how to create tax report 190, as well as reports 110 and 111 if it is necessary for you to submit them. The possibilities are, on one hand, to create the reports using a program that obtains the data from SAP and from the previous product; on the other hand, you can use the standard SAP programs for these reports, but to do so, you must load the payroll results previous to SAP that affect these programs. There is the possibility of creating the tax reports from the financial environment, providing the HR module with the necessary data through an interface file. Otherwise, see point 11.
3. DEFERRED PERIOD:
   Owing to the complexity of startup of items in the DEFERRED PERIOD, it is necessary in these cases to make parallel calculations for at least three months.

Business Attributes

ASAP Roadmap ID	152	Design data acquisition
Mandatory / Optional	1	Mandatory activity
Critical / Non-Critical	1	Critical
Country-Dependency	I	Valid for countries specified

Customizing Attributes	Country Key	Country Name
PAY_ES_DT_PROD	ES	Spain

Assigned Application Components

Documentation Object Class	Documentation Object Name	Current line number	Application Component	Application Component Name
SIMG	PAY_ES_DT_PROD	0	HLA0008530	Gross

Maintenance Objects

Maintenance object type

C

Customizing Object

Assigned objects
Customizing Object	Object Type	Transaction Code	Sub-object	Do not Summarize	Skip Subset Dialog Box	Description for multiple selections
V_T558A	V - View	SM30		☐	☐

History

Last changed by/on	SAP	20000509
SAP Release Created in	46C