Skip to Content
avatar image
Former Member

Catalog Mgmt

Have a few conceptual doubts in Catalogs Management.Please share your views:

1.]Is OCI some standard that both EBP as well as the vendor uploading the catalog has to follow??I understand that it describes the data exchange between EBP and external catalog application but does every company have its own OCI standards?Who decides the fields and how is it communicated to the vendor? Any clear explanation on how the flow works?

2.]Should all the products that show up in the catalogs be in the EBP product master as well??

3.]One of the sources to shop from(other than catalogs,description and old PO template) is the 'internal goods/services from EBP product master.Are the products in this source not catalogued?

4.]From SRM Doc:"In order for Requisite BugsEye to send items from its shopping cart to the external system via a URL, it needs an interface to define the parameters between BugsEye's common attributes and the equivalent external attributes. The Catalog Connector creates the mapping between the two sets of attributes, defining the interface between the two systems."-I cannot make any sense of it.What URL?Can anyone please explain in a simpler way.

Would appreciate any input from you all.

Thanks much!


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    avatar image
    Former Member
    Jan 09, 2006 at 03:41 PM

    Hi Priya,

    1 - OCI is not maint for catalog uploading, but for transactional exchanges between SRM Server (EBP) and external Catalogs. Each catalog internal and/or external can have a different schema (categories and attributes). This standard (list of HTML form fields) is designed by SAP and incorporated in the SRM Server standard.

    2 - In SRM you can create description Items (as in R/3) with description and product categoruy instead of material master

    3 - In SRM you can create items from catalogs, SC templates, or manually, either through local material master or through description and product category. Each SC line can be of type Goods or Servicer. If you want to use services in SRM with R/3 document creation, you ned the services to be customized in R/3 MM.

    4 - It defines the OCI exchanges between the catalog (Requisite, CCM, Supplier application or Punch Out, ...) and the SRM application.

    Data from the catalog item (attributes) are mapped to OCI fields, and sent to SRM through an HTML form.



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member


      am kiran

      we r implementing IS- U with CRM4.0 webclient.

      in this we want to configure FAQ's in the system , using TREX server,

      now we need to config catalog , catalog catagories, codegroups ,codes,

      problem type, problem subtype,solution type , solution subtype,

      where we need to confugurre this ,

      SAP suggesting that we need not create new catalog so what is the solution.