ISA-Ecommerce : Passing extension data at item level to CRM backend?

Question

Hi Experts,
I want to pass the extension filed data which is present at item level to the CRM back end system. In DEMO1 example provided, they have demonstrated about header data to pass.
HeaderData headerdata = isaBOM.getBasket().getHeaderData();(header data BOM instance)
ItemListData itemsdata = isaBOM.getBasket().getItemListData();(Item data BOM instance)
String extHDshipmethods = (String)p_request.getParameter("zhext_shippmethods");(request from http for header data)
String extIDshipmethods = (String)p_request.getParameter("ziext_shippmethods");(request from http for item data)
headerdata.addExtensionData("ZHEXTENSIONSHIPMETHODS", extHDshipmethods);(adding extension to header data)
itemsdata.add("ZIEXTENSIONSHIPMETHODS", extIDshipmethods);(adding extensoin to item data but gettin error)
In the above last line i am getting an error saying that add(itemlistdata) cannot be used as a string. Generally for header data, in the extension guide it is mentioned that we use "headerdata.addExtensionData("",)" but for items data what should be used??
Thanks a lot in Advance!
regards,
lakshman.
Edited by: lakshman reddy G on Jan 21, 2009 2:24 PM

Answer 1

Hello LRG,
In the Java and JSP layer
In the ZMaintainDispatcher, override the Item level method
public void customerExitParseRequestItem
This method is called for each item to parse
the custom variables. Hint: Since the items are processed in a loop in the JSP, it is
customary to name the page level variables suffixed with the Item index like myData1[itmIndx]
public void customerExitParseRequestItem(
   RequestParser parser,
   UserSessionData userSessionData,
   ItemSalesDoc itemSalesDoc,
   int itmIndx  {
   String zItemExtData1 = "";
// Item level data1[itmIndx] - value is set for item itmIndx
// see the method parameters
   zItemExtData1 = parser.getParameter("zItemExtData1" +
itemIdx).getValue().getString();                    
   itemSalesDoc.addExtensionData("zItemExtData1", zItemExtData1 );                    
This will parse and add item level extensions to the items object.
In the ABAP layer
Implement CRM_ISA_BASKET_ITEMS and code in the methods  changeitems_set_data and getitems_get_data
In the request cycle, you will read the value from the extension table and persist that in the
transaction - say in a EEWB field. In the method changeitems_set_data
      READ TABLE lt_extension INTO ls_extension WITH KEY
               name = 'zItemExtData1'.
      IF sy-subrc EQ 0 AND NOT ls_extension-value IS INITIAL.
        ZEEWBDATA1 = ls_extension-value.
      ENDIF.
In the response cycle, code the getitems_get_data
*     Populate Extension data Data1 - Assuming that you read it from EEWB field ZEEWBDATA1
      CLEAR ls_extension.
      ls_extension-ref_guid = ls_guid.
      ls_extension-name     = 'zItemExtData1'.
      ls_extension-value    = lv_leewbdata1.
      APPEND ls_extension TO ct_extension.
In principle, the idea is same as what is shown in the extension guide for the header.
Please note: Depending upon several user interaction requirements, you may have to
use different methods in the Item BAdI as well as other methods in the MaintainDispatcher class.
Easwar Ram
http://www.parxlns.com