Table : BLOCK SKUs
-
PID
|
Fulfillment Restriction
|
UCSC-DBUN-C200-102
|
BLOCK
|
R200-BUN-3
|
BLOCK
|
UCSC-DBUN-C200-101
|
BLOCK
|
UCSC-DBUN-C200-116
|
BLOCK
|
R200-BUN-1
|
BLOCK
|
UCSC-DBUN-C200-115
|
BLOCK
|
UCSC-DBUN-C210-105
|
BLOCK
|
R210-BUN-4
|
BLOCK
|
UCSC-DBUN-C210-103
|
BLOCK
|
UCSC-DBUN-C210-104
|
BLOCK
|
UCSC-DBUN-C210-117
|
BLOCK
|
UCSC-DBUN-C210-118
|
BLOCK
|
R210-BUN-1
|
BLOCK
|
UCSC-DBUN-C210-119
|
BLOCK
|
R200-BUN-2
|
BLOCK
|
R200-BUN-4
|
BLOCK
|
R210-BUN-2
|
BLOCK
|
R210-BUN-3
|
BLOCK
|
R210-BUN-5
|
BLOCK
|
R460-BUN-1
|
BLOCK
|
R460-BUN-2
|
BLOCK
|
R460-BUN-3
|
BLOCK
|
R210-STAND-CNFGW
|
BLOCK
|
R200-STAND-CNFGW
|
BLOCK
|
R210-CNFG1-N
|
BLOCK
|
R210-SASXP-CNFGW
|
BLOCK
|
R250-BUN-1
|
BLOCK
|
R250-BUN-2
|
BLOCK
|
R250-STND-CNFGW
|
BLOCK
|
R250-STND-CNFGW-2
|
BLOCK
|
R250-PERF-CNFGW
|
BLOCK
|
R250-PERF-CNFGW-2
|
BLOCK
|
R250-CNFG1-N
|
BLOCK
|
R250-STND-BUNDLE
|
BLOCK
|
R250-STND-BUNDLE-2
|
BLOCK
|
UCSB-DBUN-B200-102
|
BLOCK
|
UCSB-DBUN-B200-103
|
BLOCK
|
UCSB-DBUN-B200-101
|
BLOCK
|
UCSB-DBUN-B230-106
|
BLOCK
|
UCSB-DBUN-B230-107
|
BLOCK
|
UCSB-DBUN-B230-108
|
BLOCK
|
UCSB-DBUN-B250-104
|
BLOCK
|
UCSB-DBUN-B250-105
|
BLOCK
|
B200M2-BUN1
|
BLOCK
|
B200M2-BUN2
|
BLOCK
|
B200M2-BUN3
|
BLOCK
|
B200M2-BUN4
|
BLOCK
|
B200M2-BUN5
|
BLOCK
|
B200M2-BUN6
|
BLOCK
|
B200M2-BUN7
|
BLOCK
|
B250M2-BUN1
|
BLOCK
|
B250M2-BUN2
|
BLOCK
|
B440M1-BUN1
|
BLOCK
|
Redundancy and Default attributes
Redundancy & Default are key attributes in Config/Quoting/Estimate/Order process and will impact partner/subscriber systems if not maintained on configuration.
Redundancy indicates primary and redundant items in a configuration. When missing, configuration can be validated but may fail while editing configuration on CCW Portal or in CORE services.
Without a default flag, a valid configuration may become invalid due to instance mismatch.
Redundancy and Default attributes do not exist in legacy systems. These are new attributes in CCW. In order to enable partners to order valid configurations with redundant and default items, the following was changed –
-
Use the suffix in the Cisco Product Hash Code to denote the different possible combinations.
-
Cisco Product Reference is sent back to partners on the configuration XML output and hence can be sent on the order request.
-
If Cisco Product Reference is on the order request, it takes precedence over any CP, SF, RF or DF values sent. System derives these values internally.
-
Partners also have the ability to send CP, SF, RF and DF flags at line level (format described in section 10.2.1). However in case of invalid values for redundancy and/or default flags on the request, these values are ignored and not processed further.
-
In case of having (a) or (b) BGL will not be triggered.
Accepted Diacritics
System accepts a list of diacritics and processes the order as listed below –
List of Operating Units
Products and Service ordering business rules for Cisco Brazil entity
Product Ordering controls
-
All locally manufactured products can only be sold by Cisco Brazil entity
-
All non-locally manufactured products can be sold by Cisco Inc entity only and no other business operating units can sell into Brazil.
-
For all preset product configurations sold by Cisco Brazil entity, the equivalent product configurations should not be sold by Cisco Inc entity into Brazil.
-
All software and software subscriptions (excluding embedded software) will be sold by Cisco Inc entity.
Service Ordering controls
-
All Standalone TS and AS(AS-T, AS-F & AS-S) with install site as Brazil can only be sold by Cisco Brazil entity
-
Attached Technical services to Non-Locally manufactured product can be sold by Cisco Inc entity
Product Mfg
|
Service Type
|
Attached with Product
|
Cisco Brazil or Cisco Inc
|
Locally Mfg (Embedded SW)
|
TS
|
Y
|
Cisco Brazil
|
Non locally Mfg (Embedded SW)
|
TS
|
Y
|
Cisco Inc
|
Non locally Mfg or Locally Mfg
|
TS (standalone M lines)
|
N
|
Cisco Brazil
|
Advance Services.
|
AS-Fixed (product in CCW)
|
NA
|
Cisco Brazil
|
SW (e-delivery products)
|
NA
|
NA
|
Cisco Inc
|
SW Subscription Sales
|
NA
|
Y
|
Cisco Inc
|
SW Subscription Sales
|
NA
|
N
|
Cisco Inc
|
Smart Software Licensing
What is Smart Account?
-
A Smart Account is an account created by the customer or partner, and it is where Smart Licenses are deposited.
-
The unique identifier of the Smart Account is referred to as the “Account Domain Identifier”.
Example: “BigU.edu” or “IBM.com”
-
A Smart Account must be assigned to Provisioning Enabled items on an order prior to submitting an order in CCW.
-
There are two types of Smart Accounts:
-
Smart Licenses can temporarily be stored in a Holding Account, but they cannot be activated until they are placed in an End Customer’s Smart Account.
-
There cannot be a combination of Holding Account and End Customer Account on an order.
What is Virtual Account?
-
Virtual Account is a subset of a smart account
-
A Smart Account can have one or more Virtual Accounts. Virtual Accounts fall under Smart Accounts and will be used by customers to internally organize licenses. (ex. “BigU.edu, Physics Department” or “BigU.edu, Engineering Department”)
-
When a Smart Account is created, a corresponding, default Virtual Account is automatically created at the same time.
-
Used by customers internally to organize licenses.
Example:
Customer Smart Account = BigU.edu (Umbrella account)
Virtual Account = BigU.edu Physics Dept (Department specific account)
Share with your friends: |