OCI compliant catalog

Dear Experts,
i was requested to make our company's product catalog OCI compliant for one of our partners to access and use.
my question is :
- Am i just required to create an XML file for our products and place it on a server for them to access? or just create a database table with the fields they request and their SRM System'll handle the XML part?
i've read the helpful documents posted here and i'm still unsure where to start.
i'd like to add that we've our E-commerce website where this partner used to buy our stuff from there.
Thanks a lot in advance.
Edited by: Beeso9 on Jan 19, 2011 2:34 AM

Hi,
Please check the section 4.3 in OCI specification.
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e020a283-e6ce-2d10-0ebb-bd4de8c32036
It says "XML data is embedded in an HTML form for the transfer from the catalog to the SRM Server via the useru2019s browser".
You just change the checkout method and generate HTML page with embeded XML data.
You can find examples.
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/60996f9f-f5ce-2d10-e9bd-a603b4b0be2c
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/700af47a-f6ce-2d10-b994-974f32acef52
Regards,
Masa

Similar Messages

Non-OCI compliant vendor

Greetings. Does anyone have experience bringing a new vendor catalog online from a supplier that has never done OCI? Is there some documentation somewhere that I can give the Vendor that will help them understand the work that will need to be done on their side? To this point all of our roundtrip Vendors have been OCI capable and we've used the default HTTP Post technology. What is the standard method for addressing this kind of issue? Any direction you could provide would be much appreciated.
Best regards,
Shawn O'Connor

Hi Bhakti.
The link provided by Masa gives you a basic understanding and the information is enough for the suppliers to create a OCI complaint catalog. It is also applicable for SRM 7.0 as well.
According to me there were no much changes in the SRM7.0 for OCI
Note: The link has the OCI version as 4.0. Recently this is updated.
Also see the below link as well.
http://help.sap.com/saphelp_crm20c/helpdata/en/0F/F2573901F0FE7CE10000000A114084/frameset.htm
Regards
Bala

OCI Punchout Catalog integration in Webdynpro for Java

Hi,
I am planning to call a external vendor catalog (OCI) from my webdynpro application and consume the values, Can some one help me on how to achieve this ? I am not using SRM. I need to pass the value to ERP system
Thank,
Vinit Pugaliya

Hi Vinit
We're in the exact same situation today. Did you ever solve it? We're able to call the external catalog via OCI and would like to import the http post response containing the catalog items back into our own webdynpro java app. Would be great if you could share your solution.
BTW: we're not using and do not plan to use SRM
Thanks and best regards
Renaud

Is OCI (Open Cataloge Interface) supported from MM or SD

Hello.
My customer has installed SAP ERP, but do not have SAP SRM. We plan to implement a punch-out from SAP to a web site of Cisco with use of OCI.
I do find a lot of information about OCI related to SRM, but none related to ERP.
Does anybody know wether OCI somehow is support by ERP?
Geir Sunde, tlf. +47 977 555 97

Hi,
Open Catalog Interface is related to SAP SRM it is nothing to
do with SAP R/3.When we are using the Catalog for creating a
shopping basket this interface is the link between the Catalog
and the SRM server.
Please Post this message in this forum in SRM general you
will get some Inputs but definitely it is NOT supported by
SAP R/3.
We plan to implement a punch-out from SAP to a web site of Cisco with use of OCI.
I think you have to IMPLEMENT -SAP SRM only
G.Ganesh Kumar

PCUI and OCI (Open Catalog Interface)

Hi,
we want to integrate a external catalog into the PCUI application qutation. The goal is to take over the shopping basket of the catalog into a Quotation. The data which should be taken over are products out of the external product catalog. Therefore the open catalog interface (OCI) should be used. The external catalog sends the shopping basket selected by the user via a HTTP Post to a so called Hook-URL which is provided by the calling application (PCUI). The calling application (PCUI) will retrieve this POST and take over the data send by the HTTP Post.
My question is now if something like that is possible with PCUI framework?
Thanks for your help.
Regards,
Mario

Thanks for the quick and succinct reply.

OCI Punchout Catalog integration

Hi,
I am planning to call a external vendor catalog (OCI) from my webdynpro application and consume the values, Can some one help me on how to achieve this ? I am not using SRM. I need to pass the value to ERP system
Thank,
Vinit Pugaliya

