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



Download 1.42 Mb.
Page1/34
Date31.01.2017
Size1.42 Mb.
#13087
  1   2   3   4   5   6   7   8   9   ...   34


cisco_logo_blue-green tritone gradient5



Implementation Guidelines

Message Type: XML

RosettaNet PIP 3A4: Submit Purchase Order

V02.00.00



Owner: EBIS

Guide Revision Number: 29

Last Revision Date: November 20, 2015


Table of Contents

Preface 9

1.Provide a kitReference Indicator flag on the product line item with valid value to indicate that a Kit Ref ID/Name is being used. 21

1.Provide the valid ConfigSet ID/Name as the Cisco part number (in the Proprietary Product Identifier field) to be ordered. 21

1.Introduction 30

a.Overview 31

b.Audience 32

c.Scope 33

d.Prerequisites 34

2.Purchase Order Request: Process 35

1.The partner creates a PIP 3A4 PO Request in their purchasing system. 35

3.The partner submits the PO Request to Cisco via their XML gateway. 35

4.The Cisco XML gateway receives and acknowledges the PO Request. 35

5.The partner receives the PO Request via their XML gateway. 35

6.Cisco validates and processes the PO Request. 35

7.Cisco sends a PIP 3A4 PO Confirmation to the partner via Cisco XML gateway. 35

8.The partner receives the PO Confirmation via their XML gateway. 35

9.The partner processes the PO Confirmation. 35

10.Message Guideline (PIP 3A4 V02.00.00) 37

a.Guideline Annotations 38

b.Service Header Part Message Guideline 39

i.Service Header Guideline for RNIF 1.1, RNIF 2.0 40

11.Functionality 43

a.Participant Information 44

b.Document Function Code 45

c.Order Routing 46

d.Purchase Order Number 47

e.Duplicate PO Number Check 48

f.Purchase Order Type 49

g.Purchase Order Billing Information 51

h.Financing Terms 53

i.Order Shipping Information 54

i.Request Ship Date 55

ii.Shipping Address 56

j.Shipment Logistics 61

i. Shipment Terms Values in 3A4 62

k.Shipment Routing Configuration Tool 66

l.Shipping and Packaging Notes 68

m. Ship Set Number 69

n.End User / Install Site 70

i. Guidelines 71

ii.End Customer Notes 73

o.End User Vertical Market 74

p.Product Line Number and Quantity 75

q.Product Line Reference 76

12.Order Product 77

a.Product Number 78

b.Configurable Products 79

c.Non-Configurable (Spare and Software Upgrades) Products 80

i.Included Sub-Products 81

ii.Service Products 82

iii.FULFILLMENT RESTRICTIONS on SKUs 83

iv.Meraki SKUs 84

d.Service Ordering – Product Link 85

e.Service for Products on the Same PO 86

f.Service Ordering for Product(s) at Partner Site 88

g.Service Ordering 90

i.Service Contract Information 91

ii.Primary and Secondary Services (Technical) 93

iii.Reseller Information 94

h.Config Check 95

i.All or Nothing Rule 96

j.Sample Orders 97

k.Deal ID Validations 98

13.Special Cisco Programs 100

a.Channels Booking Neutrality 101

b.Managed Services Channels Program (MSCP) 102

c.United States Government Orders 103

i.Government Eligibility Check 104

ii.Trade Agreement Act (TAA) Orders 105

d.Try and Buy (TAB) Program 106

e.Trade-In Migration Orders 107

f.eRate Orders 108

g.Promotional Orders 109

h.Advanced Services Fixed (AS-Fixed) Ordering 110

i.UCSS and Term and Content Subscription Services Ordering 111

j.Co-Terming 112

1.Calculate Service Duration in years. 112

k.ServiceDuration = (EndDate – StartDate + 1 – LeapDay)/365 112

l.LeapDay = Number of times Feb 29 falls between StartDate and EndDate 112

14.Find out SPA Duration Quantity for the line service level 112

a.DurationQty = 1 if Price in Price list is for 1 year 112

b.DurationQty = 2 if Price in pricelist is for 2 years and so on 112

15.Calculate Duration Factor 112

