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

q.Product Line Reference

Line ID and Parent Line ID will be used in the configuration information tag as specified in Section 10.2. 1, Product References.

Additionally, to indicate the hierarchy and service linkage information, partners have to send in the Line ID and Parent Line ID obtained via Cisco Web Services as part of the ConfigurationInfo tag.

The use of ServiceFor (Element #304) tag has been discontinued. Partners will have to send Line ID and Parent Line ID to indicate the service linkage.

Section 10.2. 1, Product References on the same PO provides details on how the Line ID and Parent Line ID should be provided on the order.

12.Order Product

a.Product Number

Configurable

Non configurable (for example, spares and software upgrades)

Included sub items by Enterprise product SKUs

New services for serviceable Cisco products by Enterprise service SKUs

If partners do not provide a valid Cisco part number, the order is rejected.

Note – As of March 2014, Cisco is enabling configuring, quoting and ordering of pre-owned equipment in CCW UI, such SKU’s are not supported via B2B ordering mechanism.,

b.Configurable Products

The hierarchy of major and minor lines should be indicated by partners via the ConfigurationInformation. Section 5.5, Service for Products on the Same PO Number on the same PO order provides details on how the Line ID and Parent Line ID should be configured on the order.

Products can be configured using the CCW Configuration UI. Only minors displayed by the Cisco Configuration UI are valid minors. If partners need to order additional minor options that do not fit into the major (for example, chassis) configurable line, then these additional minor options need to be placed on a separate line as a spare item.

Cisco validates every configurable product in a PO. Cisco will reject orders with invalid configuration(s) and return configuration error details.

The following scenarios are examples of invalid configurations:

Missing major line in a configuration - A PO contains minor lines; a PO does not contain a major line number. This configuration is not valid because minor lines are provided without providing the parent line. Order is rejected.

Non-service part is entered as a minor of a service part - For example, take an order with major line as CON-SNT-2501 (a service part) and the minor line number is CAB-ACE (a power cable). A hardware part cannot be entered as a minor of a service part.

Minor entered for a spare - For example, take an order where the major line number is CAB-ACE= (cable), and the minor line is MEM-XP-1 (memory). This is not valid because a memory cannot be a minor of a spare cable.

A minor that is no longer a member of a major product’s Bill of Materials – In this case, a product’s Bill of Materials may change before submission of the order. For example, software may become obsolete and removed from the Bill of Materials. Please validate the configurations using a Cisco configuration tool or web service before submitting an order.

If a product is configured in a significant time period before an order is placed, it is likely that the production configuration has been updated and is causing configuration validation failure.

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

i.Included Sub-Products

Partners are not required to include zero price items of a configuration in the PO. Cisco will automatically insert zero price items into a configuration in the PO (see Section 7.1, Zero Pricing).

ii.Service Products

This requirement is indicated by a cardinality value of 1 in the No. 209 row of the table that follows.

Table : PIP 3A4 Version 02.00.00 – Service Products

No.	Cardinality	PIP Element	Notes	Field Length
205	1	| |--ProductIdentification	Required tag	N/A
207	0..n	| | |--PartnerProductIdentification	Required tag	N/A
208	1	| | | |--GlobalPartnerClassificationCode	Any valid RN value. On the PO response back, “Manufacturer” would be sent back.	N/A
209	1	| | | |--ProprietaryProductIdentifier	Cisco part number Example: “Cisco2501” “CAB-AC” “CON-SNTE-2501”	CHAR(50)

Note – The valid Rn values for GlobalPartnerClassificationCode are - PurchaseOrder.ProductLineItem.ProductIdentification.PartnerProductIdentification.GlobalPartnerClassificationCode. However, the valid RN values that can be sent in this field are "Manufacturer", "End User", "Reseller", "Retailer", "Broker", "Carrier", "Shopper", "Financier", "Warehouser", “Distributor”, “Customs Broker”, “Freight Forwarder”, “Distribution Center”, “End User Government”, “Contract Manufacturer”, “Forecast Reply Recipient”, “Original Equipment Manufacturer”. Any other Invalid values will result in failure of order submission at gateway.

Also, in case of multiple blocks of PartnerProductIdentification, the first available block with GlobalPartnerClassificationCode = “Manufacturer” is used to map SKU/kitRef from the corresponding ProprietaryProductIdentifier. If there are no blocks with GlobalPartnerClassificationCode= “Manufacturer, then the first block’s ProprietaryProductIdentifier is used to map the SKU/kitRef being ordered

iii.FULFILLMENT RESTRICTIONS on SKUs

iv.Meraki SKUs

• 
  For Meraki SKU lines, the end customer addresses and contact – email and phone, shipTo addresses and contact – email and phone, and billTo address and contact – email and phone, are required fields. Not providing this information on a PO results in a delay in processing the PO, if current addresses defaulting rules are unable to derive these addresses and contacts systematically.
  
• 
  Enabled Only for 1Tier Partners, Direct & Disti Drop ship . Disti Stocking will not be supported and Meraki SKUs will not be published on WPL.
  
• 
  There is no Service/Subscription attached to Meraki Products
  
• 
  Requested Ship date would continue to be mandatory for all the Shipping group including Shipping group that has Meraki Products , but Meraki will NOT be honoring the requested ship date, will be fulfilled on an ASAP basis.
  
• 
  Enterprise and Advanced Security Meraki licenses are not allowed on the same purchase order. Any such purchase orders having both Enterprise and Advanced Security Meraki licenses will be rejected. The Enterprise Meraki licenses and the Advanced Security Meraki licenses have to be placed in separate purchase orders.