Add New Tab Customization on SC Item Level - SRM7

[Former Member]

Hi gurus,

I have requirement to add new tab on SC Item level. Which should show data from LongText of SC. New TextID created for this development. (Since Requirement is of Vaiable number of fields per Item so cant append Strucutre simply)

After Initial analysis I see 2 ways to achieve it.

1. Like Standard SAP way (Similar way SAP did for standard Tabs)

- But its really complicated at Mapper Class & PDO Layer. Any Docs ??

2. Tab Enhancement Framework - Use of Table : /SAPSRM/C_TS_EXT

- With this I m able to call Z component. But not able to co-relate it with SC item level.

- How to pass Item GUID to Z component in proper way??

- How to link Z components data SAVE event with standard SAVE button of FPM or SC ??

Is there any other better way ??

Is it possible via Table Extension ?? what are steps to do it ??

Thanks

PK

Edited by: pkumthek on Nov 2, 2010 4:35 PM

[Former Member]

Hi Prashant,

Did you acheive this? If yes, can you please let us know how you did it.

Thanks in advance.

Regards,

Karthik Babu

[Former Member]

Hi pkumthek,

I do suggest you not try to add new tab on SC item level. We cost 4 people month to accomplish this little function...A better way is adding a hyper-link on item level which could navigate to a pop-up window. You can finish your logci in the pop-up window and it will cost pretty less. Just for your information.

[Former Member]

Hi,

You can achieve this by:

Use case: additional table-like information is supposed to be stored in a business object .

Example: create a table-like extension for Shopping Carts (SC) at item level.

First step: appending the field to the correct structure in SE11 or via transaction SPRO.

Structure names for table extensions are according to the pattern:

INCL_EEW_PD_<x>_CST_<y> with

<x>: HEADER, ITEM

<y>:

􀂾SC u2013 Shopping Cart

􀂾PO u2013 Purchaser Order

Path in IMG (transaction SPRO):

SAP SRM -> SRM server ->

-> Cross-Application Basic Settings

-> Extensions and Field Control (Personalization)

-> Create Table Extensions and Supply with Data

-> Define Customer Table Extensions on Item Level

Second step: you additionally need to append the new table extension field to the

corresponding INCL_EEW_PD_<x>_CST structure called u2018cross-documentu2019 structure. This can

also be done in IMG

You can explicitly enter the very same field(s) (name and type) into both append structures.

It is recommended, however, to first create another structure with the new field (in SE11) and

then include that other structure in both append structures

(menu path in SE11 screen: -> Edit -> Include -> Insert).

Default append structure names in this example are

ZAINCL_EEW_PD_ITEM_CST_SC and

ZAINCL_EEW_PD_ITEM_CST

when using the IMG path..

Third step: Set visibility of the table extension.Create an entry with TICUS for item data (THCUS for header data).

Donu2019t miss to populate the Transaction Type field - you could save the table entry without it,

but it will not work!

Fourth step: Configure Control of Fields of Table Extensions. Create an entry with TICUS for item data (THCUS for header data).Donu2019t miss to populate the Set Level field - you could save the table entry without it, but it will not work!

Fifth step: Configure Control of Actions

Sixth (final) step: SM30 - maintain view /SAPSRM/V_MDFSBC_DEFAULT

Now you are ready to test using tab u2018Table Extensionsu2019 at item level of the shopping cart.

Technical hint: you will find the content entered into customer table extensions in table

BBP_PDICF for item fields (like in this example) and in table BBP_PDHCF for header fields

respectively.

Thanks,

Anshuk Saxena