a.DurationFactor = ServiceDuration/DurationQty 112



16.Divide Price List List Price by Duration Factor to find prorated List Price 112

a.ListPrice = PriceListListPrice x DurationFactor 112



17.Round List Price using transaction currency rounding rules 112

a.If Transaction currency is JPY or KRW, round to 0 decimals 112



b.For all other currencies (USD/EUR/GBP, etc., round to two decimal places) 112

c.Donation Orders 113

d.Country Enablement - Brazil 114

18.Special Cisco Ordering Functions 116

a.Zero Pricing 117

b.DotX and getLatest Function 118

c.KitRef 119

1.Provide a kitReference Indicator flag on the product line item with valid value to indicate that a Kit Ref ID/Name is being used. 119

19.Provide the valid Estimate ID/Name as the Cisco part number (in the Proprietary Product Identifier field) to be ordered. 119

1.A Estimate, previously validated and created, has to be provided on the ProductIdentifier tag. If the partner uses an invalid Estimate ID/Name as the KitRef product, the order rejects. 119

20.Each such kitReference line should have a kitReference indicator (kitRefId/kitRefName). If not, the line is treated as a SKU line and would result in an Unknown SKU error. 119

21.Only valid value for each of the kitReference indicators (kitRefId/KitRefName) is "Y". Any other value will result in an order reject scenario. In case of a line not being a kitReference line, kitReference Indicator name value pairs are not expected on the request. 119

a.ConfigRef 121

b.Email Order Acknowledgments 124

c.Order Contacts 125

d.Order Reference 126

e.Order Processing Notes 127

f.Order Notes 128

System checks if the string “OrderNotes=” is present. If yes, then system will consider text after the string as Order Notes and text before the string as Order Processing notes 128

g.SWIFT and eDelivery Products 129

h.Flexible Service Start Delay (FSSD) 130

i.Cisco Capital Pre-Owned Equipment Orders 131

j.Cisco Software Simplification - Smart Software Licensing 132

k.Ultimate Consignee Address and Consignee Type 134

l.Co-term of Initial Purchase SWSS Technical Service 137

22.Product and Order Price 139

a.Currency Code 140

b.Price List Identifier 141

c.Product Price 142

d.PO Amount 143

23.Tax Exemption 144

a.Tax Exempt Status 145

i.Canadian Orders 146

ii.Australian Orders 147

iii.US Orders 148

b.Taxability Derivation 149

24.Integration with CCW Quoting and Configuration Solutions 150

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

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

1.Partner system engineer creates configuration in CCW UI. 151

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

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

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

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

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

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

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

32.Partner systems internal approval workflow kicks off. 151

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. 151

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

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

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

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

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

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

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

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

40.Partner systems internal approval workflow kicks off. 152

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. 152

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

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

42.Partner system engineer creates configuration in CCW UI. 153

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

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

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

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

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

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

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

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

i. Product References 156

ii. Configuration Check 157

iii. Included Items 158

50. Purchase Order Confirmation 159

51. Order Acknowledgement Email 163

a.Accept Scenarios 164

b.Reject Scenarios 165


Tables


Figures

Revision History

Rev No.

Revision

Date


Description

Reason for Change

Revised By

01

09/30/2011

Initiate CCW Implementation Guide

Sept 2011

Purna Sharma

02

11/10/2011

Added Glossary of Terms, Summary of Changes,

and details surrounding the enablement of the newer business models and integration with CCW via Acquire/Transfer Quote WebService.



Internal review

Bindu Thomas

03

11/14/2011

Incorporated feedback from additional internal review

Internal review

Bindu Thomas

04

11/22/2011

Modifications after review by PS team

PS team review

Bindu Thomas

05

11/28/2011

Adding clarifications surrounding line numbering

PS team review

Bindu Thomas

06

12/01/2011

Modifications to include March 2012 Service Only, AS-Fixed, UCSS and Term and Content ordering

December 2011

Bindu Thomas

07

02/13/2012

Modified to include clarification about Disti Resale Kit Ref Orders with Service Lines

Functionality clarification

Bindu Thomas

08

02/27/2012

Clarifications surrounding Service Only ordering