I hope to help you...
HTTP Post
ABAP -WebDynpro - Read URL Parameter
OCI custom Form Data Return
regards,
Angelo

Searching for an OCI Demo Catalog

Hello altogether,
am looking for an Demo OCI Catalog - which I can use for testing in SRM.
Does anybody know, if there is an test catalog in web?
Would be glad, if someone could help me.
Best Regards,
J.H.

If they are different product categories you will be required to map to your own.
This can be done via BADI 'BBP_CATALOG_TRANSFER'.
Hope this helps.
Keith
The details for this badi are below:
Transfer Shopping Cart from Catalog
You can use the Business Add-In BBP_CATALOG_TRANSFER to change or add to the data that the catalog returns to SAP Enterprise Buyer via the catalog interface.
Note that your changes also affect the following applications in SAP Enterprise Buyer:
Confirm Goods Receipt/Service Entry
Plan Products for Maintenance Order
The call of this BAdI occurs in function module 'BBP_WS_IMPORT_SC_DATA'. This module is called by the relevant application to import catalog items previously sent by the browser of the user to the application Web server from there. After the catalog has transferred the data to SAP Enterprise Buyer the system carries out the following actions.
Conversion of ISO code of unit of measure and currency to SAP format
Conversion of price field to SAP format
In the case of transfer of a material or service number:
The system reads the product master with this number. If the number exists, the system transfers from the product master record the description and the purchase order unit of measure.
In the case of a partner number:
The system reads the business partner master with this number. If the number does not exist, the number in the shopping cart item is reset.
Note
In previous Releases, only the tables with the prefix "ENRICHED" were available. These were then returned to the calling application and transferred to the relevant document structure from there. From this Release on, the data is transferred from the current document structure to the application. The relevant tables are included as additional parameters (parameters with the prefix "ET_SC_").
New implementations should use these tables only and set the parameter "ev_sc_structures_used". In order that previous implementations need not be changed, a mapping occurs after the BADI. The parameter controls the mapping direction:
Set: New structure overwrites old structure
Not set: Old structure overwrites new structure
In the method ENRICH_ITEM_DATA, the following parameters are available:
catalog_content
This parameter contains the original data that the catalog transferred to the catalog interface. The structure corresponds exactly to the catalog interface. The data in this parameter is only for information purposes, you make any changes in the parameters et_sc_item_data , et_sc_accounting, et_sc_partner, et_sc_orgdata, et_sc_longtext, and et_sc_messages.
Note
The catalog interface also contains customer fields that you can use for your own purposes. You can pass these on in fields that the application can use further.
enriched_item_data
This parameter contains the data for a shopping cart item in Enterprise Buyer.
Note
This table should not be used in new implementations (see above Note).
enriched_acct_data
This parameter contains all account assignment fields. This parameter is empty at this time in the standard system.
Note
This table should not be used in new implementations (see above Note).
enriched_item_longtext
This parameter contains the long texts for the items.
Note
This table should not be used in new implementations (see above Note).
catalog_content_errors
This parameter contains the error messages that occurred when the catalog items were being enriched.
Note
This table should not be used in new implementations (see above Note).
ev_sc_structures_used
This parameter has to be set if the following tables are used in the implementation (recommended procedure, see Note above) et_sc_item_data This parameter contains the data of a shopping cart item in Enterprise Buyer.
et_sc_accounting
This parameter contains all account assignment fields. In the standard system, this parameter is empty at this time.
et_sc_partner
This parameter contains the links to the requester and the supplier, if used.
et_sc_orgdata
This parameter contains the links to the org. data for the partners from et_sc_partner.
et_sc_longtext
This parameter contains the long texts for the items.
et_sc_messages
This parameter contains the error messages that occurred during enrichment of catalog items. If this table contains a message of type 'E', the item causing this error is not transferred to et_sc_item_data. If the item is added in the BADI again (from the data from catalog_content), the relevant error message should be deleted, since the current SRM Server application generally searches this table for error messages of type 'E' in order to output an error message to the user.

Access a OCI Catalog from ABAP code

Hi Experts,
We may need to access an OCI Catalog from an ABAP code. We will need to punch out the Catalog in a browser window, and somehow get the results from the browser back to the ABAP code.
Any idea of how can this be accomplished?
Thanks and regards,
José Omar

