h.Config Check
If the configuration of the ordered Cisco product is invalid, the PO is rejected by Cisco.
i.All or Nothing Rule
When ordering configurations with both products and services, partners should either:
Include orders for all applicable services for the product configuration on the same order
Not order any of the applicable services
Splitting of service orders for products within the same configuration is not allowed.
The following is a description of the goal of the “All or Nothing rule” for Technical Services in the CCW Program:
Not allowing for “Partial Service” purchase in CCW
Irrespective of who is selling the service, Cisco wants to sell service on most (if not all) of the lines. Business rules will check for both Technical Support and Application Software on lines. When there is service on any line, all lines are required to have service.
j.Sample Orders
As of September 2011, Sample Orders are rejected with the error message: “Order type is not handled in NextGen Order management.” if the value in PIP Element#342: proprietaryInformation.FreeFormText CiscoProgram=Version Sample
k.Deal ID Validations
A Deal ID is a Cisco identification code used by Cisco’s Sales Department to identify sales quote(s) that give partners special pricing. One or multiple quotes can belong to a Deal ID.
Partners can supply a Deal ID for a PO in the PurchaseOrder.DocumentReference. ProprietaryDocumentIdentifier with the PurchaseOrder.DocumentReference. GlobalDocumentReferenceTypeCode = “Contract”.
Note: A Deal ID ties an acquired discount (above and beyond a contractual discount) to a Sales Deal. The order rejects if the Deal ID is deemed invalid.
Table : PIP 3A4 V02.00.00 – Deal ID Validations
No.
|
Cardinality
|
PIP Element
|
Notes
|
Field Length
|
74
|
0..n
|
|-- DocumentReference
|
|
Tag
|
75
|
0..1
|
| |-- DateTimeStamp
|
Not used
|
|
76
|
1
|
| |-- GlobalDocumentReferenceTypeCode
|
Send the value “Contract”.
|
RosettaNet value
|
77
|
1
|
| |-- ProprietaryDocumentIdentifier
|
Deal ID (must be a numeric value)
|
CHAR(50)
|
The list of Deal ID validations are as listed in the table below
Table 32: Deal ID Validations
Scenario
|
Result
|
Status of deal is not “Approved” or “Ordered”
|
Order is rejected
|
Unrecognized deal ID on PO
|
Order is rejected
|
Intended Use derived from PO different than Intended use on Deal
|
Order Processing delayed
|
Pricelist mismatch on RNSD deal and order
|
Order is rejected except for GLUS and GLOBAL pricelist’s
|
Pricelist mismatch on other deals and order
|
Order Processing delayed
|
End User mismatch on deal and order
|
Order Processing delayed
|
Partner mismatch on deal and order
|
Order Processing delayed
|
Deal ID's try and buy enrollment check failed or not complete
|
Order Processing delayed
|
Unrecognized Try and Buy Deal on Try and Buy PO
|
Order is rejected
|
The total extended net price on the Order is less than the CBN Threshold.
|
Order Processing delayed
|
Invalid deal – Deal ID greater than 50 characters or Alphanumeric (other than “NA” or “N/A”) deal ID
|
Order is rejected. If deal ID is “NA” or “N/A”, system will ignore this value and treat this as a standalone order. Order pricing would be done at user’s contractual price.
|
“Global” RNSD deal ID on PO
|
Order is rejected. User can submit PO with only “Local” RNSD deal ID.
Currently order is rejected if the PO is submitted “Global” RNSD deal ID created post Q3 release (03/09/2014). User can continue to submit PO with “Global” RNSD deal ID which are created prior to 03/09/2014 until further communication.
|
Share with your friends: |