SRM 5.0 with Heiler Business Catalog

[Former Member]

We have a requirment

Business Catalogis needs to be enhanced to allow different pricing to be displayed for each region/plant during creation of shopping cart. To allow users accessing the eCatalogue through SRM to view the relevant pricing, their region/plant needs to be passed through the OCI interface to the eCatalogue.

Technically we are using standard call structure for call WEB catalog

10https://emp.smartbuy.nsw.gov.au/is-bin/INTERSHOP.enfinity/WFS/MarketSite/en_AU/-/AUD/OCICatalogService-Inbound URL

20 USERNAME EXTERNALBUYER Fixed Value

30 PASSWORD WINTER Fixed Value

40 SERVICE DETSTATEOFFICE2 Fixed Value

50 ~OkCode ADDI Fixed Value

60 ~target _top Fixed Value

70 ~caller CTLG Fixed Value

80 HOOK_URL Return URL

kindly guide me about OCI configutaion and relevent changes in catalogs to pursue with above changes.

Regards

Dayal

[jason_boggans]

Hi,

If the various views of the data within the catalog are assigned to specific users, or to a parameter read by the catalog to narrow down this view, the data can be pre-configured using the BBP_CAT_CALL_ENRICH Badi where the parameter can be added to the catalog call structure dynamically on catalog call up. This may suit your requirements.

Regards.

Jason

[Former Member]

Hi Jason,

Is there any modification require in standard call structure like ?

Seq Parameter name Parameter Value Type

90 Plant BE_PLANT SAP Field

How BBP_CAT_CALL_ENRICH BAdI will help to put dynamic parametre value to access catalog subsets (differnt price) based on plant from SRM. I mean to say how it will interact with catalog UI and it's search (Businee logic).

Regards

Dayal

[jason_boggans]

Hi,

If additional parameters are required for the catalog you are accessing like this Plant parameter then they could be added as parameters to the call structure but I am not so sure the parameter PLANT with type SAP_FIELD would be correctly interpreted, my guess for this is it would require a static value in the call structure to be interpreted correctly as I do not think at catalog call such values would be obtained, I think (just think, not sure without debugging) that the value for BE_PLANT would be obtained throguh the GLOBAL_TO_ITEMS method which is executed on catalog RETURN as strictly it is generally not required for catalog call up only on return and during Procurement Document creation.

My idea for usage of the BBP_CAT_CALL_ENRICH was to have a range of users, each with specific authority within the catalog, and using the cat_call_enrich Badi logic, these specific users would be invoked on catalog call based on importing parameters into the Badi like the SY-UNAME etc, so if SY-UNAME= [CERTAIN USER SET], then USERNAME=CATALOG_ACCESS_USER1 etc ....

Hope that helps somewhat.

Regards,

Jason