Accessing the catalog is nothing but creating a hook url and directing to that URL.
For eg. you should have the parameters read from the SPRO settings in SRM and then creating an URL in the fly.
But as of now you can have hard coded URLs being fed in.
ie you click on a link and you fire the exit plug as in Web dynpro in suspend mode.
The main criteria is to have the catalog OCI 4.0 complaint. (read mandatory fields etc in OCI 4.0 documentation)
Then once you shop from some items in the catalog , the OCI compliant catalog will send you the data in the required file format.
At the receiving end , PO etc . you should have a ABAP method (at resume ) that interprets this sent name-value pair file from the catalog. then populate this data where you want.
you can have a look at the SRM methods that does the same in ABAP.
This would the 20,000 feet or more process overview on how it works. Hope this helps
thanks
-Adrivit

OCI catalog in EHP4 Webdynpro screens

Hi Folks,
As of ECC6.0 it is possible to use an OCI compliant catalog from the PO and PR creation screen.
Do any of you know how to anebla that in the "new" webdynpro screens for creating PO's and PR's either via business client or portal?
Thanks in advance.
Thomas

Hi Vinit
We're in the exact same situation today. Did you ever solve it? We're able to call the external catalog via OCI and would like to import the http post response containing the catalog items back into our own webdynpro java app. Would be great if you could share your solution.
BTW: we're not using and do not plan to use SRM
Thanks and best regards
Renaud

Steps for Mapping OCI Catalog with R3 ISA (ERP E-Commerce)

Hi Gurus,
I just needed some help on how to go about integrating R3 ISA with OCI Catalog. Please provide reference to some relevant documentation if available.
Thanks.
Jai

