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

h.Financing Terms

Partners need to provide a value in the PIP due to cardinality rules. This fact is evidenced by a cardinality value of 0..1, also in the table. Please send the value as “Mutually Defined/Determined by TPA”.

Table : Financing Terms

No.	Cardinality	PIP Element	Notes	Field Length
78	0..n	|--FinancingTerms	Required tag	N/A
79	0..1	| |--GlobalFinanceTermsCode	Send the value “Mutually Defined/Determined by TPA”.	N/A

i.Order Shipping Information

i.Request Ship Date

Cisco booking policy requires that all orders have a requested ship date within 90 days of the date of submission. Orders with any lines having a requested ship date outside of 90 days of the submission date are rejected.

ii.Shipping Address

A valid shipping address must contain at least address line 1, the city, and the country code. Postal code (ZIP code) and state/province are required for American, Canadian, and European addresses.

If all ordered lines are to ship to one address, they can provide the shipping address at the PurchaseOrder level. In this case, if partners have not provided line level addresses, Cisco will make every effort to cascade this header level ShipTo address to the line level shipTo address. Partners will send in ShipTo address freeform text rather than the ShipTo address ID. We recommend that partners not include a Ship To address ID, as this may result in delays in the order process.

If the partner submits data at the ProductLineItem level, Cisco will ship this line to the given address. The line level addresses will override any order level addresses provided on the same 3A4 PO request.

Cisco validates provided ship to and end user addresses against country postal guidelines for completeness and validity. Addresses that do not conform to the below guidelines may cause the submitted order to require manual review by Cisco’s order processing team. This can delay subsequent order cycles.

Please ensure that you consider the following guidelines when developing your ship to and end user address mapping:

Insert street address in line 1, unless additional department name or building information is required for delivery.

If additional company department or building information needs to be included, please use address line 1 (and 2 if necessary). Street address should be placed in the next address line.

Insert contact names and contact details in the relevant contact elements, not in the address line fields.

Any additional delivery instructions should be inserted in the packing slip or carton notes fields. More information on this can be found in Section 4.12, Shipping and Packaging Notes.

PO Box references should not be used in ship to addresses.

RegionName (state/province) is mandatory for Japan, US, or Canadian addresses.

The tables that follow provide required, optional, and non-required data for the Shipping Address. Request Ship Date information is also captured.

(O) is a optional data for a valid address; it is not part of common address format for that country.

(N/A) data is not required for a valid address; it is not used in that country.

Refer to appendix C for complete list of such rules.

Note: customer name, country and address line 1 are mandatory
If partners do not provide shipping address at either the Product Line level or the Purchase Order level, Cisco will run defaulting rules as specified in Appendix C: Address Processing to make every effort to process the order. If Cisco is unable to work through any of the defaulting rules, Cisco will reject the order.

Canadian Tax Code is derived from the Ship To address by Tax Services and applied accordingly (if the ship to address is in Canada) later in the process. This default applies regardless of whether the partner has provided the code in the order XML.

Table : PIP 3A4 V02.00.00 - Line Level Requested Ship Date and Address