Adding custom column in Sourcing cockpit step2(Source of supply screen) - Urgent

[former_member130980]

Hi Experts,

I have a requirement to add custom column in SOCO step2 (Second Screen SoCo: Source of supplier screen) for this I have followed below

Component: /SAPSRM/WDC_DO_SOCO_GAF_2

View: V_AO_SOCO_GAF_2

SRM Version: 7.0

Release:713

steps:

i) Added custom field ZAPPR_DATE in structure "/SAPSRM/S_CLL_WD_SOCO_WORKAREA"

ii) Added newly created field under the node SOCO_WORKAREA-->WORKAREA by enhanceing standard view V_AO_SOCO_GAF_2 of component /SAPSRM/WDC_DO_SOCO_GAF_2

iii) Created new column in table WA_TABLE

iv) Done context binding

v) written logic to populate this field in WDDOMODIFYVIEW by using post-exit method.

After this I have executed this and data displayed in the Source of supply screen as expected.

When I scroll down the records system throwing dump.

Can some one let me know whether I am following correct procedure or not?

Is there anything else I am missing here?

Run time error:

Thanks in advance.

Prashanth S.

[daniel_marlen · Accepted solution]

Hello Prashanth,

The configuration seems to be correct, so the only reason why the value is not displayed is because of the meta data customizing. Please navigate to the following SPRO path: SAP Implementation Guide -> SAP Supplier Relationship Management -> SRM Server -> Cross-Application Basic Settings -> Extensions and Field Control (Personalization) -> Configure Field Control -> Configure Control for Fields of Substructures.

Make sure that you have an entry for the custom field with the following data.

• Bus. Object Set Type: SI
• Structure Field Name: ZZAPPR_DATE
• Bus. Object Type: AO_SOCO
• Set Level: ITEM
• Field Visible: ticked
• Field Enabled: ticked

Afterwards the value should be displayed.

Best regards,

Daniel

[former_member130980 · Accepted solution]

Hello Daniel,

Entry has been maintained in suggested SPRO path.Still there is no difference in the result.

I observed in debug mode that,value is present in the Work area Node.How ever, if I use BIND_TABLE statement in Modify view then only it is visible on the portal.

May be there is something else missing I am missing .

Thanks & Regards,

Prashanth S.

[Former Member]

Thank you, daniel.marlen.

I am just wondering if it's possible to edit a custom column in step 2?

Purchaser has two possibilities to change the Shopping Carts in their worklists. First of all the Shopping Cart can be changed in Sourcing Cockpit using the editable fields in Step 2.

The other option is to edit the Shopping Cart directly. This can be done by highlighting the item and clicking on the button Change. After this, the Shopping Cart opens in a new window in Edit mode, so that the purchaser can change the possible field of it (fields that have flag Posteditable in Metadata customizing).

Is it possible to make a custom column editable in Step 2 itself without opening the SC? I configured the meta data as editable but the custom column is still non-editable in step 2

Regards,

Prabhu

[daniel_marlen]

Hi Prabhu,

I'm not sure if changing the custom field in Step 2 would work properly, even if the field itself is set to editable, but you can try it. The standard logic that determines which field is editable on Step 2 is described at the end of Wiki page https://wiki.scn.sap.com/wiki/x/RIShG.

To find the relevant part, you can look for "Then system decides which fields should be editable in Step 2 of Sourcing Cockpit.".

Best regards,

Daniel

[Former Member]

This is a good read.. Just wondering how it's possible if the custom field should be a select option. I am working on a similar requirement.

[daniel_marlen]

Hi Prabhu,

You can find how you can add custom field as selection criteria in the following KBA:

https://launchpad.support.sap.com/#/notes/2500763

Best regards,

Daniel

[daniel_marlen]

Hi Prashanth,

That is the problem. At least field Visible should be set as X. Could you please double check, if the meta data customizing entry has been maintained. If yes, please provide a screenshot about it.

Best regards,

Daniel

[former_member130980]

Hello Daniel,

It worked.

Sorry my mistake.You are correct. I have not checked field visible & enable check boxes in Meta data configuration.

Really appreciate your help in resolving the Issue.

Best Regards,

Prashanth S

[daniel_marlen]

Hello Prashanth,

If the value is there in workarea, then the error should be with the display. Could you please debug the meta data determination logic, so that we can check if it is working correctly? To debug it, set a breakpoint in Method UPDATE_META_DATA_ELEMENT of class /SAPSRM/CL_CH_WD_MAP_META_HDLR. In this method there is a LOOP that loops at internal table it_data_attributes. In this table there are all the fields (columns) that is displayed in Step 2. Search for field ZZAPPR_DATE in the table. If you can't find it press F8, because system can call this method several times. If you find the field, go into the LOOP step where that field is processed and go into method get_field_metadata:

In Method GET_FIELD_METADATA check the values populated in field rs_field_meta_data.

Best regards,

Daniel

[former_member130980]

Hi Daniel,

I have debugged the Method GET_FIELD_METADATA and checked values in rs_field_mea_data.

All values are blank for field ZZAPPR_DATE.

Thanks ℜgards,

Prashanth .

[daniel_marlen]

Hello Prashanth,

You don't need to enhance the view to add a new node under SOCO_WORKAREA->WORKAREA, because this directory is mapped to standard structure /SAPSRM/S_CLL_WD_SOCO_WORKAREA. When you append the structure INCL_EEW_PD_ITEM_CSF, you also append this structure, so you just need to rebind the structure and select the custom field. If you display the context and click directory WORKAREA, you will find a button next to property Dictionary structure. If you click this, you can choose the custom field you appended before. Then system will add the node under WORKAREA.

Then you need to assign it to the custom column. Under the TableColumn, there should be a TextView element. The attribute Text of this element should be binded into the newly added custom node under WORKAREA.

Then system should display the value.

If it is still not working, please provide a screenshot about the custom node under WORKAREA and about the binding of the table column.

Best regards,

Daniel

[former_member130980]

Hello Daniel,

I have followed the same steps as you mentioned above.Still values are not displayed on the portal.

How ever, if I use BIND_TABLE statement in MODIFY VIEW values are displayed on the portal.But in that case when i scroll down I am getting Dump.

Pleas find below screen shots as requested.

Thanks In advance.

Best Regards.

Prashanth

[daniel_marlen]

Hi Prashanth,

This dump occurs, when a BIND_TABLE statement is called after WDDOMODIFYVIEW. I assume there is a similar statement in the mentioned post-exit enhancement that is used to populate the column. This confuses the system, which causes the dump as soon as user scrolls the table.

To avoid the dump, please don't populate the custom column dynamically when opening step 2, rather add the value as custom field into the SC and let the system populate the column in SOCO automatically using the value stored in the custom SC field. To do this, you just need to append structure INCL_EEW_PD_ITEM_CSF with the desired custom field. Then you need to populate this field according to your needs. Afterwards you need to assign the custom field from the standard workarea context for the corresponding column in SE80.

Best regards,

Daniel

[former_member130980]

Hello Daniel,

Thank you for the reply.

As suggested I have added the new custom filed in INCL_EEW_PD_ITEM_CSF and populated the value.

I can see this value on SC in BBP_PD transaction.

Then Added newly created field under the node SOCO_WORKAREA-->WORKAREA by enhancing standard view V_AO_SOCO_GAF_2 of component /SAPSRM/WDC_DO_SOCO_GAF_2.

New column is visible and no dump when scroll down on Portal but No value is displayed in it.

Is there anything else I am missing here?

Appreciate your help.

Best regards.

Prashanth S.