Cisco Capital Pre-Owned Equipment is an ACT-approved initiative with the goal of integrating the selling and fulfillment of Cisco pre-owned equipment into Cisco standard processes and tools. The Cisco Capital Remarketing organization is responsible for the remanufacture, remarketing and resale of Cisco Certified Refurbished Equipment.
The selling and fulfillment of Pre-Owned Equipment was outsourced to a 3rd party vendor ModusLink until Q3 FY14 after which the Pre-sale and Ordering process was moved to Cisco Commerce Workspace. The fulfillment, returns pick pack and shipment is still done via Modus Link.
Enabling B2B ordering for refurbished equipment will reduce manual data entry for these partners who have previously submitted refurbished orders via fax or did manual data entry.
Partners must accept the RoHS Terms and Conditions while submitting the purchase order with refurbished SKU(s). If the terms and conditions are not accepted, system would reject the order.
Partner need to pass value “Y” or “N” in the new “RoHS_Terms” Key/Value Pair. If the purchase order has refurbished SKU(s) and value passed for this attribute is N or no value is passed for this attribute, then order will be rejected.
The table that follows indicates the optional nature of RoHS Terms and Conditions key/value pair. This fact is evidenced by a cardinality value of 0..1.
Table 64: PIP 3A4 V02.00.00 – ROHS Terms key/value pair for refurbished SKU(s)
No.
|
Card
|
PIP Element
|
Notes
|
Field Length
|
342
|
0..1
|
|-- proprietaryInformation.FreeFormText
|
Will be populated at Header level
"PurchaseOrder/proprietaryInformation/FreeFormText/RoHS_Terms" Key/Value Pair
Name: RoHS_Terms
Example:
RoHS_Terms =Y
OR
RoHS_Terms =N
|
1
|
|
|
|
j.Cisco Software Simplification - Smart Software Licensing
In order to have one standard software license platform across Cisco, Smart Licensing is being enabled via B2B as part of Q2FY15 release. Instead of using PAKs or License Files, Smart Licensing establishes a pool of Software Licenses or Entitlements that can be used across the entire customer in a flexible and automated manner. All Smart products will self-register themselves upon installation/configuration, removing the need for any manual intervention on the part of the installer. Licenses are not tied directly to specific installation. Smart Licenses can be managed in the Cisco Smart Software Manager.
With the proposed Q2 solution, Partners will have to Enable Smart Account/Virtual Account Assignment in B2B Orders.
Partners need to pass Holding Smart/Virtual Account and Customer Smart/Virtual Account in separate fields at the order header level & Customer Smart/Virtual Account at the order line level.
New optional attributes to capture Smart Account details
-
Header level Smart Account/Virtual Account information
-
Holding Smart Account Domain ID
-
Holding Virtual Account Name
-
Customer Smart Account Domain ID
-
Customer Virtual Account Name
-
Major Line level Smart Account/Virtual Account information
-
Customer Smart Account Domain ID
-
Customer Virtual Account Name
If the partner does not pass any Smart / Virtual account details in the purchase order request, the default Holding Account details set up for the partner in the user profile will be used while validating the purchase order request.
Refer to Appendix K for more details about the Smart & Virtual Accounts.
Manual Processing details in the event Smart/Holding Account is missing
-
B2B orders with Smart SKUs will be submitted as-is. There will be no way for a B2B user to enter Smart Account information at the time of placing the order.
-
B2B order will be booked and processed
-
A daily report will be sent to an internal SWSC team listing all B2B orders to date that require Smart Account assignment.
-
SWSC team will use CCW to create/assign a Smart Account to B2B orders.
Table 65: PIP 3A4 V02.00.00 – Header Level Smart Account key/value pair for Smart License SKUs
No.
|
Card
|
PIP Element
|
Notes
|
Field Length
|
342
|
0..1
|
|-- proprietaryInformation.FreeFormText
|
Holding Smart Account at Header Level
Will be populated at Header level "PurchaseOrder/proprietaryInformation/FreeFormText/HoldingSmartAccountDomainID" Key/Value Pair.
Example:
HoldingSmartAccountDomainID = IBM.com
|
255
|
342
|
0..1
|
|-- proprietaryInformation.FreeFormText
|
Holding Virtual Account Name at Header Level
Will be populated at Header level "PurchaseOrder/proprietaryInformation/FreeFormText/HoldingVirtualAccountName" Key/Value Pair.
Example:
HoldingVirtualAccountName = IBM.com Sales Dept
|
255
|
342
|
0..1
|
|-- proprietaryInformation.FreeFormText
|
Customer Smart Account at Header Level
Will be populated at Header level "PurchaseOrder/proprietaryInformation/FreeFormText/ CustomerSmartAccountDomainID " Key/Value Pair.
Example:
CustomerSmartAccountDomainID = BigU.edu
|
255
|
342
|
0..1
|
|-- proprietaryInformation.FreeFormText
|
Customer Virtual Account Name at Header Level
Will be populated at Header level "PurchaseOrder/proprietaryInformation/FreeFormText/ CustomerVirtualAccountName " Key/Value Pair.
Example:
CustomerVirtualAccountName = BigU.edu Physics Dept
|
255
|
Table 66: PIP 3A4 V02.00.00 – Line Level Customer Smart Account key/value pair for Smart License SKUs
No.
|
Card
|
PIP Element
|
Notes
|
Field Length
|
304
|
0..1
|
|-- proprietaryInformation.FreeFormText
|
Customer Smart Account at Line Level
Will be populated at line level at Line level "PurchaseOrder/ProductLineItem/proprietaryInformation/Freeformtext/CustomerSmartAccountDomainID" Key/Value Pair.
Example:
CustomerSmartAccountDomainID = BigU.edu
|
255
|
304
|
0..1
|
|-- proprietaryInformation.FreeFormText
|
Customer Virtual Account Name at Line Level
Will be populated at Line level "PurchaseOrder/ProductLineItem/proprietaryInformation/Freeformtext/CustomerVirtualAccountName" Key/Value Pair.
Example:
CustomerVirtualAccountName = BigU.edu Physics Dept
|
255
|
Share with your friends: |