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



Download 1.42 Mb.
Page25/34
Date31.01.2017
Size1.42 Mb.
#13087
1   ...   21   22   23   24   25   26   27   28   ...   34

e.Order Processing Notes


Partners can enter order processing instructions for the customer service specialist.

The optional nature of specifying order processing notes is evidenced by a cardinality value of 0..1 I in the table that follows.



Table53: Order Processing Notes - Purchase Order

No.

Cardinality

PIP Element

Notes

Field Length

63

0..1

|-- comments.FreeFormText

Order processing notes

Char(2000)

Note: Customer Service processes order processing notes. If an Order Processing Note is attached to an order, the order is placed on hold. The hold must be removed before the order can be fulfilled. Holds can result in delays to order processing.

f.Order Notes


Partners can enter order notes on the Purchase Order for their own references. Cisco would not take any action on these but these can be viewed on the Order View status screen.

The optional nature of specifying order notes is evidenced by a cardinality value of 0..1 I in the table that follows.



Table 54: Order Processing Notes - Purchase Order

No.

Cardinality

PIP Element

Notes

Field Length

63

0..1

|-- comments.FreeFormText

Key value pair for specifying Order Notes Text

OrderNotes=




Char(2000)

Note: Order Processing Notes and Order Notes are utilizing the same PIP element in PO. The derivation logic would be as follows:

  • System checks if the string “OrderNotes=” is present. If yes, then system will consider text after the string as Order Notes and text before the string as Order Processing notes

If there is no string ‘OrderNotes=’ then system will consider all the text as Order Processing Notes.

g.SWIFT and eDelivery Products


Software Infrastructure and Fulfillment Technology (SWIFT) enables e-fulfillment capabilities for initial purchase and support upgrades with a long-term focus on the enablement of electronic channel fulfillment models.

When partners submit orders for a SWIFT or eDelivery product, they can provide one or more email addresses (comma separated) used to receive a URL and a license key for the products. Partners can provide the email address under the “eDeliveryemail” key/value pair at the Line level.

If the SWIFT email address is not provided, the eDelivery Application has the logic to internally derive the delivery email based on the company accounts set up.

The system shall identify the possible delivery types for an SKU being ordered and use the following defaulting logic. Delivery Method is not a new attribute on the XML order.

If a SKUs only compatible delivery method is “Physical”, the delivery method defaults to physical. (Covers Regular SKU Scenario)

If a SKUs only compatible delivery method is “Electronic”, the delivery method defaults to electronic. (Covers L-SKU Scenario).

If a “Single SKU” can be ordered both electronically and physically, the delivery method is retrieved from the partner’s profile (Covers the Single SKU Scenario). If a delivery preference is not specified the order is rejected.

For SKUs that can be delivered electronically, the SKU is delivered at the email address specified in the “eDeliveryemail” email address tag field.

The table that follows indicates the optional nature of SWIFT and eDelivery of products. This fact is evidenced by a cardinality value of 0..1.

Table 55: PIP 3A4 V02.00.00 - Swift and eDelivery Products

No.

Card

PIP Element

Notes

Field Length

304

0..1


|-- proprietaryInformation.FreeFormText


Multiple email ids can be provided by using comma (“,”) as the delimiter.


Example: eDeliveryemail=abc@company.com,xyz@company.com

150









h.Flexible Service Start Delay (FSSD)


FSSD allows partners to order Product + Service in CCW and automatically delay service start up to 60 days after ship date. FSSD is being released as Limited Availability which will allow Cisco to evaluate business impact.

In order to indicate a delay period, partners can send in a new name value pair will be sent for every service/subscription line at line level or kitRef Line.

For an initial purchase of service (both product & service on same PO or PO coming with Service lines which are covering products that are not yet shipped), system does not expect the Service Start Date to be present on the PO and if this is present, system will ignore it. Service Start Date in these scenarios are based on Product shipment unless the user qualifies for FSSD and has provided the value in the PO.

Table56: PIP 3A4 V02.00.00 – Flexible Service Start Delay

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.
Example: flexibleServiceStartDelay = numeric value 1-60












The following validations are enabled in regards to processing orders with line having FSSD –



Ineligibile Partner/Distributor placing orders with FSSD(if the BID,Customer# and Service level Combination are not valid for FSSD

Order rejected

The FSSD delay for the Technical services and subscriptions within a configuration should be SAME,i.e only one unique value of FSSD should be allowed per configuration/ATO. Orders with different FSSD per configuration/ATO

Order rejected

FSSD is not applicable on service only orders or partial service orders. FSSD on service only or partial service orders

Order rejected

FSSD value must be numeric. PO line having non-numeric FSSD value

Order rejected





Download 1.42 Mb.

Share with your friends:
1   ...   21   22   23   24   25   26   27   28   ...   34




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

    Main page