SAP List Viewer

The new object model of the SAP List Viewer (ALV) is an object-oriented encapsulation of the ALV tool that already exists.

Documentation: Link

Sample Programs: Type SALV* in se38 & press F4.

SAP Documentation for CE

SAP Has provided an extensive documentation on CE at the following link. You might consider reading this completely before you dig deeper!

Link.

How to activate CE?

At the time of writing this post, SAP has CE solution only for USA & Canada. SAP recommends that the organization has to contact them before turning CE on the system.

CE has to be activated from the SAP IMG. (TCode: SPRO).
Personnel Management -> Personal Administration -> Basic settings -> Basic Settings for CE.


When you click on 'Activate Concurrent Employment', you will be taken to the next screen where the switch CCURE -MAINS has to be set to 'X'. Here the payroll start date can also be set using the switch CCURE-PAYUS or PAYCA or PAY99.

The next setting is to activate authorization to change own data for CE. The switch is not activated by default.
Example provided in the IMG for this is as follows:

An employee is a salaried employee in organization unit A with the personnel assignment 1. At the same time, this employee has another personnel assignment 2 as a personnel administrator. Via structural authorizations, the employee with personnel assignment 2 can edit salary data for the organizational unit A. The employee cannot change his or her own salary data for the personnel assignment 2.

If you do not activate the CCURE CPAUT switch, this employee can still edit his or her own salary data for personnel assignment 1 as this personnel assignment belongs to the same organizational unit and the employee's structural authorizations are valid here. If the switch is not active, the system does not know that the personnel assignment 1 belongs to this employee and that he or she is not really allowed to change the salary data.

If you activate the switch, the employee cannot change his or her own salary data for personnel assignment 1 either, as the authorizations for changing personal data have priority over the structural authorizations.

The next option: BAdI: Determine All Personnel Assignments of a User
This BAdI is used to specify which of a user's personnel assignments are to be processed together when a self-service is called (for example, Employee Self-Service). This is activated by default in the system.


Next configuration is for the Personnel Assignment Groupings.

In this part of the IMG, you check the Customizing settings for personnel assignment groupings and change them if necessary. These Customizing settings determine whether the system, depending on the processing type, processes the personnel assignments of a concurrently employed person together or separately.

The grouping of personnel assignments is based on the following principles:

• Grouping Reason for Personnel Assignments

The grouping reason determines the business aspect for which the system carries out a certain grouping.

• Grouping Rule for Personnel Assignments

The system uses a grouping rule to assign a grouping value to each personnel assignment of a concurrently employed person.

• Grouping Value for Personnel Assignments

On the basis of the grouping value, the system decides whether it must process personnel assignments together or separately. Personnel assignments that have been assigned the same grouping value are processed together.

Grouping rules are assigned to grouping reasons. The same grouping rule can be used for several grouping reasons.

A grouping reason can also be assigned several grouping rules. Only one of these grouping rules is valid for a given time. Therefore, the system checks the existing assignments in a defined sequence and each time uses the one with the highest priority.

Concurrent Employment

As a start, here's the standard brochure provided by SAP for Concurrent Employment. (CE)

Link.

And the standard & the oldest link available which is still doing the rounds with almost everyone who makes of the mistake of asking "What is CE in SAP?".

Link.

The Reason

I am not a fan of SDN forums as it is infested with people who are always hunting for points just because their employers rate them and appraise them based on the number of points they are able to gain. In my practical experience (read: with my previous employer), I had been given poor ratings in appraisals for the reason that I didn't have enough points on SDN. It's irritating to see some people having multiple windows opened just for the sake of answering questions. One window has google and the other has SDN (I guess I don't have to explain further).
For Example: 1 2 3 4 5.
Check out these links and you will know what I mean!

All you get is stupid answers which don't solve the purpose even a little bit.

I have been working on SAP ABAP-HR since October 2005 and recently I have been assigned to work on a SAP HR Implementation which involves concurrent employment. There is not much material available for programming in SAP for Concurrent Employment and hence I have to start this blog to share (rather, document) my knowledge on CE. This will be a progressive blog as even I am new to programming with the Logical database PNPCE.

If anyone is interested to add your contributions, you can join in as an author and post here. Just leave a comment on this post.

And please, do not reward any points for anything you find useful here at this blog.