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


Special Cisco Programs a.Channels Booking Neutrality



Download 1.42 Mb.
Page18/34
Date31.01.2017
Size1.42 Mb.
#13087
1   ...   14   15   16   17   18   19   20   21   ...   34

13.Special Cisco Programs

a.Channels Booking Neutrality


Channels Booking Neutrality (CBN) program ensures neutrality across the different Routes to Market. CBN orders are associated with Deal ID. They are identified with a “DVAD” identifier in the Billing address field. To qualify for a CBN discount the order must exceed the threshold check of $100K.

Identification of a CBN order is done by looking for existence of "DVAD" in the Billing Address (Address Line 1, Address Line 2, and Address line 3) corresponding to the BID for a given order.

CBN Orders can be placed by Distributors only. Intended Use should be 'Resale' and a Deal ID must be present on the CBN order.

b.Managed Services Channels Program (MSCP)


Managed Service Channels Program (MSCP) is a type of contractual discount. When a partner is eligible for MSCP discounts, the greater of the contractual or MSCP discount is applied.

A partner is identified as a valid Managed Service partner only if the Authorization Code provided is one of the following:

MSCP

LI

L2



L3

The GlobalPurchaseOrderTypeCode for these orders should be set to “Consigned order”. This is a change from sending “Services” in this field as in Legacy.


c.United States Government Orders


When placing orders for the United States government, customers can set VerticalMarket=Federal Government and/or specify the DPAS priority code. A US government Disti stocking order with DPAS value as DX, DO, TAA-DX, or TAA-DO will be processed with a warning to reflect that stocking orders cannot have preferential indicators.

This order must be shipping to a US address and a contact email address must be provided.

A US government order cannot be a Try and Buy or an eRate order. Cisco will reject those orders.

If a CTMP code is provided along with a DPAS code, Cisco will accept this as a Trade-in order instead of a US government order.

Partners cannot order only service lines in a US government order. If there is no Cisco product in this order, Cisco will accept it as a standard order and drop the DPAS value.

i.Government Eligibility Check


Eligibility to place government orders is based on the billing country. All US government orders must have a billing country of US.

A PO is rejected if the Billing country is not US or a Contact email address is missing on the order.

The table that follows indicates the optional nature of the Government Eligibility Check element. This fact is evidenced by a cardinality value of 0..1,

Table 33: PIP 3A4 Version 02.00.00 - Government Check Eligibility

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: DPAS
Example: DPAS=TAA

CHAR(8)

ii.Trade Agreement Act (TAA) Orders


TAA orders are identified by one of the following header level DPAS rating values:

TAA


TAA-DX

TAA-DO


Additionally, the line level PartnerTAA flag should be used by partners to indicate if the major line item being ordered is TAA compliant. If a mismatch exists between the header and line level TAA flags on an order, that is, the DPAS rating value is a TAA compliant one, but the line level TAA flag is “N”, the partners will receive an email message indicating the mismatch.

Validations:

For partners submitting government orders without the intention that the order be TAA compliant, but have their line items on the request specified as TAA compliant, line item values are ignored while fulfilling the order.

For partners submitting government orders with the intention that the order be TAA compliant:

If at line level none of the lines are specified as TAA compliant, the order is rejected.

If at line level there is a mixture of TAA compliant lines and some lines that are non TAA compliant, a warning is raised to that effect.

If SKU at line level is specified as non-TAA compliant, however the SKU can only be fulfilled as TAA compliant and there is no exception process to fulfill this SKU, then the partner can expect such SKUs as TAA compliant in response.

If SKU at line level is specified as non-TAA compliant, however the SKU can be TAA compliant and there is a exception process to fulfill this SKU, then the partner can expect such SKUs as non-TAA compliant in the response.

Government TAB orders with preferential indicators (TAA-DX, TAA-DO, Dx, DO) will result in warnings and these values are ignored.

Government TAB orders can be requested as TAA compliant.

The optional nature of the TAA order is indicated by a cardinality value of 0..1 in the table that follows.

Table 4: PIP 3A4 Version 02.00.00 for TAA Orders



No.

Card

PIP Element

Notes

Field Length

304

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: PartnerTAA
Example: PartnerTAA=”Y”

CHAR(8)


Note: TAA+ SKU’s can be ordered on Federal orders where partners have indicated that order should be TAA compliant itself. Else orders are rejected.


Download 1.42 Mb.

Share with your friends:
1   ...   14   15   16   17   18   19   20   21   ...   34




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

    Main page