Owner: ebis guide Revision Number: 29 Last Revision Date: November 20, 2015 Table of Contents Preface 9


Integration with CCW Quoting and Configuration Solutions



Download 1.42 Mb.
Page31/34
Date31.01.2017
Size1.42 Mb.
#13087
1   ...   26   27   28   29   30   31   32   33   34

24.Integration with CCW Quoting and Configuration Solutions


The following process flow steps explain the three basic integration flows with CCW Quoting and Configuration Solutions via Punchout.

a.Tier Partner Quoting and Ordering with a Deal Id – Punchout Flow


  1. Partner system receives the Cisco catalog (with Cisco products and services and associated List Price information) through a bootstrap with Cisco.

  1. Partner system engineer creates configuration in CCW UI.

25.Partner system engineer shares ConfigSet with the Cisco account manager.

26.Cisco account manager creates a Quote in CCW UI by importing the Shared ConfigSet.

27.Cisco account manager requests Non Standard discounts. The Quote is submitted for offline approval.

28. Upon approval, the system notifies the partner contact of the DealId.

29. Partner contact provides the Deal ID to the partner procurement user.

30. Partner procurement user punches in to CCW quoting and acquires the Shared DealId/Quote ID.

31.Partner procurement user transfers the Quote (With Config and Pricing Details) to their system.

32.Partner systems internal approval workflow kicks off.

33.Upon approval, procurement user adds order specific details to the configuration and submits a B2B 3A4 Order to Cisco. The order will include the Deal ID.

i.Tier Partner Quoting and Ordering with Deal ID (Quick Quote) – Punch Out Flow


  1. Partner system receives the Cisco catalog (with Cisco products and services and associated List Price information) through a bootstrap with Cisco.

34.Partner system engineer creates configuration in the CCW UI.

35.Partner system engineer shares ConfigSet with Partner Procurement team.

36.Partner procurement user punches in to CCW Quoting and starts Quick Quote flow.

37.Partner procurement user enters all partner and end customer details on the Quote and imports the BOM from the Shared ConfigSet.

38.Partner procurement user attaches service SKUs and after completing Quote info, submits the quote for approval.

39.The Quote is automatically approved. Partner system engineer transfers the Quote details to their system.

40.Partner systems internal approval workflow kicks off.

41.Upon approval, procurement user adds order specific details to the configuration and submits a B2B 3A4 XML Order to Cisco. The order will include the Deal ID.


i.Tier Partner Quoting and Ordering – Standalone Order (no Deal ID) – Punch Out Flow


  1. Partner system receives Cisco Catalog and pricing information through bootstrap with Cisco products and services along with List Price.

42.Partner system engineer creates configuration in CCW UI.

43.Partner system engineer shares ConfigSet with Partner Procurement team.

44.Partner procurement user punches in to CCW Quoting and initiates Quick Quote Creation Flow.

45.Partner procurement user creates quote with only End Customer Country details and imports BOM from the Shared ConfigSet.

46.Partner procurement user attaches service and system calculates Net Price per the partner’s contractual discount.

47.Partner procurement user transfers the configuration and pricing details to their system.

48.No Deal ID transfers to the partner system. Only configuration with Contractual Discount Net Price and other partner details transfer.

49.Partner procurement user submits B2B 3A4 order with this transferred information and after adding other order specific details.

Partners will utilize the Cisco quoting and configuration web services to create their quotes and configuration. Partners can punch out and access the Cisco Configuration UI via the Acquire Quote Web Service.

The output will be transferred via a TransferCart(TransferQuote) and Save to Disk to the partner systems.

The Deal ID, Line ID, Parent Line ID and CiscoProductReference and other information will be obtainable as part of the output from the services.

The following process flow diagrams describe the process leading to the creation of a 3A4 XML order.


a.Procurement User Creates a Purchase Order in Partner’s Internal System


Figure : Procurement User Creates a Purchase Order in Partner’s Internal System

Partner creates and acquires quote, deal, and configuration via the AcquireQuote or TransferQuote Web Service and then punches out to the Configurations Web Services.



Figure : Partner Creates and Acquires Quote, Deal, and Configuration via the AcquireQuote or TransferQuote Web Service and Punches Out to Configurations Web Services

Figure : Partner System Sends a 3A4 XML Order to NG00


i. Product References


To view a sample output from the TransferQuote WebService, please refer to Appendix B: Sample Output from TransferQuote WebService.

The LineId, Parent LineId, and CiscoProductReference fields are sent in the 3A4 XML proprietaryInformation/FreeFormText tag at line level as a semicolon separated name=value pair with the name as ConfigurationInformation, as in the example that follows.

Format - ConfigurationInformation=;
;|*
Example -

ConfigurationInformation=1.0;0; 716336378

With the introduction of CBOM WS – Configuration path (CP), selection flag (SF), redundancy flag (RF) and default flag (DF) values are sent at a line level for each of the lines on the configuration. These values can be sent on the order request, if or when the Cisco Product Reference is not available. These values (CP, SF, RF, DF) can be sent in the proprietary information field in the below format. Note these values can be preceded with CiscoProductReference in which case CiscoProductReference takes priority and CP, SF, RF and DF on the order requestare ignored, since system derives these values internally with the CiscoProductReferenceAppendix G provides more information in regards to Redundancy and default flags



ConfigurationInformation=;
;|*|
ConfigurationPath= “<>”; ;“<>”|*| RedundantFlag=SELECTED or REDUNDANT| DefaultFlag = Yes Or No

Sample:


ConfigurationInformation= ;
;|ConfigurationPath= “UNITY-MODEL:UNITY_USER_OPTIONS|UNITYU5-USR-DC”; “1”; “USER”|

Combinations samples of how the ConfigurationInformation can be sent –



        1. LineID;ParentLineId;CiscoProductReferenceCode

        2. LineID;CiscoProductReferenceCode

        3. With no ConfigrationInformation, in this case the system would always qualify this for Best guess logic

Note – Numerics are expected in Line ID and Parent Line ID (decimal numbers included). However a text string/alpha numeric string in line Id or parent line ID results in an error.

Note – Line Id and Parent Line ID are required on the PO for processing.


ii. Configuration Check


When a PO is sent to Cisco, Cisco re-validates the configuration. Sometimes, configurations may no longer be valid, even though they were created using Cisco Configuration Web Services. This can happen for older configurations, because configuration rules change over time. When configurations are rejected, partners should fix the configuration using the Cisco Configuration Web Services.

iii. Included Items


Included items are options that are automatically included in the Bill of Materials for a configurable part whether they were selected or not. A price of $0.00 must be sent for all items for which the Configuration tool displays a zero price.

Note: Some of these products may have a non-zero price in the catalog.


Download 1.42 Mb.

Share with your friends:
1   ...   26   27   28   29   30   31   32   33   34




The database is protected by copyright ©ininet.org 2024
send message

    Main page