Catalog items visible to everyone, purchaseable only for some users

Question

Hello everybody
Me again trying to find a solution to the following problem:
We need to have some items in our catalog that are visible for every user but only purchaseable via shopping cart / SRM for some authorized users. I couldn't find any possibility in the customizing. So my attempt would be to add an additional attribute in CCM where I can put some kind of flag and then to construct an authorization check based on that flag and on a authorization profile. In case the authorization check fails, the catalog item may not be put in the shopping cart. Preferabily the shopping cart icon should be disabled for such items.
Did somebody out there already think about something similar or already implemented something like that?
It would also be a good basis for offering a publicly viewable, browseable catalog for "window shopping", because I also didn't find a way until now to publish the catalog as a standalone web application without shopping cart functionality.
What do you out there think about it?
Kind regards,
Renaud

Answer 1

Hi Christophe
Thanks a bunch for your great help! I could solved the problem and am now able to have some catalog items visible but only purchaseable for authorized users. This is what I've done:
1. Create a new authorization class (SU21)
2. Create a new authorization object within this class
3. Create a new authorization field within this object
Don't forget to save and quit the SU21 transaction and then reenter it (/nsu21) because only then you'll see your changes / additions... seems to be a "refresh-bug" in SU21.
4. Create a new role (PFCG) and an authorization profile containing the new authorization object. Assign the values needed.
5. Create a new attribute in CCM and assigned it to OCI cust_field5 (because this one is of type TEXT50)
6. Implemented some code in BAdI BBP_CATALOG_TRANSFER:
DATA: wa_et_sc_item_data  TYPE BBP_PDS_SC_ITEM_D.
DATA: wa_catalog_content  TYPE BBP_WS_OCI_ITEM_S.
DATA: lv_authorized       TYPE c.
DATA: lt_limtab           TYPE TABLE OF string.
DATA: wa_limtab(10)       TYPE C.
DATA: lv_message_v1       LIKE SY-MSGV1.
DATA: lv_message_v2       LIKE SY-MSGV2.
DATA: lv_message_v3       LIKE SY-MSGV3.
DATA: lv_message_v4       LIKE SY-MSGV4.
LOOP AT et_sc_item_data INTO wa_et_sc_item_data.
* Get corresponding line from transferred catalog data
  READ TABLE catalog_content INTO wa_catalog_content
                             WITH KEY line = wa_et_sc_item_data-number_int
                             BINARY SEARCH.
  IF sy-subrc = 0.
*   If field content for checking authority against is not empty...
    IF NOT wa_catalog_content-cust_field5 IS INITIAL.
*     Perform authority check
      AUTHORITY-CHECK OBJECT '<your auth.object here>'
                      ID     '<your auth.field here>'
                      FIELD  wa_tab.
      IF sy-subrc <> 0.
        MOVE wa_catalog_content-cust_field5  TO lv_message_v1.
        MOVE wa_et_sc_item_data-ordered_prod TO lv_message_v2.
*       Eliminate leading zeroes from product number
        WHILE lv_message_v2+0(1) = '0'.
          SHIFT lv_message_v2.
        ENDWHILE.
*       Output message
        MESSAGE ID     'ZXXX'
                TYPE   'W'
                NUMBER '000'
                WITH   lv_message_v1
                       lv_message_v2.
*       Remove item from SC
        DELETE et_sc_item_data.
      ENDIF.
    ENDIF.
  ENDIF.
ENDLOOP.
Interesting observation is, that when issueing the message with type = 'I' it does not condense the message text. With type = 'W' it does...
I also found out the reason, why the way via ET_SC_MESSAGES will not work: SAP <b>has hard coded</b> somewhere after the BAdI call the message id and message number... so no way to bypass this without a modification.
Kind regards,
Renaud