SAP HR Infotypes : Infotype 0302 (Additional Actions)

Hi,

Please find few points about Infotype 0302(Additional Actions)

- The Actions Infotype (0000), only one personnel action type is saved per day because of the time   constraint 1(no gaps and no overlaps). In this Infotype, we only store the personnel action types that change the status of the employee.

- Infotype 0302 is not maintained directly and is automatically updated by Infotype 0000.

- The additional actions Infotype (0302) is of time constraint 3 (gaps and overlaps).

- Specifically in some cases if we want to have a non status-changing Action on the same day where already a personnel action is existing at that time we can activate the Infotype 302 by executing Report RPUEVSUP.

- By using the semantic identification code EVSUP, we can determine Whether we want to use the Additional Events Infotype (0302).

We can use the following values:
' ':  The Additional Events Infotype (0302) is Deactivated (standard setting).
'1': The Additional Events Infotype (0302) is activated.

- We will also need to have the columns U0000 and U0302 ticked so that An entry can be recorded against these action types in IT0000 (Actions) And IT0302 (Additional Actions).

- If we run 2 actions on the same day the end-date for one of these actions is not seen. This is to indicate that this action is saved in IT0302 and not in IT0000.

- The values of the status-changing action will be stored in the table PA0000 and also in PA0302 (if and only if we have activated the Infotype 302) but in PA0302 the Begda and Enda will be same. But for The non status-changing action carried out on the same day will be saved in the Infotype 0302((if and only if we have activated the Infotype 0302) but again In the overview of the Infotype 0000 we can see only the Begda not Enda. This is to indicate that this action is saved in IT0302 and not in IT0000. And this will be stored only in the table PA0302.

-Let us assume that we want to run only the non-status changing action on some other day (I am taking consideration of only 1 action and Infotype 0302 is activated). Now this action will be stored in the Infotype 0000 and the values are updated in both the tables PA0000 and PA0302 as Infotype 0302 is activated. But as usual the Begda and Enda will be same for the action in the table PA0302.

- Let us assume that I am going to uncheck the column U0000 in the table T529A. Now for the above case it will not be stored in the Infotype 0000 but it will be stored in only in Infotype 0302 and Begda and Enda will be same and no update in the table PA000 and it will be updated only in PA0302.

- Let us asume that now already I have status-changing action in Infotype 0000 and now I am again trying to run one more status-changing action on the same day .Due to the fact that in IT0000 only ONE action can be stored at a specific date, just the LAST run action is stored in IT0000. Means the last run action overwrites the previous IT0000 record. But the previous actions are still recorded in IT0302. And we can find it in the table PA0302 with Begda and Enda same.

- In the standard SAP System, 3 features are delivered (MSN20, MSN21, and MSN32). Such features do some more checks on an executed action and 'say' if this action is allowed or not (We can find this in the table T529A).

- We can store several actions for an employee on one day. But only one is stored in Infotype 0000, the rest is stored in Infotype 0302. If we set up the actions WITH priorities, obviously the action with the highest priority is stored in IT 0. If we do NOT specify priorities then the sequence of the table T529A is followed.


The corresponding step in IMG (How to Reach):

Implementation Guide for R/3 Customizing (IMG)
< > Personnel Management
< > Personnel Administration
< > Customizing Procedures
< > Actions
< > Set up personnel actions
< > Activation 'Additional Actions'
< > Choose activity:
1. Activation 'Additional Actions'
2. Personnel Action Types
3. Priority List for Personnel Action Types


Actions Related to Additional actions IT0302:

1. Activation 'Additional Actions' (RPUEVSUP): Report RPUEVSUP makes the required entries in the Additional Actions Infotype (0302). We can set the value of the semantic code EVSUP to 1 for the group
ADMIN in table T77S0

The common error that we get during the execution of the Report RPUEVSUP:
'PerNo xxx Error while creating IT 0302' is displayed’. If this report has already been executed (so the entries already existing table PA0302), and it's executed again. In this case, as the entries already exist in the
Database, the message it displayed.

2. Personnel Action Types (T529A): We have the SAP-standard Personnel Actions and some customised Actions. The SAP-standard Actions are either status-changing (e.g. Hiring, Leaving, Transfer applicant) or non status-changing (e.g. org. re-assignment). The status will be filled in columns T529A-STAT2 (Employment Status) and T529A-STAT3 (Special payment status). We need to have the columns U0000 and U0302 ticked so that an entry can be recorded against these action types in IT0000 (Actions) and IT0302 (Additional Actions).

3. Priority List for Personnel Action Types (V_529A_B): When a non status-changing Personnel Action is copied (e.g. if we copy 02 org. re-assignment to a Zn Personnel Action type) then this will create an entry in V_529A_B and enable we to add a Priority within the PRIORITY LIST FOR PERSONNEL ACTION TYPES (step 3). We will also need to have the columns U0000 and U0302 ticked so that an entry can be recorded against these action types in IT0000 (Actions) and IT0302 (Additional Actions). It is only possible to define priorities for Action Types that are not status-changing. These priorities will then be used to decide which non status-changing Action is stored in IT0000 and which same-date non status-changing Actions are stored in IT0302.

SAP HR Salary Packaging or Flexible Benifit Package

Hi,

This is regarding Salary Packaging or Flexible Benifit Package which belongs to the family of Compensation Management module.

Salary Packaging?
(i) Salary packaging allows you to accurately forecast the impact that various salary components have on an employee's gross and net income.

(ii) By accurately projecting an employee's total package, employers can streamline remuneration to an employee's individual requirements.

(iii) Salary Packaging OR Flexible benefit Package refers to the practice of bundling salary components and other benefits to arrive at a Package often referred to as ‘Total Remuneration Package’.

(iv)Thus ‘Total Remuneration Package’ or ‘Total Package’ can be considered as a basket of Entitlements given to the Employees.


Why Salary Packaging ?
(i) This will be an on-line Flex comp declaration tool. No more filing/ submitting of a hard copy to Payroll

(ii) You can just do this at your desk with a few clicks

(iii) No hassles of getting to know the limits for each component.

(iv) System will automatically prompt you for any error.

 
Salary Packaging Components :
(i) Mandatory Salary Packaging
 
 
 
 
 
 
 
 
 
(ii) Customization of Salary Components

(iii) Eligibility Criteria for Salary Packaging

(iv) Process of Salary Packaging