Technically other than some [XCM settings and configuration|http://help.sap.com/saphelp_crm50/helpdata/en/2f/86653fac7ab21ae10000000a114084/content.htm] that define the external catalog URL, there isn't much needed to integrate a OCI compliant catalog - provided, you already have a OCI compliant catalog.
Start here on some technical information on OCI catalogs - [/people/masayuki.sekihara/blog/2007/12/07/oci-open-catalog-interface-setting-and-trouble-shooting|/people/masayuki.sekihara/blog/2007/12/07/oci-open-catalog-interface-setting-and-trouble-shooting]

OCI Catalog Limitations

Dear SAP expert,
Could you please share your experience on external / OCI catalog re- limitations in the SAP CRM E-Commerce area?
Should we expect difficulties with integration & pricing? Will it restrict available functionalities and views in the B2C scenario?
Thanks in advance,
Regards, Stephanie

OCI catalog integration with CRM Web Channel is fairly simple and works fine. CRM Web channel side of the OCI integration can be enhanced to include custom fields to be transferred from OCI catalog to Web Channel basket.
The catalog item details and Pricing are the features of the external (OCI compliant) catalog you are using. So, you must check your external catalog for this
The user interface and navigation - or how the user interacts with the catalog and orders items - is what might turn you off. Remember, the external catalog, as you know is technically another web application that is NOT web channel application. Inter web application integration is through OCI (hiitp or xml) protocol.
1. Matching the styles of external catalog and your web channel application - might sound easy, but depends on the external catalog's capability to adapt to style changes.
2. The navigation from one application (catalog) to the other (web channel) is NOT what you will like in today's slick UI-s. Two applications will be open when the user is browsing the catalog to select and "collect" the items in external catalog and then transfers the items to the web channel basket.
Suggest you do a proof-of-concept and run the UI and navigation to the business users before you jump in.
Also, explore if you can use the external catalog using web services.
Easwar Ram
http://www.parxlns.com

Punchout catalog issue

I have several punchout catalogs working fine, except for one that I cannot connect the supplier's website. The set up is the same as with other punchout catalogs that I have. The error I get with this one is that access is denied. The supplier assures me I don't need a password to log in, but they say I have to have the XML set up correctly in order for authentication to occur at their site.
I don't know what that means. What role does XML play in OCI interface? Can anyone help me with this issue?
Thanks,
SN

Hi,
XML has nothing to do with the call to the catalog, so if your supplier says that XML has to be setup correctly I doubt they have an OCI compliant catalog, more likely it will be a cXML one.
OCI uses only a HTTP GET or POST to call the supplier catalog.
Only the return message from the catalog to SRM you can choose between either a HTTP form or an XML variant.
One other thing you might want to look at is if the supplier site uses a secure http connection (https://<url_to_catalog>) in which case you might need to add a certificate to your SRM server.
Regards,
Robin

Use of Open Catalog Interface (OCI) in ERP

Dear colleagues,
I am not sure if this is the right forum to post this question but can we use Open Catalog Interface (OCI) without having SRM directly in ECC 6.0? If yes what are the prerequisites, customizing, licensing etc.
What we are planning is end users will select material(s) he/she wants to procure from a catalog from a portal (not an SAP portal) and once this is done purchase requisition will be created in ERP system.
Regards
Melih

ECC6.0 MM does support OCI. This works on both the Purchase Req and PO. You can punchout from MM and shop from an OCI compliant source such as MDM, supplier hosted, other catalog tools and then this informaiton is pulled back into the Purchase Req or PO. OCI is delivered with ECC6.0 MM so there should not be any license issues.
Configuration is part of the catalog web service set up and this is where you maintain information such as URL, user id, password, etc.

Punchout from ECC 6.0 MM via OCI to MDM Catalog

Hi Folks,
my customer wants to integrate the SRM MDM Catalog with ECC 6.0/MM without using SRM or XI. I already found threads talking about external catalogs being linked from MM using
ECC SPRO : Materials Management -> Purchasing -> Environment Data -> Web Services: ID and Description
which I have available. However, I was expecting an entry for example in PM where I have the activities for OCI (Catalog ID, HTML-Fields etc.) in detail, but not a general web service ID an description. I am familiar with OCI, but not with web services.
How can I use the web service ID to turn into a configurable OCI-interface?
Thanks, Andy

Hi Andreas,
For our customer we would like to link ECC5 MM to SRM-MDM 2.0.
Our MDM catalog works well with SRM EBP 5.5.
For a different scenario we would like to link MDM directly to ECC5 : MM / PM / PS.
1. In ECC5 MM there is no customizing entry for Web Services.
It used to be :
IMG --> Material Management --> Purchasing --> Environment Data --> Web Services.
This entry is no longer exist.
Do you have an idea of how to link MM to MDM ?
2. In order to link MDM to ECC5 PM, we customize :
IMG --> Plant Maint ... --> Maintenance and services ... --> Maintenance and services order --> Interface for procurement Using catalogs (OCI) --> define catalog
I did the same setting as in SRM EBP.
and also
IMG --> Plant Maint ... --> Maintenance and services ... --> Maintenance and services order --> Interface for procurement Using catalogs (OCI) --> Assign Catalog to Order type
I assign
PM01 order type,
a plant,
sequence 1
Catalog ID.
I have no idea about the following entry in this table :
- Organization
- User
- Password.
I put them with blank value.
Thanks for your help.
regards
XAvier NIEL

OCI Catalog Punchout From MM/PM

Hello,
We are configuring an externally maintained OCI punchout catalog with the MM and PM modules within ECC.
When adding items to the requisition in MM, and the work order in PM, none of the fields are fixed (non-changeable/editable). I was expecting certain fields (e.g. Price, Material Group, Vendor, etc.) to be fixed - similar to when punching out from an SRM system.
Shouldn't the applicable fields be non-editable?
Thanks,
Edgar

Hi Andreas,
For our customer we would like to link ECC5 MM to SRM-MDM 2.0.
Our MDM catalog works well with SRM EBP 5.5.
For a different scenario we would like to link MDM directly to ECC5 : MM / PM / PS.
1. In ECC5 MM there is no customizing entry for Web Services.
It used to be :
IMG --> Material Management --> Purchasing --> Environment Data --> Web Services.
This entry is no longer exist.
Do you have an idea of how to link MM to MDM ?
2. In order to link MDM to ECC5 PM, we customize :
IMG --> Plant Maint ... --> Maintenance and services ... --> Maintenance and services order --> Interface for procurement Using catalogs (OCI) --> define catalog
I did the same setting as in SRM EBP.
and also
IMG --> Plant Maint ... --> Maintenance and services ... --> Maintenance and services order --> Interface for procurement Using catalogs (OCI) --> Assign Catalog to Order type
I assign
PM01 order type,
a plant,
sequence 1
Catalog ID.
I have no idea about the following entry in this table :
- Organization
- User
- Password.
I put them with blank value.
Thanks for your help.
regards
XAvier NIEL

OCI compliant catalog

Similar Messages

Maybe you are looking for