In CCW, Co-terming functionality is currently supported for Software Content Subscriptions (T&C) at point of sale and renewals. Some of the partners need a capability to co-term the service purchase of Technical Services during initial purchase, and align the service end date to an existing Service Contract. Currently partners pass the duration for the Technical Services during initial purchase.
With the roll out the SWSS (Software Support Service) End Date Alignment scope in Q4Fy15 Release, Partner would have the capability to pass Start Date + End Date or Start Date + Duration combination for Initial Purchase Technical Services (certain End Date Alignment Eligible services) along with the existing option of passing only the Duration. For the initial release, selective SWSS GSPs will be qualified for “End Date alignment”. This should be extendable to additional services (future release). Eligible Services for P-line End Date alignment will be identified by a SPA/Item attribute “userSpecifiedStartDate” (values are “Y” or “N”).
Table 69: PIP 3A4 Version 02.00.00 – Service Start date, Service End date and Service Duration
No.
|
Cardinality
|
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. Values are:
Name: ContractDuration
Name: ContractNumber
Name: ContractStartDate
Name: ContractEndDate
Example: Order Service with existing contract
ContractStartDate=20150712Z |ContractEndDate=20170701Z|ContractNumber=12384636|
Example: Order Service with existing contract
ContractNumber=12384636|ContractStartDate=20050112Z| ContractDuration=12|
|
|
Maximum Start Date: Upto 60 days from date of PO submission
Minimum Start Date: Current Date of PO submission + Product OffSet (for End date Alignment enabled SWSS Technical Service SKUs). Product Offset value is currently set as 7 in ItemHub for all the End Date Alignment enabled Technical Service SKUs.
Maximum End Date: 60 Months from Start Date minus 1 day
Duration: 1 day to 60 months (for End date Alignment enabled SWSS Technical Service SKUs)
If End Date is present for an initial purchase service, system will ignore the duration (if any) passed in the PO request. System would calculate and store duration based on the Start Date and End Date.
If End Date is present without a Start Date for an initial purchase service, then the system should stamp the Start Date as Current date of PO Submission + ProductOffSet. The “ProductOffSet” value would be set up in SPA/ItemHub for these SKUs with value = 7 which is to accommodate the Product Shipment time. This “ProductOffSet” value will ensure that the Service would not be started prior to the Product shipment. Any delay in the manufacturing / shipment of product would result in further delay of the Actual Service Start Date.
For the End Date Alignment eligible Initial Purchase technical service SKUs, if Partner has provided FSSD value along with Start Date and/or End Date, then system will ignore the FSSD value.
The CCW Config service would validate the Start Date + End Date or Start Date + Duration value provided for the SKUs and if the validation fails, the PO will be rejected with appropriate message.
22.Product and Order Price a.Currency Code
The currency code is the three-character ISO code for the global currency (for example, ‘USD’ for US dollars).
With 3A4 XML orders, the currency of the given Price List Identifier determines the PO currency for both PO amount and product price. See the subsection that follows.
b.Price List Identifier
Cisco assigns Price List to partners with which they can place orders. If the Price List sent in PIP 3A4 PO Request is not in the Partner’s Cisco Profile, entitlement will fail. The PO Request will reject and an error will return in the 3A4 PO Confirmation.
Partners have to identify the price list used for an order. This allows Cisco to validate the prices. Partners should contact their B2B Project manager for the Price List ID for the price lists they are using.
The Price List Identifier can also be obtained from the output of the AcquireQuote Web Service.
Cisco rejects 3A4 XML orders if a price list id is missing or an invalid price list id is given.
Table 70: PIP 3A4 Version 02.00.00 for Price List Identifier
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: PriceListIdentifier
Example: PriceListIdentifier=GLUS
|
Char
|
Share with your friends: |