Save custom fields in custom tab attached on PO Portal screen

[Former Member]

Hello All,

Requirement :-  There are 10 business fields to be made available on PO portal screen as an additional custom tab, after overview,header,..tracking..etc tabs.

Approach :

1) Created a Z WDC with all the 10 business fields .

2) Thru FPM configurator.., included  the Z WDC as an additional tab.

3) When i tested it.. it is appearing on the PO header as a additional tab.

4) I also managed to capture the events 'EDIT' and 'DISPLAY' and made the fields enable/disable and also hold the data.

So far so good..

Now the issue is when a user clicks on edit and fills all these 10 business fields on  the z custom wdc, he gets a message saying..

" No changes were made" (but infact he/she filled out all z fields).

But if i change anything on the standard tabs... the data is saved without any message.( its obvious as it is standard code and it is the way it is coded).

Now the question is, how to notify the standard code that indeed there was a change in the Z  wdc and save the data in DB.

Regards,

Vinay

[Former Member]

Hi Vinay,

First and foremost, the context node of the custom tab and the standard tab should be the same. I have written a blog on adding custom tab to Rfx /contract / response. See if it helps.

http://scn.sap.com/community/srm/blog/2012/07/24/create-additional-data-tab-in-rfxresponsecontract

Regrads,

Naveen

[Former Member]

Naveen, thanks for the reply.. surely i will try this approach.

FYI...

if you take a look at the PO portal screen,

there you can find that all the tabs are individual WDC which are conifgured the mother FPM WDC.

All these are configured as invidual tabs in the FPM Configurators.

Can you throw some light on that after your observations.

Regards,

Vinay

[Former Member]

Hi Vinay ,

I dont have creation of PO in SRM in my landscape for me to check. But let me tell you what I have observed with respect to the other screens when it comes to tab enhancement.

If you see the blog ,I have used the same structure in the context node of the additional tab as that of the item basic data tab and extended fields to it.  The reason for this is handling UI actions and automatic save and retrieval of the data to the DB structure. If you have them as a separate structure , you will have to handle saving and displaying of data to the db explicitly.

This is what I had noticed in other Business objects such as Rfx , Response and Contracts. I am assuming it is the same for PO.

Regards,

Naveen