Adding fields to ESS screen using WebDynPro

[Former Member]

I am investigating the need for us to add roughly 10 fields to a Dependant/Beneficiary screen using WebDynPro. Is this a simple task or somewhat involved?

Does anyone have documentation on how to accomplish this?

Thanks.

Jason

[Former Member · Accepted solution]

The Benefits application is complex. You need to evaluate the PlanSelection modules, etc. We have added fields to the Benefits pages. It involved some coding to evaluate plantype and then adding to a container on that particular view. The main concern I would have is regarding the data for the fields. The main question is whether the data is avaiable in the existing bapis used by benefits.

[Former Member · Accepted solution]

Stephen -

That is something we will need to look into. Currently, we do not have anyone on site with WebDynPro experience. We are currently looking for someone.

I won't make a reference to your name because I'm sure you've heard it a million times before.

[Former Member]

Hi Jason,

Adding any fields of "Standard ESS Views" can be as easy as adding a field to the view and then bind it to a model field in the context.

But its not that simple too. Even if the field is there in the context, you cannot be sure that it will get values from backend or it will save values to backend.

If you have seen the BAPI's you would have known by now that its uses the New Infotype Framework. The data is moved between various structures before it finally comes to the screen and vice versa.

So if you see that the data is not being saved to the backend or a field is not getting the value from the backend, you need to check at every interface where the data is being moved from one structure to another that its properly moved.

Hope this is understandable.

Regards,

Shubham

[Former Member]

Thank you Shubham. Wehn I get to that point in development this information will be very helpful

Thanks again.

Jason