Another way to specify shipping instructions is to send values that comply with Cisco’s Shipment Routing Configuration Tool. These values infer a shipment routing lane based on the ship-to location and the shipment service level. Because this data is Cisco-specific, Cisco gives partners the ability to provide this information in the proprietaryInformation.FreeFormText field. The optional status of these fields are evidenced by cardinality values of 0..1 in the table that follows.
Routing Preference – This field allows the customer to specify who will be responsible for providing the freight carrier for shipping products. Valid values are:
“Cisco Routed”
“Customer Routed”
The system will derive the freight carrier code and account number from the Shipment Routing Configurator Tool (SRCT), if the RoutingPreference is ‘Customer Routed’ but no value is provided for these fields on the 3A4 XML order. Derivation is performed by the system before the order is imported into ERP, however this information is not reflected on the POA In case these are not setup in the SRC tool, then system raises tasks to reflect the same.
MoveServiceLevel – This field allows the customer to specify the service level for shipments. Valid values are:
“Standard”
“Premium”
“Express”, which delivers the fastest and is the most expensive service.
“Deferred”
Table : Purchase Order Level in PIP 3A4 V02.00.00
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; no whitespace should be around equal sign.
Name: RoutingPreference
Name: MoveServiceLevel
Example:
RoutingPreference=Cisco Routed
MoveServiceLevel=Standard
|
|
|
|
|
Table : ProductLineItem Level in V02.00.00
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; no whitespace should exist around equal sign.
Name: RoutingPreference
Name: MoveServiceLevel
Example:
RoutingPreference=Cisco Routed
MoveServiceLevel=Standard
|
|
Note –
-
If Routing Option is "CISCO", the below attributes passed in the PO request will be not be considered by Cisco Systems while capturing the order.
- Specific Delivery Time
- Authorized Receiving Party
- Carrier will call
- Remove packaging
- Contact prior to delivery
- Inside delivery required
-
If the Routing Option is "CISCO" or "SELF", the below Delivery Option Notes will be ignored by Cisco Systems while capturing the Order.
- Remove Packaging
- Pre-Shipment Inspection
l.Shipping and Packaging Notes
Partners can provide the shipping and packaging notes that display on all packing slips and invoices.
Partners can also include text to display on the carton labels or carton notes, by using the below 3A4 PIP elements on both order level and line level. Information below is regarding line level shipping and packing notes.
All three PIP elements are optional, as evidenced by cardinality values of 0..1 and 0..n in the fields of the table that follows.
Table : PIP 3A4 V02.00.for Shipping and Packaging Notes
No.
|
Cardinality
|
PIP Element
|
Notes
|
Field Length
|
123
|
0..1
|
| |-- packListRequirements.FreeFormText
|
Shipping and Packaging notes; display on all packing slips and invoices
|
CHAR(2000)
|
203
|
0..n
|
||||-- GlobalSpecialHandlingCode
|
If the value of field is sent as “Attachment – Customer’s Document”, value in element 204 is interpreted as carton notes.
|
|
204
|
0..1
|
||||-- specialHandlingText.FreeFormText
|
Carton notes, if value in element 203 is “Attachment - Customer's Document”.
Note: Actual Carton label can only accommodate 80 characters including spaces.
|
|
Share with your friends: |