can we add "Pers. Sub Area" in ABKRS feature as "Field of Decision Opera"

[Former Member]

Hi Gurus,

I have payroll Area Name "Sales" for Sales Department. I have "Personel sub Area" Sales as well. I want to use this personnel sub area to default payroll Area for sales personnel based on "Personnel Sub area".

However, personnel sub Area is not available in ABKRS feature as "Field of decision operation", when creat new node in feature.

kindly replyl

regards,

[Former Member · Accepted solution]

Ikhlaq,

Personnel Sub Area filed is not available in ABKRS feature as "Field of decision operation" for a reason.

Features are used as decision trees based on certain conditions. Here in this case, you want to default the payroll area based on the Personnel Sub Area of the employee.

When you run the hiring action the "Personnel Sub Area" field and "Payroll Area" field are in the same screen and Infotype (Org assignment - 0001). Remember infotype 0000 (Actions), which is the first infotype to appear when running an action does not have a field Personnel Sub Area. So, the feature program cannot determine the payroll area

A workaround , If you are using infotype 1008 (Acct. Assignment Features) for positions then you can write a small program to return the value in the feature based on the field BTRTL in infotype 1008 for the position specified in Infotype 0000(actions).

What Sergey wrote is correct if you want to add a decision filed in your feature but please note that the Feature program does not have artificial intelligence and it is not psychic for sure

Hope this helps.

Please let me know if you have any more questions.

-Deepak

[Former Member · Accepted solution]

Depak we can do it as below successfully tried.

execute Tcode PEO3

enter feature name i.e ABKRS

select Attribute -> display

on active screen select change

then button "structure", that is on bottom.

and then from "Valid fields for decision" list select row containing BTRTL (personnel Sub Area).

Hope u'll try it

regards

[Former Member · Accepted solution]

Imran,

I know how to add the decision field in a feature.

If you read my last post carefully , what I was trying to say is that adding BTRTL (personnel Sub Area) in ABKRS feature is useless.

Go take a look at the Org assignment and Actions infotype and you will find that the Personnel Subarea and Payroll area are in Infotype which is 00001 and actions infotype does not have personnel subarea !!!!!!!!

So you can not default the payroll area on the basis of Personnel subarea.

Go ahead and try it.

Thanks,

Deepak

[Former Member · Accepted solution]

Hi Deepak,

Since It0001 is not created yet, we cannot pick up the data on the OM side for the (Person-Position-PSA).

Do you have any other solution to default ABKRS based on BTRTL?

Thanks

G

[Former Member]

Hi,

Yes it is not possible in normal circumstances. But it is possible with the user-exit. When you are switching from IT0000 to IT0001

since the PSA is not available, feature will not be able to fetch the correct value.

What you can do is, define a default value of payroll area (e.g. 99 for which you are not executing the payroll)for the switching from IT000 to IT0001. The code the user exit which is common for the master data. You can call the feature ABKRS here again. Now when you will fill the Personnel subarea and other required parameter in IT0001and save it (or press enter), system will call the feature again and default the correct value.

For the user-exit, check with your abaper. If you are not able to find the user-exit, let me know. It works perfectly as i did the same in 1 of my implementation.

- Praveen

[Former Member]

For adding personnel subarea as a decision field, you should change the structure of ABKRS feature.

Go to PE03 -> Select Attributes and press Change -> then press Structure -> Select BTRTL and press Save.

After that you can do necessary changes in this feature. But don't forget to activate it.

Rergards,

Sergey.

[Former Member]

conceret and perfect Sergey