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

18.Special Cisco Ordering Functions

a.Zero Pricing

Although partners do not need to include zero-priced sub-items when placing an order, they still need to provide chargeable minor items as part of the configuration.

Partners can specify either the country to default the zero-priced item, for example, an Australian power cable. Not all configurable products are zero priced, so please read the error messages if orders fail. Valid country codes include: US, GB, JP, AU, etc.

The country specific zero priced items are listed in the acceptance/confirmation with the PO line reference = Z prefixed with the major line number. Since there is RN limitation on the number of characters allowed in a PO Line ref (6 characters), any prefixes of “Z” which would result in length of PO line ref greater than 6 characters, will be truncated.

The table that follows indicates the optional nature of participation in zero pricing. This fact is evidenced by a cardinality value of 0..1.

Table 46: PIP 3A4 Version 02.00.00 for Zero Pricing

No.	Cardinality	PIP Element	Notes	Field Length
342	0..1	|-- proprietaryInformation.FreeFormText	Used to send multiple Cisco proprietary information in = format. Use ‘|’ as a delimiter for multiple values, and no whitespace should exist around equal sign. Name: ZeroPriceCountry Example: ZeroPriceCountry=JP

b.DotX and getLatest Function

Based on the product ID naming convention, use of this functionality may differ.

The Product ID starts with “S” and

There is at least one hyphen ‘-‘ in the product number and

The last (1^st from right side) hyphen in the product number is immediately followed by ‘N.N.N’, where N can be any number.

In this case, the partner indicates that he requires the latest version of these products by replacing the last number with ’x’

For example:

• 
  Submit ‘S16RC-12.0.x’ to receive the latest version of S16RC-12.0.22
  

The Product ID for DotX starts with “S” and

There is at least one hyphen “-“ in the product number and

The first hyphen in the product number is immediately followed by three digits

In this case, the partner indicates that she requires the latest version of these products by replacing the numeric character(s) from fourth character after hyphen (hyphen is position zero) with an “x”.

For example:

• 
  Submit S16RB-121x to receive the latest version of S16RB-12108
  
• 
  Submit S16RB-121xT   to receive the latest version of   S16RB-12105T
  

SKU Name Wildcard Format	is DotX or not
*-NN-NNNx*	Yes
*-N.N.x*	Yes
*-NN.x*	Not
*-NNN.x*	Not
*-N.N.N.x*	Not
*-N.Nx*	No
*-NNNx*	Yes

c.KitRef

One-to-one part maps (cross reference)

One-to-many part maps (kit reference)

Before placing an order with the KitRef function, partners should create an Estimate using the Estimate UI and name it with a Partner product number, then:

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.
   

System does the following with these orders:

Retrieves the Estimate associated with the kit reference (s) along with the line item price and line item quantity

Adjusts the retrieved quantity at line level in reference to the specified kit Quantity

Reads and validates and deal provided on the order request

Validations on KitReference

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.
   

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.

Each kitReference line should have the monetaryAmount set to indicate the Net KitAmount. These amounts will be validated at the kitLevel and also that total order level. If there is no discrepancy on the system calculated price and the price on the purchase order (estimate price) then the order is autobooked and no warnings/tasks are raised.

The Cisco product line item(s) from the Estimate is returned in the response/PO confirmation message, along with the line item net prices. Response will not include kitAmounts provided on the order, but will include the net price of each of the expanded line items of each of the kitReferences. Warnings/errors at line level will be back for each of the line items associated with the Kit.

Response will include the same PO line references as on the request for each of the expanded line items associated with the kit.

Known limitations on kit references:

ConfigRef and KitRef cannot be used together in a PO.

Disti Resale Kit Ref Orders with Service Lines will return a warning about a missing service contract (reseller BID).

Partners cannot provide the Partner’s part number in the Proprietary Product Identifier element.

Mixed KitReference order (order with kitReferences as well as SKU lines)is not supported.

ZPL is not supported on kitRef orders and hence ZPL Country name value pair is not expected on kitRef orders

The table that follows indicates the mandatory nature of providing Kit Ref. This fact is evidenced by a cardinality value of 1 in the first table that follows.