Open Catalog Interface (OCI) - EqualLevel

1 open Catalog Interface (OCI)Release open Catalog 2003, 2013 SAP AG or an SAP affiliate company. All rights part of this publication may be reproduced or transmitted in any form or for any purpose without theexpress permission of SAP AG. The information contained herein may be changed without prior software products marketed by SAP AG and its distributors contain propriety softwarecomponents of other software materials are provided by SAP AG and its affiliated companies ("SAP Group") for informationalpurposes only, without representation or warranty of any kind, and SAP Group shall not be liable forerrors or omissions with respect to the materials. The only warranties for SAP Group products andservices are those that are set forth in the express warranty statements accompanying such productsand services, if any.

2 Nothing herein should be construed as constituting an additional and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and other countries. Please #trademark for additional trademarkinformation and open Catalog in Body TextIconMeaningCautionExampleNoteRecomme ndationSyntaxAdditional icons are used in SAP Library documentation to help you identify different types ofinformation at a glance. For more information, seeHelp on Help General InformationClasses and Information Classes for Business Information Warehouseon the first page of theany version ofSAP ConventionsType StyleDescriptionExample textWords or characters quoted from the screen. These include fieldnames, screen titles, pushbuttons labels, menu names, menu paths,and menu to other textEmphasized words or phrases in body text, graphic titles, and TEXTT echnical names of system objects.

3 These include report names,program names, transaction codes, table names, and key concepts of aprogramming language when they are surrounded by body text, forexample, SELECT and textOutput on the screen. This includes file and directory names and theirpaths, messages, names of variables and parameters, source text, andnames of installation, upgrade and database textExact user entry. These are words or characters that you enter in thesystem exactly as they appear in the documentation.<Example text>Variable user entry. Angle brackets indicate that you replace thesewords and characters with appropriate entries to make entries in TEXTKeys on the keyboard, for example, F2 or open Catalog of Contents1 Introduction .. 62 Calling Up the Catalog Using the SRM Server.

4 In the SRM Server .. of the Product Catalog .. URL .. Functions in the Product Catalog .. Display of a Product or Service .. of a Product .. Search .. Search .. of the Call-Up Parameters .. 103 Return from Catalog .. of the Call-Up Parameters from Section .. and Field Checks .. and Optional Fields .. Numbers .. Products .. Product Categories .. of New fields to enable transfer of Item Hierarchy to SRM .. of Inbound Handler and Outbound Handler .. of Portal Navigation while transferring data to SRM .. Extensions in the OCI .. Variant of the OCI .. 174 Handling of the Browser Window .. 185 Secure OCI .. Catalog with Secure OCI .. Handshake .. to backend call .. from Catalog .. backend call .. of Secure OCI for catalogs.

5 216 Enhancements in OCI for Mass Upload .. 21 SAP open Catalog replication of data delivered in a physical file .. replication of data over HTTP(s) connection .. Attachments .. for Data Transfer .. in the SRM Server .. External Web Services .. SICF service for delivering images/attachments .. server configuration in the BAdI SRM_GET_PROXY_INFO .. Enhancements .. settings for Mass Upload over Http(s) .. for mass upload over Http(s) .. Specification for JSON download .. Functions .. Managed Items .. Specification for real-time Quantity check .. transfer format and rules .. Numbers .. Products .. Product Categories .. Extensions in the OCI .. 507 Troubleshooting .. 50 SAP open Catalog IntroductionThe open Catalog Interface (OCI) incorporates external product catalogs into SRM Serverapplications.

6 This way, data that is required to create shopping cart items in the SRM Servercan be transferred directly from the external Catalog to the SRM Server mass upload feature is available with the release of open Catalog Interface version ,where it is possible to replicate the data from external catalogs into the SRM system usingJSON (Java Script Object Notation) format over Hyper Text Transfer Protocol (HTTP) orphysical file upload. This capability is offered only with the SAP SRM User Interface Add-On SRM Server. The OCI standard adds the following capabilities on top of OCI :a. Catalog data replication to SRM so that the end users can search for items in all catalogsusing SAP Enterprise Search without leaving the SAP SRM screen. Catalog serviceproviders can choose which items are replicated to SAP SRM and to what extent.

7 Detailsare provided insection Introduction of new fields to enable transfer of item hierarchy to SAP SRM. Details areprovided insection Introduction of the inbound and the outbound handler. Details are provided Secure transfer of user credentials (Secure OCI). Details are provided insection a Catalog to be OCI compliant, it must also be OCI compliant and support thefeatures listed Server continues to adhere to the OCI version and below, which offers the transfermechanisms over Hyper Text Transfer Protocol (HTTP).Figure 1 Overview of open Catalog Interface this case, the user is working with anSRM Serverapplication, which displays the availablecatalogs. The user calls up one of these, selects the required products, and then transfers theproduct data back to the SRM documentation describes both the architecture and the structure of the OCIand thusSAP open Catalog all the information that is necessary to support the OCIwith a product Catalog .

8 Inaddition, it describes the possible processes and their prerequisites. The documentation hasbeen written both for producers of catalogs and for system administrators ofSRM how the SRM Servercalls the Catalog as specified in OCI how the data is transferred from the Catalog to theSRM Serverasspecified in OCI the handling of the different browser windows specified in OCI describes the additions made to Secure enhancements that have been made for OCI Calling Up the Catalog Using the SRM ServerIn order for a product Catalog to be called up using the intranet or internet, its URL must beknown in the SRM Server. If the product Catalog requires additional parameters for the call-up(for example, logon names or a language identifier), these parameters also have to be knownin the SRM Serverbefore the 2 Calling the Web ServiceThe URL and the Catalog parameters are defined in the Customizing forSAP SupplierRelationship Management under Master Data Define External Web Services (Catalogs,Vendor Lists etc.)

9 In the technical settings, you can set GET or POST as the HTTP methodfor the call-up, the standard value is POST. The user s browser then calls up the catalogusing the URL and the on the situation, other parameters besides those defined in Customizing for SAPS upplier Relationship Managementcan also be transferred to the Catalog on call-up. Thesemight be, for example, to provide the Catalog with generic data or to activate specific functionsin the describes a summary of the transferred open Catalog Settings in the SRM ServerIn the SRM Server, you must enter the URL and parameters of the Catalog in the followingorder in the Customizing forSupplier Relationship Management: SRM Server MasterData Define External Web Services (Catalogs, Vendor Lists etc.)

10 URL of the Product CatalogYou enter the URL of the Catalog in the first line of the call structure; all subsequent entries(including the return URL in line 4) are transferred to the Catalog as parameters. You do notneed to specify a parameter name for the URL used here as the type. If the URLis longer than the field, you can distribute the URL over several successive fields that are thenall of the type,URL. You cannot enter Parameters as part of the URL; maintain themseparately as described in the following ParametersFollowing the URL, you must specify all parameters that the Catalog requires on call-up. Theprovider of the Catalog must have documented the names and valid values of parameter type can be eitherFixed ValueorSAP Field. This parameter type determineshow the value of the parameter is determined from theContentcolumn.