Details
Nothing to say, yet
Details
Nothing to say, yet
Comment
Nothing to say, yet
The speaker discusses changes to the NPC form for notice of position change due to HCM implementation. The changes include adding a requested action box with options for work location code change, LDPR code change, or position closure. The HRSI code is now called the HCM work location code. The form also includes an LDPR field where the LDPR code for the position can be entered. The speaker shows an example of the new form, highlighting the changes. The form requires entering the LDPR code, account string, work location code, percent distribution, and effective date. Once completed, the form can be sent for approval and signature. Hi, everyone. Today, we'll be going over changes to the NPC form notice of position change due to HCM implementation. Here's a brief overview of all the changes you'll see to the NPC form. The first thing you'll notice is that we added a requested action box. Select one for a work location code change, select two for an LDPR code change, and select three for a position closure. The second thing you'll notice is that the HRSI code is now referred to as the HCM work location code. The last thing you'll see is that we added an LDPR field, which is where you can enter the LDPR code assigned to the position that you want to modify. Now, we'll have a look at the new form. Here's an example of how the new NPC form will look with the changes and additions highlighted in red. The top row has remained the same, however, you'll see in the first red box on the left, the new requested action box. For this example, we've selected action number two because we want to modify Ryan's LDPR code. In the second red box, you'll see the LDPR code currently assigned to Ryan, along with the account string, the new work location code, and the percent distribution. Please remember that if the LDPR code consists of more than one accounting line, you'll need to list all of them and their relevant percentages. In the fourth red box, you'll see the new LDPR code that I want assigned to Ryan, along with the corresponding account string, work location code, and percent distribution. The last thing that you want to enter is the effective date. Once complete, your new NPC form is now fully ready to be sent out for approval and signature. It can now continue its normal workflow.