personnel subarea and number range

[Former Member]

Hi guru,

I have one personnel area and 5 personnel subarea linked to it. I want different number range for each personnel subarea. when I run PE03 and I use feature NUMKR, the system gives me an error when I tried to assign number range ti personnel subarea.

Please, could you help me?

Thanks

Regards

[Former Member · Accepted solution]

Hi,

NUMKR feature uses structure PME01 without personnel subarea BTRTL as a decision field.

There might be way of doing this but I might just create my own subfeature and use that.

There is a easy doc to help you to get started with features: [Creating and Using a Feature in SAP HR|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/80b18e32-003b-2c10-68a6-dce4b0396128?quicklink=index&overridelayout=true]

Hope this helps.

Saku

[Former Member · Accepted solution]

Thanks for shairng the doc saku

No Worries

KG

[Former Member]

Hi,

>In PE03 transaction copy Feature NUMKR as ZUMKR (customised name), enter in change mode and from Menu bar select GOTO option STRUCTURE here, in Valid fields for decisions block select BTRTL - Personnel Subarea and Save. Now you can use ZUMKR feature with personnel subareas.

Regards

Chandrashekar

[Former Member]

Hi,

There is no option to maintain feature (NUMKR) at Personnel subarae wise.

Pls check once.

Regards,

Mahesh

[Former Member]

Hello Sir,

Could you please clarify on the error message that you are experiencing when you use feature NUMKR?

Also, in which conditions are you using this feature?

Thank you.

[Former Member]

Hi Mauricio,.

I tried to link a number range to personnel subarea but I have the following message

E: Field value nodes must have dependent nodes

Message no. 5P387

Could you help me?

Thanks

Regards

[Former Member]

Hi,

1. As far as I know , you cannot generate Employee codes based on PSA.

Reason being Ecode is generated after IT0, where you dont specify PSA.

I have seen a reply on SDN to change IT0 screen...

2. The error you are getting is due to missing data in the node in NUMKR.

Please check NUMKR.

Param