topic Re: using feature for screen modifications in Application Development and Automation Discussions

using feature for screen modifications

RahulSoneji31 — Wed, 16 Sep 2009 07:14:52 GMT

Hi, I have created an infotype with 2 subtypes.

Now I want to use Feature for screen control. I created the feature p9600 for my infotype and added the following decision tree:

country grouping~~-> user group> subtype~~-> A or B.

Depending on A or B I havbe assigned a variable key which I have used in SPRO 'change screen modifications'.

Based on suntype a or b, different fields will show on pa30 for the infotype.

now spro has 3 entries for my infotype. 1st is the default one and the other 2 are the entries with variable keys.

But when i use the infotype in pa30, the screen modification does not work as required. It just shows all the fields, which means it is using the main entry in spro .

Please help me resolve this.

Also what are the fields itbld and tclas in features used for?

do i need to use these so that the feature works?

Re: using feature for screen modifications

Former Member — Wed, 16 Sep 2009 07:20:44 GMT

Hi,

Please make sure that when you are using the employee for PA30, he falls amoung the user groups ( Or country Group ) you have defined in the feature.

Regards

Pavan

Re: using feature for screen modifications

venkat_o — Wed, 16 Sep 2009 07:29:04 GMT

Hi, Once you define features, You need to use them in the pbo of the custome infotype screen by using the below function modules.

HR_FEATURE_BACKFIELD           Reading a Feature with Field Return 
HR_FEATURE_BACKTABLE           Reading a Feature with Back Table

Thanks Venkat.O

Re: using feature for screen modifications

MilindMungaji — Wed, 16 Sep 2009 07:30:32 GMT

Mainatain view V_T588M

Re: using feature for screen modifications

RahulSoneji31 — Wed, 16 Sep 2009 12:09:36 GMT

Hi all,

Thanks for the reply. I sollved the probelm.

I was using values other than '0001' and '0002' (VI and PR as I had named them) for the subtypes in the decision tree of the feature. below the subtype node.Hence the Feature was not working properly.

I changed it to 0001 and 0002 respectively. Now its working good.

Thanks!