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

a.ConfigRef

There can be only one ConfigSet ID or Esimate ID on a purchase order.

The expanded/newly created lines echo back in the 3A4 Confirmation message and contain the same PO Line Reference Number that was provided on the major line.

To use the ConfigSet ID based Config Ref functionality, partners need to provide:

A ConfigRef ID on the applicable product line item

The major line and all minor lines that have a dollar value applicable to the ConfigRef ID

If the partner provides an invalid ConfigRef ID, the order rejects.

The ConfigRef is an existing ConfigSet ID (that is, the ConfigSet was already created).

All minor lines that have a dollar value on the ConfigSet (for example, CS123456) have been provided and all have the ConfigRefId in the proprietary information field.

PIP Element#304: proprietaryInformation.FreeFormText

The quantity on the PO could be a multiple of the quantities on the ConfigSet.

If two major lines within the ConfigSet have the same minor item, the PO should include these minor items as separate lines with the corresponding quantity defined in the ConfigSet; no collapsing of lines is allowed. If two major lines within the ConfigSet have the same minor item, the PO should include these minor items as separate lines with the corresponding quantity defined in the ConfigSet; no collapsing of lines is allowed.

The number of lines listed with a particular ConfigRef should correspond with the same number of lines provided on the PO other than the non-configurable spare lines

If any of the above validations fail, the order rejects. The expanded lines display on the PO Confirmation message.

ConfigRef and KitRef cannot be used together in a PO.

When using ConfigRef function, Line Level Proprietary Information for all configurations of a config set, such as MOVE values (except getLatestSoftware), will have the value submitted with the first configuration of the config set.

ConfigRef function does not work for Bundled Products.

There can be only one ConfigRef ID in a PO.

There cannot be multiple lines in the PO referenced to different ConfigSet IDs.

In case of 0$ majors which have priced minor’s in the ConfigSet, it is expected for the PO to have the 0$ priced major explicitly on the PO, else system is unable to expand to a valid configuration

Line ID and Parent Line ID are required for ConfigRef processing for all the priced minors and any 0 pirced majors on the saved configuration

ZPL is not supported on configSet ID based configRef orders and hence ZPL Country name value pair is not expected on configRef orders
To use the Estimate ID based Config Ref functionality, partners need to provide:

A Estimate ID on the applicable product line item

The major line(s) and all its corresponding minor lines that have a dollar value applicable to the Estimate ID

The structure of the major and minor line items

If the partner provides an invalid ConfigRef ID, the order rejects.

The following conditions define a valid ConfigRef ID:

The ConfigRef is an existing Esimate ID (that is, the Estimate was already created).

Estimate ID starts and ends with an alpha

All minor lines that have a dollar value on the Estimate (for example, CS123456) have been provided and all have the Esimate ID in the proprietary information field.

PIP Element#304: proprietaryInformation.FreeFormText

The quantity on the PO could be a multiple of the quantities on the Estimate.

If two major lines within the Estimate have the same minor item, the PO should include these minor items as separate lines with the corresponding quantity defined in the Estimate; no collapsing of lines is allowed.

The number of lines listed with a particular Estimate should correspond with the same number of lines provided on the PO other than the non-configurable spare lines.

If any of the above validations fail, the order rejects. The expanded lines display on the PO Confirmation message.

For Estimate based ConfigRef orders with/without standard, RNSD Deal Id, if there are any price discrepancy between the system calculated net price and net price on PO, system will retain price on the order, however the order processing is delayed since a task is created for Cisco Customer Service ops for follow up.

If there is no discrepancy on the system calculated price and the price on the purchase order (estimate price) then the order is autobooked and no warnings/tasks are raised.

Known Limitations

ConfigRef and KitRef cannot be used together in a PO.

When using ConfigRef function, Line Level Proprietary Information for all configurations of a config set, such as MOVE values (except getLatestSoftware), will have the value submitted with the first configuration of the estimate.

There can be only one Estimate ID in a PO.

There is no support for non-configurable spares coming along with a Estimate ID based ConfigRef order. Such orders will be rejected.

In case of 0$ majors which have priced minor’s in the Estimate, it is expected for the PO to have in the 0$ priced major explicitly on the PO, else system is unable to expand to a valid configuration

Line ID and Parent Line ID are required for ConfigRef processing for all the priced minors and any 0 pirced majors on the saved estimate

ZPL is not supported on Estimate ID based configRef orders and hence ZPL Country name value pair is not expected on configRef orders