March 2012

Bindu Thomas

09

03/28/2012

Revisions based on feedback during review with support team and PSPM team.

Added TAA related changes



Review

Bindu Thomas

10

07/27/2012

Revisions based on feedback

Zero price logic valid countries is not limited to 4 countries

Shreyas Manjunath

11

07/27/2012

Revisions to the error messages table based on feedback on Deal validation error messages




Shreyas Manjunath

12

08/27/2012

Taxability updates

CR December 2012- Taxability verbiage changes and updates

Shreyas Manjunath

13

07/27/2012

Updates PDP values, changes to proprietary information text for Configuration Path, Landing Cost SKUs

Sept 2012

Shreyas Manjunath

14

08/28/2012

Intended Business Use table refreshed to reflect the current derivation rules

Document updated

Shreyas Manjunath

15

09/28/2012

DotX productID value start with a “S”

DotX product IDs do not start with “FR” and “FL”. Document updated.

Shreyas Manjunath

16

11/20/2012

September 2012 Release

December 2012

Shreyas Manjunath

17

12/17/2012

September 2012 Release

December 2012

Shreyas Manjunath

18

02/19/2013

and


03/04/2013

Documentation update

and


March 2013

Restructured focus to technical and business audience

and


March 2013

Laura Stearns

and


Shreyas Manjunath

19

09/25/2013

Documentation Update

Deal Validation Error message updates/Format update for Deal ID value

Analyst Team

20

01/21/2014

Documentation Update

Added Q3FY14 and MR changes

Analyst Team

21

02/13/2014

Documentation Update

Removed the sample error message table as it was redundant

Sanoj Shivashankaran

22

02/13/2014

Documentation Update

Update CE Brazil Product & service ordering business rules

Update Contract Start date for Initial purchase of services



Sanoj Shivashankaran/Tazin Nahid

23

03/20/2014

Documentation Update

Updated Fulfillment Restriction Options for B2B XML & EDI ordering

Sanoj Shivashankaran

24

04/01/2014

Documentation Update

Updated Global RNSD validation

Sanoj Shivashankaran

25

04/16/2014

Documentation Update

Updated FSSD Validation section for additional order reject scenario

Naveen Garg

26

05/15/2014

Documentation Update

Q4FY14 – CR72 :Technical Service duration accepts up to 60 months

Sanoj Shivashankaran

27

08/09/2014

Documentation Update

Added guidelines for Q2FY15 changes

1) Smart Software Licensing

2) Ultimate Consignee

3) eDeliveryemail address

4) Refurbished / Pre-owned SKUs


Sanoj Shivashankaran

28

08/04/2015

Documentation Update

Added guidelines for Q4Fy15 scope changes:

  1. Co-term of Initial Purchase SWSS Technical Service (End date Alignment for Technical Services)

Updated


  1. “RoHS_Terms” name value pair for Refurbished / Pre-owned SKUs

  2. Meraki Ordering validation changes

Sanoj Shivashankaran

29

11/20/2015

Documentation Update

Added guidelines for Q2FY15 scope changes:

  1. Contract number.

  2. Global Transportation event code.

Updated:

  1. Contract number value ‘New’ or ‘Use-Existing’ to be derived from profiles and preferences if set up when not sent in PO.

b) Global Transportation event code updated to accept additional LOVs’- ‘Dock’ & ‘Pick-up’.


Venkat Maddukuri


Preface

Submit Purchase Order is a process by which Cisco partners may submit purchase orders via B2B interchange. The partner creates the PIP 3A4 Request in their purchasing system, then submits that request to Cisco via an XML Gateway. Cisco processes the request and then sends a PIP 3A4 Confirmation to the partner. The partner processes the PO Confirmation.

In addition to purchase ordering, solutions are available for processes such as preparing and managing configurations, quoting, and invoicing. B2B integrations help partners to:

Work in their own systems

Improve productivity

Lower costs and cycle time

Obtain critical and accurate business information faster and easier

Perform real-time business processing between the partner’s system and Cisco




Download 1.42 Mb.

Share with your friends:
  1   2   3   4   5   6   7   8   9   ...   34




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

    Main page